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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWhy Use Analysis Mechanisms?Why Use Analysis Mechanisms?Oh no! I found a group of classes thathas persistent data. How am Isupposed to design these things if Idon’t even know what database we aregoing to be using?That is why we have a persistenceanalysis mechanism. We don’tknow enough yet, so we canbookmark it and come back to itlater.Analysis mechanisms are used during analysis to reduce the complexity ofanalysis and to improve its consistency by providing designers with ashorthand representation for complex behavior.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 22An analysis mechanism represents a pattern that constitutes a common solution to acommon problem. These mechanisms may show patterns of structure, patterns ofbehavior, or both. They are used during analysis to reduce the complexity of theanalysis, and to improve its consistency by providing designers with a shorthandrepresentation for complex behavior. Analysis mechanisms are primarily used as“placeholders” for complex technology in the middle and lower layers of thearchitecture. When mechanisms are used as “placeholders” in the architecture, thearchitecting effort is less likely to become distracted by the details of mechanismbehavior.Mechanisms allow the analysis effort to focus on translating the functionalrequirements into software concepts without bogging down in the specification ofrelatively complex behavior needed to support the functionality but which is notcentral to it. Analysis mechanisms often result from the instantiation of one or morearchitectural or analysis patterns.Persistence provides an example of analysis mechanisms. A persistent object is onethat logically exists beyond the scope of the program that created it. The need tohave object lifetimes that span use cases, process lifetimes, or system shutdown andstartup, defines the need for object persistence. Persistence is a particularly complexmechanism. During analysis we do not want to be distracted by the details of how weare going to achieve persistence. This gives rise to a “persistence” analysis mechanismthat allows us to speak of persistent objects and capture the requirements we willhave on the persistence mechanism without worrying about what exactly thepersistence mechanism will do or how it will work.Analysis mechanisms are typically, but not necessarily, unrelated to the problemdomain, but instead are "computer science" concepts. As a result, they typicallyoccupy the middle and lower layers of the architecture. They provide specificbehaviors to a domain-related class or component, or correspond to theimplementation of cooperation between classes and/or components.5 - 22
Module 5 - Architectural AnalysisSample Analysis MechanismsSample Analysis Mechanisms• Persistency• Communication (IPC and RPC)• Message routing• Distribution• Transaction management• Process control and synchronization (resourcecontention)• Information exchange, format conversion• Security• Error detection / handling / reporting• Redundancy• Legacy InterfaceMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 23Analysis mechanisms either provide specific behaviors to a domain-related class orcomponent, or they correspond to the implementation of cooperation betweenclasses and/or components.Some examples of analysis mechanisms are listed on this slide. This list is not meantto be exhaustive.Examples of communication mechanisms include inter-process communication (IPC)and inter-node communication (a.k.a. remote process communication or RPC). RPChas both a communication and a distribution aspect.Mechanisms are perhaps easier to discuss when one talks about them as “patterns”that are applied to the problem. So the inter-process communication pattern (that is,“the application is partitioned into a number of communicating processes”) interactswith the distribution pattern (that is, “the application is distributed across a number ofnodes”) to produce the RPC pattern (that is, “the application is partitioned into anumber of processes, which are distributed across a number of nodes”). This processprovides us a way to implement remote IPC.5 - 23
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: DEV475 Mastering Object-Oriented An
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?