Software requirement specification
Software requirement specification abbreviated as SRS is a means of translating the idea of files into a formal document. The main features of SRS include:
Establishing the basis for an agreement between the client and the developer. Producing a reference for validation of the final product.
SRS assist clients in determining if the software meets the requirements.
Mainly there are six requirements which an SRS must satisfy.
(a) It should specify the external behaviour.
(b) It should specify the constraints.
(c) It should be easy to change.
(d) It should be a reference tool.
(e) It should record throughout the lifecycle.
(f) It should have the capacity of expectation of an undesired event.
Usually we come across four types of requirement specification
(a) User Interface Requirements
(b) Database Requirements
(c) Functional Requirements
(d) Non-Functional Requirements
4.1User Interface Requirements
The user of the proposed system requires that the developed software should be user friendly, have security access, and ensure the privacy of the administrator and produce results in timely manner. The users are not frequently exposed to the on-line hotel management, so the system interface to the user must be simple and understandable. The web pages must be user-friendly and must be in an easy-to-use style. The user must be able to easily switch among various I/O screens. The product is well designed so that it can be used easily by layman and also the users who are novices to the system.
The system should be designed in such a way that only authorized users should be allowed to login to the system. The user interface should be as interactive as possible. A user-friendly interface must be provided so that the user can easily interact with the system and comprehend things in a quicker and easier way. The system must provide reliable and up-to-date information.
The application should be efficient so that the user does not spend much time in training. Consistency will increase the confidence of the user in the reliability of the application. The user must be limited with a small set of operations to achieve the result. The application should be visually and conceptually clear. The interface should accommodate user mistakes easily and fast. It should minimize the errors and should handle them peacefully.
4.2Database Requirements
The database should be designed in such a way that it enhances the efficient storage, retrieval and manipulation of all the information associated. For instance all general information regarding an item attribute should be stored in a particular table.
The concerned users should have the facility to query to the database and supply the basic information easily. Security mechanisms should be provided so that no confidential details should be accessible to unauthorized persons. The database should be organized in such a way that it helps in preparing various essential summaries needed for users.
4.3Functional Requirements
The various functional requirements of the system can be summarized as:-
(a) A home page that is user friendly and ambiguous.
(b) Administrator Login Facility
(c) Room Availability Check Facility
(d) Easy Reservation Process
(e) Provide Reservation Slip
(f) Links to other related sites.
(g) Ability of Administrator to perform any tasks which you can see in my snapshots(below) and in my running project.
4.4Non-Functional Requirements
Non-functional requirements define the system properties and constraints that arise through user needs, because of the budgeted constraints or organizational policies, or because of the need for interoperability with other software or due to the external factors such as safety regulations privacy registrations and so on.
4.5Other Requirements
Performance Requirements
(a) The database should be centralized and secure.
(b) The system should be user friendly and easily accessible
(c) The system must be reliable.
Design Requirements
The main objectives of input design are:
(a) Controlling the amount of input
(b) Keeping the process simple, avoiding errors.
(c) The best thing in the input design is to achieve all the objectives mentioned in the simplest manner possible.
The main objectives of output design are:
(a) Identifying the specific outputs.
(b) Creating reports for displaying and storing information.
Software requirement specification abbreviated as SRS is a means of translating the idea of files into a formal document. The main features of SRS include:
Establishing the basis for an agreement between the client and the developer. Producing a reference for validation of the final product.
SRS assist clients in determining if the software meets the requirements.
Mainly there are six requirements which an SRS must satisfy.
(a) It should specify the external behaviour.
(b) It should specify the constraints.
(c) It should be easy to change.
(d) It should be a reference tool.
(e) It should record throughout the lifecycle.
(f) It should have the capacity of expectation of an undesired event.
Usually we come across four types of requirement specification
(a) User Interface Requirements
(b) Database Requirements
(c) Functional Requirements
(d) Non-Functional Requirements
4.1User Interface Requirements
The user of the proposed system requires that the developed software should be user friendly, have security access, and ensure the privacy of the administrator and produce results in timely manner. The users are not frequently exposed to the on-line hotel management, so the system interface to the user must be simple and understandable. The web pages must be user-friendly and must be in an easy-to-use style. The user must be able to easily switch among various I/O screens. The product is well designed so that it can be used easily by layman and also the users who are novices to the system.
The system should be designed in such a way that only authorized users should be allowed to login to the system. The user interface should be as interactive as possible. A user-friendly interface must be provided so that the user can easily interact with the system and comprehend things in a quicker and easier way. The system must provide reliable and up-to-date information.
The application should be efficient so that the user does not spend much time in training. Consistency will increase the confidence of the user in the reliability of the application. The user must be limited with a small set of operations to achieve the result. The application should be visually and conceptually clear. The interface should accommodate user mistakes easily and fast. It should minimize the errors and should handle them peacefully.
4.2Database Requirements
The database should be designed in such a way that it enhances the efficient storage, retrieval and manipulation of all the information associated. For instance all general information regarding an item attribute should be stored in a particular table.
The concerned users should have the facility to query to the database and supply the basic information easily. Security mechanisms should be provided so that no confidential details should be accessible to unauthorized persons. The database should be organized in such a way that it helps in preparing various essential summaries needed for users.
4.3Functional Requirements
The various functional requirements of the system can be summarized as:-
(a) A home page that is user friendly and ambiguous.
(b) Administrator Login Facility
(c) Room Availability Check Facility
(d) Easy Reservation Process
(e) Provide Reservation Slip
(f) Links to other related sites.
(g) Ability of Administrator to perform any tasks which you can see in my snapshots(below) and in my running project.
4.4Non-Functional Requirements
Non-functional requirements define the system properties and constraints that arise through user needs, because of the budgeted constraints or organizational policies, or because of the need for interoperability with other software or due to the external factors such as safety regulations privacy registrations and so on.
4.5Other Requirements
Performance Requirements
(a) The database should be centralized and secure.
(b) The system should be user friendly and easily accessible
(c) The system must be reliable.
Design Requirements
The main objectives of input design are:
(a) Controlling the amount of input
(b) Keeping the process simple, avoiding errors.
(c) The best thing in the input design is to achieve all the objectives mentioned in the simplest manner possible.
The main objectives of output design are:
(a) Identifying the specific outputs.
(b) Creating reports for displaying and storing information.
0 comments:
Post a Comment