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.
1.1 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
References: 4. [Bruade] The principal source of textbook material is “Software Engineering: An Object-Oriented Perspective” by Eric J. Bruade (Wiley 2001).