This is an old revision of the document!
Survey of MBSE Methodologies
Ontology
Language: A set of syntax and semantics
Metamodel: A description of a model
Method: Techniques for performing a task. “HOW” it needs to be done
Methodology: Collection of related processes, methods and tools
Process: A logical sequence performed to achieve a particular objective. “WHAT” needs to be done
Tool: An instrument, when applied with the correct method, can enhance the efficiency of a task
Lifecycle Development Models
Waterfall
Spiral
“V” Model
Acquisition Lifecycle Models
DoD
Concept Refinement
Technology Development
System Development & Demonstration
Production & Deployment
Operations & Support
NASA
Concept Study
Concept Development
Preliminary Design
Final Design
Fabrication, Assembly and Test
Operations & Sustainment
Disposal
ISO 15288
Concept
Develop
Production
Operate
Support
Retirement
Methodologies
Harmony/SE
Harmony-SE takes a use case approach to modeling a system. Emphasis is on use of sequence diagrams and definition of operations and interfaces. Increments are use case based.
Methodology is available here. Methodology captured in a
IBM Rational Harmony Deskbook Release 3.1.2 (2010).
The Harmony Process is split between “Harmony for Systems Engineering” and “Harmony for Embedded RT Development”. As you can see from the above figure the former focuses on the downwards side of the Vee development life cycle whilst the latter focuses on the upwards trajectory.
Objectives
Identify / derive required system functionality
Identify associated system states and modes
Allocate system functionality / modes to a physical architecture
Development Activities
Requirements Analysis
Requirements Capture
Definition of System Use Cases
System Functional Analysis
Design Synthesis
Architectural Analysis (Trade Study)
Architectural Design
Allocated System Operations
Allocation is verified through model execution
After verification then architectural design may be analyzed with regard to performance analysis (reference previous measure of effectiveness metrics)
Detailed Architectural Design
Hardware / Software Design
Object-Orientated Systems Engineering Method (OOSEM)
Closely follows the recursive nature of the Vee life cycle development approach. Adopts Integrated Product Development (IPD) team.
Objectives
Capture and analysis or requirements and design information to specify complex systems
Integration with object-orientated software, hardware and other engineering methods
Support for system-level reuse and design evolution
Development Activities
Set up model
Analyze stakeholder needs
Captures as-is state, limitations and potential improvement.
Analyzed using causal analysis techniques to determine limitations therefore derive mission requirements for the to-be system
Mission requirements are provided as
Design system requirements
System is modeled as a black box.
Scenarios are modeled as activity diagrams with swim lanes
Requirement change is evaluate as risk and flexibility is built in
Define logical architecture
Decompose and partitioning the system into logical components that interact to satisfy system requirements
With a logical architecture the system design is more resilient to requirements change and is technology neutral
Synthesize candidate allocated architectures
Optimize and evaluate alternatives
Parametric models are used to analyze and optimize performance across a range of criteria (safety, reliability, cost)
Criteria and weightings are traceable to requirements and measure of effectiveness
Monitor Technical Performance Measures
Identify potential risks
Validate and verify system
Development of plans, procedures and methods
System level use cases, scenarios are primary inputs to the development of test cases and associated verification procedures
IBM Rational Unified Process for Systems Engineering (RUP SE)
Vitech MBSE Methodology
JPL State Analysis (SA)
Object-Process Methodology (OPM)
SYSMOD