Srs for Finance

Only available on StudyMode
  • Download(s) : 12
  • Published : December 14, 2012
Open Document
Text Preview
1. INTRODUCTION
1.2 OUTLINE OF PROJECT
FEES MANAGEMENT SYSTEM will provide a view, submit, online payment, uploading various documents and other mislenious resources. This view will be based on the categories like attendance view and daily activities. Further the University management student personnel can add/update/remove the resources or an automatic removal of accessing features when the time limit completes. The System will also have an ADMIN who has full-fledged rights with regards to managing resources across branches – such as transferring books across these branches. The following forms will be used in this project they are receipt, payments, income tax, balance sheet, SMS alerts. The users can view, submit, online payment, uploading various documents and information about their account etc. there are basic two types of users one are the students and other are faculty members. Each user facilitates with a different account number having a profile along with a password for private use. The two types of users differ from each other due to the accessing limits to online University management system. This document describes the design decisions, architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support. The document gives the detailed description of the both functional and non functional requirements proposed by the client. The document is developed after a number of consultations with the client and considering the complete requirement specifications of the given Project. The final product of the team will be meeting the requirements of this document. Major functionality in Fee management is maintaining fee structure for various programs. SMS provides a comprehensive fee management system to define various fees based on semester (Overall / Individual), annual, one-off payment and tuition fee base on credit points.

2. SOFTWARE REQUIREMENT SPECFICATION

2.1 INTRODUCTION
A software requirements specification (SRS) - a requirements specification for a software system - is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). The software requirements specification document enlists all necessary requirements for project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with project team and the customer. The SRS fully describes what the software will do and how it will be expected to perform. An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost. A good SRS defines how an application will interact with system hardware, other programs and human users in a wide variety of real-world situations. Parameters such as operating speed, response time, availability, portability, maintainability, footprint, security and speed of recovery from adverse events are evaluated. 

2.1.1 PURPOSE
The main objective of this document is to illustrate the requirements of the project FEES MANAGEMENT SYSTEM. This document describes the design decisions, architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support. The document gives the detailed description of the both functional and non functional requirements proposed by the client. The document is developed after a number of consultations with the client and considering the complete requirement specifications of the given Project. The final...
tracking img