The rCOS modeler is structured around different Eclipse plugins. These plugins can be split into the following categories:
- modelling: extend the EMF/UML modelling capabilities of Eclipse
- programming: non-GUI Java implementations, parser
- GUI extensions: graphical UML modeler
Edges in the diagram show dependencies, names are abbreviations of the project names in Eclipse. A class corresponds to a project, and the packages group related projects. Most of the projects bring JUnit tests to test and illustrate basic functionality, plus processing the "official" models from the CoCoME case study. A separate project (not listed in the diagram) imports all tests on the case study-models and runs them as a JUnit suite.

Modelling
- mm.resources: rCOS UML profile, helpers for importing/creating UML or rCOS models (mnemonic: "mm" = "metamodel"), AST-model (EMF/UML + generated Java) for method bodies
- csp.model: EMF metamodel + generated Java of the abstract syntax tree for the fragment of CSP we use
Programming
- spec.antlr: rCOS parser, for .rcosp-files into UML models and method designs.
- csp.{stated,seqd}: translators from UML models to CSP
- transformation: implementation of the expert pattern based on ANTLR
GUI extensions
- Modeler: graphical UML modeler, based on TOPCASED
- CSP runner: launcher for FDR2 if available on the platform you're running (i.e. no Windows)
Generators
- testing.robustness: Robustness testing
- codegen.java: Java code generation