Harnessing rCOS for Tool Support—The CoCoME Experience - Formal Methods and Hybrid Real-Time Systems - page 107

ApplicationWorkspace

isResponsibleFor

Analysis Modeler

dependsOn

*

<<dependsOnReleasedModels>>

*

isResponsibleFor *

1

Component

1

<<dependsOnReleasedModels>>

worksIn

isModeled

Construction Programmer

* releasesModels 1

Shared Pool

<<dependsOnReleasedComponents>>

1..3

+released

* *

UserWorkspace

Model

* mayRelease *

elementImplementedIn *

produces *

AnalysisModel

uses * 1

Model Manager

CommonPool

manages

produces *

DesignModel

releasesComponents

*

* *

ReleasedComponent

ImplementationModel

*

*

assembles

Element

Design Modeler

+methodBody Construction Manager

Diagram GUIElement

...

Class Code

Fig. 16. MasterCraft: class diagram of process-oriented concepts

4.1 Concepts in MasterCraft

MasterCraft introduces a body of concepts and a hierarchy of artifact reposito-
ries, designed to support team collaboration on development of the models and
code. Fig. 16 shows the relations among these concepts as a class diagram. At
the top-level of component repositories is the application workspace ,representing
the whole modelling and development space of an application. The application
workspace is further partitioned into components . Different from conventional
component-based software development (CBSD) focusing on architecture, Mas-
terCraft is oriented towards organizing the development activities in the indi-
vidual components. Nevertheless, a component is characterized by its interface
(consisting however only of the component's provided operations) and its depen-
dencies on other components.
As analysis and design models are created in the individual components of
the application workspace, stable versions of these models can be released into
the shared pool . This allows developers of other components, depending on the
components already released, to use stable versions of the models. In order to
preserve consistency, once the model has been released, it is “frozen” and any
subsequent change starts a new modelling cycle; this is also reflected by a change
in the version identifier of the new model.
The models in MasterCraft are created as instances of a metamodel based
on UML. Besides the modelling constructs already available in UML, Master-
Craft introduces a few technology-oriented concepts, such as database queries
(eventually translated into classes), and also several concepts for modelling the