UML Basic Architecture Modeling--gaining a common mechanism



Sometimes you just has to color outside the lines. For example, at a job site, an architect might scribble a few notes on the building's blueprints to Comm Unicate a subtle detail to the construction workers. In a recording studio, a composer might invent a new musical notation to represent some unusual effect she wants from a gu Itarist. In both cases, there already exist well-defined languages------the language of structural blueprints and the language of M Usical notation------But sometimes you had to bend or extend those languages in controlled ways to communicate your Inten T.

Sometimes you have to color out online. For example, at the job site, a designer may casually write notes on the blueprints to communicate with construction workers in minor details. In the studio, the composer may create a new musical symbol to make the guitarist Express some of the less common effects. In these two cases, there is already a well-defined language-the language of the structural blueprint and the language of the musical notation-but sometimes you have to reduce or extend those languages in a controlled manner to convey your intentions.

Modeling is all about communication. The UML already gives all the tools are need to visualize, specify, construct, and document the artifacts of a wide RA Nge of software-intensive Systems. However, you might find circumstances in which'll want to bend or extend the UML. This happens-human languages all the time's why new dictionaries get published every year), because no static language can ever is sufficient to cover Everythin G You'll want to communicate for all time. When using a modeling language such as the UML, remember that is doing so to communicate, and that means you'll want to stick to the core language unless there's compelling reason to deviate. When you find yourself needing-to-color outside the lines, you should does so only in controlled ways. Otherwise, you'll make it impossible for anyone and understand what do you've done.

Modeling is all about communication. UML has given you all the tools to help you visualize, detail, structure and document a wide range of integrated systems. However, you may find that you would like to reduce or extend UML. This always happens in human languages (that's why new dictionaries are published every year), because there is no static language enough to cover the things you want to convey at any time. When using modeling languages like UML, remember that the communication you do means that you have to stick to the core of the language and deviate from its core unless there are compelling reasons. When you find yourself needing to be colored outside the line, you should make sure to do so in a controlled manner, otherwise you will not be able to let anyone understand what you want to do.

Notes is the mechanism provided by the UML-let's capture arbitrary comments and constraints to help illuminate t He modelsyou've created. Notes may represent artifacts that play a important role in the software development life cycle, such as requirements, or They may simply represent free-form observations, reviews, or explanations.

A note is a mechanism that UML provides you with arbitrary annotations and constraints to help you clarify the model you are creating. Notes can express products that play an important role in the software development cycle, such as requirements, and can easily express free-form data, review or explain.

The UML provides a graphical representation for comments and constraints, called a note, as Figure 6-1 shows. This notation permits visualize a comment directly. In conjunction with the proper tools, notes also give you a placeholder to link to or embed other documents.

UML provides annotations and constraints with a graphical representation of what is called a note, which is shown in 6-1. This symbol allows you to visualize an annotation directly. In conjunction with the appropriate tools, notes can also give you a link to a point character or embed other documents.

Stereotypes, tagged values, and constraints is the mechanisms provided by the UML-let you add new building blocks, Create new properties, and specify new semantics. For example, if is modeling a network, you might want to having symbols for routers and hubs; You can use the stereotyped nodes to make these things appear as primitive building blocks. Similarly, if you is part of your project'S release team, responsible for assembling, testing, and then deploying releases, you might want to keep track of the Version number and test results for each major subsystem. You can use the tagged values to add the information to your models. Finally, if you is modeling hard real time systems, you might want to adorn your models with information about time Budge TS and deadlines; You can use the constraints to capture timing requirements.

Stereotypes, tag values and constraints are the mechanisms that UML provides to you to add new building blocks, create new properties, and describe new semantics. For example, if you are modeling a network, you may want to have a symbol for routers and hubs, and you can use modal nodes to make these things appear as original building blocks. Similarly, if you are part of the project release team, the responsibility is to integrate, test and deploy the release version, you may want to track the version number and test the results for each major subsystem. You can use tag values to add information to your model. Finally, if you are modeling real-time systems, you might want to use time budgeting and throttling information to decorate your model, and you can use constraints to capture time requirements.

The UML provides a textual representation for stereotypes, tagged values, and constraints, as Figure 6-2 shows. Stereotypes also let's introduce new graphical symbols so this you can provide visual cues to your models that speak the Language of your domain and your development culture.

UML is modeled, and tag values and constraints provide a textual representation. 6-2 is displayed. Patterning also allows you to introduce new graphical symbols so that you can provide visual information for your model so that you can speak the language of your domain and use your development habits.

UML Basic Architecture Modeling--gaining a common mechanism