version 12.0 c jog system engineering 315-1 jogse grand systems development training program...
TRANSCRIPT
VERSION 12.0 c JOG System Engineering315-1
JOGSE GRAND SYSTEMSDEVELOPMENT TRAINING
PROGRAM OVERVIEW
JOG SYSTEM ENGINEERINGGRAND SYSTEMS DEVELOPMENT TRAINING PROGRAM
0900 09-01-2010
VERSION 12.0 c JOG System Engineering315-2
Agenda
• Introduction• Proposed program description• Systems management overview• Systems requirements overview• Systems synthesis overview• Systems verification overview• Discussion
VERSION 12.0 c JOG System Engineering315-3
Who Is Jeff Grady?CURRENT POSITION
President, JOG System EngineeringSystem Engineering Assessment, Consulting, and Education Firm
PRIOR EXPERIENCEU.S. MarinesGeneral Precision, Librascope Div
Customer Training Instructor, SUBROC and ASROC ASW Systems
Teledyne Ryan AeronauticalField Engineer, AQM-34 Series Special Purpose AircraftProject Engineer, System Engineer, Unmanned Aircraft Systems
General Dynamics Convair DivisionSystem Engineer, Cruise Missile, Advanced Cruise Missile
General Dynamics Space Systems DivisionEngineering Manager, Systems Development Department
FORMAL EDUCATIONSDSU, BA Math; UCSD, System Engineering Certificate;USC, MS Systems Management and Information Systems Certificate
INCOSE First Elected Secretary, Initial Journal Editor, Fellow, Founder, ESEPAUTHOR System Requirements Analysis (2), System Integration, System
Validation and Verification, System Engineering Planning and Enterprise Identity, System Engineering Deployment, System Management, System Synthesis
VERSION 12.0 c JOG System Engineering315-4
JOGSE Client Base
Boeing Defense and Space GroupBAE SystemsNorthrop GrummanUnited DefenseHughes Defense CommunicationsInterstate Electronics CorporationRaytheon (3 Divisions)CAEOrbital Science Corporation (Pamona)Loral Aeroneutronic and VoughtBooz, Allen, Hamilton (BAH)McDonnell Douglas C-17 ProgramNewport News ShipyardTalley Defense SystemsComputing Devices (US and Canada)Collins Defense SystemsTeledyne Ryan AeronauticalNaval Surface Warfare Center DahlgrenNaval Undersea Warfare Center NewportPuget Sound Naval BaseFederal Aviation Administration (FAA)NASA Lewis Research CenterNASA Johnson Space CenterMarine Corps Base Quantico, VA
SAICMagnavoxScitor (Santa Maria, El Segundo, Cape offices)Sandia National LaboratoryWestinghouse Savannah River SiteTUBITAK-SAGECollins Commercial AvionicsGeneral Motors Electromotive DivisionCaterpillar Inc.Case CorporationCubic Transportation SystemsITT (Gilfillian & Automotive Divisions)Lucas Varity (Kelsey Hayes)Beckman CoulterUS ElectricarMotorola UniversityUniversity of California, San Diego, Riverside, Irvine, and BerkeleyIndiana-Purdue UniversityUniversity of Alabama, HuntsvilleOld Dominion UniversitySOLEuropeAgronomy Society of AmericaINCOSE (symposium tutorials)
VERSION 12.0 c JOG System Engineering315-5
F41F42F44 GRANDSYSTEMS
SUSTAINMENT
USESYSTEMF47F48DISPOSEDSYSTEM
SUPPLIERMATERIALSUPPLIERCONTROL25FF4LESSONSLEARNED
NEWPROGRAM
PROGRAMRESOURCES22XX: REFER TO PROGRAM SYSTEM DEFINITION DOCUMENT FOR EXPANSION22 MANAGECUSTOMERACTIVITIES
F52ENTERPRISEVISION
CUSTOMERNEEED
FFNEEDSUPPLIERFUNCTIONSF6 GRAND
SYSTEMSREQUIREMENTS
GRANDSYSTEMS
SYNTHESIS
GRANDSYSTEMS
VERIFICATION
ENTERPRISESCOPE
GRAND SYSTEMSDEVELOPMENT
OVERLAY
GRAND SYSTEMSEMPLOYMENT
OVERLAY
SYSTEM/PROGRAM LIFE CYCLE OVERLAYACQUIRE NEWBUSINESS
F3PROVIDE PROGRAMRESOURCES
35F247GRAND SYSTEMS MANAGEMENT OVERLAYF49MANAGE ENTERPRISEF1 MANAGEPROGRAM
9F46ASSUREPRODUCT
AND PROCESSQUALITY
F4AFAF4B System Life Cycle
2
1
3 4
VERSION 12.0 c JOG System Engineering315-6
The JOGSE Grand Systems Development Training Program
Four-Course Certificate Program
• Systems Management• Systems Requirements• Systems Synthesis• Systems Verification
Grand Systems = Each enterprise program integrating and optimizing at true system level (product and process) while the enterprise integrates and optimizes across the programs.
VERSION 12.0 c JOG System Engineering315-7
Possible Program Electives• Systems Sustainment
• Systems Effectiveness 1 (Reliability, Availability, and Maintainability)
• Systems Effectiveness 2 (Systems Safety and Human Engineering)
• Systems Effectiveness 3 (Systems Security and Privacy)
• Control Systems Theory
• Operations Analysis
• System Simulation
• Universal Architecture Description Framework
• Information Systems Development Using DoDAF
VERSION 12.0 c JOG System EngineeringA-1-8
JOG System Engineering6015 Charae StreetSan Diego, CA 92122(858) [email protected]
51525354555657
Grand Systems ManagementGrand Systems Requirements Elicitation and AnalysisGrand Systems Requirements Documentation and ManagementGrand Systems SynthesisSpecialty Engineering Methods and ModelsGrand Systems VerificationGrand Systems Requirements
58595A5B5C5D5E
Grand Systems SustainmentSystems Test and EvaluationSystems SimulationComputer Software ManagementComputer Software RequirementsComputer Software SynthesisComputer Software Verification
1
2
3 4
Program Documentation
VERSION 12.0 c JOG System Engineering315-9
Recommended Program CasesLECTURER
IN THE CLASSROOM
STUDENTIN THE CLASSROOM
STUDENTAT
DISTANCE
LECTURERAT WEB
SITE
RECORDEDITLECTURERON
RECORDEDMEDIA/WEB
STUDENTSELF
DIRECTED
LECTURERON
RECORDEDMEDIA/CD
STUDENTSELF
DIRECTED
ABDEC
VERSION 12.0 c JOG System Engineering315-10
HR TOPIC TITLE GSD INCOSE SEM-------- ------------------------------------------------------------------------------------- ---------------- --------------------------------------------57-01 Introduction to Requirements Analysis 2.1 2.1, 2.2, 2.3, 2.7, 57-02 Introduction to Requirements Analysis (Continued) 2.8, 357-03 Requirements Fundamentals 2.2.1, 2.2.357-04 Requirements Relationships 2.2.2 8.457-05 Initial System Analysis 2.3.1 8.1, 8.2, 11.6, 11.8 57-06 Traditional Structured Analysis 2.3.1, 2.3.2 9.1, 9.2, D.1, D.3, D.5, D.957-07 Traditional Structured Analysis (Continued)57-08 Performance Requirements Analysis 2.3.4 8.3, D.457-09 Product Entity Synthesis 2.3.5 1057-10 Interface Identification & Requirements Analysis 2.3.6 D.257-11 Specialty Engineering Requirements Analysis 2.3.7 11.9-11.15, 11.3, 11.5, 11.6, 11.757-12 Environmental Requirements Analysis 2.3.8 11.457-13 Software Structured Analysis Using Early Methods and IDEF-1X 2.4.1, 2.4.3 Not Covered57-14 Software Structured Analysis Using MSA 2.4.2 D.757-15 Software Structured Analysis Using OOA/UML 2.4.4 D.857-16 Software Structured Analysis Using DoDAF 2.4.5 Not Covered57-17 Structured Analysis Workshop 2.3 9.557-18 Structured Analysis Workshop (Continued)57-19 Specification Management 2.5, 2.6, 2.7 38.557-20 Requirements Risk Abatement 2.7.2 6, D.1057-21 Requirements Verification 2.5 11.2, 11.357-22 Tools 2.5.2.8 9.357-23 Structured Analysis Documentation 2.3.11 Not Covered57-24 Student Team Briefings - -
INCOSE MappingRequirements Course to INCOSE SEM
VERSION 12.0 c JOG System Engineering315-11
ManagementKnowledge Grows & We Have Our Limitations
MAN'SKNOWLEDGE
EXPANDINGKNOWLEDGE
MAN'SLIMITATIONS
SPECIALIZATIONEFFECTS
IT WON'TALL FIT!
VERSION 12.0 c JOG System Engineering315-12
ALL KNOWLEDGE
GENERALIST KNOWLEDGE BASEDOMAIN KNOWLEDGE BASESPECIALIST KNOWLEDGE BASE
BREADTH OF KNOWLEDGED
EPTH
OF
KN
OW
LED
GE
ManagementWe Are All Specialists
VERSION 12.0 c JOG System Engineering315-13
ManagementDevelopment In Reverse
A*
E*
I*
P
F
S = P:(A* x E* x I*) F
I*
VERSION 12.0 c JOG System Engineering315-14
ManagementWe Seek To Forge Crowds Into Teams
A POWERFULUINIFYING
FORCE
COMMONVISION
VERSION 12.0 c JOG System Engineering315-15
ManagementOrganizational RAS
DEFINEPRODUCT
DEFINEDESIGN
VERIFYDESIGN
F4231 F4232 F4333
MODEL ENTITYMID
F4231
F4232
F4233
ORGANIZATIONAL ENTITYDEPT
210
220
230
DEFINE
D200
SYSTEMS
D210
DESIGN
D220
VERIFICATION
D230
ENTERPRISE PROCESS DEFINITION
ENTERPRISE FUNCTIONAL
ORGANIZATIONALSTRUCTURE DEFINITION
NAME
DEFINE PRODUCT
DEFINE DESIGN
VERIFY DESIGN
TASK ENTITYDESCRIPTION NAME
SYSTEMS
DESIGN
VERIFICATION
ALLOCATION OF FUNCTIONALITY
RA
S
VERSION 12.0 c JOG System Engineering315-16
ManagementOrganizing for Programs
PROGRAM AMANAGER
PROGRAM A
PROGRAM B
PROGRAM C
ENTERPRISEGENERALMANAGER
PROGRAM INTEGRATION TEAM
PRODUCTDEVELOPMENT TEAM 1
PRODUCTDEVELOPMENT TEAM 2
PRODUCTDEVELOPMENT TEAM 3
PROGRAMBUSINESSTEAM
PRODUCTIONDIRECTOR
LOGISTICSDIRECTOR
PROCUREMENTDIRECTOR
SCHEDULINGDIRECTOR
LEGALDIRECTOR
QUALITYDIRECTOR
CONTRACTSDIRECTOR
FINANCEDIRECTOR
ENGINEERINGDIRECTOR
PROGRAM AFUNCTION 1PDT 1
PROGRAM AFUNCTION 1PDT 2
PROGRAM AFUNCTION 1PDT 3
PROGRAM AFUNCTION 2PDT 2
PROGRAM AFUNCTION 3PDT 1
PROGRAM AFUNCTION 2PDT 3
PROGRAM AFUNCTION 1PIT
PROGRAM AFUNCTION 2PIT
PROGRAM AFUNCTION 4PIT
PROGRAM AFUNCTION 6PIT
PROGRAM AFUNCTION 7PIT
PROGRAM AFUNCTION 8PIT
PROGRAM AFUNCTION 4PDT 1
PROGRAM AFUNCTION 7PDT 1
PROGRAM AFUNCTION 6PDT 2
PROGRAM AFUNCTION 4PDT 3
PROGRAM AFUNCTION 6PDT 3
PROGRAM AFUNCTION 6BUSINESS
PROGRAM AFUNCTION 8BUSINESS
PROGRAM AFUNCTION 9BUSINESS
PROGRAM AFUNCTION 7PDT 3
PROGRAM AFUNCTION 5PIT
PROGRAM AFUNCTION 5PDT 1
ENTERPRISEINTEGRATIONTEAM (EIT)
ENTERPRISEFUNCTIONALORGANIZATION
VERSION 12.0 c JOG System Engineering315-17
ManagementHierarchical Integration Teaming
SEIT
PROGRAM 113
CORPORATE
BUSINESSAREA 11
SECTOR 1
PROJECT1132
PROJECT1133
PROJECT1131
Integration Paths
Management Paths
Integration Agent
VERSION 12.0 c JOG System Engineering315-18
ManagementTypical Planning String GSD Approach
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 IMP PLANNING STRING
VERSION 12.0 c JOG System Engineering315-19
ManagementRisk Index Values
VERSION 12.0 c JOG System Engineering315-20
ManagementAggregate Program Risk Index Over Time
VERSION 12.0 c JOG System Engineering315-21
ManagementAn Aggregate Assessment Metric
PRACTICE DOCUMENTATION QUALITY ASSESSMENT
TASK
IMPLEMENTATION
QUALITY
ASSESSMENT
50
50 100
100GOOD DOCUMENTATIONWELL IMPLEMENTED
POORDOCUMENT-ATIONPOORLYIMPLEMENTED
PO
OR
DO
CU
ME
NT
AT
ION
WE
LL
IM
PL
EM
EN
TE
D
GOOD DOCUMENTATIONPOORLY IMPLEMENTED
(100,100)
(38,29)
(98,15)
(13,97)
0
0
YEAR 2004EVENT 001TASK 121DEPT 877PROG 001
AUDIT EVENTIDENTIFICATION
VERSION 12.0 c JOG System Engineering315-22
RequirementsHow Does the System Engineer Approach
Unprecedented Problem Space?
PROBLEMSPACE
ANALYST
FUNCTIONALFACET
OBJECTFACET
BEHAVIORALFACET
VISION
VERSION 12.0 c JOG System Engineering315-23
RequirementsSpecification Generator
MAPMETHODS
ANDDOMAINS
TOTEMPLATE
PREPARESAR
PUBLISHSPECIFI-CATIONS
REQUIRE-MENTS
ANALYSIS(RAS &
DATABASE)
TEMPLATE
METHODS
SYSTEM ARCHITECTURE
REPORT
DOMAINS
SAR TEMPLATE
SPECIFI-CATIONS
VERSION 12.0 c JOG System Engineering315-24
RequirementsRAS-Complete In Table Form
MODEL ENTITY REQUIREMENT ENTITY PRODUCT ENTITY DOCUMENT ENTITYMID MODEL ENTITY NAME RID REQUIREMENT PID ITEM NAME PARA TITLE--------- ------------------------------------------------ ---------- -------------------------------------------- --------- --------------------------------- ------------ ------------------------------F47 Use System A Product SystemF471 Deployment Ship Operations A Product SystemF4711 Store Array Operationally XR67 Storage Volume < 10 ISO Vans A1 Sensor Subsystem
H Specialty Engineering Disciplines A Product SystemH11 Reliability EW34 Failure Rate < 10 x 10-6 A1 Sensor Subsystem 3.1.5 ReliabilityH11 Reliability RG31 Failure Rate < 3 x 10-6 A11 Cable 3.1.5 ReliabilityH11 Reliability FYH4 Failure Rate < 5 x 10-6 A12 Sensor Element 3.1.5 ReliabilityH11 Reliability G8R4 Failure Rate < 2 x 10-6 A13 Pressure Vessel 3.1.5 ReliabilityH12 Maintainability 6GHU Mean Time to Repair < 0.2 Hours A1 Sensor Subsystem 3.1.6 MaintainabilityH12 Maintainability U9R4 Mean Time to Repair < 0.4 Hours A11 Cable 3.1.6 MaintainabilityH12 Maintainability J897 Mean Time to Repair < 0.2 Hours A12 Sensor Element 3.1.6 MaintainabilityH12 Maintainability 9D7H Mean Time to Repair < 0.1 Hours A13 Pressure Vessel 3.1.6 Maintainability
I System Interface A Product SystemI1 Internal Interface A Product SystemI11 Sensor Subsystem Innerface A1I181 Aggregate Signal Feed Source E37H Aggregate Signal Feed Source A1 Sensor Subsystem
Impedance Impedance= 52 ohms + 2 ohmsI181 Aggregate Signal Feed Load E37I Aggregate Signal Feed Load A4 Analysis and Reporting
Impedance Impedance= 52 ohms + 2 ohms SubsystemI2 System External Interface A Product System
Q System Environment A Product SystemQH Hostile Environment A Product SystemQI Self-Induced Environmental A Product System
StressesQN Natural Environment A Product SystemQN1 Temperature 6D74 -40 degrees F< Temperature A Product System
< +140 degrees FQX Non-Cooperative Environmental A Product System
Stresses
VERSION 12.0 c JOG System Engineering315-25
SynthesisWhere Do System Engineers Play?
Knowledge DomainsP
rod
uct
Do
mai
ns
The Sand Box of the SystemEngineer
VERSION 12.0 c JOG System Engineering315-26
SynthesisIntegration Skills
DOMAINX
DOMAINY
DOMAIN OF THESYSTEM ENGINEER
INTEGRATIONELEMENT Xi
INTEGRATIONELEMENT Yi
VERSION 12.0 c JOG System Engineering315-27
SynthesisBenefits of Product Team Organization
SEGMENT1
SEGMENT2
SEGMENT3
SEGMENT4
IPT1
IPT2
IPT 3
IPT 4
PRODUCT N-SQUARE DIAGRAM
ORGANIZATION N-SQUARE DIAGRAM
Cross-OrganizationalInterfaceRequirement
Inter-teamCommunicationRequirement
InterfaceControlWorkingTeams
ComponentTeams
WBS, SOW, IMP, IMSBudget and scheduleSpecifications
VERSION 12.0 c JOG System Engineering315-28
SynthesisThe Fundamental Problems in Interface Work
COMPONENTX
COMPONENTY
There is a one-to-one correspondence between teams and components. There is a one- to-two correspondence between teams and interfaces.
VERSION 12.0 c JOG System Engineering315-29
SynthesisThe Fundamental Problems in Interface Work
COMPONENTX
COMPONENTY
We tend to focus inwardly
VERSION 12.0 c JOG System Engineering315-30
SynthesisThe Fundamental Problems in Interface Work
COMPONENTX
COMPONENTY
We are dependent on the worst interface on planet Earth in the development of interfaces.
HUMANCOMMUNICATIONS!!
VERSION 12.0 c JOG System Engineering315-31
SYSTEMTEST
END ITEMTEST
COMPONENTTEST
SUBSYSTEMTEST
SYSTEMREQUIREMENTS
END ITEMREQUIREMENTS
COMPONENTREQUIREMENTS
SUBSYSTEMREQUIREMENTS
DESIGN &INTEGRATION
DEVELOPMENTDOWNSTROKE DEVELOPMENT
UPSTROKE
NEED DELIVERY
Verification V Model Encourages Good Requirements
VERIFICATIONPLANNING PLANE
VERIFICATIONREPORTING
PLANE
VERSION 12.0 c JOG System Engineering315-32
VerificationVerification 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
VERSION 12.0 c JOG System Engineering315-33
3.2.7
4.2.5.1
3.2.7 4.2.5.1
Table 4-1 Verification Traceability Matrix
SPECIFICATION LIBRARY
3.2.7 4.2.5.1
ITEM A1
ID
A1
VTN
VTN
123
123
}
Table C-1 Verification Compliance Matrix
Table C-2 Verification Task Matrix
Table C-3 Verification Item Matrix
}
123
123
Table B-2 Verification Process Flow Diagram
Table B-1 Verification Schedule
INTEGRATED VERIFICATIONMANAGEMENT REPORT
INTEGRATEDVERIFICATION
PLAN (IVP)TASK
123
INTEGRATEDVERIFICATIONREPORT (IVR)
SAME PATTERN FOR QUALIFICATION USING ITEM PERFORMANCE SPECIFICATIONS SYSTEM USING SYSTEM SPECIFICATION ACCEPTANCE USING ITEM DETAIL SPECIFICAITONS
ID
A1
VERIFICATIONIMPLEMENTATION
ITEM A1 TASK 123
ITEM A1 TASK 123
ST
AT
US
INF
OR
MA
TIO
N
FCAPCA
VerificationDocumentation Stream