Package Relationships

I l @ ve RuBoard

Package relationships are also added to the model. The type of relationship is a dependency relationship, shown as a dashed arrow to the dependent package, as shown in Figure 6-10. If package A is dependent on package B this implies that one or more classes in package A initiates communication with one or more public classes in package B. Package A is referred to as the Client package and package B is referred to as the Supplier package. Package relationships are also discovered by examining the scenarios and class relationships for the system under development. As this is an iterative process, the relationships will change as analysis and design progresses.

Figure 6-10. Package Relationships


Package Relationships in the ESU Course Registration Problem

In the Add a Course Offering scenario, the AddACourseOffering class sends a message to the ProfessorCourseManager class. This implies that there is a relationship between the Interfaces package and the UniversityArtifacts package. At this time, we have not discovered any relationships to the People package.


  1. Select the dependency relationship icon from the toolbar.

  2. Click on the client package and drag the arrow to the supplier package.

The package relationships for the Course Registration System are shown in Figure 6-11.

Figure 6-11. Package Relationships in the ESU Course Registration System


I l @ ve RuBoard

Visual Modeling with Rational Rose 2002 and UML
Visual Modeling with Rational Rose 2002 and UML (3rd Edition)
ISBN: 0201729326
EAN: 2147483647
Year: 2002
Pages: 134

Similar book on Amazon © 2008-2017.
If you may any questions please contact us: