You are on page 1of 3

USE CASES: A Use Case is a set of scenarios that describing an interaction between a user a nd a system.

Every use Case derived from SRS Document. BUsiness Analyst in an organization prepares the use case diagrams. This defines how use the functionality in terms of the application requirment.Th is usecase also defines the actors, task flow, preconditions, post conditions of one functionality. Use Cases are used in almost every project. They are helpful in exposing the req uirements and planning of the project. Most of the use cases are defined in the initial stages of the project.

Use Case Diagram: or task flow diagram Important Components are, actors : user, system Usecases: task flow connections: ________

USE CASE TEMPLATE: Use Case Id (Identifier): Use Case Name: Use Case Objective: Entry Conditions / Pre Conditions: Success End Conditions / Post Conditions: Fail End Conditions: Actors: Task Flow Diagram / Use Case Diagram: Main Scenario: Extension / Alternate Path:

EXAMPLE: USE CASE DOCUMENT FOR ATM SYSTEM:

Use Case Id (Identifier): UC_001 Use Case Name: Deposit Money Use Case Objective: To deposit the money in the ATM System Entry Conditions / Pre Conditions: ATM SYStem should be "ON" Mode / customer s elects the Deposit button Success End Conditions / Post Conditions: Customer gets the deposit slip Fail End Conditions: Customer selects the cancel Button Actors: Customer, ATM System Task Flow Diagram / Use Case Diagram: Main Scenario: 1. Customer press "Deposit' Button 2. System prompts the account number 3. customer enters the 10/14/16 digit Account nUmber and press the 'confirm / En ter' button 4. System will validate the account number 5. System will open the drawer. 6. Sytems pops up a message "Please put the money in the drawer 7. Customer puts the money in the drawer. 8. System closes the drawer and counts the money in the drawer 9. system will display the amount and ask for confirmation. 10. customer confirms the amount by pressing the 'confirm' button 11. System pops up a message "Do you want a receipt for the transaction" 12. Customer confirms 'Yes' or "No" 13. If 'Yes' System will issue the deposit slip 14. Customer gets the slip Extension / Alternate Path: 1. If the system cannot find the account number. then go back to step 2 with the message 'Invalid Account Number, Please Try Again'. 2. Customer presses the cancel button. the drawer is opened ad request the custo mer to take the money. Assignment: "Withdrawal" functionality of the ATM System.

Next Session: Software Testing TEchniques: White box testing Techniques & Blac k Box Testing Techniques

You might also like