www.ATIcourses.com

Boost Your Skills with On-Site Courses Tailored to Your Needs 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

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-3

Systems Jeff Grady Worked Onas an Employee

USAF/GDC AQM 129 Advanced Cruise Missile

USAF/GD Atlas Missile

USAF/Ryan Aeronautical AQM-81 Firebolt

USN/Librascope ASROC/SUBROC

ASW Computer Systems

VERSION 12.0 c JOG System Engineering3212A1-4

Ryan War Birds

USAF/Ryan Models 147G, NX, H, and J at Bein Hoa, SVN

U.S. Navy/Ryan Model 147SK

USAF/RyanBGM-34C

USAF/Ryan Aeronautical AQM-34L 58 Combat Missions

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-5

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 c JOG System Engineering3212A1-6

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

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-7

Course Outline123456789

101112131415

16

17

181920

21222324252627

IntroductionIntroductionRequirements FundamentalsRequirements RelationshipsInitial System AnalysisFunctional Analysis Functional AnalysisPerformance RequirementsProduct Entity SynthesisInterface Ident & Requirements AnalInterface Ident & Requirements AnalSpecialty EngineeringEnvironmental Requirements AnalSystem Architecture ReportSystem Modeling Using MSA & PSARESystem Modeling Using Early OOA, UML, and SysMLSystem Modeling Using Early OOA, UML, and SysML

System Modeling Using DoDAFSystem Modeling Using DoDAFUniversal Architecture DescriptionFramework (UADF)Specification ManagementRequirements Risk AbatementToolsRequirements Verification OverviewExpansion TimeExpansion TimeWorkshop Submission and Briefing

NOTE: A university course generallyincludes 27 contact hours and a commercial industry course 24. Workshop time will be inserted as time permits in a university course.

VERSION 12.0 c JOG System Engineering3212A1-8

“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 2009Reformatted to appear as Part 9 of the Elsevier book

in your student manual

The Principal Course References

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-9

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 c JOG System Engineering3212A1-10

Student Materials Map

TextDivision 1

CourseWorkDivision 2

SupportingDocumentsDivision 3

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-11

Systems requirements analysisis an important part of a

problem solving techniquefor

complex problems.

VERSION 12.0 c JOG System Engineering3212A1-12

Why is the problem of developingsystems that solve complex

problems so complex?

Is there a better way?

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-13

Specialization of KnowledgeKnowledge Grows & We Have Our Limitations

MAN'SKNOWLEDGE

EXPANDINGKNOWLEDGE

MAN'SLIMITATIONS

SPECIALIZATIONEFFECTS

IT WON'TALL FIT!

VERSION 12.0 c JOG System Engineering3212A1-14

ALL KNOWLEDGE

GENERALIST KNOWLEDGE BASEDOMAIN KNOWLEDGE BASESPECIALIST KNOWLEDGE BASE

BREADTH OF KNOWLEDGE

DE

PT

H O

F K

NO

WLE

DG

E

We Are All Specialists

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-15

Humans Are Knowledge Limitedand Knowledge Expands

ALL KNOWLEDGE

EXPANDING IN ALL DIRECTIONS AT INCREASING PACE

COMPANY A KNOWLEDGE BASE

COMPANY B KNOWLEDGE BASE

TYPICALINDIVIDUALEMPLOYEE'SKNOWLEDGEBASE

KNOWLEDGE BASENEEDED FORPROGRAM X

VERSION 12.0 c JOG System Engineering3212A1-16

Large Problem Decomposition

LARGE PROBLEM

SMALLPROBLEM

1

SMALLPROBLEM

2

SMALLPROBLEM

6SMALL

PROBLEM5

SMALLPROBLEM

3

SMALLPROBLEM

4

SMALLPROBLEM

7

SMALLPROBLEM

8

SMALL PROBLEMS EACH APPEAL TO LIMITED TECH-NOLOGY SCOPE

WE SHOULD AVOIDDECOMPOSING THELARGE PROBELM INTOSMALL PROBLEMS BASEDON HOW WE HAVE PARTITIONEDKNOWLEDGE AND FOCUS ONDECOMPOSING IT THE WAY THE PRODUCT SYSTEMMUST FUNCTION.

PROBLEM SPACESCOMPATIBLE WITHSPAN OF CONTROLLIMITS

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-17

Specialization of KnowledgeCompetitive Advantage Goes To Those

With Knowledge They Can Effectively Use

KNOWLEDGE

$DEVELOPMENTPROCESS

Competition (along with knowledge for the sake of knowledge)is the engine for continued expansion of knowledge

VERSION 12.0 c JOG System Engineering3212A1-18

The System Development SequenceThat Minimizes Risk

• Define the problem– Specifications

• Solve the problem– Design, material, and manufacturing

• Prove it– Verification

• Within a sound management infrastructure

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-19

Requirement Defined

Something wanted ornecessary.

Something essential to the existence oroccurrence of something else.

A necessary character-istic or attribute of something (or item).

ITEM

REQUIREMENTSARE THE ANSWER!

Of what items must asystem consist and how canI communicate neededcharacteristics for those items to designers?

VERSION 12.0 c JOG System Engineering3212A1-20

Requirements Types

PRODUCTIONPROCESSREQUIREMENTS

PRODUCTREQUIREMENTS

OPERATIONAL PROCESS AND LOGISTICS SUPPORT REQUIREMENTS

TEST PROCESSREQUIREMENTS

SUPPORT EQUIPMENTTOOLSTRAININGPROCEDURESFACILITIESSPARES

PERFORMANCE REQUIREMENTSCONSTRAINTS

INTERFACEENVIRONMENTALSPECIALTY ENGINEERING

All of these requirements must be identifiedbefore product detailed design work is started and they must be mutually consistent.

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-21

Requirements Types

• Hardware– Performance

– Constraints• Interface

• Specialty Engineering

• Environmental

• Software– Functional

– Non-Functional

VERSION 12.0 c JOG System Engineering3212A1-22

What is a Specification?

A specification contains all of the requirements for a given item.

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-23

In Writing a Specification, What Is the Target?

VERSION 12.0 c JOG System Engineering3212A1-24

How to Hit the Target ofMinimized 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).

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-25

STRUCTUREDDECOMPOSITION

ARCHITECTURESYNTHESIS

ITEMIDENTREQUIREMENTS

ANALYSISSTRUCTUREDANALYSIS

FREESTYLE IS FOREXPERTS ANDOTHER FOOLS

FREESTYLEOR AD HOC

Requirements Derivation Strategies

COOLINGSYSTEM

VALVE X VALVE Y

POWERGENERATINGSYSTEM

POWERPLANT COMPONENT

STANDARD

STANDARD

LIKEITEMPARENT

ITEM

FLOWDOWN

THE CUSTOMERINTERVIEWAPPROACH

• ALLOCATION• IDENTITY• ANALYSIS

AL

LO

CA

TIO

N

VERSION 12.0 c JOG System Engineering3212A1-26

Hardware and Systems Analysis Models

Traditional structured analysis

Functional flow diagrammingEnhanced functional flow diagrammingBehavioral diagramming (RDD)/IPOIDEF 0/SADT Process flow analysisHierarchical functional analysisFRAT

State diagrammingQFDSysML

3213A1-

VERSION 12.0 c JOG System Engineering3212A1-27

Traditional Structured AnalysisFUNCTIONAL FLOW DIAGRAM

ALLOCATE FUNCTIONALITYTO THINGS IN SYSTEM

PLACE ALLOCATEDITEMS INTO SYSTEMARCHITECTURE

WORK BREAKDOWN STRUCTURE

INTERFACE ANALYSIS

DEVELOPMENT ORGANIZATIONSTRUCTURE

CONFIGURATION ITEM ANALYSISSPECIFICATION TREE DEVELOPMENTTEAM/PRINCIPAL ENGINEER ASSIGNMENT{

PERFORMANCEREQUIREMENTSANALYSISPERFORMED ONALLOCATEDFUNCTIONALITY

PERFORMANCEREQUIREMENTSFOR ITEM FUNCTIONALLOCATED TO

MANUFACTURING BREAKDOWNSTRUCTURE

DRAWING BREAKDOWN STRUCTURE

MAKE-BUY PLAN

RAS

CONSTRAINTS ANALYSIS

VERSION 12.0 c JOG System Engineering3212A1-28

Two Interface Definition Models

Schematic Block Diagramming

N-Square Diagramming

Lines define interfaces

Blocks are objects only from the architecture

Marked intersections define interfaces

Diagonal blocks are objects only from architecture diagram

Apparent ambiguity reflects directionality

X X

X

X

X

X

A1

A2

A4

A3

A5

A1A2

A3A4

A5

A6

A6

X

X

XX

X

X

3213A1-

VERSION 12.0 c JOG System Engineering,3212A1-29

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 c JOG System Engineering3212A1-30

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

3213A1-

VERSION 12.0 c JOG System Engineering5232A1-31

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 c JOG System Engineering5232A1-32

DoD Acquisition Life Cycle

3213A1-

VERSION 12.0 c JOG System Engineering5232A1-33

NASA Life Cycle Acquisition Model

VERSION 12.0 c JOG System Engineering5232A1-34

FAA Acquisition Life Cycle

3213A1-

VERSION 12.0 c JOG System Engineering5232A1-35

An Enterprise Needs Its Own Common Process

F41 F42 F44

GRAND SYSTEMS

SUSTAINMENT

USE SYSTEM

F47

F48 DISPOSED SYSTEM

SUPPLIER MATERIAL

SUPPLIER CONTROL

F49

F46

MANAGE ENTERPRISE

PROVIDE PROGRAM RESOURCES

ACQUIRE NEW BUSINESS

25

35F

F4

F1

F3

F2

LESSONS LEARNED

NEW PROGRAM

PROGRAM RESOURCES

SYSTEM/PROGRAM LIFE CYCLE

22

X

X: REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION

2 2

9

MANAGE CUSTOMER ACTIVITIES

F5

2

ENTERPRISE MISSION

CUSTOMER NEEED

FF

47

NEED

SUPPLIER FUNCTIONS

F6

GRAND SYSTEMS

REQUIREMENTS

GRAND SYSTEMS

SYNTHESIS

GRAND SYSTEMS

VERIFICATION

MANAGE PROGRAM

GRAND SYSTEMS MANAGEMENT

ASSURE PRODUCT

AND PROCESS QUALITY

ENTERPRISE SCOPE

GRAND SYSTEMS DEVELOPMENT

OVERLAY

GRAND SYSTEMS EMPLOYMENT

OVERLAY

VERSION 12.0

X REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION

DESIGNSYSTEM

GRAND SYSTEMS SYNTHESISF42

MANUFACTURE COMPONENTS

& ASSMBLEEND ITEMS

MATERIAL

SUPPLIERCONTROL

NEED

SUPPLIERMATERIAL

F421

F422

F423

QUALIFY COMPONENTS

& END ITEMSF441

ACCEPT COMPONENTS

& END ITEMS

F442

IOR

XOR

CONDUCT SYSTEM TEST

ANDEVALUATION

F443

F44

GRAND SYSTEMS

VERIFICATION

DEPLOY/ DELIVERSYSTEM

F481

GRAND SYSTEMSSUSTAINMENT

USESYSTEM

DISPOSE OFSYSTEM

LOGISTICALLY SUPPORT

SYSTEM TEST

MODIFYSYSTEM

F48

F482

F485

F483

F484

F47

F46

ASSURE PRODUCT AND

PROCESSQUALITY

MANAGEPROGRAM

F49

SYSTEM/PROGRAMLIFE CYCLE

IOR

IOR

MANAGEVERIFICATION IOR

F444

DISPOSEDSYSTEM

LOW VOLUME HIGH DOLLAR

REFURBF424

X

8

ONE-OF-A-KINDVERIFICATION

IOR

F446

14

8

11

9

LOGISTICALLY SUPPORT

SYSTEM

1

X

X

X

X

MANAGEMENTINFORMATION

8

11

VALIDATEMODELS

57F447

8

MANAGESUSTAINMENT

F486

DESIGNMANUFACTURING,

QUALITY, AND MATERIAL

PROCESSES

F425

MANAGESYNTHESIS

GRAND SYSTEMS DEVELOPMENT

OVERLAY

F426

GRAND SYSTEMS

DEFINITION

F4

4F41

GRAND SYSTEMSEMPLOYMENT OVERLAY

c JOG System Engineering5232A1-36

System Life Cycle

3213A1-

VERSION 12.0 c JOG System Engineering5232A1-37

Grand Systems Definition

PRIOR WORK

CUSTOMERQ&A

F4112

F411

CUSTOMER NEEDS

ANALYSIS

FUNCTIONALLY DERIVED

PERFORMANCE REQUIREMENTS

ANALYSIS

F41311

F4131

F41312

MSA/PSARE DERIVED

PERFORMANCE REQUIREMENTS

ANALYSIS

UML/SYSML

DERIVED PERFORMANCE REQUIREMENTS

ANALYSISF41313

MSA/PSARE INPUT

UML/SYSML INPUT

DODAF

DERIVED PERFORMANCE REQUIREMENTS

ANALYSISF41314

DODAF INPUT

IOR

PERFORMANCE REQUIREMENTS

ANALYSIS

INTERFACE REQUIREMENTS

ANALYSIS

IDENTIFIED INTERFACES

AND MEDIA INTERFACE

REQUIREMENTSTO RAS

SPECIALTY ENGINEERNIG

REQUIREMENTSANALYSIS

SPECIALTY ENGINEERING

MODELING RESULTS

SPECIALTY ENGINEERING

REQUIREMENTS TO RAS

ENVIRONMENTAL REQUREMENTS

ANALYSIS

ENVIRONMENTIDENTIFICATION

ENVIRONMENTAL REQUIREMENTS

TO RAS

F41321

F41322

F41323

REQUIREMENTSANALYSIS

FUNCTIONAL ANALYSIS

INPUT

FUNCTIONALANALYSIS

ENVIRONMENTALMODELING

SPECIALTY ENGINEERING

MODELING

INTERFACEMODELING

IOR

IOR

IOR

IOR

IOR

PRODUCT ENTITY

STRUCTURE

PERFORMANCE REQUIREMENTS

TO RAS

MANAGERAS

PUBLISH SPECIFICATIONS

AND PLANS

AUDIT, ASSURE TRACEABILITY,

INTEGRATE AND VALIDATE

REQUIREMENTS

SYSTEM NEEDSTATEMENT

HIGHER TIER CONCEPT

FEEDBACK

MSA/PSAREMODELING

UML/SYSMLMODELING

IDEF/DODAF/ MODAF

MODELING

IORIOR

SPECIFICATIONSAND PLANS

ITEMCONCEPTS

VERIFICATION REQUIREMENTS

ANALYSIS

ALLOCATE REQUIREMENTS

TO ENTITIES

IOR

IOR

IOR

UNIVERSAL ARCHITECTUREDESCRIPTION FRAMEWORK

MANAGE MARGINS AND

BUDGETS

MANAGEREQUIREMENTS

GRAND SYSTEMS

DEFINITION

F41

F412

F412124

F412123

F412122

F412121

F412114

F412113

F412112

F412111

F4133

PROBLEM SPACE

MODELING

F41212

SOLUTION SPACEMODELING

F41211

SIMULATION FEED

FOWARD EXECUTABLEMODELING

F414

1

F4132

F4123

F416

F4162

F4161

F4163

F4166

DESIGN CONSTRAINTS ANALYSIS

PRODUCTENTITIES

INTER- MODEL:TRANSFER

ITEM FILTERED SPECIFICATION

DATA AND PARAGRAPH

NUMBER ORDERED

DOCUMENT DESCRIPTIVE

MODELINGARTIFACTS

F4165

SYSTEM ARCHITECTURE

REPORT

REPORTS

DOCUMENTAND APPROVE

CONCEPTS

DOCUMENT APPROVED

SIMULATIONS

F4167

F4168

PREPARE PROGRAM

FOR MODELING AND REQUIRENTS

ANALYSIS WORK

SPECIFICATIONTEMPLATE

SPECIALTY ENGINEERING

SCOPINGMATRIX

PROGRAM MODELING

PREFERENCES

24

24

68

45

40

20

REVIEW ANDEVALUATE

NEED ANDPRIOR WORK

F4111

F4122

ENTERPRISERESOURCES

F413F4134

F4169

APPLICABLEDOCUMENTS

APPLICABLEDOCUMENTS

PRODUCTENTITIES

DESCRIPTIVE MODELING

F4121

CONCEPTDEVELOPMENT

APPLICABLE DOCUMENT

CALLS

F4164

TEAMASSIGNMENTS

NEWENTITIES

INTEGRATE AND OPTOMIZE

MODELS

F4124

IOR

65

5

PROGRESSIVE PROCESS

REQUIREMENTS ANALYSIS

F41256

GENERIC PROCESS

DEFINITION

FORM TEAMS

PIT/IPPT

DEFINITION

F416A

REQUIREMENTS

ALLOCATIONS

PLANS

PLANS DATATO RAS

26

F417

CLONESPECIFICATION

41

44

13

AND

PRECEDENTEDDEVELOPMENT

F415

PRECEDENTED SYSTEM

PRODUCT ENTITIES

PREPARE DETAIL

SPECIFICATION

F416B

PRODUCTDESIGN

AND

61

ANSWERS

C.O0NDUCTSDR

CONDUCTSRR

SRRREPORT

SDRREPORT

VERSION 12.0 c JOG System Engineering5232A1-38

Publish Specifications

3213A1-

VERSION 12.0 c JOG System Engineering5232A1-39

REQUIREMENTS

DESIGN

Program Sequence ModelsWaterfall Development Model

INTEGRATION & TEST

PRODUCTION

VERSION 12.0 c JOG System Engineering5232A1-40

Program Sequence Models“V” Development Model

SYSTEMREQUIREMENTS

SYSTEMTEST

END ITEMREQUIREMENTS

END ITEMTEST

COMPONENTREQUIREMENTS

COMPONENTTEST

SUBSYSTEMTEST

SUBSYSTEMREQUIREMENTS

DESIGN &INTEGRATION

VERIFICATIONREQUIREMENTS

DEVELOPMENTDOWNSTROKE

DEVELOPMENTUPSTROKE

SECTION 3 REPORTS

PLANS ANDPROCEDURES

SECTION 4

3213A1-

VERSION 12.0 c JOG System Engineering5232A1-41

BUILD

Program Sequence Models The Spiral Development Model

CUSTOMERNEED

ITERATIVEDEVELOPMENT

TIME

RAPID PROTOTYPINGCOMMERCIAL EXITS

TEST

ANALYSIS