Attachment

PROJECT REPORT
ON
FRENCH COURIER MANAGEMNET
SUBMITTED TO THE
UNIVERCITY OF MUMBAI
FOR THE DEGREE OF
BACHELOR OF SCIENCE
IN
INFORMATION TECHNOLOGY
SUBMITTED BY
KHAN JUWERIA SEAT NO.:
GUIDED BY
Ms. SIDRANAAZ KAZI
SOPHIA COLLEGE FOR WOMEN

BHULABHAI DESAI ROAD
MUMBAI- 400026
2017- 18
CERTIFICATE
This is to certify that the project report entitled
“FRENCH COURIER MANAGEMENT”

is a bonafide work of
KHAN JUWERIA SEAT NO.:
Submitted to the University of Mumbai in partial fulfillment of the requirement for

the award of the Degree of Bachelor of Science in Information Technology for the
Academic year 2017- 18
NAME OF GUIDE: Ms. SIDRANAAZ KAZI Ms. RINJAL R.JAIN
BSc.IT COORDINATOR
SIGNATURE: _______________________
NAME OF EXTERNAL EXAMINAR: _____________________________________
SIGNATURE: ________________________ DATE: __________________
INDEX
Sr.no Topics Page.no
1. Introduction 2
2. Problem Definition 4
3. Requirement Gathering 7
4. Analysis 11
4.1 Project Scope
5. System Requirement Specification 14
5.1 Software Used
5.2 Software Requirements
5.3 Feasibility Study
6. Software Specification 17
6.1 Front End
6.2 Back End
7. Software Development Life Cycle 19
7.1 Overview
7.2 Software development phases
7.3 Phases SDLC
7.4 Design Phase
7.5 Incremental Model
7.6 Working of Incremental Model
8. The Unified Modeling Language 26
8.1 Entity relationship diagram
8.2 Class diagram
8.3 Use case diagram
8.4 Data flow diagram
8.5 Activity diagram
8.6 Sequence diagram
9. System Planning & Scheduling 50
9.1 Project schedule
10. Gantt Chart 55
11. Data dictionary 57
12. Testing Phase 62
12.1 Test levels
12.2 Testing methods
13. System Coding 75
14. Screenshot 84
15. Limitations and Future Scope 89
16. Maintenance 91
17. Conclusion 93
18. References 95
ABSTRACT
This project deals with the ‘Courier Information System’. The

system is used for daily activities such as booking a courier, maintain employee
details, process payroll of employees, maintain hub details, maintain company
details etc,..
The aim of the project “COURIER MANAGEMENT”, which is website, is to

decrease the manual task of courier management.
The goal of the system is to automate the manual task of courier management with
more reliable performance and realize the vision of paperless work.
ACKNOWLEDGEMENT
The success of this project depends on the encouragement and guidance of many
others. I take this opportunity to express my gratitude to all of them.
First of all, we would like to express our gratitude to our principal, Dr. (Sr.)
Ananda Amritmahal for extending her support for this project.
I would like to thank Ms. Rinjal R. Jain BSc.IT Coordinator for her
encouragement.
I would like to express our gratitude to Ms. Sidranaaz kazi for the consistent
support and guidance rendered throughout the completion of this project.
I would like to appreciate the value addition done by our teachers Ms. Sqqueeba
mistry and Ms. Ambreen Shaikh in compiling the entire project.
KHAN JUWERIA
INTRODUCTION
1.1 INTRODUCTION
The software will be easy to handle, the website will provide information of
booking a courier ,
, maintain hub details .
The courier management project has different modules .The login section will have
login facility for admin, customer, employee.While taking the orders from the
customers, it will take all the details of the customer and the details of the recipient
such as address, mobile number etc.During billing process the system will generate
the tracking id for the products. Through this tracking id the customer or recipient
will be able to track their products from any location through internet.
The courier service work as a destination office or source office .
PROBLEM DEFINITION
2.1 PROBLEM
The existing system has lot of problems such as:

• The entire database is maintained manually which is rather tedious and error
prone.
• Time delay is more because of verification of many records for generating
reports, answering queries etc.
• Queries are not answered properly due to lack of communication.
• More space is required to keep all the records.
• Improper interface.
2.2 CURRENT SYSTEM
The existing system is not totally automated. Though the system is computerized to
a particular extent, it has to do a lot of manual work.

The different processes involved are:
• To maintain details of bookings manually.
• Calculate salaries of the employees.
• To maintain details of the incoming couriers.
• To maintain returns details.
• To maintain out return details.
2.3 PROPOSED SYSTEM

This project deals with the ‘Courier information ’. The system is used for
daily activities such as booking, non delivery, out return, company details, and
pickup centers. It is very difficult to do this process manually. Hence it is
recommended to computerize the process by developing the relative software as
the world is turning into information and technology; computerization becomes
necessity in all walks of life.
2.4 BENEFITS OF PROPOSED SYSTEM

The organization will obviously be able to gain benefits such as savings in
operating cost, reduction in ppaerwork,better utilization of human resources and
more presentable image increasing goodwill.
REQUIREMENT GATHERING
i. SOFTWARE USED
• Microsoft Visual Studio 2010.
• Microsoft SQL Server 2008

ii. SOFTWARE REQUIREMENTS
• Windows 8 or Windows 10 Professional Service Pack 1.
• Web Browser: Microsoft Internet Explorer 7.0, Mozilla, Google Chrome or

later.
iii. HARDWARE REQUIREMNETS
• 1 or 2.5 GHZ Dual Core Processor.
• 2GB RAM.
• 3 or 4GB Hard Disk.
iv.SUPPLEMENTARY REQUIREMNETS
• HP Printer
ANALYSIS
4.1 INTRODUCTION
• Computer system of the courier service provide fast access.
• If our documents or any consignmemt is missed then we can know
it easily using the databases in the computer system of courier
services.
• In computer system the person has to fill the various forms &
number of copies of the forms can be easily generated at a time.
• Accuracy of work.
• Easy & fast retrieval of information.
• Well designed reports.
• Decrease the load of the person involve in existing manual system.
• Access of any information individually.
• Work becomes very speedy.
• Easy to update information.
4.2 PROJECT SCOPE
• We will host the platform on online servers to make it accessible worldwide.
• Implement the backup mechanism for taking up the backup of codebase and
databases on regular basis on different platforms.
SYSTEM REQUIREMENT
SPECIFICATION
5.1 SOFTWARE USED
• Microsoft Visual Studio 2010.
• Microsoft Visual Studio Database.
5.2 SOFTWARE REQUIREMENTS

• Web Browser: Microsoft Internet Explorer 7.0 or above
• Mozilla
• Google Chrome
5.3 FEASIBILITY STUDY
• A feasibility study is carried out to select the best system that meets
performance requirements.
The main aim of the feasibility study activity is to determine whether it
would be financially and technically feasible to develop the product.
• The feasibility study activity involves the analysis of the problem and
collection of all relevant information relating to the product such as the
different data items which would be input to the system, the processing
required to be carried out on these data, the output data required to be
produced by the system as well as various constraints on the behavior of the
system.
5.4 OPERATIONAL FEASIBILITY:

• Operational feasibility study tests the operational scope of the software
to be developed.The proposed software must have high operational feasibility.
• The usability will be high.
5.5 TECHNICAL FEASIBILITY:

• The technical feasibility study compares the level of
technology available in the software development firm and the level
of technology required for the development of the product
.Here the level of
technology consists of the programming language, the hardware reso
urces, Other software tools etc.
5.6 ECONOMIC FEASIBILITY:
• The economic feasibility study evaluate the cost of the

software development against the ultimate income or benefits gets
from the developed system.
There must be scopes for profit after the successful
Completion of the project
Cost Estimation
This Project “FRENCH COURIER MANAGEMENT” is developed at a small

scale and hence it is a low budget project. The cost is calculated based on the
requirement and development of this system.
They are as follows:

• Licensed version of the Operating System.
• Usage of Internet.
• Effort taken to develop and design the system.
• Hardware’s required.
6. SOFTWARE SPECIFICATIONS
6.1 FRONT END: ASP.NET
• ASP.NET is object-oriented programming language. ASP.NET support web

application framework developed and marketed by Microsoft to allow
programmers to build dynamic web sites.
• ASP.NET is used to produce interactive, data-driven web applications over

the internet. It consists of a large number of controls such as text boxes,
buttons, and labels for assembling, configuring, and manipulating code to
create HTML pages.
• It is purely server-side technology so, ASP.NET code executes on the server

before it is sent to the browser. Being language-independent, it allows you to
choose the language that best applies to your Application or partition your
application across many languages.
6.2 BACK END: MICROSOFT SQL SERVER 2010

• Microsoft SQL Server is a relational database management system
(RDBMS) from Microsoft that's designed for the enterprise environment.
• Microsoft SQL Server runs includes transaction control, exception and error
handling, row processing, and declared variables. Microsoft SQL Server
support for structured and semi-structured data, including digital media
formats for pictures, audio, video and other multimedia data.
• Microsoft SQL server includes better compression features, which also helps
in improving scalability. It enhanced the indexing algorithms and introduced
the notion of filtered indexes. It also includes capabilities for transparent
encryption of data (TDE) as well as compression of backups.
SOFTWARE DEVELOPMENT LIFECYCLE
Software development life cycle
• The software development life cycle (SDLC) is a framework defining

tasks performed at each step in the software development process.
7.1 OVERVIEW
SDLC is a process followed for a software project, within a software organization.
It consists of a detailed plan describing how to develop, maintain, replace and alter
or enhance specific software. The life cycle defines a methodology for improving
the quality of software and the overall development process. The SDLC aims to
produce high quality software that meets or exceeds customer expectations,
reaches completion within times and cost estimates.
7.2 SYSTEM DEVELOPMENT PHASES
Software life cycle models describe phases of the software cycle and the order in
which those phases are executed. Each phase produces deliverables required by the
next phase in the life cycle. Requirements are translated into design. Code is
produced according to the design which is called development phase. After coding
and development the testing verifies the deliverable of the implementation phase
against requirements.
7.3 PHASES IN SOFTWARE DEVELOPMENT LIFE CYCLE
There are following six phases in every Software Development Life

Cycle model
• Requirement gathering and analysis
• Design
• Implementation or coding
• Testing
• Deployment
• Maintenance
Phase 1: Requirement gathering and analysis:
Requirement analysis is the most important and fundamental stage in SDLC. This
information is then used to plan the basic project approach and to conduct product
feasibility study in the economical, operational, and technical areas. Planning for
the quality assurance requirements and identification of the risks associated with
the project is also done in the planning stage.
• In census system it helps to gather the information about municipal offices,

hospital, police stations, NGO and the process carried out to maintain all
health department information. Analysis is used to study the census process.
Phase 2: Defining Requirements:
Once the requirement analysis is done the next step is to clearly define and
document the product requirements and get them approved from the market
analysts. This is done through SRS (Software Requirement Specification)
document.
• The SRS for census application has been documented within this phase with
a well define proposed system as well as scope of project.
Phase 3: Design:
In this phase the system and software design is prepared from the requirement
specifications. System Design helps in specifying hardware and system
requirements and also helps in defining overall system architecture. In this phase
the testers comes up with the Test strategy, where they mention what to test, how
to test.
• The census web application is developed on freeware Microsoft Visual

Studio IDE which helps to develop any website application. The software
and hardware requirement will be that of machine requirements.
Phase 4: Implementation / Coding:
On receiving system design documents, the work is divided in modules/units and

actual coding is started. Since, in this phase the code is produced so it is the main
focus for the developer. This is the longest phase of the software development life
cycle.
• In census application each module was coded based on the design of each
module and how the working and process needs to go about. The code was
checked particularly twice, so that at the time of testing where the whole
application is set to test is error free and to avoid large modifications.
Phase 5: Testing:
After the code is developed it is tested against the requirements to make sure that
the product is actually solving the needs addressed and gathered during the
requirements phase. During this phase all types of testing are done such as unit
testing, integration testing, system testing, acceptance testing are done as well
as non-functional testing are also done.
• In census after each module was designed and coded was tested
immediately to check whether it meets the requirement of the end user.
Phase 6: Deployment:
After successful testing the product is delivered / deployed to the customer for
their use. As soon as the product is given to the customers they will first do
the beta testing. If any changes are required or if any bugs are caught, then they
will report it to the engineering team. Once those changes are made or the bugs are
fixed then the final deployment will happen.
• After the successful testing of census application the website will be

deployed to the management for use and to see whether it is useful to meet
the requirements of municipal management system and if at all any changes
are made into application then release update will be send
Phase 7: Maintenance:
Maintenance is a process that helps in maintaining the system. The process where
the care is taken for the developed product is known as maintenance.
• Once when the user starts using the developed system then the actual
problems comes up and needs to be solved from time to time.
DESIGN PHASE
The Waterfall Model was the first Process Model to be introduced. It is also referred to as a
linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed before the next phase can begin and there is no overlapping in the
phases.
The Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential flow.
This means that any phase in the development process begins only if the previous phase is
complete. In this waterfall model, the phases do not overlap.
Waterfall Model - Design

Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure
success of the project. In "The Waterfall" approach, the whole process of software development
is divided into separate phases. In this Waterfall model, typically, the outcome of one phase acts
as the input for the next phase sequentially.
The following illustration is a representation of the different phases of the Waterfall Model.
The sequential phases in Waterfall model are −
• Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification
document.
• System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying hardware
and system requirements and helps in defining the overall system architecture.
• Implementation − With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
• Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
• Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
• Maintenance − There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined
set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model".
In this model, phases do not overlap.
Waterfall Model - Application

Every software developed is different and requires a suitable SDLC approach to be followed
based on the internal and external factors. Some situations where the use of Waterfall model is
most appropriate are −
• Requirements are very well documented, clear and fixed.
• Product definition is stable.
• Technology is understood and is not dynamic.
• There are no ambiguous requirements.
• Ample resources with required expertise are available to support the product.
• The project is short.
Waterfall Model - Advantages

The advantages of waterfall development are that it allows for departmentalization and control.
A schedule can be set with deadlines for each stage of development and a product can proceed
through the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds
in strict order.
Some of the major advantages of the Waterfall Model are as follows −
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model. Each phase has specific deliverables and
a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
Home Page
Admin Login
Admin Previlizes
Employee Registration
Employee Details
Update Employee
PaySlip
View Employee Salary Details
View Query Of Customer
Employee Previlizes
Courier Booking
View Booking Details
Incoming Details
Non Delivery Details
Out Returns
THE UNIFIED MODELINGLANGUAGE

INTRODUCTION TO UML
The Unified Modeling Language (UML) is a standard language for writing

software blueprints. The UML may be used to visualize, specify, construct, and
document the artifacts of a software-intensive system. The UML is process
independent, although optimally it should be used in a process that is use case
driven, architecture-centric, iterative, and incremental.
DIAGRAMS IN THE UML
A diagram is the graphical presentation of a set of elements, most often rendered

as a connected graph of vertices (things) and arcs (relationships). You draw
diagrams to visualize a system from different perspectives, so a diagram is a
projection into a system.
8.1 ENTITY RELATIONSHIP

Entity–Relationship Model (ER model) is a data model for describing the data. The
main components of ER models are entities (things) and the relationships that can
exist among them.
An entity-relationship model is a systematic way of describing and defining a
business process.
Diagrams created to represent these entities, attributes, and relationships
graphically are called entity–relationship diagrams.
ER DIAGRAM SYMBOLS
Symbol Shape Name Symbol Description

Entities
An entity is represented by a
Entity rectangle which contains the
entity’s name.
An entity that cannot be

uniquely identified by its
attributes alone. The existence
Weak Entity
of a weak entity is dependent
upon another entity called the
owner entity.
An entity used in a many-to-
Associative
many relationship (represents
Entity
an extra table).
Attributes
In the Chen notation, each
attribute is represented by an
Attribute
oval containing attributes
name
An attribute that uniquely
Key identifies a particular entity.
attribute The name of a key attribute is
underscored.
An attribute that can have
many values (there are many
Multi-
distinct values entered for it in
valued
the same column of the table).
attribute
Multi-valued attribute is
depicted by a dual oval.
An attribute whose value is
calculated (derived) from other
attributes. The derived
Derived
attribute may or may not be
attribute
physically stored in the
database. It is represented by
dashed oval.
Relationships
A relationship where entity is
existence independent of other
Strong
entities and PK of Child
relationship
doesn’t contain PK component
of Parent Entity. A strong
relationship is represented by a
single rhombus
A relationship where Child
entity is existence-dependent
Weak on parent and PK of Child
(identifying) Entity contains PK component
relationship of Parent Entity.
This relationship is represented
by a double rhombus.
Cardinalities
. USE CASE DIAGRAM:
Use case diagrams are usually referred to as behaviour diagrams used to describe a set of actions
(use cases) that some system or systems (subject) should or can perform in collaboration with
one or more external users of the system (actors). Each use case should provide some observable
and valuable result to the actors Or other stakeholders of the system.
USE CASE DIAGRAM SYMBOLS AND THEIR MEANINGS
Symbol Name Description
Actor in a use case diagram is any entity that

Actor performs a role in one given system. This could
be a person, organization or an external system
and usually drawn like skeleton shown below.
A use case represents a function or an action

Use Case within the system. It’s drawn as an oval and
named with the function.
An association is a connection between an actor
Association and a use case. An association indicates that an
actor can carry out a use case.
System is used to define the scope of the use

case and drawn as a rectangle. This an optional
System element but useful when your visualizing large
systems.
It indicates that the use case to which the arrow

points is included in the use case on the other
Include
side of the arrow. This makes it possible to reuse
Relationships
a use case in another use case.
An extend relationship specifies how the

behaviour of the extension use case can be
Extend
inserted into the behaviour defined for the base
Relationships
use case.
• USECASE DIAGRAM
• USECASE DIAGRAM FOR NORMAL EMPLOYEE
CLASS DIAGRAM SYMBOLS AND MEANINGS
Class:
A class represents a relevant concept from the domain, a set of persons, objects, or
ideas that are depicted in the sys:
Attribute:
An attribute of a class represents a characteristic of a class that is of interest for the
user of the system
Generalization:
Generalization is a relationship between two classes: a general class and a special
class:
Association:
An association represents a relationship between two classes:
An association indicates that objects of one class have a relationship with objects
of another class, in which this connection has a specifically defined meaning (for
example, "is flown with").
Multiplicity:
A multiplicity allows for statements about the number of objects that are involved
in an association:
Aggregation:
An aggregation is a special case of an association. The diamond documents this
meaning; a caption is unnecessary.
8.4 Data Flow Diagram
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modeling its process aspects. DFDs can also be
used for the visualization of data processing (structured design).A DFD shows
what kind of information will be input to and output from the system, where the
data will come from and go to, and where the data will be stored. It does not show
information about the timing of processes, or information about whether processes
will operate in sequence or in parallel.
DFD DIAGRAM’S SYMBOLS

Process:
A process transforms incoming data flow into outgoing data flow.
Data store:
Data stores are repositories of data in the system. They are sometimes also referred
to as files.
Dataflow:
Dataflow are pipelines through which packets of information flow. Label the
arrows with the name of the data that moves through it.
External Entity:
External entities are objects outside the system, with which the system
communicates. External entities are sources and destinations of the system's inputs
and outputs.
Context DFD
A context diagram is a top level (also known as "Level 0") data flow diagram. It
only contains one process node ("Process 0") that generalizes the function of the
entire system in relationship to external entities.
DFD Layers:
Draw data flow diagrams can be made in several nested layers. A single process
node on a high level diagram can be expanded to show a more detailed data flow
diagram. Draw the context diagram first, followed by various layers of data flow
diagrams.
DFD Levels:
The first level DFD shows the main processes within the system. Each of these
processes can be broken into further processes until you reach pseudo code.
ACTIVITY DIAGRAM:
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system.
Activity diagram is basically a flow chart to represent the flow form one activity to another
activity. The activity can be described as an operation of the system.
So the control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using different
elements like fork, join etc.
ACTIVITY DIAGRAM SYMBOLS, MEANINGS AND RULES
Symbol Name Description

The start symbol represents the beginning
Start of a process or workflow in an activity
diagram.
The activity symbol indicate the activities
activity that make up a modeled process.
The connector symbol shows the

connector directional flow, or control flow, of the
activity
The join symbol combines two concurrent
activities and re-introduces them to a flow
join
where only one activity occurs at a time.
A fork multiple arrowed lines from a join.

It splits a single activity flow into two
fork
concurrent activities.
The decision it represents the branching or

merging of various flows with the symbol
decision
acting as a frame or container.
The end symbol represents the completion

end of a process or workflow.
• ACTIVITY DIAGRAM FOR CHECKING LOGIN CREDENTIALS

• ACTIVITY DAIGRAM FOR REGISTRATION
• ACTIVITY DIAGRAM FOR CHECKING LOGIN CREDENTIALS
8.6 Sequence Diagram
The Sequence Diagram models the collaboration of objects based on a time

sequence. It shows how the objects interact with others in a particular scenario of a
use case. Sequence diagram is the most common kind of interaction diagram,
which focuses on the message interchange between a numbers of lifelines.
Sequence diagram describes an interaction by focusing on the sequence of
messages that are exchanged, along with their corresponding occurrence
specifications on the lifelines.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes
or objects that live simultaneously, and, as horizontal arrows, the messages
exchanged between them, in the order in which they occur. This allows the
specification of simple runtime scenarios in a graphical manner.
System Planning & Scheduling
9.1 Project Schedule

Project Title FRENCH COURIER MANAGEMENT
Front End ASP.NET
Black End SQL SERVER 2008
Project Member
NAME ROLL NO
KHAN JUWERIA T14057
SR.N CONTENTS PROPOSE SUBMISSIO TEACHER’ REMAR

O D DATE N DATE S K
SIGNATUR
E
1. Investigation
Project Fixing 28/11/17 01/12/17
Synopsis 08/12/17 03/12/17
2. Requirement
Analysis &
Planning
Project 15/12/17 15/12/17
History
Requirement 24/12/17 20/12/17
Gathering
Objective 06/01/18 04/01/18
And Scope Of
Project
Problems 10/01/18 10/01/18
With The
Existing
System
Advantages 15/01/18 15/01/18
of Proposed
System
Feasibility 17/01/18 18/01/18
Study
Cost Benefits 18/01/18 18/01/18
Analysis
Requirements 20/01/18 20/01/18
Specifications
Tools And 24/01/18 21/01/18
Technology
3. Design Phase
Detailed Life 27/01/18 25/01/18
Cycle Of The
Project(Logic
al Diagram)
E.R Diagram 5/02/18 5/02/18
Class 5/02/18 5/02/18
Diagram
Use Case 7/02/18 6/02/18
Diagram
Activity 7/02/18 6/02/18
Data Flow 10/02/18 8/02/18
Diagram
Sequence 14/02/18 9/02/18
Diagram
Database 17/02/18 14/02/18
Design
4. Coding
phase
Forms 17/02/18 20/02/18
Module 28/02/18 26/02/18
5. Testing
Phase
Module 15/03/18 16/3/18
Testing/Unit
Testing
Integration 22/03/18 22/03/18
Testing
System 26/03/18 27/03/18
Testing/White
Box Testing
Acceptance 28/03/18 29/03/18
Testing/Black
Box Testing
6. Maintenance
And
Evaluation
System 31/03/18 26/03/18
Maintenance
And Future
Enhancement
User Manual 9/04/18 29/03/18
7. Review 11/04/18 31/03/18
8. Project/Blac 9/04/18 16/04/18
k Book And
Back-up
Softcopy
Submission
gantt chart
10. data dictionary
DATA DICITONARY:
ADMIN DETAILS:
Serial No Column Name Data Type Constrains
1 a_name Varchar(50) Not Null
2 a_password Varchar(50) Not Null
EMPLOYEE DETAILS:

1 e_name Varchar(50) Not Null
2 e_password Varchar(50) Not Null
CUSTOMER DETAILS:
1 c_id Varchar(100) Unique Key
2 c_name Varchar(100) Not Null
3 c_username Varchar(100) Not Null
4 c_password String(100) Not Null
Hub Centre
Pick Up Centre
Company Details
Employee Previlizes
Change Password
Customer Previlizes
View Booking Details
View Non Delivery Details
Customer Details
View Report of Admin
About Us
Contact Us
6. SOFTWARE SPECIFICATIONS
6.1. Front End: C#.NET:

• C# is an elegant and type- safe object oriented language that enables developers to build a
variety of secure and robust application that run on .NET framework.
• Visual C# provides an advanced code editor, convenient user interface designers,

integrated debugger, etc. to make it easier to develop applications based on the C# language and
the .NET framework.
• C# program runs on the .NET framework, an integrated component of Windows that

includes a visual execution system called the common language runtime (CLR) and a unified set
of class libraries.
• The CLR is the commercial implementation by Microsoft of the common language

interface (CLI), an international standard that is the basis for creating execution and development
environment in which languages and libraries work together.
6.2. Back End: Microsoft SQL Server Data Tools 2015:
• Microsoft SQL Server is a relational database management system (RDBMS) from

Microsoft that's designed for the enterprise environment.
• Microsoft SQL Server runs on T-SQL (Transact -SQL), a set of programming extensions
from Sybase and Microsoft that add several features to standard SQL, including transaction
control, exception and error handling, row processing, and declared variables.SQL Server 20016
includes support for structured and semi-structured data, including digital media formats for
pictures, audio, video and other multimedia data.
• SQL server includes better compression features, which also helps in improving
scalability. It enhanced the indexing algorithms and introduced the notion of filtered indexes. It
also includes capabilities for transparent encryption of data (TDE) as well as compression of
backups.
TESTING PHASE
TESTING:
Software testing is a process of executing a program or application with the intent of finding the
software bugs. It can also be stated as the process of validating and verifying that a software
program or application or product:
• Meets the business and technical requirements that guided it’s design and development
• Works as expected
• Can be implemented with the same characteristic
11.1. TESTING LEVELS:
• Unit Testing
• Integration Testing
Unit Testing: Unit testing is a level of software testing where individual units/ components of a
software are tested. The purpose is to validate that each unit of the software performs as
designed. A unit is the smallest testable part of software. It usually has one or a few inputs and
usually a single output.
Integration Testing: Integration testing is a level of software testing where individual units are
combined and tested as a group. The purpose of this level of testing is to expose faults in the
interaction between integrated units. Test drivers and test stubs are used to assist in Integration
Testing.
11.2. TESTING METHODS:
• Black box Testing
• White box Testing
11.2.1. BLACK BOX TESTING:

This testing method considers a module as a single unit and checks the unit at interface and
communication with other modules rather getting into details at statement level. Here the module
will be treated as a black box that will take some input generate output. Output for a given set of
input combinations are forwarded to other module. The main purpose of the Black Box is to
check whether the software is working as per expected in requirement document & whether it is
meeting the user expectations or not.
• Equivalence partitioning: Equivalence partitioning or equivalence class
partitioning (ECP) is a software testing technique that divides the input data of a
software unit into partitions of equivalent data from which test cases can be derived. In
principle, test cases are designed to cover each partition at least once.
• Boundary value analysis: Boundary value analysis is a black box test design technique
and it is used to find the errors at boundaries of input domain rather than finding those
errors in the center of input. Equivalence Partitioning and Boundary value analysis are
linked to each other and can be used together at all levels of testing.
. WHITE BOX TESTING:

Also known as glass box, structural, clear box and open box testing. A software
testing technique whereby explicit knowledge of the internal workings of the item being
tested are used to select the test data. Unlike black box testing, white box testing uses specific
knowledge of programming code to examine outputs.
• Path Coverage: In this the test case is executed in such a way that every path is
executed at least once.
• Statement Coverage: In this the test case is executed in such a way that every statement
of the code is executed at least once.
• Data Flow: Data flow testing is a family of test strategies based on selecting paths
through the program's control flow in order to explore sequences of events related to the
status of variables or data objects. Dataflow Testing focuses on the points at which
variables receive values and the points at which these values are used.
MAINTENANCE:
Software maintenance is widely accepted part of SDLC now a days. It stands for all the
modifications and updations done after the delivery of software product. There are number of
reasons, why modifications are required, some of them are briefly mentioned below:
• Market Conditions - Policies, which changes over the time, such as taxation and newly
introduced constraints like, how to maintain bookkeeping, may trigger need for
modification.
• Client Requirements - Over the time, customer may ask for new features or functions in
the software.
• Host Modifications - If any of the hardware and/or platform (such as operating system)
of the target host changes, software changes are needed to keep adaptability.
• Organization Changes - If there is any business level change at client end, such as
reduction of organization strength, acquiring another company, organization venturing
into new business, need to modify in the original software may arise.
TYPES OF MAINTENANCE:
In a software lifetime, type of maintenance may vary based on its nature. It may be just a
routine maintenance tasks as some bug discovered by some user or it may be a large event in
itself based on maintenance si
ze or nature. Following are some types of maintenance based on their characteristics:
• Corrective Maintenance - This includes modifications and updations done in order to
correct or fix problems, which are either discovered by user or concluded by user error
reports.
• Adaptive Maintenance - This includes modifications and updations applied to keep the
software product up-to date and tuned to the ever changing world of technology and
business environment.
• Perfective Maintenance - This includes modifications and updates done in order to keep
the software usable over long period of time. It includes new features, new user
requirements for refining the software and improve its reliability and performance.
• Preventive Maintenance - This includes modifications and updations to prevent future
problems of the software. It aims to attend problems, which are not significant at this
moment but may cause serious issues in future.
CODINGS
SOURCE CODE
Home.aspx:
<%@ Page Language="C#" MasterPageFile="~/Home.master" AutoEventWireup="true"

CodeFile="Home.aspx.cs" Inherits="Default2" Title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Names="WST_Germ"
Font-Size="24pt" ForeColor="#990033" Style="z-index: 100; left: 301px; position:
absolute;
top: 587px" Text="Welcome To French Courier"></asp:Label>
</asp:Content>
Home.master:
<%@ Master Language="C#" AutoEventWireup="true" CodeFile="Home.master.cs" Inherits="Home"
%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>French Courier Service</title>
<style type="text/css">

</style>
</head>
<body bgcolor="#E4F4FB">
<form runat ="server">
<table width="800" align="center" cellpadding="0" cellspacing="0" background=""
class="tablebg">
<tr>
<td colspan="2" bgcolor="#FFFFFF" style="width: 700px; height: 60px;"><img
src="images/logo.gif" width="440" height="60" /></td>
</tr>
<tr>
<td colspan="2" style="width: 700px; height: 70px;"><table align="center"
cellpadding="0" cellspacing="0" style="height: 1px; width: 798px;">
<tr>
<td background="images/menu_mid.gif" style="height: 50px"><%--<img
src="images/menu_l.gif" />--%></td>
<td background="images/menu_mid.gif" style="height: 50px; width: 752px;"
> <asp:Menu ID="Menu1" runat="server" Font-Bold="True" ForeColor="#99FFFF"
Orientation="Horizontal"
Width="742px" Height="26px">
<Items>
<asp:MenuItem Text="HOME" Value="Home"
NavigateUrl="~/Home.aspx"></asp:MenuItem>
<asp:MenuItem Text="ADMIN" Value="ADMIN"
NavigateUrl="~/admin/adminlogin.aspx"></asp:MenuItem>
<asp:MenuItem Text="COURIER" Value="New Item"
NavigateUrl="~/courier/login.aspx"></asp:MenuItem>
<asp:MenuItem Text="EMPLOYEE" Value="New Item"
NavigateUrl="~/employee/emplogin.aspx"></asp:MenuItem>
<asp:MenuItem Text="CUSTOMER" Value="New Item"
NavigateUrl="~/customer/login.aspx"></asp:MenuItem>
<asp:MenuItem Text="ABOUT US" Value="ABOUT US"
NavigateUrl="~/Aboutus.aspx"></asp:MenuItem>
<asp:MenuItem Text="CONTACT US" Value="CONTACT US"
NavigateUrl="~/contactus.aspx"></asp:MenuItem>
</Items>
</asp:Menu>
</td>
<td background="images/menu_r.gif" style="width: 11px; height: 64px;"><%--<img
src="images/menu_r.gif" style="width: 20px; height: 60px" />--%></td>
</tr>
</table></td>
</tr>
<tr>
<td colspan="2" align="center" valign="middle" style="width: 798px"><h4
class="style1"><img src="images/banner.gif" width="774" height="200" /></h4></td>
</tr>
<tr>
<td colspan="2" align="center" valign="middle" style="width: 798px; height:
343px;"><table width="774" align="center" cellpadding="0" cellspacing="0"
class="innertable">
<tr>
<td height="320" bgcolor="#FFFFFF" align="left">
<asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</td>
</tr>
</table></td>
</tr>
<tr>
<td style="height: 10px"></td>
</tr>
<tr>
<td height="49" background="images/footer.gif"></td>
</tr>
</table>
</form>
</body>
</html>
Aboutus.aspx:
CodeFile="Aboutus.aspx.cs" Inherits="Aboutus" Title="Untitled Page" %>
<asp:Panel ID="Panel1" runat="server" Height="379px" Width="792px"
BackColor="#FFC0C0">
 &nbsp
; With the rapid strides in technology and telecommunication,
the world has shrunk to such an extent that what was
unheard of or
incommunicado has become possible. However technological
advancements without
effective backing ends, infrastructure, leave a wide
gap in effective
communication
 &n
bsp; Incepted in the year 1987 with a sole mission of catering
effective written messages, documents and cargo “The
French Couriers” (TPC) have
reached the pinnacle of being
a truly professional courier company,
having today the infrastructure
for bulk cargo both nationally and internationally, with a strong work
force
and a Network of offices spread globally.

 &n
bsp; The French
Couriers have
come a long way
in providing t otal solutions for
a broad
spectrum from individuals to leading Public
Sector Undertakings,
Government Bodies, Corporates, MNCs,
Educational and Financial
Institutions

 &n
bsp; The real attribute in the success of 
TPC is its willingness to upgrade the systems with changing
times and
also to incorporate fresh and innovative ideas to make its presence felt.


 &nbsp
; The real attribute in the success of 
TPC is its willingness to upgrade the systems with changing
times and
also to incorporate fresh and innovative ideas to make its presence felt

nbsp; &nb
sp; At Professional the sophisticated Hub-and-
spoke
system with ware housing and storage f
acilities, modern communication
network and large fleet of
transportation vehicles backed by
dedicated team of professionals truly proves that their
claim “We care…. For
your valuables” is the quintessence of their business philosophy.

</asp:Panel>
</asp:Content>
Contactus.aspx:
CodeFile="contactus.aspx.cs" Inherits="contactus" Title="Untitled Page" %>
<asp:Panel ID="Panel1" runat="server" BorderColor="#003366" BorderStyle="Ridge"
BorderWidth="4px"
style="z-index: 1; left: 49px; top: 267px; position: absolute; height: 523px;

width: 903px"
BackColor="#FFCCCC">
<asp:Label ID="Label2" runat="server" Text="Contact Us"
style="position :absolute; top: 17px; left: 43px;" Font-Bold="True"
Font-Size="XX-Large" Font-Underline="True" ForeColor="#0000CC"></asp:Label>
<asp:Panel ID="Panel2" runat="server"
style="z-index: 1; left: 41px; top: 65px; position: absolute; height: 418px;
width: 823px">
<table class="style5" style="color: #003366">
<tr>
<td class="style7">
AHMEDABAD : F-10, New
 
Madhupura Market
 
Near Police Commissioner Office
 
AHAMEDBAD - 380 004. 
Ph:(079) 25627290, 25632147, 25632148,
 
E-mail : <a
href="mailto:amdgjtpcindia.com">amdgj@tpcindia.com</a></td>
<td class="style9">
BHUBANESHWAR : AROHI, 13/A
 
Unit - III, Station Square,
 
BHUBANESHWAR - 751 001 
Ph:(0674) 2535256,
 
E-mail:<a
href="mailto:tpcorissa@sify.com">tpcorissa@sify.com,</a>
<a href="mailto:bbior@tpcindia.com">bbior@tpcindia.com</a></td>
<td class="style14">
HYDERABAD : 501,5th Foor Jade
Arcade, Opp.
Hotel Paradise
 
M.G.Road,
 
SECUNDERABAD - 500 003.
 
Ph:(040) 27813344 (10 Lines) 
Fax - (040) 27813344
 
E-mail: <a href="mailto:tpcsebd@satyam.net.in">t</a>
<a href="mailto:hydap@tpcindia.com">hydap@tpcindia.com</a></td>
</tr>
<tr>
<table border="0" cellpadding="0" cellspacing="0"
class="totalframe" height="1"
width="100%">

<tr>
<td class="protitle" height="1" valign="middle"
width="498">
</td>
</tr>
<tr>
<td class="innerbox" height="1" valign="top">


</td>
</tr>
</table>
class="totalframe"
width="100%">
<tr>
width="516">
JAIPUR : 
</td>
</tr>
<tr>
#15, Motilal Atal Road,
 
Opp. Neelam Hotel, 
JAIPUR - 302 001. 
Ph : (0141) 2376261, 2360883 
 
E-mail : 
<a
href="http://us.f317.mail.yahoo.com/ym/Compose?To=maatn@tpcindia.com">
jprrj</a><a
href="http://us.f317.mail.yahoo.com/ym/Compose?To=maatn@tpcindia.com"
rel="nofollow" target="_blank"
ymailto="mailto:maatn@tpcindia.com">@tpcindia.com</a>,
</td>
</tr>
</table>
</td>
class="totalframe"
width="100%">

<tr>
width="516">

 
KOLKATA : 
</td>
</tr>
<tr>
No:1A, Raja Subodh Mullick Square 
Opp. Hind Cinema,
 
KOLKATA - 700 013.
 
Ph:(033) 30287046, 48, 49 
E-mail: <a
href="mailto:ccuwb@tpcindia.com">ccuwb@tpcindia.com</a></td>
</tr>
</table>
</td>



PATNA : 

#118, Ashoka Palace,
 
Exhibition Road, 
PATNA - 800 001. 
Ph : (0612) 5584239, 
 
E-mail : 
<a
href="http://us.f317.mail.yahoo.com/ym/Compose?To=maatn@tpcindia.com">
patbh@</a><a
href="http://us.f317.mail.yahoo.com/ym/Compose?To=maatn@tpcindia.com"
rel="nofollow" target="_blank"
ymailto="mailto:maatn@tpcindia.com">tpcindia.com</a>,
</td>
</tr>
<tr>
<td class="style6">
</td>
</td>
<td>
</td>
</tr>
<tr>
</td>
</td>
</td>
</tr>
</table>
</asp:Panel>
</asp:Panel>

 































</asp:Content>
Adminlogin.aspx:

CodeFile="adminlogin.aspx.cs" Inherits="admin_Add_an_employee" Title="Untitled Page" %>
<table width="100%" style="height: 300px">
<tr >
<td rowspan="3" style="width: 216px">
<img src="../admin/images/sending.jpg" style="width: 254px; height: 398px; border-
left-color: #006666; border-bottom-color: #006666; border-top-style: solid; border-top-
color: #006666; border-right-style: solid; border-left-style: solid; border-right-color:
#006666; border-bottom-style: solid;" /></td>
<td style="width: 274px; vertical-align: top;">
<img src="../admin/images/courier-and-delivery-services.jpg" style="width: 353px;
height: 108px; border-left-color: #006666; border-bottom-color: #006666;
border-top-style: solid; border-top-color: #006666; border-right-style: solid; border-
left-style: solid; border-right-color: #006666; border-bottom-style: solid;" /></td>
<img src="../admin/images/sidepic_couriers.jpg" style="width: 234px; height:
402px" /></td>
</tr>
<tr >
<td style="width: 274px; height: 144px; vertical-align: text-top; background-color:
#ccccff; border-left-color: #336666; border-bottom-color: #336666; border-top-style:
solid; border-top-color: #336666; border-right-style: solid; border-left-style: solid;
border-right-color: #336666; border-bottom-style: solid;">

<asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Names="Arial CE"
Text="Admin Login" BorderColor="#804000" BorderStyle="Groove"></asp:Label>
 
 
<asp:Label ID="Label2" runat="server" Font-Bold="True" Text="UserId:"></asp:Label>
<asp:TextBox ID="txtuid" runat="server"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="txtuid"
ErrorMessage="*"></asp:RequiredFieldValidator> 
 
<asp:Label ID="Label3" runat="server" Font-Bold="True"
Text="Password"></asp:Label>

<asp:TextBox ID="pwd" runat="server" TextMode="Password"></asp:TextBox>
ControlToValidate="pwd"


 

<asp:Button ID="signin" runat="server" Text="SignIn" Font-
Bold="True" OnClick="signin_Click" /> 
</td>
</tr>
<tr >
<td style="width: 274px; height: 76px;" rowspan="3">
<img src="../admin/images/image-main.jpg" style="border-left-color: #336666;
border-bottom-color: #336666;
width: 358px; border-top-style: solid; border-top-color: #336666; border-
right-style: solid;
border-left-style: solid; height: 80px; border-right-color: #336666; border-
bottom-style: solid" /></td>
</tr>
</table>
</asp:Content>
Adminlogin.aspx.cs:
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class admin_Add_an_employee : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void signin_Click(object sender, EventArgs e)
{
SqlConnection con = new
SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
con.Open();
SqlCommand cmd=new SqlCommand("select count(*) from admin where uname='" +
txtuid.Text + "' and password='" + pwd.Text+"'",con);
int i= Convert.ToInt16( cmd.ExecuteScalar());
if (i>0)
{
Response.Redirect("~/admin/adminprelvs.aspx");
}
else
{
Response.Write("<script>alert('Invalid username or password Try
again')</script>");
}
}
}
Courier/login.aspx:

CodeFile="login.aspx.cs" Inherits="courier_Default" Title="Untitled Page" %>
<tr >
402px" /></td>
</tr>
<tr >

Text="Courier Login" BorderColor="#804000" BorderStyle="Groove"></asp:Label>
 
 
 






 

Bold="True" OnClick="signin_Click" style="position: static" BackColor="#66FFFF"
ForeColor="#333366" /> 
</td>
</tr>
<tr >
right-style: solid;
</tr>
</table>
</asp:Content>
Login.aspx.cs:
using System;
using System.Data;
using System.Web;
public partial class courier_Default : System.Web.UI.Page

{
{
}
{

con.Open();
SqlCommand cmd = new SqlCommand("select count(*) from emp where empid='" +
txtuid.Text + "' and password='" + pwd.Text + "'", con);
int i = Convert.ToInt16(cmd.ExecuteScalar());
if (i > 0)
{
Response.Redirect("~/courier/courierprelvs.aspx");
}
else
{
Response.Write("<script>alert('wrong id or password please try
again')</script>");
}
}
}
Customer/login.aspx:
CodeFile="login.aspx.cs" Inherits="customer_login" Title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server"><table width="100%" style="height: 300px">
<tr >

402px" /></td>
</tr>
<tr >

Text="Customer Login" BorderColor="#804000" BorderStyle="Groove"></asp:Label>
 
 
 




 

<asp:HyperLink ID="HyperLink1" runat="server" Font-Bold="True" Font-Italic="True"
Font-Size="14pt" Height="1px" NavigateUrl="~/customer/customerreg.aspx"
Style="position: static"
Width="75px">Sign Up</asp:HyperLink>

Bold="True" OnClick="signin_Click" style="position: static" BackColor="#66FFFF"
ForeColor="#333366" /> 
</td>
</tr>
<tr >
right-style: solid;
</tr>
</table>
</asp:Content>
Login.aspx.cs:
using System;
using System.Data;
using System.Web;
public partial class customer_login : System.Web.UI.Page

{
{
}
{
SqlConnection con=new
con.Open();
SqlCommand cmd=new SqlCommand("select count(*) from customerreg where
customerid='"+txtuid.Text+"' and password='"+pwd.Text+"'",con);
int i =Convert.ToInt16(cmd.ExecuteScalar());
if (i > 0)
{
Response.Redirect("~/customer/customerprelvs.aspx");
}
else
{
Response.Write("<script>alert('wrong id or password please try
again')</script>");
}
}
Emplogin.aspx:
CodeFile="emplogin.aspx.cs" Inherits="employee_emplogin" Title="Untitled Page" %>
<tr >
402px" /></td>
</tr>
<tr >

Text="Employee Login" BorderColor="#804000" BorderStyle="Groove"></asp:Label>
 
 
 



 

Bold="True" OnClick="signin_Click" /> 
</td>
</tr>
<tr >
right-style: solid;
</tr>
</table>
</asp:Content>
Emplogin.aspx.cs:
using System;
using System.Data;
using System.Web;
public partial class employee_emplogin : System.Web.UI.Page

{
{
}
{
con.Open();
SqlCommand cmd=new SqlCommand("select count(*) from emp where empid='" +
txtuid.Text + "' and password='" + pwd.Text+"'",con);
int i= Convert.ToInt16( cmd.ExecuteScalar());
if (i>0)
{
Response.Redirect("~/employee/empprelvs.aspx");
}
else
{
Response.Write("<script>alert('Invalid username or password Try

again')</script>");
}
}
}
Blpayslip.cs:
using System;
using System.Data;
using System.Web;
/// <summary>
/// Summary description for payslip
/// </summary>
public class blpayslip
{
public blpayslip()
{
//
// TODO: Add constructor logic here
//
}
private string _empid;
public string empid

{
get { return _empid; }
set { _empid = value; }
}
private string _empname;
public string empname

{
get { return _empname; }
set { _empname = value; }
}
private String _salary;
public string salary

{
get { return _salary; }
set { _salary = value; }
}
private string _advances;
public string advances

{
get { return _advances; }
set { _advances = value; }
}
private string _incentives;
public string incentives

{
get { return _incentives; }
set { _incentives = value; }
}
private string _netsal;
public string netsal

{
get { return _netsal; }
set { _netsal = value; }
}
private string _dosal;
public string dosal

{
get { return _dosal; }
set { _dosal = value; }
}
public int payinsert()

{
//throw new Exception("The method or operation is not implemented.");
dalpayslip obj1 = new dalpayslip();
return obj1.payinsert(this);
}
public DataSet check()

{
return obj2.check(this);
}
public DataSet getsal()

{
return obj2.getsal(this);
}
}
Conclusion
The entire project has been developed and deployed as per the requirements stated by the user, it
is found to be bug free as per the testing standards that is implemented. Any specification-
untraced errors will be concentrated in the coming versions, which are planned to be developed
in near future. The system at present does not take care of the money payment methods, as the
consolidated constructs need SSL standards and are critically to be initiated in the first Phase; the
application of the credit card transactions is applied as a developmental phase in the coming
days. The system needs more elaborative technicality for its inception and evolution.

Attachment

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Attachment

Hochgeladen von

Copyright:

Verfügbare Formate

PROJECT REPORT

SOPHIA COLLEGE FOR WOMEN

“FRENCH COURIER MANAGEMENT”

Submitted to the University of Mumbai in partial fulfillment of the requirement for

NAME OF GUIDE: Ms. SIDRANAAZ KAZI Ms. RINJAL R.JAIN

NAME OF EXTERNAL EXAMINAR: _____________________________________

SIGNATURE: ________________________ DATE: __________________

This project deals with the ‘Courier Information System’. The

The aim of the project “COURIER MANAGEMENT”, which is website, is to

The courier service work as a destination office or source office .

The existing system has lot of problems such as:

2.2 CURRENT SYSTEM

a particular extent, it has to do a lot of manual work.

2.3 PROPOSED SYSTEM

2.4 BENEFITS OF PROPOSED SYSTEM

• Microsoft Visual Studio 2010.

• Microsoft SQL Server 2008

• Windows 8 or Windows 10 Professional Service Pack 1.

• Web Browser: Microsoft Internet Explorer 7.0, Mozilla, Google Chrome or

iii. HARDWARE REQUIREMNETS

• 1 or 2.5 GHZ Dual Core Processor.

• 3 or 4GB Hard Disk.

• Microsoft Visual Studio Database.

5.2 SOFTWARE REQUIREMENTS

5.3 FEASIBILITY STUDY

5.4 OPERATIONAL FEASIBILITY:

• The usability will be high.

5.5 TECHNICAL FEASIBILITY:

5.6 ECONOMIC FEASIBILITY:

• The economic feasibility study evaluate the cost of the

This Project “FRENCH COURIER MANAGEMENT” is developed at a small

They are as follows:

• Effort taken to develop and design the system.

• ASP.NET is object-oriented programming language. ASP.NET support web

• ASP.NET is used to produce interactive, data-driven web applications over

• It is purely server-side technology so, ASP.NET code executes on the server

6.2 BACK END: MICROSOFT SQL SERVER 2010

• The software development life cycle (SDLC) is a framework defining

7.2 SYSTEM DEVELOPMENT PHASES

7.3 PHASES IN SOFTWARE DEVELOPMENT LIFE CYCLE

There are following six phases in every Software Development Life

• Requirement gathering and analysis

• In census system it helps to gather the information about municipal offices,

Phase 2: Defining Requirements:

• The census web application is developed on freeware Microsoft Visual

On receiving system design documents, the work is divided in modules/units and

• After the successful testing of census application the website will be

Waterfall Model - Design

Waterfall Model - Application

Waterfall Model - Advantages

THE UNIFIED MODELINGLANGUAGE

The Unified Modeling Language (UML) is a standard language for writing

DIAGRAMS IN THE UML

A diagram is the graphical presentation of a set of elements, most often rendered

8.1 ENTITY RELATIONSHIP

Symbol Shape Name Symbol Description

An entity that cannot be

Actor in a use case diagram is any entity that

A use case represents a function or an action

System is used to define the scope of the use

It indicates that the use case to which the arrow

An extend relationship specifies how the

DFD DIAGRAM’S SYMBOLS

ACTIVITY DIAGRAM SYMBOLS, MEANINGS AND RULES

SIGNATURE: ______ DATE: