Managing Software Requirements: A Use Case Approach, Second Edition

Chapter 20. Software Requirements—A More Rigorous Look

Key Points

• A complete set of requirements can be determined by defining the inputs, outputs, functions, and attributes of the system plus the attributes of the system environment.

• Requirements should exclude project-related information, such as schedules, project plans, budgets, and tests, as well as design information.

• The requirements/design process is iterative; requirements lead to the selection of certain design options, which in turn may initiate new requirements.

• Design constraints are restrictions on the design of the system or on the process by which a system is developed.

In the prior team skills, the features we defined and the use-case model we developed for the system were purposely ...