1. 1. Use case:It will be developed by Business Analyst based on the requirement specification.It is a detailed description of the Specification in a simplified version with realtime scenarios.Based on Use case, test cases will be written by the testers.

2.Scenario:While writing a test case for a module, you write different tests for that module say, Creating a user.There may be several ways to create a user like, creating a user thru wizard or thru uploading set of users.These are all the things we can call as a scenario. This is the literal meaning.

Test case:

What are all the steps we should follow for creating a user using a wizard andWhat are all the steps we should follow for creating a user using upload are called as test case.

User use Cases:1.Users sign up. 2.User login. 3.Search for flight. 4.Search for fare. 5 .Make Reservation. 6. Modify flight. 7.Cancel flight. 8.Select no of seats. 9.Select class. 10.Reserve flight type (1) one way (2) round trip.11. Logout. Admin use Cases:9. Admin login. 10. Add a flight. 11. Delete/cancel a flight. 12. Modify flight information 13. Modify user reservation14. Main user information 15. View user information. 6.1 Use Case Diagrams: 6.1.1 Use Case: 6.1.1 Activity Diagram:6.1.1 Sequence Diagram: 2 Functional Requirements:User:        Sign up.  Login. Search for flight. Search for fare. Select class Reserve flight type (1) one way (2) round trip. Make Reservation.       Modify flight. Cancel flight. Logout. Admin: 

1. Sign up.2.Admin login.3. Add a flight.4.Delete/cancel a flight.5. Modify flight information 6. Modify user reservation 7. Maintain user information 8. View user information

One of the necessary skills for successful system development is gathering and developing functional requirements. This

particular hub was created based on a term paper developed to fulfill the requirements of a graduate school course in System

Development; the scenario for the assignment follows:

Bank customers and credit card holders use ATM machines to perform transactions and check account balances. This

functional requirements document is based on a scenario comprising a small bank that is planning the installation of 30 ATMs

throughout the region. A description of the requirements gathering process is contained in Appendix A at the end of the paper.

Preconditions and Assumptions1. The system will only accept ATM cards from participating banks and credit card institutions.2. The system can interface with participating banks and credit card institutions.3. All 30 bank ATMs may be used simultaneously.4. Customers can only make payments to accounts linked to their ATM cards.5. The system can verify the availability of funds in an account before dispensing cash for withdrawals or cash advances.High Level Description of Functionality 1. A customer must be able to make a cash withdrawal from any suitable account linked to the card, in multiples of $20.00.  Approval must be obtained from the bank before cash is dispensed.2. A customer must be able to make a deposit to any account linked to the card, consisting of cash and/or checks in an envelope. The customer will enter the amount of the deposit into the ATM, subject to manual verification when the envelope is removed from the machine by an operator.  Approval must be obtained from the bank before physically accepting the envelope.3. A customer must be able to make a transfer of money between any two accounts linked to the card.4. A customer must be able to make a balance inquiry of any account linked to the card.(Bjork, 1998)Functional Requirements1. An ATM machine accepts a card from a user.2. The user inputs a Personal Identification Number (PIN) to authenticate the user’s identity.3. The system validates the card and the PIN, then either continues processing or rejects the card.4. The ATM prompts the validated user for the type of transaction; valid transaction types are as follows: ·        Check account balance·        Process a deposit·        Process a withdrawal for an ATM customer or a ·        Process a cash advance for a credit card holder·        Transfer funds

·        Pay bills

5. The ATM communicates the request to the appropriate financial system

6. The appropriate financial system responds with permission or denial of the request.7. The ATM asks the user if they want a printed receipt.8. The ATM acts on the request according to the response received from the financial system. Possible actions for granted requests include the following:

· reject the request· accept a deposit· dispense cash· display or print an account balance· pay a bill· perform an Electronic Funds Transfer (EFT)9. The system updates the bank’s financial system for ATM transactions or sends an EFT to the appropriate financial institution for credit card transactions.10. The ATM prints a receipt if one is requested.11. The system prompts the user for another transaction and repeats steps 4 – 10 if yes.12. The ATM closes the session and waits for another user when done.

Data Constraints1. PINs are four digits in length.2. Account numbers are contained on the cards used to gain access.3. Card readers must read embossed characters and magnetic information.4. The ATM system must format transactions in Electronic Data Interchange format for transmission to other financial institutions.5. Non-sufficient funds in an account should cause the rejection of a withdrawal request or cash advance transaction.6. ATM cards may link to more than one account.7. PINs and account numbers are issued by the appropriate financial institutions.