6

	Sign In Sign-Up

6.2. Description of the methodology

This is not a compulsory step but it is very useful in large systems. To create a package diagram, we begin from a general package diagram that we identify for our system and we try to allocate use cases inside one of these packages by reading the basic and alternative descriptions of the use case. During the process we might need to create new packages or new dependency relationships between existing packages. Every step that is described in the basic and alternative flows of action should refer to a use case that is already included inside the same package. If this is not true, then we should create a dependency relationship between the two packages.

To summarise:

From the description of the problem and the use case diagram identify the packages of the system
Try to allocate each use case inside a package
If a use case of a package refers to a use case in another package create a dependency relationship among the two packages.