SIMVA-SoS Modeler

1. Overview

In this manual, we present our modeling tool – SIMVA-SoS modeler. SIMVA-SoS modeler is a conceptual modeling method (in this version) that can be used to model system of systems concepts and their relationship at a conceptual level.

The manual provides essential information including prerequisites to use the modeling methods, library installation steps, model types description, and example models.

2. Modeling Language Configuration using ADOxx Library (ABL)

 2.1 Prerequisites

 2.2 ABL library installation

     (1) Description

An application library which has been exported into an ABL file may be imported to the ADOxx development toolkit on another computer. SIMVA-SoS modeler ABL file is a library that contains all model types we developed to represent and analyze system of systems at a conceptual level.

     (2) Installation steps

To start using SIMVA-SoS modeler, you may follow the installation process as illustrated below

  1. (Get SIMVA-SoS abl file( SIMVA-SoS modeler download link )

2. Install ABL file (development toolkit)

After you log in to the development toolkit, click Libraries

Click Import migration

Click Library import

Indicate the abl file in your directory, Import and then installation completed

         3. Create user account with the SIMVA-SoS modeler abl

           -On the development toolkit, click User list

– The following dialog box displayed

– 0 Click Add

– Click Add, after filling the user name and password, and selecting the application library (SIMVA-SoS modeler v2)

       4. Login with the user credential (modeling toolkit)

       5. Start modeling with SIMVA-SoS modeler

3. Model Types

On this version, SIMVA-SoS Modeler provides six model types: task organization, domain environment, infrastructure, integration, CS capability, and goal decomposition model. Each model type is briefly described and its metamodel are presented as follow.

We use the following example case to demonstrate the various SIMVA-SoS model types. Collaborative Research Development (CRDS) SoS is a system where individual systems with different capabilities collaborate to develop a research and jointly work to publish a scientific paper. We consider each individual system as a system that has certain capabilities that cannot be handled by any other individual system. In addition, without the engagement of each individual system, the higher level goal (publish research paper) cannot be achieved. The collaboration is a directed type SoS because all individual systems are managed and controlled centrally. They also have a designated goal.

3.1 SoS Goal decomposition model

  • Description

The purpose of goal decomposition model is to capture requirements by decomposing goals into subgoals. A goal, as we use it in system-of-systems, describes the reasons for fusing (bring together) constituent systems’ contributions for shared purpose. Constituent systems have their own goals. Their goals may or may not align (designed to) with SoS goal, but their capabilities contribute to shared purpose, while they strive to complete their own goals. From this perspective, goal decomposition model helps (SoS level) requirements/goal engineers to graphically represent the desired application domain, and analyze concepts related to goal such as task, rules and resources.

  • Metamodel

  • Example model

3.2 SoS Task Organization model

  • Description

Task organization model is used to capture and represent organization related information. It describes roles of the organization, relates the roles with required capabilities and tasks, and identifies responsible constituent systems that takes in charge of the roles. Contract is part of the model. It is used to represent agreements that binds constituent systems and the organization for the common goal.  Requirement engineers and architects, domain experts, and business process experts can utilize task organization model to represent the organization and make analysis about organization related information in the analysis phase.

  • Metamodel

 

  • Example model

3.3 SoS Domain Enviroment Model

  • Description

The purpose of domain environment model type is to model the environment where the system under consideration exists in. The model helps to analyze the system by looking into environment components that can affect, or can be affected by the system operations. It provides ways to represent environment data, resource, and a corresponding measuring units. The model provides ways to capture and represent domain related information. Requirement engineers and domain engineers can utilize the model to elaborate the environment the system operates in.

  • Metamodel

 

  • Example model

 

3.4 CS capability model

  • Description

CS Capability model is used to model constituent systems focusing on the capabilities they possessed, which they can contribute to the system of systems arrangement. As constituent systems are constructing units of the system of systems, their capabilities are building blocks to the services and functionalities of system of systems. The capability model helps to capture and represent constituent systems’ action, knowledge, goal, capability, resource, and decision making mechanism. Requirement and goal engineers can utilize the model to capture and represent constituent systems capability related information, and further make analysis to put components into perspective relating with other model types.

  • Metamodel

  • Example model

3.5 SoS Infrastructure model

  • Description

SoS Infrastructure model type is used to capture and represent infrastructure related information including services, systems, resources, and communication channels. Infrastructure, broadly speaking, embodies system of systems, and provides utilities for the system to operate.  This model type can also be used to capture and represent protocols to mediate interaction between system of systems, and within a system of system.

  • Metamodel

 

 

  • Example model

3.6 SoS Integration model

  • Description

SoS Integration model type is used to capture and represent concepts related to component model types that comprise system of systems.  We have defined four model types that comprise system of systems: goal decomposition model, task organization model, infrastructure model, and domain environment model. The integration model type views system of systems as a combination of these model types. The model types are driven by the target problem, and certain stakeholder define and own the system. Integration model type provides a higher level conceptual view of the system in terms of other model types.

  • Metamodel

  • Example model