Chapter Summary

  • A requirements specification is a collection of documents and models that attempt to unambiguously describe a software system to be built.

  • A requirements specification needs to be made available to nearly everyone connected with the project.

  • A requirements specification is a contract that binds the stakeholders to accept a system that meets the criteria specified in the requirements documents.

  • A requirement, a constraint that the system must observe, is typically expressed as a statement that begins with a phrase like "The system shall …."

  • It is important to objectively prioritize every requirement.

  • Use cases are a powerful technique for capturing and expressing detailed system behavior. A use case is a textual description of the ...

Get Building Web Applications with UML now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.