UML Weekend Crash Course™ - To Parent Directory

328
Appendix A
represents the application logic that manipulates the model and feeds information
to the view.
12. The Component diagram shows the dependency between the Web components.
Superimposing the Component diagram on the Deployment diagram provides a
complete picture of where the software resides on the network.
13. The Class diagram supports the description of the structure of each resource as
well as their relationships and dependencies.
14. The UML allows customization through the use of stereotypes and alternative
icons. As a point of further study, you might check out the UML discussion on
profiles, complete schemas for applying the UML modeling standards to morediverse
domains like business process modeling (see UML 1.4 chapter 4 UML
Example Profiles).
15. The main features of a modeling tool interface are the main menu, which includes
the tools and diagrams selections, the browser navigation area, and the drawing
canvas.
16. Usually there are a limited number of licenses but a large number of project participants
who need to see the work products created in the tool. The HTML documentation
can be created and distributed to a larger audience. The documentation can
also be maintained to keep everyone up to date, again without tying up the tool.
17. Class diagrams are used throughout the development process. The same diagram
initially created in the early phases is continuously changed through analysis and
design and finally through implementation. Without version control, you will lose
the history of the diagrams that explains how you arrived at the current image.
18. The four types of translation between models and code are
1. Forward Engineering: A Class diagram is used to generate code that never
existed before.
2. Reverse Engineering: Code may be used to create a Class diagram that never
existed before.
Maintenance involves work in both directions:
3. Diagram updates the Code: The diagram changes so you need to regenerate
the code. Some tools replace the existing code while others are smart enough
to isolate the changes and even comment out the replaced or deleted code.
4. Code updates the Diagram: The code has changed, so you need to update the
diagram to keep in sync. This is not as easy as it sounds. Always do it in very
small increments. Also, some diagram concepts, like aggregation and composition,
are not reflected in code, so you will need to modify the diagram to
make certain that it continues to represent your model accurately.
19. Many projects require a number of people to contribute to the modeling effort.
This implies that they need to share the same models, each working on different
aspects but sharing each other’s products. Vendors have come up with a variety of
techniques to support such team development. Some require a check-out/check-in
method where one person has exclusive access to the checked out portion of the
model. Others provide diagram or even element-level locking so that many people
may have the same diagram or element open but only one person may modify the
diagram or element until they release it.