Using model components with Java

What are model components?

Model components are independent, identified and coherent parts of a larger model, packaged into a single file.

Model components can contain the following:

· stable model extracts

· tagged value and note types specific to certain MDACs

· external files

Sometimes referred to as RAM components (reusable autonomous model components), model components are used in a teamwork context, to allow different developers or development teams working on the same project to work only on a limited part of the complete project model.

In a large scale multi-user development project, with several people working together at the same time and in the same workspace, it can be challenging, not to say difficult, to efficiently manage all the interactions that take place.

Model components allow you to increase your efficiency, by reducing the size of the different model extracts involved in a project, and the number of people working on any given model part. This means that each development team can progress in its own teamwork environment and according to its own schedule, without affecting the work of the other project participants.

For more information, please see "Introducing model components" in the Objecteering UML Modeler User Guide.

Creating a model component

A model component manage one or more packages. When creating a model component, the Objecteering Java Developer MDAC can request the addition of certain information. The jar file corresponding to the manifested package can be added to the model component, and if the "Add sources files to model components" parameter is active, source files are also added.

Deploying a model component

When you deploy a model component in a database, the model appears in your project, and you can make links to the model. Jar files deployed by this model component are also deployed and automatically taken into account as part of your classpath for compilation and reverse.