0% found this document useful (0 votes)
5 views35 pages

Mr. Prakash Chandra Srivastava KV No.1 AFS Chakeri, Kanpur: PGT (Computer Science)

The document is a project report by Anand on a 'Courier Service System' developed for the academic year 2024-2025 under the guidance of Mr. Prakash Chandra Srivastava. It outlines the project's objectives, proposed system, and the System Development Life Cycle (SDLC) phases, detailing the methodology for developing the software. The report includes acknowledgments, a table of contents, and source code for the application.

Uploaded by

anandbhai1551
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views35 pages

Mr. Prakash Chandra Srivastava KV No.1 AFS Chakeri, Kanpur: PGT (Computer Science)

The document is a project report by Anand on a 'Courier Service System' developed for the academic year 2024-2025 under the guidance of Mr. Prakash Chandra Srivastava. It outlines the project's objectives, proposed system, and the System Development Life Cycle (SDLC) phases, detailing the methodology for developing the software. The report includes acknowledgments, a table of contents, and source code for the application.

Uploaded by

anandbhai1551
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 35

PROJECT GUIDE : Mr.

Prakash Chandra Srivastava


PGT (Computer Science)
KV No.1 AFS Chakeri, Kanpur KV
NO 1 AFS CHAKERI

ACADEMIC YEAR : 2024-2025

PROJECT REPORT ON

Courier service system:

ROLL NO : 23699503

NAME : ANAND

CLASS : XII-A

SUBJECT : COMPUTER SCIENCE

SUB CODE : 083

Page 1 of 35
CERTIFICATE

This is to certify that Anand of class XIIA,


has prepared the report on the
project entitled ‘courier service
system’ . The report is the result
of his effort and endeavors . The
report is found worthy of
acceptance as final project report
for the subject of Computer
Science of class XII under
the CBSE curriculum 2024-25.
He has prepared the
report under my guidance .

PRAKASH CHANDRA SRIVASTAVA

PGT(COMPUTER SCIENCE)

KV NO 1 AFS CHAKERI KANPUR

TABLE OF CONTENTS [ T O C ]

Page 2 of 35
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 FLOW CHART 15

08 SOURCE CODE 18

09 OUTPUT 29

10 TESTING 34

11 HARDWARE AND SOFTWARE REQUIREMENTS 36

12 INSTALLATION PROCEDURE 37

13 BIBLIOGRAPHY 38

ACKNOWLEDGEMENT

Page 3 of 35
I would like to express a deep sense of thanks &
gratitude to my project guide Mr. P. C.
Srivastava Sir, for guiding me immensely
through thecourse of the project. He always
evinced keen interest in my work. His
constructive advice & constant motivation have
been responsible for the successful completion

of this project.

My sincere thanks go to Shri Shiv pratap sir . Our principal


and IT infrastructure for the completion of this project.

I also thanks to my parents for their motivation &support.


must thanks to my classmates for their timely help &
support for compilation of project .

Last but not the least, I would like to thank


all those who had helped directly or indirectly
towards the completion of this project.

Page 4 of 35
PROJECT ON COURIER SERVICE SYSTEM

INTRODUCTION
Now a days Couriers are essential for the mobile world, Therefore
there comes a need for managing the courier service in places. so
developers use DBMS and programming languages like python to create
a software which could manage
the courier services from a place for several parts of the world and to
begin with the introduction of my project this is a small project (a
software) developed by me to manage the courier service and the name
of my courier service system is BATMAN COURIER SERVICE

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.

Page 5 of 35
5. Students will demonstrate ability to conduct a 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 has to 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 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.

Page 6 of 35
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.

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.

Page 7 of 35
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?
Page 8 of 35
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:

Page 9 of 35
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.

Page 10 of 35
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

Page 11 of 35
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:

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.

Page 12 of 35
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.

Page 13 of 35
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

Page 14 of 35
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:

Page 15 of 35
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
Page 16 of 35
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.

Page 17 of 35
Source code:

import mysql.connector as sql

conn=sql.connect(host= 'localhost' ,user= 'root' ,passwd= 'manager',


database='courier_service_system2' )

cust1=conn.cursor()

print('WELCOME TO BATMAN COURIER SERVICE:')

print('Hi')

o=input('Press enter to begin your courier surfing')

print('1.CREATE YOUR COURIER SERVICE ACCOUNT')

print('2.LOGIN')

choose=int(input('ENTER (1) FOR NEW ACCOUNT OR (2) FOR LOGIN:'))

if choose==1:

name=input('Enter your user-name:')

passwd=input('Set your password here:')

passwd1=input('Confirm password:')

cust1.execute("INSERT INTO login VALUES(' "+name+" ',' "+passwd+" ')")

conn.commit()

print('ACCOUNT CREATED CONGRATULATIONS')

move_in=input('press enter to login:')

import B_COURIER_MENU

elif choose==2:

email=input('Enter your email-id')

Page 18 of 35
passd=input('Enter your PASSWORD:')

cust1.execute('select * from login where user_name=" '+email+' " and


password=" '+passd+' " ')

if cust1.fetchone() is None:

print(' sorry your password in wrong')

else:

import B_COURIER_MENU

B_COURIER_MENU:

import mysql.connector as sql

conn=sql.connect(host= 'localhost' ,user= 'root' ,passwd= 'manager',


database='courier_service_system2' )

cust1=conn.cursor()

for i in range(0,76):

print('WELCOME TO BATMAN COURIER SERVICE:')

print('1.Courier_order and customer_details')

print('2.billing_procedure')

print('3.courier_service_boys')

print('4.exit')

choice=int(input('enter the section you want to access:....(1,2,3or4)........:'))

if choice==1:

print('A.courier placement')

print('B.courier order list')

sect=str(input('enter the section that you want to access:'))

Page 19 of 35
if sect=="A":

print('COURIER-ORDER')

a=(input('enter the customer name:'))

b=int(input('enter the customer mobile number:'))

c=(input('enter the customer address:'))

d=(input('enter the receiver name:'))

e=int(input('enter the receiver mobile number:'))

f=(input('enter the receiver address:'))

cust1.execute("INSERT INTO couriers VALUES(' "+a+" ',"+str(b)+",' "+c+" ','


"+d+" ',"+str(e)+",' "+f+" ')")

conn.commit()

print(cust1.rowcount,'courier (s) placed')

print('===========================================================
====================================================')

elif sect=="B":

S=str(input('do you want to see your courier_order''(yes...\..no):'))

if S=="yes":

a=input('enter the customer mob number:')

cust1.execute('select * from couriers where


customer_mobile_number="{}" '.format(a))

order=cust1.fetchall()

print('customer name,','customer mob no,','customer address,','receiver


name,','receiver mob no,','receiver address:')

for j in order:
Page 20 of 35
print(j)

print('===========================================================
====================================================')

else:

print('Thank you')

print('===========================================================
===================================================')

elif choice==2:

print('BILLING PROCEDURE:[weight_in_kgs......AND.......cost_in_rupees]')

cust1.execute("select * from couriers2")

bill=cust1.fetchall()

for x in bill:

print(x)

print('===========================================================
====================================================')

if choice==3:

city1=input('enter your city name:')

cust1.execute("select * from couriers3 where city='{}' ".format(city1))

boys=cust1.fetchall()

print(' City courier_boy mobile no:')

for y in boys:

print(y)

Page 21 of 35
print('===========================================================
====================================================')

elif choice==4:

quit()

Page 22 of 35
Page 23 of 35
Output:

Page 24 of 35
Page 25 of 35
Page 26 of 35
Page 27 of 35
Page 28 of 35
Page 29 of 35
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.

Page 30 of 35
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.

Page 31 of 35
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.
They both return coverage metric, measured as a percentage

Page 32 of 35
HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)

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

K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

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 : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

Page 33 of 35
INSTALLATION PROCEDURE

STEP 1: Open py file create table courier in the location : C:\Users\cadet\


Documents\COURIER SERVICE SYSTEM

STEP 2: Run the file create table courier in python idle 3.7(64-bit)

('Table courier is created')

STEP 3:Open py file create table couriers2 in the location :C:\Users\cadet\


Documents\COURIER SERVICE SYSTEM

STEP 4:Run the file create table couriers2 in python idle 3.7(64-bit)

('Table couriers2 is created')

STEP 5:Open py file create table couriers3 in the location :C:\Users\cadet\


Documents\COURIER SERVICE SYSTEM

STEP 6:Run the file create table couriers3 in python idle 3.7(64-bit)

('Table couriers3 is created')

STEP 7:Open py file billing procedure in the location :C:\Users\cadet\Documents\


COURIER SERVICE SYSTEM

STEP 8:Run the file billing procedure in python idle 3.7(64-bit)

('The billing procedure values are inserted into the table couriers2')

STEP 9:Open py file courier service boys in the location :C:\Users\cadet\Documents\


COURIER SERVICE SYSTEM

STEP 10:Run the file courier service boys in python idle 3.7(64-bit)

('The couier service boys bio data are inserted into the table couriers3')

STEP 11:Open py file courier service system in the location :C:\Users\cadet\


Documents\COURIER SERVICE SYSTEM

STEP 12:Run the file in python IDLE 3.7(64-bit)

(1.first ,The user should create an account or login with his existing account,

2.second,The file courier service system IMPORTS another python file


COURIER MENU,

3.NOW, The user can access BATMAN COURIER SERVICE)

Page 34 of 35
BIBLIOGRAPHY

1. COMPUTER SCIENCE WITH PYTHON CLASS XII – BY PREETHI ARORA


2. COMPUTER SCIENCE WITH PYTHON CLASS XI – BY SUMITHA ARORA
3. A PROJECT REPORT ON COURIER SERVICE SYSTEM
4. WWW.W3RESOURCE.COM/

***

Page 35 of 35

You might also like