ISOM221+Lecture+12+-+Object-Oriented+Modeling+II+_Base+Use+Case+Model_

ISOM221+Lecture+12+-+Object-Oriented+Modeling+II+_Base+Use+Case+Model_

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

View Full Document Right Arrow Icon
ISOM221 Information Systems Analysis and Design Lecture 12: Object-Oriented Modeling II (Base Use Case Model) 1 Agenda Interim report for the project Base use case descriptions 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
Interim Report: Overview The interim report should cover at least till Iteration 1 Prepare your interim report according to the Team Project Report Template The more you include in your interim report, the more useful detailed comments will be provided for your future efforts The key purpose of the interim report is to give early comments on your project, rather than evaluating your work 3 Interim Report: Contents Your interim report will be evaluated based on the key artifacts from Iteration 1 as follows a well defined system concept an initial list of actors and brief actor specification cards an initial context diagram an initial list of use cases a complete set of initial use case descriptions Due Oct. 29 (moved from Oct 22) Both hardcopy and softcopy are acceptable 4
Background image of page 2
Team Project Size – Number of Use Cases Your team project should identify and document about 6 to 8 key business events that will trigger use cases i.e., Your use case model for the project should i.e., Your use case model for the project should have about 6 to 8 base use cases 5 Two Use Case Modeling Extremes System Scope = Use Case Scope Individual Use Case Scope is too Small Do Everything Actor1 Actor2 UseCase1 UseCase2 UseCase3 UseCase4 UseCase5 UseCase6 UseCase7 UseCase8 UseCase9 UseCase10 UseCase11 UseCase13 UseCase14 UseCase15 UseCase16 UseCase17 UseCase18 Actor1 Actor2 Actor3 Actor4 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
More Remarks on Actors and Use Cases (1) Any number of actors may be participating in a use case It is recommended to start with primary actors when developing use cases A use case exists to provide value to at least one actor (i.e., a primary actor) Secondary actors provide service in the use case and would not exist if there were no primary actor 7 More Remarks on Actors and Use Cases (2) An initiator can request a service or otherwise trigger the event A use case should be initiated by an actor (i.e., an initiator) Sometimes a use case is triggered by the need of an entity that may not actually physically interact with the system (e.g., a customer and a cashier at McDonald) An initiator may or may not be a primary actor; however, in many cases, the initiator of a use case is the actor that receives some value from the system (i.e., primary actor) 8
Background image of page 4
More Remarks on Actors and Use Cases (3) An external server is almost always a secondary actor When a primary actor needs to access service performed by the system but does not always interact with the system directly, a facilitator carry out the interaction for the primary actor An actor can have multiple personalities within a use case and across multiple use cases 9 More Remarks on Actors and Use Cases (4) Actor types and personalities can be used to
Background image of page 5

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

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 20

ISOM221+Lecture+12+-+Object-Oriented+Modeling+II+_Base+Use+Case+Model_

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

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