Requirements Writing for System Engineering

  • George Koelsch

Table of contents

  1. Front Matter
    Pages i-xxiii
  2. The Foundation of Requirements

    1. Front Matter
      Pages 1-1
    2. George Koelsch
      Pages 3-29
    3. George Koelsch
      Pages 31-74
    4. George Koelsch
      Pages 75-80
  3. Types of Requirements

    1. Front Matter
      Pages 81-81
    2. George Koelsch
      Pages 83-105
    3. George Koelsch
      Pages 107-149
    4. George Koelsch
      Pages 169-194
    5. George Koelsch
      Pages 195-207
  4. Cradle to Grave Requirements

    1. Front Matter
      Pages 209-209
    2. George Koelsch
      Pages 211-243
    3. George Koelsch
      Pages 245-255
    4. George Koelsch
      Pages 257-272
  5. Alternatives to Shall Requirements

    1. Front Matter
      Pages 273-273
    2. George Koelsch
      Pages 301-326
    3. George Koelsch
      Pages 327-348

About this book


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 covers techniques for defining user needs so you can determine which combination of approaches to use for your projects. You’ll also learn how to analyze different development methodologies so that you can determine the advantages and disadvantages 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.

This book

  • Presents many techniques for capturing requirements.
  • Demonstrates gap analysis to find missing requirements.
  • Shows how to address both software and hardware, as most projects involve both.
  • Provides extensive examples of “shall” statements, user stories, and use cases.
  • Explains how to supplement or replace traditional requirement statements with user stories and use cases that work well in agile development environments 


Modeling Techniques User Story Requirements Collection Requirements Engineering Requirement Engineers Functional Requirements Interface Control Documents Requirements Documents Physical Requirements Section 508 Use Cases Acceptance Criteria Requirements Creep

Authors and affiliations

  • George Koelsch
    • 1
  1. 1.HerndonUSA

Bibliographic information

  • DOI
  • Copyright Information George Koelsch 2016
  • Publisher Name Apress, Berkeley, CA
  • eBook Packages Professional and Applied Computing
  • Print ISBN 978-1-4842-2098-6
  • Online ISBN 978-1-4842-2099-3
  • About this book