ABSTRACT

e-PostOffice
In the recent past, Internet and e-mail have revolutionized the world of communications. In its endeavor to make the benefits of e-mail available to everyone and to bridge the digital divide, Department of Posts has introduced ePOST service. Through ePOST, customers can send their messages to any address in India with a combination of electronic transmission and physical delivery through a network of more than 1,55,000 Post Offices. ePOST sends messages as a soft copy through internet and at the destination it will be delivered to the addressee in the form of hard copy. At a cost of Rs. 10 per page of A4 size, e Post provides a cost-effective distributive solution for sending messages across the country, covering urban and rural populace . ePost services are available at 3,340 post offices. Just walk to your ePOST centre at the nearest post office and send ePost message today. It¶s easy ! It¶s cost-effective ! For corporate customers, ePOST corporate service that will enable the customers to send ePost from their premises for any destination across the nation. It costs just Rs 6 per ePost message of A4 size. Corporate can design their own templates and send them to multiple addresses through ePost corporate. Just a click and your message will reach the addressee thro ePost. PROJECT MEMBERS: 1)Amit Goyal 2)Ch.N.S.S.Aditya 3)M.Sridar

Sundarababu.POTLURI SIDDHARTHA INSTITUTE OF TECHNOLOGY. M. VIJAYAWADA A Mini Project on e-Post Submitted by AMIT GOYAL (08501A1225) CH. KANURU.N.S.Tech.ADITYA (08501A1214) M.V.S. ASSITANT PROFESSOR DEPARTMENT OF INFORMATION TECHNOLOGY Signature of the Guide Signature of the Project coordinator .SRIDHAR (08501A1246) BATCH NO: 11 Under the Guidance of Mr M.PRASAD.

Software Requirements Specification e-POST Under the Guidance of Mr. M.N.S.Aditya M.Tech. Submitted By G.Amit CH.Sridhar .Sundarababu M.S.

1 Use-Case Model Survey 2. 5.6 Overview Overall Description 2.2 Supplementary Requirements Supporting Information Concerns / Queries / Doubts if any: 5 5 5 5 6 6 6 7 8 13 15 15 15 15 15 Error! Bookmark not defined.3 Definitions.Table of Contents 1.1 Use-Case Reports 3.1 Purpose 1. 4.3 Assumptions and Dependencies Specific Requirements 3. Acronyms and Abbreviations 1.5 Technologies to be used 1. Introduction 1. 3. 2.2 Scope 1.4 References 1.2 Architecture diagram 2. .

Adequate payment mechanism as available from time to time. assure home delivery. e-Post employees are responsible for internal affairs like processing orders. of A4 sheets required for writing the letter can be selected. A sent soft copy will remain with the customer for reference. 1. Feedback mechanism. getting customer's delivery-time feedback. updating post's status and answering client's queries online. Also feedback can be given on the performance of particular vendors and the entire mall as well. so that customers can give feedback for the service which they have purchased.2 Scope Initial functional requirements will be: Secure registration and profile management facilities for Customers After registering the customer enters a page where no. Also facility rating of individual products by relevant customers. This document is meant to delineate the features of e-Post Office. so as to serve as a guide to the developers on one hand and a software validation document for the prospective client on the other. Maintaining database of the customers of different needs. Once the postal address of the destination is given in the ³TO´ field. 1. the entire letter is sent to that address as a hard copy.1 Introduction Purpose . . Regular updates to registered customers of the e-Post about new arrivals.Software Requirements Specification 1.

Help link on each of the screens. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer). due to the highly evolving nature of the project. a final one.Initial non functional requirements will be: Secure access of confidential data (user¶s details). by end user demands for whom this is being built. 1.4 References IEEE SRS Format 1. In addition to the above mentioned points. 24 X 7 availability Better component design to get better performance at peak time Advertisement space where it will effectively catch the customer¶s attention and as a source of revenue. the two main ones being TCP and IP. Acronyms and Abbreviations SLA: Service Level Agreement or SLA is a formal written agreement made between two parties. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between a web browser & a Web Server. market forces and most importantly. EJB: Enterprise Java Beans. It defines the term of engagement the fundamental rules that will govern the relationship. the suite of communication protocols used to connect hosts on the Internet. JAVA EE: Java Enterprise Edition 5 is a programming platform² part of the Java Platform-for developing and running distributed multi-tier architecture Java applications. TCP/IP uses several protocols. Customizable color scheme or skins. This list is by no means. the following are planned to be delivered if deemed necessary: Warehousing within the very ambits of the project More payment gateways. SSL can be used.3 Definitions. 1. TCP/IP: Transmission Control Protocol/Internet Protocol. based largely on modular software components running on an application server. The final list will be dictated by implementation constraints.5 Technologies to be used Programming languages: JAVA EE: Java Enterprise Edition is a programming platform² part of the Java . the service provider & the service recipient. Dynamic price model by which prices can be changed based on demand and supply Dynamic Storefront: Each user will have a web page personalized based on his or her recent activity.

This project envisages bridging the gap between the post offices and common man. It should run on Windows based platform. embedded images. It provides a means to describe the structure of text-based information in a document and to supplement that text with interactive forms.6 Overview The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. based largely on modular software components running on an application server. µquick to learn¶ and a reliable software for the above purpose. Section 3 gives specific requirements which the software is expected to deliver. It gives what level of proficiency is expected of the user. some general constraints while making the software and some assumptions and dependencies that are assumed. Tools & Development Environment: Tomcat server 1. 2. 2. HTML. JavaScript: A client side scripting language used to create dynamic web content and user interface. e-post office is intended to be a stand-alone product and should not depend on the availability of other software. e-post office should be user-friendly.Platform-for developing and running distributed multi-tier architecture Java applications. XML: Hyper Text Markup Language and Extensible markup Language are the predominant markup languages for web pages. Functional requirements are given by use case diagram. and other objects. . Some performance requirements and design constraints are also given.1 Overall Description Product perspective e-Post office is aimed towards the customers who want to reach out to the maximum cross-section of customer and common people who can be potential customer.

The user should be familiar with the Internet. Limited to HTTP/HTTPS. the user is prompted to login.2. post. The administrator also manages the list of available product categories. 2. stamps and transactions. The user have to pay some money to the postoffice bank account such that the user can get sufficient balance for posting.4 Constraints There is no maintainability of back up so availability will get affected. Use-Case Model Survey: edit catalog administrator user registration login payment . 2.2 Product functions User: Administrator Functions: The database Administrator is the super user and has complete control over all the activities that can be performed. To proceed with the sending of letters. and the administrator can then approve or reject them.3 User characteristics The user should be familiar with the post office related terminology like email.of pages and stamps required to send his message to the desired one. The application notifies the administrator of all product requests. User: Man who uses the online post office Functions: A valid user can choose the no. No multilingual support.

of pages and can send the letter through an email or by post. valid username and password. 2.   View all details: View the details of all users and control the whole site.   Registration: New users can sign up by creating new ID giving their name. Users: Login: Users must have a valid login id to enter into the site.Given below is an overall picture of the system. post office details to create a new id.  Selection of items: The users can select the various items required like stamps and no. Edit the catalogue: The administrator is also responsible for editing the catalogue. as depicted in the above use-case diagrams: 1.  Visitors: Visiting the Site: Can only visit the site without registration.  Payment: User can pay the amount of money by giving the card number. . Administrator:  Database Management: Control the database and keep track of all records of users and their details.

invalid details Collobaration Diagram for Login: 1: enter username.invalid details 3: checks 4: if yes then go to home page 2: checks for validity databas e .password checks for validity checks database if yes then go to home page otherwise.password user login page 5: otherwise.Sequence Diagram for login: user login page enter username.

Sequence Diagram for registration: user opens registration form database enter the fields press submit updates the user registred successfully Collobaration for registration: 1: opens 2: enter the fields 3: press submit button user registratio n form 5: registred successfully 4: updates the user details databas e .

Sequence Diagram for payment: user enter card number credit card user account money is deducted shows the remaining balance 1: enter card number user credit card 3: shows the remaining balance 2: money is deducted user account .

Calloboration diagram for payment 2.5 Architecture diagram .

6 Class Diagram user username : String password : String address : String email : Variant phoneno : Integer cardno : Integer cardcode : Integer cardinfo : Variant loginstatus : Boolean register() login() updateinfo() selection() display stamps : Variant pages : Integer account : Integer 1 1 selectionbymail() selectionbypost() display() pagesaccessed() * 1 administrator adm-name : String postoffice-address : String verification() delete() insert() adm-details() .2.

refined to the necessary level of detail to describe this subsystem or feature.1 [In use-case modeling. For each use case in the above use-case model or subset thereof. The specific requirements from the Supplementary Specifications which are applicable to this subsystem or feature should be included here. Administrator is created in the system already. these requirements are captured in the use cases and the applicable supplementary specifications. payment and service transaction provided manually. the outline for supplementary specifications may be inserted directly into this section. refer to or enclose the use-case report in this section. When using use-case modeling. Supporting Information [The supporting information makes the SRS easier to use. and testers to test that the system satisfies those requirements. b) Index.2. the use cases often define the majority of the functional requirements of the system.] 4. It includes: a) Table of contents. Roles and tasks are predefined. the SRS should explicitly state whether or not the appendices are to be considered part of the requirements. When appendices are included. along with some non-functional requirements. These may include use-case storyboards or userinterface prototypes. Make sure that each requirement is clearly labeled. These may be captured directly in this document or refer to separate Supplementary Specifications. Specific Requirements [This section of the SRS should contain all the software requirements to a level of detail sufficient to enable designers to design a system to satisfy those requirements.] 3. c) Appendices. customer. If use-case modeling is not used.] Use-Case Reports 3. . 3. Make sure that each requirement is clearly labeled. which may be used as an enclosure at this point.2 Supplementary Requirements [Supplementary Specifications capture requirements that are not included in the use cases.7 Assumptions and Dependencies The details related to the product.