ISOM221+Lecture+11+-+Object-Oriented+Modeling+I+_Initial+Use+Case+Model_

ISOM221+Lecture+11+-+Object-Oriented+Modeling+I+_Initial+Use+Case+Model_

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
ISOM221 Information Systems Analysis and Design Lecture 11: Object-Oriented Modeling I (Initial Use Case Model) 1 Agenda Key steps for initial use case modeling 1. Identify actors 2. Create a context diagram 3 Identify use cases* 3. 4. Create initial use case descriptions* 5. Create an initial use case diagram* *they will be covered today 2
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Levels of Use Cases Initial Use Case Include only Base Use Case Provide a Elaborated Use Case Add alternative and general use case descriptions complete description of the normal set of primary interactions (flows of events) conditional flows of events, if any Develop extended and included use cases, if appropriate 3 What are Use Cases again? Use cases are scenarios for understanding system requirements The use case model describes the uses of the system and shows the major function and and shows the major functions and courses of events that can be performed 4
Background image of page 2
Process of Developing Use Cases Identify major use cases Prepare use case descripGons Identify the major steps within each use case Identify elements within step Identify elements within steps Cycle through the above steps iteraGvely and document use case descriptions Initial use case descriptions Base use case descriptions Elaborated use case descriptions 5 Identifying Use Cases List all goals for all primary actors (e.g., obtain a loan, obtain banking services) Identify business events that will accomplish these goals (e.g., apply for a loan, withdraw cash) Each business event or goal that yields observable Each business event or goal that yields observable value to a primary actor maps to a use case Actor specification cards are useful for this ±oals are not always fulfilled by the system (e.g. ATM has no cash) Use cases need to model “sunny day” and “rainy day” scenarios 6
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
“Initial ” Use Cases More on base and elaborated use cases later Prepare a list of all use cases based on the actor goals identified in all Actor Specification cards Not all use cases need to be identified at this stage; more use cases will probably be discovered during the elaboration phase For each Use Case, fill in a use case form
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 18

ISOM221+Lecture+11+-+Object-Oriented+Modeling+I+_Initial+Use+Case+Model_

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online