Learn how to create good requirements when designing hardware and software systems. While this book emphasizes writing traditional "shall" statements, it also provides guidance on use case design and creating user stories in support of agile methodologies. The book surveys modeling techniques and various tools that support requirements collection and analysis. You'll learn to manage requirements, including discussions of document types and digital approaches using spreadsheets, generic databases, and dedicated requirements tools. Good, clear examples are presented, many related to real-world work the author has done during his career.
Requirements Writing for System Engineering of different requirements approaches and implement them correctly as your needs evolve. Unlike most requirements books, Requirements Writing for System Engineering teaches writing both hardware and software requirements because many projects include both areas. To exemplify this approach, two example projects are developed throughout the book, one focusing on hardware and the other on software.
What You Will Learn
- Understand the 14 techniques for capturing all requirements.
- Address software and hardware needs; because most projects involve both.
- Ensure all statements meet the 16 attributes of a good requirement.
- Differentiate the 19 different functional types of requirement, and the 31 non-functional types.
- Write requirements properly based on extensive examples of good ‘shall’ statements, user stories, and use cases.
- Employ modeling techniques to mitigate the imprecision of words.
Requirements Writing for System Engineering| George Koelsch (Author)| Apress
Table of Contents
Part 1. The Foundation of Requirements
Chapter 1. The Importance of Requirements
Chapter 2. What Makes a Good Requirement?
Chapter 3. Specialized Language
Part 2. Types of Requirements
Chapter 4. Functional Requirements
Chapter 5. Nonfunctional Requirements
Chapter 6. Lists of Items and the Order of Steps and Data Elements
Chapter 7. Data Interfaces and Documents
Chapter 8. Physical Requirements
Part 3. Cradle to Grave Requirements
Chapter 9. How to Collect Requirements
Chapter 10. User Interface Requirements
Chapter 11. Managing Requirements
Part 4. Alternatives to Shall Requirements
Chapter 12. Supplementing or Replacing Standard Requirements
Chapter 13. User Stories
Chapter 14. Use Cases
Chapter 15. Revisiting Requirement Problems and Their Solutions
Part 5. Appendixes
Acronyms and Abbreviations
Requirements Documents
Section 508 Compliance
Glossary
Bibliography
LINK FOR THE BOOK
