DOWNLOAD
Use Case Template
Version 1.20
Instructions for removing the ‘Hints, Guidelines and Examples’ from this document
After you have completed the Use Case document, you may want to remove the hints and guidelines provided in the document.
To remove the hints: (This procedure applies to Microsoft Word XP and higher)
1. Click on any text formatted as Hint.
2. Then, click the right mouse button.
3. A pop-up menu will appear, choose ‘Select text with similar formatting’
4. All Hint text will now be selected in the document.
5. Ensure that none of the text that you have entered is in the selection.
6. Press the Delete key to remove the Hints , Guidelines and examples..
Revision History
|
Date |
Author |
Description of change |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use Case Template. Copyright (c) 2004-2005 TechnoSolutions Corporation
(Learn more about “TopTeam for Use Cases” at www.technosolutions.com)
Permission is hereby granted, free of charge, to any person obtaining a copy of this document and its associated documentation, to use the document on their projects for any commercial or non-commercial purpose. However you may not publish, distribute, sublicense, and/or sell copies of this document.
THE DOCUMENT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DOCUMENT OR THE USE OR OTHER DEALINGS IN THE DOCUMENT. TECHNOSOLUTIONS CORPORATION MAKES NO REPRESENTATIONS ABOUT THE SUITABILITY OF THIS DOCUMENT FOR ANY PURPOSE.
Use Case:
e.g. Withdraw Cash, Register Customer, Rent Video, Calculate Sales Tax, etc.>
Id: UC-
Description
e.g. Customer brings selected video(s) to the sales counter for the purpose of renting them. Store clerk processes the rental payment, records the rented video(s) against customer’s account, and hands over the video(s) to the customer.>
Level:
Summary, User Goal, Sub-Function, Low Level>
Primary Actor
e.g. Store Clerk>
Supporting Actors
e.g. Customer, Store Manager>
Stakeholders and Interests
e.g. In a Use Case ‘Generate Salary Stub’, the entity Internal Revenue Service(IRS) has no direct interaction, however, it sure has interest in ensuring that the proper tax deduction has been made from the employee’s salary. This can be written as follows:
Internal Revenue Service – Has interest in ensuring that the tax deduction is made from each employee’s salary as per the tax table.>
Pre-Conditions
< List the system state/conditions which must be true before this Use Case can be executed.
e.g. Store Clerk must be logged in to system.>
Post Conditions
Success end condition
e.g. Video is rented to the customer and customer is charged for the rental. Rental store’s inventory is updated to reflect the rented video.>
Failure end condition:
< Enter the failure end condition of the Use Case if the Primary Actor’s goal has not been achieved.
e.g. Customer is unable to rent the video. Rental Store’s video inventory remains unchanged.>
Minimal Guarantee
< The guarantee or assurance that this Use Case provides to all Actors and Stakeholders to protect their interest regardless of whether the Use Case ends with success or failure.
e.g. For Withdraw Cash (ATM Use Case), minimal guarantee could be, Customer is logged out of the ATM system.
This minimum guarantee ensures that the system will ensure that no unauthorized withdrawals can be made from the ATM thus protecting the interest of the Bank Customer as well as the Bank’s stakeholders. >
Trigger
Example
For Rent Video Use Case - Customer brings the Video to the sales counter.
For Withdraw Cash Use Case - Customer inserts the bank card into the ATM machine.>
Main Success Scenario
-
-
Extensions
Example of an Extension in Rent Video Use Case:
4a. In step 4, if the customer has accumulated late returns fee greater than ten dollars
1. System will prompt for payment of the dues
2. Customer pays the dues
3. Store clerk adds the amount to the total
4. Use Case resumes on step 4.
>
Variations
e.g.
3’. In step 3, instead of reading Video Id using a bar code scanner, the store clerk may enter it directly using the keyboard.>
Frequency:
< How often will this Use Case be executed. This information is primarily useful for designers.
e.g. enter values such as 50 per hour, 200 per day, once a week, once a year, etc.>
Assumptions
e.g. For Withdraw Cash Use Case(ATM system) an assumption could be:
The Bank Customer understands either English or Spanish language.>
Special Requirements
Performance
1. The ATM shall dispense cash within 15 seconds of user request.
User Interface
1. The ATM shall display all options and messages in English and Spanish languages.
2. The height of letters displayed on the display console shall not be smaller than 0.5 inches. (Reference - Americans with Disabilities Act, Document xxx, para xxx).
Security
1. The system shall display the letters of PIN numbers in a masked format when they are entered by the customer.
i.e. Mask the PIN with characters such as ****. Rationale – This is to ensure that a bystander will not be able to read the PIN being entered by the customer.
2. The ATM system will allow user to Cancel the transaction at any point and eject the ATM card within 3 seconds. Rationale – In case the customer in duress/in fear of own security he/she needs to quickly get away.
3. The ATM system shall not print the customer’s account number on the receipt of the transaction.
>
Issues
-
Example
1.What is the maximum size of the PIN that a use can have? >
To do
-
Example
1. Obtain the sales tax table for computation of tax on video rentals from user.
2. Need to ensure that we have covered all parties under the ‘Stakeholders and Interests’ heading. >