+

AMRITA VIDYALAYAM
SENIOR SECONDARY, NAGAPATTINAM
CBSE AFFILIATION NO: 1930359

DEPARTMENT OF COMPUTER SCIENCE

2024 – 2025

MENTION YOUR PROJECT TITLE

NAME :
REGISTER NO :
CLASS :
SUBJECT : COMPUTER SCIENCE
SUBJECT CODE : 083
PROJECT GUIDE : Mrs. K. PRIYATHARSHINI
 AMRITA VIDYALAYAM
SENIOR SECONDARY, NAGAPATTINAM
CBSE AFFILIATION NO: 1930359

CERTIFICATE

This is to certified that your name of Class XII – A, Register No.

____________ has successfully completed the project under the guidance of

Mrs. K. PRIYATHARSHINI, PGT (COMP.) during the year 2024 – 2025 as

required according to the Central Board of Secondary Education.

Internal Examiner External Examiner

Date: Principal
 ACKOWLEDMENT
Apart from my efforts, the success of any project depends largely on the
encouragement and guidance of many others. I take this opportunity to express
my gratitude to the people who have been instrumental in the successful
completion of this project.
I express my deep sense of gratitude to the almighty God for giving me the
strength for the successful completion of the project.
I express my heartful gratitude to my parents for constant encouragement
while carrying out this project.
I grateful acknowledge the contribution of the individual who contributed
in bringing this project up to this level, who continues to look after me despite
my flaws.
I express my deep sense of gratitude to the luminary Mr. K Chinnaiyan,
Principal, Amrita Vidyalayam Senior Secondary, Nagapattinam who has been
continuously motivating and extending their helping hand to us.
I express my heartful gratitude to Mrs. K. PRIYATHARSHINI, Teacher,
Amrita Vidyalayam Senior Secondary, Nagapattinam In-charge, A Guide,
Mentor all the above a friend, who critically reviewed my project and helped in
solving each and every problem, occurred during implementation of the project.
The guidance and support received from all the members who contributed
and who are contributing to this, was vital for the success of the project. I am
grateful for their constant support and helps.
 PARKING MANAGEMENT SYSTEM
INTRODUCTION

The parking management helps us to enter, display or alter the details of vehicles in

parking records.

Moreover and most importantly the program helps us. The program also helps us to

know the present status of a parking detail, vehicle detail etc.

It includes various function programs to do the above mentioned tasks. Introduction

Data file handling has been effectively used in the program. The database is collection of

interrelated data to serve multiple applications. That is database program create files of

information. So we see that files are worked with most, inside the program.

There is greater sense of security due to the fact that patrons do not actually walk to

and from their own space. It is highly feasible for extremely small sites that are unable to

accommodate a conventional ramped parking structure.

It is possible that the retrieval time is lower than the combined

driving/parking/walking time in conventional ramped parking structures. There is easier

façade integration since there are no ramping floors or openings in exterior walls.
OBJECTIVE OF THE PROJECT

In this project we mainly focus on designing a new smart parking system that assists

drivers to find parking spaces in specific parking district. In addition, an important goal of

the system is to reduce traffic searching for parking, hence reduce energy consumption and

air pollution.

Moving on, this vehicle parking system project in python focuses mainly on dealing

with customer’s parking details with their number, and slot.

This report also describes the use of an UPS system from the entrance into a parking

lot until the finding of a vacant parking space.

In this project an LED display in the entrance of the parking will show to the drivers

which level of the parking has available space and which space is the closest to the driver.

Helps in parking centers in making their business more efficient. Complete

automation of the parking place. Automate vehicle registration processes to reduce manual

effort and errors. Track vehicle maintenance schedules to ensure optimal performance and

safety. Manage inventory of vehicles and spare parts efficiently to minimize downtime.

Provide real-time monitoring of vehicle status for better fleet management.

Enhance overall organization productivity by streamlining vehicle management tasks.

Improve accountability and transparency in vehicle-related operations through centralized

system access and tracking.

PROPOSED SYSTEM

There is a greater sense of security due to the fact that patrons do not actually walk to

and from their own space. Advantages of this project, it is highly feasible for extremely

small sites that are unable to accommodate a conventional ramped parking structure. There

is high parking efficiency (i.e. SF/Space and CF/Space).

There is no need for driving while looking for an available space. Emissions are

greatly brought down and reduced .The patrons wait for their car in a highly controlled

environment. There are less chances for vehicle vandalism .There is a minimal staff

requirement if it is used by known parkers.

It is possible that the retrieval time is lower than the driving/parking/walking time

combined in conventional ramped parking structures. Also, the system allows inserting

details of vehicle owners including their contact number, vehicle number, and vehicle

category.

But here, the system automatically sets a slot for reservation after inserting vehicle

details until the vehicle gets out.

Talking about parking slots, the system indicates empty and occupied slots with green

and red color respectively. In an overview of this app, the system displays all the parked

vehicles under the manage vehicles section where the user can cancel the parking once it’s

done.
SYTEM DEVELOPMENT LIFE CYCLE (SDLC)

The system development life cycle is a project management technique that divides complex
project 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 organisation 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 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 face begins when a business sponsor identify 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 a method 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. A 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
your project management chapter which outlines authority of the project
manager to begin the project.

Careful oversight is required to ensure project support strategic business objectives and
resources are effectively implemented into an organization’s enterprise architecture. The
initiation phase begins when an opportunity to add, modify, 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 organizations 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 developing phase begins after a business need or opportunity is
validated by 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 the 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.
Identify and initiate a risk mitigation action 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:

PLANNING PHASE
The planning phase is the most critical strip 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 risk effectively. The depth and
formality of project plans should be commensurate with the characteristics and risk of a
given project. Project plans refine the information gathered during the initiation phase by
further identifying the specific activities and resources to complete a project.

A critical part of your project manager’s job is to coordinate discussion 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 the documents the approach to be used and these 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 define the detailed functional user requirements using high level
requirements identified in the initiation, system concept and the planning phases. It also
delineates the 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 refined the functional and data requirements documents.

Complete business process re-engineering 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 model. (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 a planning phases into unified design
specifications that a developers used to script programs during the development phase.
Program designs are constructed in various ways. Using a top down approach, designer first
identify and link major program components and interfaces, then expand design layouts as
they identify and link smaller subsistence and connections. Using a bottom up approach,
designer first identify and link minor program components and the interfaces, then expand
design layouts as they identify and the link larger systems and connections.
 Contemporary design techniques often use proto typing tools that build mock-up
designs of items such as application screens, database layouts, and system architecture. 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
or considered in the design to mitigate risk. These include:

I did saying 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
the draft system design document, which capture 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 sponsor, the final system design document is created to serve as the
critical/detailed design for the system.
This document received a rigorous review by agency technical and functional
representatives to ensure that it is satisfy 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
under the training plan.
DEVELOPMENT PHASE
The development phase involves converting designs specifications into executable
programs. Effective development standards included requirements that programmers and the
other project participants discuss designs specifications before programming begins. The
procedures help ensure programmers clearly understand program designs and functional
recruitments. 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 your program.
Effective completion of the previous stages he see key factor in the success of the
development phase. The development phase consists of:

Translating the detailed recruitment Sunday design in two system components.

Testing individual elements for usability.
Preparing for integration and testing of the IT systems.

INTEGRATION AND TESTING 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
documents, are satisfied by the developed or modified system. OIT security staffs 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 the developed system with end users working together with the
contract personnel.
Operational testing by the end user alone performing all functions.
 Requirements are traced throughout testing, a final independent verification &
validation 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 indented business functions. System
performance is compared to performance objectives established during the planning phase.
Implementation includes used in notification, user training, installation of hardware,
installation of software on to protection computers and integration of the system into daily
work processes. This phase continues until the system is operating in protection in
accordance with the defined user requirements.

OPERATION AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued performance
in accordance with user requirements and needed system notifications are incorporated.
Operations continue as long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or change 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.
SOURCE CODE
OUTPUT:
TESTING
Software testing is an empirical investigation conducted to provide stakeholder with
information about the quality of the product or service under test [1], 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 includes, 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 you 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 and employed, can be
implemented at any time in the development process, however the most test effort is
employed after the requirement have been defined under 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 designer
takes when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box", without any knowledge of
internal implementation. Black box testing methods include: equal and partitioning,
boundary value analysis, all parts testing fuzz testing, model based testing, traceability
matrix, exploratory testing and specification based testing.
WHITE BOX TESTING
White box testing, by contrast to black box testing, is when the tester has access to the
internal data structure and algorithms.

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.
Fault Injection methods.
Static testing – White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing method can also be used to evaluate the completeness of your test
should created with a black box testing methods. This allows a software team to examine
parts of the system that are rally 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.

Statement coverage: Which reports on the number of lines executed to complete the test.
SPECIFICATION – BASED TESTING:

Specification-Based Testing uses the specification of the program as the point of

reference for test data selection and accuracy. Specification-based testing can be used to test
any type of system but is particularly well suited to testing systems with a well-defined
interface, such as web applications. Specification-based testing is a type of testing that uses a
formal specification of a software component to generate test cases.

Test cases are derived from the specifications by identifying the inputs and outputs
of the system and then determining the conditions under which the inputs should
produce the expected outputs.
These conditions can be specified in terms of equivalence classes, boundary values,
or other criteria. Once the test cases have been derived, they can be executed to
validate the system’s behavior.
The specification can be in the form of a requirements document, design document,
or code. The tester then writes test cases that exercise the different parts of the
specification.
HARDWARE AND SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

SOFTWARE REQUIREMENTS:
BIBLIOGRAPHY