Phase I: Creating the Backbone
Creating the Backbone
The first step is creating the fundamental architecture of the model. To do this, you need to agree upon a package structure within your business area. It is important that everyone shares the same fundamental structure so that systems engineering contributors can easily jump from project to project and be familiar with the layout and so that when your system level models get incorporated into a system-of-systems model, the connections from parent model and all the child models will be uniform.
Creating The Skeleton
Phase I Steps
Steps 1-3: These steps are meant to be done in series.
Prerequisite: Setup Digital Engineering Environment: Determine company’s methodology, framework, package structure, & shared common libraries
Step 1)
Determine Project Scope: What is the system, what is the system of systems, what are the subsystems
Determine how many project models should be created based on how many people you have allocated to the effort. (Assume 2-5 people per project model, with 3-4 contributors per model ideal)
Make a master schedule outlining man hours and schedule (use 3 phase approach) and agile methodologies.
Provide team with resources to data and begin communicating with SMEs to understand what data is available where.
Step 2)
Initial Vision: Determine Model Domains Desired and Priority (Stakeholder Interaction Map)
Figure out how data currently flows between domains
Step 3)
Basic Framework: Buildout Abstract Top Level Assembly bdd
Determine which framework, methodology, and package structure to utilize whether that be MagicGrid, OOSEM, or a homegrown approach.
Methodologies, Framework, & Package Structure
There are several different package structures and layout methodologies which are perfectly good to use. MagicGrid and OOSEM are two places to start. Read more methodology related information here: What MBSE Methodologies Are Widely Accepted?
MagicGrid Methodology
Go to this site, https://discover.3ds.com/magicgrid-book-of-knowledge, and download the 350 page manual for implementing the MagicGrid Methodology. This pdf is free and instant download after clicking the link. The MagicGrid methodology came out in 2017 and piggy backs off of the previous Methodologies meantioned here : What MBSE Methodologies Are Widely Accepted?
OOSEM Methodology
OOSEM stands for Object Oriented Systems Engineering Method. OOSEM was originally based on the Object Management Group (OMG) Unified Modeling Language (UML); it now uses the OMG Systems Modeling Language (SysML) to represent systems analysis and design information. It contains activities for needs and requirements analysis, logical and allocated architecture design, and includes guidance for trade studies, validation and verification.
www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method
Home Grown Methodology
If creating a homegrown package structure, we suggest at least having the following packages:
Metamodel information
System structure,
System behavior,
System parametrics
System requirements
Documentation and traceability
Sandbox
Alternatively, Model Based System Architecture suggests 3 main packages (pg93):
Core
Configurations
Variations
Phase I Model Timeline Buildout
The diagrams below show how the model will be built out. Several tasks will happen in parallel during development. The team will explore the available external software tools, they will build out the low level Cameo system architecture, and work on building out the threads. Steps 1→4 below show a practical way to build out the model.
Note: Make sure you don't build out medium levels of fidelity on domains you already have external tools which perform that function/simulation. Likely, the external tool will do a better job, people will wonder why we are solving the problem using two different approaches, and your team will likely end up removing the medium fidelity Cameo simulation and replacing it causing significant rework.
LESS MATURE
1) Starting Point
→
2) External Simulation Tools Realized
→
3) Investigate Threads & Build Out Cameo Low Fidelity "Hooks"
MORE MATURE
4) Add Thread(s) & Build Out Low Fidelity Domains
Template Models & Shared Common Libraries
There should be at least two levels of digital engineering implementation: the higher level and the lower level. The higher global level makes the templates for all following projects starting points and updates the shared common libraries. The lower project level includes project specific content and structure.
