2 Dec 2017 Model Based Systems Engineering MBSE DISTRIBUTION STATEMENT A Approved for public release distribution is unlimited 30 NOVEMBER 2017 Greg Shaffer SPAWAR Assistant Chief Engineer for Mission Architecture ID: 763472
Download Presentation The PPT/PDF document "2 Dec 2017 Model Based Systems Engineeri..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
2 Dec 2017 Model Based Systems Engineering(MBSE) DISTRIBUTION STATEMENT A: Approved for public release, distribution is unlimited (30 NOVEMBER 2017) Greg ShafferSPAWAR Assistant Chief Engineer for Mission ArchitectureSPAWAR Code 5.0B INCOSE San Diego Mini Conference
Upfront System of Systems Engineering Matters Stove-pipe Development: The Collective Result of Individual Decisions Infrastructure : Too much Too varied Too old Software & Applications:Too manyToo varied to maintain it all Infrastructure :Rapid hardware refresh as a requirementDecouple Hardware from Software & ApplicationsSoftware & Applications:Quality AssuranceConfiguration Management Holistic Enterprise Approach to Drive Resiliency & Interoperability Difficult to Manage & Operate Easier to Manage & Operate Today’s Navy The Future Navy Challenges to Improving Resiliency & Interoperability
Engineering Building Blocks Systems Engineering Enterprise Architecture Integration & Interoperability Components Systems Enclaves Platforms End-to-End / Mission Thread Ship / Shore / Sub / Air
External Focused Engineering Internal Focused Engineering System of Systems Engineering Systems Engineering JMPS GCCS-M IBS TBMCS GBS ISNS SE vs SoSE DCGS-N* GALE Common Geo-positioning Service GGCS-J I-3 Image Product Library GERT SOCET GXP SIGINT Subsystem Multi-INT Subsystem GCCS-M IBS TBMCS GBS ISNS JMPS GALE Common Geo-positioning Service GGCS-J I-3 Image Product Library GERT SOCET GXP SIGINT Subsystem Multi-INT Subsystem DCGS-N*
SoSE Approach Mission / Capability focus Enterprise / SoS Requirements Technology Insertion Driving Program Implementation Adherence to Target Architectures Coordination with Certification activities Provide End-to-End SoSE /SE rigor by working with programs/projects to address implementation Better hand-off to Certification activities – OQE to support Independent Assessments Provide SoSE to ensure SoS Mission capabilities context in test planning and certification activities Ensure SoS performance and resilience to support missions
Cohesive architecture for all of Capabilities Bake in interoperability and resiliencyTraceability from mission to capability to function Unified requirements at the Enterprise levelEliminate stovepipesBuild in enterprise requirements Enterprise Architecture Vision Single authoritative data repository Centralized documentation of all builds and installs Enables COA analysis against fielded and programmed baselines Enterprise change control process Ensures all effected parties have a voice in changes before they occur “Single Source of Truth” Architecture is a Means to an End
MBSE Definition Model-Based S ystems E ngineering (MBSE) is the formalized application of modeling to support Systems Engineering activities including, but not limited to: requirements analysis; validation and verification; functional analysis and allocations; performance analysis and trade studies; and system architecture specification beginning in the conceptual design phase and continuing throughout the System Development Life Cycle (Planning, Analysis, Design, Development, Integration/Test, Implementation, Operation/Maintenance, and Disposition).Today:Standalone models related through documents Future: Shared system model with multiple views, and connected to discipline models
MBSE Framework Collect SoS Design SoS Design Develop Data Model (DIV-1) Develop/Identify Relationships between Use Cases and Operational Model Trace top level Requirements to Operational Situations Establish Functional Baseline/ ICTB-1s AnalyzeSoS Req. Allocation SoS Req. Allocation
Extended MBSE Framework Identify Cyber control Points Synchronize Test plans with all relevant PoR’s and systems in the SoS Document System allocated Baseline Create test plans from state machine diagrams Sys. Req. Sys. Design Implementation Integration & Test Sys. Eval. & Cert. Operations & Support
MBSE Framework & System Engineering “V” An MBSE process should encompass all Engineering activities including implementation, testing, and fielding. Sustain Field Validate System Design Integrate & Test Characterize System Identify Boundaries Implement
Making it All Work Together Alignment of SE and SoSE Activities to Deliver Capabilities System / Interface Specs & Requirements Compliance and Certification Implementation Guidance (Standards) Models Target Architectures Artifacts & Implementation Enterprise Architecture Policy SETR MBSE Governance Process Sub-WGs Architecture Working Group (AWG) WG Chair Architecture Governance Board (AGB) Chief Architect MBSE as a key enabler Deliver Capabilities with Resiliency and Interoperability “ Baked In ”
BACKUP
What is an Architecture A conceptual model that defines the structure and behavior of a system/enterprise. It is a formal description and representation of a system/enterprise, organized in a way that supports reasoning about the structures and behaviors of the system/enterprise. It comprises the system/enterprise components, a mapping of functionality onto hardware and software components, information exchanges between the system/enterprise components and externally visible properties of those components and the relationships (e.g. the behavior) between them.