R.P.

S INTERNATIONAL SCHOOL,
SECTOR -50, GURUGRAM

ACADEMIC YEAR: 2024-25

PROJECT REPORT ON

PARKING MANAGEMENT SYSTEM

ROLL NO :
NAME : JAI
CLASS : XII
SUBJECT : COMPUTER SCIENCE
SUB CODE : 083

PROJECT GUIDE: Ms. Neetu

PGT (CS)
R.P.S INTERNATIONAL SCHOOL,SEC-50,
GURUGRAM

1
 R.P.S INTERNATIONAL SCHOOL,
SECTOR-50, GURUGRAM

CERTIFICATE

This is to certify that “Parking Management System” is

submitted by the Jai under the supervision of Ms. Neetu in the
academic year 2024-25.

Sign of teacher Sign of external

2
 INDEX

SER DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 07

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 08

07 SOURCE CODE 17

08 OUTPUT 22

09 TESTING 24

10 HARDWARE AND SOFTWARE REQUIREMENTS 27

11 BIBLIOGRAPHY 28

3
 ACKNOWLEDGEMENT

I would like to express my special thanks of gratitude to my teacher Ms. Neetu

as well as our principal Dr. Pooja Sharma who gave me the golden opportunity to do

this wonderful project on the topic Parking Management System , which also helped

me in doing a lot of Research and I came to know about so many new things. I am

thankful to them.

Secondly, I would also like to thank my parents and friends who helped me a lot

in finalizing this project within the limited time frame.

4
 PROJECT ON PARKING MANAGEMENT
SYSTEM

INTRODUCTION

This project is all about a software for Parking Management System. It helps the

Parking owner to have a full-fledged control over his/her vehicles parked. It adds a

new car parked record, updates an existing record, and manage the records.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming

knowledge into a real- world situation/problem and exposed the students how

programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object-oriented programming principles effectively when developing

small to medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory, and software development.

5
 5. Students will demonstrate ability to conduct research or applied Computer

Science project, requiring writing and presentation skills which exemplify

scholarly style in computer science.

PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be really wants

to stand against today’s merciless competition where not to wise saying “to err is

human” no longer valid, it’s outdated to rationalize your mistake. So, to keep pace

with time, to bring about the best result without malfunctioning and greater efficiency

so to replace the unending heaps of flies with a much-sophisticated hard disk of the

computer.

One must use the data management software. Software has been an ascent in

atomization various organisations. Many software products working are now in

markets, which have helped in making the organizations work easier and efficiently.

Data management initially had to maintain a lot of ledgers and a lot of paperwork must

be done but now software product on this organization has made their work faster and

easier. Now only this software must be loaded on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully automated and

any information regarding the organization can be obtained by clicking the button.

Moreover, now it’s an age of computers of and automating such an organization gives

the better look.

6
 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that

divides complex projects into smaller, more easily managed segments or phases.

Segmenting projects allows managers to verify the successful completion of project

phases before allocating resources to subsequent phases.

Software development projects typically include initiation, planning, design,

development, testing, implementation, and maintenance phases. However, the phases

may be divided differently depending on the organization involved.

For example, initial project activities might be designated as request,

requirements-definition, and planning phases, or initiation, concept-development, and

planning phases. End users of the system under development should be involved in

7
reviewing the output of each phase to ensure the system is being built to deliver the

needed functionality.

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an

opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business accomplishments of the

organization or a deficiency related to a business need.

Identify significant assumptions and constraints on solutions to that need.

Recommend the exploration of alternative concepts and methods to satisfy the

need, including questioning the need for technology, i.e., will a change in the

business process offer a solution?

Assure executive business and executive technical sponsorship. The Sponsor

designates a Project Manager, and the business need is documented in a Concept

Proposal. The Concept Proposal includes information about the business process

and the relationship to the Agency/Organization.

Infrastructure and the Strategic Plan. A successful Concept Proposal results in a

Project Management Charter which outlines the authority of the project manager

to begin the project.

8
 Careful oversight is required to ensure projects support strategic business

objectives and resources are effectively implemented into an organization's enterprise

architecture. The initiation phase begins when an opportunity to add, improve, or

correct a system is identified and formally requested through the presentation of a

business case. The business case should, at a minimum, describe a proposal’s purpose,

identify expected benefits, and explain how the proposed system supports one of the

organization’s business strategies. The business case should also identify alternative

solutions and detail as many informational, functional, and network requirements as

possible.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership and the

Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.

Identify basic functional and data requirements to satisfy the business need.

Establish system boundaries; identify goals, objectives, critical success factors,

and performance measures.

Evaluate costs and benefits of alternative approaches to satisfy the basic

functional requirements.

Assess project risks.

9
 Identify and initiate risk mitigation actions, and develop high-level technical

architecture, process models, data models, and a concept of operations. This

phase explores potential technical solutions within the context of the business

need.

It may include several trade-off decisions such as the decision to use COTS

software products as opposed to developing custom software or reusing software

components, or the decision to use an incremental delivery versus a complete,

one-time deployment.

Construction of executable prototypes is encouraged to evaluate technology to

support the business process. The System Boundary Document serves as an

important reference document to support the Information Technology Project

Request (ITPR) process.

The ITPR must be approved by the State CIO before the project can move

forward.

PICTORIAL REPRESENTATION OF SDLC:

10
 PLANNING PHASE

The planning phase is the most critical step in completing development,

acquisition, and maintenance projects. Careful planning, particularly in the early stages

of a project, is necessary to coordinate activities and manage project risks effectively.

The depth and formality of project plans should be commensurate with the

characteristics and risks of a given project. Project plans refine the information

gathered during the initiation phase by further identifying the specific activities and

resources required to complete a project.

A critical part of a project manager’s job is to coordinate discussions between

user, audit, security, design, development, and network personnel to identify and

document as many functional, security, and network requirements as possible. During

this phase, a plan is developed that documents the approach to be used and includes a

discussion of methods, tools, tasks, resources, project schedules, and user input.

Personnel assignments, costs, project schedule, and target dates are established.

A Project Management Plan is created with components related to acquisition

planning, configuration management planning, quality assurance planning, concept of

operations, system security, verification and validation, and systems engineering

management planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements using

high-level requirements identified in the Initiation, System Concept, and Planning

phases. It also delineates the requirements in terms of data, system performance,

11
security, and maintainability requirements for the system. The requirements are

defined in this phase to a level of detail sufficient for systems design to proceed. They

need to be measurable, testable, and relate to the business need or opportunity

identified in the Initiation Phase. The requirements that will be used to determine

acceptance of the system are captured in the Test and Evaluation Master Plan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and document them

in the Requirements Document,

Complete business process reengineering of the functions to be supported (i.e.,

verify what information drives the business process, what information is generated,

who generates it, where does the information go, and who processes it),

Develop detailed data and process models (system inputs, outputs, and the process.

Develop the test and evaluation requirements that will be used to determine

acceptable system performance.

DESIGN PHASE

The design phase involves converting the informational, functional, and network

requirements identified during the initiation and planning phases into unified design

specifications that developers use to script programs during the development phase.

Program designs are constructed in various ways. Using a top-down approach,

designers first identify and link major program components and interfaces, then expand

design layouts as they identify and link smaller subsystems and connections. Using a

12
bottom-up approach, designers first identify and link minor program components and

interfaces, then expand design layouts as they identify and link larger systems and

connections. Contemporary design techniques often use prototyping tools that build

mock-up designs of items such as application screens, database layouts, and system

architectures. End users, designers, developers, database managers, and network

administrators should review and refine the prototyped designs in an iterative process

until they agree on an acceptable design. Audit, security, and quality assurance

personnel should be involved in the review and approval process. During this phase,

the system is designed to satisfy the functional requirements identified in the previous

phase. Since problems in the design phase could be very expensive to solve in the later

stage of the software development, a variety of elements are considered in the design to

mitigate risk. These include:

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.

Developing a conversion plan to migrate current data to the new system.

Determining the operating environment.

Defining major subsystems and their inputs and outputs.

Allocating processes to resources.

Preparing detailed logic specifications for each software module. The result is a

draft System Design Document which captures the preliminary design for the

system.

Everything requiring user input or approval is documented and reviewed by the

user. Once these documents have been approved by the Agency CIO and Business

13
Sponsor, the final System Design Document is created to serve as the

Critical/Detailed Design for the system.

This document receives a rigorous review by Agency technical and functional

representatives to ensure that it satisfies the business requirements. Concurrent

with the development of the system design, the Agency Project Manager begins

development of the Implementation Plan, Operations and Maintenance Manual,

and the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design specifications into

executable programs. Effective development standards include requirements that

programmers and other project participants discuss design specifications before

programming begins. The procedures help ensure programmers clearly understand

program designs and functional requirements. Programmers use various techniques

to develop computer programs. The large transaction-oriented programs associated

with financial institutions have traditionally been developed using procedural

programming techniques. Procedural programming involves the line-by-line

scripting of logical instructions that are combined to form a program. Effective

completion of the previous stages is a key factor in the success of the Development

phase. The Development phase consists of:

Translating the detailed requirements and design into system components.

Testing individual elements (units) for usability.

Preparing for integration and testing of the IT system.

14
 INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is

conducted during the integration and test phase. The user, with those responsible

for quality assurance, validates that the functional requirements, as defined in the

functional requirements document, are satisfied by the developed or modified

system. OIT Security staff assess the system security and issue a security

certification and accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly supported by

end users.

Testing as a deployed system with end users working together with contract

personnel.

Operational testing by the end user alone performing all functions. Requirements

are traced throughout testing a final Independent Verification & Validation

evaluation is performed and all documentation is reviewed and accepted prior to

acceptance of the system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and accepted by the user.

In this phase, the system is installed to support the intended business functions. System

performance is compared to performance objectives established during the planning

phase. Implementation includes user notification, user training, installation of

hardware, installation of software onto production computers, and integration of the

15
system into daily work processes. This phase continues until the system is operating in

production in accordance with the defined user requirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued

performance in accordance with user requirements and needed system modifications

are incorporated. Operations continue if the system can be effectively adapted to

respond to the organization’s needs. When modifications or changes are identified, the

system may re-enter the planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.

Conduct periodic assessments of the system to ensure the functional

requirements continue to be satisfied.

Determine when the system needs to be modernized, replaced, or retired.

16
 SOURCE CODE

import mysql.connector

mydb=mysql.connector.connect(host="localhost",user="root",password="1234",database='parking')

mycursor=mydb.cursor()

mysqlquery= 'create table parkmaster12(pid int(8) primary key,pnm varchar(30) not null,level varchar(30) not
null,freespace varchar(30)not null,vehicleno varchar(30) not null,nod varchar(30) not null, payment int(5) not
null);'

mycursor.execute(mysqlquery)

quer2='create table vehicle(vid int(8) primary key,vnm varchar(30) not null,dateofpur date);'

mycursor.execute(quer2)

import os

import platform

import mysql.connector

mydb=mysql.connector.connect(host="localhost",user="root",password="1234",database='parking')

mycursor=mydb.cursor()

def Add_Record():

L=[]

id1=int(input("Enter the parking number : "))

L.append(id1)

pname1=input("Enter the Parking Name: ")

L.append(pname1)

level1=input("Enter level of parking : ")

L.append(level1)

freespace1=input("Is there any freespace or not :YES/NO ")

L.append(freespace1)

vehicleno1=input("Enter the Vehicle Number : ")

L.append(vehicleno1)

nod1=int(input("Enter total number of days for parking: "))

L.append(nod1)

17
 if nod1==1:

Payment1=20

elif nod1==2:

Payment1=40

elif nod1==3:

Payment1=60

elif nod1==4:

Payment1=80

elif nod1==5:

Payment1=100

elif nod1==6:

Payment1=6969

L.append(Payment1)

stud=(L)

sql='insert into parkmaster12(pid,pnm,level,freespace,vehicleno,nod,payment)

values(%s,%s,%s,%s,%s,%s,%s)'

mycursor.execute(sql,stud)

mydb.commit()

def Rec_View():

print("Select the search criteria : ")

print("1. Parking Number")

print("2. Parking Name")

print("3. Level No")

print("4. All")

ch=int(input("Enter the choice : "))

if ch==1:

s=int(input("Enter Parking no : "))

rl=(s,)

sql="select * from parkmaster12 where pid=%s"

18
 mycursor.execute(sql,rl)

res=mycursor.fetchall()

elif ch==2:

s=input("Enter Parking Name : ")

rl=(s,)

sql="select * from parkmaster12 where pnm=%s"

mycursor.execute(sql,rl)

res=mycursor.fetchall()

elif ch==3:

s=int(input("Enter Level of Parking : "))

rl=(s,)

sql="select * from parkmaster12 where level=%s"

mycursor.execute(sql,rl)

res=mycursor.fetchall()

elif ch==4:

sql="select * from parkmaster12"

mycursor.execute(sql)

res=mycursor.fetchall()

print("Details about Parking are as follows : ")

print("(Parking Id,Parking Name,Level,FreeSpace(Y/N),Vehicle No,No of days for parking,Payment)")

for x in res:

print(x)

print('Task comple ted')

def Vehicle_Detail():

L=[]

vid1=int(input("Enter Vehicle No : "))

L.append(vid1)

vnm1=input("Enter Vehicle Name/Model Name : ")

L.append(vnm1)

19
 dateofpur1=input("Enter Year-Month-date of purchase : ")

L.append(dateofpur1)

vdt=(L)

sql="insert into vehicle(pid,vnm,dateofpur) values(%s,%s,%s)"

mycursor.execute(sql,vdt)

mydb.commit()

def Vehicle_View():

vid1=int(input("Enter the vehicle number of the vehicle whose details is to be viewed : "))

sql='select parkmaster12.pid,parkmaster12.pnm,parkmaster12.vehicleno, vehicle.pid,vehicle.vnm from

parkmaster12 INNER JOIN vehicle ON parkmaster12.pid=vehicle.pid and vehicle.pid=%s'

rl=(vid1,)

print('The following are the detailes you wanted:')

mycursor.execute(sql,rl)

res=mycursor.fetchall()

for x in res:

print(x)

print('Task compelted')

def remove():

vid1=int(input("Enter the vehicle number of the vehicle to be deleted : "))

rl=(vid1,)

sql="Delete from vehicle where pid=%s"

mycursor.execute(sql,rl)

mydb.commit()

print('Removed as per the command')

def Menu():

print("Enter 1 : To Add Parking Detail")

print("Enter 2 : To View Parking Detail ")

print("Enter 3 : To Add Vehicle Detail ")

print("Enter 4 : To Remove Vehicle Record")

print("Enter 5 : To see the details of Vehicle")

20
 input_dt = int(input("Please Select An Above Option: "))

if(input_dt== 1):

Add_Record()

elif (input_dt==2):

Rec_View()

elif (input_dt==3):

Vehicle_Detail()

elif (input_dt==4):

remove()

elif (input_dt==5):

Vehicle_View()

else:

print("Enter correct choice....")

Menu()

def runAgain():

runAgn=input('\nwant to run Again Y/n:')

while(runAgn.lower()=='y'):

if(platform.system()=='Windows'):

print(os.system('cls'))

else:

print(os.system('clear'))

Menu()

runAgn=input('\nwant to run Again Y/n:')

runAgain()

21
OUTPUT

22
23
 TESTING
Software Testing is an empirical investigation conducted to provide stakeholders

with information about the quality of the product or service under test, with respect to

the context in which it is intended to operate. Software Testing also provides an

objective, independent view of the software to allow the business to appreciate and

understand the risks at implementation of the software. Test techniques include, but are

not limited to, the process of executing a program or application with the intent of

finding software bugs.

It can also be stated as the process of validating and verifying that a software

program/application/product meets the business and technical requirements that guided

its design and development, so that it works as expected and can be implemented with

the same characteristics. Software Testing, depending on the testing method employed,

can be implemented at any time in the development process, however the most test

effort is employed after the requirements have been defined and coding process has

been completed.

TESTING METHODS

Software testing methods are traditionally divided into black box testing and

white box testing. These two approaches are used to describe the point of view that a

test engineer takes when designing test cases.

BLACK BOX TESTING

24
 Black box testing treats the software as a "black box," without any knowledge of

internal implementation. Black box testing methods include equivalence partitioning,

boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability

matrix, exploratory testing, and specification-based testing.

SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according to

the applicable requirements. Thus, the tester inputs data into, and only sees the output

from, the test object. This level of testing usually requires thorough test cases to be

provided to the tester, who then can simply verify that for a given input, the output

value (or behaviour), either "is" or "is not" the same as the expected value specified in

the test case. Specification-based testing is necessary, but it is insufficient to guard

against certain risks.

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's perception is

very simple: a code must have bugs. Using the principle, "Ask and you shall receive,"

black box testers find bugs where programmers don't. But, on the other hand, black box

testing has been said to be "like a walk in a dark labyrinth without a flashlight,"

because the tester doesn't know how the software being tested was constructed.

That's why there are situations when (1) a black box tester writes many test cases

to check something that can be tested by only one test case, and/or (2) some parts of

the back end are not tested at all. Therefore, black box testing has the advantage of "an

25
unaffiliated opinion," on the one hand, and the disadvantage of "blind exploring," on

the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has access

to the internal data structures and algorithms (and the code that implement these)

Types of white box testing: -

The following types of white box testing exist:

api testing - Testing of the application using Public and Private APIs.

Code coverage - creating tests to satisfy some criteria of code coverage.

For example, the test designer can create tests to cause all statements in the

program to be executed at least once.

fault injection methods.

mutation testing methods.

static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness of a

test suite that was created with black box testing methods. This allows the software

team to examine parts of a system that are rarely tested and ensures that the most

important function points have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and

26
 Statement Coverage: Which reports on the number of lines executed to

complete the test.

They both return coverage metric, measured as a percentage.

HARDWARE AND SOFTWARE REQUIREMENTS

1. OPERATING SYSTEM :WINDOWS 8 AND ABOVE

2. PROCESSOR :PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)

3. MOTHERBOARD :1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

4. RAM :512MB+

5. Hard disk :SATA 40 GB OR ABOVE

6. CD/DVD r/w multi drive combo: (If back up required)

7. MONITOR 14.1 or 15 -17 inch

8. Keyboard and mouse

9. Printer :required

SOFTWARE REQUIREMENTS:

I. Windows OS

II. Python

III. MySQL

27
BIBLIOGRAPHY

1. Computer science With Python - Class XI By : Sumita Arora

2. Website: https://www.youtube.com

28