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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWhat Is a Design Pattern?What Is a Design Pattern?• A design pattern is a solution to a commondesign problem.• Describes a common design problem• Describes the solution to the problem• Discusses the results and trade-offs of applying thepattern• Design patterns provide the capability to reusesuccessful designs.TemplateParametersPattern NameParameterizedCollaborationStructural AspectBehavioral AspectMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 12We will look at a number of design patterns throughout this course. Thus, it isimportant to define what a design pattern is up front.Design patterns are being collected and cataloged in a number of publications andmediums.You can use design patterns to solve issues in your design without“reinventing the wheel.” You can also use design patterns to validate and verify yourcurrent approaches.Using design patterns can lead to more maintainable systems and increasedproductivity.They provide excellent examples of good design heuristics and designvocabulary. In order to use design patterns effectively, you should become familiarwith some common design patterns and the issues that they mitigate.A design pattern is modeled in the UML as a parameterized collaboration.Thus it hasa structural aspect and a behavioral aspect. The structural part is the classes whoseinstances implement the pattern, and their relationships (the static view).Thebehavioral aspect describes how the instance collaborate — usually by sendingmessages to each other — to implement the pattern (the dynamic view).A parameterized collaboration is a template for a collaboration.The TemplateParameters are used to adapt the collaboration for a specific usage.These parametersmay be bound to different sets of abstractions, depending on how they are applied inthe design.5 - 12
Module 5 - Architectural AnalysisWhat Is an Architectural Pattern?What Is an Architectural Pattern?• An architectural pattern expresses a fundamentalstructural organization schema for softwaresystems. It provides a set of predefinedsubsystems, specifies their responsibilities, andincludes rules and guidelines for organizing therelationships between them – Buschman et al,“Pattern-Oriented Software Architecture — A System ofPatterns”• Layers• Model-view-controller (M-V-C)• Pipes and filters• BlackboardMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 13Architectural Analysis is where you consider architectural patterns, as this choiceaffects the high-level organization of your object model.Layers: The layers pattern is where an application is decomposed into different levelsof abstraction. The layers range from application-specific layers at the top toimplementation/technology-specific layers on the bottom.Model-View-Controller: The MVC pattern is where an application is divided intothree partitions: The Model, which is the business rules and underlying data, theView, which is how information is displayed to the user, and the Controllers, whichprocess the user input.Pipes and Filters: In the Pipes and Filters pattern, data is processed in streams thatflow through pipes from filter to filter. Each filter is a processing step.Blackboard: The Blackboard pattern is where independent specialized applicationscollaborate to derive a solution, working on a common data structure.Architectural patterns can work together. (That is, more than one architectural patterncan be present in any one software architecture.)The architectural patterns listed above imply certain system characteristics,performance characteristics, and process and distribution architectures. Each solvescertain problems but also poses unique challenges. For this course, you willconcentrate on the Layers architectural pattern.5 - 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:
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: DEV475 Mastering Object-Oriented An
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 ...

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

Delete template?

Save as template?