Report
UNDER SUPERVISION OF G.S.Baluja
SUBMITTED BY NAME: ENROLMENT NO:
Submitted in partial fulfillment of the requirements of the degree of
BCA 1
Administrative & Logistic Management System for Courier Company
Under Supervision of
:
Submitted By: Name
:
Programme Code
:
Enrollm Enrollment ent No.
:
Study centre
:
BCA
ACKNOWLEDGEMENT
2
Administrative & Logistic Management System for Courier Company
Under Supervision of
:
Submitted By: Name
:
Programme Code
:
Enrollm Enrollment ent No.
:
Study centre
:
BCA
ACKNOWLEDGEMENT
2
With Candor and Pleasure I take opportunity to express my sincere thanks and obligation to my esteemed guide G.S.Baluja. It is because of his able and mature mature guidan guidance ce and co-ope co-operati ration on witho without ut which which it would would not have have been been possible for me to complete my project. It is my pleasant duty to thank all the staff member of the computer center who never hesitated me from time during the project.
Finally, I gratefully acknowledge the support, encouragement & patience of my family, and as always, nothing in my life would be possible without God, Thank You!
Amit Tuteja
3
DECLARATION
ADMINISTRATIVE & LOGISTIC I hereby declare that this project work titled “ADMINISTRATIVE MANAGEMENT SYSTEM COURIER BOOKING” is my original work and no
part of it has been submitted for any other degree purpose or published in any other from till date.
Amit Tuteja
4
Administrative & Logistic Management System for Courier Company
TABLE OF CONTENTS Acknowledgment
3
Declaration
4
1. Introduction & Objectives of the Project
8
1.1 Introduction
8
1.2 Objectives
8
1.3 Advantage
9
1.4 Drawback of Current Manual-System
10
1.5 Proposed System
11
1.6 Need
15
2. System Study 2.1 Preliminary Investigation
24
2.2 System Development Life Cycle
25
3. System Analysis
4.
3.1 Importance of Computerized System
30
3.2 Principle of System Analysis
31
System Design
4.1 Design Objectives
34
4.2 Data Modeling
40
4.3 E-R Diagram
41
4.4 Context Level DFD
42
4.5 Modules
48 5
4.6 Process Logic for Each Modules
51
4.7 Tool/Platform, Hardware and Software Requirement Specification 54 4.8 Scheduling
56
5. System Development 5.1 Source Code
59
5.2 Code Efficiency
208
5.3 Optimization of code
208
6.
Testing
6.1 Testing Phase
210
6.2 Level of Testing
211
6.3 Verification and Validation (V&V)
216
7.
System Implementation
7.1 7.2 7.3 7.4 7.5
Post Implementation Maintenance and Review Hardware Evaluation Factors Software Evaluation Factors Conversion and Training Training Needs
219 220 221 222 223
8.
Cost Estimation of the Project
224
9.
GANTT & PERT CHART
222
10. Security and Validations
228
11. Scope of Future Application
229
12. Conclusion
230
13. Bibliography
162
6
7
This system is being developed to manage a process known as Trading, which is one of the basic pillars in development of human society. This system, which is known as ‘Administrative & Logistic Management System for Courier Company’, is useful for courier companies, which acts as a carrier to carry goods from one place to another, to and from all stations where it operates. A shipper sends some consignment to the buyer and charge transportation charges to carry those goods.
1.2 Objectives of the Project 1. The main objective of ‘‘Administrative & Logistic Management System for Courier Company’
is to manage the whole courier booking and distribution
process, so that an error free transaction can be done. Other objectives which this system possess are :
2. This software is developed keeping customer in focus. I have tried to make the whole logic of system very easy and understandable, so that transparency can be achieved. It is very necessary to make system understandable as any person who is giving business to airline (known as Customer), has right of information. At any point of time, a customer can ask about the status of its courier. So, to provide a proper customer service, the system should be able to tell about the current status of courier.
3. ‘‘Administrative & Logistic Management System for Courier Company’’
is
developed to make process of booking, planning and delivery of Courier very easy and manageable. This system will be mostly used by Courier Companies Employees so, it is very necessary to make their work systematic and ergonomic. All modules will be easy to use.
4. As whole Courier trade is based on commercialism, so accounting should be an integrated part of such system. So, this system should manage all accounts and keeps records of amount credited and debited on individuals.
8
5. To manage user profiles and to validate who can do business on credit basis and who cannot.
I have designed the given proposed system in the ASP.NET to automate ‘‘Administrative & Logistic Management System for Courier Company’ ’. The following steps that give the detailed information of the need of proposed system are: Performance: During past several decades, the records are supposed to be manually handled for all activities. The manual handling of the record is time consuming and highly prone to error. To improve the performance of the Company system, the computerized system is to be undertaken. The computerized project is fully computerized and user friendly even that any of the members can see the report and status of the company. Efficiency: The basic need of this website is efficiency. The website should be efficient so that a user can track his courier. The website is updated by the administrator. This record will be useful for other users instantly. Control: The complete control of the project is under the hands of authorized person who has the password to access this project and illegal access is not supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry. Security: Security is the main criteria for the proposed system. Since illegal access may corrupt the database. So security has to be given in this project.
9
1.4 DRAWBACKS OF CURRENT MANUAL- SYSTEM
•
The current manual system has a lot of paper work and it does not
deal with old and new car purchase and sale. •
To maintain the records of sale and service manually, is a Time-
consuming job. •
With the increase in database, it will become a massive job to
maintain the database. •
Requires large quantities of file cabinets, which are huge and
require quite a bit of space in the office, which can be used for storing records of previous claims. •
The retrieval of records of employees will be a tedious job.
•
Lack of security for the records, anyone disarrange the records of
your system.
10
ESTABLISH THE NEED OF NEW SYSTEM
Problem of Reliability: Current system is not reliable. It
1.
seems to vary in quality from one month to the next. Some times it gives good output, but some times the output is worst.
Problem of Accuracy: There are too many mistakes in
2.
reports.
3.
Problem of timeliness: In the current system the reports
and output produced is mostly late and in most of the cases it is useless because it is not on time.
4.
Problem of Validity: The output and reports mostly contains
misleading information. The customer's information is sometimes not valid.
5.
Problem of Economy: The current system is very costly.
We have to spend lots of money to keep the system up and going, but still not get the desired results.
6.
Problem of Capacity: The current system is suffering from
problem of capacity also. The staff for organization is very less and the workload is too much. Few peoples cannot handle all the work.
1.5 PROPOSED SYSTEM
1.
Details: The new proposed system stores and maintains all the eye bank details,donators details,nodal hospital details etc.
2. Calculations: The new proposed system updates tables and other
information automatically and it is very fast and accurate. 3. Registers: There is no need of keeping and maintaining salary and
information manually. It remembers each and every record and we can get any report at any time. 11
4. Speed: The new proposed system is very fast with 100% accuracy and saves time. 5. Manpower: The new proposed system needs less manpower. Less
people can do the large work. 6. Efficiency: The new proposed systems complete the work of many people in less time. 7. Past details: The new proposed system contains the details of every
past claims taken by the employees.
8. Reduces redundancy: The most important benefit of this system is
that it reduces the redundancy of data within the data. 9. Work load: Reduces the work load of the data store by helping in
easy updates of the products and providing them with the ne ce ssar y
det ai ls
t oget her
wi th
f in an ci al
t ra ns ac ti on s
management. 10. Easy statements: Month-end and day-end statement easily taken
out without getting headaches on browsing through the day end statements.
1.6 NEED I have designed the given proposed system in the ASP.NET to automate the process of ADMINISTRATIVE & LOGISTIC MANAGEMENT SYSTEM COURIER BOOKING. This project is useful for the authorities who keep track of all the
eye bank details . The following steps that give the detailed information of the need of proposed system are: •
Performance: During past several decades, the records are supposed to be manually handled for all activities. The manual handling of the record is time consuming and highly prone to error. To improve the performance of the system, the computerized 12
system is to be undertaken. The computerized project is fully computerized and user friendly even that any of the members can see the report and status of the eye bank.
•
Efficiency: The basic need of this website is efficiency. The website should be efficient so that whenever a new user submits his/her details the website is updated automatically. This record will be useful for other users instantly.
•
Control: The complete control of the project is under the hands of authorized person who has the password to access this project and illegal access is not supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry.
•
Security: Security is the main criteria for the proposed system. Since illegal access may corrupt the database. So security has to be given in this project.
13
SOFTWARE & HARDWARE REQUIREMENTS “Client-Server approach with XML / ASP.NET” The need of today’s software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications.
FRONT END .NET programming tools are complete programming environments. It allows programmers to build a GUI program using the various on-screen controls such as buttons, text, menus, boxes etc. These controls are placed on a form and then the processing details related with each control are filled in.
In the business world, competitive strategies have become the order of the day to improve quality, cut costs and provide a high response customer service base. Most organizations today need to be market driven and do a lot of value addition to their products and services. This naturally calls for rational decision making, which requires information. Information Technology or IT provides that effective channel to support and implement this strategy. Client/Server is the technology that empowers the desktop, thus setting a trend for the way successful organizations will use technology in the next decade.
INTRODUCTION TO .NET What is .NET? •
A vision of how information technology will evolve
•
A platform that supports the vision
•
A business model of software as a service
14
1. A Vision. •
Web sites will be joined by Web services
•
New smart devices will join the PC
•
User interfaces will become more adaptable and customizable
•
Enabled by Web standards
2. A Platform. •
The .NET Framework
•
Visual Studio.NET
•
.NET Enterprise Servers
o Database, Messaging, Integration, Commerce, Proxy, Security, Mobility, Orchestration, Content Management •
.NET Building Block Services
o Passport o .NET My Services (“Appin”) •
Goal: make it incredibility easy to build powerful Web applications and Web services
3. A business model. •
Software as a service
•
Subscription-based services
•
Application hosting, e.g. bCentral
Interoperability: Web languages and protocols must be compatible with one another independent of hardware and software.
Evolution: The Web must be able to accommodate future technologies. Encourages simplicity, modularity and extensibility.
Decentralization: Facilitates Scalability and Robustness. Web Services •
A programmable application component accessible via standard Web protocols
•
The center of the .NET architecture
•
Exposes functionality over the Web 15
•
Built on existing and emerging standards
are HTTP, XML, SOAP,
UDDI, WSDL, …
The .NET Framework
What is the .NET Framework? •
A set of technologies for developing and using components to create:
o Web Forms o Web Services o Windows Applications •
Supports the software lifecycle
o Development o Debugging o Deployment o Maintenance •
Application Architectures
o The Different types of Applications may vary from single-tier desktop applications (applications that follow the single-tier architecture) to multi-tier applications (applications that follow the two-, three, or n-tier architecture)
o Single-tier architecture 16
−
A single executable file handles all functions relating to the user, business, and data service layers. Two-tier architecture
o −
Divides an application into the following two components:
Client
Server
o Three-tier architecture −
All the three service layers reside separately, either on the same machine or on different machines.
o n-tier architecture −
Uses business objects for handling business rules and data access.
−
Has multiple servers handling business services.
The .NET Initiative •
The introduction of the Internet and its rapid growth in the recent past has led to the development of a number of new Technologies.
•
One of the most important requirements of such applications is the ability to interchange information across platforms and to benefit from the functionality provided by
•
other applications.
In the current scenario, although applications serve
organization-
specific requirements, they are not interoperable. Microsoft has introduced the .NET initiative with the intention of bridging the gap in interoperability between applications. •
The .NET initiative offers a complete suite for developing and deploying applications, which consists of the following:
o NET products: Microsoft has already introduced Visual Studio .NET, which is a tool for developing NET applications by using programming languages such as Visual Basic, C#, and Visual C++.
o NET services: Microsoft is coming up with its own set of Web services, known as My Services. These services are based on the Microsoft Passport Authentication service, the same service that is used in Hotmail. 17
Explanation of the .NET Framework •
Is a collection of services and classes?
•
Exists as a layer between .NET applications and the underlying operating system.
•
Encapsulates much of the functionality, such as debugging and security services.
•
The following figure depicts the components of the .NET Framework:
The .NET Framework Base Classes or the .NET Class Framework •
Consists of a class library that works with any .NET language, such as Visual Basic .NET and C#.
•
Provides classes that can be used in the code to accomplish a range of common programming tasks.
•
Comprises
o Namespaces: Namespaces help you to create logical groups of related classes and interfaces that can be used by any language targeting the .NET Framework.
o Assembly: An assembly is a single deployable unit that contains all the information about the implementation of classes, structures, and interfaces. •
The Common Language Runtime
o Provides functionality such as exception handling, security, debugging, and versioning support to any language that targets it.
o Can host a variety of languages and offer a common set of tools across these languages, ensuring interoperability between the codes. •
Provides the following features:
o Automatic memory management o Standard type system o Language interoperability 18
o Platform independence o Security management o Type safety
Advantages of the .NET Framework •
Some advantages of the .NET Framework are:
o Consistent programming model o Multi-platform applications o Multi-language integration o Automatic resource management o Ease of deployment
ADO.NET •
Is a model used by Visual Basic .NET applications to communicate with a database for retrieving, accessing, and updating data?
•
Uses a structured process flow to interact with a database.
ADO .NET Data Access Most applications need data access at one point of time making it a crucial component when working with applications. Data access is making the application interact with a database, where all the data is stored. Different applications have different requirements for database access. VB.NET uses ADO.NET (Active X Data Object) as it's data access and manipulation protocol, which also enables us to work with data on the Internet. Let's take a look
why
ADO.NET
came
into
picture
replacing
ADO.
Evolution of ADO.NET The first data access model, DAO (data access model) was created for local databases with the built-in Jet engine which had performance and functionality issues. Next came RDO (Remote Data Object) and ADO (Active Data Object) which were designed for Client Server architectures but soon ADO took over RDO. ADO was a good architecture but as the language changes so is the technology within it. With ADO, all the data is contained in a 19
record set object which had problems when implemented on the network (Internet) and penetrating firewalls. ADO was a connected data access which means that when a connection to the database is established the connection remains open until the application is closed, which raises concerns about database security and network traffic. And also as databases are becoming increasingly important and as they are serving more people a connected data access model makes us think about its use. For example, an application with connected data access may do well when connected to two clients, the same may do poorly when connected to 10 and might be unusable when connected to 100 or more. Also, open database connections use system resources to a maximum
extent
making
the
system
performance
less
effective.
Why ADO.NET? To cope up with some of the problems mentioned above, ADO.NET came into existence.
ADO.NET
addresses
the
above
mentioned
problems
by
maintaining a disconnected database access model which means that when an application interacts with the database the connection is opened to serve the request of the application and is closed as soon as the request is completed. Likewise if a database is updated, the connection is opened long enough to complete the Update operation and is closed. By keeping connections open for only a minimum period of time ADO.NET conserves system resources and provides maximum security for databases and also has less impact on system performance. Also, ADO.NET when interacting with database uses XML by converting all the data into XML and using it for database
related
operations
making
them
more
efficient.
Features of ADO.NET •
Disconnected data architecture — Applications connect to the database only while retrieving and updating data.
•
Data cached in datasets — ADO.NET is based on a disconnected data structure. Therefore, the data is retrieved and stored in datasets.
•
Data transfer in XML format — ADO.NET uses XML for transferring information from a database into a dataset and from the dataset to another component. 20
•
Interaction with the database is done through data commands.
ADO.NET Object Model Key Components of the ADO.NET Model Data Provider • o Is used for connecting to a database, retrieving data, and storing the data. •
Is of two types:
o OLE DB data provider o SQL Server data provider
Components of a Data Provider •
Connection o Used to establish a connection with a data source
o Some commonly used properties and methods:
•
ConnectionString property
Open()method
Close()method
State property
Data adapter o Creates a dataset and updates the database.
o Handles data transfer between the database and the dataset through its properties and methods.
o Displays the data through the process of table mapping. o Are of two types:
•
SqlDataAdapter
OleDbDataAdapter
Data command
o Is a SQL statement or a stored procedure that is used to retrieve, insert, delete, or modify data from a data source.
o Is an object of the OleDbCommand or SQLCommand class. •
Data reader
21
o Is used to retrieve data from a data source in a read-only and forward-only mode.
o Stores a single row at a time in the memory. o Commonly used methods:
•
Read()
Close()
NextResult()
Dataset
o Is a disconnected, cached set of records that are retrieved from a database.
o Is present as a DataSet class in the System.Data namespace. o Has its own object model.
22
23
2.1 PRELIMINARY INVESTIGATION System development, a process consisting of two major steps of system analysis and design, start when management or sometimes system development personnel feel that a new system or an improvement in the existing system is required. The system development life cycle is classically thought of as the set of activities that analysts, designers and users carry out to develop and implement an information system. The system development life cycle consists of the following activities:
Preliminary investigation
Determination of system requirements
Design of system
Development of software
System testing
Implementation, evaluation, and maintenance
A request to take assistance from information system can be made for many reasons, but in each case someone in the organization initiates the request is made, the first system activity the preliminary investigation begins. This activity has three parts: 1) Request clarification 2) Feasibility study 3) Request approval
Request clarification: Many requests from employees and users in the organizations are not clearly defined, therefore it becomes necessary that project request must be examined and clarified properly before considering systems investigation.
24
2.2 SYSTEM DEVELOPMENT LIFE CYCLE Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic world, the subject System Analysis and Design (SAD), mainly deals with the software development activities.
DEFINING A SYSTEM A collection of components that work together to realize some objective forms a system. Basically there are three major components in every system, namely input, processing and output. In a system the different components are connected with each other and they are interdependent. For example, human body represents a complete natural system. We are also bound by many national systems such as political system, economic system, educational system and so forth. The objective of the system demands that some output is produced as a result of processing the suitable inputs.
SYSTEM LIFE CYCLE System life cycle is an organizational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required for developing a system. System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle means software development life cycle.
25
Following are the different phases of software development cycle:
System study
Feasibility study
System analysis
System design
Coding
Testing
Implementation
Maintenance
26
The Different Phases Of Software Development Life Cycle Are Shown Below. PRELIMINARY INVESTIGATION
DETERMINATION OF REQUIREMENTS
REVIEW RUNNING SYSTEM AND SYSTEM MAINTENANCE
DEVELOPMENT OF PROTOTYPE SYSTEM
SYSTEM IMPLEMENTATION
DESIGN OF SYSTEM
DEVELOPMENT OF SOFTWARE AND CODING
SYSTEM TESTING SYSTEM ANALYSIS 50% DESIGN DESI GN OF SYST EM
30%
CODING 20%
FIG: SHOWING GENERAL LIFE CYCLE PROCESS AND PERCENTAGE OF TIME DEVOTED
27
A system analysis is a separation of a substance into parts for study and their implementation and detailed examination. Before designing any system it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination provides the specific data required during designing in order to ensure that all the client's requirements are fulfilled. The investigation or the study conducted during the analysis phase is largely based on the feasibility study. Rather it would not be wrong to say that the analysis and feasibility phases overlap. High-level analysis begins during the feasibility study. Though analysis is represented as one phase of the system development life cycle (SDLC), this is not true. Analysis begins with system initialization and continues until its maintenance. Even after successful implementation of the system, analysis may play its role for periodic maintenance and up gradation of the system. One of the main causes of project failures is inadequate understanding, and one of the main causes of inadequate understanding of the requirements is the poor planning of system analysis. Analysis requires us to recall the objectives of the project and consider following three questions:
What type of information is required?
What are the constraints on the investigation?
What are the potential problems that may make the task more difficult?
28
29
3.1 IMPORTANCE OF COMPUTERIZED ADMINISTRATIVE & LOGISTIC MANAGEMENT SYSTEM There are several attributes in which the computer based information works. Broadly the working of computer system is divided into two main groups: ♦
Transaction System
♦
Decision Support System
Transaction System: A transaction is a record of some well-defined single and usually small occurrence in a system. Transactions are input into the computer to update the database files. It checks the entering data for its accuracy. This means that numeric data appears in numeric field and character data in character field. Once all the checks are made, transaction is used to update the database. Transaction can be inputted in on-line mode or batch mode. In on-line mode, transactions are entered and updated into the database almost instantaneously. In batch mode, transactions are collected into batches, which may be held for a while and inputted later.
Decision Support System: It assists the user to make analytical decision. It shows the various data in organized way called analysis. This analysis can be made to syrdy preferences and help in making decisions. Computer system works out best with record maintenance. It will tell you which customer would get how much pending/reports statements. It will also help to search the information about a particular person by simply entering his telephone number. User can store information as per requirement, which can be used for comparison with other reports.
30
3.2 PRINCIPLES OF SYSTEM ANALYSIS Principles: 1.
Understand the problem before you begin to create the
analysis model. 2.
Develop prototypes that enable a user to understand how
human machine interaction will occur. 3.
Record the origin of and the reason for every requirement.
4.
Use multiple views of requirements like building data,
function and behavioral models. 5.
Work to eliminate ambiguity.
A Complete Structure:
The limited time and resources have restricted us to incorporate, in this project, only the main activities that are performed in news sites, but utmost care has been taken to make the system efficient and user friendly.
For the optimum use of practical time it is necessary that every session is planned. Planning of this project will include the following things: • • • •
Topic Understanding. Modular Break – Up of the System. Processor Logic for Each Module. Database Requirements.
Topic Understanding: It is vital that the field of application as introduced in the project may be totally a new field. So as soon as the project was allocated to me, I carefully went through the project to identify the requirements of the project.
31
Modular Break –Up of the System:
Identify The Various Modules In The System. List Them In The Right Hierarchy. Identify Their Priority Of Development Description Of The Modules:
32
33
The final deliverable from system analysis is a document containing an unambiguous statement of the client's requirements from the new system and what the development project will have to deliver in order to be considered a success. The functional specification is the starting point for designing, which depends to a large extent on the accuracy and thoroughness with which the analysis has been carried out. Understanding of the business, appreciation of the client's problems and documentation of requirements provide the foundation on which the designing is based. A key factor in this approach is the use of the structured techniques. Analysis ends with a description of what the new system must do to fulfill the requirements of the organization, while design specifies how this will be done by selecting one of the many ways of doing it.
DESIGN
ANALYSIS Describing WHAT the The gap
System will do?
Describing HOW the system will do it
The structured techniques used during the analysis which provide this logical view are:
• Data flow diagrams - representing the process, which manipulate the data as it passes through the system. • Entity model - showing the relationship within the data items held within the system. • A data dictionary - providing an overall consistent definition of the data used during the system development. This definition includes the content of the data stores, data flows and the process shown on the data flow diagrams, and the entities that make up the entity model. 34
4.1 DESIGN OBJECTIVES AND CONSTRAINTS: Flexible –
The design would enable future requirements of the organization to be incorporated without much difficulty. Often the organizational needs and objectives change over time and hence such a design enables the system to reflect these changes.
• Maintainable -
A good design is easy to maintain and this reduces the client's maintenance cost, which usually represents a proportion of the lifetime of the system.
• Portable -
A client for whom the software was developed may wish to change the hardware on which the system run. A good design is portable - in other words it is capable of being transferred from one machine environment to another with minimum amount of effort.
• Easy to use -
With increasing number of general users having exposure to computers and access to web sites, expectations of computer applications in term of their ease of use are also increasing. A good design will result in a system which is `user - friendly' - easy to understand, not difficult to learn how to use and straightforward to operate.
• Reliable -
The system designed must be secure against human error, deliberate misuse or machine failure, and which the data will be stored without corruption.
35
4.2 Data Modeling Describing Data Elements : Each entry in the data dictionary consists of a set of details describing the data used or produced in the system. Each item is identified by a data name, description, alias, and length and has specific values that are permissible for it in the system being studied.
User Table Field Name
Type
Constrains
User id
Char (30)
Primary key
User Name
Char (30)
Not Null
Password
Char (30)
Not Null
Email
Char (30)
Not Null
Address
Char (30)
Not Null
Phone
Numeric
Not Null
Field Name
Type
Constrains
User name
Char (30)
Primary key
Password
Char (30)
Not Null
ADMIN TABLE
COURIER TABLE Field Name
Type
Constrains
Reg. No.
Char (30)
Primary Key
Shipper Name
Char (30)
Not Null
S Address
Char (50)
Not Null
S Phone
Numeric
Not Null
S Email
Char (30)
Not Null
Receiver Name
Char (30)
Not Null
R Address
Char (30)
Not Null
R Phone No.
Numeric
Not Null
36
R City
Char (30)
Not Null
R Pin
Numeric
Not Null
Country
Char (30)
Not Null
Amount
Numeric
Not Null
Time
Date/ Time
Not Null
Date
Date/ Time
Not Null
Weight
Numeric
Not Null
AGENT TABLE Field Name
Type
Constrains
Agent_Id
Char (30)
Primary key
Agent Name
Char (30)
Not Null
Address
Char (30)
Not Null
City
Char (30)
Not Null
Phone
Numeric
Not Null
MNFST TABLE (Contain Summery of Shipments sent to a Particular Station) Field Name
Type
Constrains
Mnfst ID
Char (30)
Primary key
Pieces
Numeric
Not Null
Weight
Numeric
Not Null
Remarks
Char (100)
Not Null
37
RATE TABLE (Contains rate applicable on each shipment) Field Name
Type
Constrains
Orgn
Char (30)
Not Null
Destination
Char (30)
Not Null
Rate Min
Numeric
Not Null
Rate Q100
Numeric
Not Null
Rate Q300
Numeric
Not Null
Rate Q500
Numeric
Not Null
DIMENSION TABLE Field Name
Type
Constrains
Courier No
Char (30)
Not Null
Length
Numeric
Not Null
Weight
Numeric
Not Null
Width
Numeric
Not Null
Height
Numeric
Not Null
Piece
Numeric
Not Null
BOOKING BRANCH TABLE Field Name
Type
Constrains
Branch id
Char (30)
Primary Key
Name
Char (30)
Not Null
Address
Char (30)
Not Null
Phone
Numeric
Not Null
Email
Char (30)
Not Null
38
DO TABLE Field Name
Type
Constrains
DONO
Char (30)
Primary Key
Courier_id
Char (30)
Not Null
Pieces
Char (30)
Not Null
Origin
Char (30)
Not Null
Destination
Char (30)
Not Null
Amount Paid
Numeric
Not Null
Weight
Numeric
Not Null
Remark
Char (100)
Not Null
SEGREGATION TABLE (Registers all discrepancies in shipments and record of action steps taken thereafter) Field Name
Type
Constrains
Courier Id
Char (30)
Not Null
Origin
Char (30)
Not Null
Destination
Char (30)
Not Null
Descrep Detail
Char (100)
Not Null
Action Tkn
Char (100)
Not Null
39
An Entity Entity-Rela -Relatio tionsh nship ip model model is an abstrac abstractt concep conceptua tuall repres represent entati ation on of structural data. In an E-R Diagram, Data objects are represented by labeled rectangles and Relationships are indicated with diamonds. Connections between data objects and relat relatio ions nshi hips ps are are esta establ blis ishe hed d usin using g a vari variety ety of speci special al conn connect ectio ion n line lines. s. In ‘Administrative & Logistic Management System for Courier Company’ , identified identified
Data objects or Entities are given below:
40
Na me
Name Address Cust Id
Date
City N
Agent Id
City
N
Books Courier
Customer
Address
Tim e
Agent
Forwar d Na me
Addr ess
Branch Id
City
Consignment No
Branch Date
Id
Delive rs To
1
Delivery Slip ID N
N
Shippe d To
Shipping
41
1. ADMIN
2. Customer
3. Agent
Administrative & Logistic Management System for Courier Company
6. Delivery Module
5. Booking
42
7. Shipping
DFD for ADMIN
Password & username
1.1 Validate Password & username
USER
Not Validated
1.3 Error Message Screen
Not Validated
1.2 Main Screen
43
DFD for Customer
Customer data 2.1 Accept the customer data Customer
Update Date Customer data
Customer
2.3 Display DATATA
Screen / Print
44
DFD for Agent
Agent Data 3.1 Accept agent data Agent
Update Date Agent data
3.2 Display Agent Data
Agent
Screen | Print
45
DFD for Branch
Accept Data 3.1 Accept Branch data Branch
Update Date Branch data
3.2 Display Branch Data
Screen | Print
46
Branch
DFD for Booking Booking Courier
Customer
Bill
5.1 Accept Courier
5.2 Forward to branch
5.3 Shipped
5.4 Delivery to customer
47
4.5 Modules Number of Modules and their description: 1.1 Password Module
In this module, this website is for multiple users. If a User enters a password and the software checks its validity. If the password is valid then option is given to change the password, otherwise “Invalid User/Password” message is displayed. There is an option for password recovery, log out, login, new users sign in. The Administrator can also update changes in the site after login. 1.2 Creating new Entities ( Users , Courier, Agents, Rates, Administrator)In
this module, whenever a new entity is required to be added the corresponding forms are opened and the database is manipulated to check whether the data is already existing or not. If it already exists, then it prompts that “Entry already existing” and if not than the data is entered with the various validation checks.
1.3 Modifying / Updating Existing Entities
In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the administrator can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry.
1.4 Searching
In this module, whenever an existing entity is required to be searched the corresponding forms are opened and the database is manipulated and the data is fetched. Again, the checks are followed in case there is any invalid entry.
1.5 Booking Module
This module deals with booking of the courier. A shipper or its agent puts the details of the goods which he wants to send to an active destination. He can just put mandatory data to request a booking and rest of the information for complete booking can be provided later on, which facilitates shipper as sometimes shipper doesn’t have full information.
48
1.6. Reconciliation Module
This module comes into effect at Destination stage there. All Courier is checked as per the manifest and all discrepancies like pilferage, tear and wear etc. are noted. All shipments which are received in good condition are kept in warehouse. 1.7
Courier Arrival Notification Module
A Courier Arrival Notice is send to Consignees of all shipments which were received in good condition from Origin Station using this module. 1.8
Courier Delivery Module
That entire Courier, which is lying at Import Warehouse of a station and bears no discrepancy, can be delivered to Consignee. At this stage, Courier is delivered to consignee or its authorized agent using a Delivery Challan, and amount pertaining to shipment, if any, is collected from them.
1.9
Bill Status Module
Using this module, we can display the whole Consignment Note. It shows all details of a Bill and its current status. 1.10
Dimensions Module.
This module contains dimensions of all pieces of each consignment. As weight of each piece matters, likewise volume of each piece is also required because we have to accommodate shipment into the aircrafts, railways.
1.11
Discrepancies Module.
When shipment reaches destination, Courier check is done under Reconciliation Module. Any discrepancy found there is registered under Discrepancy Module and a report is sent to Origin Station for further action. All shipments which lies under discrepancy list, are not delivered to consignee or its authorized agent until the discrepancy is solved.
49
COMPLETE STRUCTURE: The limited time and resources have restricted us to incorporate, in this project, only the main activities that are performed in Courier Company, but utmost care has been taken to make the system efficient and user friendly.
For the optimum use of practical time it is necessary that every session is planned. Planning of this project will include the following things: Topic Understanding. Modular Break – Up of the System. Processor Logic for Each Module. Database Requirements.
Topic Understanding: It is vital that the field of application as introduced in the project may be totally a new field. So as soon as the project was allocated to me, I carefully went through the project to identify the requirements of the project. Modular Break –Up of the System: Identify The Various Modules In The System. List Them In The Right Hierarchy. Identify Their Priority Of Development Description Of The Modules:
50
Bill Generation
Input input data to request a booking Proces A new AWB is created or existing AWB gets s updated. Output Bill is ready to be planned for loading
Input
All finalised Bills are available at warehouse for planning Process Bills are selected on basis of destination and priority Output A Pre-Manifest is generated for load planning
Pre
Manifestation
Input Proces s
Manifest
Segregation
Output
Pre Manifest report after loading on transport Offloaded Courier is eliminated from Pre Manifest and rest Courier is finalised and Manifest report is generated. Manifest report is sent to Destination.
Input Proces s Output
Manifest report for a particular area Courier is checked physically and any discrepancy is registered and informed to Origin Station. Segregation report of received Courier.
Input
Shipments which are received at Destination without any discrepancy. Proces A notice is prepared to be sent to Consignee to inform them to collect their Courier. s Output Courier Arrival Notice. CAN
51
Input
All Bills which bears no discrepancy and are related to one Consignee. Process All such Bills are listed, date and time of delivery is noted. Any amount pending on any Bill is also shown in report. Output Delivery Challan Report is generated for record purpose.
Courier Delivery
Input Shipments which are delivered Process Amount of all shipments booked within a particular time period by individual agent or shipper are listed and total amount due on them is shown in list Output CSR is generated and sent to those agents or shippers for releasing payment. Courier Sales Report
52
Report Generation 'Crystal Reports' is a popular third party package that is included with .NET, which allows you to create reports for your application. The package consists of a designer where you can design and test the reports, Crystal Reports API calls and Crystal Report Viewer control. The administrator can generate following reports
1. Report on different Users: This report contains total no. of Users
Logged in the system (such as in a day, week, month etc.).
2. Report on Courier Details: This report contains how many couriers booked in
the system (such as in a day, week, month etc.).
3. Report on discrepencies listing: This report contains the time taken in delivering
courier.
4. Report on tracking couriers: This report contains information about courier
from origin to destination.
5. Report on different agencies: This report contains total no. of agencies of a
courier company.
6. Report on different transactions: This report contains the total no. of
transactions.
53
4. 7.
Tools/Platform used are:
FRAMEWORK:- ASP.NET version 2 .0 with C# DATABASE:- SQL Server PLATFORM USED:- Windows XP
S/w Requirement specification:
.NET framework 2.0 Visual Studio.NET 2005 ASP.NET ADO.NET SQL Server 2005 Visual C#.NET HTML Internet Information Services (IIS) v 5.1
H/w Requirement specification: Pentium 3, 1.5 GHz and above 256 MB DDRAM or more 20 GB HDD Pen Drive 2Gb
Advantages of the .NET Framework •
Some advantages of the .NET Framework are:
o Consistent programming model o Multi-platform applications o Multi-language integration o Automatic resource management 54
o Ease of deployment
Security •
Evidence-based security (authentication)
•
Based on user identity and code identity
•
Configurable policies
•
Imperative and declarative interfaces
Microsoft SQL Server is an application used to create computer databases for the Microsoft Windows family of server operating systems. It provides an environment used to generate databases that can be accessed from workstations, the web, or other media such as a personal digital assistant (PDA). Microsoft SQL Server is probably the most accessible and the most documented enterprise database environment right now. This also means that you can learn it a little quicker than most other database environments on the market.
55
4.8 SCHEDULING Scheduling of a software project does not differ greatly from scheduling of any multi- task engineering effort. Therefore, generalized project scheduling tools and techniques can be applied with little modification to software projects. Program evaluation and review technique (PERT) and critical path method (CPM) are two project scheduling methods that can be applied to software development. Both techniques are driven by information already developed in earlier project planning activities.
Estimates of Effort
A decomposition of the product function.
The selection of the appropriate process model and task set.
Decomposition of tasks.
Interdependencies among tasks may be defined using a task network. Tasks, sometimes called the project Work Breakdown Structure (WBS) are defined for the product as a whole or for individual functions.
Both PERT and CPM provide quantitative tools that allow the software planner to (1) determine the critical path-the chain of tasks that determines the duration of the project; (2) establish "most likely" time estimates for individual tasks by applying statistical models; and (3) calculate "boundary times" that define a time window" for a particular task.
Boundary time calculations can be very useful in software project scheduling. Slippage in the design of one function, for example, can retard further development of other functions. It describes important boundary times that may be discerned from a PERT or CPM network: (I) the earliest time that a task can begin when preceding tasks are completed in the shortest possible time, (2) the latest time for task initiation before the minimum project completion time is delayed, (3) the earliest finish-the sum of the earliest start 56
and the task duration, (4) the latest finish- the latest start time added to task duration, and (5) the total float-the amount of surplus time or leeway allowed in scheduling tasks so that the network critical path maintained on schedule. Boundary time calculations lead to a determination of critical path and provide the manager with a quantitative method for evaluating progress as tasks are completed.
Both PERT and CPM have been implemented in a wide variety of automated tools that are available for the personal computer. Such tools are easy to use and take the scheduling methods described previously available to every software project manager.
57
58
5.1 Source code Default.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %> <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %> <%@ Register src="WebUserControl2.ascx" tagname="WebUserControl2" tagprefix="uc2" %>
Online Courier Booking Distribution & Tracking System
66
67
Aboutus.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="AboutUs.aspx.cs" Inherits="_Default" %> <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %> <%@ Register src="WebUserControl2.ascx" tagname="WebUserControl2" tagprefix="uc2" %>
Online Courier Booking Distribution & Tracking System
75
Contactus.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="ContactUs.aspx.cs" Inherits="_Default" %> <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %> <%@ Register src="WebUserControl2.ascx" tagname="WebUserControl2" tagprefix="uc2" %>
Online Courier Booking Distribution & Tracking System
Register.aspx
83
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Register.aspx.cs" Inherits="_Default" %> <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %> <%@ Register src="WebUserControl2.ascx" tagname="WebUserControl2" tagprefix="uc2" %>
Online Courier Booking Distribution & Tracking System
Administrativeregister.aspx.cs using using using using using using using using using using using using
System; System.Configuration; System.Data; System.Data.SqlClient ; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq;
public partial class _Default : System.Web.UI.Page { SqlConnection con;
96
protected void Page_Load(object sender, EventArgs e) { con = new SqlConnection(ConfigurationManager .AppSettings["mycon"]); } protected void Button1_Click(object sender, EventArgs e) { SqlCommand cmd = new SqlCommand("Insert into UserRegistration values(@Email,@Password,@ContactName,@ContactNo,@SecurityQuestion,@Se curityAnswer)", con); SqlParameter pa1 = new SqlParameter("@Email", DbType.String); pa1.Value = TextBox1.Text; cmd.Parameters.Add(pa1); SqlParameter pa2 = new SqlParameter("@Password", DbType.String); pa2.Value = TextBox8.Text; cmd.Parameters.Add(pa2); SqlParameter pa3 = new SqlParameter("@ContactName", DbType.String); pa3.Value = TextBox4.Text; cmd.Parameters.Add(pa3); SqlParameter pa4 = new SqlParameter("@ContactNo", DbType.String); pa4.Value = TextBox5.Text; cmd.Parameters.Add(pa4); SqlParameter pa5 = new SqlParameter("@SecurityQuestion", DbType.String); pa5.Value = TextBox6.Text; cmd.Parameters.Add(pa5); SqlParameter pa6 = new SqlParameter("@SecurityAnswer", DbType.String); pa6.Value = TextBox7.Text; cmd.Parameters.Add(pa6); con.Open(); try { cmd.ExecuteNonQuery(); con.Close(); Label1.Text = "You are successfully registered!"; TextBox1.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = ""; TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; } catch (Exception ex) { Response.Write(ex.Message); } } }
97
Adminlogin.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="AdminLogin.aspx.cs" Inherits="_Default" %> <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %> <%@ Register src="WebUserControl2.ascx" tagname="WebUserControl2" tagprefix="uc2" %>
Online Courier Booking Distribution & Tracking System
110
Adminwelcome.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="AdminWelcome.aspx.cs" Inherits="_Default" %> <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %> <%@ Register src="WebUserControl2.ascx" tagname="WebUserControl2" tagprefix="uc2" %>
Online Courier Booking Distribution & Tracking System 
