UML Weekend Crash Course™ - To Parent Directory

Answers to Part Reviews 327
It maps the logical need to the physical capability to ensure that the application
can in fact work properly.
30. The node is labeled with a name and a type in the format “name : type.” But actually
both elements are optional, although exercising that option doesn’t make
your diagram very descriptive.
Sunday Afternoon Review Answers
1. The Deployment diagrams illustrate the hardware and the connections that make
communication possible between the devices (nodes). Use Component diagrams
more frequently to show how mixed technologies work together in the Web
application.
2. The Sequence or Collaboration diagrams are ideal for showing how Web components
work together to complete a process.
3. The Activity diagram is used to model any logic process, whether it is business workflow,
business transactions, computations, or communication. When the objects that
will take responsibility for the process have been identified, the Activity diagram
can be translated to a set of Sequence and/or Collaboration diagrams.
4. The Statechart diagram models the condition of the object at different points in
time and the events or stimuli that cause the changes that redefine the condition
of the object (its state).
5. No, it is not redundant. Component diagrams show a big-picture view of the architectural
solution, whereas Class diagrams show a more detailed view of that solution.
Deployment diagrams contribute a network view of the solution. Sequence
diagrams show the process for how all the classes and components work together
to complete the process. Thus, it is often useful to use all four diagrams together.
6. Use the Sequence and Collaboration diagrams to show how objects in the system
interact to complete a process. Many non-OO technologies may be viewed as
objects for the sake of these diagrams.
7. The Deployment diagram is particularly useful in Web systems, because Web applications
are usually distributed over multiple machines. The Deployment diagram
models how the software is distributed across the various pieces of hardware.
8. You may use Statechart diagrams to show how objects change over time and why.
This would work well for modeling how the user’s session state changes and how
the behavior of the application changes along with it.
9. A Web application is a business process much like any other. Any place in the
development process where you need to model a logic sequence of behaviors and
decisions, the Activity diagram may be applied to help bring greater precision and
visibility to the effort.
10. Sure. Although the rules are less formally enforced in HTML, HTML documents
have a hierarchical structure of tags just like XML. You could make a Class diagram
that represents each tag as a class.
11. The pattern is the Model/View/Controller pattern. The model represents the information
resources. The view represents the presentation portion. The controller