e-Post Office

1. Purpose:
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. In order to use the load writing procedure, the customer registers itself in the e-PostOffice and receives a login for its purchases name.

2. Technologies used:

This project is a web application that is developed in JavaScript having oracle as back end.

1. Database Design(Oracle) 2. Input Design (JSP) 3. Coding(JavaScript)

3.

Hardware Interface: Client Side:

Internet Explorer Processor RAM : : : 6.0 and above Pentium IV 2.0 and above. 512 MB

Server Side:
Processor RAM Disk space : : : 4GB Pentium IV 2.0 and above. 1 GB

4.

Software Interface:

Client Side: JAVA Framework, Web Browser, Windows XP/2000/Vista Web Server: JAVA Framework, Windows XP/2000/Vista Data Base Server: ORACLE

5.

Constraints:
User interface is only in English i.e. no other language option is

available. User can login only with his assigned username and password i.e. no guest facility is available.

Limited to HTTP/HTTPS.

Feasibility Study:

A feasibility study is defined as an evaluation or analysis of the potential impact of a proposed project or program. A feasibility study is conducted to assist decision-makers in determining whether or not to implement a particular project or program. The feasibility study is based on extensive research on both the current practices and the proposed project/program. The feasibility study will contain extensive data related to financial and operational impact and will include advantages and disadvantages of both the current situation and the proposed plan. The feasibility study is conducted to assist the decision-makers in making the decision that will be in the best interest of the e-post office system. Feasibility study should be performed on the basis of various criteria and parameters. The various feasibility studies are

Economic Feasibility Operational Feasibility Technical Feasibility

Economic Feasibility:
An economic feasibility test focuses on returns and costs of a proposed plan in both the short and long-term. An economic feasibility study (EFS) should consider investment and operating costs, the time value of money, risk and uncertainty, quality of available data, and the sensitivity of assumptions. An economic feasibility study should demonstrate the net benefit of the proposed course of action in the context of direct and indirect benefits and costs to the organization and to the general public as a whole. This product is highly economically feasible for the environments (Linux), the front end (PHP), the back end (Postgres), for the Open source Software
4

which we can easily download without economic effort. This product is designed in such a way that reduces the economic expenses when compared to the manual process.

Operational Feasibility:
It refers to the feasibility of the product to be operational. Some products may work efficiently at design phase and implementation phase but may fail in the real time environment. It includes the study of additional human resource required and their technical expertise. Our product is highly operational and feasible because of its user

friendliness, graphical user Interface and it is developed in such a way, it makes even the novices feel comfortable in using it

Technical Feasibility:
It refers to whether the software that is available in the market fully supports the present application. It studies the pros and cons of using particular software for the development and its feasibility. It also studies the additional training needed to be given to the people to make the application work. Our product is highly technically feasible for it is developed by taking into account all the possible future enhancements.

Specification Report System Interface

Application would be a self-contained system. It will not access data of any other application nor will other application have access to its data.

User Interface
Application will be accessed through a Browser Interface. The interface would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to access any part of the application without logging on to the system.

Hardware Interface For Server

Intel Pentium III or above with 512 MB RAM 4 GB hard disk Network Interface

For Client
PC With 256 MB RAM Network Interface

Software Interface For Server

Windows 2000 Enterprise Edition WAS Server DB2 Server

For Client
Windows 95/98/2000/NT Microsoft Internet Explorer 6 & above

Communication Interface
The system should be accessed over LAN or WAN. For Clients to access application server the network should be running TCP/IP protocol.

Operations
Client Side Interactive operations using options provided in the application, Example Data Entry generation and viewing of reports.

Server Side Database backup should be taken every day. In case of data base crash, last backup should be restored.

User Characteristics The end user of the software can be divided into two categories

Administrator: Access to master forms for the purpose of data entry and generation of reports.

Operator: Access to his corresponding records and giving examination only.

Bottlenecks Identified in Existing System

The first problem is that there are loads of hard copied documents being generated. This brings us to the age-old discussion of keeping information in the form databases versus keeping the same on sheets of paper. Keeping the information in the form of hard-copied documents leads to the following problems: I. Lack of space It becomes a problem in itself to find space to keep the sheets of paper being generated as a result of the ongoing discussion. The documents being generated are too important to be ill-treated. ii. Filing poses a problem Filing the documents categorically is a time consuming and tedious exercise. iii. Filtering is not easy It becomes hard to filter relevant documents for the irrelevant ones if the count of the same crosses a certain manageable number. iv. Reviewing becomes time-consuming All the process done manually at the centers and all the records are maintained on the papers. So the maintenance of the record is very difficult in the departments and as well as its very difficult for the workers to check the record. The Existing system is paper based, time consuming, monotonous, less flexible and provides a very hectic working schedule. The chance of loss of records is high and also record searching is difficult. Maintenance of them system is also very difficult and takes lot of time.

v. Result Processing is slow due to paper work and requirement of staff.

Need for the New System

To solve these problems they required a computerized system to handle all the works. They required a web based application that will provide a working environment that will be flexible and will provide ease of work and will reduce the time for report generation and other paper works.

Aims and Objective The main purpose behind the proposed system is to provide a comprehensive computerized system, which can capture, collate and analyze the data from these wards and evaluate the impact of the program.

Constraints, Assumptions, Dependencies Constraints As this system is based on client server technology, so for normal operation minimum of 64 MB RAM will be required on all clients.

Assumptions In general it has been assumed that the user has complete knowledge of the system that means user is not a nave user. Any data entered by him/her will be valid. To make the software as user friendly as possible but at the same time keeping in minds user requirements. Server OS should be Windows NT/2000/XP. Client PC should be Windows 9X/NT/WorkStation or Windows 2000 with latest service pack.

Dependencies It depends that the one should follow the international standards for the generating the User ID & should fill the related information in the proper format.

10

Software System Attributes

Usability: The links are provided for each form. The user is facilitated to view and make entries in the forms. Validations are provided in each field to avoid inconsistent or invalid entry in the databases. Some forms consists Hyper Links, which provides further details. Reports screen contains text boxes and drop down lists, so that reports can be produced. Security: Application will allow only valid users to access the system. Access to any application resource will depend upon users designation. There are two types of users namely Administrator and Student. Security is based upon the individual user ID and Password. Maintainability: The installation and operation manual of examination management system will be provided to the user. Availability: System will be available around the clock except for the time required for the back up of data. Portability: The application is developed in ASP.NET. It would be portable to other operating system provided .NET Framework is available for the OS. As the database is made in DB2, porting the database to another database server would require some development effort.

11

Acceptance Criteria
The software should meet the functional requirement and perform the functionality effectively and efficiently. A user-friendly interface with proper menus. Data transfer should be accurate and with in a reasonable amount of time keeping in mind the network traffic. The system should not allow entry of duplicate key values. System should have the ability to generate transactional Logs to avoid any accidental loss of data. Log file should also be generated.

12

Table Definitions :

Table Definitions of Customer Registration:

Table No.: Table Name: 1 Registration

Table Description: This table contain the personal information of the customer. Seq. # Column Name 1 2 3 fname lname mailadd permadd 4 5 6 7 8 9 zipcode country pnumber email username Column Description Firstname Lastname Mailing address Permanent address Zipcode Country PhoneNumber Mail Id Username Numeric Varchar Numeric Varchar Varchar PK notnull Column PK/FK Type Varchar Varchar Varchar Varchar ? Null/ Not Null Remarks

Constraints: Primary Key:email Foreign Key:

13

Table No.: Table Name:

2 Login

Table Description: This table contain the username and passwords of registered customers and administrator Seq. # Column Name 1 2 3 username password id Column Description Username Password Id Column PK/FK Type Varchar Varcahr Varchar ? PK Null/ Not Null Remarks

14

Table Definitions of Product:

Table No.: Table Name:

Stamp1 Stamps

Table Description: This table contains information about various stamps ordered. Seq. # Column Name 1 Sname Column Description Name of the product 2 Sid Unique identifier 3 4 Price Quanty Price Total no. of stamps available Double Integer Not Null Not Null Varchar(10) Not Null Column Type Varchar(20) PK/FK Null/ ? Not Null Not Null Remarks

15

Table No.: Table Name:

Letters1 Letters

Table Description: This table contains information about various letters ordered. Seq. # Column Name 1 Lid Column Description Unique identifier 2 Lname Name of the product 3 4 Price quantity Price Total no. of letters available Double Integer Not Null Not Null Varchar Not Null Column Type Varchar PK/FK Null/ ? Not Null Not Null Remarks

16

Table No.: Table Name:

Mobilecards1 Mobile Cards

Table Description: This table contains information about various mobilecards ordered. Seq. # Column Name 1 Mid Column Description Unique identifier 2 mname Name of the product 3 4 Price quantity Price Total no. of mobile cards available Double Integer Not Null Not Null Varchar Not Null Column Type Varchar PK/FK Null/ ? Not Null Not Null Remarks

17

Table No.: Table Name:

Cartons1 Cartons

Table Description: This table contains information about various cartons ordered. Seq. # Column Name 1 carton_id Column Description Unique identifier Column Type PK/FK Null/ ? Not Null Not Null 20 digit alpha numeric number 2 carton_name Name of the product 3 4 Price quantity Price Total no. of cartons available Integer Integer Not Null Not Null Varchar(10) Not Null Remarks

Varchar(20) PK

18

Table Definitions For Services :

Table No.: Table Name: courier1 Courier

Table Description: This table contains details of couriers available . Seq. # Column Name 1 cid Column Description Unique identifier 2 Cname Name of the courier 3 Price Double Varchar Not Null Column Type Varchar PK/FK Null/ ? Not Null Not Null Remarks

19

Table No.: Table Name:

courier2 Courier1

Table Description: This table contains details of couriers ordered . Seq. # Column Name 1 2 3 Userid Column Description userid Column Type Varchar(10) Varchar(50) Double(50) PK/FK Null/ ? Not Null Not Null Not Null Remarks

fromaddress Address toaddress Destination address

Table No.: Table Name:

telegram1 Telegram

Table Description: This table contains details of telegram services . Seq. # Column Name 1 2 3 4 user_id frmadd Toad message Column Description Username Column Type Varchar Not Null Not Null PK/FK Null/ ? Not Null Remarks

From address Varchar To address Message Varchar Varchar

20

Table Definitions For Billing:

Table No.: Table Name: Bill Bill

Table Description: This table contains details of all the transactions till now . Seq. # Column Name 1 2 3 user_id product_id Qty Column Description Userid Productid Column Type Varchar(20) Varchar(20) Not Null Not Null PK/FK Null/ ? Not Null Remarks

Total quantity Integer ordered

4 5 6

Price total_price datetime

Double Double Timestamp

21

Table No.: Table Name:

Bill bill1

Table Description: This table contains billdetails of mobilecards purchased . Seq. # Column Name 1 2 3 user_id product_id Qty Column Description Userid Productid Column Type Varchar(20) Varchar(20) Not Null Not Null PK/FK Null/ ? Not Null Remarks

Total quantity Integer ordered

4 5 6

Price total_price datetime

Double Double Timestamp

22

Table No.: Table Name:

Bill Billstmp

Table Description: This table contains billdetails of stamps purchased . Seq. # Column Name 1 2 3 user_id product_id Qty Column Description Userid Productid Column Type Varchar(20) Varchar(20) Not Null Not Null PK/FK Null/ ? Not Null Remarks

Total quantity Integer ordered

4 5 6

Price total_price datetime

Double Double Timestamp

23

Table No.: Table Name:

Bill Billltr

Table Description: This table contains billdetails of letters purchased . Seq. # Column Name 1 2 3 user_id product_id Qty Column Description Userid Productid Column Type Varchar(20) Varchar(20) Not Null Not Null PK/FK Null/ ? Not Null Remarks

Total quantity Integer ordered

4 5 6

Price total_price datetime

Double Double Timestamp

24

Table No.: Table Name:

Bill Billctr

Table Description: This table contains billdetails of cartons purchased . Seq. # Column Name 1 2 3 user_id product_id Qty Column Description Userid Productid Column Type Varchar(20) Varchar(20) Not Null Not Null PK/FK Null/ ? Not Null Remarks

Total quantity Integer ordered

4 5 6

Price total_price datetime

Double Double Timestamp

25

State Transition Diagram

26

Activity Diagram

27

Class Diagram:

28

Sequence Diagram

29

Input and Output Forms

Home Page :

30

Registration Form:

31

CUSTOMER LOG:

32

UserFeedBack Form:

33

CONCLUSION

An e-Post Office System is developed by a team in an effort to provide an on line postal services for the user.

The vision of e-Post Office is a step towards the greater mission. This module ensures those flexibility and efficiency of the postal services on line.

The project is also designed as user friendly as it is easy to use the user interfaces. Sitting at home a common man can view all the services provided to him.

34

BIBLIOGRAPHY
1. www.w3school.com 2. Complete Reference 3. www.codeguru.com 4. www.devex.com

35