Deck 4: Gathering Requirements

Question 1

Requirements identify the ________ that the information system users want to achieve.

A) objectives
B) verifications
C) quality
D) reliability

Answer 1

objectives

Question 2

Gathering requirements is an ongoing process that provides system development with ________ that it must implement to satisfy its objectives.

A) tools
B) technology
C) features and rules
D) right people

Answer 2

features and rules

Question 3

The reliability and the correctness of requirements is dependent on ________.

A) their sources
B) the techniques that we employ to elicit and verify them
C) effective management
D) all of the above

Answer 3

all of the above

Question 4

Like any other product, an information system must have ________ that its customer wants in order to achieve specific objectives.

A) a name
B) features
C) the quality
D) the size

Question 5

Which of the following is NOT one of the elicitation techniques for gathering requirements?

A) quality assurance
B) interviews
C) modeling
D) document analysis

Question 6

Which of the following is a source for requirement gathering?

A) domain expert
B) programmer
C) designer
D) analyst

Question 7

Which of the following is an example of non-functional requirements?

A) features of the system
B) reliability
C) business rules
D) business objectives

Question 8

In an object-oriented approach to software development, we use ________ to capture, define, and represent requirements.

A) models
B) UML
C) common sense
D) ERP

Question 9

To accomplish each tactical goal, the system and its users must interact in a set of clearly defined steps-called ________.

A) non-functional requirements
B) functional requirements
C) operational requirements
D) daily and non-daily requirements

Question 10

The mission of an ATM system is to allow customers to perform many banking transactions through automated teller machines. Which of the following would NOT be considered as an objective for ATM system?

A) get cash
B) deposit check
C) transfer money
D) buy mutual bonds

Question 11

________ are deployed to model requirement gathering.

A) Use cases
B) UML
C) SDLC
D) Functional requirements

Question 12

________ specifies how the behavior of the system must be tailored to the level of its users' expertise.

A) Reliability
B) Testability
C) Usability
D) Maintainability

Question 13

A reliable system is both ________ and ________.

A) cheap, easy to use
B) dependable, available
C) expensive, difficult to use
D) possible, probable

Question 14

Performance of the system must be ________.

A) proven
B) fast
C) measurable
D) inexpensive

Question 15

If a piece of software can be updated and enhanced with relative ease, then the software is ________.

A) maintainable
B) user friendly
C) fast
D) reliable

Question 16

The right of access to the services of a system is related to which of the following non-functional requirements?

A) reliability
B) maintenance
C) performance
D) security

Question 17

________ a stakeholder of the system is an indispensable tool not only for its verbal responses but also because it allows one to observe and learn from non-verbal reactions.

A) Observation of
B) A questionnaire from
C) An interview with
D) Document analysis by

Question 18

Which of the following requirement gathering techniques is the most flexible?

A) observation
B) questionnaire
C) document analysis
D) interview

Question 19

Which of the following is (are) the advantage(s) of open questions for an interview?

A) provide leads
B) produce desired results
C) provide the interview with a second chance
D) both A & C

Question 20

"How many employees use the current system?" is an example of a(n) ________ in an interview.

A) closed question
B) open question
C) qualitative question
D) quantitative question

Question 21

In gathering requirements, questionnaires can play two roles: ________.

A) elicitation and quantification
B) elicitation and verification
C) elicitation and qualification
D) elicitation and maintenance

Question 22

Questionnaires have disadvantages such as: ________.

A) they do not happen in real time
B) lack direct interaction
C) they are inflexible
D) all of the above

Question 23

________ is the most traceable tool for the verification of requirements.

A) A questionnaire
B) An interview
C) Observation
D) Document analysis

Question 24

The most expensive requirement elicitation is ________.

A) a requirement workshop
B) an interview
C) joint application development
D) either A or C

Question 25

Dispute settlement is one the advantages of ________.

A) a requirement workshop
B) observation
C) an interview
D) a questionnaire

Question 26

The value of observing a workflow depends on the ________ of the observation.

A) value
B) purpose
C) content
D) observer

Question 27

The observation is wasted if the observer is ________.

A) unqualified
B) too quick
C) too lazy
D) too excited

Question 28

An owner's view is a drawing or a word chart that is primarily aimed at ________.

A) programmers
B) banks
C) analysts
D) business stakeholders

Question 29

An activity diagram models the ________.

A) owner's view
B) business stakeholder's view
C) either A or B
D) programmer's view

Question 30

________ are those who launch the project and decide its fate.

A) Sponsors
B) Domain experts
C) Users
D) Clients

Question 31

________ are those who are the most knowledgeable about the areas of business activity within the project scope.

A) Stakeholders
B) Sponsors
C) Domain experts
D) Clients

Question 32

________ are those whose interests are affected by the operation of the system.

A) Stakeholders
B) Sponsors
C) Domain experts
D) Users

Question 33

________ are those who directly interact with the system.

A) Users
B) Sponsors
C) Domain experts
D) Stakeholders

Question 34

A source of information for reverse engineering is ________.

A) the new system
B) the legacy system
C) the stakeholders
D) the users

Question 35

To avoid missing or conflicting requirements, we need to ________.

A) document and update requirements
B) store information
C) draw conclusion
D) make decisions quickly

Question 36

As accurate as a requirement may be, we must be able to trace the sources to ________.

A) verify the requirements
B) resolve inconsistencies
C) both A & B
D) appease the stakeholder

Question 37

Each requirement must be written in a way that a simple ________ can verify the essence of it.

A) up or down
B) yes or no
C) description
D) true or false

Question 38

Usually missing or conflicting requirements are discovered during ________.

A) design
B) implementation
C) both A & B
D) requirement gathering

Question 39

New information system development is often expected to upgrade, replace, or collaborate with ________.

A) the existing system
B) new equipment
C) old equipment
D) government laws and regulations

Question 40

All requirements derived from reverse engineering must be verified by consulting ________.

A) stakeholders
B) users
C) experts
D) all of the above

Question 41

The task of requirements gathering is to collect and define all features that the information system must have in order to fulfill the objectives that the customer has set.

Question 42

During the process of development, the role of requirements gathering never changes.

Question 43

Requirements discovery is the same as requirements gathering.

Question 44

Requirements define both specific objectives and constraints on those objectives.

Question 45

Requirements discovery is very deep and narrow.

Question 46

Requirements discovery is a phase that takes place at the start of the development process.

Question 47

An analogy to distinguish requirements discovery and requirements gathering would be "requirements gathering locates where we must "drill," while requirements discovery is the act of drilling down.

Question 48

Requirements discovery aims to separate "wish lists" from actual business goals.

Question 49

Requirements gathering acts on the belief that the goals are poorly defined and we must identify what is needed to achieve the goals.

Question 50

Non-functional requirements specify the behavior of the system and the constraints on that behavior.

Question 51

Functional requirements specify how the mission is to be accomplished by achieving tactical goals.

Question 52

To accomplish strategic goals, the system and its users must interact in a set of clearly defined steps.

Question 53

The main device for capturing functional requirements and modeling them is UML.

Question 54

Reliability defines how the behavior of the system must be shaped to fit the users and their work environment.

Question 55

That the interface must be designed for a touch-sensitive screen is an example of non-functional requirement.

Question 56

Reliability requirements generally relate to issues such as availability and accuracy.

Question 57

Performance is simply a hardware issue.

Question 58

How many users a system can handle before its response time becomes unacceptable is an example of a functional requirement.

Question 59

One architectural approach to better maintainability is to construct the software system from components with distinct responsibilities and relative independence of components.

Question 60

To send or receive unencrypted data for a credit card transaction is an example of security requirement.

Question 61

An interview is the least flexible and direct tool for eliciting requirements.

Question 62

Interviewing requires a great amount of "people skill" and experience.

Question 63

Early interviews in the requirements gathering process have a narrow scope, while the later ones are defined by more focus on specificity.

Question 64

An interview is structured when the flow of an interview can be planned according to a script.

Question 65

An interview is focused when the questions center around many topics.

Question 66

When we have discovered and verified a broad outline of requirements, we must then gather specific and detailed requirements.

Question 67

In an interview, the initiative is always with the interviewee.

Question 68

By establishing a profile of the interviewee, the analyst can better evaluate his or her responses on other topics.

Question 69

Understanding how a system functions now is essential for the success of any future plans.

Question 70

Asking questions about limitations must be an afterthought.

Question 71

Open-ended questions can provide us with leads to issues and concepts of which we have been unaware.

Question 72

When prepared questions are not producing the desired results, open-ended questions can provide the interview with a second chance.

Question 73

By asking open-ended questions, the control of the response is shifted to the interviewer.

Question 74

Like open-ended questions, closed questions require the interviewee to give answers that fall within a predictable range.

Question 75

In an interview, a closed question means "answer correctly and answer now!"

Question 76

Probes are requests that the interviewer poses to clarify and expand concepts expressed by the interviewer.

Question 77

Probes are also called "follow-ups."

Question 78

It is a waste of time to end an interview by verifying the responses of the interviewee and the conclusions of the interviewer.

Question 79

Questionnaires are open to misunderstanding.

Question 80

In an interview, it is possible to adjust your wording in response to the reactions of the interviewee. In a questionnaire, such adjustments are impossible.