01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SESSION<br />

3<br />

How to Approach the <strong>UML</strong><br />

Session Checklist<br />

✔ Explaining the types of <strong>UML</strong> diagrams<br />

✔ Explaining the concepts of views<br />

✔ Organizing the diagrams into views by function<br />

✔ Explaining the basic Object-Oriented concepts that support modeling<br />

The <strong>UML</strong> includes specifications for nine different diagrams used to document various<br />

perspectives of a software solution from project inception to installation and maintenance.<br />

In addition, Packages provides a means to organize your work. The Component<br />

and Deployment diagrams describe an implementation. The remaining seven diagrams are<br />

used to model requirements and design. This session presents a way to organize these last<br />

seven diagrams to make them easier to remember and apply, and an overview of the principles<br />

that guide their development.<br />

Views<br />

One way to organize the <strong>UML</strong> diagrams is by using views. A view is a collection of diagrams<br />

that describe a similar aspect of the project. I very often use a set of three distinct yet<br />

complementary views that are called the Static View, Dynamic View, and Functional View.<br />

Figure 3-1 illustrates the complementary nature of the three views and the diagrams that<br />

make up each view.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!