DEV475 Mastering Object-Oriented Analysis and Design with UML ...

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLThe Anatomy of Sequence DiagramsThe Anatomy of Sequence DiagramsThis is a sample script.Client ObjectSupplier Object:Client:SupplierObject Lifeline1: PerformResponsibilityReflexive MessageMessage1.1: PerformAnotherResponsibilityFocus of ControlHierarchical MessageNumberingMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 30A Sequence diagram describes a pattern of interaction among objects, arranged in achronological order. It shows the objects participating in the interaction and themessages they send.An object is shown as a vertical dashed line called the "lifeline." The lifelinerepresents the existence of the object at a particular time. An object symbol is drawnat the head of the lifeline, and shows the name of the object and its class separatedby a colon and underlined.A message is a communication between objects that conveys information with theexpectation that activity will result. A message is shown as a horizontal solid arrowfrom the lifeline of one object to the lifeline of another object. For a reflexivemessage, the arrow starts and finishes on the same lifeline. The arrow is labeled withthe name of the message and its parameters. The arrow may also be labeled with asequence number.Focus of control represents the relative time that the flow of control is focused in anobject, thereby representing the time an object is directing messages. Focus ofcontrol is shown as narrow rectangles on object lifelines.Hierarchical numbering bases all messages on a dependent message. Thedependent message is the message whose focus of control the other messagesoriginate in. For example, message 1.1 depends on message 1.Scripts describe the flow of events textually.6 - 30
Module 6 - Use-Case AnalysisExample: Sequence DiagramExample: Sequence Diagram: Student: RegisterForCoursesForm : RegistrationController : CourseCatalogSystem : Schedule : Student : Course CatalogCreate a newschedule1: // create schedule( )2: // get course offerings( )3: // get course offerings(forSemester)4: // get course offerings( )A list of the availablecourse offerings for thissemester are displayed5: // display course offerings( )A blank scheduleis displayed for thestudents to selectofferings6: // display blank schedule( )7: // select 4 primary and 2 alternate offerings( )8: // create schedule with offerings( ) 9: // create with offerings( )10: // add schedule(Schedule)At this point, the Submit Schedule sub-flow is executed.Sequence Diagram: Register forCourses / Register for Courses - BasicFlow (Submit Schedule)Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 31The above example shows the object interactions to support the Create a Schedulesub-flow of the Register for Courses use case. Some of the rationale for responsibilityallocation is as follows:• The RegisterForCoursesForm knows what data it needs to display and how todisplay it. It does not know where to go to get it. That is one of theRegistrationController’s responsibilities.• Only the RegisterForCoursesForm interacts with the Student actor.• The RegistrationController understands how Students and Schedules are related.• Only the CourseCatalogSystem class interacts with the external legacy CourseCatalog System.• Note the inclusion of the actors. This is important as the diagram explicitlymodels what elements communicate with the “outside world.”6 - 31
Page 2 and 3:
Rational UniversityDEV475 Mastering
Page 5 and 6:
AcknowledgmentsThe development of t
Page 7 and 8:
► ► ► Module 0About This Cour
Page 9 and 10:
Module 0 - About This CourseCourse
Page 11 and 12:
Module 0 - About This CourseIntende
Page 13 and 14:
Module 0 - About This CourseRationa
Page 15 and 16:
Module 0 - About This CourseRationa
Page 18 and 19:
DEV475 Mastering Object-Oriented An
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189: DEV475 Mastering Object-Oriented An
Page 276: DEV475 Mastering Object-Oriented An
show all

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

Create successful ePaper yourself

Delete template?

Save as template?