Chapter 1

System Requirements Specification (SRS)

“Automated Car Parking System”

Version 1.0

Location of electronic version of File:

Department of Information and Technology, SCOE, Pune

1
1.1 INTRODUCTION Automated Car Parking is a mechanical, electrical, software system
used to park car without assistance of a human being. AutoMotion Parking Systems
introduces the first fully automated parking garage system in New York City
providing the easiest, fastest and safest way to park available, while doubling the
number of parking spaces compared to conventional parking. In this system, driver
enters through garage door, parks the vehicle on a pallet inside an “entry and exit
room”. He swipes his RF smart card and walks away. The car automatically parked by
the system. Need for system development: In conventional car parking system driver
has to park car at available place.It is difficult for a human to constantly
examine the eternal flow of vehicles to the parking space. In conventional car
parking system anyone, anything can touch the car so scratches, dings problems can
occur. Due to this less security because of the possibility of accusation of stolen
personal items in the car. So there is need to develop Automated Car Parking
System. Park, swipe and leave- three simple steps are in Automated Car Parking
System. Integrating the latest in laser and computer technology with conventional
elevator components parking offers a solution that eliminates most of the hassle of
conventional parking. 1.1.1 Product Overview

Automated Parking Systems provides customized parking systems for many areas like
super markets, shopping malls, multiplexes. It integrates the latest in laser and
computer technology with conventional elevator components. Automated Parking
Systems offers a parking solution that eliminates most of the hassles of
conventional parking and doubles, sometimes triples the capacity of similarly sized
conventional garages. It provides Security against theft, damage and scratches,
dings because no one ever touches the cars. The system delivers cars to their
owners within 2 minutes. It has numerous designs that can fit within any project
size. With this vast range of products we can design a system to fit any site. For
each project we provide all the necessary

2
services associated with the design, approval, installation, and operation of
automated parking systems

1.2 SPECIFIC REQUIREMENTS 1.2.1 External Interface Requirements Hardware Interfaces

• • • •
• •

Sensors Lasers Storage and Retrival unit. RF Card Reader RF Smart Card
Camera and sensors

Software Interfaces: Software interface will contain the software GUI for user to
interact with the system. 1.2.2 • • • • • • • Software Product Features System
provides for the safe/secure parking of cars with safety advantages for users.
System accommodates different car heights and large, luxury cars. Easy operation
with several control options. Security against theft, damage and scratches, dings.
Doubles parking capacity over comparably sized conventional garages. Delivers cars
to their owners within 2 minutes. Simultaneous exchange of empty pallet with
occupied significantly increases the speed of the parking system.

3
1.2.3

Software system attributes • Reliability As client is looking for Automated Car

Parking System to be built, it is desirable that, the system should give less or
completely zero opportunities to have human errors, which itself will make system
reliable. • Availability Availability software attribute will make sure that system
should be available to the end user in its required form and it should not
compromise any of its functionality. • Security Security software attribute will
prevent system from any kind of unauthorized access. It will add all required
features to the system which should ultimately lead to the system’s as well as end
user’s security. • Maintainability Maintainability software attribute will provide
all kinds of required technical, documentation assistance to the end user, so that
he / she can easily maintain the system to its proper working condition. •
Portability Software development team will try to achieve portability software
attribute by making system portable to the different car manufacturer who are also
looking for automatic car parking. • Performance Performance software attribute
will make sure that system failure chances should reach to zero percentage.
Software development team will give their best to achieve 99.99 percentage accuracy
and reliability in the system that would be deployed to the end user / client.

1.2.4

Database Requirements SQL Server 2005

4
1.3 Additional Material RFID Card:

RFID Card Reader:

Storage and Retrival Unit (SRU):

5
Chapter 2

Software Project Management Plan (SPMP)

“Automated Car Parking System”

Version 1.0

Location of electronic version of File:

Department of Information and Technology, SCOE, Pune

6
2.1 INTRODUCTION: 2.1.1 Project Overview: This section of the document is an
introduction to “Automation Car parking System” project. It will describe the
purpose of the project and the objectives that are to be accomplished, the
assumptions and constraints that underlie the effort, the deliverables that will be
produced by the project, and a summary of the project schedule and budget.

2.2 PROJECT DELIVERABLES The following is the list of the deliverables those are to
be delivered to the stakeholder at regular interval of time. The list consists of
the outcome/result obtained at the end of each phase of SDLC. Sr. No. 1 Requirement
gathering Report of the initial developer meeting, SRS document 2 Analysis Use case
diagram with specifications, Data Flow Diagram, Activity Diagram, Project Plan with
cost and effort estimation 3 Design UML diagrams, Design document 4 5
Implementation Testing Source code of the system Testing document, Change report 6
Deployment System as an installable package, User manual and Guide Phase of SDLC
Deliverables

7
2.3 PROJECT ORGANIZATION 2.3.1 Software Process Model

The project is carried out using “SPIRAL DEVELOPMENT MODEL”. Spiral Development
Model The spiral model is a software development process combining elements of both
design and prototyping-in-stages, in an effort to combine advantages of top-down
and bottom-up concepts. This model of development combines the features of the
prototyping model and the waterfall model. The spiral model is intended for large,
expensive and complicated projects. A spiral model is divided into a number of
framework activities Typically, there are between three and six task regions. Fig
depicts a spiral model that contains six task regions: Customer Communication—tasks
required to establish effective communication between developer and customer.
Planning—tasks required to define resources, timelines, and other project related
information. Risk analysis—tasks required to assess both technical and management
risks. Engineering—tasks required to build one or more representations of the
application. Construction and release—tasks required to construct, test, install,
and provide user support (e.g., documentation and training). Customer evaluation—
tasks required to obtain customer feedback based on evaluation of the software
representations created during the engineering stage and implemented during the
installation stage The following diagram illustrates the information, document and
product flow between the lifecycle process.

8
2.3.2

Roles and Responsibilities Sr. No. 1 Requirement gathering Phase of SDLC Team
Involved Savita, Monali Prepare report of the initial developer document 2 Analysis
Seema Project Plan with cost and effort estimation 3 Design Savita Prepare use case
diagram with specifications, meeting, SRS members Responsibilities

9
Data Flow Diagram, Activity Diagram, Design document 4 Implementation Seema,
Savita, Monali Develop source code of the system 5 6 Testing Deployment Savita
Seema, Savita, Monali Prepare testing document Deliver System as an installable
package, User manual and Guide

2.3.3 Methods, tools and techniques Development methodology: The project shall use
the spiral software development methodology to deliver the software products. The
decision to use the Spiral methodology is due to the following characteristics of
the project: The product definition is stable Requirements and implementation of
the product are both very well-understood Technical tools and hardware technology
are familiar and well-understood Waterfall methodology has proven successful for
projects of this nature Risk analysis Development techniques: This architecture
allows us to use object-oriented methods and tools for analysis, design, and
implementation. We will use Object Modeling Technique (OMT) for this purpose.
Tools: The following work categories will have their work products satisfied by the
identified tools: o Team member desktop foundation o Microsoft Windows 2000 desktop
operating system o Microsoft Project 2003 [WBS, schedule/cost estimates, resource
planning, project control]

10
o Microsoft Word 2003 [document preparation and revision] o Implementation o
Microsoft Visual C++ [programming language, development tools and object code
generation] o Windows Software Development Kit (SDK) [programming support] o
Microsoft PowerPoint 2003 [training presentations] o Microsoft Windows 2000 Server
Standard [server operating system]

2.4 PROJECT MANAGEMENT PLAN 2.4.1 Description of tasks with planned milestones Sr.
No. 1 2 3 4 5 6 7 Task Scope Determine the Project Scope Define Preliminary
Resources Establish the Project Goals Analysis / Software Requirements Conduct
Project Requirement analysis Draft Preliminary Days 04 1 1 2 10 5 Start Date 12-08-
11 12-08-11 13-08-11 14-08-11 14-08-11 14-08-11 19-08-11 Finish Date 15-08-11 12-
08-11 13-08-11 14-08-11 23-08-11 18-08-11 21-08-11

software 3

specification 8 9 10 11 12 13 14 15 16 17 18 Obtain approval to proceed further

Design Review Preliminary software Develop functional specification Develop initial
documentation Develop prototype Review functional specification Obtain approval to
proceed further Implementation and Coding Review Functional Specification Identify
Modules 2 20 2 4 4 3 3 4 25 3 5 22-08-11 23-08-11 11-09-11 13-09-11 16-09-11 20-09-
11 23-09-11 26-09-11 30-09-11 30-10-11 03-12-11 23-08-11 11-09-11 12-09-11 16-09-11
19-09-11 22-09-11 25-09-11 29-09-11 24-10-11 02-10-11 07-10-11

11
19 20 21 22 23 24 25

Develop Code Problem of Different Versions Development Complete Testing Unit

Testing Integration Testing, System Testing Installation testing , Finalize Testing

10 5 2 10 3 5 2

08-10-11 19-10-11 23-10-11 25-10-11 25-10-11 02-11-11 07-11-11

18-10-11 23-10-11 24-10-11 03-11-11 27-10-11 06-11-11 08-11-11

2.4.2

Deliverables and milestones

Sr. No. 1

Phase of SDLC Deliverables

Milestones(Dates)

Requirement gathering

Report of the initial developer 12-08-11 to 15-08-11 meeting, SRS document Use case
diagram with 14-08-11 to 23-08-11

Analysis

specifications, Data Flow Diagram, Activity Diagram, Project Plan with cost and
effort estimation 3 Design UML diagrams, Design document 4 5 Implementation Testing
Source code of the system Testing document, Change report 6 Deployment System as an
installable package, User manual and Guide 04-11-11 to 09-11-11 30-09-11 to 24-10-
11 25-10-11 to 03-11-11 23-08-11 to 11-09-11

12
2.4.3 Risks and Contingencies Risk Project risks Description Identifies potential
budgetary, schedule, personnel (staffing and organization), resource, customer, and
requirements problems and their impact on a software project. It threatens the
project plan. That is, if project risks become real, it is likely that project
schedule will slip and that costs will increase. Technical risks Identifies
potential design, implementation, interface,

verification, and maintenance problems. Technical risks threaten the quality and
timeliness of the software to be produced. If a technical risk becomes a reality,

implementation may become difficult or impossible. Market risk Building a excellent

product or system that no one really wants Budget risks Known risks Losing
budgetary or personnel commitment Those that can be uncovered after careful
evaluation of the project plan. Predictable risks Unpredictable risks Extrapolated
from past project experience They can and do occur, but they are extremely
difficult to identify in advance. Support risk The degree of uncertainty that the
resultant software will be easy to correct, adapt, and enhance. Schedule risk The
degree of uncertainty that the project schedule will be maintained and that the
product will be delivered on time.

13
Chapter 3

Software Design Description (SDD)

“Automated Car Parking System”

Version 1.0

Location of electronic version of File:

Department of Information and Technology, SCOE, Pune

14
3.1 INTRODUCTION 3.1.1 Design Overview Users can take RFcards according to their
need and can charge according to his requirement. The user will be provided with a
prepaid wireless RF smart card. The data regarding this will be registered on a
centralized server. The client machine will be attached with a smart card reader.
When the user having the charged smart card comes to park car , he will need to
swipe the card to the card reader. The reader data is further processed. This data
is then passed to the server, which will first authenticate the user’s validity,
checks for the balance and acknowledge to the client. The software should provide
fully automated solution for car parking. Software should recognize car from all
sides and determine whether it will fit into the system or not.

Design Overview

15
Use Case Diagram

16
Use Case for Administrator

Use Case for User Activity Diagram

Activity diagram for Entry Section

17
Activity Diagram for Exit section

18
Sequence Diagram

Sequence Diagram

19
Data Flow Diagram

Level 0 DFD for Overall System

Level 1 DFD for Login System

20
Chapter 4

Software Test Document (STD)

“Automated Car Parking System”

Version 1.0

Location of electronic version of File:

Department of Information and Technology, SCOE, Pune

21
4.1 TEST PLAN Test Plan: TP_1 Test Scope Only authorized user should get access to
the system. Sensors should sense the object from all directions in concern with
car. System should provide proper empty pallet to park the car. Only authorized
user should get access to the system. User must have RFID card to get access to the
system System should not get any kind of failure while car is on the way. System
should prompt the message of failure before it gets out of control. Test Director

Test Objective Assumption Risk Analysis Roles & Responsibilities Test Tools

4.2 TEST CASE Test Case: TD_1 - Login Module

Test Form id 01 name Login

Test condition

Description Steps

Expected result

Actual result Entered

Pass/fail

Click on Enter Login button

the Enter the Entered

Pass

username, password and click Login button

username, successfully successfully password and click Login button Enter the Login
username and click Login button not Login not Pass

successful. Message “please enter

successful. Message “please

the enter

the

22
Password” Enter the Login

Password” not Pass

not Login

username, successful. password and click Login button Message “please enter

successful. If login

attempt < 3 the then Message “please enter Correct Password” Else exit. the

Password”

02

Login

Click on Enter close button

the Enter the The

form The

form Pass

username, password and

username, get closed password

get closed

click and click

close button close button

23
References: • • •
•

www.automotionparking.com/
www.automotionparking.com/.../pdf/Car_Parking_SP_System.pdf
www.electroautomation.com/ www.technovelgy.com/ct/Technology-Article.asp

24