Elicitation and Gathering

Question 1

Agile processes has worked well for _____ projects

Answer 1

SMALL

Question 2

We will always need experienced _____ requirements analyst for large projects because of the limited availability of knowledgeable users

Answer 2

subject matter experts (SME)

Question 3

2 levels of requirements elicitation

Answer 3

HIgh level, low level

Question 4

The requirements analyst must probe and understand the business rationale and justification for the software or the software project

Answer 4

High Level

Question 5

The requirements analyst must elicit and gather the details of the users’ needs and desires

Answer 5

Low Level

Question 6

The actual elicitation may be conducted in several modes:

Answer 6

Verbal, Written, Online

Question 7

_____ is highly recommended for users to expand on their input

Answer 7

Verbal follow up

Question 8

Throughout all the elicitation and gathering process, the requirements analyst must possess the following vital skills:

Answer 8

be patient, listen carefully, ask for more information when needed

Question 9

The requirements analyst should also gather existing information that is available in the following documents:

Answer 9

business process document, business and technical policy document, previous system manual

Question 10

Information that contributes to this high-level business profile includes:

Answer 10

Opportunity/needs, justification, scope, major constraint, major functionality, success factor, user characteristics

Question 11

(High level) State what high-level problems the software suppliers have been brought in to address

Answer 11

Opportunity/needs

Question 12

(High level) The company may be losing 50% of customer orders due to poorly managed documents

Answer 12

Opportunity/needs

Question 13

(High level) Some type of business payback

Answer 13

Justification

Question 14

(High level) The customer may state that there is P2M of extra inventory

Answer 14

Justification

Question 15

(High level) Establish the limits and scope of the project

Answer 15

Scope

Question 16

(High level) The above-mentioned inventory and customer orders are the two top problems that need to be solved ASAP, such that these become areas of MAJOR requirements

Answer 16

Scope

Question 17

(High level) The allotted budget for the software project.:

Information on budget constraints is important when detailed requirements are being prioritized

Answer 17

Major Constraint

Question 18

(High level) Vital to have a list of what the customer and the business executives perceive as the major functionality the new software will be delivered

Answer 18

Major Functionality

Question 19

(High level) goes back to the opportunity and needs stated earlier

Answer 19

Success Factor

Question 20

(High level) Success of the system depends heavily on how well the users are trained

Answer 20

User Characteristics

Question 21

(High level)
- person’s job title and formal responsibilities,
- job activities,
- education and experience levels and
- technical competence

Answer 21

User Characteristics

Question 22

During this activity, some of the more technically savvy requirements analysts should be brought in

Answer 22

Low Level

Question 23

Low level requirements:

Answer 23

Individual Functionality, Business flow, Data and data formats, User Interfaces, Systems with other interface, (Reliability, Performance, Security, and Adaptability)

Question 24

(low level) Most obvious group and usually the natural starting point of requirements elicitation

Answer 24

Individual Functionality

Question 25

(low level) Functionality by itself is not enough, it must be explained in the context of the______ or in the context of how users perform their tasks

Answer 25

business flow

Question 26

(low level) What is the information that needs to be entered into the system and for what purpose?

Answer 26

data and data fromats

Question 27

(low level) How the input and output of a software system is presented

Answer 27

user interfaces

Question 28

(low level) Besides interface with users, there are other interfaces such as those with an existing application or to a network system

Answer 28

Systems with other interface

Question 29

(low level) Serves as a catchall group and acts as a prompter for all nonfunctional requirements that are important to a software project

Answer 29

Reliability, Performance, Security, and Adaptability

Question 30

addresses the system is up

Answer 30

Availability

Question 31

addresses the issue of it functioning properly WITHOUT defect and according to specification

Answer 31

Reliability