Вы находитесь на странице: 1из 9

IQRA UNIVERSITY ISLAMABAD

Submitted to: MR. Immad Ahmed

WEB-ENGINEERING
Software Requirement Specification

Online Showroom Management System

Submitted by
Hashar Ahmed,Muhammad Usama
Registration No.
23250,23430
Date 21-11-2019

For office use only


Comments:
___________________________________________________________________
___________________________________________________________________
Software Requirement
Specification

Table of Contents
Introduction .......................................................................................................................................................... 3
Purpose: ................................................................................................................................................................ 3
Scope:.................................................................................................................................................................... 4
Definitions, Acronyms, and Abbreviations:......................................................................................................... 4
References: ........................................................................................................................................................... 4
Overview: .............................................................................................................................................................. 5
Overall Description: .............................................................................................................................................. 5
Product Perspective: ............................................................................................................................................ 5
Product Function: ................................................................................................................................................. 5
Functional Requirement ...................................................................................................................................... 6
 Main: ........................................................................................................................................................ 6
 Vehicles: ................................................................................................................................................... 6
 Vehicle Selection: ..................................................................................................................................... 6
 Booking:.................................................................................................................................................... 6
 Admin: ...................................................................................................................................................... 6
 Dealer: ...................................................................................................................................................... 7
NON FUNCTIONAL REQUIREMENTS ..................................................................................................................... 7
 Usability .................................................................................................................................................... 7
 Reliability .................................................................................................................................................. 8
 Performance ............................................................................................................................................. 8
 Security ..................................................................................................................................................... 8
System requirements ........................................................................................................................................... 8
User Interfaces: ................................................................................................................................................ 8
The user interface for the software shall be compatible to any browser such as Internet Design..................... 8
Constraints: ....................................................................................................................................................... 8
Performance: ................................................................................................................................................ 8
Data Storage: .................................................................................................................................................... 8
On-line User Documentation and Help System Requirements: ......................................................................... 9
Software Interfaces: ............................................................................................................................................. 9
Hardware Interfaces: ........................................................................................................................................... 9

Introduction
The purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. This project document describes the project's target audience
and its user interface, hardware and software requirements.

The aim of this document is to gather and analyze and give an in-depth insight of the
complete Online Vehicle Showroom by defining the problem statement in detail. The detailed
requirements of the Online Vehicle Showroom are provided in this document.

Purpose:
The purpose of the document is to collect and analyze all assorted ideas that have come
up to define the system, its requirements with respect to consumers. The main purpose of this
Vehicle showroom is to develop a web based interface for Vehicle showroom companies.

The main purpose of this Online Vehicle Showroom is that it provides provision to
customers to buy or book vehicles through online. The current system is offline system, in this to
purchase vehicle the customer should visit to showroom. So this current system is very difficult
because its time consuming. So our project aims at creating an web application which tracks
Customer records, Online booking, Online vehicle records, etc. and it provides easy to use web
based interface for customers where customers can search for vehicles, view a complete details,
models, features, pricing of the vehicles and book the vehicles.

Scope:
The name of the project is “ONLINE SHOWROOM MANAGEMENT SYSTEM”. The main
scope of this web application is that depicts online Vehicle showroom and booking vehicles
through online. Customer can register to this site and he/she can book vehicles by entering
his/her login information. Administrator is main user of this system and he/she can add
employees, and new vehicle details.

 The current system can be extended to allow the customers to register accounts and save
favourite vehicles in to wish list.
 The design of the web application involves the listing the vehicles, search for vehicles,
display the complete details of vehicles, etc.
 It provides updated information about the vehicles of all the companies.
 Customer can view Purchase details and billing records any time.

Definitions, Acronyms, and Abbreviations:


SRS Software requirement specification
OSMS Online Showroom Management System

PHP PHP: Hypertext pre-processor.


PHP is a server scripting language, and is a powerful tool for making dynamic and
interactive Web pages quickly. PHP is a widely-used, free, and efficient alternative
to competitors such as Microsoft's ASP.

MySQL MySQL Database server.


MySQL is a most popular database system used on the web. It supports standard
SQL Queries. The data in MySQL is stored in tables. A table is a collection of
related data, and it consists of columns and rows.

References:
 University Notes
 www.w3schools.com
 www.php.net
 www.mysql.com

Overview:
The following subsections provide complete overview of the SRS documentation for the
product “Online Vehicle Showroom”. The entire SRS is documented in the view of customers,
dealers and admin and the following subsections are arranged to complete outlook of the
software, its perspective, features, and System requirements.

Overall Description:
User Friendliness is provided in the web application with various controls provided by
system Rich User Interface. This project which helps customers to buy or book vehicles through
online. It keeps track of Customers records, Vehicle records, Payment and billing records, dealer
records, etc. This is web application and it’s developing using PHP language. All the records
stores in MySQL Database.

Product Perspective:
This totally self-contained and works efficiently. It provides simple database rather then
complex ones for high requirements and it provides good and easy graphical user interface new,
naïve as well as experienced users of the computers.

Product Function:
The product functions will include the following areas:
 Admin logs in into the application user name & password.
 After successful login the main page appears.
 The application is capable enough to store data and also perform some editing on them
that is added. It will be having user friendly GUI’s that will guide the user to easily
achieve the same. This program is a menu driven program. When we click the main menu
the different forms will be enabled.
 View/Edit/Delete Vehicle Details
 Booking Status Detail
 Login/Registration of User
 View Car Details

Functional Requirement
The program consists of the following:

 Main:
o The main page, neatly designed page, here login option is provided to login. Also
new signup option is provided for new user to signup.

 Vehicles:
o This screen will display all the vehicle details, with exact cost, Features, Model
details, etc.

 Vehicle Selection:
o This search screen Option must be provide to select the vehicles based on name.
In this option customer can select vehicles based on its model or name.

 Booking:
o In this page user can book vehicles by entering cart information. After booking
vehicles user will receive booked vehicles information via mail.

o This page also includes the details about the payment must be done by the
customer during the time of delivery.

 Admin:
o Administrator has full permission to access this web site. Here administrator can
add new vehicle details, and he/she can add his/her dealers.
 Dealer:
o Dealers can handle customer details, and he can communicate with customers
through mail. If customer forgets his password dealer can reset his password.

NON FUNCTIONAL REQUIREMENTS


Nonfunctional requirements are the properties that your product must have. Think of
these properties as the characteristics or qualities that make the product attractive, or usable, or
fast, or reliable. These properties are not required because they are fundamental activities of the
product -- activities such as computations, manipulating data, and so on -- but are there because
the client wants the fundamental activities to perform in a certain manner. They are not part of
the fundamental reason for the product's existence, but are needed to make the product perform
in the desired manner.
Nonfunctional requirements do not alter the product functionality. That is, the
functional requirements remain the same no matter what properties you attach to them. The
nonfunctional requirements add functionality to the product -- it takes some amount of pressing
to make a product easy to use, or secure, or interactive. However the reason that this
functionality is part of the product is to give it the desired characteristics. So you might think of
the functional requirements as those that do the work, and the nonfunctional requirements as
those that give character to the work.
Nonfunctional requirements make up a significant part of the specification. They are important
as the client and user may well judge the product on its non-functional properties. Provided the
product meets its required amount of functionality, the nonfunctional properties -- how usable,
convenient, inviting and secure it is -- may be the difference between an accepted, well-liked
product, and an unused one.
Let's take a look at another real example. Anyone who has purchased a car, whether they were
aware of it or not, made their final decision based on which car met both their functional and
nonfunctional needs. Functionally, the car had to be able to transport passengers from some
starting location to a particular destination (that is, get me from point A to point B). A variety of
nonfunctional attributes or characteristics were likely considered: security and safety,
maintainability (ease of repair), reliability (probability of failure), scalability (ease of expansion),
efficiency and performance (gas mileage, engine size, capacity -- both in number of passengers
and cargo space), portability (ease of transport -- can it be towed easily or can it tow a trailer),
flexibility (ease of change -- can it adapt to changes in weather/road conditions), and usability
(ease of use -- comfort, handling, stereo sound quality)

 Usability
o User interface will be user friendly, so user can familiar to the system and easy to
use.
 Reliability
o The system will be able to meet specified objectives as well as the expectations of
the customers.

 Performance
o The system should provide the services in considerable time interval.

 Security
o The information provider by the user should be authentic which protect the
system from external attack and spamming

System requirements
User Interfaces:

The user interface for the software shall be compatible to any browser such as Internet Design

Constraints:
 There are no memory requirements.
 The computers must be equipped with web browsers such as Internet explorer, Google
chrome, Mozilla Firefox, etc.
 A general knowledge of basic computer skills is required to use the product.

Performance:
 Good working computer with all requirements.
 The product shall be based on web and has to be run from a web server.
 The product shall take initial load time depending on internet connection strength.

Data Storage:
 The customer’s web browser shall never display a customer’s password.
 The customer’s web browser shall never display a customer’s credit card number after
retrieving from the database.
 The system’s back-end servers shall only be accessible to authenticated administrators.
 The system’s back-end databases has login id and password.
On-line User Documentation and Help System
Requirements:
It shall provide specific guidelines to a customers for using the Online Vehicle
Showroom. To implement online user help, link and search fields shall be provided.

Software Interfaces:
 Technology Implemented : Apache Server
 Language Used : PHP/HTML/CSS
 Database : My SQL
 User Interface Design : HTML, JavaScript
 Web Browser : Mozilla, Google Chrome, etc.

Hardware Interfaces:
 Processor : Pentium, AMD or Higher Version.
 Operating System : Windows XP/ Windows 7/ Linux
 RAM : 256 MB, 2GB recommended
 Hardware Devices : Keyboard with mouse
 Hard disk : 10GB or More
 Display : Standard Output Display