Book description
Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement “patterns” offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification.
A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it’s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need—determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs—giving developers the valuable advice they need for building effective software requirements
Table of contents
- Foreword
- Preface
-
I. Setting the Scene
- 1. Synopsis of “Crash Course in Specifying Requirements”
- 2. Synopsis of “The Contents of a Requirements Specification”
-
3. Requirement Pattern Concepts
- 3.1 Introduction to Requirement Patterns
- 3.2 The Anatomy of a Requirement Pattern
- 3.3 Domains
- 3.4 Requirement Pattern Groups
- 3.5 Relationships Between Requirement Patterns
- 4. Using and Producing Requirement Patterns
-
II. Requirement Pattern Catalog
-
5. Fundamental Requirement Patterns
-
5.1 Inter-System Interface Requirement Pattern
- Basic Details
- Applicability
- Discussion
- Content
- Template(s)
- Example(s)
- Extra Requirements
- Resilience and Availability Requirements
- Traffic Verification and Recording Requirements
- Upgrade Requirements
- Security Requirements
- Documentation and Third-Party Interface Development Requirements
- Considerations for Development
- Considerations for Testing
- 5.2 Inter-System Interaction Requirement Pattern
- 5.3 Technology Requirement Pattern
- 5.4 Comply-with-Standard Requirement Pattern
- 5.5 Refer-to-Requirements Requirement Pattern
- 5.6 Documentation Requirement Pattern
-
5.1 Inter-System Interface Requirement Pattern
- 6. Information Requirement Patterns
- 7. Data Entity Requirement Patterns
- 8. User Function Requirement Patterns
- 9. Performance Requirement Patterns
- 10. Flexibility Requirement Patterns
- 11. Access Control Requirement Patterns
- 12. Commercial Requirement Patterns
-
5. Fundamental Requirement Patterns
- Glossary
- A. References
- Index
- About the Author
- Copyright
Product information
- Title: Software Requirement Patterns
- Author(s):
- Release date: June 2007
- Publisher(s): Microsoft Press
- ISBN: 9780735623989
You might also like
book
Software Requirements, Second Edition
Learn effective, field-tested techniques to manage the requirements engineering process and get expert guidance from a …
book
Visual Models for Software Requirements
Apply best practices for capturing, analyzing, and implementing software requirements through visual models—and deliver better results …
book
Incremental Software Architecture
The best-practices solution guide for rescuing broken software systems Incremental Software Architecture is a solutions manual …
book
Economics-Driven Software Architecture
Economics-driven Software Architecture presents a guide for engineers and architects who need to understand the economic …