Management No Comments

degree for software projects.

Multiple Choice

5. The requirements gathered are clustered by:

[1] individual functionality.

[2] business flow.

[3] data and data format.

[4] All of these are correct.


6. A use case contains requirement information.


7. Requirements definition involves formally spelling out the requirements.

Multiple Choice

8. Graphically depicting a system’s data flow is done with the:

[1] Unified Modeling Language (UML).

[2] data flow diagram (DFD).

[3] entity-relationship (ER) diagram.

[4] All of these are correct.


9. SRS is the artifact that spells out the final specific software requirements from the requirements engineering activities.

Multiple Choice

10. The pages of documentation in the SRS depend on:

[1] size, complexity, and customer support activities for the project.

[2] plan releases of the project.

[3] software engineering’s knowledge of the project’s subject area.

[4] All of these are correct.

Chapter 6

Multiple Choice

1. The set of statements that describe the user’s needs and desires are the:

[1] plans.

[2] requirements.

[3] designs.

[4] All of these are correct.

[5] plans and requirements.

2. Incomplete requirement specification will always contribute to:

[1] project development time.

[2] project costs.

[3] project failures.

[4] All of these are correct.

[5] project development time and project costs.

3. Subject matter experts are used instead of users and customers when the software project:

[1] is large and complex.

[2] is small and simple.

[3] is developed with an Agile process.

[4] has a high level of requirements.

[5] has a low level of requirements.

4. Analysis of the requirements consists of:

[1] categorizing the requirements.

[2] clustering the requirements.

[3] prioritizing the requirements.

[4] All of these are correct.

[5] categorizing and clustering the requirements.

5. All requirements must be enumerated uniquely. Why?

[1] Traceable

[2] Identifiable

[3] Categorized

[4] All of these are correct.

6. The SRS has a recommended standard guideline from _____.




D. All the above

E. A and B only


1. Requirements are the “what” and design is the “how.”

2. The requirements engineering activities include review and validation, which are the testing of the requirements.

3. High-level requirements elicitation serves as the opportunity, needs, and justification for the software project in the client’s business world.

4. Low-level requirements elicitation uncovers constraints for the software project to be developed.

5. Collection of the detail level information pertaining to data and their formats includes the input and output data of the software system.

6. The requirements are ordered once they are elicited and collected.

7. The detailed requirements section of the SRS is the shortest section.

Comments are closed.

Open chat
Whatapp Us
Hey? You want your project done, Whatsapp us Now.
Click to Submit a Project