Software Requirements

Specification
For

Online Car Showroom Web App

Prepared by < ABID>

<Department of Computer Science, IUB>

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
[Type here]

Table of Contents
Table of Contents....................................................................................................................... ii
Revision History......................................................................................................................... ii
1. Introduction.......................................................................................................................... 3
1.1 Purpose...................................................................................................................................... 3
1.2 Document Conventions..............................................................................................................3
1.3 Intended Audience and Reading Suggestions...............................Error! Bookmark not defined.
1.4 Product Scope............................................................................................................................4
1.5 References..................................................................................................................................4
2. Overall Description.............................................................................................................. 5
2.1 Product Perspective....................................................................................................................5
2.2 Product Functions.......................................................................................................................6
2.3 User Classes and Characteristics..................................................Error! Bookmark not defined.
2.4 Operating Environment...............................................................................................................6
2.5 Design and Implementation Constraints......................................Error! Bookmark not defined.
2.6 User Documentation...................................................................................................................7
2.7 Assumptions and Dependencies..................................................................................................7
3. External Interface Requirements........................................................................................ 7
3.1 User Interfaces............................................................................................................................7
3.2 Hardware Interfaces....................................................................................................................7
3.3 Software Interfaces......................................................................Error! Bookmark not defined.
3.4 Communications Interfaces.........................................................................................................8
4. System Features.......................................................................Error! Bookmark not defined.
4.1 System Feature 1.........................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on)......................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements.................................................................................... 8
5.1 Performance Requirements.........................................................................................................8
5.2 Safety Requirements...................................................................Error! Bookmark not defined.
5.3 Security Requirements................................................................................................................8
5.4 Software Quality Attributes........................................................................................................8
5.5 Business Rules............................................................................Error! Bookmark not defined.
6. Other Requirements............................................................................................................. 9
Appendix A: Glossary.............................................................................................................. 10
Appendix B: Analysis Models.................................................................................................. 12
Appendix C: To Be Determined List............................................Error! Bookmark not defined.

Revision History
Name Date Reason For Changes Version

Car Show Room System

[Type here]

1. Introduction

1.1 Purpose

Aim of this implementing system is to facilitate the client and also provide ease. And also
promotion of business globally. Client can access from all over by using web site services of
the implementing system and also he can purchase or rent a car. Client can book the car at
home by using online services of the implementing system.

In past user where access the information about car or client by using register work. The aim
of this project is provide ease to user by using this implementing system because there is no
need of register.

The main aim of that system is to manage a record for long period of time and help the end-
users to take advantage it. Users can booked a car in advance, users add a car in wish list, and
users compare specification of different cars online that help in purchasing a car that which is
one of the best for you. The second aim of that system is to increase the popularity of
showroom increases because there is no of showroom available in Multan. The system will
increase the popularity of the organization. Through this system the organization keep a
record for long period of time and access it quickly if they need any record.
Today market are online market and in future the online market are the only market where
everyone shopping. So the increase of online shopping we build an online system to maintain
her place in market and run an organization in future to bet a competitor

1.2 Document Conventions

In writing this SRS I followed some standards e.g. font Size:

 Heading :18px bold;
 Sub-Heading: 14px bold;
 All the contextual data : 12px
And font style I used in this Documentation is Times New Roman.

1.3 Product Scope

By using this system the user will be able to book their car with rent. It will provide the
facility to manage all booking. By the use of online car booking it will enable to see all the

Car Show Room System

[Type here]

booking car for rent all available at one place. Admin will be able to add car for sale and set
their Purchase record.

The scope of the ‘Online car showroom System’ project is to create a web-based interface
which deals with the online car booking and car sale information. To purchase a car a
database has been established to efficiently store all information of the car and registered
customers can booked car for rent only. This database will not be accessed directly by
customers. When a user will make his/her account then he/she can add the car in ‘Wish List’.
There is HTML/PHP/JavaScript links. These are the set of scripts to dynamically create web
pages which can be viewed by any commonly used web browser. This project also provides
security with the use of Login-id and Password, so that any unauthorized users cannot use
your account. The only Authorized that will have proper access authority can access the
software.

The major deliverables constitute an information system to:

 Allow user to create and setup his/her account by using the webpage.

 Allow administrators to delete the customer account

 Allow registered customers to view all car in detail of them

 Allow customers view their booking history

 Allow customers to booked car for rent

1.4 References:
Here is detail of the systems already in use and I get help from these systems..

Existing System # 1

URL: https://www.carmudi.pk/

Main Feature
The search engine

 The user accounts
 Admin account
 Deferent cities covers

Car Show Room System

[Type here]

Limitation
 Prices

 Picture of cars view

 Adds which make users unlike.
Existing System # 2
URL: https://www.vroom.com/

Main Feature
The Interface of front page
 Different model which it will buy and sale
 The user accounts
 Admin account

Limitation
 Prices

 Users satisfaction because the system will not grantee the cars that are used in any
illegal work.

2. Overall Description

2.1 Product Perspective

Before this system the organization will work on paper work to store data and others record.
This system will help the organization that how it will work in easier way. The main aim of
that system is to manage a record for long period of time and help the end-users to take
advantage it. Users are booked a car in advance, users add a car in wish list, and users
compare specification of different cars online that help in purchasing a car that which is one
of the best for you. The second aim of that system is to increase the popularity of showroom
increases because there is no of showroom available in Multan. The system will increase the
popularity of the organization. Through this system the organization keep a record for long
period of time and access it quickly if they need any record. Today market are online market
and in future the online market are the only market where everyone will supposed to do
shopping, sale and purchase.

Car Show Room System

[Type here]

2.2 Product Functions:

1-Admin (he can also add, update the login accounts):

 Login

 Add Car ads

 Manage Purchase car records

 Manage sale car records

 Manage users

 Manage online booking car

 Mange counter car booking

2-User (only view all detail):

 Login user

 View car ads

 View which car is available for rent

 Add ads on wish list

 Online booking a car for rent

3-Car detail:

 Add car pictures

 Add car prices

 Add which car is available for rent and which for sale.

2.3 Operating Environment

The software is web based Application and can be used at any web browser.

3. External Interface Requirements

3.1 User Interfaces

Admin Panel
Admin panel is designed to provide ease to admin where admin can manage the data entries
by using INSERTION, DELETION, and MODIFICATION. Only admin can access this
Car Show Room System
[Type here]

panel by using login form. In this module admin has access to update a website front-end and
access to manage a user records. Admin has every rights for example if admin want to update
front-end images or contact information like facebook link, gmail link, etc. In admin panel
the record of users, cars which we purchase or sale both records and the time of period in
which car are available for rent and which car are on rent every needed information are
mentioned in attractive way.

Admin Restriction:

Admin has no rights to add users manually through admin panel.

User Panel
User panel is designed to arrange for ease to user where user can contact to admin and also
use their services for client by using online booking of car. User can access wish list by using
login procedure. In this panel admin can access the data services by using username and
password of the existing user.

In this panel or module user we shown the user rent a car history that which car he/she take a
rent for us. In user panel user are access to update his/her profile, Order a car advance
booking, purchase a car and add a car in wish list. Users which is register are secure with
their unique username and password.

Access Restrictions:
User has no access to upload anything on a website. We mentioned a user access in policy or
privacy page. User has no access to delete its rent a car history. Users are only see a record
which we show on its panel. User access are defined by session.

3.1 Hardware Interfaces

We are developing a web site online car showroom sale system. Anyone using browser and
having internet access can use the system without hardware limitations

3.2 Communications Interfaces

For this project we access of internet because we are creating an online database system.
Browser is the communication interface between user and the system. User can use the
system only by browser.

Car Show Room System

[Type here]

4. Other Non-functional Requirements

4.1 Performance Requirements:

It means that to make a project failure free. But this is in specific period and specific environment.
That’s way we are use a suitable model for our project and that optimized the file process

4.2 Security Requirements

I am trying that only authorized person is only enter in to the system otherwise nobody can
access in this both panel.

4.3 Software Quality Attributes

System should not allow users to add any data and managing database.

4.4 Maintainability:
There should be fixed bugs easily and quickly, added new features easily, it increase its
performance and it change to support in new environment or OS.

5. Other Requirements
 Project Title: Online car showroom system

 Programming language: HTML, CSS, PHP, JavaScript, Bootstrap, JQuery

 Software tools: notepad++

 Database: SQL Server 2014

 End User System Requirements:- web browser support

 Hardware: web browser support

 Operating system: window, Andriod, apple os, mac

 Storage Capacity: 2 GB

 Implementation: Khan Motors Showroom T.M.Panah

 Maintenance: As Required

Car Show Room System

[Type here]

Appendix A: Glossary
T.M: Taranda Muhammad Panah
OS: Operating System.
SQL: Sequential query Language.

Appendix B: Analysis Models

1. Use case Diagrams
Use Case Diagram of Admin:

Figure 1

Admin has manage the overall admin panel as well as front end of the web site.

Car Show Room System

[Type here]

Admin manage the car sale and purchase records as well as rent a car records also. Admin
also manages the user and its need. Admin will delete any user as well as products. Admin
also manages those record which is occur on real-time sale and purchases of cars. Admin
received feedbacks from open or register users. Admin manage booking of cars and its
appearance on front end.

Car Show Room System

[Type here]

Use case Diagrams of user:

Figure 2

User panel is designed to arrange for ease to user where user can contact to admin and also
use their services for client by using online booking of car. User can access wish list by using
login procedure. In this panel admin can access the data services by using username and
password of the existing user.

Car Show Room System

[Type here]

Class Diagrams:

Figure 3

In Class diagram, we defined the methods (Add, Delete, Update, Show) of each tables.

Car Show Room System

[Type here]

3.6 Sequence Diagrams

Admin Login:

Figure 4

Admin username and password is assign by the developer. Admin need to be enter this
information to access the system. In this diagram we define how admin login to the system and
what the process if admin entered wrong information’s. The admin has unique username and
password. Through this diagram we can clearly show that how admin to server and server to
database respond.

Car Show Room System

[Type here]

User Login:

Figure 5

User login process show that how user login into the system and if he/she enter wrong
information then what will be happened. User entered wrong information are not access to the
user panel and suggest it to register first. The users accounts are secure with username and
password which unique and its relaed legal information shown into the privacy and term &
condition portion of the website.

Car Show Room System

Software Requirements Specification <Car Showroom System> Page 1

Add Product Sequence Diagram:

Figure 6

In this diagram I am showing that how system add new company, product into the database and
admin entered wrong information than what will do our checks actions. Admin enter record for
website maintain related or record for sale and purchasing the checks are perform action on each
activity. Admin entered data into the database and stored record for long period of time.

Car Show Room System