Functional requirement

The functional requirements of the system describe the functionality or services that the
system is expected as provide.
1. User
ID Requirements Justification

REQ-1 Registration User will register.

To login this application user required username and
REQ-2 Login
password.
REQ-3 Check services User can check all the services.
REQ-4 Request for services User can request for any services.
REQ-5 Cancel services User can also cancel the service in given time.
REQ-6 payment After getting the service user pay the charges.
REQ-7 complains User can complain to the admin about the service.
REQ-8 Review User can also give the review about the service.
REQ-9 Rate User can rate the service
REQ-10 Change password Users can change password.

2. Admin
ID Requirements Justification

REQ-1 Register Admin will register.

To login this application Admin required username
REQ-2 Login
and password.
REQ-3 Register User Admin will register the user.
REQ-4 Register Hotels Admin will register the Hotels.
REQ-5 Register Transports Admin will register the Transports.
Admin will manage all the services that are provided
REQ-6 Manage all
by the application

3. Hotels
ID Requirements Justification

REQ-1 Register Hotels will register.

To login this application Hotels required username
REQ-2 Login
and password.
Hotel will share all the information about the
REQ-3 Hotel information
services.
Hotel will manage the rate of room according to the
REQ-4 Room types and rate
room type.
Maintain customer Hotel will maintain the record of previous
REQ-5
record customers.
REQ-6 Cancelation policy Hotel will define their service cancelation policy.
REQ-7 Check payments Hotel can check the customer is paid or unpaid.
REQ-8 Hotel updates Hotel can update about the news and events.
REQ-9 Rating Rate the application
REQ-10 Reviews Review about the application
REQ-11 Report Hotel can report the customer to admin

4. Transportation
ID Requirements Justification

REQ-1 Register Transports will register.

To login this application transports required
REQ-2 Login
username and password.
Transport will share all the information about type,
REQ-3 Transport information
schedule, and availability.
REQ-4 Seat reservation Transport will manage the seat reservation.
REQ-5 Check payments Hotel can check the customer is paid or unpaid.
REQ-6 Rating Rate the application
REQ-7 Reviews Review about the application
REQ-8 Report Transport can report the customer to admin

Non Functional Requirements

Non-functional requirements are the quality requirements that stipulate how well software
does what it has to do. These are Quality attributes of any system. These can be seen at the
execution of the system and they can also be the part of the system architecture.
2.3.1 Accuracy:
The system will be accurate and reliable based on the design architecture. If there is any
problem in the accuracy, then the system will provide alternative ways to solve the
problem.
2.3.2 Usability:
The proposed system will be simple and easy to use by the users. The users will
comfort in order to communicate with the system. The user will be provided with an easy
interface of the system.
2.3.3 Accessibility:
The system will be accessible through internet.
2.3.4 Performance:
The system performance will be at its best when performing the functionality of the
system.
2.3.5 Reliability:
The system will be reliable in all circumstances and if there is any problem that will
be affectively handle in the design.
2.3.5 Security:
The proposed system will be highly secured; every user will be required registration
to use the system. The system will do the proper authorization and authentication of the users
based on their types and their requirements. The proposed system will be designed
persistently to avoid any misuse of the application. There is no restriction on read access.
 Use case diagram
1. Admin

Login
Reject request
<<extend>>
Manage signup <<extend>> Accept request
requests

Add
<<include>>
<<include>>
Update
Manage Hotels <<include>>
Delete
Add
<<include>>
<<include>> Update
Manage Transports
<<include>>
Delete

Add
<<include>>
Manage Customer
<<include>>
Update
<<include>>
Admin
Delete
View notifications

2. User
 Register

Login

Check services facilities

availibility
Prices
<<include>>
<<include>>

<<include>>
Secuirity
Compare service

Select hotels
<<include>>
Make Booking
Customers <<include>>
Select
Make payment transports

Cancel Booking

Make Complains

Rate
Service

Change
passwoord

3. Hotels
 Register
Add Details

Login <<include>> Update Details

<<include>>

Manage Hotle <<include>>

Delete Details
Services

Add
<<include>>

Customer Record <<include>> Update

<<include>>

Delete

Hotels Recive payments

<<include>>
<<include>> Online
Cancel order
Cash

Manage <<include>> Add

Photogallary
<<include>>

<<include>> Update

Report Customer
Delete

Logout

4. Transportation
 Signup
Transport
Login type

<<include>> Transport
<<include>>
rent
Transportation info
<<include>> Transport
Timing

Manage booking inquiries <<include>>

Customer place
an inquiry

<<include>>
Add
Maintain customer
Record <<include>>
Update
<<include>>
Delete
Make
Transportation Payments <<include>>
Online
<<include>>

Cash
Report Customer

Logout

Use Case description

Use case Name: Signup
Scope Wanderpak (Traveling application)
Level User goal
Primary Actor User
Preconditions Actor should have accessed the system.
Post conditions Actor successfully performs his operation.
Main Success Scenario: Actor Action System Responsibility

1. User requests the 2. System ask for the following

system to create new information
account.  Name

 Email

 Password

3. User provides the

required information.
4. System validates the user
information.
5. System creates new account.

Extension/Alternate: 4a. Phone no already exists.

Frequency of Occurrence: As required

Use case Name: Sign In

Scope WanderPak (Traveling application)
Level User goal
Primary Actor User
Preconditions Actor should have accessed the system.
Post conditions Actor successfully performs his operation and login to the app.
Main Success Scenario: Actor Action System Responsibility
2. System ask for the following information
1. User requests the system
for login.  Email

 Password

3. User provides the required

information.
4. System validates the user information.

5. System successfully allows login.

Extension/Alternate: 4a. User not exists in the Database.

4b. Wrong Password

Frequency of Occurrence: As required