ATI's Systems Engineering - Requirements course

This three-day course provides system engineers, team leaders, and managers with a clear understanding about how to develop good specifications affordably using modeling methods that encourage identification of the essential characteristics that must be respected in the subsequent design process. Both the analysis and management aspects are covered. Each student will receive a full set of course notes and textbook, “System Requirements Analysis,” by the instructor Jeff Grady. View Course Sampler

What You Will Learn:

• How to model a problem space using proven methods where the product will be implemented in hardware or software.
• How to link requirements with traceability and reduce risk through proven techniques.
• How to identify all requirements using modeling that encourages completeness and avoidance of unnecessary requirements.
• How to structure specifications and manage their development.

This course will show you how to build good specifications based on effective models. It is not difficult to write requirements, The hard job is to know what to write them about and determine appropriate values. Modeling tells us what to write them about and good domain engineering encourages identification of good values in them.

Course Outline:

1. Introduction
2. Introduction (Continued)
3. Requirements Fundamentals – Defines what a requirement is and identifies 4 kinds.
4. Requirements Relationships – How are requirements related to each other? We will look at several kinds of traceability.
5. Initial System Analysis – The whole process begins with a clear understanding of the user’s needs.
6. Functional Analysis – Several kinds of functional analysis are covered including simple functional flow diagrams, EFFBD, IDEF-0, and Behavioral Diagramming.
7. Functional Analysis – (Continued)
8. Performance Requirements Analysis – Performance requirements are derived from functions and tell what the item or system must do and how well.
9. Product Entity Synthesis – The course encourages Sullivan’s idea of form follows function so the product structure is derived from its functionality.
10. Interface Analysis and Synthesis – Interface definition is the weak link in traditional structured analysis but n-square analysis helps recognize all of the ways function allocation has predefined all of the interface needs.
11. Specialty Engineering Requirements – A specialty engineering scoping matrix allows system engineers to define product entity-specialty domain relationships that the indicated domains then apply their models to.
12. Environmental Requirements – A three-layer model involving tailored standards mapped to system spaces, a three-dimensional service use profile for end items, and end item zoning for component requirements.
13. Software Modeling Using Early Methods – We all began with the same model using flow charts.
14. Software Modeling Using MSA/PSARE – Modern structured analysis is extended to PSARE as Hatley and Pirbhai did to improve real-time control system development but PSARE did something else not clearly understood.
15. Software Modeling Using UML/SysML – The latest models are covered.
16. Software Modeling Using DoDAF – DoD has evolved a very complex model to define systems of tremendous complexity involving global reach.
17. Structured Analysis Workshop/Demo – When presented at a single client student teams experiment with modeling. In a public course methods are demonstrated.
18. Structured Analysis Workshop/Demo - (Continued)
19. Specification Management – Specification formats and management methods are discussed.
20. Requirements Risk Abatement – Special requirements-related risk methods are covered including validation, TPM, margins and budgets.
21. Requirements Verification Overview - You should be basing verification of three kinds on the requirements that were intended to drive design. These links are emphasized.
22. Tools –
23. Structured Analysis Documentation – How can we capture and configuration manage our modeling basis for requirements?
24. Workshop Submission/Briefing