Overview
The following steps are performed in this tool mentor:
Additional Tool Information
Look for existing subsystems or components that offer similar interfaces. Some assets may have been packaged for
intentional reuse using the Reusable Asset Specification (RAS). If created within the tool, such assets can be
browsed and loaded. See Packaging Assets for Reuse in the online Help.
For assets that do not include an RSA model, it may be useful to reverse engineer a model to better understand the
design. Some of these components could be discovered using the code visualization and the pattern/anti-pattern
detection capabilities which are part of the support for Architectural Analysis. If the asset proves to be usable, the
diagrams will be the base for building or generating new model elements and the asset might qualify as a RAS candidate.
See the Architectural Discovery, Analysis and Control guidelines.
For an asset that your company controls, there may be opportunities to make minor changes to a candidate interface
which will improve its conformance to the desired interface. For assets that your company does not control, you can
create adapter or bridge design elements that map your desired interface onto interfaces provided by the assets reused.
See Identify Design Elements for guidelines on creating and modifying
interfaces and classes.
Reorganize the design elements into packages as necessary. Refer to the white paper: Model Structure Guidelines for Rational Software Architect for more guidance on
organizing the design model.
If there is a separate logical view, it needs to be maintained. See the white paper Model Structure Guidelines for Rational Software Architect.
Tutorials:
-
Apply
a Pattern
-
Create
a Pattern
-
Import a RAS Asset
-
Export a RAS Asset
Samples:
-
RAS Assets
-
Patterns
|