Requirements

Question 1

a set of statements that describe the user’s needs and desires

Answer 1

Requirements

Question 2

One of the top reasons for software project failures is ________ requirements specifications

Answer 2

INCOMPLETE

Question 3

One of the essential reasons for project success may be attributed to ______ requirements statements

Answer 3

Clear

Question 4

Requirements Engineering Activities in a Software Project

Answer 4

Elicitation, Documentation and Definition, Specification, Prototyping, Analysis, Review and Validation, Agreement and Acceptance

Question 5

(Preparing for Requirements Processing) requirements gathering and requirements engineering is to ensure that all the preparations are made and all requirements engineering activities are planned.

Answer 5

First step

Question 6

(Preparing for Requirements Processing) whether the underlying structure follows Agile/flexible approach or a more traditional or rigorous one.

Answer 6

Agree to a process

Question 7

(Preparing for Requirements Processing) The plan should include the following

Answer 7

Process, Resource needed, Schedule

Question 8

(Preparing for Requirements Processing) the plan itself may take several hours or days, or weeks to develop.

Answer 8

Depending on the size and complexity of the project,

Question 9

(Preparing for Requirements Processing) Once the plan is drawn, it must be _____

Answer 9

reviewed and agreed upon by ALL parties involved.

Question 10

(Preparing for Requirements Processing) After the plan is agreed upon, the resources from experienced analysts to the________ – must be acquired and brought on board

Answer 10

required prototyping tools

Question 11

(Preparing for Requirements Processing) Good requirements analysts must possess multiple talents:

Answer 11

Communication, Special industry, technical

Question 12

(Preparing for Requirements Processing) The people involved must be _______ in requirements engineering activities

Answer 12

properly trained on the tools and the process that would be used

Question 13

Requirements Engineering Process:

Answer 13

Elicitation, Analysis, Requirements definition, prototyping, Review, Specification, agreement

Question 14

(Requirements Engineering Process) The process begins with requirements analysts performing the elicitation and gathering of requirements from users and customers

Answer 14

Elicitation

Question 15

(Requirements Engineering Process) During the analysis step, various requirements statements are checked for accuracy and conflict, categorized, and prioritized

Answer 15

Analysis

Question 16

(Requirements Engineering Process) Clearly, the analyzed requirements must be properly defined and documented

Answer 16

Requirements Definition and Documentation

Question 17

(Requirements Engineering Process)If necessary, user Interface aspects need to be prototyped

Answer 17

Prototyping

Question 18

(Requirements Engineering Process) The defined and documented requirements and statements and prototyped user interfaces must be reviewed by the users

Answer 18

Review

Question 19

(Requirements Engineering Process) This document will serve as the “contract” between the customer and the software development organization

Answer 19

Agreement

Question 20

(Requirements Engineering Process) Once the requirements specifications are agreed upon, they become the BASELINE

Answer 20

Agreement

Question 21

(Requirements Engineering Process) Thereafter, any modification or change request needs to be controlled and managed through a change control process to prevent the infamous project SCOPE CREEPING problem.

Answer 21

Agreement

Question 22

where the project slowly grows in size without anyone’s detection

Answer 22

Scope Creeping