1111111C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi602187000000246200000013210247682462000000218700000002187000000246200000010.0000001.00000024478651220500496UML 2.0 Diagrams (cont.)1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi50170000000021870000001321024768246200000017000000002750000001700000000218700000010.0000001.00000024478651220500495UML 2.0 Diagrams1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi40123300000017000000001321024768246200000012330000007620000001233000000170000000010.0000001.00000024478651220500494Messages1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi301124000000123300000013210247682462000000112400000012290000001124000000123300000010.0000001.00000024478651220500493Representing Object Classes in the UML1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi208640000001124000000132102476824620000008640000001338000000864000000112400000010.0000001.00000024478651220500492Object Classes1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi1050000000086400000013210247682462000000500000000159800000050000000086400000010.0000001.00000024478651220500491Behavior & Encapsulation1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap10aSummary\Chap10aSummary.avi0005000000001321024768246200000001962000000050000000010.0000001.00000024478651220500490Objects & Object Instances100x000003E9Objects & Object Instances1005000000000x000003EABehavior & Encapsulation1018640000000x000003EBObject Classes10211240000000x000003ECRepresenting Object Classes in the UML10312330000000x000003EDMessages10417000000000x000003EEUML 2.0 Diagrams10521870000000x000003EFUML 2.0 Diagrams (cont.)10632000
Teaching Notes
This figure depicts the symbol for representing an object
Teaching NotesThis figure depicts the symbol for representing an object
instance using the UML modeling notation. An object is represented using a rectangle.
instance using the UML modeling notation. An object is represented using a rectangle.
The name of the object instance and its classification are underlined and appear at the
The name of the object instance and its classification are underlined and appear at the
top of the symbol. The attribute values for the object instance are optionally
top of the symbol. The attribute values for the object instance are optionally
recorded within the symbol and are separated from the object name with a line.
recorded within the symbol and are separated from the object name with a line.
The name of an object instance is the value of the attribute that uniquely identifies it.
The name of an object instance is the value of the attribute that uniquely identifies it.
The attribute customer number, whose value is 412209, uniquely identifies that instance of
The attribute customer number, whose value is 412209, uniquely identifies that instance of
customer. Thus, 412209 is the name of the object instance and customer is its
customer. Thus, 412209 is the name of the object instance and customer is its
classification.
classification.
Teaching Notes
In encapsulation, both attributes and behavior of the
Teaching NotesIn encapsulation, both attributes and behavior of the
object are packaged together. The only way to access an object's attributes is through
object are packaged together. The only way to access an object's attributes is through
that object’s behaviors. No other object may perform that object’s behavior.
that object’s behaviors. No other object may perform that object’s behavior.
Have students identify the behaviors of a door, window, or VCR.
Have students identify the behaviors of a door, window, or VCR.
Conversion Notes
This is a new slide in the seventh edition
Conversion NotesThis is a new slide in the seventh edition
Teaching Notes
In UML an object class is represented using a rectangle
Teaching NotesIn UML an object class is represented using a rectangle
symbol.
The object rectangle is divided into three portions.
symbol. The object rectangle is divided into three portions.
The top portion contains the name of the class.
The middle portion contains the
The top portion contains the name of the class. The middle portion contains the
names of the attributes.
The lower portion contains the behaviors (or methods).
names of the attributes. The lower portion contains the behaviors (or methods).
To simplify the appearance of a diagram, or to specify more details about a class, class symbols can be drawn without methods or attributes, or the attribute portion can be expanded to include data types, lengths, etc. The appearance depends on what the author of the diagram is intending to communicate.
To simplify the appearance of a diagram, or to specify more details about a class, class symbols can be drawn without
Teaching Notes
The object sending a message does not need to know how the
Teaching NotesThe object sending a message does not need to know how the
receiving object is organized internally or how the behavior is to be accomplished, only that
receiving object is organized internally or how the behavior is to be accomplished, only that
it responds to the request in a well-defined way.
A message can be sent only
it responds to the request in a well-defined way. A message can be sent only
between two objects that have an association between them.
between two objects that have an association between them.
Conversion Notes
With the seventh edition we have switched to UML 2.0.
Conversion NotesWith the seventh edition we have switched to UML 2.0.
Teaching Notes
As we study an overview of the systems analysis life cycle,
Teaching NotesAs we study an overview of the systems analysis life cycle,
three chapters will delve into the core UML diagrams:
Chapter 7 – FAST Requirements
three chapters will delve into the core UML diagrams: Chapter 7 – FAST Requirements
Analysis Phase
Use Case Diagrams
Chapter 10 – FAST Logical Design
Analysis PhaseUse Case DiagramsChapter 10 – FAST Logical Design
Phase
Activity Diagrams
System Sequence Diagrams (a
PhaseActivity DiagramsSystem Sequence Diagrams (a
high-level kind of Sequence Diagram)
Class Diagrams
high-level kind of Sequence Diagram)Class Diagrams
Chapter 18 – FAST Physical Design Phase
Sequence Diagrams
Chapter 18 – FAST Physical Design PhaseSequence Diagrams
Class Diagrams (with more detail)
State Machine Diagrams
Class Diagrams (with more detail)State Machine Diagrams
Communication Diagrams
Component Diagrams
Deployment Diagrams
Communication DiagramsComponent DiagramsDeployment Diagrams
Conversion Notes
With the seventh edition we have switched to UML 2.0.
Conversion NotesWith the seventh edition we have switched to UML 2.0.
Teaching Notes
As we study an overview of the systems analysis life cycle,
Teaching NotesAs we study an overview of the systems analysis life cycle,
three chapters will delve into the core UML diagrams:
Chapter 7 – FAST Requirements
three chapters will delve into the core UML diagrams: Chapter 7 – FAST Requirements
Analysis Phase
Use Case Diagrams
Chapter 10 – FAST Logical Design
Analysis PhaseUse Case DiagramsChapter 10 – FAST Logical Design
Phase
Activity Diagrams
System Sequence Diagrams (a
PhaseActivity DiagramsSystem Sequence Diagrams (a
high-level kind of Sequence Diagram)
Class Diagrams
high-level kind of Sequence Diagram)Class Diagrams
Chapter 18 – FAST Physical Design Phase
Sequence Diagrams
Chapter 18 – FAST Physical Design PhaseSequence Diagrams
Class Diagrams (with more detail)
State Machine Diagrams
Class Diagrams (with more detail)State Machine Diagrams
Communication Diagrams
Component Diagrams
Deployment Diagrams
Communication DiagramsComponent DiagramsDeployment Diagrams