Application of Model-Based Systems Engineering John M. Green Senior Lecturer, Naval Postgraduate School 1
Agenda • Capstone Objective • Overview of Q1 and Q2 – Team Organization – Execution & Scope – Research – Methodology • Results & Products – Requirements – Functional Analysis – Architecture – Modeling and Simulation – CORE • Capstone Conclusions
Capstone Objective • The Objective of this Project was to Develop a System Engineering (SE) Methodology for Creating Complex, Supportable System Architectures that: – Utilize a Model Based Systems Engineering (MBSE) approach – Integrate Requirements Traceability – Implement Open Architecture (OA) and SPLs – Identify a structure which supports Combat System Software Reuse – Support early Integration of Supportability Requirements – Integrate DoDAF Artifacts with the Acquisition Requirements Process
Team Organization IPT Structure Evolved with CAPSTONE Need Q1Structure based on key research objective Requirem ents DoDAF-Requirem ents Methodology Berhane * Sarabia, Hoang, Matela, *Vajdos, Sung Mendiola ; Spt:Childs, W ellesley Kinberg , Kong, Sysavath, Valdez, Vasquez Independent Supportability Kang, Chandler *Carpenter, Banner-Bacin, Chacon, Kinberg Advisor OIPT Q2 Structure based on M Green *Childs, W ellesley, Howard, Sarabia, W entland, Carpenter, Vajdos, Pham , O’Neill; Capstone Architect Spt: Matela *Howard process execution AAW Architecture SW / O A * O’Neill, Isaian, Ortiz, *W entland, Sysavath; Rayshouny, W heeler; Spt: Carpenter , Sung, Spt: Banner-Bacin , M&S/CORE Mendiola W entland *Pham , Kong, Valdez, Vasquez; Spt: Chacon , CORE M&S Across Acq SW Arch Hoang, Matela, Sarabia Manz Q3 Structure based on OIPT artifact development Final SysML Report
Primary Research Topics Research Areas Research Artifacts Quantity Open Architecture 14 • Research focused on Service Oriented Architecture 2 tools, methodologies, DoD Architecture Framework 8 languages which could be Domain Analysis 6 applied to meet capstone Software Product Lines 8 objectives Model Based Systems Engineering 23 Systems Engineering “ VEE ” 3 Software Reuse 6 Process System Architecture & Requirements Engineering 3 • Crucial areas of project Concept of Operations 1 were researched more Software Architecture Types 7 extensively (OA, MBSE, Modeling & Simulation 3 SysML, and AAW) Systems Modeling Language 13 ExtendSim Tools & Discrete Event Modeling 2 CORE 4 Reliability Theory 3 Supportability 7 Anti-Air Warfare (P RA , etc.) 10 Total = 123
Research Application Methodology Initial Research Findings Best Practice Defined for • No single process or solution MBSE SPL Reuse Proposed • M&S & Supportability limited Language Methodology Tool • Select correct modeling language Requirements Traceability M&S Application Artifact Generation • DoDAF is not a process DoDAF SPL V&V Methods Library Structure • MBSE provides significant benefits SysML • Navy wrestling w/similar issues MBSE Agile Tool Usage M&S
Methodology Overview Sub Process SysML and MBSE Focus SysML OV5 EFFBD SV6 M&S Mission Functional System Arch Domain Rqrmnts Activity Allocation Assess Storage Analysis Best Practice Focus Friedenthal Hatley CORE Dam Bosch Moore Pirbhai Steiner Architecture Requirements M&S System Spec Proposed Arch -Ao .90 Process Process -EFFBD0 Process Agile (Iterative) Process Historical Results System Related to SPL Specification -Ao 0.96 / SPL Used -SPL Artifact -Ao 0.90 M&S Results -Predicted Ao -Confidence ANALYSIS Analysis: Does Proposed Architecture meet JCIDS Compliant Stated Requirements? Y DODaF Artifact
Methodology Top Tier Process Target System Library Context Diagram Software Product Line Use Cases Block Definition Diagram Requirements Diagram Internal Block Diagram Package Diagram Enhanced FFBD Parametric Diagram Stated Activity Diagram KPP Sequence Diagram Discrete Event Model State Machine Diagram System Timing Model Products Process Requirements Functional Architecture Verification & Generation & Analysis & Definition Validation Analysis Allocation (Process 3) (Process 4) (Process 1) (Process 2) Target System Specification Target System Architecture Generation Generation
Approach to Verify Methodology • Use Methodology to Develop an AAW Mission Architecture • Meet the following MOEs: – Self Defense – Limited Area Defense – Surveillance
Requirements Issues and Resolutions • SysML Tool Availability – No software license Independent Research for proven tools – No formal training available On-Line User for proven tools Manuals Process 3 Process 3 Process 3 Process 3 Process 3 Process 3 Process 2 Process 2 Process 2 Process 2 Process 2 Process 2 Process 4 Process 4 Process 4 Process 4 • Baseline for Requirements 1.2.1 Define 1.2.1 Define 1.2.1 Define 1.2.1 Define 1.2.1 Define 1.2.1 Define 1.3.1 Define 1.3.1 Define 1.3.1 Define 1.3.1 Define 1.3.1 Define 1.3.1 Define Mission/System Mission/System Mission/System Mission/System Mission/System Mission/System Environmental & Environmental & Environmental & Environmental & Environmental & Environmental & Objective Objective Objective Objective Objective Objective Design constraints Design constraints Design constraints Design constraints Design constraints Design constraints – Schedule required, Interaction 1.4 Define/Derive 1.4 Define/Derive 1.4 Define/Derive 1.4 Define/Derive 1.4 Define/Derive 1.4 Define/Derive 1.1 Collect 1.1 Collect 1.1 Collect 1.1 Collect 1.1 Collect 1.1 Collect 1.2.2 Define 1.2.2 Define 1.2.2 Define 1.2.2 Define 1.2.2 Define 1.2.2 Define 1.3.2 Define 1.3.2 Define 1.3.2 Define 1.3.2 Define 1.3.2 Define 1.3.2 Define Functional & Functional & Functional & Functional & Functional & Functional & Stakeholder Stakeholder Stakeholder Stakeholder Stakeholder Stakeholder System System System System System System Operations & Operations & Operations & Operations & Operations & Operations & Performance Performance Performance Performance Performance Performance 1.5 Validate 1.5 Validate 1.5 Validate 1.5 Validate 1.5 Validate 1.5 Validate 1.6 Integrate 1.6 Integrate 1.6 Integrate 1.6 Integrate 1.6 Integrate 1.6 Integrate Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Requirements Scenarios Scenarios Scenarios Scenarios Scenarios Scenarios Support Concept Support Concept Support Concept Support Concept Support Concept Support Concept Requirements Requirements Requirements Requirements Requirements Requirements parallel development 1.2.3 Define 1.2.3 Define 1.2.3 Define 1.2.3 Define 1.2.3 Define 1.2.3 Define 1.3.3 Define 1.3.3 Define 1.3.3 Define 1.3.3 Define 1.3.3 Define 1.3.3 Define System System System System System System Measures of Measures of Measures of Measures of Measures of Measures of Boundary Boundary Boundary Boundary Boundary Boundary Effectiveness Effectiveness Effectiveness Effectiveness Effectiveness Effectiveness 25 20 Max Intercepts 15 – Insufficient information 10 Target Track Geometry, 5 to derive many of Max # Intercepts @ CPA 0 3 10 20 30 40 50 60 70 80 requirements needed CPA for Parametric
Requirements Results / Products External Interface Requirements Major Functions SysML Context Diagram SysML Use Case Diagram Traceability Achieved w/SysML Supportability Requirements SysML Supportability Package SysML Requirements Diagram
Requirements Summary • Process Execution • Issues and Resolutions – Tools, KSAs and processes are not in place to – Improved over time lead requirements development on large complex systems – Teams became more effective with • This Issue can be overcome to support PHD experience technical oversight and strategic objectives • Artifacts • Lessons Learned – Expand M&S Usage – Requirements Decomposition – The process resulted in valid artifacts – Requirements Allocation which support Capstone objectives – Understand Artifact Relationship – Maintain Tool – Traceability Establishment – Verification of Allocation
Functional Analysis Issues and Resolutions • Systems Engineering process to optimize allocation of functions – Deriving Software Requirements – Tendency to map based on experience • Common Domain and Functional Descriptions NTAs & UNTL
Functional Analysis Results / Products SysML traceability from requirements Activity diagram used to to functions understand event sequence SysML Functional Diagram EEFBD provided control Sequence diagram provides graphical representation and timing relationships AAW Sequence Diagram C2 SENSOR TARGET Initiate Sensor Start Search Target Detection Data Target Detection Request Detection Update Target Tracking & Assign Track ID Track Update Target Tracking Data ENGAGE Provide Engagement Options and Initiate Engagement (Doctrine Assessment TEWA) Engage Target Assess Battle Damage SysML Supportability Package
Recommend
More recommend
