Grasp Component Usage and Trace relationships

With ARCSeeker, you can grasp components' usage and trace relationships among components.

Summary

The following image shows relationships among products and components.

You can see that:

• Product A uses Component A, Component B, Shared Component X and Shared Component Y.
• Shared Component X and Shared Component Y are also used by Product B.
• Component D is created from Component B (derived relationship means that a component is modified (updated) to other component).

By defining these relationships, you could trace products and components. For example, if Component A has an issue, you can know that Product A is affected by the issue, but Product B is not affected. If Component B has an issue, Component D (and Product B) is affected because Component D is derived component.

Not only managing the components, but also using these relationships, ARCSeeker offers more work efficiencies.

How to Make

Component can be created by Enterprise Architect's UML model. The component contains source files, build scripts, UML model (as XMI file), test items and result, various document, etc. like the following image.

For the product component, however, you need to create manually in ARCSeeker. It is convenient to store the various related files to the product component.

Then, you need to define the relationship between products and components. There are two ways to do this.

• In the relationship diagram, drag and drop between components.
• Drag target component into the Relationships tab of a component's property pane.

You need to create lots of relationships in the actual development, so we recommend to create your own Add-ins and make relationships automatically.

For your information, derived relationships are automatially added when creating components from Enterprise Architect UML model.