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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLSoftware Architect’s ResponsibilitiesSoftware Architect’s Responsibilities• TheSoftwareArchitectleads andcoordinatestechnicalactivitiesand artifacts.ArchitectAnalysis ModelDesign ModelDeployment ModelReferenceArchitectureSoftwareArchitectureDocumentMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 14The software architect role leads and coordinates technical activities and artifactsthroughout the project. The software architect establishes the overall structure foreach architectural view: the decomposition of the view, the grouping of elements,and the interfaces between these major groupings. Therefore, in contrast to the otherroles, the software architect's view is one of breadth as opposed to one of depth.In summary, the software architect must be well-rounded and possess maturity,vision, and a depth of experience that allows for grasping issues quickly and makingeducated, critical judgment in the absence of complete information. Morespecifically, the software architect, or members of the architecture team, mustcombine these skills:• Experience in both the problem domain, through a thorough understanding ofthe requirements, and the software engineering domain. If there is a team, thesequalities can be spread among the team members, but at least one softwarearchitect must provide the global vision for the project.• Leadership in order to drive the technical effort across the various teams, and tomake critical decisions under pressure and make those decisions stick. To beeffective, the software architect and the project manager must work closelytogether, with the software architect leading the technical issues and the projectmanager leading the administrative issues. The software architect must have theauthority to make technical decisions.• Communication to earn trust, to persuade, to motivate, and to mentor. Thesoftware architect cannot lead by decree — only by the consent of the rest of theproject. In order to be effective, the software architect must earn the respect ofthe project team, the project manager, the customer, and the user community, aswell as the management team.• Goal orientation and being proactive with a relentless focus on results. Thesoftware architect is the technical driving force behind the project, not a visionaryor dreamer. The career of a successful software architect is a long series of suboptimaldecisions made in uncertainty and under pressure. Only those who canfocus on doing what needs to be done are successful in this environment of theproject.4 - 14
Module 4 - Analysis and Design OverviewDesigner’s ResponsibilitiesDesigner’s Responsibilities• The designermust knowuse-casemodelingtechniques,systemrequirements,and softwaredesigntechniques.Use-CaseRealizationPackage/SubsystemDesignerClassMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 15The designer role defines the responsibilities, operations, attributes, and relationshipsof one or several classes, and determines how they are adjusted to theimplementation environment. In addition, the designer role may have responsibilityfor one or more design packages, or design subsystems, including any classes ownedby the packages or subsystems.The designer must have a solid working knowledge of:• Use-case modeling techniques• System requirements• Software design techniques, including object-oriented Analysis and Designtechniques, and the Unified Modeling Language• Technologies with which the system will be implementedIn addition, the designer must:• Understand the architecture of the system, as represented in the SoftwareArchitecture Document.4 - 15
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: DEV475 Mastering Object-Oriented An
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?