Generating code for component diagrams

About this task

The following code generation semantics apply to component diagrams:

The CG::Component::ComponentsSearchPath property specifies the name of related components, although the dependencies are checked before the property. For example, a dependency from component A to component B is equivalent to putting B in the ComponentsSearchPath property (with the obvious advantage on name change recovery).

Consider the diagrams shown in the following figure.

Classes C1 and C2 have a relation to each other (an association). The model has two components, component_1 and component_2, that each have a configuration with the same name. Component_1 has a dependency with stereotype «Usage» to component_2. Class C1 is in the scope of component_1. Class C2 is not in the scope of component_1, but is mapped to a file F1 in component_2.


Feedback