Use Case modeling is used to diagrammatically depict a system and those people or processes that interact with it. This system can be a business system (a process) or an application system (computer or web based). To understand the scope of the system under consideration a system boundary is used. Anything depicted within the system boundary is part of the system under consideration, while anything outside of it is not. Use cases are then used to define a group of user-system interactions that together deliver value to the user of the system. These users are called actors.
Primary Actor: The primary actor of a use case is the stakeholder that calls on the system to deliver one of its services. It has a goal with respect to the system – one that can be satisfied by its operation. The primary actor is often, but not always, the actor who triggers the use case.
Secondary Actors: Actors that the system needs assistance from to achieve the primary actor’s goal.
Finally, the Oracle Unified Method (OUM) concurs with the UML definition of Actors, along with Cockburn’s refinement, but OUM also includes the following:
Secondary actors may or may not have goals that they expect to be satisfied by the use case, the primary actor always has a goal, and the use case exists to satisfy the primary actor.
Example:
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