Acoustics & Sonar Engineering Radar, Missiles & Defense Systems ...

Systems Engineering - Requirements
NEW!
January 10-12, 2012
Columbia, Maryland
March 20-22, 2012
Columbia, Maryland
$1795 (8:30am - 4:30pm)
"Register 3 or More & Receive $100 00 each
Off The Course Tuition."
Call for information about our six-course systems engineering
certificate program or for “on-site” training to prepare for the
INCOSE systems engineering exam.
Summary
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.
Instructor
Jeffrey O. Grady is the president of a System
Engineering company. He has 30 years
of industry experience in aerospace
companies as a system engineer,
engineering manager, field engineer,
and project engineer. Jeff has authored
seven published books in the system
engineering field and holds a Master of
Science in System Management from
USC. He teaches system engineering courses nationwide.
Jeff is an INCOSE Founder, Fellow, and ESEP.
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. Interface Analysis and Synthesis – (Continued)
12. 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.
13. 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.
14. Structured Analysis Documentation – How can
we capture and configuration manage our modeling basis
for requirements?
15. 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.
16. Software Modeling Using Early OOA and UML –
The latest models are covered.
17. Software Modeling Using Early OOA and UML –
(Continued).
18. Software Modeling Using DoDAF – DoD has
evolved a very complex model to define systems of
tremendous complexity involving global reach.
19. Universal Architecture Description Framework
A method that any enterprise can apply to develop any
system using a single comprehensive model no matter
how the system is to be implemented.
20. Universal Architecture Description Framework
(Continued)
21. Specification Management – Specification
formats and management methods are discussed.
22. Requirements Risk Abatement - Special
requirements-related risk methods are covered including
validation, TPM, margins and budgets.
23. Tools Discussion
24. Requirements Verification Overview – You
should be basing verification of three kinds on the
requirements that were intended to drive design. These
links are emphasized.
30 – Vol. 109 Register online at www.ATIcourses.com or call ATI at 888.501.2100 or 410.956.8805