5. OOA -1.pptVIP

* Each use case has a web of flow of events with a scenario being an instance of a particular flow of events. The scenario may involve the basic flow and any number of alternative flows in any number of combinations. How many scenarios are needed? As many as needs to understand the system being developed. You must elaborate the scenarios of the interesting and high-risk use cases. Scenarios can be used to understand, as well as to validate, the use-case flows of events. Some people write scenarios first and extract use cases, while others find use cases first and validate those use cases by writing scenarios. Scenarios make excellent test cases. * * * * Scenarios A scenario is an instance of a use case. It is one flow through a use case. How many scenarios are needed? Scenarios make excellent test cases. Zhang Shuang, zhangs@ Software College, Zhang Shuang, Zhangs914@163.com Normal Scenario Software College, Zhang Shuang, Zhangs914@163.com Exception Scenario Practice OOA: get use case diagram for your case. Zhang Shuang, zhangs@ * * * We can see from the diagram of Object-Oriented Life Cycle, which we have learned previously, that OOA should follow Requirements phase. In the chapter of “requirements phase”, we have learned that the objective of the requirements phase is to determine what software the client needs. Then, the objective of the following phase “OOA” is to distinguish the domain issues, including actors, use cases, classes, their attributes and actions, and also the relationships among them, which will be the basis for OOD. * * * Now, let’s study the first step: use-case modeling. Surely you will ask what a use case model is actually? A use-case model describes a system’s functional requirements in terms of use cases. The use-case model is a model of the system’s environment----actors, and its intended functions----use cases. The product of use-case modeling is use case diagram. * * As we see jut now that in use case model, actor is represented as