Identifying Use cases Identifying the use cases: Goals • The use-case approach to object-oriented analysis and the object-oriented analysis process. • Identifying actors. • Identifying use cases. • Documentation. What Is Analysis?
• Analysis is the process of transforming a
problem definition from a fuzzy set of facts and myths into a coherent statement of a system’s requirements. Analysis • The main objective of the analysis is to capture: – a complete, unambiguous, and consistent picture of the requirements of the system and – what the system must do to satisfy the users' requirements and needs. Where Should We Start?
• 1. Examination of existing system
documentation. • 2. Interviews. • 3. Questionnaire. • 4. Observation. Why analysis is a difficult activity? Three most common sources of requirements difficulties are: 1. Incomplete requirements. 2. Fuzzy descriptions 3. Unneeded features. Why analysis is difficult? Contd.. • Fuzzy and ambiguous sentences like “Fast response time”, “very easy and very secure updates”, will lead to user dissatisfaction. • Certain requirements necessary for successful system development are not included for a variety of reasons. • Forgetting to identify the requirements, politics in business, high cost are reasons for incomplete requirements. Why analysis is difficult? Contd.. • Additional features could affect the performance, complexity, stability, maintenance and support costs of an application. • Example: If the primary task is to select a single object but in the support if it is tried to select multiple options could make frequent and simple action into difficult one. • Through experience, try to reflect the errors in the incomplete understanding of the problem, refine and try another run. The Object-Oriented Analysis (OOA) Process (6 steps) The process consists of the following steps: • 1. Identify the actors: – Who is using the system? – Or, in the case of a new system, who will be using system? The OOA Process (Con’t) 2. Develop a simple business process model using UML activity diagram. • Example: The OOA Process (Con’t) 3. Develop the use case: – What the users are doing with the system? – Or, in the case of a new system, what users will be doing with the system?
Use cases provide us with comprehensive
documentation of the system under study. The OOA Process (Con’t)
• 4. Prepare interaction diagrams:
– Determine the sequence. – Develop collaboration diagrams. The OOA Process (Con’t) • 5. Classification—develop a static UML class diagram: – Identify classes. – Identify relationships. – Identify attributes. – Identify methods. The OOA Process (Con’t) • 6. Iterate and refine: If needed, repeat the preceding steps.