3.

SOFTWARE RECQUIREMENT SPECIFICATION:

A. USE CASE SPECIFICATION:<LOGIN>

1.USE CASE NAME:LOGIN

1.1.DESCRIPTION:This feature is used to enable the user to login into bus

reservation system.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1.The user will enter the username and password.
2.If the entered details are correct then the user is allowed to access the
software.
3.Then user is allowed to create account for reservations.
2.2.ALTERNATIVE FLOW:
1.If login fails suitable retry options are available
2.An error message is displayed stating ‘invalid username or password’.
2.3.SPECIFICRECQUIREMENTS:(NON-FUNCTIONAL
RECQUIREMENTS)
The username and password should be at length of atleast 8 characters. The
password should contain special characters numbers and alphabets.
2.4.PRE CONDITION:
The user should login only using their ID and password.
2.5.POST CONDITION:
Now the software validates the entered username and password. If incorrect it
will show a error message as incorrect.
2.6.EXTENSION POINT:
Not applicable.

B.USE CASE SPECIFICATION:<CREATE ACCOUNT>

1.USE CASE NAME:CREATE ACCOUNT

1.1.DESCRIPTION: passengers can give their personnel details in this page.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1.The passenger can fill up a form to provide there details.
 2.The passenger should provide information which are compulsory in the
form.
3.Personel account is created with the corresponding details.
4.Then user is taken to check the availability of bus.
2.2.ALTERNATIVE FLOW:
1.If any compulsory information are not filled a pop message will appear on
the screen.
2.The user should fill up the left area.
3.And now an account is created with the provided details and takes to next
page.
2.3.SPECIFIC RECQUIREMENTS:
Not applicable
2.4.PRE CONDITION:
The provided details should be true and valid.
2.5.POST CONDITION:
The submitted details will be saved and a success message is displayed in a
popup dialogue box.
2.6.EXTENSION POINT:
Once the personal account is created it goes to check the bus and other
facilities.

C.USE CASE SPECIFICATION:<CHECK BUS SEATS>

1.USE CASE NAME:CHECK BUS SEATS

1.1.DESCRIPTION: Bus seats and cost of bus are available in this page.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1.The passenger can give the date and check with the bus seats available.
2.the passenger can also check with their respective classes.
3.the passenger can check the cost of bus seats.
4.they can check with their needed extra facilities.
5.Then user can confirm their booking in the next page.
2.2.ALTERNATIVE FLOW:
1.An error message is displayed if there is no bus in the provided date.
2.And shows other options available.
 2.3.SPECIFIC RECQUIREMENTS:(NON-FUNCTIONAL RECQUIRMENTS)
Provide a valid date.
2.4.PRE CONDITION:
The bus detail for which the availability is viewed has to be already present
in the database.
2.5.POST CONDITION:
if any option is unsuccessful then suitable retry options are available.
2.6.EXTENSION POINT:
After choosing the suitable bus they can confirm their booking in next page.

D. USE CASE SPECIFICATION:<BOOK TICKETS>

1.USE CASE NAME: BOOK TICKETS

1.1.DESCRIPTION: This feature is to confirm reservation of tickets.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1. The passenger can enter the start and destination place.
2. The passenger can also provide the date and time of bus.
3. The passenger can also select the number of respective seats wanted.
3. Now the availability is checked and booking can be confirmed.
4. If user have any inconveniences they can cancel their ticket in next page.
2.2.ALTERNATIVE FLOW:
1. If booking fails suitable retry options are available.
2. And an error message is displayed stating ‘booking is not confirmed’.
2.3.SPECIFIC RECQUIREMENTS:(UI RECQUIREMENTS)
The input details should be valid.
2.4.PRE CONDITION:
Review of the booking ticket is shown to the passenger before booking is
confirmed and then the ticket is booked.
2.5.POST CONDITION:
An error message is displayed if the ticket is not booked.
2.6.EXTENSION POINT:
Booking is confirmed and proceed to make payment.

E. USE CASE SPECIFICATION:<MAKE PAYMENT>

1.USE CASE NAME:MAKE PAYMENT
 1.1.DESCRIPTION: This feature is used to make payment for bus reservation.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1.Many payment methods are shown to the passenger to make their payment.
2.Passenger should give the bank details for the respective payment method.
3.An OTP pin is send through the phone number or Email id to confirm the
payment.
4.And the payment is validated with the bank.
4.The payment is made after the verification and validation.
2.2.ALTERNATIVE FLOW:
1.If verification or validation fails suitable retry options are available.
2.And an error message is displayed stating 'Payment cancelled'.
2.3.SPECIFIC RECQUIREMENTS:(UI RECQUIREMENTS)
Provided payment details should be valid.
2.4.PRE CONDITION:
Payment should be make with correct details. A message is sent to the email
after payment is done and a report is generated.
2.5.POST CONDITION:
Now the software validates the entered details to make payment. If incorrect
it will show a error message as incorrect.
2.6.EXTENSION POINT:
Not applicable.

F. USE CASE SPECIFICATION:<CANCELLATION OF TICKET>

1.USE CASE NAME:CANCELLATION OF TICKET

1.1.DESCRIPTION:This feature is used for cancellation of ticket.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1.The booking is cancelled by the passenger .
2.The corresponding reason for cancellation is asked to the passenger.
3.And the reason of cancellation is send to the admin.
2.2.ALTERNATIVE FLOW:
1.The cancellation is confirmed.
2.the feedback is also fetched from the passenger.
3.The money is refunded to the passenger.
 2.3.SPECIFIC RECQUIREMENTS:(UI RECQUIREMENTS)
The ticket details for cancellation should be given correctly.
2.4.PRE CONDITION:
The passenger should enter a valid feedback to cancel the ticket.
2.5.POST CONDITION:
Now the software validates the entered details and feedback. The ticket is
cancelled.
2.6.EXTENSION POINT:
Not applicable.

G. USE CASE SPECIFICATION:<GENERATE REPORT>

1.USE CASE NAME:GENERATE REPORT

1.1.DESCRIPTION: This use case is used for process of generating report.

2.FLOW OF EVENTS:

2.1.BASIC FLOW:
1.Name of the bus, date and time has to be entered by the employee.
2.The report is generated and displayed.
2.2.ALTERNATIVE FLOW:
1.If task fails suitable retry options are available.
2.And an error message is displayed stating 'report generation failed'.
2.3.SPECIFIC RECQUIREMENTS:
The input details should be valid.
2.4.PRE CONDITION:
The available number of seats and booking details after reservation has to be
updated in the database for the bus.
2.5.POST CONDITION:
Now the software validates if successful, generated report is displayed. Error
message and suitable retry options are provided if generation of report fails.
2.6.EXTENSION POINT:
Not applicable.