COSMOD-RE

COSMOD-RE (sCenario- and gOal-based System development MethOD) supports the intertwined co-development of requirements and architectural artefacts for software-intensive embedded systems at multiple layers of abstraction. The method is the result of several industry collaborations, in which we have investigated the interaction between requirements engineering and architectural design.

The COSMOD-RE method consists of three main building blocks:

  • The four COSMOD-RE abstraction layers
  • The four COSMOD-RE artefact types
  • The tree COSMOD-RE co-development processes

Abstraction Layers

The COSMOD-RE method is based on a hierarchy of four abstraction layers:

  • the system layer
  • the functional decomposition layer
  • the hardware/software partitioning layer
  • the deployment layer

Each abstraction layer has a well-defined focus and defines a specific viewpoint on the system. At each abstraction layer, requirements and architectural artefacts are defined.

Artefact Types

COSMOD-RE differentiates, at each abstraction layer, four basic types of artefacts:

  • Goals
  • Scenarios
  • Solution-oriented requirements
  • Architectural artefacts

Co-design Processes

COSMOD-RE provides three distinct co-design processes which structure the development process across the four abstraction layers. Each of the three co-design processes focusses mainly on two abstraction layers. For instance, the system co-design process focusses on the development of the artefacts at the system layer and the artefacts at the functional decomposition layer. In addition, each co-design process partially overlaps with another co-design-process with regard to a specific abstraction layer. The goals of the tree co-design processes can be briefly characterized as follows:

  • System-level co-design: The main goal of this co-design process is to develop the system requirements along with an initial functional decomposition of the system.
  • Function-level co-design: The scope of this co-design process is the definition of the functional component requirements and an initial hardware/software partitioning.
  • Hardware/software-level co-design: This co-design process mainly aims at defining the hardware/software requirements along with an initial deployment of the hardware/software components to the hardware/software platform.

More Information on COSMOD-RE

If you wish to learn more about the COSMOD-RE method, please refer to our Requirements Engineering textbook. Part VII thoroughly describes the whole approach.

Klaus Pohl (2010): Requirements Engineering. Fundamentals, Principles, and Techniques