26-07-2014, 10:50 AM
Software Requirements Specification
Software Requirements.doc (Size: 317 KB / Downloads: 15)
1 Introduction
Temple Management System is a software designed for better management of temple activities. It is used for interaction between pilgrims, temple employees and the management. Considering the real situation, This Temple Management System helps the Managements to store, retrieve the details of any type of pooja’s and stock details, and manage the booking of Vazhipadu, customer registration, staff registration,. Utilizing this Temple management system they can check income of preferred date, vazhipadu details, notifications and adding of new vazhipadu to the list.
1.1 Document Purpose
This Software Requirements Specification (SRS) specifies the requirements of the TEMPLE MANAGEMENT SYSTEM (TMS ) which will be used in most of the temples. This document will be useful for the clients to ensure all specifications and requirements are conductive as mentioned by the software engineer to design the system. The system is a self contained product that is it is not a follow on of any product family or it is not a replacement of any existing system. It is the software which provides the temple details.
1.2 Product Scope
Temple Management System is designed for better management of temple activities. It is used for interaction between pilgrims, temple employees and the management. Considering the real situation, This Temple Management System helps the Managements to store, retrieve the details of any type of pooja’s and manage the booking of Vazhipadu. Utilizing this Temple management system they can check income of preferred date, vazhipadu details, employee registration, and adding of new vazhipadu to the list. This software generates the report of the day sheet. These details will be provided for the corresponding administrator whenever they login.
1.3 Intended Audience and Document Overview
The first section of SRS builds a brief idea what the proposed System of SIC is and what is the need behind having it. Along with this background information it also provides the reference information for further study, design and implementation.
The second section shows the way to overall description of application, functions, perspective, operating environment, design and implementation constraints, data inputs required.
The third section explores the various descriptions of external interfaces such as user interface, hardware interface, communication interface and software interface.
3.2 Functional Requirements
This software generates the report of the day sheet. These details will be provided for the corresponding administrator whenever they login.
1 Normalization
The normalization process takes a relation schema through a series of tests to certify whether it satisfies a certain normal form. The process, which proceeds in a top-down fashion by evaluating each relation against the criteria for normal forms and decomposing relations as necessary, can thus be considered as relational design by analysis. There are mainly three normal forms: first, second, and third normal form. All these normal forms are based on a single analytical tool: the functional dependencies among the attributes of a relation.
Normalization of data can be considered a process of analyzing the given relation schemas based on their FDs and primary keys to achieve the desirable properties of,
• Minimizing redundancy
• Minimizing the insertion, deletion, and update anomalies
4.1 Performance Requirements
Temple management system software is real time and should be performed in minimum requirements. This software will work in all conditions except that require an un-interrupted power supply throughout its performance.
4.2 Safety and Security Requirements
The data handled in the system is very vital. The server should always be
confirmed to run properly and the data are saved to the consecutive intervals. Power is a significant feature and the power supply should be always taken care of. An Uninterrupted Power Supply is always recommended Provide at least 3 different safety requirements based on your interview with the client .
The security system features from having a login for all the users to access the software. The login details will be used in the system also. So the chances of the software getting intruded are very less.
4.3 Software Quality Attributes
Illegal duplication of the reports should be strictly dealt with. The administrator should have full details of the user while a user is getting registered to the system.