Packages and Namespaces - Package Stereotypes - Package and Models

13 important questions on Packages and Namespaces - Package Stereotypes - Package and Models

Packages are the primary organizing and .....  for UML Models.

Packages are the primary organizing and CM structure for UML Models.

UML tools often cooperate with standard CM tools to ...?

  • allow check-in
  • check-out
  • change management
  • compare
  • baseline
  • and restore on Package boundaries.

When projects are new and subject to many changes, Packages tend to be ...?

small, because if you have to check out a Package to start editing, you do not want to lock out other modelers from doing any work.
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart

On the other hand, when maintenance work is causing changes that tend to ripple through multiple Packages.... Then what?

, small Packages with repeated check-outs, and check-ins will cause delay to the working process

Some projects will change their Package structure as the project evolves, but it is best to ...?

pick Packages properly sized to capture closely related Elements so typical changes would only affect one Package.

One of the common stereotypes of Package allows the modeler to show that we are splitting the model by organizing principles.

How do we do this?

The stereotype is «model» which indicates that the contents of the Package are intended to be a complete version of your system based on a modeling aspect.

If you remember our discussion at the end of Chapter 2, What is UML?, we talked about different types of a modeling.

Which one and how does this relate with packages?

Such as :
  • conceptualization
  • requirements
  • analysis
  • analysis, and design.

If you have a Package whose totality of contents follows one of these aspects, you would flag the Package with the stereotype of «model».

How do we connect the seperate <<models>> ?

Depending on the methodology, the separate «models» may be connected by a chain of dependencies.

There are special types of dependencies that often are, but are not required to be used in these circumstances.

What is an abstraction?

An abstraction relates two NamedElements that represent the same concept at different levels of abstraction or from different viewpoints.

What are the types of abstractions?

Any of the abstractions in Table 8.3 can be associated with a string that explains how the mapping works.

What is the abstraction type <<trace>> ?

A generic relationship between different versions. May be bi-directional

What is an optional notation for the stereotype <<model>> ?

The optionally have a triangle adornment Δ in the upper right to indicate their model status.

Models may have a viewpoint field that uses a string to document the organizing principle or perspective for that model, see Fig.

Many modelers make their top-level Packages (the ones not contained by other things) into «models».

However, this is not required and would prevent models from being contained in other Packages or models (as shown in Fig. 8.20).

As with most use of models, the project methodology will determine your practice.

The question on the page originate from the summary of the following study material:

  • A unique study and practice tool
  • Never study anything twice again
  • Get the grades you hope for
  • 100% sure, 100% understanding
Remember faster, study better. Scientifically proven.
Trustpilot Logo