A-2-12L-02 C JOG SYSTEM ENGINEERING, INC. SYSTEM DEVELOPMENT POWERHOUSE Jeffrey O. Grady President...

A-2-12L-02 C JOG SYSTEM ENGINEERING, INC.

SYSTEM DEVELOPMENTPOWERHOUSE

Jeffrey O. GradyPresident

JOG System Engineering, Inc.6015 Charae Street

San Diego, CA 92122(858) [email protected]

http://www.jogse.com

This presentation offers National Defense Industrial Association (NDIA) Systems Engineering Conference occurring October 20-23, 2003 at the Hyatt Regency Ilandia Hotel in San Diego, California is a portion of a four hour presentation (a subset of an 18 day system engineering course of study) covering the four fundamental areas of excellence required for an enterprise to satisfy the presentation title.

NDIA INCOSE

mailto:[email protected]


Who Is Jeff Grady?CURRENT POSITION

President, JOG System Engineering, Inc.System Engineering Assessment, Consulting, and Education Firm

PRIOR EXPERIENCE1954 - 1964 U.S. Marines1964 - 1965 General Precision, Librascope Div

Customer Training Instructor, SUBROC and ASROC ASW Systems1965 - 1982 Teledyne Ryan Aeronautical

Field Engineer, AQM-34 Series Special Purpose AircraftProject Engineer, System Engineer, Unmanned Aircraft Systems

1982 - 1984 General Dynamics Convair DivisionSystem Engineer, Cruise Missile, Advanced Cruise Missile

1984 - 1993 General Dynamics Space Systems DivisionFunctional Engineering Chief & Manager, Systems DevelopmentAdvanced Projects Systems Engineering

FORMAL EDUCATIONBA Math, SDSUMS Systems Management, USC with Information Systems certificate

INCOSE Fellow, Founder, First Elected SecretaryAUTHOR System Requirements Analysis, System Integration, System

Validation and Verification, System Engineering Planning and Enterprise Identity, System Engineering Deployment


First, what is a system?

SYSTEMSYSTEM

ENVIRON-MENT

A collection of entities that interact through relations to achieve common purpose.


Is Your Company a Powerhouse of System Engineering?

INPUT

OUPUT

PROCESS

Or is it only wishful thinking that it could be.


The Answer is in the ProcessF41F42F44 GRAND

SYSTEMSSUSTAINMENT

USESYSTEMF47F48DISPOSEDSYSTEM

SUPPLIERMATERIALSUPPLIERCONTROLF49F46MANAGE ENTERPRISEPROVIDE PROGRAM

RESOURCESACQUIRE NEW

BUSINESS2535FF4F1F3F2LESSONSLEARNED

NEWPROGRAM

PROGRAMRESOURCESSYSTEM/PROGRAM LIFE CYCLE22XX: REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION229MANAGE

CUSTOMERACTIVITIES

F52ENTERPRISEMISSION

CUSTOMERNEEED

FF47NEEDSUPPLIERFUNCTIONSF6 GRAND

SYSTEMSREQUIREMENTS

GRANDSYSTEMS

SYNTHESIS

GRANDSYSTEMS

VERIFICATION

MANAGEPROGRAM

GRAND SYSTEMS MANAGEMENTASSUREPRODUCT

AND PROCESSQUALITY

ENTERPRISESCOPE

GRAND SYSTEMSDEVELOPMENT

OVERLAY

GRAND SYSTEMSEMPLOYMENT

OVERLAY


The Simple Secret to Successful System Development

• Define the problem• Synthesize a solution

– Engineering design– Acquisition of material– Manufacturing

• Prove that the solution satisfies the requirements

• Accomplish all three steps within the context of a sound management infrastructure


Engineer Your Enterprise as a System

DEFINEPRODUCT

DEFINEDESIGN

VERIFYDESIGN

F4231 F4232 F4333

FUNCTION

F4231

F4232

F4233

FUNCTIONAL/PROCESS ORGANIZATION

DEPT 210

DEPT 220

DEPT 230

DEFINE

D200

SYSTEMS

D210

DESIGN

D220

TEST &EVALUATION

D230

ALLOCATION OF FUNCTIONALITY

ENTERPRISE COMMON PROCESS DEFINITION

ENTERPRISE FUNCTIONAL ORGANIZATIONAL STRUCTURE

DEFINITION


The Five Enterprise Functions Mapped to an Organization Structure

PROGRAM JDIRECTORPROGRAM

INTEGRATIONTEAM MGR

PROGRAMBUSINESSTEAM MGR

INTEGRATEDPRODUCT

TEAM 1 MGR

INTEGRATEDPRODUCT

TEAM T MGR

TECHNICALFUNCTIONS

VP

ENTERPRISEEXECUTIVE

NEWBUSINESS

VP

CONTRACTSHUMANRESOURCESFACILITIESD900PROGRAM JD130D110D120D170FINANCED150LEGALD140D000FUNCTIONALORGANIZATION

PROGRAMSVP

D400D4J0D200ENTERPRISEINTEGRATION

TEAM VP

D300D4JZD4J1D4JTD4JYENTERPRISE TOPMANAGEMENT

ENGINEERINGMANUFACT-URING

SYSTEMQUALITYLOGISTICSD210D220D500D230BUSINESS

FUNCTIONSVP

D100INFORMATIONSYSTEM VP

D600MATERIAL &PROCUREMENTSECURITYD240

ASSUREPRODUCT AND

PROCESSQUALITY

PROVIDE PROGRAM

RESOURCES

MANAGE THEENTERPRISE

PERFORMENTERPRISE

BUSINESS

ACUIRE NEWBUSINESS


Functional Planning Structures, F-Strings

ENTERPRISEFUNCTIONALITY (F)

FUNCTIONALDEPARTMENT

STRUCTURE (D)

PLANNING LEVEL GRANULARITY

F122-D262 IDENTIFIES A UNIQUEELEMENT OF WORK

BEWARE OF EXCESSIVE PLANNING DETAIL

F122

D262


F342-D230

F342

D230D310

D420

D140

D160

D330

D450

D330

F342-D310F342-D420

F342-D140

F342-D160

F342-D330

F342-D450

F342-D330

E3

PROGRAMWORK PACKAGE

FOR ITEM A11TASK F342

DESIGNITEM

ENTERPRISEFUNCTIONALITY

FUNCTIONALDEPARTMENTSTRUCTURE

GENERICWORK

CATALOG

GENERIC TASKMAPPING TO

PROGRAM TASK

Primary Task Responsibility

PRINCIPAL DEPARTMENT LEADS INPRACTICES DESCRIPTIONTOOLS SELECTIONTOOLS AND PRACTICES TRAINING


Program Planning Strings,P-Strings

• PROGRAM IDENTIFICATION (P)– PERMITS COMPREHENSIVE ENTERPRISE DATABASE

• PROGRAM PHASE/STAGE (S)– COORDINATES COMMON PROCESS WITH CUSTOMER

PROGRAM PHASING

• PROGRAM EVENTS (E)– FITS WORK INTO TIME AXIS

• PROGRAM ARCHITECTURE (A)– LINKS PLANNING TO PRODUCT– LINKS PLANNING TO IPD TEAMS

P05-S01-E03-A12


Typical Composite Planning String

P05-S01 -E03 -A12-F122-D262

ENTERPRISEPROGRAM 05

PRODUCT WBS/ARCHITECTUREITEM A12

E00E01E02E03E04E05E06

CONTRACT AWARDSYSTEM REQUIREMENTS REVIEWSYSTEM DESIGN REVIEWPRELIMINARY DESIGN REVIEWCRITICAL DESIGN REVIEWFUNCTIONAL CONFIGURATION AUDITPHYSICAL CONFIGURATION AUDIT

PROCESS (SEE EDD APPENDIX A)

FUNCTIONAL DEPARTMENTSUPPLYING PERSONNELDOING PROGRAM WORK(SEE EDD APPENDIX C)

ENTERPRISEF-STRINGS

PROGRAM PHASE 01

SOW(INITIAL PLANNING STRINGS)

PROGRAM EVENT 03

PROGRAMP-STRINGS


Define Product Requirements- 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?


Kinds of Product Requirements

PERFORMANCEREQUIREMENTS

(ENTITY CAPABILITIES)

INTE

RFA

CE

REQ

UIR

EMEN

TS

ENVI

RO

NM

ENTA

LR

EQU

IREM

ENTS

SPEC

IALT

YEN

GIN

EER

ING

REQ

UIR

EMEN

TS

FUNCTIONALREQUIREMENTS

(ENTITYCAPABILITIES)

NON-FUNCTIONALREQUIREMENTS

SYSTEMS AND HARDWAREREQUIREMENTS

SOFTWAREREQUIREMENTS

DESIGN CONSTRAINTS


Use Structured Analysis to Understand Problem Space

PROBLEMSPACE

ANALYST

FUNCTIONALFACET

OBJECTFACET

BEHAVIORALFACET

VISION


Systems and Hardware Structured Analysis Models

• Traditional structured analysis• Flow diagramming• Enhanced flow diagramming• Behavioral diagramming• IDEF-0• Process diagramming

• State diagramming• FRAT• Quality function deployment (QFD)


Functional Flow Diagramming Levels

F151 F152

1.5.4 1.5.5

F156F153

F121 F122

F124 F125

F126F123

F21 F22 F23 F24 F26

2.5F11 F12

F13 F15

F16F14

F3F2F1

F4

LIFECYCLE

FIRSTEXPANSION

SECONDEXPANSION

F6F5

USING BASE 60 FUNCTION IDNOTATION

NEEDF


Traditional Structured Analysis SummaryFUNCTIONAL FLOW DIAGRAM

SYNTHESIZE THEARCHITECTURE

FUNCTION TRANS-FORMED INTO PERFORMANCEREQUIREMENTSAND ALLOCATEDTO ARCHITECTURE

MANUFACTURING BREAKDOWN STRUCTUREDRAWING BREAKDOWN STRUCTUREWORK BREAKDOWN STRUCTUREINTERFACE ANALYSISMAKE-BUY PLAN/PROCUREMENTCONFIGURATION ITEM ANALYSISSPECIFICATION TREE DEVELOPMENTTEAM/PRINCIPAL ENGINEER ASSIGNMENT

F-A MATRIX

CONSTRAINTS ANALYSIS


Who Does the Structured Analysis Work?

SYSTEMSEGMENTELEMENTCOMPONENTITEM


Understand the Source of Needed Interfaces and Manage Them Well

FUNCTION AXIS

ARCHITECTUREAXIS

F4713

A14

PERFORMANCEREQUIREMENTS

A11F4711

INTERFACE I115

INTERNALINTERFACEMATRIX(N-SQUARE)

FUNCTION-ARCHITECHTURE MATRIX(TRADITIONAL RAS)


2.11.1 1.2 1.3 1.4

2.22.33.13.24.14.25.15.25.36.1

DD

1.5D1

A11 A12 A13 A14

D2D3D4D5D6

D8D9DADB

DD

A15X X X

XX

XXXX X X

X X

XX

XXX

X

X XX X

XX

X

X

X

XXXX X

X X X X

X XX

XX

X

ARCHITECTURE-SPECIALTY ENGINEERING MATRIX(DESIGN CONSTRAINTS SCOPING MATRIX)

SPECIALTY ENGINEERING REQUIREMENTSFLOW INTO THE INDICATED SPECIFICATIONS

D7 A11

D7 A12

D7 A13

A25A24

D7 A21

CONSTRAINT

D7 XX

X

ARCH

ARCHITECTURE

X

Systematic Identification of Specialty Engineering Constraints

Motivated by AFSCM-375 Series

DOMAINS


Recognize the Complete Set of Environmental Stresses

SYSTEMENVIRONMENTESPACETIMENATURALENVIORNMENTAL

STRESSES

ENNATURALENVIRONMENTEN1EN2EN3NON-COOPERATIVE

ENVIRONMENTHOSTILE

ENVIRONMENTEXEHSELF INDUCEDENVIRONMENTAL

STRESSES

EICOOPERATIVESYSTEMS

ENVIRONMENT

EC

SDDAPPENDIX

D

SDDAPPENDIX

B


Environmental Requirements Analysis Algorithm

• System environmental requirements– Define system spaces– Select standards covering those spaces– Delete unnecessary requirements– Tailor remaining parameter ranges

• End item environmental requirements– Map end items to process steps– Define process step environments– Integrate multiple process step differences

• Component environmental requirements– Zone end item and define zone environments– Map components to zones


Link Structured Analysis to Specification Templates

UNIFIED MODELING LANGUAGE ANALYSIS PLANETRADITIONAL STRUCTURED ANALYSIS PLANEICDAPPENDIXFAPPENDIXEMISSIONS ANDFUNCTIONALANALYSIS &ALLOCATION

APPENDIX ASYSTEMTIME AND SPACE

ANALYSIS

APPENDIX BAPPENDIX CARCHITECTURESYNTHESIS

APPENDIXDINTERFACEANALYSIS

ENVIRONMENTALANALYSIS

SPECIALTYASSESSMENTPERFORMANCEREQUIREMENTS

DEFINITION

TIMINGREQUIREMENTS

DEFINITION

SPECIFICATIONTREE

DEVELOPMENT

INTERFACEREQUIREMENTS

DEFINITION

ENVIRONMENTALREQUIREMENTS

DEFINITION

SPECIALTYENGINEERING

REQUIREMENTSDEFINITION

PROGRAMSPECIFICATION

FORMATTING ANDPUBLICATION

SYSTEMDEFINITIONDOCUMENT

NEEDMIL-STD-961DSYSTEM

MIL-STD-961DITEM PERF

ITEM CONSTRAINTS ANALYSISITEM PERFORMANCE REQUIREMENTS ANALYSISSYSTEM ANALYSISMIL-STD-961DITEM DETAIL

PROCESSANALYSIS

SELECTEDSPECIFICATION

TEMPLATES


MIL-STD-961E Specification StructureSystems and Hardware Template

PARA

33.13.1.13.1.23.1.33.1.43.1.53.1.63.1.73.1.83.1.93.1.103.1.113.1.123.1.133.1.143.1.153.1.163.1.173.1.18

TITLE

RequirementsFunctional and Performance Rqmts.MissionsThreatRequired States and ModesEntity Capability RequirementsReliabilityMaintainabilityDeployabilityAvailabilityEnvironmental ConditionsTransportabilityMaterials and ProcessesElectromagnetic RadiationNameplates and Product MarkingsProducibilityInterchangeabilitySafetyHuman Factors EngineeringSecurity and Privacy

ANALYTICAL METHOD

N/AN/AMission analysisThreat analysisTraditional structured analysisTraditional structured analysisReliability math modelMaintainability math modelTraditional structured analysisAvailability math modelStandards, EUP, ZoningTraditional structured analysisBoilerplateStandardsBoilerplateBoilerplateBoilerplateStandardsStandardsStandards


Computer Software Structured Analysis Models

• Process-oriented analysis• Flow charting• Yourdon-Demarco• Hatley-Pirbhai

• Data-oriented analysis• Table normalizing• IDEF-1X

• Object-oriented analysis– Early models– UML


Structured Analysis Pathways

TRADITIONALSTRUCTURED

ANALYSIS

FLOWCHARTING

MODERNSTRUCTURED

ANALYSIS

EARLYOOA

UML

SE-UML

1950s 2010s


UML and TSA ComparedThe Future Revealed

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

TIMEFACET

BEHAVIORALFACET

FUNCTIONAL FACET

STATEDIAGRAM

STATIC MODELING DYNAMIC MODELING


MAN'SKNOWLEDGE

EXPANDINGKNOWLEDGE

MAN'SLIMITATIONS

SPECIALIZATIONEFFECTS

IT WON'TALL FIT!

The Basis For Everything We Do in System Engineering


We Are All Specialists - a Partial Solution

GENERALIST KNOWLEDGE BASESUBSYSTEM KNOWLEDGE BASESPECIALIST KNOWLEDGE BASE

ALL KNOWLEDGE

BREADTH OF KNOWLEDGE

DEP

TH O

F K

NO

WLE

DG

E


ITEM X ITEM Y

HUMAN COMMUNICATIONS -WORST INTERFACE ONPLANET EARTH!!

Physically Collocate to Recognize the Most Efficient Communication

Media

Electrical EngineerMechanical EngineerStructural Dynamics AnalystTeam Leader

ITEM XTEAM


Integration Skills

DOMAINX

DOMAINY

DOMAIN OF THESYSTEM ENGINEER

INTEGRATIONELEMENT Xi

INTEGRATIONELEMENT Yi


Integration Agent IdentificationInterface Integration and Lowest Common

Parent Team (LCPT)

SYSTEMSEGMENTELEMENTCOMPONENTITEM


Benefits Of Product Team Organization

WBS1000

WBS2000

WBS3000

WBS4000

IPT1

IPT2

IPT 3

IPT 4

PRODUCT N-SQUARE DIAGRAM

ORGANIZATION N-SQUARE DIAGRAM

CROSS-ORGANIZATIONALINTERFACEREQUIREMENT

INTER-TEAMCOMMUNICATIONREQUIREMENT

ICWG

The Most Powerful Way to Organize on a Program

ORGANIZATIONALMANAGEMENT

PRODUCTINTEGRATION


VERIFICATIONREPORTS

The Powerful Message Offeredby the “V” Model

SYSTEMREQUIREMENTS

SYSTEMTEST

END ITEMREQUIREMENTS

END ITEMTEST

COMPONENTREQUIREMENTS

COMPONENTTEST

SUBSYSTEMTEST

SUBSYSTEMREQUIREMENTS

DESIGN &INTEGRATION

VERIFICATIONREQUIREMENTS

DEVELOPMENTDOWNSTROKE

DEVELOPMENTUPSTROKE

VERIFICATIONPLANS

V WORK


Verification Atomic Structure

SECTION3 PARA

3.5.6.3

TITLE

Transmitter Power

METHOD

Test

SECTION4 PARA

4.3.24

Verification String

• Link specification part 3 to method and part 4 verification requirements content to form strings

• Allocate verification strings to verification tasks• Collect strings about these tasks• Assign task responsibility• Plan tasks• Implement tasks on schedule• Report results and collect these reports• Form a judgment about report content

Table 4-1 Verification Traceability Matrix


Transformation of Requirements Into Tasks (Molecules of Work)

1

TEST ANALYSIS DEMO EXAMINATION

2

34

5 6 78

910 1112

13

14

15

16

17

18

19 20 21

22

23 24

2526 27

28

29

3031

32

333435

36

37

3839

40

41

42

4344

45

46

4748

49

50

51

ATOMS


Verification Tracking Matrices

VERIFICATIONCOMPLIANCE

MATRIX

VERIFICATIONTASK TRACKING

MATRIX

INCLUDES EVERY VERIFICATION STRING

INCLUDES EVERY VERIFICATION TASKEACH OF WHICH IS COMPOSED OFMULTIPLE STRINGS

SPECIFICATIONVERIFICATIONTRACEABILITY

MATRICES

TASK ONLYSCREEN

UNION OFMATRICES

VERIFICATIONITEM TRACKING

MATRIX

ITEM ONLYSCREEN

VERIFICATIONDESIGN

HAPPENS HERE


Verification Documentation Pattern

ITEMPERFORMANCE

SPECIFICATIONS

ITEMDETAIL

SPECIFICATIONS

SYSTEMSPECIFICATION

ITEM QUALPLANS AND

PROCEDURES

SYSTEM TEST AND EVAL

PLANS ANDPROCEDURES

ITEM ACCEPTANCEPLANS AND

PROCEDURES

ITEM QUAL REPORTS

SYSTEM TEST AND EVALREPORTS

ITEM ACCEPTANCE

REPORTS


Road to Success

• Define the problem• Synthesize a solution

– Engineering design– Acquisition of material– Manufacturing

• Prove that the solution satisfies the requirements

• Accomplish all three steps within the context of a sound management infrastructure

A-2-12L-02 C JOG SYSTEM ENGINEERING, INC. SYSTEM DEVELOPMENT POWERHOUSE Jeffrey O. Grady President...

Documents

Transcript of A-2-12L-02 C JOG SYSTEM ENGINEERING, INC. SYSTEM DEVELOPMENT POWERHOUSE Jeffrey O. Grady President...