ModelBased Systems Engineering on a Quick Reaction Program
Model-Based Systems Engineering on a Quick Reaction Program 20 May 2015 Charles H. Patton Engineering Manager and Systems Engineer Copyright 2015 Northrop Grumman Systems Corporation. All rights reserved.
Agenda • Why invoke Model-Based Systems Engineering? • What is Model-Based Systems Engineering? • What we did on the Surrogate SATCOM IRa. D • What should you do? 2 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
The Perception? “Process is not the enemy – bad process is. ” – Toward Agile Systems Engineering Processes, Turner, Cross. Talk April 2007) Practicality Needn’t Be Cumbersome 3 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Why • Systems Engineering V Model 4 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Why (cont. ) • Collaboration – Develop models • Requirements: CONOPS, COIs, Missions, etc. • Architecture: OV 1, Block Diagrams, Data Flows, Drawings, etc. • Operation: Test and Demo plans, etc. – From different points of view • Business Development • Hardware • Software • Test • Deployment We see things differently 5 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Why (cont. ) • Coordination – Multiple engineering efforts – Accommodate changes • Communication – Common understanding • What the system is supposed to do • How the system is configured – Define subsystems and components – Identify interfaces – Logical and Physical Effective Development is the Goal 6 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
What • Model-based systems engineering (MBSE) is the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases • A model is an approximation, representation, or idealization of selected aspects of the structure, behavior, operation, or other characteristics of a real-world process, concept, or system, i. e. an abstraction • A model usually offers different views in order to serve different purposes – A view is a representation of a system from the perspective of related concerns or issues 7 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
What – Model Examples • Video games • Weather maps • Schedules • Message Simulators • Test Organizations PRI-1 8 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
What – View Examples • Hardware • Software • System – Logical – Physical – Operational 9 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
How • Operational • Logical – CONOPS, Missions – Context Diagrams – COIs, MOEs, MOPs – Architecture Block Diagram – OV 1 – Interconnect Diagrams – Requirements – Architecture Flow Diagrams – Test and Demo Plans • Functional • Physical – Product Entity Diagram – Decomposition – Drawings – Data Flow Diagrams – Equipment Configuration Diagrams – Use Cases – Checklists Capture the Thinking 10 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
How – Operational • CONOPS, Missions • COIs, MOEs, MOPs • OV 1 • Requirements ID 1 • Test and Demo Plans COI Need to increase crop yield for amount of time and material used 1. 1 MOE MOP Crop yields compared to historical yields under similar conditions 1. 1. 1. 2 1. 1. 3 CONCEPT FOR THE PROPOSED SYSTEM Annual crop yield Cost of soil amendments Time (hours) to manage irrigation The RSMS is a hardware and software Need solution applied to an existing irrigation system to monitor soil to minimize change conditions and control the application ofimpact water-based 2 on the host soil amendments according to a tailorable irrigation system parametric model. The RSMS can be configured to accommodate present and short-term forecast Percentage change in 2. 1 weather conditions. The human-system interface (HSI) provides access to the monitoring and control operability 2. 1. the parameters of the heuristic model to best. Percentage change to physical functions, and allows the user to tailor suit on-going local 1 interfaces conditions. Sensors are hot-swappable, are easily moved, and operate wirelessly. Percentage change to user 2. 1. 11 2 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. 2. 1. Approved for Public Release #15 -0852; Unlimited Distribution interfaces Percentage change to user
How – Functional • Decomposition • Data Flow Diagrams • Use Cases 12 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
How – Logical • Context Diagrams • Architecture Block Diagram • Architecture Flow Diagrams • Interconnect Diagrams 13 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
How – Physical • Product Entity Diagram • Drawings • Equipment Configuration Diagrams • Checklists 14 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Tie It All Together CONOPS, Missions, COIs, OV 1 s Operational Reqs Use Cases System Reqs Context Diagrams Architecture Block Diagrams 15 Product Entity Diagram Functional Decomposition Data Flow Diagrams Architecture Flow Diagrams Interconnect Diagrams Drawings Equipment Configuration Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Questions 16 Copyright 2015 Northrop Grumman Systems Corporation. All rights reserved.
Actions for Success q Document and review the system development plan o SEMP or SEIT Plan (what, who, when) q Document and review system operational concepts o CONOPS o Missions o OV 1 s o COIs, MOEs, MOPs q Identify, document, and review operational requirements q Describe, document, and review the system functionally o Functional Decomposition o Data Flow Diagrams o Use Cases q Identify, document, and review system requirements 17 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Actions for Success (cont. ) q Describe, document, and review the system at the logical level o Context Diagrams o Architecture Block Diagrams o Interconnect Diagrams o Architecture Flow Diagrams q Describe, document, and review the system physically o Product Entity Diagrams o Drawings o Equipment Configuration Diagrams q Document and review system test and demo plans and procedures q Create and use checklists 18 Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
Copyright � 2015 Northrop Grumman Systems Corporation. All rights reserved. Approved for Public Release #15 -0852; Unlimited Distribution
- Slides: 19