UML Basic Architecture Modeling--General modeling technology of General mechanism (II.)



Modeling New Properties

New Feature Modeling

the basic properties of the UML " s Building blocks-----attributes and operations for classes, the contents of packages, and so on----is Generic enough to address most of the things you " ll want to model. However, if you want to extend the properties of these basic building blocks, you need to define stereotypes and tagged VA Lues.

The basic features of the UML building blocks--class properties and operations, the contents of the package, and so on--are generally enough to solve most of the things you want to model. However, if you want to extend the features of these basic building blocks, you need to define the layout and label values.

To model new properties,

l first, Make sure there " s not already a-from-express what you want by using basic UML.

l If You ' re convinced there ' s no other-to-express these semantics, define a stereotype and add the new properties to the stereotype. The rules of generalization apply----Tagged values defined for one kind of stereotype apply to its children.

　To model the properties,

l first, make sure that you use basic UML without existing methods to express your thoughts.

l If you're sure there's no other way to express these semantics, you can define the layout and add new features to the layout. Application of generalization rules-defines a label value for a layout and applies it to its subclasses.

For example, suppose your want to tie the models you create to your project's configuration management system. Among other things, this means keeping track of the version number, current check in/check out status, and perhaps even th e creation and modification dates of each subsystem. Because This is process-specific information, it's not a basic part of the UML, although you can add this information as Tagged Values. Furthermore, this information was not just a class attribute either. A Subsystem'S version number is part of the IT meta-data, not part of the model.

For example, suppose you want to connect the model you create to your project configuration management system, which, among other things, means keeping a traceable version number ﹑ Current Login/Logout status ﹑ even the creation and modification date of each subsystem. Because this is the information for the process, it is not a basic part of UML, although you can keep this information by adding tag values. In addition, this information is not a property of a class. The version number of a subsystem is part of its metadata, not part of the model.

Figure 6-10 shows three subsystems, each of the which have been extended with the ? versioned ? stereotype to include its version number and status.

6-10 of the three subsystems shown, each with a ? version ? layout, this layout contains their version number and status.

Note:THe values of tags such asversion andStatusIs things that can is set by tools. Rather than setting these values in your model by hand, can use a development environment that integrates your Configu Ration management tools with your modeling tools to maintain these values for you.

remark: Elephant version and the Status The tag values for these things can be set by the tool. Rather than setting these values manually in your model, you might as well keep these values with a development environment that consolidates your modeling tools and configuration management tools.

UML Basic Architecture Modeling--General modeling technology of General mechanism (II.)