Project dependency
Project dependency enables you to reference to an another project, and use its model elements in developing our own project. You can organize our model elements in a more disciplined approach by having one Visual Paradigm project per library project. This also helps to "slim up" projects by breaking down a project one into smaller pieces. Other than this, you can reference to other projects, and create an overview project for them.
Adding dependent projects
To reference to another project:
- Right-click on the background of any of the following panes and select Manage Dependent Project... from the popup menu.
- Diagram Navigator
- Model Explorer
- Class Repository
- Logical View
- ORM
To manage dependent project - In the Manage Dependent Projects dialog box, click Add.
- In the Open dialog box, choose the Visual Paradigm project file (*.vpp) to reference to and click Open.
NOTE: You can only reference to a project that was saved under the same version of VP-UML you are opening. For example, if you are running VP-UML 7.1, you can only reference to a project saved by version 7.1 of VP-UML. - Click Close.
Using model elements in dependent projects
Once a project dependency has been established, you can develop your model using model elements in dependent project. To do this:
- In Model Explorer, click on the drop down menu at the top of the pane and select the project that contains the model elements you want to use.
Selecting a dependent project NOTE: By selecting the first selection (Current), model elements in the current project will be listed. - In the model element list, select the model element you want to use. Press and drop to diagram. This create views from them.
Forming class diagram from model elements in dependent project NOTE: Alternatively, you can right-click on the model elements and select Create View in Active Diagram from the popup menu. - Continue modeling with the referenced elements.
Modeling with model elements in dependent project NOTE: Views for dependent project are read-only (i.e. non edit-able).
Mirroring model element
Due to views of dependent model elements are read-only, you cannot add shapes in it. This may be a problem when you want to use dependent packages in your project, and to add model elements such as classes in it. To overcome this problem, you can create a mirror of container-typed dependent model element. By mirroring, a dependent element is localized partially by keeping a mirrored copy in your project which echos the element in dependent project. The mirrored copy can be accessed in Model Explorer that lists model elements in current project, but not editable.
To create a mirror from a container-typed dependent model element (e.g. package, business pools/lanes...), right click on the element in Model Explorer and select Create Mirror Model Element from popup menu. By doing so, you can use it in your project, and add shapes in it. If you have already created a view for a non-mirrored element and you want to create a mirror, you can also right click on the shape and select Convert to Mirror from popup menu.
 |
| Mirror a dependent package |
| 3. Organizing diagrams by model explorer | Table of Contents | 5. Maintaining Backups |
