Projects

Development of an e-Post Office System

 

Title of the Project

 

Development of an e-Post Office System

 

Abstract of the project

 

The e-Post Office is the shopping portal of the world renowned postal service on the internet and an additional distribution channel. It sells Stamps, PostCards, Packets, Cartons and has services like courier, registering for electricity vendors, selling mobile cards, etc.  Under this website many products and services can be ordered , that are also available  in a "normal" branch.  The product prices are identical with the prices of their normal branches. 

 

The e-Post Office is expanded permanently through new products and services in order to offer a product portfolio corresponding to the market.  Private customer and business customers can order the selected products of the postal service online quickly and comfortably.  Besides this,  the e-Services offer new flexibility through e-Packet, the PICKUP order for packages over the internet as well as the online forwarding order and storage order.  For the case of the absence or the move, one can let delegate here the after shipment of the postal service at another address or store the letter shipments.  The customers can register themselves and can be served individually.

 

Target groups of customer of the e-PostOffice are predominantly little and middle-class business(SMEs).  The customers can have a payment alternative through credit card.  In order to use the load writing procedure, the customer registers itself in the e-PostOffice and receives a login for its purchases name.

 

You have to develop this web site , which captures the above functionality. It is an internet application

 

Keywords

 

Generic Keywords

 

Databases, Middleware, Programming

 

Specific Technology Keywords

 

Oracle Stored Procedures, ASP/JSP, HTML, JavaScript/VBScript, Struts

 

Project Type keywords

 

Analysis, Design, Implementation, Testing, Graphical User Interface

 

Functional components of the project

 

Following is a list of functionality of the system. More functionality that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed.

 

Users of the system : Customer is the user of the system.An adminstrator of the website is the super user.

 

When the user types in the URL of the website, a Welcome page is shown which has a menu on the left hand side, a banner at the top and any related links to other sites. This site contains an online catalog for the user. User has to login to Welcome Page before ordering anything. Login functionality should  check the authenticity of the user from the database.

 

Menu should contain following screens

·        Registration Screen

If the user is not registerd, then registration screen should be available

 

·        Stamps and Bulk Stamps Order

This screen will show all the types of Stamps with their values and minimum quantity that should be ordered. If possible, provide the image of each of the stamp types. On selecting any one of the Stamp type, user is shown the columns for the quantity to be entered.

After entering the quantity, price is automatically set by the system based on the product price data. On adding to catalog, kindly check the inventory and take appropriate action.

 

·        Letter Order

This Screen will show  different types of letter which can be ordered online. Provide an image for each type of letter. On selecting any one of the Letter type, user is shown the columns for the quantity to be entered.. After entering the quantity, price is automatically set by the system based on the product price data.

On adding to catalog, kindly check the inventory and take appropriate action.

 

·        Catalog Information

This screen contains the information about the orders for the user.

It gives total  value of the order together with individual items ordered.

On ordering, the validation about users credit is made. Credit information can be kept in the database for the sake of simplicity. Once the order is accepted, inventory is updated and shipment entry is made in the database. Once the shipment is done, shipment status is updated.

 

·        Terms and Conditions – A Breif text on the website explaining terms and conditions and printable copy of it.

 

·        Contact Information – Contact information regarding the office addresses with phones and faxes are provided on this screen

 

In addition to this , we can have a help link on each of the screens.

 

Steps to start-off the project

 

Microsoft platform: The system is developed using Active Server Pages as the  front end and Oracle/SQL Server/DB2 as the back end.

Or

Java Platform: The system is developed using Java Server Pages/ Servlets as the  front end and Oracle/SQL Server/DB2 as the back end.

 

The following steps will be helpful to start off the project

1.      Get a firm grasp on the above technology.

2.      Decide on the number of users and their profile, number of products, type of products,  business rules.

3.      Make a super user who will be able to assign users to groups and will be able to assign rights to a group.

4.      Help should be very user friendly.

5.      UI should include good images and have a constant look and feel throughout the application.

 

 

Requirements

                       

Hardware requirements

 

Number

Description

Alternatives (If available)

1

PC with 5 GB hard-disk and 512 MB RAM

Not-Applicable

 

 

 

 

 

Software requirements

 

 

Number

Description

Alternatives (If available)

1

Windows 95/98/XP with MS-office

Not Applicable

2

MS-SQL server/Oracle

MS-Access

3

Linux

Not Applicable

4

IIS for MS

Tomcat for java

 

 

Manpower requirements

 

2 to 3 students can complete this in 4 – 6 months if they work fulltime on it.

 

Milestones and Timelines

 

Number

Milestone Name

Milestone Description

 

 

Timeline

 

Week no. 

from the start

of the project

Remarks

 

 

1

Requirements Specification

Complete specification of the system (with appropriate assumptions) that constitutes this milestone. A document detailing the same should be written and a presentation on that be made.

2-3

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

2

Technology familiarization

Understanding of the technology needed to implement the project.

4-5

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.

3

Database creation

A database of atleast 20 different products and 100 different users should be created.

5-7

It is important to finalize on the database at this stage itself so that development and testing  can proceed with the actual database itself.

4

High-level and Detailed  Design

Listing down all possible scenarios  and then coming up with flow-charts or pseudocode to handle the scenario.

7-9

The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).

5

Implementation of the front-end of the system

Implementation of the main screen giving the login facility, screen that follows the login giving various options, screens for each of the options.

10-12

During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan 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 like. In short, the system should be ready for integration testing.

12-13

 

7

Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).

14-15

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

8

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

16-18

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)

 

Guidelines and References

 

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnasp/html/asptutorial.asp (ASP tutorial)

 

http://www.functionx.com/sqlserver/ (SQL-server tutorial)



Tags :
0
Your rating: None