Beyond MBSE: Looking towards the Next Evolution in Systems Engineering

Beyond MBSE: Looking towards the Next Evolution in Systems Engineering David Long INCOSE President david.long@incose.org @thinkse Copyright 2015 by D. Long. Published and used by INCOSE with permission.

A Changing Environment for SE 3

A Changing Environment for SE From Aerospace & Defence to Broader Recognition 4

A Changing Environment for SE From Electromechanical to Software-Intensive to Cyber-Physical 5

A Changing Environment for SE From Stand-Alone to Interconnected to Internet of Things 6

A Changing Environment for SE 7

Building a Solid Foundation Before looking beyond MBSE, we must first look to MBSE 8

Traditional Towards MBSE: A Practice in Transition Specifications Future ATC Pilot Airplane Interface requirements Authorize Request to proceed System design Initiate power-up Power-up Report Status Analysis & Trade-off Direct taxiway Initiate Taxi Executed cmds Test plans Moving from document-centric to model-centric Reprinted from INCOSE Model-Based Systems Engineering Workshop, February 2010 9

Step 1 to Improving the Journey: Demystify (and Demythify ) Models are not new o o Central to engineering, even if they only reside in the engineer s mind Evolution from low-fidelity representations in documents to higher-fidelity, richer representations Documents remain a flexible communication mechanism serving a diverse audience MBSE requires integration, connectivity, coherence o o A series of diagrams a model Models in SE (or modeling & simulation in SE) MBSE Views allow us to construct, communicate, and analyze models o Diagrams, tables, documents, dashboards, and more can comprise a fitfor-purpose library from which to draw 10

Step 2 to Improving the Journey: Clarify 11

Step 3 to Improving the Journey: Remove Roadblocks MBSE requires SysML (or UML or UPDM or UAF). o Everyone must learn fill in the blank for our organization to adopt MBSE. We re doing SysML (or UML or UPDM or UAF) so we are already doing MBSE. We are already doing modeling and simulation. We must implement the architectural and analytical aspects to get any benefit. It s too complex. We must model everything, and it s not possible to model everything. Implementing MBSE is one size fits all. It s a technical problem. o o All I need is the right tool. I can learn it myself. We need to avoid tool lock. MBSE is the answer it does everything. 12

Plotting the Journey Beyond MBSE For Ourselves and Our Organizations Complexity Design Project Life Cycle Cross-Project Learning SE-PM 14

Aligning and Responding with Reference Architectures Complexity Image credit Don McCullough Design Project Life Cycle Cross-Project Learning 15

Recognizing Product Line Engineering Complexity Design Project Life Cycle Cross-Project Learning 16

Embracing Reuse and Composability Complexity Design Project Life Cycle Cross-Project Learning 17

Connecting across MBE: Communications, Semantics, Syntax Complexity Design Project Life Cycle One model to coordinate them all SE-PM 18

Applying SE Concepts to the Deployment of MBSE Design Project Life Cycle 19

Looking Beyond the Bounds of the Organization Advancing the Greater Community 20

Maturity Evolving Our MBSE Capability as a Community MBSE Capability Reduced cycle times System of systems interoperability Design optimization across broad trade space Cross-domain effects-based analysis Institutionalized MBSE across Academia/Industry Distributed & secure model repositories crossing multiple domains Defined MBSE theory, ontology, and formalisms Well Defined MBSE Ad Hoc MBSE Document-Centric Emerging MBSE standards Architecture model integrated with Simulation, Analysis, and Visualization Matured MBSE methods and metrics, Integrated System/HW/SW models Planning & Support Research Standards Development Processes, Practices, & Methods Tools & Technology Enhancements Outreach, Training & Education 2010 2020 2025 Reprinted from INCOSE MBSE Workshop, February 2010 21

Enabling Communication, Analysis, Learning, and More Photo Hans Hillewaert 22

Enabling Communication, Analysis, Learning, and More Photo Hans Hillewaert 23

Enabling Communication, Analysis, Learning, and More Technical Processes SE Management Non-traditional domains Model-Based SE SE Leadership Photo Hans Hillewaert Soft Systems Systems Science Systems Thinking Complexity Design Project Life Cycle Cross-Project Learning SE-PM 24

Developing Heuristics and Wizards It looks like you are trying to write a requirements specification. Can I help? It looks like you are trying to achieve.99999 reliability. Would you like me to help? Complexity Design Project Life Cycle Cross-Project Learning 25

Recognizing the Future of Systems Engineering What Lies Beyond MBSE 27

Learning from Our Colleagues Image credit Nick Veasey Image credit Or Perel 28

Analysis Models U(s) G(s) Hardware Models SSET Q RCLR Q U(s) Analysis Models G(s) Joining Our Engineering Colleagues to Enable Model-Based Engineering Operational Models System Models Component Models Operational Models System Models Component Models Systems Program Management Test Manufacturing Operational Models System Models Hardware Logistics Software Configuration Management Customer MBE Enhances Affordability, Shortens Delivery and Reduces Risk Across the Acquisition Life Cycle NDIA Model-Based Engineering Final Report, February 2011 29

Leveraging Model-Based, Focusing on Systems Engineering Enriched toolbox for communication and analysis Tailorability Composability Flexible reference architectures Heuristics Insight into efficient frontiers Rigor Scalability Higher value Toolbox of theories supporting SE Progress Systems Engineering 30