VAILANKANNI PUBLIC SCHOOL (CBSE)

AFFILIATION NUMBER: 1931354

BARGUR - 635 104.

ACADEMIC YEAR: 2024–2025

COMPUTER SCIENCE

PROJECT REPORT ON
AUTOMOBILE MANAGEMENT SYSTEM

SUBMITTED BY: SUBMITTED TO:

 CERTIFICATE

This is to certify that the project report entitled on

Submitted to CENTRAL BOARD OF SECONDARY

EDUCATION in partial fulfillment to the requirement for the completion of ALL

INDIA SENIOR SECONDARY COMMON EXAMINATION is a record of original

work done by of VAILANKANNI PUBLIC

SCHOOL–BARGUR under my supervision and guidance during the period of 2024–25.

PROJECT VIVA– VOCE HELD ON

PRINCIPAL

INTERNALEXAMINER EXTERNALEXAMINER
 DECLARATION

I, hereby declare that the

project entitled submitted to

CENTRAL BOARD OF SECONDARY EDUCATION in partial completion of ALL INDIA

SENIOR SECONDARY COMMON EXAMINATION is a record of original and

independent project work done by me during 2024 – 2025 under the supervision and

guidance of ., PGT COMPUTER SCIENCE

VAILANKANNI PUBLIC SCHOOL– BARGUR

SIGNATURE OF THE CANDIDATE

 ACKNOWLEDGMENT

I Humbly prostate myself before almighty for grace abundant that enabled me to
complete this project successfully.

I remain indebted to the Correspondent VAILANKANNI PUBLIC SCHOOL–

BARGUR.to enrich my knowledge by using resource in the school campus.

I express my healthful thanks to MRS.MANJULA S, PRINCIPAL of

VAILANKANNI PUBLIC SCHOOL (CBSE) – BARGUR. For her valuable
suggestions and constant encouragement.

Foremost, I would like to express my deepened sincere gratitude to my

guide PGT Computer Science, VAILANKANNI
PUBLIC SCHOOL–BARGUR., I am Thankful for his eminent guidance, meticulous
care,inspiration,valuable suggestions, and constant encouragement given to me to shape
the project work, without whose timely and constant help, this project work would not
have been completed in time.

Above all, I wish to express my deep sense of gratitude and sincere thanks to my
teachers, parents and friends for their support and encouragement to achieve this
milestone.
 TABLE OF CONTENTS

SNO DESCRIPTION PAGE NO

01 INTRODUCTION

02 OBJECTIVES OF THE PROJECT

03 BRIEF OVERVIEW OF PROJECT

04 NEED FOR COMPUTERIZATION

05 SOFTWARE AND HARDWARE REQUIREMENT

06 ADVANTAGES OF PROJECT

07 LIMITATIONS OF PROJECT

08 PROPOSED SYSTEM

09 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

10 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

11 SOURCE CODE OF PROJECT

12 OUTPUT SCREENS

13 TESTING

14 FUTURE ENHANCEMENT OF PROJECT

15 BIBLIOGRAPHY
 PROJECT ON AUTOMOBILE MANAGEMENT
SYSTEM

1.INTRODUCTION
In today's fast-paced world, efficient data management systems
play a crucial role in streamlining operations across industries. The
"Automobile Management System" is designed to address the
challenges faced in managing automobile inventories. It serves as a
comprehensive solution for storing, updating, and accessing critical
data about automobiles with minimal effort.
This project leverages Python, a versatile programming language,
and MySQL, a robust relational database management system, to
build a reliable and user-friendly platform. The software eliminates
the need for traditional manual record-keeping methods, which are
often prone to human errors and inefficiencies.
By automating routine tasks, the system ensures data consistency
and significantly reduces the time required for inventory operations.
Users can perform operations such as adding new records, modifying
existing ones, and viewing the complete inventory with just a few
clicks.
Additionally, the project aligns with modern technological trends by
focusing on data-driven solutions that improve accuracy, efficiency,
and productivity. It demonstrates how software tools can be utilized
to transform traditional workflows into streamlined digital processes.
Overall, the "Automobile Management System" is a step forward in
simplifying inventory management, catering to the needs of
automobile dealers, workshop managers, and other stakeholders.
 2. Objectives of the Project

The "Automobile Management System" aims to fulfill several key

objectives that are vital for efficient inventory management:

1.Automation of Processes: Replace manual methods of managing

automobile data with a fully automated system.

2.User-Friendly Interface: Provide an easy-to-use platform that

requires minimal technical knowledge.

3.Accurate Record-Keeping: Ensure data integrity and consistency

across all operations.

4.Improved Accessibility: Enable quick and efficient retrieval of

information.

5.Cost and Time Efficiency: Reduce operational costs and save time
through automated processes.

6.Scalability: Design the system to handle increasing data volumes as

the inventory grows.

These objectives collectively aim to improve the overall efficiency

and reliability of inventory management processes in the automobile
sector.
 3.Brief Overview of the Project

The "Automobile Management System" is a Python-based software

application that interacts with a MySQL database to manage
automobile inventory. It provides functionality to add, update, delete,
and view records of automobiles in a user-friendly manner.
The project uses the following components:

• Python: For creating the interface and handling logic.

• MySQL: For storing and retrieving automobile data.
• Structured Queries: To ensure efficient data handling and
retrieval.

Key features include:

• Adding automobile details such as make, model, year, and price.

• Modifying existing records to reflect updates in inventory.
• Removing outdated or incorrect entries.
• Viewing a complete list of automobiles with details presented in a
tabular format.

The project is designed to streamline operations for businesses such as

automobile dealers, workshops, and showrooms.
 4. Need for Computerization

Managing inventory manually often leads to errors, inefficiencies, and

delays. In the automobile industry, these issues can result in significant
losses, such as misplaced records, delayed customer service, and
inaccurate pricing.

Computerization addresses these challenges by providing a reliable,

fast, and efficient way to handle data. The "Automobile Management
System" offers the following advantages of computerization:

• Data Accuracy: Minimizes human errors and ensures precise

record-keeping.

• Efficiency: Speeds up processes such as data retrieval and

updates.

• Cost Reduction: Reduces the need for physical storage and

manual labor.

• Improved Customer Service: Enables quick access to data,

ensuring timely responses to customer inquiries.

• Scalability: Easily handles an increasing volume of data as the

business grows.

By adopting a computerized system, businesses can significantly

enhance their operational efficiency and competitiveness.
 5.SOFTWARE AND HARDWARE REQUIREMENTS

I. OPERATING SYSTEM : WINDOWS 10 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)
III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

1. K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON
IV. RAM : 512 MB+

V. Hard disk : SATA 40 GB OR ABOVE

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

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : required

XI. SOFTWARE REQUIREMENTS:

a. Windows OS
b. Python
c. MySQL
 6. Advantages of the Project

The "Automobile Management System" offers several advantages

that make it a valuable tool for inventory management:

1. Time-Saving: Automated processes significantly reduce the

time required for routine tasks.

2. Accuracy: Ensures data consistency and minimizes errors in

record-keeping.

3. User-Friendly: The intuitive interface makes it easy for users to

operate without extensive training.

4. Centralized Database: All data is stored in a single location,

making it easier to manage and access.

5. Customizability: The system can be tailored to meet the

specific needs of different businesses.

6. Cost-Effective: Reduces the need for extensive paperwork and

manual labor.

7. Scalable: Designed to handle a growing number of records as

the business expands.
 7.LIMITATIONS OF PROJECT

While the "Automobile Management System" offers many benefits,

it also has certain limitations:

1. Local Deployment: The current version is limited to local

systems and does not support remote access.

2. Performance Constraints: Handling very large datasets may

affect system performance.

3. Technical Knowledge: Users need basic familiarity with

computers and database management.

4. Lack of Advanced Features: The system does not include

analytics or reporting capabilities.

5. Security: As a standalone system, it lacks advanced security

features like encryption.
6. These limitations can be addressed in future enhancements.
 8. 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 has to use the data management software. Software has

been an ascent inatomization various organizations. 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 paper work has to
be done but now software product on this organization has made their
work faster and easier. Now only this software has to 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.
 9.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 reviewing the output of
each phase to ensure the system is being built to deliver the needed
functionality.
 10.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 andthe
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.
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
• Identify and initiate risk mitigation actions, andDevelop 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, onetime
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 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’ sjob 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, security,
and maintainability requirements for the system. The requirements
are defined in this phase to alevel 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 MasterPlan.
The purposes of this phase are to:
o Further define and refine the functional and data
requirements and document them in the Requirements
Document,
o 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),
o Develop detailed data and process models (system inputs,
outputs, and the process.
o 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 scriptprograms 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 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 Sponsor, the final System Design
Document is created to serve as the Critical/Detailed Design for
the system.
This document receives a rigorous review byAgency 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.
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 reviewedand 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 system into daily work
processes. This phase continues until the system is operating in
production in accordance with the defined userrequirements.

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
as long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or changes are identified,
the system may reenter 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.
 11.SOURCE CODE OF PROJECT
import mysql.connector as sql

# Database connection
def get_db_connection():
return sql.connect(host="localhost", user="root",
password="vps123", database="automobile")

# Function to create tables if not exists

def initialize_database():
db = get_db_connection()
cursor = db.cursor()
cursor.execute("""
CREATE TABLE IF NOT EXISTS automobiles (
id INT AUTO_INCREMENT PRIMARY KEY,
make VARCHAR(255),
model VARCHAR(255),
year INT,
price DECIMAL(10, 2)
)
""")
db.commit()
db.close()

# Add a new automobile

def add_automobile():
db = get_db_connection()
cursor = db.cursor()

make = input("Enter automobile make: ")

model = input("Enter automobile model: ")
 year = int(input("Enter manufacture year: "))
price = float(input("Enter price: "))

query = "INSERT INTO automobiles (make, model, year, price)

VALUES (%s, %s, %s, %s)"
cursor.execute(query, (make, model, year, price))

db.commit()
print("Automobile added successfully.")
db.close()

# Update automobile details

def update_automobile():
db = get_db_connection()
cursor = db.cursor()

id = int(input("Enter automobile ID to update: "))

print("1. Update Make")
print("2. Update Model")
print("3. Update Year")
print("4. Update Price")
choice = int(input("Enter your choice: "))

if choice == 1:
new_make = input("Enter new make: ")
query = "UPDATE automobiles SET make = %s WHERE id = %s"
cursor.execute(query, (new_make, id))
elif choice == 2:
new_model = input("Enter new model: ")
query = "UPDATE automobiles SET model = %s WHERE id = %s"
cursor.execute(query, (new_model, id))
elif choice == 3:
 new_year = int(input("Enter new year: "))
query = "UPDATE automobiles SET year = %s WHERE id = %s"
cursor.execute(query, (new_year, id))
elif choice == 4:
new_price = float(input("Enter new price: "))
query = "UPDATE automobiles SET price = %s WHERE id = %s"
cursor.execute(query, (new_price, id))
else:
print("Invalid choice.")
db.close()
return

db.commit()
print("Automobile updated successfully.")
db.close()

# Delete an automobile
def delete_automobile():
db = get_db_connection()
cursor = db.cursor()

id = int(input("Enter automobile ID to delete: "))

query = "DELETE FROM automobiles WHERE id = %s"
cursor.execute(query, (id,))

db.commit()
print("Automobile deleted successfully.")
db.close()

# View all automobiles

def view_automobiles():
db = get_db_connection()
 cursor = db.cursor()

query = "SELECT * FROM automobiles"

cursor.execute(query)
results = cursor.fetchall()

print("---------- Automobile List ----------")

print(f"{'ID':<5} {'Make':<15} {'Model':<15} {'Year':<10} {'Price':<10}")
print("-" * 50)
for row in results:
print(f"{row[0]:<5} {row[1]:<15} {row[2]:<15} {row[3]:<10}
{row[4]:<10}")
print("-" * 50)

db.close()

# Main menu for the system

def main_menu():
initialize_database()
while True:
print("\n---------- Automobile Management System ----------")
print("1. Add Automobile")
print("2. Update Automobile")
print("3. Delete Automobile")
print("4. View All Automobiles")
print("5. Exit")

choice = int(input("Enter your choice: "))

if choice == 1:
add_automobile()
elif choice == 2:
 update_automobile()
elif choice == 3:
delete_automobile()
elif choice == 4:
view_automobiles()
elif choice == 5:
print("Exiting system. Goodbye!")
break
else:
print("Invalid choice. Please try again.")

# Run the system

if __name__ == "__main__":
main_menu()
 12.OUTPUT SCREENS

---------- Automobile Management System ----------

1. Add Automobile
2. Update Automobile
3. Delete Automobile
4. View All Automobiles
5. Exit
Enter your choice: 1
Enter automobile make: toyota 1935
Enter automobile model: 2024
Enter manufacture year: 2024
Enter price: 500000
Automobile added successfully.

---------- Automobile Management System ----------

1. Add Automobile
2. Update Automobile
3. Delete Automobile
4. View All Automobiles
5. Exit
Enter your choice: 4
---------- Automobile List ----------
ID Make Model Year Price
--------------------------------------------------
1 bike 2025 2024 100000.00
2 car 2024 2024 100000.00
3 toyota 1935 2024 2024 500000.00
--------------------------------------------------

---------- Automobile Management System ----------

1. Add Automobile
2. Update Automobile
3. Delete Automobile
4. View All Automobiles
5. Exit
Enter your choice: 2
Enter automobile ID to update: 2
1. Update Make
2. Update Model
3. Update Year
4. Update Price
Enter your choice: 4
Enter new price: 700000
Automobile updated successfully.

---------- Automobile Management System ----------

1. Add Automobile
2. Update Automobile
3. Delete Automobile
4. View All Automobiles
5. Exit
Enter your choice: 3
Enter automobile ID to delete: 3
Automobile deleted successfully.

---------- Automobile Management System ----------

1. Add Automobile
2. Update Automobile
3. Delete Automobile
4. View All Automobiles
5. Exit
Enter your choice: 4
---------- Automobile List ----------
ID Make Model Year Price
--------------------------------------------------
1 bike 2025 2024 100000.00
2 car 2024 2024 700000.00
--------------------------------------------------

---------- Automobile Management System ----------

1. Add Automobile
2. Update Automobile
3. Delete Automobile
4. View All Automobiles
5. Exit
Enter your choice:
 13.TESTING
Software Testing is an empirical investigation conducted to provide
stakeholders 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 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
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.[16] 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 actually 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 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

Statement Coverage: Which reports on the number of

lines executed to complete the test.
 14.FUTURE ENHANCEMENT OF PROJECT

The "Automobile Management System" has been designed with

scalability and future improvements in mind. Possible enhancements
include:

1. Web-Based Interface: Developing a web application to enable

remote access and multi-user functionality.

2. Advanced Analytics: Introducing features to analyze trends and

generate insights from inventory data.

3. Enhanced Security: Adding encryption and multi-factor

authentication for data protection.

4. Report Generation: Including options to export data as reports in

formats like PDF or Excel.

5. Mobile Application: Creating a mobile version of the system for

on-the-go access.

6. Cloud Integration: Storing data on the cloud for improved

accessibility and scalability.

These enhancements will further improve the system's utility and

applicability in the automobile industry.
 15.BIBLIOGRAPHY

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

2. Computer science With Python - Class XI By : Preeti Arora
3. News API - https://newsapi.org
4. Wikipedia - https://www.wikipedia.org
5. Python - https://www.python.org
6. MySQL - https://www.mysql.com
7. Website: https://www.youtube.com
8. Website: https://www.w3resource.com