Srs Parking Management System

lOMoARcPSD|34865063
SRS-parking management system
Software engineering (Bahria University)
Studocu is not sponsored or endorsed by any college or university

Downloaded by Abhinav Oli (oli123indian@gmail.com)
lOMoARcPSD|34865063
Software Requirements
Specification
for
E-PARKING MANAGEMENT
SYSTEM
Version 0.1 approved
Prepared by
Muhammad Zafar 01-135201-071

Muneeba Ijaz 01-235192-093
Areej Fatima 01-135201-012
BAHRIA UNIVERSITY ISLAMABAD CAMPUS
26th December 2021

lOMoARcPSD|34865063
P a g e | ii
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History............................................................................................................................iii
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................2
1.4 Product Scope:............................................................................................................................2
1.5 References..................................................................................................................................3
2. Overall Description:................................................................................................................3
2.1 Product Perspective....................................................................................................................3
2.2 Product Functions.......................................................................................................................3
2.3 User Classes and Characteristics................................................................................................3
2.4 Operating Environment..............................................................................................................4
2.5 Design and Implementation Constraints.....................................................................................4
2.6 User Documentation...................................................................................................................4
2.7 Assumptions and Dependencies.................................................................................................4
3. External Interface Requirements...........................................................................................4
3.3 Hardware Interfaces....................................................................................................................5
3.4 Hardware and software requirement...........................................................................................6
3.5 User Interface.............................................................................................................................6
3.6 Database Snaps...........................................................................................................................6
4. System Features.......................................................................................................................7
4.1 Accessibility......................................................................................................................................7
4.1.1 Description and Priority.........................................................................................................7
4.1.2 Stimulus/Response Sequences...............................................................................................7
4.1.3 Functional Requirements.......................................................................................................7
4.2 Lightweight and Elegant.............................................................................................................7
4.3 Interactive User Interface............................................................................................................8
4.4 Highly Customizable..................................................................................................................8
4.4.2 Stimuus/Response Sequences................................................................................................8
4.5 Administrator:............................................................................................................................9
5. Other Nonfunctional Requirements.......................................................................................9
5.1 User Requirement.......................................................................................................................9
5.2 Security Requirements................................................................................................................9
5.2.1 Security:.................................................................................................................................9
5.2.2 System Integrity...................................................................................................................10
5.3 Reliability.................................................................................................................................10
5.4 Availability...............................................................................................................................10
5.5 Maintainability.........................................................................................................................10
5.6 Portability:................................................................................................................................10
5.7 Robustness:..............................................................................................................................10
5.8 System Maintenance and Evaluation:.......................................................................................10
Page ii of 23

lOMoARcPSD|34865063
P a g e | iii
5.9 Software Quality Attributes......................................................................................................11

5.10 Business Rules..........................................................................................................................11
Appendix A: Glossary..................................................................................................................11
Appendix B: Analysis Models.....................................................................................................12
6. Use Case Description.............................................................................................................14
7. System Future Enhancement................................................................................................19
7.1 Scopes For Expansion..............................................................................................................19
Revision History
Name Date Reason For Changes Version
Page iii of 23

lOMoARcPSD|34865063
Software Requirements Specification for E-parking management system
1. Introduction
E-Parking management system for managing the records of the incoming and outgoing vehicles
in a parking house
It’s an easy for Admin to retrieve the data if the vehicle has been visited through number, he can
get that data.
Now days in many public places such as malls, multiplex system, hospitals, offices, market areas
there is a crucial problem of vehicle parking. The vehicle parking area has many lanes/slots for
car parking. So, to park a vehicle one must look for all the lanes. Moreover, this involves a lot of
manual labor and investment. Instead of vehicle caught in towing the vehicle can park on safe
and security with low cost.
Parking control system has been generated in such a way that it is filled with many secure
devices such as, parking control gates, toll gates, time and attendance machine, car counting
system etc. These features are hereby very necessary nowadays to secure your car and to
evaluate the fee structure for every vehicle’s entry and exit
The objective of this project is to build a Vehicle Parking management system that enables the
time management and control of vehicles using number plate recognition. The system that will
track the entry and exit of cars, maintain a listing of cars within the parking lot, and determine if
the parking lot is full or not. It will determine the cost of per vehicle according to their time
consumption.
1.1 Purpose
We can park our vehicle in our own slot by paying.
 Because of that there are no towing problems.

 And our vehicle has been parked as a secure condition.
 There is no risk for vehicle owner for parking the car.
 In case of any damages and problem of vehicle that will claim by parking management.
 As the world is facing many threads daily, robberies are done easily with no track to trace,
bomb blasts occur with the use of vehicle, so if a proper system is adopted each record
can be saved and anyone can be track easily therefore mainly is to make a better and fast
software, most important user-friendly
 Maintain records in short time of period.
 Determines the parking area is full or not.
 Enhances the visitor’s experience.
1.2 Document Conventions

- The main Chapter headings are given with font: Times and font size of 18.
- The Subheadings of each chapter are given with font: Times and size of 14.
- Emphasize is given in Italics.
- Critical information in specific scenario is given in Bold Words.
Page 1 of 23

lOMoARcPSD|34865063
When composing this report, it was acquired that all necessities have a similar need. First there is
introduced a general view about E-PMS and afterward all elements and capacities are
investigated exhaustively.
Abbreviation Explanation
API Application programming
Interface
EPMS E parking management
system
GUI Graphical user interface
IDE Integrated development
environment
IT Information technology
OS Operating system
SQL Structure query language
1.3 Intended Audience and Reading Suggestions

This prerequisite record contains general data about E- PMS, capacities, highlights, and unique
advancements. It portrays exhaustively all that E- PMS requires to work appropriately and with
wellbeing.
Developers: to be sure, they are developing the right project that fulfills requirements
provided in this document.
Testers: to have an exact list of the features and functions that must respond
according to requirements and provided diagrams.
Users: to get familiar with the idea of the project and suggest other features that
would make it even more functional.
1.4 Product Scope:

In the modern age. Many people have vehicles. Vehicle is now a basic need. Every place is under
the process of urbanization. There are many corporate offices and shopping centers, hospitals,
schools, government organizations etc. So, all these places need a parking space where people
can park their vehicles safely and easily. Every parking area needs a system that records the
detail of vehicles to give the facility. These systems might be computerized or non-computerized.
With the help of computerized system, we can deliver a good service to customer who wants to
park their vehicle into the any organization’s premises.
Vehicle parking management system is an automatic system which delivers data processing in
very high speed in systematic manner. Development of this system is very useful in this area of
field. We can sell this system to any organization. By using our system, they can maintain records
very easily. Our system covers every area of parking management. In coming future there will be
excessive need of Vehicle parking management system.
Its motivation is to tackle an issue that truly annoys numerous sellers today for overseeing of
parking spaces inside a parking story. So, it gives you an exceptionally oversimplified
Page 2 of 23

lOMoARcPSD|34865063
arrangement of overseeing leaving spaces which furnishes you with making a passage of
approaching and active vehicles. Parking Management System close to overseeing openings.
1.5 References
www.google.co.in
www.w3schools.com
www.youtube.com
www.DocFoc.com
www.SlideShare.com
www.codeproject.com
2. Overall Description:
2.1 Product Perspective

PMS ought to have the option to give an essential and simple exchange of data.
For example,
It ought to have the option to eliminate the correspondence holes between a representative and
the client. It ought to be viable with every one of the working frameworks.
2.2 Product Functions

The PMS login box ought to on the intranet.
 The secret key field ought to be secured
 By tapping on the dropdown box of the choices the worker ought to have the option to see
reports and accessible slots.
 Employee ought to have the option to change the passwords.
There are a lot of functions in E-PMS. These functions can be placed into broader categories as
follows:
 Security over performance
 Efficiency over functionality
 Accessibility in all aspects
 Lightweight and elegant
2.3 User Classes and Characteristics

A client can just have his/her worker ID number as username so assuming he joins the parking
MS then no one but he can login. This forestalls abuse, unapproved access and hacking of the
item.
Page 3 of 23

lOMoARcPSD|34865063
2.4 Operating Environment

There are many OS environment where our E-PMS is compatible with differ version of OS as
describe in hardware and software requirements, so it does not need to rely on any other
Operating System. Though, one dependency is hardware, and the performance of PMS will
depend on the degree of hardware performance. The PMS will provide the best features of both
Android and iOS combined, so it will have to provide complete support to old and new
applications designed for both Android OS and iOS. To achieve this PMS will have to provide app
development environment (and support) for both Java and Swift/C++ applications.
2.5 Design and Implementation Constraints

Server limit is the number of clients can get to or can be online immediately. More is the quantity
of clients more will be the organization traffic and henceforth the server arrives in a down state.
Individual firewall and refreshing are an intense undertaking, it ought to be with the end goal that
it ought not hinder the organization traffic, making the framework more slow.
As an operating system, the major constraint for PMS will be hardware and its performance.
There are several trivial and non-trivial constraints, which are from both development perspective
and context perspective. Some of them are listed as follows;
1) Memory of the device

2) Cope with boot up procedures of different manufacturers
3) Precise exception handling for both hardware and software
4) Prevent deadlock during applications execution (Prioritize core tasks)
2.6 User Documentation

First off, the end users will be required to sign our Terms and Conditions while first running
E-PMS in their devices. These terms and conditions will contain agreements relevant to the
features implemented in the PMS.
Once the PMS has successfully run up for the first time, a detailed documentation page
will be shown right on the device, which can be skipped as of now, upon clicking skip, the user will
get instructions on how to access the detailed documentation inside the PMS settings app. This
documentation will also be accessible through the web (inside E-PMS web side).
2.7 Assumptions and Dependencies

PMS should work even at when the organization traffic is high. Server ought to have a power
reinforcement just as a data set reinforcement. The PMS ought to be viable with a large portion of
the working frameworks for example past and most recent one
3. External Interface Requirements

Interface Requirement:
Page 4 of 23

lOMoARcPSD|34865063
3.1 GUI:
This is interface should be profoundly natural or intuitive on the grounds that there won't be a help
for the client who is working the Framework. At most of the spots assist work area with being
accommodated clients’ comfort. The screens seeming ought to be planned in such a way that it
can draw Client attraction towards the new designs for the clients.
Likewise, the pin and secret word classification ought to be kept up, this should be possible by
utilizing reference marks at the secret phrase board. Legitimate security messages ought to be
shown all things considered of the spots.
3.2 Software Interface:

 Any windows working framework.
 The PHP should be introduced. For the information base taking care of MYSQL should be
introduced. These items are open-source items.
 The last application should be bundled in a set up program, with the goal that the items
can be effectively introduced on machines. This application should be organized to
comparing banks.
 Front End: Asp.net with C#
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft.

It is used to develop computer programs for Microsoft Windows, as well as web sites, web
applications and web services. Visual Studio uses Microsoft software development
platforms such as Windows API, Windows Forms, Windows Presentation
Foundation, Windows Store. It can produce both native code and managed code.
Visual Studio includes a code editor as well as code refactoring. The

integrated debugger works both as a source-level debugger and a machine-level
debugger. Other built-in tools include a forms designer for building GUI applications, web
designer, class designer, and database schema designer.
 Back End: SQL server
Microsoft SQL Server is a relational database management system developed

by Microsoft. As a database server, it is a software product with the primary function of
storing and retrieving data as requested by other software applications—which may run
either on the same computer or on another computer across a network (including the
Internet).
Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed at
different audiences and for workloads ranging from small single-machine applications to
large Internet-facing applications with many concurrent users
Page 5 of 23

lOMoARcPSD|34865063
3.1 Hardware Interfaces

The E-PMS will be interfacing with hardware all the time and the real challenge during
development is to make most efficient possible usage of hardware components, otherwise, there
will be no market of a new PMS that does not even provide better performance. So, several
strategies will be used during development so that applications as well as operating system uses
least possible hardware resources. As far as the dependency goes, the PMS will be capable of
running on all devices whether that be Snapdragon processors or MediaTek or Kirin and being an
operating system, it will be interfacing with all the hardware components.
3.2 Hardware and software requirement
Processor type Pentium IV or above for optimum performance.
3.3 System type 1.00GB and above
Input device Basic Keyboard and Touch Pad
Output device Standard color monitor
Operating system WINDOWS Versions (7,8.1,8,10,11)
Front End VISUAL STUDIO 2015
Back End SQL SERVER 2008

User Interface
1. Admin Login
2. Invalid login and password
3. Password required field error
4. Register page
5. Registration successful prompt
6. Admin logout
7. Search for customer Details
8. Add and Update customer
9. Search for vehicle details
10. Add and Update vehicle details
3.4 Database Snaps
1. Login database
2. Register database
3. Add Customer
4. Add Vehicle
Page 6 of 23

lOMoARcPSD|34865063
4. System Features
As discussed in Section 2.2, the E-PMS will provide all the features that predecessor E-PMS
software offer, along with new features to improve the quality and performance of the system.
Since this is E-PMS, all the features cannot be listed here. Therefore, the system features are
placed into different categories, with each category representing multiple smaller features of its
own.
4.1 Accessibility
4.1.1 Description and Priority

Accessibility is one of the highest priority features of E-PMS. From thorough
analysis, this accessibility not only includes better UI.
4.1.2 Stimulus/Response Sequences

Normal controls accessibility is enhanced by adding clearer, simple buttons
representing whatever the specific section does.
4.1.3 Functional Requirements
REQ-1: Hardware Monitor & Back-end SQL:

To access fast accessibility these requirements, place a vital
role to enhanced or decrease accessibility to end users.
4.2 Lightweight and Elegant
One of the main or key difference of E-PMS offers least use of hardware resources
while keeping the device’s performance at maximum priority. This can be achieved by
keeping the OS lightweight and only require the hardware when needed.
As soon as the operating system starts, a dedicated system file at back-end of

SQL is set to start-up the data and merge with so called as Hardware Monitor will be
launched. Its responsibility is to keep the hardware free as much as possible. By using this
app, E-PMS will not only increase system performance, but will also restrict other apps
overlapping from misusing the hardware resources.
REQ-1: Hardware Monitor:

This application is required to carry out the goal of making least
Page 7 of 23

lOMoARcPSD|34865063
possible usage of hardware resources, as explained above.
4.3 Interactive User Interface
The users of current E-PMS are not entirely satisfied with their user interfaces,
whether that be Android users or OS users. They always find the UI of the other OS more
interactive. The goal is to make the UI as much accessible as possible, and simple at the
same time. The OS will be made more lightweight by providing simple UI as well.
Initially, the OS will run on user interface which is supposed to be most accessible and
interactive. Once user starts up for the first time, they’ll be shown the way to change the UI
from the settings.
This feature does not depend on any other functionality, it depends on the system as a
whole.
4.4 Highly Customizable
The E-PMS is expected to be most customizable in terms of usability. The different

options will contain different sections to customize different parts to customize information
stored in SQL server at back end. it will basically give the user ability to make the
Operating System how they want. This customization also includes Applications
management, how they should be allowed to use different options to alter data in SQL
server if required. Considering these, Customization is also among one of the most
important features of E-PMS.
4.4.2 Stimuus/Response Sequences
Customization is not one feature, it’s rather a set of features developed to

customize the whole system. So, there is no one trigger for this functionality. The user can
access customization in different options provided by app where they can change required
information according to their needs in return, the changes can be applied right away.
Page 8 of 23

lOMoARcPSD|34865063
This feature does not depend on any other functionality, it depends on the system.
4.5 Administrator:
An overseer is that individual who makes some altering for the E-parking management
system framework like add/drop client, check the exchanges and so forth yet this
executive should be substantial client. Subsequently the administrator should have a
username and secret word. In the venture we won't go somewhere down in a
administrator since we will zero in on the client and his/her necessities more than the
administrator.
 Admin need to enter all details for registration.
 Admin need to insert all details about customer and vehicle.
 Admin need to save all the details of customer and vehicle.
 Admin can retrieve the details of customer.
 Admin must generate a report for payment.
5. Other Nonfunctional Requirements
5.1 User Requirement

 Need for an application that makes communicating easy and comfortable.
 An application that enables user to park a vehicle with safe and secure.
 Need for an application that is easy to use and widely available and hence a web
application
 Handling all functions done with organization in a computerized manner.
 Allowing the user to park the vehicle directly .
5.2 Security Requirements

The system security problem can be divided into following relates issues. They determine the file
structure, data structure and access procedures.
system security an (operating) system is responsible for controlling access to system resources,
which will include sensitive data. The system must therefore include a certain amount of
protection for such data and must in turn control access to those parts of the system that
administer this protection. System security is concerned with all aspects of these arrangements.
5.2.1 Security:
The financial framework should be completely available to just genuine client. It ought to require
pin for passage to another climate
Page 9 of 23

lOMoARcPSD|34865063
5.2.2 System Integrity

State of a system where it is performing its intended functions without being degraded or impaired
by changes or disruptions in its internal or external environments.
That condition of a system wherein its mandated operational and technical parameters are within
the prescribed limits.
The state that exists when there is complete assurance that under all conditions an IT system is
based on the logical correctness and reliability of the operating system, the logical completeness
of the hardware and software that implement the protection mechanisms and data integrity.
5.3 Reliability
The application ought to be profoundly dependable and it ought to create all the refreshed data in
right request.
5.4 Availability
Any data about the record ought to be rapidly accessible from any PC to the approved client. The
recently visited client's information should not be cleared.
5.5 Maintainability
The application ought to be viable in such a way that assuming any new prerequisite happens, it
ought to be handily consolidated in an individual module.
5.6 Portability:
The application ought to be versatile on any windows-based framework. It ought not be machine
explicit.
5.7 Robustness:
This is a very critical requirement of any software. During development stage, the developers will
take into consideration all the possible system failures and will make sure system copes with
them, and at least does not get crashed. Even if, under some circumstances, the OS shuts down
unexpectedly, it will be Kernel’s responsibility to restart the OS as soon as possible.
5.8 System Maintenance and Evaluation:

System Maintenance is a modification of the software product after delivery to accomplish one of
the following objectives:
 Correct faults.
 Improve the performance or other attributes
 Adapt the product to the change environment
Page 10 of 23

lOMoARcPSD|34865063
The performance of the system can be measured by two factors, viz, the efficiency and
effectiveness. The efficiency indicates the way the inputs are used by the system.
Throughout the Lifecycle of the project, it is put through test against efficiency and effectiveness
quite frequently. The stronger the system is, the lesser maintenance the system requires. As of
now, there is no significant maintenance policy adopted or proposed for the system.
5.9 Software Quality Attributes

The following are the attributes of the product PMS:
 It should be equipped with current and archive database.
 All records can easily be updated.
 It should have its personal firewall
5.10 Business Rules

There are several rules set before development of E-PMS to ensure that users and developers
can access the only part which they are allowed to. These roles are broadly categorized as
follows;
1. Project managers will be able to lead the development team apart from accessing the
code. Project Managers will further be divided so that only specific PMs can access
their field within the development stage.
2. Developers can access both backend (code) and frontend of the operating system.
The developers are further ranked so that only specific expertise perform their duty
and do not take control of all the development.
3. QA team can only review bug reports and propose proper fixes for the bug. For this
purpose, they may be given access to some part of the system’s code.
4. End-users can only use the front-end of the system and use its features. They are not
allowed to, and will not be, given access of the code of the system.
Appendix A: Glossary
Terms Definitions
Page 11 of 23

lOMoARcPSD|34865063
API Application programming Interface

Availability The quality of being able to be used or obtained.
Book Chapter A subdivision of a book or of some categories of
reference work; usually numbered and titled.
Characteristics A feature or quality belonging typically to a person, place,
or thing and serving to identify them.
Component A uniquely identifiable constituent part of a content
item composed
Constraints A limitation or restriction.
Database A collection of electronically stored data or unit
records (facts, bibliographic data, texts) with a
common user interface and software for the retrieval
and manipulation of data.
Dependencies The quality or state of being dependent especially
Documentation Material that provides official information or evidence
or that serves as a record.
GUI Graphical user interface
Hardware The machines, wiring, and other physical components
of a computer or other electronic system.
IDE Integrated development environment
JAVA, C++ Programming language
Maintenance The process of preserving a condition or situation or
the state of being preserved.
Quality attributes A property of a work product or goods by which its
quality will be judged by some stakeholder or
stakeholders.
Requirements A thing that is compulsory; a necessary condition.
Scope The extent of the area or subject matter that
something deals with or to which it is relevant.
Security The state of being free from danger or threat
Software The programs and other operating information
SQL Structure query language
System A set of things working together as parts of a
mechanism or an interconnecting network
Appendix B: Analysis Models

PROCESS MODEL:
Page 12 of 23

lOMoARcPSD|34865063
Iterative Model
Iterative process starts with a simple implementation of a subset of the software requirements
and iteratively enhances the evolving versions until the full system is implemented. At
each iteration, design modifications are made, and new functional capabilities are added.
An iterative life cycle model does not attempt to start with a full specification of requirements.
Instead, development begins by specifying and implementing just part of the software, which can
then be reviewed to identify further requirements. This process is then repeated, producing a new
version of the software for each cycle of the model.
The developments are delivered and then assembled into a working prototype. After delivering a
fully functional system within 90 days, the user can give feedback if the system needs any update
or not. This model is flexible and adaptable to changes as well as it is useful when we have to
reduce the overall project risk. In addition, each increment in delivers highest priority functionality
to client
.
Why not Waterfall Model?
Waterfall model is a linear sequential model where next phase starts only after completion of the
previous phase. It is very simple to understand and easy to use because of its systematic well-
defined. Waterfall model can be used when requirements are not changing frequently,
requirement is clear, environment is stable, resources are available and trained. Besides, high
amounts of risk and uncertainty, poor model for long and ongoing projects, cannot accommodate
changing requirements. So, waterfall model is not appropriate for our parking management
system project.
Why not Agile Model?

Agile development model is also a type of Incremental model. Software is developed in
incremental, rapid cycles. This results in small incremental releases with each release building on
previous functionality. Each release is thoroughly tested to ensure software quality is maintained.
It is used for time critical applications. In Agile Model, there is lack of emphasis on necessary
designing and documentation. Projects can become ever lasting because there's no clear end.
So, we think it is not appropriate for our project.
6. Use Case Description

Use case name: E-parking management system
Page 13 of 23

lOMoARcPSD|34865063
Scenario1: create admin account
User actions System

response
1. Enter signup to add 1. Go to registration

information screen.
2. Enter the “create 2. Go to the login
account” button to create screen
account successfully.
Alternate
1a. If user does not enter valid information display error message and directed to
same page.
Scenario2: login account
User actions System response
1 Enter username and 1. Validate username

password. and password.
2 Enter “login” button 2. Go to the system’s
to login. dashboard
Alternate
1a. If user does not enter valid username and password, display error” the username
and password you enter doesn’t matched try again” message and directed to same page.
Scenario3: forgot password

1. Enter email 1. Validate email, send

2. Enter verification verification code to
code, set and enter new password
confirm the new 2. Go to the system’s
password. dashboard, after
login.
Alternate
1a. If user does not enter valid email, display error message and directed to same
page.
2a. verification code is not matched try again or click resend code.
Page 14 of 23

lOMoARcPSD|34865063
Scenario4: select module1 ( add customer , vehicle details and update details)_
1. select customers 1. Go to the customer’s

details from details screen to add
dashboard the records.
to add and view
details of the
customers then 2. Go to the update
screen for changes.
press “add” button.
2. press “update” to
3. Go to the dashboard
update record.
again.
3. Press “E parking
MS” top of the
screen.
Alternate
1a. If user does not enter valid details, display error message and directed to same
page.
3a. if system not response wait and try again later
Scenario5: select module2 (slot’s details)
1. select slot’s details 1. Go to the slot’s

from dashboard details screen to add
to view and give the slot’s according
specific slot to the to specific place,
customers then rows and column
press “add” button. wise.
2. Go to the update
2. press “update” to screen for changes.
update record.
3. Press “E parking again.
MS” top of the
screen.
Alternate
Page 15 of 23

lOMoARcPSD|34865063
1a. If user does not give valid(available) slot, display error message” this slot is
currently not available try another” and directed to same page.
Scenario6: select module3 (transaction details)
1. select transactions 1. Go to the transaction

details from details screen.
dashboard
to view or enter
transaction details of
the customer to
2. print the bill for the
generate bill. customer according
to their time
2. press “printbill”. duration.
Press to go
further
Otherwise press
to cancel the 3. Go to the dashboard
generating bill. again.
MS” top of the
screen.
Alternate
Scenario7: select module4 (camera details)
Page 16 of 23

lOMoARcPSD|34865063
1. select camera’s 1. Go to the camera

details from detail’s screen.
dashboard
to view which
camera is active or
offline.
again.
MS” top of the
screen.
Alternate
1a. If not showing camera’s detail’s, display error message and directed to same
page.
Scenario8: select module5 (Account details)
1. select Account 1. Go to the account

settings from settings screen.
dashboard, in which
the admin can
view and update his
account information.
2. Press “E parking again.
MS” top of the
screen.
Page 17 of 23

lOMoARcPSD|34865063
Alternate
1a. If not access, display error message and directed to same page.
Scenario9: select invoice
1. Select invoice to see 1. Go to the receipt

the transcript/receipt information record
of the customer. screen of the
customer.
2. Press “E parking 2. Go to the dashboard

MS” top of the again.
screen.
Alternate
Scenario10: select logout
3. Select logout 3. Directed to the

admin login page.
Alternate
1b . if system not response wait and try again later
Page 18 of 23

lOMoARcPSD|34865063
7. System Future Enhancement
7.1 Scopes For Expansion
This is the modern age. Many people have vehicles. Vehicle is now a basic need. Every place is
under the process of urbanization. There are many corporate offices and shopping centers etc.
There are many recreational places where people used to go for refreshment. So, all these places
need a parking space where people can park their vehicles safely and easily.
Every parking area needs a system that records the detail of vehicles to give the facility. These
systems might be computerized or non-computerized. With the help of computerized system, we
can deliver a good service to customer who wants to park their vehicle into the any organization’s
premises.
Enhancement to create a Bigger and Better System.
These enhancements deal with what would be required in a new improved, bigger and better
system
 In future if when a vehicle enters into the parking area there should be one sensor in
which the user can easy identify from outside only Is there parking is full or empty or space
is allocated.
 In future the vehicle can be parked by machines
 A website will be online where person should sign up first to see if the parking space is
available at his/her destination if not then nearby!
 Database will indirectly help security regulatory bodies to find the location of suspected
vehicles if parked anywhere and comes in our database.
Page 19 of 23

Srs Parking Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Srs Parking Management System

Uploaded by

Copyright:

Available Formats

lOMoARcPSD|34865063

SRS-parking management system

Software engineering (Bahria University)

Studocu is not sponsored or endorsed by any college or university

Version 0.1 approved

Muhammad Zafar 01-135201-071

26th December 2021

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Downloaded by Abhinav Oli (oli123indian@gmail.com)

5.9 Software Quality Attributes......................................................................................................11

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

 Because of that there are no towing problems.

1.2 Document Conventions

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope:

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

2.1 Product Perspective

2.2 Product Functions

2.3 User Classes and Characteristics

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

2.4 Operating Environment

2.5 Design and Implementation Constraints

1) Memory of the device

2.6 User Documentation

2.7 Assumptions and Dependencies

3. External Interface Requirements

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

3.2 Software Interface:

 Front End: Asp.net with C#

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft.

Visual Studio includes a code editor as well as code refactoring. The

 Back End: SQL server

Microsoft SQL Server is a relational database management system developed

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

3.1 Hardware Interfaces

Processor type Pentium IV or above for optimum performance.

3.3 System type 1.00GB and above

Input device Basic Keyboard and Touch Pad

Output device Standard color monitor

Operating system WINDOWS Versions (7,8.1,8,10,11)

Front End VISUAL STUDIO 2015

Back End SQL SERVER 2008

3.4 Database Snaps

Downloaded by Abhinav Oli (oli123indian@gmail.com)

Software Requirements Specification for E-parking management system

4.1.1 Description and Priority

4.1.2 Stimulus/Response Sequences

4.1.3 Functional Requirements

REQ-1: Hardware Monitor & Back-end SQL:

4.2 Lightweight and Elegant

4.2.1 Description and Priority

4.2.2 Stimulus/Response Sequences

As soon as the operating system starts, a dedicated system file at back-end of

4.2.3 Functional Requirements

REQ-1: Hardware Monitor:

Downloaded by Abhinav Oli (oli123indian@gmail.com)