软件需求课件刘艳霞课件2 chap 3-inception.ppt

Complete checklists are provided in the online Rational Unified Process. A normal system has 20 to 50 use cases. A very large system has no more than 100 use cases. The number of use cases is more a measure of the complexity of the interaction between the system and actors. A big, but simple, system may have a few use cases, but a small system (that may be complex to build) may have lots of use cases. The number of use cases a project may initially identify may be large (because they are doing functional decomposition) The idea of fewer use cases helps to push them towards the real usage of use cases - thinking of functionality rather than algorithms when doing functional requirements analysis. Note: These checkpoints really only apply to concrete use cases, not use cases that extend other use cases or are used by other use cases, but use-case uses and extends were not covered in this course for scoping reasons. Have the students review each of the artifacts and note any questions, comments, and/or concerns. Then discuss the comments as a group. During the artifact discussion, I recommend that you display the Use-case model main diagram from the Payroll System Rose model, and then walk through with the students to make sure that they understand the system they will be working with in the exercises throughout the course. Some students may question why Printer is included as an actor. See the Instructor Best Practices document for a discussion of the rationale. Have the students review each of the artifacts and note any questions, comments, and/or concerns. Then discuss the comments as a group. During the artifact discussion, I recommend that you display the Use-case model main diagram from the Payroll System Rose model, and then walk through with the students to make sure that they understand the system they will be working with in the exercises throughout the course. Some students may question why Printer is included as an actor. See the Instructor B