1. Thoughts on Model Interoperability
NDIA Modeling and Simulation Workshop
Sean McGervey
13 August, 2018

2. Agenda Why is a new paradigm for development needed?
Three enabling elements for the new paradigm
Model-Based Systems Engineering
Multidisciplinary Analysis and Optimization
Product Line Architecture
Rationale for combining these enabling elements?
How can these enabling elements be combined?

3. Why is a New Development Paradigm Needed?
Product development is still often based on opportunistic reuse or one-off modification of components to fit needs
Components that are modified must go through time consuming and costly verification and validation again
New and modified components have no pedigree or usage history making them riskier to use in products
Component development often involves multidisciplinary design aspects, conflicting requirements, and management of complex sets of system attributes and their parametric relationships
Product A
Payload
Radar
Structural
Frame
EO/IR
Engine
Comms
Product B
Radar
Payload
Structural
Frame
Weapon System
EO/IR
Engine
Comms

4. Enablers for a Better Development Paradigm:
Model-Based Systems Engineering
Requirements
Well-defined interfaces and self-consistent specifications for products and components
Robust traceability of flow down of requirements to design of products and components
Ability to assert structural, behavioral, and parametric relationships between components of products
Behavior
Structure
Parametrics

5. Enablers for a Better Development Paradigm:
Multidisciplinary Analysis and Optimization
MDAO has long been a staple of the aerospace industry
MDAO attacks the problem of multidisciplinary system design, analysis, and optimization
Federates computational models of the system from the perspective of various design disciplines
ModelCenter™ by the vendor Phoenix Integration is a COTS tool supporting MDAO work

6. Building a Better Development Paradigm, Part 1:
MBSE + MDAO = Integrated Analytical Design Verification
MBSE Workflow
MDAO Workflow
During Product Development, system attributes captured in the system model can be parametrically related to technical measures and analyzed by an integrated MDAO framework

7. Enablers for a Better Development Paradigm:
Product Line Architecture
Product lines enable reuse at each phase of the systems engineering lifecycle
Everything including product requirements, features, and configurations can be reused during product development
Many requirements will be common across all products in a product line, while others are optional
Key to realizing “economy of scale” benefits lies in pre-planned reuse of product components

8. Enablers for a Better Development Paradigm:
Product Line Lessons Learned from Lego™
Lego™ products are not just popular for the predefined designs that can be built, but for the reusable blocks
Blocks have well-defined specifications which govern how they can be used
While an entire predefined design has limited reuse value, the blocks have tremendous reuse value

9. Enablers for a Better Development Paradigm:
Reuse Should Be Pre-Planned, Not Opportunistic
Failing to appreciate that can result in unforeseen time and money modifying a component to fit a new product context
Reusing a component means reusing all the requirements and architectural decisions that drove its development

10. Building a Better Development Paradigm, Part 2:
PLA + MBSE = Domain Specific Modeling Language
Combining PLA with MBSE allows unambiguous and self-consistent specification of systems in terms of the components that are common, optional, and variable across members of its product line
Models can be built using standardized elements that are domain-specific with rules for their use that can be validated and enforced by system modeling tools

11. Building a Better Development Paradigm, Part 2:
PLA + MBSE = Domain Specific Modeling Language
The application of MBSE to the specification of a PLA also sets the stage for using MDAO for verifying design assertions

12. Putting the Pieces Together:
MBSE + MDAO + PLA = Robust Product Development
Development starts with specifying the new product in terms of the product line’s architecture constraints, and determining which components are already provisioned and which must be developed.
MBSE
(Product Specification)
New components are developed using the domain specific modeling language for the product line, and their design is verified using the integrated MDAO framework.
Verified components are added to the collection of provisioned components for the product line, and can be used in future product development.
PLA
(Component Provisioning)
MDAO
(Product Verification)

13. Summary
Products can be made faster, cheaper, and better by adopting a product line approach to their development
Opportunistic reuse and one-off modification of components is replaced by pre-planned reuse for product development
Development of new components is managed in accordance with the constraints of the product line architecture
The architecture of each component, product, and product line is specified using a SysML-based modeling language that is specific to that product line’s domain
Development of products and new components is guided by continuous verification of their design using an integrated multidisciplinary analysis and optimization framework