UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 3—How to Approach the UML 33 Encapsulation of an object requires you to hide: The implementation that provides the behavior requested through the interface The data within the object that provides the structure that supports its behavior, and tracks the condition of the object, its state, at any given point in time REVIEW The UML includes specifications for nine different diagrams used to document different perspectives of a software solution from project inception to installation and maintenance. Packages provide a means to organize your work. The Component and Deployment diagrams are specific to implementation. The remaining seven diagrams are used to model requirements and the design. Views provide a means of organizing these seven UML diagrams by their features and applications, thus making it easier to identify the right tool for the right job. The Functional View employs the Use Case and Activity diagrams to describe the behavior of the system. The Static View includes the Class and Object diagrams to define all the resources of the system. The Dynamic View includes the Sequence and Collaboration diagrams, also known as interaction diagrams, to define how objects work together to respond to the environment, and the Statechart diagram, which describes how and why an object changes over time. An object is an abstraction, a representation of something in the real world. An object can describe its own structure and its current state. An object knows what it can do and what can be done to it. Encapsulation defines a way to organize an object definition (a class). QUIZ YOURSELF 1. Why is the Static View called static (See “Static View.”) 2. Describe the purpose of the Class diagram. (See “Static View.”) 3. What diagrams are used to represent the Dynamic View (See “Dynamic View.”) 4. What is illustrated in the Sequence diagram (See “Dynamic View.”) 5. How can using multiple views help you (See “Three views.”) 6. What is an abstraction (See “Abstraction.”) 7. What does it mean to encapsulate an object (See “Encapsulation.”)
- Page 6 and 7: About the Author Tom Pender is the
- Page 8: With thanks to Lynne Angeloro for h
- Page 11 and 12: x Preface To get the most out of th
- Page 13 and 14: xii Preface Features First, as you
- Page 15 and 16: Part VI—Sunday Afternoon ........
- Page 17 and 18: xvi Contents Encapsulation ........
- Page 19 and 20: xviii Contents Modeling the Class C
- Page 21 and 22: xx Contents Session 22-Modeling the
- Page 24: UML Weekend Crash Course
- Page 27 and 28: PART I Friday Evening Session 1 Wha
- Page 29 and 30: 6 Friday Evening The UML is a stand
- Page 31 and 32: 8 Friday Evening will find three pa
- Page 33 and 34: 10 Friday Evening The Continuing Re
- Page 36 and 37: SESSION 2 UML and Development Metho
- Page 38 and 39: Session 2—UML and Development Met
- Page 40 and 41: Session 2—UML and Development Met
- Page 42 and 43: Session 2—UML and Development Met
- Page 44 and 45: Session 2—UML and Development Met
- Page 46 and 47: SESSION 3 How to Approach the UML S
- Page 48 and 49: Session 3—How to Approach the UML
- Page 50 and 51: Session 3—How to Approach the UML
- Page 52 and 53: Session 3—How to Approach the UML
- Page 54 and 55: Session 3—How to Approach the UML
- Page 58 and 59: SESSION 4 Defining Requirements for
- Page 60 and 61: Session 4—Defining Requirements f
- Page 62 and 63: Session 4—Defining Requirements f
- Page 64 and 65: Session 4—Defining Requirements f
- Page 66 and 67: Session 4—Defining Requirements f
- Page 68: PART # I Friday Evening Part Review
- Page 71 and 72: PART II Saturday Morning Session 5
- Page 73 and 74: 50 Saturday Morning System Name Ass
- Page 75 and 76: 52 Saturday Morning Use Case scenar
- Page 77 and 78: 54 Saturday Morning In Use Case dia
- Page 79 and 80: 56 Saturday Morning Association not
- Page 81 and 82: 58 Saturday Morning Customer Withdr
- Page 84 and 85: SESSION 6 Building the Use Case Dia
- Page 86 and 87: Session 6—Building the Use Case D
- Page 88 and 89: Session 6—Building the Use Case D
- Page 90 and 91: Session 6—Building the Use Case D
- Page 92 and 93: SESSION 7 Building the Use Case Nar
- Page 94 and 95: Session 7—Building the Use Case N
- Page 96 and 97: Session 7—Building the Use Case N
- Page 98 and 99: Session 7—Building the Use Case N
- Page 100 and 101: Session 7—Building the Use Case N
- Page 102: Session 7—Building the Use Case N
- Page 105 and 106: 82 Saturday Morning a way that the
Session 3—How to Approach the <strong>UML</strong> 33<br />
Encapsulation of an object requires you to hide:<br />
The implementation that provides the behavior requested through the interface<br />
The data within the object that provides the structure that supports its behavior,<br />
and tracks the condition of the object, its state, at any given point in time<br />
REVIEW<br />
The <strong>UML</strong> includes specifications for nine different diagrams used to document different<br />
perspectives of a software solution from project inception to installation and maintenance.<br />
Packages provide a means to organize your work. The Component and Deployment diagrams<br />
are specific to implementation. The remaining seven diagrams are used to model requirements<br />
and the design. Views provide a means of organizing these seven <strong>UML</strong> diagrams by their features<br />
and applications, thus making it easier to identify the right tool for the right job.<br />
The Functional View employs the Use Case and Activity diagrams to describe the<br />
behavior of the system.<br />
The Static View includes the Class and Object diagrams to define all the resources of<br />
the system.<br />
The Dynamic View includes the Sequence and Collaboration diagrams, also known as<br />
interaction diagrams, to define how objects work together to respond to the environment,<br />
and the Statechart diagram, which describes how and why an object<br />
changes over time.<br />
An object is an abstraction, a representation of something in the real world.<br />
An object can describe its own structure and its current state.<br />
An object knows what it can do and what can be done to it.<br />
Encapsulation defines a way to organize an object definition (a class).<br />
QUIZ YOURSELF<br />
1. Why is the Static View called static (See “Static View.”)<br />
2. Describe the purpose of the Class diagram. (See “Static View.”)<br />
3. What diagrams are used to represent the Dynamic View (See “Dynamic View.”)<br />
4. What is illustrated in the Sequence diagram (See “Dynamic View.”)<br />
5. How can using multiple views help you (See “Three views.”)<br />
6. What is an abstraction (See “Abstraction.”)<br />
7. What does it mean to encapsulate an object (See “Encapsulation.”)