1I-A-1

PROBLEM SPACE MODELINGA Dynamic Future For

Requirements Analysis

Jeffrey O. GradyPresident JOG System Engineering, Inc.

6015 Charae StreetSan Diego, CA 92122

(858) 458-0121jgrady@ucsd.edu

1I-A-2

Agenda

• A current reality• Program preparation• Traditional structured analysis• UML• The future

1I-A-3

How Should the Engineer ApproachUnprecedented Problem Space?

PROBLEMSPACE

ANALYST

FUNCTIONALFACET

OBJECTFACET

BEHAVIORALFACET

VISION

1I-A-4

System EntitiesFAMILY OFSYSTEMS

A

A1 A2 A3 A4

AIRCRAFTSYSTEM

SATELLITESYSTEM

LANDSYSTEM

WEAPONSSYSTEMS

SOFTWAREENTITIES

1I-A-5

A Single Model Will Not Work

Hardware Content

Software Content

SystemElements

1I-A-6

Prepare the Enterprise

MAPMETHODS

ANDDOMAINS

TOTEMPLATE,BUILD DID

PREPARESDD

PUBLISHSPECIFI-CATIONS

REQUIRE-MENTS

ANALYSIS

TEMPLATE

METHODS

SYSTEM DEFINITIONDOCUMENT

DOMAINS

SDD TEMPLATE

SPECIFI-CATIONS

SYSTEM & HW

SOFTWARE

RAS &DATABASE

TOOLS

1I-A-7

Prepare the Enterprise• Select standards and corresponding templates• Select preferred structured analysis models• Tailor templates for alignment with models you choose to

use to explore problem space• Build data item description (DID) for each specification

type/model application– System specification/TSA– Hardware performance specification/TSA– Software performance specification/UML– Software performance specification/DoDAF– Hardware ICD/TSA and software IRS/UML and DoDAF

• Map organization and models to template• Apply SDD as a means to capture models products

1I-A-8

Generic Template3.1 States and modes3.2 Entity capabilities3.2.m Entity capability m3.2.m.n Entity capability m, requirements n3.3 Interface requirements3.3.1 External interfaces3.3.1.m External interface m3.3.1.m.n External interface m, requirement n3.3.2 Internal interfaces3.3.2.m Internal interface m3.3.2.m.n Internal interface m, requirement n3.4 Specialty engineering requirements3.4.m Specialty discipline m3.4.m.n Specialty discipline m, requirement n3.5 Environmental requirements3.6 Precedence and criticality considerations

1I-A-9

Do the Analysis Work Using PreferredModels

MAPMETHODS

ANDDOMAINS

TOTEMPLATE,BUILD DID

PREPARESDD

PUBLISHSPECIFI-CATIONSREQUIRE-

MENTSANALYSIS

TEMPLATE

METHODS

SYSTEM DEFINITIONDOCUMENT

DOMAINS

SDD TEMPLATE

SPECIFI-CATIONS

SYSTEM & HW

SOFTWARE

RAS &DATABASE

TOOLS

1I-A-10

Ultimate Process Diagram

F41 F42 F44

GRANDSYSTEMS

SUSTAINMENT

USESYSTEM

F47

F48 DISPOSEDSYSTEM

SUPPLIERMATERIA

L

SUPPLIERCONTROL

25

F

F4LESSONSLEARNED

NEWPROGRAM

PROGRAMRESOURCES

22

X

X: REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION

2 2

MANAGECUSTOMERACTIVITIES

F5

2

ENTERPRISEVISION

CUSTOMERNEEED

FF

NEED

SUPPLIERFUNCTIONS

F6

GRANDSYSTEMS

REQUIREMENTS

GRANDSYSTEMS

SYNTHESIS

GRANDSYSTEMS

VERIFICATION

ENTERPRISESCOPE

GRAND SYSTEMSDEVELOPMENT

OVERLAY

GRAND SYSTEMSEMPLOYMENT

OVERLAY

SYSTEM/PROGRAM LIFE CYCLE OVERLAY

ACQUIRE NEWBUSINESS

F3

PROVIDE PROGRAMRESOURCES

35F2

47

GRAND SYSTEMS MANAGEMENT OVERLAY

F49

MANAGE ENTERPRISE

F1

MANAGEPROGRAM

9 F46

ASSUREPRODUCT AND

PROCESSQUALITY

GRAND SYSTEMSUNIVERSE

1I-A-11

The Process

AVAILABLE�FUNCTIONAL�

DEPARTMENTS

AVAILABLEAPPROVED�

MODELS

AVAILABLE�SPECIFICATION�

TEMPLATES

MAP MODELS &�DEPARTMENTS�TO TEMPLATES

ACCOMPLISH�PLANNED�

MODELING WORK

SYSTEM �DEFINITION�DOCUMENT�TEMPLATE

AND

ANDSPCIFICATION�

DATA ITEM�DESCRIPTION

SYSTEM �DEFINITION�DOCUMENT�

DID

AND

ENTER�REQUIREMENTS�

INTO RAS

SET UP COPYOF DATABASE�FOR PROGRAM

AVAILABLE�COMPUTER�

TOOLS

AND

ENTER SDD�DATA INTO THE �

RECORD

PUBLISH�SPECIFICATION

PUBLISH�SDD

RELEASED�SPECIFICATIONS

RELEASED�SDD

EN

TER

PR

ISE

EN

GIN

EE

RIN

G

MANAGE�DATABASE

PROGRAM�WORK

GENERIC�PREPARATION�

WORK

REQUIREMENTSWORK

1I-A-12

Traditional Structured Analysis

MAINTAINREQUIREMENTS

ANALYSISSHEET

(IN ACOMPUTERDATABASE)

STATES ANDMODES

ANALYSIS

SELECTTEMPLATE

SYNTHESIZEARCHITECTURE

DEFINESPECIALTY

ENGINEERINGREQUIREMENTS

NATURAL ENVIRONMENTALREQUIREMENTS ANALYSIS

PUBLISHSPECIFICATIONS

DEFINEINTERFACESIDENTIFY

INTERFACE

DEFINEINTERFACE

MEDIATECHNOLOGY

IDENTUFYSPECIALTYENGINERING

DOMAINS

IDENTIFYSYSTEMSPACES

SELECTPARAMETERSAND TAILOR

RANGE

PROCSSESANALYSIS

DEFINEPROCSSES

ENVIRONMENT

MAPARCHITECTURETO PROCESSES

DEFINEEND ITEM

ZONES

MAPCOMPONENTS

TO ZONES

DEFINEZONE

ENVIRONMENTS

NEED

SPECIFICATIONS

REQUIREMENTSANALYSIS

DEVELOPDESIGN

CONCEPTS

PROGRESSIVE FEEDBACK

MAPDISCIPLINES TOARCHITECTURE

DEFINEENTITY

CAPABILITYREQUIREMENTS

IDENTIFYHOSTILETHREATS

DEFINEHOSTILE

ENVIRONMENTALREQUIREMENTS

IDENTIFY NON-COOPERATIVE

ENVIRONMENTALSTRESSES

DEFINENON-COOPERATIVE

ENVIRONMENTALREQUIREMENTS

IDENTIFY SELF-INDUCED

ENVIRONMENTALSTRESSES

DEFINESELF-INDICED

ENVIRONMENTALREQUIREMENTS

INTEGRATEENVIRONMENTALREQUIREMENTS

ENVIRONMENTALREQUIREMENTS

ANALYSIS

PERFORMANCEREQUIREMENTS

ANALYSIS

INTERFACEREQUIREMENTS

ANALYSIS

SPECIALTYENGINEERING

REQUIREMENTSANALYSIS

MISSIONANALYSIS

JOG SYSTEM ENGINEERING 10-22-2004

Template/DID

3.1

3.2

3.3

3.5

3.4

SystemDefinitionDocument

Specification

Specification templateparagraph numbers in

red.

NOTE

1I-A-13

Functional Decomposition

1.5.1 1.5.2

1.5.4 1.5.5

1.5.61.5.3

1.2.1 1.2.2

1.2.4 1.2.5

1.2.61.2.3

2.1 2.2 2.3 2.4 2.6

2.51.1 1.2

1.3 1.5

1.61.4

3.02.01.0

4.0

TOPLEVEL

FIRSTLEVEL

SECONDLEVEL

6.05.0USING DECIMAL-DELIMINATEDLEVEL NOTATION

1I-A-14

Integrated RAS and N-Square DiagramFor Internal and External Interface

INTERNAL�N-SQUARE�DIAGRAM

FUNCTION-ARCHITECTURE�MATRIX (FAM)

A11 A13

I1x

PERFORMANCE�REQUIREMENTS

ARCHITECTURE�AXIS

A

A12

I2yEXTENDED�N-SQUARE�DIAGRAM

EXTENDED COOPERATIVESYSTEMS AXIS

F4783

FUNCTION�AXIS

F4781

F

EXTENDED�FAM

QC1

F4782PERFORMANCE�REQUIREMENT�

FOR COOPERATIVE�SYSTEM

TRADITIONAL�RAS

1I-A-15

Identification ofSpecialty Engineering Constraints

2.1

1.1 1.2 1.3 1.4

2.2

2.3

3.1

3.2

4.1

4.2

5.1

5.2

5.3

6.1

HD

1.5H1

A11 A12 A13 A14

H2

H3

H4

H5

H6

H8

H9

HA

HB

HD

A15

X X X

X

X

XXX

X X XX X

X

X

XXX

X

X X

X X

X

XX

X

X

XXX

X X

X X X X

X XX

X

X

X

ARCHITECTURE-SPECIALTY ENGINEERING MATRIX(DESIGN CONSTRAINTS SCOPING MATRIX)

SPECIALTY ENGINEERING REQUIREMENTSFLOW INTO THE INDICATED SPECIFICATIONSTHROUGH THE RAS

H7 A11

H7 A12

H7 A13

A25A24

H7 A25

CONSTRAINT

H7 XX

X

ARCH

CONSTRAINTS

ARCHITECTURE

X

SDD APPENDIX E

1I-A-16

Specialty Engineering AllocationSpecialty Discipline Q7 Allocated to Architecture A11

SPECIALTY ENGINEERINGDISCIPLINE AXIS

ARCHITECTUREAXIS

Q7

A11

FUNCTION AXIS

ARCHITECTURE-SPECIALTY ENGINEERINGMATRIX (GREEN)

FUNCTION-ARCHITECTUREMATRIX (YELLOW)

INTERNAL INTERFACEMATRIX (RED)

1I-A-17

Four System Environmental ClassesSYSTEM�

ENVIRONMENTQ

COOPERATIVE�ENVIRONMENT

QC

NON-�COOPERATIVE�ENVIRONMENT

QX

SELF-INDUCED�ENVIRONMENT

QI

NATURAL�ENVIRONMENT

QN

HOSTILE�ENVIRONMENT

QH

SYSTEM�SPACE

QN1

NATURAL�STRESSES

DEVELOPED AS �ENVIRONMENTAL �

STRESSES��

SEE SDD APPENDIX B

DEVELOPED AS�EXTERNAL�

INTERFACES��

SEE SDDAPPENDIX D

SYSTEM�TIME

QN2

QN3

1I-A-18

Three Environmental RequirementsLayers• System

– Identify spaces within which the system will have to function– Select standards covering those spaces– For each standard, select parameters that apply– Tailor the range of selected parameters

• End item– Build three dimensional model of end items, physical

processes, and process environments– Extract item environments

• Component– Zone end item into spaces of common environmental

characteristics– Map components to zones– Components inherit zone environmental requirements

1I-A-19

RAS-Complete In Table FormMODEL ENTITY �REQUIREMENT ENTITY �PRODUCT ENTITY �DOCUMENT ENTITY�MID �MODEL ENTITY NAME �RID �REQUIREMENT �PID �ITEM NAME �PARA �TITLE�--------- �------------------------------------------------�----------�-------------------------------------------- �--------- �--------------------------------- �------------ �------------------------------F47 �Use System � � �A �Product System ��F471 �Deployment Ship Operations � � �A �Product System�F4711 �Store Array Operationally �XR67 �Storage Volume < 10 ISO Vans �A1 �Sensor Subsystem ���H �Specialty Engineering Disciplines � � �A �Product System�H11 �Reliability �EW34 �Failure Rate < 10 x 10-6 �A1 �Sensor Subsystem �3.1.5 �Reliability�H11 �Reliability �RG31 �Failure Rate < 3 x 10-6 �A11 �Cable �3.1.5 �Reliability�H11 �Reliability �FYH4 �Failure Rate < 5 x 10-6 �A12 �Sensor Element �3.1.5 �Reliability�H11 �Reliability �G8R4 �Failure Rate < 2 x 10-6 �A13 �Pressure Vessel �3.1.5 �Reliability�H12 �Maintainability �6GHU Mean Time to Repair < 0.2 Hours �A1 �Sensor Subsystem �3.1.6 �Maintainability�H12 �Maintainability �U9R4 �Mean Time to Repair < 0.4 Hours �A11 �Cable �3.1.6 �Maintainability�H12 �Maintainability �J897 �Mean Time to Repair < 0.2 Hours �A12 �Sensor Element �3.1.6 �Maintainability�H12 �Maintainability �9D7H �Mean Time to Repair < 0.1 Hours �A13 �Pressure Vessel �3.1.6 �Maintainability��I �System Interface � � �A �Product System�I1 �Internal Interface � � �A �Product System�I11 �Sensor Subsystem Innerface � � �A1 ��I181 �Aggregate Signal Feed Source �E37H �Aggregate Signal Feed Source �A1 �Sensor Subsystem ��

�Impedance � �Impedance= 52 ohms + 2 ohms�I181 �Aggregate Signal Feed Load �E37I �Aggregate Signal Feed Load �A4 �Analysis and Reporting ��

�Impedance � �Impedance= 52 ohms + 2 ohms � �Subsystem ��I2 �System External Interface � � �A �Product System��Q �System Environment � � �A �Product System�QH �Hostile Environment � � �A �Product System ��QI �Self-Induced Environmental � � �A �Product System�

�Stresses�QN �Natural Environment � � �A �Product System�QN1 �Temperature �6D74 �-40 degrees F< Temperature �A �Product System ��

� � �< +140 degrees F�QX �Non-Cooperative Environmental � � �A �Product System�

�Stresses�

1I-A-20

Prepare the SDD Capturing theAnalytical Work Products

MAPMETHODS

ANDDOMAINS

TOTEMPLATE,BUILD DID

PREPARESDD

PUBLISHSPECIFI-CATIONS

REQUIRE-MENTS

ANALYSIS

TEMPLATE

METHODS

SYSTEM DEFINITIONDOCUMENT

DOMAINS

SDD TEMPLATE

SPECIFI-CATIONS

SYSTEM & HW

SOFTWARE

RAS &DATABASE

TOOLS

1I-A-21

Structured Analysis Work ProductCapture and Configuration Management

UNIFIED MODELING LANGUAGE ANALYSIS PLANE

TRADITIONAL STRUCTURED ANALYSIS PLANE

ICD

APPENDIX F

APPENDIX E

MISSION AND�FUNCTIONAL�ANALYSIS &�

ALLOCATION

APPENDIX ASYSTEM TIMEAND SPACE�ANALYSIS

APPENDIX B

APPENDIX CARCHITECTURE�SYNTHESIS

APPENDIX DINTERFACE�ANALYSIS

ENVIRONMENTALANALYSIS

SPECIALTY�ASSESSMENT

PERFORMANCE�REQUIREMENTS�

DEFINITION

TIMING�REQUIREMENTS�

DEFINITION

SPECIFICATION�TREE�

DEVELOPMENT

INTERFACE�REQUIREMENTS�

DEFINITION

ENVIRONMENTAL�REQUIREMENTS�

DEFINITION

SPECIALTY�ENGINEERING�

REQUIREMENTS�DEFINITION

PROGRAM�SPECIFICATION�

FORMATTING AND�PUBLICATION

SYSTEM�DEFINITION�DOCUMENT

NEED

MIL-STD-961E�SYSTEM

MIL-STD-961E�ITEM PERF

ITEM CONSTRAINTS�ANALYSIS

ITEM PERFORMANCE �REQUIREMENTS ANALYSIS

SYSTEM ANALYSIS

MIL-STD-961E�ITEM DETAIL

PROCESS�ANALYSIS

SELECTED�SPECIFICATION�

TEMPLATES

RAS

APPENDIX G

1I-A-22

Accomplish the SW Analysis

MAPMETHODS

ANDDOMAINS

TOTEMPLATE,BUILD DID

PREPARESDD

PUBLISHSPECIFI-CATIONSREQUIRE-

MENTSANALYSIS

(RAS &DATABASE)

TEMPLATE

METHODS

SYSTEM DEFINITIONDOCUMENT

DOMAINS

SDD TEMPLATE

SPECIFI-CATIONS

SYSTEM & HW

SOFTWARE

RAS &DATABASE

TOOLS

1I-A-23

Unified Modeling LanguageImplementation Approach

BuildContextDiagram

LP LPBuild UseCases For

EachTerminator

LPBuild Scenarios

For EachUse Case

LPTranslate

Scenarios IntoActivity Diagrams

IntegrateActivity

Diagrams

Assign/AdjustClassifiers

Need

SequenceDiagramAnalysis

StateAnalysis

CommunicationAnalysis

IOR IOR

Assign SwimLanes ToActivity

Diagrams

XOR

PackagingAnalysis This

Level

Class, ObjectComponent,

Node, Subsystem

XOR

StartSpiralN+1

DynamicAnalysis

Structural ClassifierAnalysis

Design Software

Format andPublish

SpecificationSpecification

Template

Write Code FormallyVerify Code

Simulate AND

AND

Requirements Analysis and Specification Publication

Alloca

tion

1I-A-24

Structural Classifier AnalysisUse Cases

Scenarios Activities

Context�Diagram

Activity�Integration

FinalActivity�

View

Swim Lanes�Not �

Illustrated

1I-A-25

Swim Lanes for AllocationCOMPONENT AX31 COMPONENT AX32 COMPONENT AX33

ACTIVITY DIAGRAM FOR NODE AX3

NY1

NY2

NY3

NY4 NY5

NY6

1I-A-26

Progressive Identification of ProductEntities

NODE NODE NODE

COMPONENT

CLASS

OBJECT

SOFTWARE�ENTITY

AX

AX1 AX2 AX3

AX31

AX311

AX3111

COMPONENTAX32

COMPONENTAX33

SYSTEMA

1I-A-27

Dynamic Diagrams to Explore ProductEntity Capabilities

COMPONENT AX31 COMPONENT AX32

LZ1LZ2

LZ3

LZ4

COMPONENT�AX31

COMPONENT�AX32

COMPONENT�AX33

Sequence Diagram State Diagram Communication Diagram

1I-A-28

Specification

The Entity Capabilities Flow Into theSpecification Through the RAS

MODELING ENTITY REQUIREMENT ENTITY PRODUCT ENTITYMID TITLE RID TITLE PID TITLE--------- --------------------------- -------- --------------------------- ---------- ---------------------------U452 Use Case D4XT A5412 Software ComponentBU7Y Activity DiagramL456 State DiagramR4367 Sequence DiagramC5RT Communication Diag.O44324 Object/Class DiagramC4432 Component DiagramZ443 Deployment Diagram

1I-A-29

A Particular Implementation Today

RAS�IN�

DOORS

ENHANCEDFFBD�

IN CORE

MODERN�STRUCTURED�

ANALYSIS�USING�

STP

MANUALLY�ACCOMPLISHED�

N-SQUARE�ANALYSIS

MANUALLY�ACCOMPLISHED�

ENVIRONMENTAL�ANALYSIS

UML�ACCOMPLISHED�

WITH�RATIONAL�PRODUCTS

PUBLISH�SPECIFICATION

VERTICAL�TRACEABILIY

1I-A-30

Publish the Results

MAPMETHODS

ANDDOMAINS

TOTEMPLATE,BUILD DID

PREPARESDD

PUBLISHSPECIFI-CATIONS

REQUIRE-MENTS

ANALYSIS

TEMPLATE

METHODS

SYSTEM DEFINITIONDOCUMENT

DOMAINS

SDD TEMPLATE

SPECIFI-CATIONS

SYSTEM & HW

SOFTWARE

RAS &DATABASE

TOOLS

1I-A-31

Specification Review and ApprovalProcess

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

1I-A-32

Toward Process Simplicity

TRADITIONALSTRUCTURED

ANALYSIS

FLOWCHARTING

MODERNSTRUCTURED

ANALYSIS

EARLYOOA

UML

SYS ML1950s 2010s

SYSTEMSAND HARDWARE

PATH

SOFTWAREPATH

TIME

UTOPIA!

AFs

USE OFEXECUTABLE

MODELS

1I-A-33

Evidence of an Approach PathUML and TSA

UNIFIED MODELING LANGUAGE (UML)

TRADITIONAL STRUCTURED ANALYSIS (TSA)

DEPLOY-MENT

DIAGRAM

COMPONENTDIAGRAM

OBJECT& CLASS

DIAGRAMS

ARCHITECTUREBLOCK DIAGRAM

ACTIVITYDIAGRAM

SEQUENCEDIAGRAM

COLLABOR-ATION

DIAGRAM

TIMELINEDIAGRAM

STATECHART

SCHEMATICBLOCK

DIAGRAM

FUNCTIONALFLOW

DIAGRAM

USECASE

DIAGRAM

INTERACTION DIAGRAMS

PHYSICALFACET

BEHAVIORALFACET

FUNCTION-AL FACET

STATEDIAGRAM

STATIC REPRESENTATION DYNAMIC REPRESENTATION

1I-A-34

We Still Have to Push These TogetherSome More

UMLVERSION

2.0

SysMLVERSION

1.0

1I-A-35

Movement to Model-DrivenDevelopment

MODEL DRIVEN DEVELOPMENT

2010 203019701920 1990

NO

W

DATES ARENOTIONAL

DOCUMENT DRIVEN DEVELOPMENT

RISE IN THE USEOF STRUCTURED

ANALYSIS

DATABASE DRIVENDEVELOPMENT