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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWhat Are Architectural Mechanisms?What Are Architectural Mechanisms?RequiredFunctionalityImplementationEnvironmentSupplementarySpecification“realized by clientclasses using”Mechanisms“constrained by”COTS ProductsDatabasesIPC Technologyetc.“responsible for”Use-Case ModelArchitectMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 20In order to better understand what an analysis mechanism is, we have to understandwhat an architectural mechanism is.An architectural mechanism is a strategic decision regarding common standards,policies, and practices. It is the realization of topics that should be standardized on aproject. Everyone on the project should utilize these concepts in the same way, andreuse the same mechanisms to perform the operations.An architectural mechanism represents a common solution to a frequentlyencountered problem. It may be patterns of structure, patterns of behavior, or both.Architectural mechanisms are an important part of the "glue" between the requiredfunctionality of the system and how this functionality is realized, given the constraintsof the implementation environment.Support for architectural mechanisms needs to be built in to the architecture.Architectural mechanisms are coordinated by the architect. The architect choosesthe mechanisms, validates them by building or integrating them, verifies that they dothe job, and then consistently imposes them upon the rest of the design of thesystem.5 - 20
Module 5 - Architectural AnalysisArchitectural Mechanisms: Three CategoriesArchitectural Mechanisms: Three Categories• Architectural Mechanism Categories• Analysis mechanisms (conceptual)• Design mechanisms (concrete)• Implementation mechanisms (actual)Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 21There are three categories of architectural mechanisms. The only difference betweenthem is one of refinement.Analysis mechanisms capture the key aspects of a solution in a way that isimplementation-independent. They either provide specific behaviors to a domainrelatedclass or component, or correspond to the implementation of cooperationbetween classes and/or components. They may be implemented as a framework.Examples include mechanisms to handle persistence, inter-process communication,error or fault handling, notification, and messaging, to name a few.Design mechanisms are more concrete. They assume some details of theimplementation environment, but are not tied to a specific implementation (as is animplementation mechanism).Implementation mechanisms specify the exact implementation of the mechanism.Implementation mechanisms are are bound to a certain technology, implementationlanguage, vendor, or other factor.In a design mechanism, some specific technology is chosen (for example, RDBMS vs.ODBMS), whereas in an implementation mechanism, a VERY specific technology ischosen (for example, Oracle vs. SYBASE).The overall strategy for the implementation of analysis mechanisms must be built intothe architecture. This will be discussed in more detail in Identify Design mechanisms,when design and implementation mechanisms are discussed.5 - 21
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: DEV475 Mastering Object-Oriented An
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?