Dispatch Tracking Software for Sophisticated Courier System

Title of the Project: Dispatch Tracking Software for Sophisticated Courier System Project Architecture : N-Tier SDLC Methodologies: Waterfall/Spiral Model Course: Roll No: Name of the Student: Technology used: Java Internal Guide: E-Mail ID: Mobile No (Student): Abstract of the Project: Introduction:
Dispatch Tracking Software for Sophisticated Courier System will be the best ecommerce solution for courier business. If you need to setup a new courier business then this system is your quickest solution. Very easy to setup and manage powerful administration.

Functional Requirements
Following is the List of Functionalities of the System. Functional requirements means interface between the user and the hardware. In this project, we discuss the functionality of the each module. The functional Requirements are It It It It It It should should should should should should allow allow allow allow allow allow administrator to manage the different users. the administrator to manage different Branches Info. the administrator to add a new request for the branch. the dealer to place a new request for the branch. the dealer to add employees in that particular branch. the dealer to add consignments details.

Non-Functional Requirements:

The system should be web-based system. Each user should have a user account. The system should ask the username and password to users. It doesnt permit to unregistered user to access for Integrated Claim Settlement Services. The system should have Role based System functions access. Approval Process has to be defined. The system should have Modular customization components so that they can be reused across the implementation. These are the mainly following: 24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension.

Existing System:
Current system is a manual one where in consignments, deliveries, dispatches, receives etc details are maintained in books. Whenever a consignment is booked or delivered or dispatched or received by a dealer, the details are entered into various books. Monthly or annual reports and returns are prepared based on the data from these books. Disadvantages: The following are the disadvantages of current system It is not secure to maintain important information manually More manual hours need to generate required reports It is tedious to manage historical data which needs much space to keep all the past years applications, books etc. User need to wait more time to get his application status. Data is not in sync in case of manual system. Co-ordination between various branches is very difficult

Proposed System:
Proposed system is a software application which avoids more manual hours that need to spend in record keeping and generating reports. This application keeps the data in a centralized way which is available to all the users simultaneously. It is very easy to manage historical data in database. No specific training is required for the employees to use this application. They can easily use the tool that decreases manual hours spending for normal things and hence increases the performance. Advantages: The following are the advantages of proposed system Easy to track the status of applications at any level at any point of time Can generate required reports easily Easy to manage historical data in a secure manner Centralized database helps in avoiding conflicts Easy to use GUI that does not requires specific training.

Number of Modules:
The System after careful analysis has been identified to present with the following modules. 1. Admin Module: This module maintains deals with functionality like accepting requests for new branches and adding new branches etc. 2. USERS MODULE: This module deals with major and crucial part which includes information of branches, deliveries, dispatches and consignments. This module provides interface to add the branches details and dealer ship requests. 3. DEALERS MODULE: This module deals with major and crucial part that includes the details of available branches and dealers. This module deals with the functionalities like placing a request for dealer ship, recruiting employs, take care about the consignment booking, delivery dispatch and receivers particulars. 4. CONSIGNMENT MODULE: This module deals with major and crucial part that includes tracking and viewing the details of all the consignments. This module deals with the functionalities like storing material particulars including cost category and to find the status of the booked consignment. 5. EMPLOYEE MODULE: This module deals with the functionalities recruiting and terminating employs when a new branch is started. This module contains the details of all the employees those who are recruited by the dealers.

Users of the System:

This system should be designed to support the following users: Admin Dealer User

Environment:
Servers: Apache Tomcat. Operating System Server: - Microsoft Windows XP/2000 or Higher Data Base Server: My SQL 5.0. Clients: Microsoft Internet Explorer (Client Browser) Development Tools: Net Beans 6.8. Documentation Tools: MS Office 2007/2010 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: HTML,JAVASCRIPT

 Code Behind: JSE,JEE Requirements: Hardware Requirements:

Number 1 Description PC With Minimum 2.6 GB Hard-Disk And 1GB RAM

Software Requirements:
Number 1 2. 4. Description Windows NT/ XP My SQL 5.0 MS-Internet Explorer

Milestones:
No. Milestone Name Requirements Specification Milestone Description Remarks

Technology Familiarizatio n

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Database Creation

A database of at least 10 entries of users with at least 1 should application admin.

High-level and Detailed Design Development of Front End Functionalitie s.

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. The scenarios should map to the requirement specification

During this milestone period, it would be a good idea for the team to start working on a testplan for the entire system. This test-plan can be updated as and when new scenarios come to

mind. 6 Integrating the Front-end with the Database The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review.

Integration Testing

Final Review

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start of the project: Study and be comfortable with technologies such as: HTML, JAVASRIPT, JEE, JSE,
CSS, JSP. Gather some knowledge of product hierarchies and maintenance before starting the Design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.