srs-ipas

Software Requirements Specification

For

iINTELLIGENT PARKING ASSISTANCE SIMULATOR

ABHIMANYU KAKKAR (0706413001)HARSH RAJPAL (0706440046)MANWENDRA KUMAR (0706413064)

(DEPARTMENT OF INFORMATION TECHNOLOGY)

HINDUSTAN COLLEGE OF SCIENCE & TECHNOLOGY, FARAH,MATHURA

(OCTOBER 16, 2010)

Software Requirements Specification for IPAS(Intelligent Parking Assistant Simulator) Page ii

Table of ContentsTable of Contents iiRevision History ii1. Introduction 1

1.1 Purpose 11.2 Document Overview 11.3 Intended Audience and Reading Suggestions 11.4 Product Scope 11.5 References 1

2. Overall Description 22.1 Product Perspective 22.2 User Classes and Characteristics 22.3 Operating Environment 22.4 Design and Implementation Constraints 22.5 Assumptions and Dependencies 3

3. External Interface Requirements33.1 User Interfaces 33.2 Hardware Interfaces 33.3 Software Interfaces 33.4 Communications Interfaces 3

4. System Features 44.1 System Feature 1 44.2 System Feature 2 4

4.2 System Feature 3……………………………………………………………………………………………………………45. Other Nonfunctional Requirements 4

5.1 Performance Requirements 45.2 Safety Requirements 55.3 Security Requirements 55.4 Software Quality Attributes 5

6. Other Requirements 5Appendix A: Glossary 5Appendix B: Analysis Models5

Revision History

Name Date Reason For Changes Version

Software Requirements Specification for IPAS(Intelligent Parking Assistant Simulator)Page 1

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the IPAS(Intelligent Parking Assistant Simulator). It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli.

1.2 Document Overview

This document includes the previous works of others and references taken from the past researches made and by other professors from various universities and governmental department of various countries relative to the objective of IPAS. The detailed methodology of implementation of the API along with the various search algorithms and techniques to obtain the desired results. This includes the process of how the user gains access to the system and uses the services provided, including the navigation system and parking space information.The conclusion includes the further work that can be done in the direction of improvement of the project so as to make it feasible for real world implementation and to provide better services to the people associated with the system.

1.3 Product Scope

IPAS aims to achieve following objectives:Lot-Specific Parking Information Systems- Lot-specific systems provide parking information using signs that typically have both passive and active components. Space- Specific Parking Information Systems- In addition to providing information about which lots are full and how many spaces are available at remaining lots, more complex advanced parking information systems have signs on every floor of a garage, at the start of every aisle, and sometimes in front of every individual parking space.Parking Navigation Systems- The most sophisticated type of IPAS is one that guides the traveler to an open spot. The use of this API will be made to facilitate the users to guide themselves to the parking area in case of them being in an unknown land.Security System- The main feature of IPAS is security system. IPAS would not allow any unauthorized vehicle to park in and immediately reports a danger signal. It helps in detecting the suspicious vehicle and those vehicles, which have been stolen.Parking Site system- Another main feature of IPAS is that it provides a simple and user friendly computerized panel to parking site owners, so that they can easily handles the traffic and their accounts.


Furthermore, the scope of IPAS extends to:Access Control SystemSecurity SystemStatistical Information SystemNavigation System

1.4 References

IEEE.

1. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications.

IEEE Computer Society, 1998.

2. http://www.cse.msu.edu/~chengb/RE-491/Papers/SRSExample-webapp.doc.

2. Overall Description

2.1 Product Perspective

The IPAS model has been developed according to two principles.

First, it is a spatially explicit model, which builds on high-resolution urban Google Maps with layers representing every element of the traffic infrastructure important for investigating the parking process–street segments, on-street parking places, off-street parking places, and buildings.

Second, it is an agent-based model, which directly represents every driver who drives to the destination, searches for a parking place, parks, and leaves the parking place when his activity has ended. This model uses heuristic search techniques along with the shortest path algorithm and Google Maps. The Ajax technology helps to correlate with the above used API to provide necessary result. IPAS is the advancement of the efforts laid in DOWNTOWN PARKING MANAGEMENT PLAN in California on November 19, 2007 by Carl Walker, Inc., Spark Parking, Inc., Spencer Consulting Services, and, ADVANCED PARKING MANAGEMENT SYSTEMS in Washington on January 2007, by Jeffrey F. Paniati, Associate Administrator for Operations, Federal Highway Administration, US.

2.2 User Classes and Characteristics

There are basically 4 types of user:System Admin: This user has highest level of privileges. This user can perform all administrative functions.Registered User: This user can use all the service of system by just login into his account.


Unregistered User: This user has very limited access; If he want to use the service the he must first register himself.Parking Site Owner: This user can track details about any vehicle, any user, Date/Time of entering and departure.Characteristics of different users can be shown by:

s

2.3 Design and Implementation Constraints

There are mainly following design and implementation constraints:-

First, RTO, POLICE department should be digitized. Second, the databases of RTO and POLICE should be available to the system proposed, So

these databases should be centralized. The main feature “navigation system” should be implemented with higher resolution map. There should be an efficient algorithm to calculate distance and generate path on map

efficiently.

2.4 Assumptions and Dependencies

The System is based on the assumption that RTO, POLICE databases are centralized with this system as well as they can be accessed by this system.

At the client side there is a necessity of computer system and internet. All stolen vehicles should be reported and registered in POLICE database.


3. External Interface Requirements

3.1 User Interfaces

User Interface of the system includes web page to login, if the user is registered previously.If the user is new to the system, then he has to first must register himself. For Login and registration two different forms are provided.After login user can fill the parameters such as longitude, latitude to find the nearest parking available.After processing these parameters, the map is generated, which can be shown on web browser with path to the parking spaces.

3.2 Hardware Interfaces

Client Side:


Processor RAM

Pentium II at 500 GHz 64 MB

Server side:

Processor RAM Hard Disk Space

Pentium III at 1 GHz 256 MB 20 GB

3.3 Software Interfaces

Client Side:

Web Browser : Internet Explorer 8.0

Server Side:

Application Architecture : J2EE

Database : SQL Server

Google API :

Web Server : Apache Tomcat

3.4 Communications Interfaces

The user will use HTTP protocol to access system on web.The SOAP architecture consists of several layers of specifications for message format, message exchange patterns (MEP), underlying transport protocol bindings, message processing models, and protocol extensibility.SOAP is a simple XML-based protocol to let applications exchange information over HTTP.HTTP has gained wider acceptance as it works well with today's Internet infrastructure; specifically, HTTP works well with network firewalls.

4. System FeaturesThis system include following different features such as :-

It should provide ‘LOT SPECIFIC AND SPACE SPECIFIC PARKING’. It should perform as ‘PARKING NAVIGATION SYSTEM’. It should act as ‘SECURITY SYSTEM’. It should have information system feature ‘PARKING SITE RECORDS SYSTEM’.


4.1 System Feature : LOT SPECIFIC AND SPACE SPECIFIC PARKING.

4.1.1 Description and Priority

Whenever a user enters into a parking lot or leaves from a parking lot, a counter about the no of spaces available of two wheeler and four wheeler increases and decreases. So at the time of users query we make that data available to the user about the number of four wheelers already parked and how many can be parked. It gives the space specific parking site information. We also provide the parking fees using the amount field in the database, which is already known for every site. For providing a lot specific parking site we use a shortest path algorithm on the distance parameter of each site. Use of earlier algo will give us the lot specific parking site.

4.1.2 Stimulus/Response Sequences

User query about parking space. The no. of space available are shown, and how many are already filled are also shown. For lot specific parking, shortest path algorithm is used.

4.1.3 Functional Requirements

For space specific parking, we use a counter and a hardware device.counter automatialy updates database, when some vehicle enters or outs.

For lot specific parking ,there should be devised some efficient shortest path algorithm.

4.2 System Feature : PARKING NAVIGATION SYSTEM.


User has to give the location where he wants to find the parking site. After the input simulator processes the input and provide the map, which shows the path of the nearest parking site. It will act as a navigation system for the user.

4.2.2 Stimulus/Response Sequences

User enters longitude, latitude parameters. Simulator processes input and map is generated.


There should be some technology which processes data and generates map on web browser ,such as Google API.

4.3 System Feature : SECURITY SYSTEM


Whenever a user enters into a parking site, its entering time loads into the database, and when he came out an out time loads, so whenever a user exceeds certain time limit or he extends his parking time a notification will generate to the officials regarding this. Secondly at the time of entrance in parking site user gets authenticated through the RTO database and the valid identity card to check any unauthorized usage of vehicles. Thirdly, whenever a car have been stolen an


entry in the reported vehicle database will insert. Whenever user comes system also checks whether the car is the reported one or not. Fourthly, system regularly keep checking that no two vehicles have the same registration number while vehicle gets parked.

Stimulus/Response Sequences

User login in his account. If user is new then he has to register himself first. Path is generated on map. Vehicle enters in parking. It is validated from RTO and POLICE database. If it is suspicious, or time limit exceeds the allotted time then notification is generated.


There should be some technology such as Ajax, for displaying information without refreshing the whole page. So that the notifications are generated.

4.4 System Feature : PARKING SITE RECORDS SYSTEM.


There are several database tables which are used for maintaining the record of the parking site. It will generate daily report and the details of different users and many other information.

Stimulus/Response Sequence

Based upon information of User such as Date/Time of entering, and of going out reports are generated.

Information about suspicious vehicles/users are maintained separately.


There should be some technology which provide integration of all these facilities, as well as provide centrality to different databases. SQL Server and AJAX can be used, and architecture J2EE can be used.

Other Nonfunctional Requirements

4.5 Performance Requirements

Database should be automatically updated when vehicle enters and goes outside, so there is always correct knowledge to the user about the space available in the parking.User should be provided with correct path to the appropriate parking on the map.


4.6 Safety Requirements

The project is web application project , anybody can use it from their house , It is always safe to search for parking form their house rather than going outside and the searching for it. As we are using web so it should be safe, so login facilities is provided.

4.7 Security Requirements

1. First at the time of entrance in parking site user should be authenticated through the RTO database and the valid identity card to check any unauthorized usage of vehicles.

2. Secondly, whenever a car have been stolen an entry in the reported vehicle database will insert. Whenever user comes system should also check whether the car is the reported one or not.

3. Thirdly, system should regularly keep checking that no two vehicles have the same registration number while vehicle gets parked.

4.8 Software Quality Attributes

The System should satisfy some Software Quality Attributes. Some of which are:-

Availability: It should be easily available, as awe are going to develop web application project ,so it is easily available. Correctness: As much possible, it should provide correct path and distance to the appropriate parking. Flexibility: It should be flexible enough so that it can be modified later if any functionalty is to be added.Portability:It should provide portability because it is a web project. Reliability:It should be enough reliable. Usability:As everybody needs to park their vehicle safe, so it is Usable to the most of vehicle owners.

Appendix A: Glossary

Term DefinitionAdmin Person responsible for managing the whole system. He has

the highest level of authority.Database Collection of all the information monitored by this system.Parking Site Owner Person having their parking site available on system will

have facility for tracking suspicious vehicles, their time of entering, departure etc.

Reader Anyone visiting the site to read articles.


Registered UserA user which is registered can use the services any time by just login to their account.

RTO Department which maintains information about different vehicles.

Software Requirements Specification

A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document.

Unregistered User Person which is not registered on the system have a limited access. For using services he has to first register himself.

Appendix B: Analysis Models

The Working of whole system will be based on the above analysis model.

srs-ipas

Documents

parking navigation system

system features

security system

parking site records

security requirements

software interfaces

performance requirements

safety requirements