ppt课件-anintroductiontoobject-orientedsystemsanalysisand.pptVIP

An Introduction toObject-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004Stephen R. Schachsrs@vuse.vanderbilt.edu CHAPTER 5 — Unit C THE REQUIREMENTS WORKFLOW II Continued from Unit 5C Refining the Revised Requirements: MSG Rechecking the revised requirements uncovers two new problems A use case has been partially duplicated Two of the use cases need to be reorganized Partially Duplicated Use Case Use case Manage a Mortgage One action is to modify a mortgage Use case Update Borrowers’ Weekly Income Its only action is to update the borrowers’ weekly income The borrowers’ weekly income is an attribute of the mortgage Use case Manage a Mortgage already includes use case Update Borrowers’ Weekly Income Accordingly, use case Update Borrowers’ Weekly Income is superfluous, and must be deleted Sixth Iteration of the Revised Use-Case Diagram The modified use case is shaded Refining the Revised Requirements: MSG This iteration resulted in a decrement, not an increment In fact, deletion occurs often Whenever we make a mistake Sometimes we can fix an incorrect artifact More frequently we have to delete an artifact Refining the Revised Requirements: MSG (contd) However, when we discover a fault, we do not have to start the whole process from scratch First we try to fix the current iteration If the mistake is too serious for this to work, we backtrack to the previous iteration, and try to find a better way to go forward from there Reorganizing Two Use Cases Determine the funds available for the current week Use case Estimate Funds Available for Week models performing the calculation Step 1.3 of use case Produce a Report models printing out the result of the computation There is no point in estimating the funds available unless the results are printed out Reorganizing Two Use Cases (contd) The descriptions of the use cases Estimate Funds Available for Week, and Produce a Report have to be modified (the use cases do not