SWE-PART 3

Which of the following is NOT a way to deal with risks in software development?

• avoid (replan or change requirements)
• ignore (act as if it won't happen)
• mitigate (devise tests to see if it occurs)
• confine (restrict the scope of its effect)
• monitor (constantly be on the lookout for it)

Which reason for the failure of or problems with software development is NOT related to requirements capture?

• incomplete requirements captured
• lack of user involvement
• unrealistic user expectations
• lack of resources
• changing requirements and specifications

SRS stands for _____

• Software Resource Solution
• System Refinement Solution
• Structured Requirements Specification
• System Requirements Specification
• Structured Refinement Solution

The best way to conduct a requirements validation review is to

• examine the system model for errors
• have the customer look over the requirements
• send them to the system design team and see if they have any concerns
• use a checklist of questions to examine each requirement
• categorize the requirements into functional and nonfunctional

Having quality design goals is of most help in reducing the complexity of:

• designing the system.
• building the system.
• maintaining the system.
• cost and time estimates for developing the system.
• understanding the system.

Which of the following is a benefit of having a software development process?

• It is not necessary to train the developers.
• We have to gather fewer requirements from users.
• It is easier to divide up the work among development team members.
• It is not necessary to maintain the system.
• There is less need for the development team to communicate with the users.

In domain modeling we capture the system's most important

• user interfaces.
• functional requirements.
• use cases and scenarios.
• classes and associations.
• acceptance tests.

All required functionality is described in the

• actor directory.
• class library.
• use cases.
• scenario book.
• task description.

Actors are connected to use cases only by

• association relationship.
• dependency relationship.
• generalization relationship.
• inheritance relationship.
• realization relationship.

A use case captures the system's behaviour from which point of view?

• design
• developer's
• user interface
• user's
• domain model