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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWaterfall Development CharacteristicsWaterfall Development CharacteristicsWaterfall ProcessRequirementsanalysisDesignCode and unit testSubsystem integrationSystem test• Delays confirmation ofcritical risk resolution• Measures progress byassessing workproducts that are poorpredictors of time-tocompletion• Delays and aggregatesintegration and testing• Precludes earlydeployment• Frequently results inmajor unplannediterationsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved8Waterfall development is conceptually straightforward because it produces a singledeliverable. The fundamental problem of this approach is that it pushes risk forwardin time, when it is costly to undo mistakes from earlier phases. An initial design maybe flawed with respect to its key requirements, and late discovery of design defectsmay result in costly overruns and/or project cancellation. The waterfall approachtends to mask the real risks to a project until it is too late to do anything meaningfulabout them.1 - 8
Module 1 - Best Practices of Software EngineeringIterative Development Produces an ExecutableIterative Development Produces an ExecutableRequirementsAnalysis & DesignInitialPlanningPlanningManagementEnvironmentImplementationTestEvaluationEach iterationresults in anexecutable releaseDeploymentMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved9The earliest iterations address the greatest risks. Each iteration includes integrationand testing and produces an executable release. Iterations help:• Resolve major risks before making large investments.• Enable early user feedback.• Make testing and integration continuous.• Focus project short-term objective milestones.• Make possible deployment of partial implementations.Iterative processes were developed in response to these waterfall characteristics. Withan iterative process, the waterfall steps are applied iteratively. Instead of developingthe whole system in lock step, an increment (for example, a subset of systemfunctionality) is selected and developed, then another increment, and so on. Theselection of the first increment to be developed is based on risk, with the highestpriority risks first. To address the selected risk(s), choose a subset of use cases.Develop the minimal set of use cases that will allow objective verification (that is,through a set of executable tests) of the risks that you have chosen. Then select thenext increment to address the next-highest risk, and so on. Thus you apply thewaterfall approach within each iteration, and the system evolves incrementally.1 - 9
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 76 and 77:
DEV475 Mastering Object-Oriented An
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:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
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?