Configure DANSE Tool-Net environment

Description

This solution method is listed last because it is normally used only once, while other solution methods are used repeatedly. However, this solution method is usually performed first. Its purpose is to provide the infrastructure that allows the other solution methods to proceed. In this solution method, each of the DANSE tools is loaded and configured to operate properly in a total Tool-Net environment.

Initial Situation

This solution method begins when the SoS architect desires to start implementing the DANSE methodology using the DANSE tools. The description below assumes that the architect has an available computer of sufficient capacity, but that none of the DANSE tools are yet loaded into the environment.

Expected Result

At the end of this solution method, the architect will have available the appropriate tools to perform the DANSE methodology, including all the other solution methods in this chapter.

Required Tools

This solution method requires and implements all the DANSE tools listed in section 2.2.3.

Activities

Figure 59 shows the sequence of activities to configure the DANSE Tool-Net environment.

Figure 59. Activity Diagram: Configure DANSE Tool-Net Environment

Load Rhapsody

IBM Rhapsody is a key program in the DANSE Tool-Net environment, providing the capability to create SoS models in either SysML or UPDM. It is also the host for several plug-ins and profiles that are essential to the DANSE solution methods. Obtain Rhapsody from IBM with the appropriate licenses, and follow IBM instructions to load Rhapsody into the computer.

Load Rhapsody Plug-Ins and Profiles

DANSE relies on a series of Rhapsody plug-ins and profiles, including the following:

  • Architecture Patterns
  • Architecture Optimization Workbench
  • Architecture Generation
  • DANSE Modelling Extension Profiles
  • GCSL Editor (with GROOVE graph grammar tool)
  • Rhapsody SysML FMU exporter

All of these are required for full use of the DANSE methodology. Obtain the source files for each and load them into the computer environment as Rhapsody plug-ins or profiles.

Load System Architect (optional)

System Architect is an alternate IBM tool that supports SysML modelling but not UPDM. SysML exports may be part of joint simulation. System Architect may be used to create and execute standalone simulations on SysML diagrams, providing additional modelling capability. Its use is optional. If desired, obtain the source files for System Architect from IBM and load it in accordance with IBM instructions.

Load constituent system modelling tools

The specific CS modelling tools required for any DANSE Tool-Net depends on the SoS and its CS designers. Joint simulation implies that there are CS models, and that those models may be in tools other than Rhapsody or System Architect. The DANSE project has successfully used versions of Modelica and Simulink. Modelica with System Modeler is specifically supported by the DANSE SMC. If Simulink is used, then the user should also load the Dymola Simulink FMU Export tool. Other modelling tools may be configured for use with the DANSE Tool-Net by using the SMC configuration tools noted below. Obtain the appropriate CS modelling tools from their respective vendors, and load them in accordance with instructions.

Load Tool-Net semantic mediation container (SMC) platform

The Tool-Net SMC is based on IBM Jazz. To provide the underlying infrastructure of connection among the DANSE tools, obtain Jazz and the SMC from IBM and load in accordance with IBM instructions.

Load SMC configuration tools (optional)

There are three SMC configuration tools that may be useful for “power” users:

  • Protégé ontology editor – allows the power user to define and modify the ontology that drives the semantic mediation among tools. Use of this tool can allow the user to connect other modelling tools into the Tool-Net by defining the semantics of their interactions.
  • MDWorkbench – allows the power user to create and modify rules for UPDM models mediation among Rhapsody, other UPDM, NAF, and other similar architecture frameworks. Use of this tool can define interfaces among various architecture framework modelling tools.
  • SMC client software development kit (SDK) – allows the software developer to create clients for the SMC Tool-Net for use by other tools. This tool is primarily intended for tool vendors, to allow their connection into the Tool-Net.

These tools are not required to perform the DANSE methodology for an SoS, but can extend the methodology to other applications for users that do not normally operate in the Rhapsy/Jazz/SMC environment. Select, obtain, and load these tools as desired per their instructions.

Load DESYRE

DESYRE is the engine for the DANSE joint simulation, taking inputs from the Tool-Net environment and integrating multiple simulation definitions into a single joint simulation environment. DESYRE also normally integrates the operation of PLASMA within the DANSE environment. Obtain source files for DESYRE from ALES and load per instructions. (Note that DESYRE is currently a research-oriented tool and is not yet available as a commercial purchase.)

Load PLASMA

PLASMA is the statistical model checking tool, that examines the results from DESYRE to determine compliance with goals, contracts, and other requirements. PLASMA can operate standalone, but works best in the DANSE environment when operated through DESYRE. Obtain source files for PLASMA from INRIA and load per instructions.

Load simulation analysis tools (optional)

There are three additional tools that provide specific analysis capabilities on the joint simulations from DESYRE:

  • TestCast test generator – allows the creation of test cases to guide the joint simulation configuration.
  • Synthesis for diagnosis and prognosis – operates as a plug-in to DESYRE to interpret GCSL into executable monitors that become part of the simulation trace configuration. (This analysis tool is required to perform GCSL checking in the statistical model checking.)
  • RTANA timing analysis – allows the verification of timing parameters within the joint simulation.

All three of these tools are still being evaluated by the DANSE project. At the time of this document, TestCast and RTANA should be treated as optional. Obtain source files for these tools if desired and load per instructions.

Limitations

The DANSE Tool-Net environment is a research environment. As such, the smooth integration of tools is not guaranteed. The Tool-Net SMC provides the appropriate mediation where it has been tested, but most of the DANSE tools are still being evaluated.

Follow-up Solution Methods

This solution method creates the infrastructure to allow the use of all other solution methods. It is likely that the next solution method to be used would be Model SoS.

Home About Technical Approach Configure DANSE Tool-Net environment