This ATI professional development course, Systems Engineering - Requirements, 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.

1. Slides From ATI Professional Development Short Course
Systems Requirements
Instructor:
Jeff Grady
ATI Course Schedule: http://www.ATIcourses.com/schedule.htm
ATI's Systems Requirements: http://www.aticourses.com/systems_engineering-requirements.html

2. www.ATIcourses.com
Boost Your Skills 349 Berkshire Drive
Riva, Maryland 21140
with On-Site Courses Telephone 1-888-501-2100 / (410) 965-8805
Tailored to Your Needs
Fax (410) 956-5785
Email: ATI@ATIcourses.com
The Applied Technology Institute specializes in training programs for technical professionals. Our courses keep you
current in the state-of-the-art technology that is essential to keep your company on the cutting edge in today’s highly
competitive marketplace. Since 1984, ATI has earned the trust of training departments nationwide, and has presented
on-site training at the major Navy, Air Force and NASA centers, and for a large number of contractors. Our training
increases effectiveness and productivity. Learn from the proven best.
For a Free On-Site Quote Visit Us At: http://www.ATIcourses.com/free_onsite_quote.asp
For Our Current Public Course Schedule Go To: http://www.ATIcourses.com/schedule.htm

3. Systems Jeff Grady Worked On
as an Employee
USAF/GDC AQM 129
Advanced Cruise Missile
USN/Librascope USAF/GD Atlas Missile
ASROC/SUBROC
ASW Computer Systems
USAF/Ryan Aeronautical AQM-81 Firebolt
VERSION 12.0 3212A1-3 c JOG System Engineering
Ryan War Birds
USAF/Ryan Models 147G, NX, H, and J at Bein Hoa, SVN
USAF/Ryan Aeronautical AQM-34L
58 Combat Missions U.S. Navy/Ryan USAF/Ryan
Model 147SK BGM-34C
VERSION 12.0 3212A1-4 c JOG System Engineering
3213A1-

4. Course Goals
• The course goal is a student who can apply modeling methods on
the job from which to derive all requirements that would appear
in program peculiar specifications for systems, hardware entities,
or software entities. A student who can understand the modeling
work accomplished by system and software engneers to
understand the problem space such that they can use the content
of those models to probe deeper into hardware-software issues on
programs. A student who can support program management in
the control of program risk relative to product performance issues
by applying TPM, traceability, as well as margins and budgets.
VERSION 12.0 3212A1-5 c JOG System Engineering
Course Sequence
• What are requirements and what kinds might we
have to identify?
• Next we will look at a very simple way to write
requirements
– Controlled characteristic, value and units, relation
• Then, we will discuss ways these requirements
are inter-related
• In subsequent periods, we will construct a
toolbox full of effective tools to help us identify
appropriate requirements for systems, hardware,
and software entities
• Management aspects close out the course
VERSION 12.0 3212A1-6 c JOG System Engineering
3213A1-

5. Course Outline
1 Introduction 18 System Modeling Using DoDAF
2 Introduction 19 System Modeling Using DoDAF
3 Requirements Fundamentals 20 Universal Architecture Description
4 Requirements Relationships Framework (UADF)
5 Initial System Analysis 21 Specification Management
6 Functional Analysis 22 Requirements Risk Abatement
7 Functional Analysis 23 Tools
8 Performance Requirements 24 Requirements Verification Overview
9 Product Entity Synthesis 25 Expansion Time
10 Interface Ident & Requirements Anal 26 Expansion Time
11 Interface Ident & Requirements Anal 27 Workshop Submission and Briefing
12 Specialty Engineering
13 Environmental Requirements Anal
14 System Architecture Report
15 System Modeling Using MSA & NOTE: A university course generally
PSARE includes 27 contact hours and a
16 System Modeling Using Early OOA, commercial industry course 24.
UML, and SysML Workshop time will be inserted as time
17 System Modeling Using Early OOA, permits in a university course.
UML, and SysML
VERSION 12.0 3212A1-7 c JOG System Engineering
The Principal Course References
“System Requirements Analysis”
Jeffrey O. Grady, Elsevier Academic Press, Jan. 2006
"Universal Architecture Description Framework"
INCOSE Journal, Volume 12, Number 2, Summer 2009
Chosen Best Paper 2009
Reformatted to appear as Part 9 of the Elsevier book
in your student manual
VERSION 12.0 3212A1-8 c JOG System Engineering
3213A1-

6. Course-Textbook Coordination
• Refer to Table C-1 on page C-7 of Division 2,
Exhibit C for a map between the periods of the
course and the Elsevier Academic Press
textbook. That table also coordinates course
periods with the INCOSE System Engineering
Manual Version 3.
• Ideally, you should try to read the textbook
sections for a period before you experience that
period either attending the course in a classroom
or using the course materials on a web site.
VERSION 12.0 3212A1-9 c JOG System Engineering
Student Materials Map
Text
Division 1
Course
Work
Division 2
Supporting
Documents
Division 3
VERSION 12.0 3212A1-10 c JOG System Engineering
3213A1-

7. Systems requirements analysis
is an important part of a
problem solving technique
for
complex problems.
VERSION 12.0 3212A1-11 c JOG System Engineering
Why is the problem of developing
systems that solve complex
problems so complex?
Is there a better way?
VERSION 12.0 3212A1-12 c JOG System Engineering
3213A1-

8. Specialization of Knowledge
Knowledge Grows & We Have Our Limitations
EXPANDING
KNOWLEDGE
SPECIALIZATION
EFFECTS
MAN'S
KNOWLEDGE
IT WON'T
ALL FIT! MAN'S
LIMITATIONS
VERSION 12.0 3212A1-13 c JOG System Engineering
We Are All Specialists
DEPTH OF KNOWLEDGE
BREADTH OF KNOWLEDGE
ALL KNOWLEDGE
GENERALIST KNOWLEDGE BASE
DOMAIN KNOWLEDGE BASE
SPECIALIST KNOWLEDGE BASE
VERSION 12.0 3212A1-14 c JOG System Engineering
3213A1-

9. Humans Are Knowledge Limited
and Knowledge Expands
EXPANDING IN ALL
DIRECTIONS AT
INCREASING PACE
TYPICAL
INDIVIDUAL
EMPLOYEE'S
KNOWLEDGE
BASE ALL KNOWLEDGE
KNOWLEDGE
BASE
NEEDED FOR
PROGRAM X
COMPANY A
KNOWLEDGE BASE
COMPANY B
KNOWLEDGE BASE
VERSION 12.0 3212A1-15 c JOG System Engineering
Large Problem Decomposition
SMALL LARGE PROBLEM
PROBLEM SMALL
6 PROBLEM
WE SHOULD AVOID 5 SMALL
DECOMPOSING THE PROBLEM
SMALL
LARGE PROBELM INTO 1 SMALL PROBLEMS
PROBLEM
SMALL PROBLEMS BASED 7
ON HOW WE HAVE PARTITIONED
EACH APPEAL TO
KNOWLEDGE AND FOCUS ON SMALL LIMITED TECH-
DECOMPOSING IT THE WAY PROBLEM
THE PRODUCT SYSTEM
NOLOGY SCOPE
4
MUST FUNCTION.
SMALL
SMALL
PROBLEM
PROBLEM
SMALL 2
3
PROBLEM
8 PROBLEM SPACES
COMPATIBLE WITH
SPAN OF CONTROL
LIMITS
VERSION 12.0 3212A1-16 c JOG System Engineering
3213A1-

10. Specialization of Knowledge
Competitive Advantage Goes To Those
With Knowledge They Can Effectively Use
DEVELOPMENT
PROCESS
$
KNOWLEDGE
Competition (along with knowledge for the sake of knowledge)
is the engine for continued expansion of knowledge
VERSION 12.0 3212A1-17 c JOG System Engineering
The System Development Sequence
That Minimizes Risk
• Define the problem
– Specifications
• Solve the problem
– Design, material, and manufacturing
• Prove it
– Verification
• Within a sound management infrastructure
VERSION 12.0 3212A1-18 c JOG System Engineering
3213A1-

11. Requirement Defined
Something wanted or ITEM
necessary.
Something essential
to the existence or
occurrence of
something else. Of what items must a
system consist and how can
A necessary character- I communicate needed
istic or attribute of some characteristics for those
items to designers?
thing (or item).
REQUIREMENTS
ARE THE ANSWER!
VERSION 12.0 3212A1-19 c JOG System Engineering
Requirements Types
TEST PROCESS
REQUIREMENTS OPERATIONAL PROCESS
PRODUCT AND LOGISTICS SUPPORT
REQUIREMENTS REQUIREMENTS
PRODUCTION
PROCESS
REQUIREMENTS SUPPORT
EQUIPMENT
TOOLS
PERFORMANCE REQUIREMENTS TRAINING
CONSTRAINTS PROCEDURES
INTERFACE FACILITIES
ENVIRONMENTAL SPARES
SPECIALTY ENGINEERING
All of these requirements must be identified
before product detailed design work is started
and they must be mutually consistent.
VERSION 12.0 3212A1-20 c JOG System Engineering
3213A1-

12. Requirements Types
• Hardware
– Performance
– Constraints
• Interface
• Specialty Engineering
• Environmental
• Software
– Functional
– Non-Functional
VERSION 12.0 3212A1-21 c JOG System Engineering
What is a Specification?
A specification
contains all of
the requirements
for a given item.
VERSION 12.0 3212A1-22 c JOG System Engineering
3213A1-

13. In Writing a Specification, What Is the
Target?
VERSION 12.0 3212A1-23 c JOG System Engineering
How to Hit the Target of
Minimized Completeness
• Every function mapped to one or more performance
requirements in the specification
• Every external interface for the item includes interface
requirements in the specification (unless ICD applied)
• Every specialty engineering discipline mapped to the item is
included in the specification
• Every environmental influence defined in the appropriate
model (system, end item, component) mapped to appropriate
specification content.
• Every requirement in the specification traceable to a parent
item specification requirement (ideally applies to the system
specification relative to user requirements as well).
• Requirements are quantified as appropriate to the statement.
• Requirements are validated (risks understood and mitigated).
VERSION 12.0 3212A1-24 c JOG System Engineering
3213A1-

14. Requirements Derivation Strategies
ALLOCATIO
STRUCTURED ARCHITECTURE
FREESTYLE IS FOR
DECOMPOSITION SYNTHESIS
EXPERTS AND
OTHER FOOLS
ITEM
N
STRUCTURED REQUIREMENTS IDENT
ANALYSIS
ANALYSIS FREESTYLE
OR AD HOC
POWER
GENERATING FLOWDOWN
SYSTEM • ALLOCATION
• IDENTITY
• ANALYSIS
POWER
PLANT COMPONENT
STANDARD
COOLING
STANDARD
SYSTEM
VALVE X VALVE Y
THE CUSTOMER
INTERVIEW
LIKE
PARENT
ITEM
ITEM APPROACH
VERSION 12.0 3212A1-25 c JOG System Engineering
Hardware and Systems Analysis
Models
Traditional structured analysis
Functional flow diagramming
Enhanced functional flow diagramming
Behavioral diagramming (RDD)/IPO
IDEF 0/SADT
Process flow analysis
Hierarchical functional analysis
FRAT
State diagramming
QFD
SysML
VERSION 12.0 3212A1-26 c JOG System Engineering
3213A1-

15. Traditional Structured Analysis
FUNCTIONAL FLOW DIAGRAM
ALLOCATE FUNCTIONALITY
TO THINGS IN SYSTEM MANUFACTURING BREAKDOWN
STRUCTURE
RAS
DRAWING BREAKDOWN STRUCTURE
PERFORMANCE
REQUIREMENTS WORK BREAKDOWN STRUCTURE
ANALYSIS
PERFORMED ON
ALLOCATED INTERFACE ANALYSIS
FUNCTIONALITY MAKE-BUY PLAN
PLACE ALLOCATED
ITEMS INTO SYSTEM DEVELOPMENT ORGANIZATION
ARCHITECTURE STRUCTURE
{
PERFORMANCE CONFIGURATION ITEM ANALYSIS
REQUIREMENTS SPECIFICATION TREE DEVELOPMENT
FOR ITEM FUNCTION TEAM/PRINCIPAL ENGINEER ASSIGNMENT
ALLOCATED TO
CONSTRAINTS ANALYSIS
VERSION 12.0 3212A1-27 c JOG System Engineering
Two Interface Definition Models
Schematic Block Diagramming
A2 Lines define interfaces
A1
A5
Blocks are objects only
A3
from the architecture
A4 A6
N-Square Diagramming
Marked intersections define interfaces
A1 X
X A2 X X Diagonal blocks are objects only from
X A3 X X X
X A4
architecture diagram
X X A5
X A6 Apparent ambiguity reflects directionality
VERSION 12.0 3212A1-28 c JOG System Engineering
3213A1-

16. Environmental Requirements
Modeling
• System level
– Identify spaces
– Select standards for the spaces
– Select parameters that relate to system pattern of use
– Tailor parameter range
• End item level
– Define physical processes
– Derive process environments
– Map architecture to process steps
– Unify item requirements
• Component level
– Identify end item zones
– Map components to zones
– Components inherit zone requirements
VERSION 12.0 3212A1-29 c JOG System Engineering,
Three Specialty Engineering
Requirements Approaches
• Specialty engineering models
– Reliability model
– Life cycle cost model
– Maintainability model
– Mass properties model
• Appeal to applicable documents
– MIL-STD-850 pilot visibility
– IL-M-39310 mass properties control requirements
• Flow diagrams
VERSION 12.0 3212A1-30 c JOG System Engineering
3213A1-

17. Computer Software Structured
Analysis Models
• Process-oriented analysis
• Flow charting
• MSA as practiced by Yourdon-Demarco
• Hatley-Pirbhai now called PSARE
• Data-oriented analysis
• Table normalizing
• IDEF-1X
• Object-oriented analysis
– Early models
– UML
• DoD architecture framework (DoDAF)
VERSION 12.0 5232A1-31 c JOG System Engineering
DoD Acquisition Life Cycle
VERSION 12.0 5232A1-32 c JOG System Engineering
3213A1-

18. NASA Life Cycle Acquisition Model
VERSION 12.0 5232A1-33 c JOG System Engineering
FAA Acquisition Life Cycle
VERSION 12.0 5232A1-34 c JOG System Engineering
3213A1-

19. An Enterprise Needs Its Own
Common Process
ENTERPRISE CUSTOMER
MISSION NEEED
F F
ACQUIRE NEW
BUSINESS
F3
25
NEW
PROGRAM
SUPPLIER
CONTROL
SUPPLIER
FUNCTIONS GRAND GRAND GRAND GRAND
SYSTEMS SYSTEMS SYSTEMS SYSTEMS
REQUIREMENTS SYNTHESIS VERIFICATION SUSTAINMENT
F42 F44 F48 DISPOSED
NEED 2 F41 2
2 2 SYSTEM
F6 SUPPLIER
MATERIAL MANAGE
PROGRAM USE
MANAGE SYSTEM
CUSTOMER F49 F47
ACTIVITIES X
ASSURE
ENTERPRISE
F5 PRODUCT
SCOPE
AND PROCESS GRAND SYSTEMS GRAND SYSTEMS
QUALITY DEVELOPMENT EMPLOYMENT
9 F46 OVERLAY OVERLAY
SYSTEM/PROGRAM LIFE CYCLE F4
2
GRAND SYSTEMS MANAGEMENT
LESSONS
MANAGE ENTERPRISE PROGRAM
LEARNED
F1 RESOURCES
47
PROVIDE PROGRAM
RESOURCES
F2
35
F
X: REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION
VERSION 12.0 5232A1-35 c JOG System Engineering
System Life Cycle
SYSTEM/PROGRAM
LIFE CYCLE
1
GRAND SYSTEMS
VALIDATE EMPLOYMENT OVERLAY
GRAND SYSTEMS GRAND
DEVELOPMENT SYSTEMS MODELS GRAND SYSTEMS
OVERLAY VERIFICATION SUSTAINMENT
F447
57
LOGISTICALLY
IOR CONDUCT SUPPORT
SYSTEM TEST SYSTEM TEST
AND
MANAGE EVALUATION F482
IOR VERIFICATION IOR F443
11 MANAGE
F444 SUSTAINMENT
QUALIFY F486
COMPONENTS ONE-OF-A-KIND
& END ITEMS VERIFICATION
F441
11 F446
LOW VOLUME
GRAND DESIGN ACCEPT DEPLOY/ DELIVER
HIGH DOLLAR
NEED SYSTEMS SYSTEM REFURB COMPONENTS XOR SYSTEM IOR
DEFINITION & END ITEMS
F421 F424
8 F481
F41 X
4 DESIGN MANUFACTURE
COMPONENTS F442 IOR
MANUFACTURING, 14 DISPOSE OF DISPOSED
QUALITY, AND & ASSMBLE SYSTEM SYSTEM
MATERIAL END ITEMS
PROCESSES F485
F423 X
F425
8
MODIFY
SUPPLIER
SYSTEM
CONTROL
MATERIAL MANAGE F44
SYNTHESIS F484
X
SUPPLIER F422 F426
8 LOGISTICALLY
MATERIAL F42 SUPPORT
GRAND SYSTEMS SYNTHESIS SYSTEM
MANAGEMENT 8
INFORMATION ASSURE F483
X F48
PRODUCT AND
MANAGE PROCESS
PROGRAM
QUALITY
F49 USE
F46
9 SYSTEM
F47
X
F4
X REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION
VERSION 12.0 5232A1-36 c JOG System Engineering
3213A1-

20. Grand Systems Definition
1
GRAND
SYSTEMS CLONE
DEFINITION SPECIFICATION
41 F417
CUSTOMER UNIVERSAL ARCHITECTURE REQUIREMENTS
NEEDS DESCRIPTION FRAMEWORK DESCRIPTIVE MODELING ANALYSIS
ANALYSIS
PROBLEM PERFORMANCE
SYSTEM NEED INTER- MODEL: SPACE REQUIREMENTS
STATEMENT TRANSFER FUNCTIONALLY
REVIEW AND FUNCTIONAL MODELING DERIVED ANALYSIS
ANALYSIS FUNCTIONAL MANAGE
PRIOR WORK EVALUATE AND IOR IOR ANALYSIS PERFORMANCE REQUIREMENTS
NEED AND INPUT REQUIREMENTS
PRIOR WORK ANALYSIS
IOR F412111 SRR
F4111 F41311 CONDUCT REPORT
61 20 SRR
CUSTOMER IOR MSA/PSARE
MSA/PSARE DERIVED
Q&A MODELING PERFORMANCE
ANSWERS MSA/PSARE INPUT
REQUIREMENTS PIT/IPPT
F4112 ANALYSIS DEFINITION
IOR F412112 FORM TEAMS
F41312
F411 40
UML/SYSML F416A
UML/SYSML DERIVED
MODELING UML/SYSML INPUT IOR
PERFORMANCE
REQUIREMENTS PERFORMANCE SPECIFICATIONS
IOR ANALYSIS REQUIREMENTS PUBLISH AND PLANS
F412113 SPECIFICATIONS
45 F41313 TO RAS
AND PLANS
IOR ITEM FILTERED
IDEF/DODAF/ DODAF F4166 SPECIFICATION
MODAF DERIVED 65
DODAF INPUT DATA AND
MODELING PERFORMANCE PLANS PARAGRAPH
REQUIREMENTS MANAGE
MARGINS AND NUMBER ORDERED
IOR ANALYSIS
F412114 BUDGETS
68 F41314
F41211 F4163
VERIFICATION
REQUIREMENTS
SOLUTION SPACE ANALYSIS
MODELING 26 F4133 F4131
MANAGE
RAS
INTERFACE IDENTIFIED INTERFACE
IOR MODELING INTERFACES REQUIREMENTS REPORTS
INTERFACE
AND MEDIA ANALYSIS REQUIREMENTS
F412121 TO RAS
24 F41321
F4161
SPECIALTY SPECIALTY SPECIALTY
ENGINEERING ENGINEERING SPECIALTY ENGINEERING
IOR MODELING MODELING REQUIREMENTS AUDIT, ASSURE
ENGINEERNIG
RESULTS REQUIREMENTS TO RAS TRACEABILITY,
F412122 ANALYSIS INTEGRATE
F41322 AND VALIDATE
44 REQUIREMENTS
ENVIRONMENTAL
MODELING ENVIRONMENT ENVIRONMENTAL ENVIRONMENTAL 5 F4162
IOR SYSTEM
IDENTIFICATION REQUREMENTS REQUIREMENTS
ANALYSIS TO RAS ARCHITECTURE
F4122 13 F412123 DOCUMENT REPORT
HIGHER TIER DESCRIPTIVE
CONCEPT F41323
MODELING
PRODUCT FEEDBACK
DESIGN CONSTRAINTS ANALYSIS ARTIFACTS
ENTITY F4132 F4165
STRUCTURE
PRODUCT
ENTITIES ALLOCATE REQUIREMENTS APPLICABLE
24 F412124 REQUIREMENTS DOCUMENT
F41212 TO ENTITIES AND CALLS TEAM
ASSIGNMENTS
F4121 F4134 F4164
F413
GENERIC NEW
PROCESS ENTITIES PROGRESSIVE PREPARE PRODUCT
DEFINITION PROCESS DETAIL DESIGN
REQUIREMENTS ALLOCATIONS SPECIFICATION
ANALYSIS PLANS DATA
6 TO RAS F416B
F4125 PRECEDENTED
DEVELOPMENT SIMULATION
INTEGRATE AND DOCUMENT FEED
OPTOMIZE EXECUTABLE APPROVED FOWARD
MODELS MODELING F415 SIMULATIONS
F4124 F4123 F4167
PRECEDENTED F412
SYSTEM PRODUCT
PRODUCT ENTITIES ENTITIES
DOCUMENT SDR
AND APPROVE C.O0NDUCT REPORT
CONCEPTS SDRITEM
CONCEPT CONCEPTS
DEVELOPMENT F4168
SPECIALTY
ENGINEERING APPLICABLE SPECIFICATION
PROGRAM F414 DOCUMENTS TEMPLATE PREPARE
MODELING SCOPING PROGRAM
ENTERPRISE PREFERENCES MATRIX FOR MODELING
RESOURCES AND REQUIRENTS
ANALYSIS WORK
F4169 F416
APPLICABLE
DOCUMENTS
F41
VERSION 12.0 5232A1-37 c JOG System Engineering
Publish Specifications
VERSION 12.0 5232A1-38 c JOG System Engineering
3213A1-

21. Program Sequence Models
Waterfall Development Model
REQUIREMENTS
DESIGN
INTEGRATION & TEST
PRODUCTION
VERSION 12.0 5232A1-39 c JOG System Engineering
Program Sequence Models
“V” Development Model
SYSTEM SYSTEM
REQUIREMENTS TEST
VERIFICATION
REQUIREMENTS
END ITEM END ITEM
REQUIREMENTS PLANS AND TEST
PROCEDURES
SECTION 3 SECTION 4 REPORTS
SUBSYSTEM SUBSYSTEM
REQUIREMENTS TEST
DEVELOPMENT
COMPONENT COMPONENT UPSTROKE
REQUIREMENTS TEST
DEVELOPMENT
DOWNSTROKE DESIGN &
INTEGRATION
VERSION 12.0 5232A1-40 c JOG System Engineering
3213A1-

22. Program Sequence Models
The Spiral Development Model
CUSTOMER
NEED
TIME
ITERATIVE
DEVELOPMENT
RAPID PROTOTYPING
COMMERCIAL EXITS
ANALYSIS
BUILD
TEST
VERSION 12.0 5232A1-41 c JOG System Engineering
3213A1-

23. You have enjoyed ATI's preview of
Systems Requirements
Please post your comments and questions to our blog:
http://www.aticourses.com/blog/
Sign-up for ATI's monthly Course Schedule Updates :
http://www.aticourses.com/email_signup_page.html