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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLAnalysis and Design WorkflowAnalysis and Design Workflow[EarlyElaborationIteration][InceptionIteration (Optional)]AnalysisDefine a CandidateArchitecturePerformArchitecturalSynthesisAnalyze BehaviorDesignRefine theArchitectureDefineComponents(Optional)Design theDatabaseMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 12A mere enumeration of all workers, activities, and artifacts does not constitute aprocess. We need a way to describe the activities, some valuable result, andinteractions between workers. A workflow is a sequence of activities that produces aresult of observable value.In UML terms, a workflow can be expressed as a sequence diagram, a collaborationdiagram, or an activity diagram. We use a form of activity diagram in the RationalUnified Process. For each core workflow, an activity diagram is presented. Thisdiagram shows the workflow, expressed in terms of workflow details.This slide shows the Analysis and Design workflow. The early Elaboration Phasefocuses on creating an initial architecture for the system (Define a CandidateArchitecture) to provide a starting point for the main analysis work. If the architecturealready exists (because it was produced in previous iterations, or projects, or isobtained from an application framework), the focus of the work changes to refiningthe architecture (Refine the Architecture) analyzing behavior, and creating an initialset of elements that provide the appropriate behavior (Analyze Behavior).After the initial elements are identified, they are further refined. Design Componentsand Design Real-Time Components produce a set of components that provide theappropriate behavior to satisfy the requirements on the system. In parallel with theseactivities, persistence issues are handled in Design the Database. The result is aninitial set of components that are further refined in the Implementation Discipline.4 - 12
Module 4 - Analysis and Design OverviewAnalysis and Design Activity OverviewAnalysis and Design Activity OverviewArchitectDesignerMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 13Remember, for Analysis and Design, we start out with the Use-Case Model and thesupplementary specifications from the Requirements Discipline and end up with theDesign Model that serves as an abstraction of the source code.The design activities are centered around the notion of architecture. The productionand validation of this architecture are the main focal points of early design iterations.The architecture is an important vehicle not only for developing a good DesignModel, but also for increasing the quality of any model built during systemdevelopment.The focus of this course is on the activities of the designer. The architect activities arediscussed, but many of the architectural decisions will be given. Each of the architectand designer activities will be addressed in individual course modules.4 - 13
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: DEV475 Mastering Object-Oriented An
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?