Chapter 28. Technical Methods for Specifying Requirements

Throughout this book, we have assumed that most requirements will be written in the team's natural language, be it in the form of a traditional statement or via the use-case method. We also suggest that requirements be augmented with diagrams, tables, or charts or other techniques to help clarify the meaning of a user ...

Get Managing Software Requirements: A Unified Approach now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.