Soft Card Software Requirement Specification Author Name ID Hanan Naseeb Khan F2021065158 Idrees F2021065200 Turab Rasool F2021065159 Abdullah F2021065148 1. Introduction 1.1 Purpose of the Document This document provides a description of the interfaces, key concepts, and overall purpose of the software project, “Soft Card”. This documents helps you to understand the product ability to fulfill a task, and quickly search and find a particular section within the document, or find resolution when encountered using the product. 1.2 Scope of the project Soft Card offering an easier and quicker way of buying, renewing and using tickets at the convenience of the passenger 2. General Description Apply for card online by selecting its category according to your requirement. Once ordered online, you will receive your card swiftly through the post or some other method like from the station within working days you will receive your card and then you activated your card by entering the specific information. 2.1 User Characteristics To use this software there is no need of Computer Knowledge and any other type of knowledge like language. 2.2 Domain Overview 2.2.1 Access the card Login to your account and apply for card then you book your ticket. First checked your balance and then you get the ticket. 2.2.2 Card Functionalities Once you can book your ticket you card is active one time swap your card on barrier and you enter on the vehicle and then you card is inactive you cannot use it again for entering purpose to doing this you have to book more than one ticket. 2.2.3 Booking ticket Process User have to search first bus route in which they have to see the bus timing and bus routes then checked the availability of the seats and set the destination. First checked your balance and the payment of the ticket is done from your soft card account. In case of cancellation there is specific time to cancel it and money goes back to user account. For any type of issue report your issue there is a legal action on your report. 3. Specific Requirement In this section all software requirement will be explain some information of the user. All requirement are divided into the two main part one is Functional R Requirement and other is Non-Functional Requirement. 3.1 Functional Requirement No Requirements Description FR1 Apply for Card Customer can Apply for Card online. The following information will be needed: FR2 Add Card Category Name ID Card Email Customer can select the card category of card : FR3 Load Card FR4 Search bus route Golden card is valid for an year and get 20% discount on every ticket Silver card is valid for 30 days and get 10% discount on every ticket Customer can add balance to his card by using credit card detail. You can also add balance physically. This Balance can be used while booking a ticket. Customer can search bus routes. FR5 Set Destination Customer will be asked to select following: Departure station Destination FR6 Available Seats Customer can check available seats in Bus. FR7 Book Tickets Ticket will be reserved for customer after checking following: FR8 Give incentive Current Balance The following customers can get discount: Regular user for 3 months using soft card can get a bonus ticket to any route Click on payment button. Payment will be deducted from account balance. Your bus will arrive within specific time at your departure station FR9 Payment FR10 Notification FR11 Travel history Customer can check the Travel history. FR12 Edit schedule Admin can change the followings: FR13 Cancel Ticket Route Schedule Customer can cancel the ticket by giving following reasons: FR14 Report Issue FR15 Sharing Location FR16 Change Setting Personal issue Bad current situations Change in bus time Customer can report any issue regard of: Staff Driver Passengers Customer can share location with anyone. To whom you share location can track bus. You can change the following details: Personal information Credit card detail Account settings 3.2 Non Functional Requirement: No Requirement Description NFR 1 Security Sensitive information not leaked to any unauthorized parties like account balance or any information or also damaged the personal information. To access the system you first need to be logged for admin and user. To do any type of change in system admin can access only. There is only authorized and authentic person can logged the system. There is different security system for user and admin for specific purpose. Another thing is in case of any issue the admin can access your system. NFR 2 Availability Software will available for 24/7 hours. A system is responsive to request. A user may always access her account for balance quires and booking the ticket. Denials of services attacks attempt to compromise availability by any type of error or cutting off the network services. The server will also inform the user about the error. NFR 3 Usability The functionalities is perceived to the user in efficient way, for instance how easy it must be to learn and how efficient it must be for carrying out user tasks. Like booking the ticket, cancel the ticket and some other tasks. And the system also must be the user interface. NFR 4 Performance The software how they have to work speedily like searching for some result. They can provide a quick result of any type (Bus route) search. The system will be able to handle the multiple request by increasing the server. In case of increasing the user the software have to be work properly. NFR 5 Reliability This system is must be fully error free. They have a great ratio of doing work without error. The system will be perform the specified functionalities without failure.
