UML Weekend Crash Course™ - To Parent Directory

Preface
xi
Part I: Friday Evening
In this part, I provide the background of the UML and how you can approach it to get the
most out of it. I cover a brief history of the UML and what exactly the UML defines. Next,
I briefly cover some sample methodologies to explain the context in which you will use the
UML. I also cover an overview of the diagrams supported by the UML and the fundamental
object-oriented concepts used throughout the development of those diagrams.
When the background is complete, you will dive into the Case Study to gather requirements.
Part II: Saturday Morning
This part covers the application of the Use Case Model, from the diagram through narratives
and scenarios to fully document user requirements. You will learn to identify and define Use
Cases in terms that can be verified by your clients. You will explain the requirements of
each Use Case so that they form the foundation for testing throughout the project. Then,
based on the requirements, you will begin the construction of the Class diagram, including
classes and associations.
Part III: Saturday Afternoon
In the afternoon session, you will learn the rest of the Class diagram notation and apply it
to the case study. You will refine the Class diagram by applying aggregation, composition,
and inheritance. You will then test the Class diagram using the Object diagram, applying
test cases to validate your Class diagram notation. You will also learn to use the Activity
diagram to model logic, such as business processes and complex system behaviors. Then you
start modeling the interactions between objects using the Sequence diagram by bringing
together the test cases and the resources defined in your Class diagram.
Part IV: Saturday Evening
You will continue your application of the Sequence diagram. Then you will learn another,
complementary tool, the Collaboration diagram, to model object interactions. You will learn
the unique properties of these diagrams and how they can work together to reveal holes in
your design. For those objects that are constantly changing, you will learn the Statechart
diagram so that you can fully understand and document their behavior over time.
Part V: Sunday Morning
The application of the Statechart will continue into Sunday Morning with lots of practical
examples. By this time you will have seen a lot of diagrams. You will learn how to organize
your work using Package diagrams. Then, when the design is reaching the point where you
need to build the system, you will learn how to model the physical implementation using
the Component and Deployment diagrams.
Part VI: Sunday Afternoon
Sunday Afternoon you will learn how the UML diagrams are applied to the development of a
Web application. Finally, I will provide some information about modeling tools, including
evaluation criteria and sources to obtain evaluation copies.