Courier Service System PROJECT
Courier Service System PROJECT
Courier Service System PROJECT
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
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
SYSTEM ANALYSIS
EXISTING SYSTEM
Most of the operations in the existing systems of this project is to do the basic
operations
The Admin can view the details of Items, Delivery man, user, add and remove items
The major drawback in the existing system is it does not remove the item details and
also it does not check the status of user.
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.
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.
2
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.
3
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies a need or an opportunity.
4
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.
5
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,
6
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.
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.
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
7
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:
8
DEVELOPMENT PHASE
9
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.
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 re-enter
the planning phase.
10
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.
HARDWARE REQUIREMENTS:
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. MySQL
11
RESULTS AND DISCUSSIONS
Source code:
cust1=conn.cursor()
print('Hi')
print('2.LOGIN')
if choose==1:
passwd1=input('Confirm password:')
conn.commit()
12
move_in=input('press enter to login:')
import B_COURIER_MENU
elif choose==2:
if cust1.fetchone() is None:
else:
import B_COURIER_MENU
B_COURIER_MENU:
cust1=conn.cursor()
for i in range(0,76):
print('2.billing_procedure')
print('3.courier_service_boys')
print('4.exit')
13
choice=int(input('enter the section you want to access:....(1,2,3or4)........:'))
if choice==1:
print('A.courier placement')
if sect=="A":
print('COURIER-ORDER')
conn.commit()
print('==============================================================
=================================================')
elif sect=="B":
if S=="yes":
14
cust1.execute('select * from couriers where customer_mobile_number="{}" '.format(a))
order=cust1.fetchall()
for j in order:
print(j)
print('==============================================================
=================================================')
else:
print('Thank you')
print('==============================================================
================================================')
elif choice==2:
print('BILLING PROCEDURE:[weight_in_kgs......AND.......cost_in_rupees]')
bill=cust1.fetchall()
for x in bill:
print(x)
print('==============================================================
=================================================')
if choice==3:
15
cust1.execute("select * from couriers3 where city='{}' ".format(city1))
boys=cust1.fetchall()
for y in boys:
print(y)
print('==============================================================
=================================================')
elif choice==4:
quit()
16
Output
17
18
19
20
TESTING
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.
SPECIFICATION-BASED TESTING
21
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
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, 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)
22
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.
23
INSTALLATION PROCEDURE
STEP 2: Run the file create table courier in python idle 3.7(64-bit)
STEP 4:Run the file create table couriers2 in python idle 3.7(64-bit)
STEP 6:Run the file create table couriers3 in python idle 3.7(64-bit)
('The billing procedure values are inserted into the table couriers2')
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')
(1.first ,The user should create an account or login with his existing account,
24
2.second,The file courier service system IMPORTS another python file COURIER
MENU,
BIBLIOGRAPHY
***
25