Documente Academic
Documente Profesional
Documente Cultură
M. VINOD BABU M.Sc (comp.Sci), Mtech (IT), M.Sc engineering (S/W Engg) Sweden
Actors
Actors are the external entities that interact with the system. An actor may be:
people; computer hardware and devices; or external systems.
Actors (contd)
An actor represents a role that a user can play, but not a specific user. For example, John and Peter may be consultants, but John may also be a project manager in the company. Thus, the same person may be an instance of more than one actor, and conversely several people can play the same role of an actor.
Actors (contd)
Primary ActorAny one or thing that interacts with the system causing it to respond to business events - Something we dont have control over Secondary Actor Something or someone that responds to system requests. - Something the system uses to get its job done
Actors (contd)
Primary actors are those who use the systems main functions, deriving benefits from it directly.
Primary actors are completely outside the system and drive the system requirements. Primary actors use the system to achieve an observable user goal.
Secondary actors play a supporting role to facilitate the primary actors to achieve their goals.
Secondary actors often appear to be more inside the system than outside. Secondary actors are usually allocated many system requirements that are not derived directly from the statement of requirements. Hence, the designer can have more freedom in specifying the roles of these actors.
Actors (contd)
A bank loan officer wants to review a loan application from a customer, and part of the process involves a real-time credit rating check.Use Case Name: Review Loan Application Primary Actor: Loan Officer Secondary Actors: Credit Rating System
Generalization Actors
The fact that actors are classes means that actors can be generalized. Through the generalization process, we can identify the similarities between different actors.
Use Cases
A use case describes a sequence of actions a system performs to yield an observable result or value to a particular actor. Naming convention = verb + noun or verb + noun phrase, e.g. withdraw cash.
Example
system name
actor
use case
communication
system boundary
Use Case: Login Account Flow of Events: 1. The user inserts an ATM card. The system prompts the user to enter a password. 2. The user enters the password. The system validates the user password.
<<Include>>
Alternative flow does not return to the point at which it is inserted. <<extend>> relationship is for modeling alternative flow!
Exception flow may or may not return to a base use case flow. <<extend>> relationship is not for modeling exceptions.
Flow or Scenario
Template
Use Case Name: Scenario: Triggering Event: Brief Description: Checkout Movies Checkout movies at counter Customer brings movies to checkout counter When customer brings movies to counter, clerk checks membership ID, clerk scans in each movie identifier, takes payment, and notifies customer of return due date and time.
Video clerk Add new member Clerk, Store manager Movie titles must exist Movie copy must exist Customer must exist (or Add new member must be invoked)
Postconditions:
Video Rental and rental line items must be created Payment transaction must be created Status of movie copy must be updated Video Rental must be connected to customer family member
Summary
Concrete Use Case/Base Use Case Abstract Use Case Include Extend Generalization Flow/Scenario (Main, Alternative, Exceptional)