The requirements state Session 1 (COSE Lesson 43)

This module covers requirements, providing an overview of the problems (as well as corresponding solutions) posed by the need to collect well-written requirements and how to deal with poorly articulated requirements. The module also covers the much-neglected Systems Engineering Management Plan (SEMP) and how to create it.

Contents

1. The critical applied systems engineering tasks which systems and software engineers must perform in the requirements identification stated
2. A little-known way to capture poor requirements and convert them into well-written requirements
3. An improved template for a requirement statement
4. How to convert stakeholder needs into well-written requirements using some systems thinking tools
5. How to minimize missing requirements using a mixture of class-of-system generic and system-specific requirements
6. Why a requirement must be more than just the statement, “the system shall”
7. How the different mission and support requirements can provide greatest flexibility to designers
8. Where and how requirements are used in the systems development process
9. Some of the consequences of poorly written requirements

Notes

• 0701-1 The requirements state Session 1 notes (Version 4.0.1)

Readings

• None