What MBSE Methodologies are Widely Accepted?
The following methodologies seem to be the basis for all methodologies today.
Methodologies:
INCOSE Object Oriented Systems Engineering Method (OOSEM)
"This methodology is developed by INCOSE (INCOSE, 2010). It combines object-oriented techniques, a model-based design approach, and top-down waterfall-style system engineering practices. Analyze needs, define system requirements, define logical architecture, synthesize allocated architectures, optimize and evaluate alternatives, and verify & validate systems are the main activities of OOSEM. When designing a system-of-systems, these activities are performed for each system individually. OOSEM was integrated with ISO-15288 standard, which is dedicated to harmonize the processes used by any organization or project throughout the full lifecycle of a man-made system (Pearce and Hause, 2008). The integration allows identifying the sequence of the processes needed to deliver the essential products of the development. System Engineering processes are organized into five groups: agreement, enterprise, project, technical, and special." -MBSE Grid
"Defined as an end-to-end MBSE method, where the artifacts of the method are modeling artifacts that are managed and controlled throughout the SE process. " -INCOSE SE Handbook
IBM Rational Telelogic Harmony-SE
"The process for integrated systems development by Harmony can be represented by the classic “V” diagram. The left leg of the “V” describes the top-down design flow, while the right-hand side shows the bottom-up integration phases from unit test to the final system acceptance (Hoffmann, 2011). The workflow is iterative with incremental cycles through the phases of the requirements analysis, system functional analysis, and design synthesis. Models that support the requirements analysis phase are the requirement models and the system use cases model. In the system functional analysis phase, each use case is transformed into an executable model and the related system requirements are verified using model execution. The main executable models in the design synthesis phase are architectural analysis model and system architecture model. Harmony methodology is claimed to be compatible with SysML." -MBSE Grid
IMB Rational Unified Process for Systems Engineering (RUP-SE)
Vitech MBSE Methodology
Source requirements, behavior, architecture, and verification and validation – these are the main domains of this methodology (Vitech). It uses MBSE System Definition Language (SDL) to manage the syntax (structure) and semantics (meaning) of model artefacts, which can be specified either in the form of schema or ontology. Vitech methodology also uses iterations, so called, levels. These levels help to detail system specification, but they don't solve the problem of information abstraction management (Estefan, 2008).
It is a "function based methodology" -INCOSE SE Handbook
JPL State Analysis (SA)
"This methodology was created by the California Institute of Technology Jet Propulsion Laboratory (JPL). It is based on a state control architecture, where state is defined to be “a representation of the momentary condition of an evolving system,” and models describe how state evolves (Ingham et al., 2006). SA methodology provides activities for state modeling (modeling behavior according to state variables and relationships between them); state-based software design (methods to achieve objectives); goal-directed operations engineering (preparing detailed scenarios for mission objectives). Together, state and models supply what is needed to operate a system, predict future state, control towards a desired state, and assess performance (Estefan, 2008)."-MBSE Grid
Dori Object-Process Methodology (OPM)
SYSMOD
"It is dedicated to model systems by using SysML as modeling language. These are the main phases of SYSMOD: project’s context description; requirement’s collection; system’s context modeling; system’s use case and process modeling; system’s structure and state modeling; collect domain knowledge. Starting with the description of the project context, requirements of the system are captured and modeled. Use case specification allows clarifying requests and working scenarios. Processes of the system are created simultaneously. Finally, the internal structure of the system is created, parameters are defined, and behavior is modeled." -MBSE Grid
Definitions: Methodology, Process, Method, Tool, & Environment
"The word methodology is often erroneously considered synonymous with the word process. For purposes of this study, the following definitions from Martin [2] are used to distinguish methodology from process, methods, and tools:
A Process (P) is a logical sequence of tasks performed to achieve a particular objective. A process defines “WHAT” is to be done, without specifying “HOW” each task is performed. The structure of a process provides several levels of aggregation to allow analysis and definition to be done at various levels of detail to support different decision-making needs.
A Method (M) consists of techniques for performing a task, in other words, it defines the “HOW” of each task. (In this context, the words “method,” “technique,” “practice,” and “procedure” are often used interchangeably.) At any level, process tasks are performed using methods. However, each method is also a process itself, with a sequence of tasks to be performed for that particular method. In other words, the “HOW” at one level of abstraction becomes the “WHAT” at the next lower level.
A Tool (T) is an instrument that, when applied to a particular method, can enhance the efficiency of the task; provided it is applied properly and by somebody with proper skills and training. The purpose of a tool should be to facilitate the accomplishment of the “HOWs.” In a broader sense, a tool enhances the “WHAT” and the “HOW.” Most tools used to support systems engineering are computer- or software-based, which also known as Computer Aided Engineering (CAE) tools.
Based on these definitions, a methodology can be defined as a collection of related processes, methods, and tools. A methodology is essentially a “recipe” and can be thought of as the application of related processes, methods, and tools to a class of problems that all have something in common [7].
Associated with the above definitions for process, methods (and methodology), and tools is environment.
An Environment (E) consists of the surroundings, the external objects, conditions, or factors that influence the actions of an object, individual person or group [2]. These conditions can be social, cultural, personal, physical, organizational, or functional. The purpose of a project environment should be to integrate and support the use of the tools and methods used on that project. An environment thus enables (or disables) the “WHAT” and the “HOW.” A visual graphic that depicts the relationship between the so-called “PMTE” elements (Process, Methods, Tools, and Environment) is illustrated in Figure 2-1 along with the effects of technology and people on the PMTE elements."
-Survey of Model-Based Systems Engineering (MBSE) Methodologies