A frame in the
UML encapsulates a
collection of collaborating instances or refers to
another representation of such. Frames are
depicted as rectangles with a notched descriptor box in
the top left corner. Frames come in two flavors, a
diagram frame such as Batch Transcript Printing
and combined fragment frame such as the loop
frame, both in Figure 1 .
Diagram frames explicitly define the boundary of a
diagram whereas combined fragment frames encompass
portions of a diagram or provide references to other
diagrams or method definitions.
Figure 1. A
frame encompassing a sequence diagram.
Figure 2. Modeling alternate
courses of logic.
Figure 3. The
internals of the seminar component.
Frames. The Batch Transcript
Printing diagram frame of Figure 1 adds a significant amount of visual
clutter in the process.
Use Interaction Occurrences Over Part Decompositions. There are two references to
logic external to Figure 1:
the TranscriptBatch object includes a
reference to PrintRun and there is a combined
fragment referencing the SharedServices.print()
method. The style of the first reference is
called a part decomposition and the second an
Fully Specify Operation Names in References. Depict
Interface Per Port.
connection points between a classifier and its
environment which, are depicted on the side of frames
as small rectangles. Depict
One Port Per
Realizing Class. See also
UML interface style guidelines.
Frame Borders. In Figure 1
you see that the frame border is lighter than the lines
Standard Labels to Descriptors.
summarizes common labels for diagram frames and
Table 2 the common labels for
Table 1. Diagram
frame labels. Table 2. Combined
Indicates several alternatives,
only one of which will be taken, separated by
dashed lines. Used to model if and
switch statements. See the example in
Indicates that the fragment
models an assertion.
Indicates that the fragment must
be treated as atomic and cannot be interleaved
with other event occurrences. Often used within
a par frame (Douglass 2004).
Models logic which will be
potentially repeated several times.
Models optional logic depending
on the run-time evaluation of a guard.
Indicates several fragments of logic, separated
by dashed lines, all of which will run in
References another diagram or a
Share with friends:
Let Us Help
We actively work with clients around the world to improve their information technology (IT) practices,
typically in the role of mentor/coach, team lead, or trainer. A full description of what we do, and how to contact us, can be found at
Scott Ambler + Associates.
The Elements of UML 2.0 Style describes a collection
of standards, conventions, and
for creating effective
. They are based on sound, proven
software engineering principles that lead to diagrams
that are easier to understand and work with. These
conventions exist as a collection of simple, concise
guidelines that if applied consistently, represent an
important first step in increasing your productivity as
a modeler. This book is oriented towards
intermediate to advanced UML modelers, although there
are numerous examples throughout the book it would not
be a good way to learn the UML (instead, consider
The Object Primer
). The book is a brief 188
pages long and is conveniently pocket-sized so it's easy to carry around.
This book, Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise
describes the Disciplined Agile Delivery
(DAD) process decision framework.
The DAD framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and provides the foundation for
This book is particularly important for anyone who wants to understand how agile works from end-to-end within an enterprise setting.
Data professionals will find it interesting because it shows how agile modeling and agile database techniques fit into the overall solution delivery process.
Enterprise professionals will find it interesting beause it explicitly promotes the idea that disciplined agile teams should be enterprise aware and therefore work closely with enterprise teams.
Existing agile developers will find it interesting because it shows how to extend Scrum-based and Kanban-based strategies to provide a coherent, end-to-end streamlined delivery process.
The Object Primer 3rd Edition: Agile Model Driven
Development with UML 2 is an important reference book for agile modelers,
describing how to develop 35 types of agile
models including all 13
UML 2 diagrams .
Furthermore, this book describes the fundamental programming and testing techniques
for successful agile solution delivery. The book also shows how to move from your
agile models to source code, how to succeed at implementation techniques such as
test-driven development(TDD) .
The Object Primer also includes a chapter overviewing the critical database development techniques ( database refactoring ,
object/relational mapping ,
legacy analysis , and
database access coding) from my award-winning
Agile Database Techniques book.