INTRODUCTION
The SRS provides functioning of the Post Office Transaction System software used in postal offices all over the country. This software works in a Client Server environment with the server storing the data and clients connecting to the server for all types of transactions.
It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate, specific requirements and other supporting information. This document is intended for both the stakeholders and the developers of the system.
This document is intended for developers, project coordinator, project guide, users and testers. The developer can use the document to view the analysis and design part, to understand requirements specification. The project coordinator can use this document to review the idea of project whether it is innovative and usable or not.
The project guide can use this document to analyze and manage the flow of project development. The tester can use this document to get clear idea about system, to understand the exact input domain of system and to generate respective test cases for the testing purpose.
PURPOSE
This Software Requirements Specification provides a complete description of all the functions and specifications of the Postal Transaction management system software. The purpose of this document is to present a detailed description of the Post Office Transaction System.
This document is useful for Postal employees who use this system on the daily basis. This document will also serve as a reference to incorporate any changes made in the system to the future.
It will also prove to be useful to the managerial staff which is responsible for the smooth functioning of the counter transactions that are performed on daily basis.
This document is primarily intended to provide a detailed specification of the functional requirements for developers of the product. It also provides an overview of the product for the users. It will explain the purpose and features of the system, what the systems do and the constraints under which it will operate.
This SRS document contains the complete software requirement for Post Office Transaction System and describes the design decisions, architectural design and the detail design needed to implement the system. It provides the visibility in the design and provides information needed for software support.
SCOPE
This software is used by System Administrator, Supervisor, Counter Assistant (Operator), IPO Assistant.
The system is designed to provide user authentication by maintaining the user database which contains all the details of user along with login details such as username and password. Each user has a different level of operation for the authentication purpose. The user is required to provide all the details regarding orders for booking. The system will create invoices of the placed orders and maintain databases for the same.
The major goal of the system is to provide a single window for all the post office transactions and to computerize all accounting functions. By integrating the daily transactions carried out by subordinate offices and front office and back office functioning, the system provides a facility to the customers to carry out all the transactions from any post office counter.
REFERENCES
- Shivaji Nagar head office, Pune 411005
- Meghdoot Software for post office.
- [IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,” 2001 edition. The IEEE standards for Software Project Requirements Specifications, 830-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes.
- [Bruade] The principal source of textbook material is “Software Engineering: An Object-Oriented Perspective” by Eric J. Bruade (Wiley 2001).
OVERVIEW
This document contains a brief history and insight into the problem as well as what the system is designed to do, the scope of the solution. It gives a brief summary of whom the system is targeted at, its capabilities, and its positioning in the device development process. It also explains requirements of the system and also where exactly the user and stakeholders are placed in the scheme of things. It elaborates on security issues, hardware and software requirement and also the priorities of various functionalities.
The document helps the user to understand the Postal System. The first part of the document provides the purpose, objectives and scope of the proposed system. It includes important definition and abbreviation, the problem statement specify the needed details to avoid any kind of ambiguity from user’s perspective. The document also states the feature set and capabilities of the system.
The document also highlights the feature of proposed system and the advantages over the existing system. The document also highlights the various issues, error handling and the modification to be done in the system. The document is helpful to the user as it gives them opportunities to state what they expect from the system. In addition, the hardware specification required for the system is also mentioned. The user can read the document and make sure that his machine is equipped to run the system to avoid any inconvenience The user should make use of the document to understand the system better.
The rest of this document provides a full description of the project for the postal office. It lists all the functions performed by the system. It gives the details of each of the system functions and actions in full for the software developer’s assistance. It also gives the overview of the problems currently faced by the system and provides solutions for the same.
OVERALL DESCRIPTION
The project deals with the problem of requiring the customers to interact with two or more counters to get the transactions done. The system will avoid this problem by including all the post office transaction functionalities on a single machine. The system will authenticate the user. The system will provide intuitive menu that provides checks and controls to guide the operator. The system will allow the user to enter the details. The system will create invoices of the placed orders and maintain database for the same. The system will maintain a database that stores information about the employee and the details regarding various bills
The system will receive at the national level a comprehensive and accurate accounting and statistical data concerning counter operations. The system will fully automate the counter operations, ensuring security of cash flow and accurate tracking of all operations. The system will maintain the record of all the letters according to the area wise distribution.
PROBLEM STATEMENT
The problem of
- Manually handling all the post office transactions in an environment where specific counters are put in place.
- The customer generally needs to interact with two counters to get any transaction done.
Affects
- Postal employees, customers
The impact of which is
- All the data which is captured at the counter, is duplicated again at the back-end and all the accounting and integrating functions are required to be done manually.
A successful solution would
- Provide single window for all the post office transactions;
- computerize all accounting functions;
- integrate daily transactions carried out by subordinate offices and integrate front office and back office functioning.
It would provide a single window facility to the customers so that all transactions can be carried out from any post office counter
PRODUCT PERSPECTIVE
The Post Office transaction management system is a part of the entire postal software used in postal department. The system mainly simplifies the manual work done by clerks in post offices. It provides customer satisfaction by providing ‘single window facility’.