SCAN SBV NO.

2 B-BLOCK
JANAKPURI NEW DELHI
110058

REPRESENTED TO :- MR. GANESH NARAIAN MEENA

PRACTICAL FILE OF COMPUTER

SCIENCE

NAME :- KRRISH TIWARI

ROLL NO. :- 26702383
CLASS & SEC. :- XII thA
 SCAN SBV NO.2 B-BLOCK
JANAKPURI NEW DELHI
110058

A PROJECT REPORT ON
“Auto Mobile Service Station”

SUBMITTED TO :- SUBMITTED BY :-
MR. GANESH NARAIAN MR. KRRISH TIWARI
MEENA CLASS & SEC.:-XII thA CS
P.G.T (COMP. SCI.) ROLL NO. :- 26702383
 TABLE OF CONTENTS [ T O C ]

S. No. DESCRIPTION PAGE NO

1. ACKNOWLEDGEMENT

2. INTRODUCTION

3. OBJECTIVES OF THE PROJECT

4. PROPOSED SYSTEM

5. SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

6. PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

7. FLOW CHART

8. SOURCE CODE

9. OUTPUT

10. TESTING

11. HARDWARE AND SOFTWARE REQUIREMENTS

12. BIBLIOGRAPHY
ACKNOWLEDGEMENT
It is with pleasure that I acknowledge my sincere
gratitude to our teacher, MR. GANESH NARAIAN
MEENA who taught and undertook the responsibility
of teaching the subject Computer Science. I have been
greatly benefited from his classes.
I am especially indebted to our Principle MR. INDER
KUMAR who has always been a source of
encouragement and support and without whose
inspiration this project would not have been a
successful I would like to place record Heartfelt thanks
to him.
Finally, I would like to express my sincere appreciation
for all the other students for my batch their friendship
& the fine times that we all shared together.
 Introduction of the Project
This project automates the E – COMMERCE DATABASE MANAGEMENT SYSTEM which gives the
user three different options through which they can search for the product of their choice, and
finally place their orders.

The first option is to search through various categories of products, for e.g. Smartphones, Clothes,
Groceries, etc.

The user can choose their category and they will be shown all the products available in that
particular category.

The second option is to take a look at all the products available. The user can choose to take a look
all the different types of products available and choose their product from there.

The third option is to search through the various brands available. The user can choose to take a
look at all the brands available and choose a particular brand. On choosing the particular brand
the user will be shown all the products that are available from that particular brand.

Lastly, the user can place an order of their product of choice. On placing the order of a particular
product, that product is added

into the order_table in the database with various other details like the transaction ID (which is
allotted to every transaction that has been made), product ID, product name, date of dispatch and
the contact details of the customer.

Also the quantity of the product which has been ordered is reduced by 1 from the main_table.
 OBJECTIVES OF THE PROJECT

The objective of a computer program for e-commerce is to provide a seamless, secure, and efficient

platform for buying and selling goods or services online. The program aims to facilitate various

aspects of the e-commerce process, including product browsing, order management, payment

processing, customer interaction, and inventory tracking. By integrating key features like a user-

friendly interface, secure payment gateways, real-time updates, and responsive design, the program

seeks to enhance customer satisfaction, optimize business operations, and drive sales growth for the

online store. Additionally, it aims to support scalability and adaptability to accommodate growing

market demands and technological advancements.

The objective of a computer program for e-commerce is to create a comprehensive and dynamic

digital ecosystem that facilitates the entire process of online buying and selling of goods and

services. This system is designed to ensure smooth, efficient, and secure transactions between

buyers, sellers, and service providers while enhancing the overall user experience. Below is a

detailed breakdown of the specific objectives.

In summary, the objective of a computer program for e-commerce is to build a robust, secure, and

efficient platform that meets the needs of both customers and businesses. It should foster a smooth

transaction process, enhance user experience, support business growth, and ensure secure and

compliant operations while adapting to future demands and technological advancements.

 PROPOSED SYSTEM
The proposed system for an e-commerce platform aims to create a robust, scalable, and
secure online marketplace that effectively supports the buying and selling of goods and
services. The system will be designed to handle a variety of e-commerce operations,
including product catalog management, order processing, secure payment handling,
customer relationship management, inventory management, and marketing.

System Overview

The system will be a web-based application with mobile compatibility, designed to cater to
both the customer and the admin (business owner) needs. It will consist of several
interrelated components that will work together to provide a seamless and secure online
shopping experience. Key features will include product browsing, payment processing, order
management, user profiles, customer support, and business analytics. In summary, the
objective of a computer program for e-commerce is to build a robust, secure, and efficient
platform that meets the needs of both customers and businesses. It should foster a smooth
transaction process, enhance user experience, support business growth, and ensure secure
and compliant operations while adapting to future demands and technological
advancements.

Conclusion

The proposed e-commerce system is designed to be a comprehensive solution that

streamlines online business operations, enhances the customer experience, and ensures
security and scalability. By integrating features such as product management, secure
payment processing, real-time inventory tracking, and customer relationship management,
the system aims to optimize both the customer shopping experience and the administrative

efficiency of the business.

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.
 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.

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, 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, 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’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, 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 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 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-byline 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 assesses 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 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 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.

FLOW CHART
Start
|
v
[User Visits Website]
|
v
[User Browses Products]
|
v
[User Selects Product]
|
v
[User Adds Product to Cart]
|
v
[User Proceeds to Checkout]
|
v
[User Logs In/Registers] <------------------- No
------------------> [Proceed As Guest]
|
v
[User Enters Shipping Information]
|
v
[User Chooses Payment Method]
 |
v
[User Reviews Order]
|
v
[User Confirms Purchase]
|
v
[Payment Processing]
|
v
[Payment Success?]
|
|
v
v
[Yes]
[No]
|
|
v
v
[Order Confirmation]
[Payment Failed Message]
|
v
[Send Order Details to User]
|
v
[Send Order to Warehouse for Fulfillment]
|
v
[Shipping/Delivery Process]
 |
v
[Order Delivered to User]
|
v
[User Confirms Receipt]
|
v
[End]
SOURCE CODE
OUTPUT
 TESTING
Software Testing is an empirical investigation conducted to provide With
Information about the quality of the product or service under test stakeholders
a with respect to the context 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. These
one 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, modelbased
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 through
test cases to be provided to the tester, who they test that for a given input.
The output value (or behaviour), either RUUPE 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.

HARDWARE AND SOFTWARE REQUIREMENTS

Recommended System Requirements:
Processors: Intel® Core™ i3 processor 4300M at 2.60 GHz.
RAM: 2 to 4 GB.
Operating systems: Windows® 10, MACOS, and UBUNTU.
Python Versions: 3.10.2 or Higher. With
mysql.connector module installed
MYSQL Versions: 8.0.28 or Higher.

Minimum System Requirements Processors:

Intel Atom® processor or Intel® Core™ i3 processor.
Disk space: 512 GB to 1TB.
Operating systems: Windows 8 or later, MACOS, and
UBUNTU.
Python Versions: 2.7.X, 3.6.X

Prerequisites before installing MySQL Connector

Python
You need root or administrator privileges to perform the
installation process. Python must be installed on your machine.
Note: – MySQL Connector Python requires python to be in the
system’s PATH. Installation fails if it doesn’t find Python.

On Windows, If Python doesn’t exist in the system’s PATH,

Please manually add the directory containing python.exe

yourself

BIBLIOGRAPHY
1. python.org
2. Wikipedia
3. Our Subject Teacher Ganesh Kumar Meena
4. Preeti Arora and Sumita Arora python books
5. LearnPython.org
6. Google