Blog


Management No Comments

determining the architectural “macro” view for the software

Essentials of Software Engineering, Fourth Edition

Ch6

True/False

1. All requirements activities are needed in the same degree for all software projects.

True/False

2. A software engineering team must plan requirements engineering activities for all software projects.

Multiple Choice

3. Requirements elicitation must have a set of organized questions to ask the:

[1] clients.

[2] users.

[3] business.

[4] All of these are correct.

[5] clients and users.

True/False

4. During the requirements elicitation, the list of what the customer wants as the functions for the new software is not elicited, just what the business needs to do.

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.

True/False

6. A use case contains requirement information.

True/False

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.

True/False

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.

Comments are closed.

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