1

INTRODUCTION
The project Online Courier Management System delivery status and notification system is being developed for the need of company running simultaneously courier & cargo service this is specially meant for their frontline user service information. This is one of the best efforts by us to prove that how Internet can be helpful in tire service industry where inquiries are always in queue. This system however is a snap shot of the whole scenario for the booming service industry. This basically deals with the queries of user for a company simultaneously running its courier & cargo service where the users having booked some cargo or couriers or both for delivery can view the status online about where there booked courier or cargo. How much more time it will take to reach the place, and whether received it in original state. nd many other queries such as the reason of blockage, queries with the user care officers regarding handling etc. there is a user satisfaction guest book where user should put some notes about our service user complaint register. s the domain in of the system is to a bigger area so the best and convenient way is internet as this is the best way to satisfy the user queries. between the user and the company. !ith the advent of the Internet technologies wavered. "very year millions more people around are using internet interact in more ways than ever before to date the find old classmates check of medical elements and cures to react and e#press and interactive view of the news also gives live sales, H"$% &nline and ma#imum hit mostly in the service industries. This is an instance to show that how internet can be the best deal with the fast growing network of optical fiber making micro broadband and economical to access the Internet whether in the modern or Information retrieval term. The e#tract of all these whether the data access retrieval and our goal is placed in a well ordered by using it's technologies on net. !e will not loose our data whether it is user or service provider. (o comp is now helpful in many other cases too)* website can prove the best interface

+ast retrieval of information around the globe by browsing the net. "asy access by sitting home to most of the work places. "asy database access with the invaluable functions of online entertainment and jobs and placements.

Through this portal we have tried to automate the process of an instance of user care industry service a web based support for a cargo and courier to provide automates service regarding their courier ,packets and parcels- delivery status.

OBJECTIVES OF THE PROJECT

The objective of the project .&nline courier delivery status Information & notification system/ Is to deal with the queries of manger. How much more time it will take to reach the place, and whether received in original state. 0ueries among the officers regarding handling etc. user satisfaction guest book where user should put some notes about service and other suggestions. 1ser complaint registers to help us get a better feedback for our failures as a hospitable interface.

The major objectives of this project are as follows:

%roviding an interactive interface for the user query for online status of the packets booked. ,2urrent (tatus- using the net technology under the framework is necessary. Helping the user to search his specific booked packet & parcel as where it is5 !hich intermediate office, when it will move from here, reasons for delay, when it will reach the destination5 &nline updating of packet & parcel status through intermediate and end office regarding truck no, status, reloading of cargo from one truck to another truck etc. %roviding (ecured "nvironment for secured data access whatever necessary. 6etrieval of data from database using easy buttons links and interfaces in a very fast and efficient manner. &n*line updating of all type of data. 1pdating data using web based interfaces and with the help of buttons & links in an easy & convenient way. 7eveloping a viable candidate system that fulfills the following requirements +aster and accurate information retrieval. "asy registration. $ogin dependent information updating. 2orrect and consistent maintenance of data and its quick retrieval. 8inimi9ing the page download time hence less investment. .(.%.3"T with 24 .net. fter all interface has a lot to do when proper interaction and attraction

Improving the switches button and hyperlink so that the candidate could find all the queries they need at the first sight. 8aintaining the fast download of the page by using the flavors of cookies. (mooth transition and easy access to the pages not requiring much training to the end user.

The overall objective:

(ystem helps to bring the company and its user round the globe more closely to each other so that one should have the perfect services.

PROJECT CATEGORY
The software which is being developed comes under both &&%( and 67:8( category. The proposed project based on 2 (harp .3"T as a front end and (0$ (erver as a back end. !hile taking 24.3et it gives the strong support of &bject &riented %rogramming (ystem technology. &n the other hand (0$ (erver gives the database consistency, reliability and strong 67:8( supports. &bject &riented %rogramming is a programming paradigm in its own right and on the other hand, it is a set of software engineering tools which can be used to build more reliable and reusable systems. t present, &bject &riented %rogramming is emerging from research laboratories and invading the field of industrial applications. &bject &riented %rogramming is at the core of 24 .3"T. In fact, all .3"T programs are to at least some e#tent object oriented. &bject &riented %rogramming is so integral to .3"T that it is best to understand its basic principles before we begin writing even simple .3"T %rogram. ;ust about everything we do in .3"T involves objects in some way*even simple variables are base on the 2 (harp object class. nd all our code hast to appear in a class of some sort, even if we are using a module or structure, which are also types of classes now, ll object oriented programming languages provide mechanisms that help us to implement the object*oriented model. It consists following supports) bstraction! The ability to create an abstract representation of a concept in code. The technique of creating new data types that are well suited to an application to be programmed is known as data abstraction. It provides ability to create user*defined data types, for modeling a real world object, having the properties of built in data types and a set of permitted operators. "ncapsulation! "ncapsulation is all about the separation between implementation and interface. In other words, when you encapsulate and object, you make its code and data internal and no longer accessible to the outside e#cept through a well* defined interface. This is also called data hiding. #olymorphism! This is all about creating procedure that can operate on object of different types. 2 (harp .3"T handles polymorphism with both late binding and multiple interfaces. $nheritance! Inheritance allows us to derive new classes from other classes. The idea here is that if we were to create, for e#ample, a class for a specific c sharp form and then derive a new type of form from that class, thee derived class will inherit all the base class's functionality, even before we start adding code or customi9ing the new form.

S#%&"T
(%.3"T is a programming framework built on the common language runtime that can be used on a server to build powerful !eb applications. (%.3"T offers several important advantages over previous !eb development models)

"nhance' #erformance:

(%.3"T is compiled common language runtime code running on the server. 1nlike its interpreted predecessors, (%.3"T can take advantage of early binding, just*in*time compilation, native optimi9ation, and caching services right out of the bo#. This amounts to dramatically better performance before you ever write a line of code.

(orl'!Class Tool Support: The (%.3"T framework is complemented by a

rich toolbo# and designer in the <isual (tudio integrated development environment. !=(I!=> editing, drag*and*drop server controls, and automatic deployment are just a few of the features this powerful tool provides. #ower an' )le*ibility: :ecause (%.3"T is based on the common language runtime, the power and fle#ibility of that entire platform is available to !eb application developers. The .3"T +ramework class library, 8essaging, and 7ata ccess solutions are all seamlessly accessible from the !eb. (%.3"T is also language*independent, so you can choose the language that best applies to your application or partition your application across many languages. +urther, common language runtime interoperability guarantees that your e#isting investment in 2&8* based development is preserved when migrating to (%.3"T. Simplicity: (%.3"T makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. +or e#ample, the (%.3"T page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, <isual :asic * like forms processing model. dditionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection. Manageability: (%.3"T employs a te#t*based, hierarchical configuration system, which simplifies applying settings to your server environment and !eb applications. :ecause configuration information is stored as plain te#t, new settings may be applied without the aid of local administration tools. This ?9ero local administration? philosophy e#tends to deploying (%.3"T +ramework applications as well. n (%.3"T +ramework application is deployed to a server simply by copying the necessary files to the server. 3o server restart is required, even to deploy or replace running compiled code. Scalability an' vailability: (%.3"T has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. +urther, processes are closely monitored and managed by the (%.3"T runtime, so that if one misbehaves ,leaks, deadlocks-, a new process can be created in its place, which helps keep your application constantly available to handle requests. Customi+ability an' "*tensibility: (%.3"T delivers a well*factored architecture that allows developers to ?plug*in? their code at the appropriate level. In fact, it is possible to e#tend or replace any subcomponent of the (%.3"T runtime

with your own custom*written component. Implementing custom authentication or state services has never been easier. Security: !ith built in !indows authentication and per*application configuration, you can be assured that your applications are secure.

C,
24 is 8icrosoft@s new programming language for the .3"T platform. It combines some of the best features of modern programming languages such as ;ava, 2AA or <isual :asic. 24 is an object*oriented language with single inheritance but multiple interfaces per class. It supports component*based programming by properties ,smart fields-, events and delegates ,enhanced function pointers-. 24 is fully interoperable with other .3"T languages such as <:.3"T, "iffel.3"T or &beron.3"T. 24 is designed to be a platform*independent language in the tradition of ;ava. It@s synta# is similar to 2 and 2AA synta#, and 24 is designed to be an object*oriented language. There are, for the most part, minor variations in synta# between 2AA and 24. 8ain has no return type, there are no semicolons after class names, there are some ,to 2AA programmersstrange decisions regarding capitali9ation * such as the capitali9ation of 8ain. &ther a few differences, the synta# is often the same. This decision is reasonable, in light of the fact that 2 synta# has been used with several other languages * notably ;ava. (imilar to ;ava, 24 does not support multiple inheritanceB instead it provides ;ava@s solution) interfaces. Interfaces implemented by a class specify certain functions that the class is guaranteed to implement. Interfaces avoid the messy dangers of multiple inheritance while maintaining the ability to let several classes implement the same set of methods. nother helpful feature of 24 is garbage collection. Therefore, it is unnecessary to include a destructor for each class unless a class handles unmanaged resourcesB if so, it@s necessary to release control those resources from within the class ,The +inali9e function is used to clear up these unmanaged resourcesB it can even be abbreviated with the same synta# as a 2AA destructor-. &f course, 24 also provides direct access to memory through 2AA style pointers, but these pointers are not garbage collected until specifically released by the programmer. 24, as part of the .3"T framework, is compiled to 8icrosoft Intermediate $anguage ,8(I$-, which is a language similar to ;ava@s byte code. 8(I$ allows 24 to be platform independent and runs using just in time compiling. Therefore programs running under .3"T gain speed with repeated use. +urthermore, because the other languages that make up the .3"T platform ,including <: and 2&:&$- compile to 8(I$, it is possible for classes to be inherited across languages. The 8(I$, like byte code, is what allows 24 to be platform independent.

C, 'vantages:

C8$ documentation generated from source code comments. ,This is coming in <:.3"T with !hidbey ,the code name for the ne#t version of <isual (tudio and .3"T-, and there are tools which will do it with e#isting <:.3"T code already.&perator overloading * again, coming to <:.3"T in !hidbey.

$anguage support for unsigned types ,you can use them from <:.3"T, but they aren@t in the language itself-. gain, support for these is coming to <:.3"T in !hidbey. The using statement, which makes unmanaged resource disposal simple. "#plicit interface implementation, where an interface which is already implemented in a base class can be reimplemented separately in a derived class. rguably this makes the class harder to understand, in the same way that member hiding normally does. 1nsafe code. This allows pointer arithmetic etc, and can improve performance in some situations. However, it is not to be used lightly, as a lot of the normal safety of 24 is lost ,as the name implies-. 3ote that unsafe code is still managed code, i.e. it is compiled to I$, ;ITted, and run within the 2$6.

S-. Server provides a suite of tools for managing all aspects of (0$ (erver development, querying, tuning, and administration. !hile designing a database, the database administrator creates database objects such as tables, columns, keys, indices, relationships, constraints, and views. To help create these objects, the (0$ (erver 8anagement (tudio provides access to visual database tools. These tools provide three mechanisms to aid in database design) the 7atabase 7esigner, the Table 7esigner, and the view designer The integrated 0uery "ditor provides a simple graphical user interface for running (0$ queries and viewing the results. The 0uery "ditor also provides a graphical representation of show plan, the steps chosen by the optimi9er for query e#ecution. (0$ (erver supports the hosting of the .3"T 2ommon $anguage 6untime ,2$6- inside the (0$ (erver process to enable database programmers to write business logic as functions, stored procedures, triggers, data types, and aggregates. The ability to run pplication code inside the database adds fle#ibility to the design of application architectures that requires business logic to e#ecute close to the data and cannot afford the cost of shipping data to middle*tier process to perform computation outside the database. pplication code is deployed inside the database by using assemblies, which are the units of packaging, deployment, and versioning of application code in .3"T. 7eployment of application code inside the database provides uniform way to administer, :ack up, and restore complete database applications.

TOOLS/PLATFORM
)or the un'ergoing project/ following tools are use': #latform Operating System )ramewor1 )ront!"n' Tool Scripting .anguage $nterface Server ;ac1!"n' Tool Technology (in'ows (in'ows 0# professional with Service #ac1 2 %&et )3 M"(O34 2%5 6isual Stu'io 7889 C,/ :TM. :TM./ 6isual Stu'io $nternet $nformation Server S-. Server 7885 S#%&"T

HARDWARE : #rocessor Memory &etwor1 'apter Mo'em Secon'ary Storage $ntel #entium 7%< =:> 75? M%;%/ @%@%3% 3 M "thernet 'apter 5?1pbs 6oice )a* @ata SamsungASeagate :ar' 'is1 B<8 =%;C

Minimum System Requirements

:ar'ware reDuirement:
%rocessor ) %entium I< D.E >HF. 8emory ) DGH 8: 6 8

Hard 7isk ) IJ >: Keyboard 8onitor

Software reDuirement:
The minimum requirement for the application to run is given below)
Front End : (%.3"T 24 Back End : (0$ (erver DJJJ Operating System : !I37&! C% with (%D, !I37&! DJJJ

SYSTEM DESIGN
(ystem design phase starts after the software requirements have been analy9ed and specified. (ystem design is the first of the three technical activities) Design, code and test required to build and verify the software. design methodology is a systematic approach to create a design by application of a set techniques and guidelines. (ome desirable properties for a software system design are as follows) 6erifiability Completeness Consistency "fficiency Traceability SimplicityAEn'erstan'ability that is

The system 'esign consi'erations are:

The design objective that include practicality, efficiency, security etc. The constraints, which include the hardware, software, budget, time, scale and the interface with all other systems. The processing techniques, which include batch processing, real time processing and on*line processing.

There are three metho'ologies for 'esigning which are as follows: B$C Top F 'own:
The top L down approach starts from the highest*level component of the hierarchy and proceeds through to lower levels. It starts by identifying the major components of the system, decomposing them into lower level components and iterating until desired level of details is achieved.

This approach of designing the system might be best if the designer has detail idea about the whole Courier Management System project to be developed. In this methodology designer start with a front or top form, often called 8 I3 % >", for the project and work branching off from there. The advantage of the top*down approach is that form can be changed to affect the look and feel of the whole project because all forms are designed according to the top form look and feel.

B$$C ;ottom!up:
bottom*up approach starts from the lowest level of component hierarchy and proceeds through progressively higher levels to top levels components. This design approach starts with designing the most basic or primitive components and proceed to higher*level components that use this lower level components. This approach is adopted when the designer hasn't a good idea about the layout of final project, but know how specific forms look and work. It might be that working from these specific forms to the top forms is the way to proceed. This is particularly true if there are, already, e#isting forms as a result of development of some other project made by some one having the same concept. If there are no forms from which the designer has to start, then he can begin by designing leave forms that accomplish specific objectives and then linking them together through intermediate forms to the top forms. The advantage of this design is that the designer is not constrained by the style of top forms in the leaf form.

B$$$C $ncrementalA$n times:

(imilar in ways to both the top*down and bottom*up approaches, the IncrementalM In time approach develops forms ?just in time? when they are needed. It may be the case that an initial top form is needed and specific leaf forms that implement particular objectives. These are created and linked together with understanding that later, intermediate forms may be needed. This works well if the client wants very quickly have a working project that will grow incrementally, rather than being developed all at once. The Courier Management System %roject has been designed by following the down approach as well as IncrementalMIn time approach. 7esign step produces a data design, an architectural design and a procedural design. In the data design phase information

domain model created during analysis phase is transformed into the data structure. In the architectural design the relationship among major structural components of the Courier Management System %roject are defined. In the procedural design major structural components transformed into a procedural description of the software.

ANALYSIS
@)@ of the #roject
t 9ero and one level the border scenario of the whole portal is considered and at second level an instance of this project is shown. "ach break*up has been numbered as per the rule of 7+7. Here we attempted to incorporate all the details of the system.

8 .evel @)@:
This is the conte#t level 7+7 of the proposed system. The whole system has been depicted in the way so that the information flow continuity should not be lost in the ne#t level. The purposed system is shown as a whole process and the inputs and outputs are shown with incoming and outgoing arrow from the system.

1st .evel @)@:

This 7+7 shows all the processes together with all the data stores ,tables-. It shows the true data flow i.e. how data is actually flowing in the system. 7ata is coming from which table and going into which table is clearly shown by this understanding the whole system. The application developer will fall back upon this 7+7 during the development phase.

8 .evel @)@

!eb %anel &ffice 6egistration

6eg. 7ata

!eb panel display

(ite 7ata 1pload

7isplay (uccessMfailure 6eg. Information

6egistration display

(taff $ogin

1ser id & pwd %rocess status search 2alculate distance &time %rocess query

(tatus (earch 7elay

&nline courier & cargo booking delivery status information & notification system
%rocess 2omplaint

$ogin (uccessMfailure 7isplay (tatus (how delay %rocess 6esponse

$ogin 7isplay

(tatus display 7elay

%rocess action

2ustomer query

6esponse display ction display

2ustomer 2omplaints

."6". 1 @%)%@
The 2ompany 7atabase 7ata upload !eb %anel 1pdating 1pdate &ffice 6eg. (taff $ogin 1ser id and pwd (tatus search Input :ooking Id %rocess (earch id 6oute 7ata %rocess 6oute 7istance & 7ate %rocess 7istance & time 7elay reasons 7elay 2ustomer query 1pdating 1pdate new query 6esponse update 1pdate reasons 7ata 6esponse Handler 6esponse 2ustomer 2omplaints 1pdating 1pdate new query 0uery 1pdate 6esponse handler 6esponse display %rocess user id & pwd 2heck &ffice status %rocess current office 2heck administor %rocess &ffice 6eg. <alid id msg. 2heck 2andidate !eb panel display

6eg. 7isplay

(tatus 7ata (tatus

7elay

6esponse ction 7isplay

"!3 @iagram

dminNid

%assword

1serNid

%assword

dministrator

1ser

2reates &fficeNid 2ontainerNid :aseNcit yNid tyNid 6outes 2ourier

:ooke d

&ffice

2ontainer

2argo

3ame

ddress

7istance &fficeN bearer 7elivery Nstatus 7estinationNc ityNid 7etailesNofNcargo 7etailsNofNc ourier

2ityNid 2ontainerNat

)low @iagram

(uggestion 2ourier :ooking 1ser $oadingMunloading 2ontainer

2ourier booking lot link

dmin

$oadingMunloading truck

&ffice 6eg. &ther 3etwork $ot 3etwork Transfer 6oute 7etail 6oute 8ap (tatus Information 2ity Truck 6oute Truck Truck 6oute D

(tate

2ountry 2ontainer $ot

(ourceM7estination

COMPLETE STRUCTURE OF THE PROGRAM

Pro ect Modu!es
The proposed website will have its main page and will be mainly divided into partially dependent and partially independent modules as* I. $ogin master D. 6egistration master O. 2ourier & cargo differentiation master E. 2ourier status notification marker G. The page design maker H. 7elivery status notification system for courier P. 2ourier booking detail master Q. The site master ,control panelR. 2ustomer query handler master IJ. The validations master II. The other network courier L handling master ID. 2argo status notification marker IO. 7elivery status notification system for cargo IE. 2argo booking detail master IG. The other network cargo* handling master These modules with their sub modules are describe below*

1% .O=$& M ST"3:
$ogin master is the specific module, which only has to deal with the updating of the database. Two types of user can login administrator and the employee. It checks for a valid candidate when the user enters his user id password and link to the correct page and link to the registration page. It is divided into following functions.

BaC ES"3 $@ C:"C4"3:

s user id rules the system for updating ,control panel-. (o his uniqueness and type of his user id know a person whether he is master or one of the employee. in different cases to validate the genuinely of the candidate. s it is to provide the viable candidate system, so the user id is being validated with password

BbCT:" .O=$& ST TES M ST"3:

This module keeps the status of who and when logged in and for which purpose and for how much time.

7% 3"=$ST3 T$O& M ST"3:

s this module is only accessible through administrator password. (o this has not much to do directly. This modules deal with the different state of registration as* a. b. c. d. 6egistration form display 2lient's does validation being handles by validation master 1nique user id checker ,checks that the user id being entered by the candidate is unique or nouto user id generator ,user id field by taking the email id of the user if it is unique or suggest by combining it will some number-.

2% COE3$"3 &@ C 3=O @$))"3"&T$ T$O& M ST"3:

This module checks the booking id as of courier and cargo, and act according with that. This module differentiates the data as well as process the credential regarding to that, this module handles to and from data from the intermediate process.

<% COE3$"3 ST TES &OT$)$C T$O& M ST"3:

This module handles the query of customer and displays the result according to that customer is asked to enter the booked id in the specified input area. &n the basis of input the detail regarding where material e#actly is shown. This module contains the following sub modules*

BaC -E"3G : &@."3:

This module handles to and from the courier and cargo differentiation master searches the data in the database, which through different conversion through numbers of tables shows the result regarding where e#actly the cargo is. The booking id is first searched into the courier booked table. "ach booking id has a unique number associated with the different offices and also with the courier. &n the basis of that booking id, matched with the lot id, and then with the medium and after that medium halted at which station. These statuses are shown.

5%

T:" # =" @"S$=& M ST"3:

This module is specially meant for auto style sheet generator by using C8$. The document object modeling basically deals with the development of a common model for display to have a better interface and look. 7T7 ,the document type declarationhelps the generated page to be validated with tile 7T7 object and file inserted into, so that tile generated should follow the rules and regulation defined in the document type declaration. (imply one is validating the page so that strict entry should be made to avoid any failure and redundancy in the database. The style sheet generation through C($ has lot to do and much work is their when you defined and generali9e an instances of the tag defined to display in a common attractive and impulsive format.

Here in some pages 2(( is being used and for some common C($ will be used for the generation of fully formatted and fully validated web pages.

?%

@".$6"3G ST TES &OT$)$C T$O& SGST"M )O3 COE3$"3:

This module deals with the delivery status whether the following courier has been delivered to the destination or not, how much time it will take to reach the destination. It has following sub modules*

BaC

@$ST &C" C .CE. TO3:

It takes the data from the route table that specifies distance between the current city ,the city through which tile courier is passing and the destination-.

BbC

T$M" C .CE. TO3:

n average time is calculated on the basis of the average time taken to reach the two adjoining city subsequently to the destination.

BcC

@"."6"3"@ ST TES:
It checks the current status if the current status of the courier gives the destination address and after taking the received detail. It display whether the courier is on its way or delivered successfully.

H%

T:" S$T" M ST"3:

The site maintenance master is the main and the biggest module handling the updating of all type of information regarding the courier & cargo system. It can only be accessed through user id and password, as it deals with the work related the date necessary to keep the site working. menu is displayed asking for to update the instance of the site a user wants, as the si9e of the module directly depend upon the table design and updating. through a site master account and the employee account. It includes the following sub modules* special control panel is design to use for uploading of data in different table. This is done

BaC COE&T3G S"36$C" "&T3G:

iiiiiiiv-

2ountry in which true courier & cargo service is &ther network collaboration for cargo &ther network collaboration for courier &ther network services country

available,only administrator-

BbC

ST T" "&T3G:
The state in which the courier service is available ,only administrator-

BcC C$TG "&T3G:

The city in which the service is available ,only administrator-.

B'CO))$C" "&T3G:
&ffices, their address and other credentials ,only administrator-.

BeC 3OET" M ST"3:

7istance and time taken between each city, shortest route between two destinations ,only administrator- and other entries to keep the site working.

9%

;OO4$&= @"T $.S )O3 COE3$"3 :

2ourier booked, source office, destination office, lot, container, truck details, date dispatched etc regarding booking of new courier with a unique id. It includes the following sub modules*

BaC

COE3$"3 ST TES :
This specially deals with the updating at intermediate office about the truck number that passed through office.

BbC.O @$&= E&.O @$&= @"T $." :

This deals with the loading and unloading courier from one truck to another truck or one container to another container and other entries to keep the site working.

I%

;OO4$&= @"T $.S )O3 C 3=O :

2argo booked, source office, destination office, container, truck detail, date dispatched etc regarding booking of new courier with a unique id. It includes the following sub modules*

BaC C 3=O ST TES :

This specially deals with the updating at intermediate office about the truck number that passed through office.

BbC

.O @$&= E&.O @$&= @"T $." :

This deals with the loading and unloading cargo from one truck to another truck or one container to another container and other entries to keep the site working.

18% CESTOM"3 -E"3G : &@."3 M ST"3 :

This module specially deals with the handling of query of the customer. This module has following sub modules L

BaC

CESTOM"3 -E"3G : &@.$&= :

This module generates a input form through which customer can directly interact with tile intermediate office where there courier & cargo isS Through different function and tables.

BbC

CESTOM"3 COM#. $&T 3"=$ST"3 :

2ustomer can directly enter the complaint regarding end office, and the response is sending through the head office. This complaint is only viewable through administrator account.

11% T:" 6 .$@ T$O& M ST"3 :

This basically deals with the validation of different entries done during form building process. This module specially uses the client side validation scripting from java script and server side scripting from vb.net to make the system robust reliable and error free. This module as specially integrated with the different page and forms checks all the discrepancies such as incorrect email, date of birth, address, etc to

finally deal with the any wrong entries being done by the user . it validates as well Is suggests for correct input. This module has the different sub modules depending upon the above modules find forms.

i% C 3=O E#@ T" 6 .$@ T$O& M ST"3 : 7eal with the validation regarding the updating of product. ii% 3"=$ST3 T$O& 6 .$@ T$O& M ST"3 : 7eals with the discrepancies in registration process etc. iii% COE3$"3 E#@ T" 6 .$@ T$O& M ST"3 : 7eals with the validation regarding the updating of courier and its status.

17% T:" OT:"3 &"T(O34 COE3$"3 : &@.$&= M ST"3 :

This module deals specifically with the handling of packet to other network for future delivery and their status mapping with their server to our server. This part of module simply tries to correct to their server automatically to retrieve the details with the no being mapped with the original booking id, this helps the customer to remember only one booking id but track the status of the courier while it travels through other network to.

12% C 3=O ST TES &OT$)$C T$O& M 34"3 :

This module handles the query of customer and display the result according to that customer is asked to enter the booked id in the specified input area. &n the basis of input the detail regarding where there material e#actly is shown. This modules contains the following sub modules*

BaC -E"3G : &@."3 :

This module handles the query of the customer searches the data in the database, through number of tables shows the result regarding where e#actly the cargo is.

The booking id is first searched in to the cargo booked table. "ach booking id has unique number associated with the different offices and also with the cargo. &n the basis that booking id, matched with the container, and then with the truck, and after that true halted at which station. The status is shown.

1<% @".$6"3G ST TES &OT$)$C T$O& SGST"M )O3 C 3=O:

This system deals with the delivery status whether the following cargo has been delivered to the destination or not or how much time it will take to reach the destination. It has following sub modules*

BaC @$ST &C" C .CE. TO3:

It takes the data from the route table that specifies distance between the places then calculates the distance between the current cargo ,the city through which the cargo is passing and the destination-.

BbC

T$M" C .CE. TO3:

n average time is calculated on the basis of the average time taken to reach the two adjoining city subsequently to the destination average truck halt time and a time in day returned.

BcC

@"."6"3"@ ST TES:
It checks the current status if the current status of the cargo gives the destination address and after taking the received detail. It displays whether the cargo is delivered successfully or not.

15% T:" OT:"3 &"T(O34 C 3=O : &@.$&= M ST"3 :

This modules deal specifically with the handling of cargo or container to other network for future delivery and their status mapping with their server to our server. This part of module simply tries to connect to their server automatically to retrieve the details with the number being mapped with the original booking id. This helps the customer to remember only one booking id, but track the status of the courier while it travels through other network to.

DATA STRUCTURE
The normali9ed form of the table with their structure is describe as under*

Table 1: .ogin
)iel' &ame 1serNid &fficeNid %assword @ata Type <archar Integer <archar @escription 1serid,unique&fficeid %assword 4ey Constraint %rimary key +oreign Key *

Table 7: 'ministration login

)iel' &ame 1serNid %assword %assword @ata Type <archar <archar <archar @escription 1serid,unique%assword %assword 4ey Constraint %rimary key * *

Table 2: Office registration

)iel' &ame &fficeNid 3ame ddressI ddressD %honeI %honeD 2ell e*mail 2ountryNid (tateNid 2ityNid 6egistration date Handles @ata Type Integer <archar <archar <archar <archar <archar <archar <archar Integer Integer 3umeric 7ate <archar @escription &ffice id 2andidate name %ermanent address Temporary address %hone,residence%hone,office8obile e*mail id country to which belong (tate * 6egistration date 2ourier, cargo 4ey Constraint %rimary key * * * * * * * +oreign key +oreign key +oreign key * *

Table <: Courier boo1e' 'etail

)iel' &ame :ookedNbyNuserNid :ookingNno :ookedNitem :ookedNweight HandlingNdescription $otNid :ookingNdate 6eceiveNdate 6eceiveNat !hether @ata Type <archar 3varchar <archar Integer <archar Integer 7ate 7ate <archar <archar @escription &ffice :ooking no. unique Item name !eight bout handling the cargo 2ontainer id 6eceiving date 1serid of receiving office 2ourierMcargo 4ey Constraint +oreign key %rimary key * * * +oreign key * * +oreign key *

Table 5: .ot Status

)iel' &ame &fficeNid $otNid $otNstatus 6easonNofNstay !henNmoved @ata Type Integer 3umeric <archar <archar <archar @escription :ooking office id :ooking no. unique &fficeNif of office Through which passing * 4ey Constraint +oreign key %rimary key * * *

Table ? .ot 'etail

)iel' &ame $otNid :ookingNid &fficeNid 7ispatchNdate @ata Type 3umeric 3umeric <archar 7ate @escription 2ontainerNid :ooking id booked for special lot &ffice lot made 7ate of dispatch 4ey Constraint +oreign key +oreign key * *

Table H: 3oute 'etail

)iel' &ame :aseNcityNid 7istintionNcityNid 2urrentNdeliveryNstatus verageNspeed 7istance @ata Type 3umeric 3umeric Integer Integer 3umeric @escription * * Time take (peed 7istance in k.m. 4ey Constraint +oreign key +oreign key * * *

Table 9: 3oute Map

)iel' &ame :aseNcityNid 7istintionNcityNid &riginalN via 2urrentlyNvia 6easonNrouteNchange @ata Type 3umeric 3umeric Integer Integer <archar @escription 2ityNid 2ityNid 2ities 2ities reason 4ey Constraint +oreign key +oreign key * * *

Table I: .oa'ing Enloa'ing #ac1et

)iel' &ame &fficeNid :ookingNidNunloaded @ata Type 3umeric 3umeric @escription :ooking id of lot unloaded 3ew lot made with that booked packet 4ey Constraint +oreign key +oreign key

$otidNloaded $otidNunloaded &fficeNid 6eason

3umeric 3umeric 3umeric <archar

+rom unloaded * * 1nloading reason

+oreign key +oreign key +oreign key *

Table 18: .ogin Status Master

)iel' &ame $oginNid $oginNtime $ogoutNtime @ata Type <archar 7ateMtime 7ateMtime @escription 1ser id $ogin time $ogout time 4ey Constraint +oreign key +oreign key %rimary key

Table 11: Country Services

)iel' &ame 2ountryNid country @ata Type 3umeric <archar @escription 2ountryNid 2ountry 4ey Constraint +oreign key *

Table 17: State Services

)iel' &ame (tateNid 2ountryNid (tate @ata Type 3umeric 3umeric <archar @escription TT2ountry id * * 4ey Constraint +oreign key * *

Table 12: City Services

)iel' &ame (tateNid 2ountryNid 2ityNid city @ata Type 3umeric 3umeric Integer <archar @escription 2ountry id * * * 4ey Constraint +oreign key +oreign key %rimary key *

Table 1<: .ot .oa'ing Enloa'ing

)iel' &ame $otNid 7estroyedNat 3ewNlotNid reason @ata Type Integer Integer Integer <archar @escription * &ffice Track load * 4ey Constraint +oreign key * +oreign key *

Table 15: Country Services

)iel' &ame :ookingNno @ata Type 3varchar @escription :ooking 3umber 4ey Constraint +oreign key

2ustomerNname ddress 2omplaintNagainst 2omplaintNregarding 2omplaintNdetail 7ate ctionNtaken :y gainst ctionNdetails 7ateNaction

<archar <archar <archar <archar <archar 7atetime <archar <archar <archar <archar 7atetime

* * * * * * * dministrator id &ffice id * *

* * * * * * * +oreign key +oreign key * *

Table 1?: Suggestion 3egister

)iel' &ame :ookingNid (uggestion ToNofficeNid 6esponce 7ateNsuggest 7ateNresponded @ata Type Integer <archar Integer <archar 7atetime 7atetime @escription :ooking id (uggestion * (uggestion * * 4ey Constraint +oreign key * +oreign key * * *

Table 1H: Other &etwor1 Collaboration

)iel' &ame 3etworkNid 2ompanyNname 2ompanyNoffice !ebsite 2ustomerNcareNno !hetherNcollaborated 7ateNcollaboration !hetherNhandles @ata Type Integer <archar Integer <archar 7atetime 7atetime 7ate <archar @escription :ooking id (uggestion * (uggestion * * * 2ourierMcargo 4ey Constraint +oreign key * +oreign key * * * * *

Table 19: Other &etwor1 Courier Transfer

)iel' &ame 3etworkNid &fficeNid $otNid 3ewNnetworkNlotNid 7ateNtransfer &fficeNidNreceived 7ateNreceived @ata Type Integer 3umeric 3umeric <archar 7ate 3umeric 7ate @escription :oking id (uggestion $ot 2ourier company transfer 7ate booked * * 4ey Constraint +oreign key * * * * * *

Table 1I Truc1 @etails

)iel' &ame &fficeNid TruckNid TruckNno 7rivers TruckNstatus 6easonNofNstay !henNmoved @ata Type Integer 3umeric <archar <archar <archar <archar 7atetime @escription 1ser id of office * * * &ffice id of office at which staying * * 4ey Constraint +oreign key %rimary key * * * * *

Table 78: Container

)iel' &ame 2ontainerNid &fficeNbearer 2ontainerNat @ata Type 3umeric Integer Integer @escription 2ontainer id &ffince id &ffice id 4ey Constraint %rimary key +oreign key +oreign key

Table 71: Truc1 Container Mapping

)iel' &ame TruckNid 2ontainerNid :ookingNdate :ookedNbaseNoffice !hetherNunloadNtruck 1nloadingNdate !hetherNunloadedNcontaine r 2date @ata Type 3umeric 3umeric 7ate <archar 2har 7ate 2har 7ate @escription * * * &ffice id =esM3o * =esM3o 1nloaded container date 4ey Constraint +oreign key +oreign key * +oreign key * * * *

Table 77: .oa'ing Enloa'ing Container

)iel' &ame &fficeNid 2ontainerNidNunloaded 2ontainerNidNloaded 6eason @ata Type <archar Integer Integer <archar @escription * 2ontainer id from which cargo unloaded 2ontainer id from which cargo loaded 1nloading reason 4ey Constraint +oreign key +oreign key * *

Table 72: Truc1 .oa'ing Enloa'ing

)iel' &ame TruckNid 1nloadedNat $oadedNto reason @ata Type Integer Integer Integer varchar @escription * &ffice Truck loaded * 4ey Constraint +oreign key * +oreign key *

Table 7<: Other &etwor1 Cargo Transfer

)iel' &ame 3etworkNid &fficeNid $otNid 3etNnetworkNlotNid 7ateNtransfer &fficeNidNreceived 7ateNreceived @ata Type Integer 3umeric 3umeric <archar 7ate 3umeric 7ate @escription :ookingid (uggestion $ot 2ourier company Transferred 7ate booked * * 4ey Constraint +oreign key * * * * * *

PROCESS LOGIC
Online Courier J Cargo System #rocesses in the following manner:
This website contains information about user function such as :ooking the couriers and cargo, $oading the collection of lots in the selected truck or container ,in case of cargo-, $oading the container,s- in the truck ,in case of cargo- etc. as well as administrator function such as &ffice 6egistration, 2reating 1ser, <iewing suggestions and complaints of user, dding new 2ities, (tate and 2ountries, <iew the (tatus of 2ontainer and Truck etc. The project Online Courier J Cargo System delivery status and notification system is being developed for the need of company running simultaneously courier & cargo service this is specially meant for their frontline customer service information. This is one of the best efforts by us to prove that how Internet can be helpful in tire service industry.

REPORTS
Eser:
(tatus of 2ourier & 2argo. (tatus of $ot. (tatus of Trucks.

'ministrator:
(earch the status of 2ourier & 2argo. <iew complaints and suggestions of 1ser and &ffices.

SECURITY
#hysical Security
The 7ivisionalM2entral (ecurity of the system Their responsibilities shall include 8aintenance of security of 7atabase (ervers by keeping it locked and prohibiting entry of any unauthori9ed person to prevent thefts and other untoward incidents ccess to the database server shall be protected by password and only the (ystem dministrator shall be aware of the same. dministrator shall be responsible for the physical security

8aintenance of multiple power supply connections for uninterrupted power supply.

@atabase Security
S-. Server uthentication) In this case, (0$ (erver requires that a user specifies a name and password at the time when connection is attempted. The login name and one*way hash of the password need to match one of entries in the sys login table for the login attempt to be successful. (in'ows uthentication: !ith built in !indows authentication and per* application configuration, you can be assured that your applications are secure.

SCREENSHOTS
:ome #age

'ministrator .ogin )orm

'ministrator #age fter .ogin

Create &ew Office

Create Container

Create Truc1

Create &etwor1

Create 3oute )orm

Create 3oute Map )orm

Create City )orm

Search ;oo1ing Status )orm

Eser .ogin )orm

Eser #age fter .ogin

;oo1ing )orm

FUTURE SCOPE
It is highly likely that the scope will change as the web application moves forward the web process model should be incremental. This allows development team to free9e the scope for one increment so that an operation web application of the preceding increment but once the second increment commence, scope is again fro9en temporarily. This approach enables the web application team to work with having to accommodate continual stream of change be still recogni9ed. The continuous evolutions characteristics of most web application. :eside that the following basic quality in the software always safeguards the future scope of the software.

LIMITATIONS OF THE PROJECT

Though this project is very useful an' has several a'vantages over a manual system% Ese of this no 'oubt will result in faster processing an' a better service but has some limitations also% These limitations inclu'e
!e do not have online transactions. This application can run on the !eb server and (0$ server. "nd user cannot directly interact with the dynamic performance of this project.

BIBLIOGRAPHY
!e referred some books which had provided us with much of guidance to develop the code for the website. There are a few good books and websites that we referred to develop (%, 2((, ;ava(cript and HT8$ codes. part from codes these books and websites had provides us with few good techniques and methodologies to develop the website. There are a list of few books and websites that we referred are) ;OO4S: 24 %rofessional :y (ro* #ublication (%.3et :y (ro* #ublication (0$ ("6<"6 DJJG $n Techme'ia/ 71 @ays

S$T"S )O3 3")"3"&C" http)MMwww.google.com http)MMwww.aspcode.net http)MMmsdnD.microsoft.comMen*usMasp.netMdefault.asp#