Software Requirement Specification Based Study Material for gate Computer Science
Hello friends today in this gate study material for computer science we are going to tell you about software requirement specification document such as what characteristics a srs should have or what are the issues that should be addresses by a software requirement specification.
SRS is the process of establishing the services, the system should provide of the system in new, it is difficult for software engineer to understand the nature of problem constraints under which it must operates, so software engineer take help of a step called requirement capture and analysis. It is first formal document Informal design outline More formal
Design Finished design Informal Design.
The SRS should be: Correct, Unambiguous, Complete
- Correct: An SRS is correct iff every requirement stated therein is one that the software shall meet.
- Unambiguous: An SRS is unambiguous iff every requirement stated therein has only one interpretation. Each sentence in SRS should have the unique interpretation.
- Complete: An SRS is complete iff it includes all significant requirements full labels and references to all figures and diagram and definition of all terms and units of measures produce in the software development process and it serves as a basis for the contract between a producer and a software developer/supplier.
Here in this Study Material for gate Computer Science we are also telling some issues addressed by software requirement specification. The important issues that a SRS must address are:
(a) System goals and requirements are different: Goal is a more general characteristics." e. g. Whole system should be designed in a user friendly manner or more robust system". Requests are more testable in nature. For example all users command selection should be only using pop up menus.
(b) Request Definition: A statement in a natural language stating what services the system should expected to provide. It should be understandable by clients, contractors, management & users.
(c) Request Specification: A structured document maintaining the services in more details than definition, and precise enough to act as a contract. It should be understandable by technical staff both at a developer and producer’s place.
(d) Software Specification (Design Specifiation): It is an abstract design description of the software which is the basis for design and implementation. There should be a clear relationship between this documents and the software request specification. The reader of this document is software engineer, system analyst and project leaders.
(e) Requirement Capture and Analysis: It is the process of designing the system request captures through: -
(i) Observation of existing system.
(ii) Discussion with potential users, producers.
(iii) Personal interviews and task analysis.
(iv) Standard published documents/reports from the user.
(f) Feasibility Study:
(i) It is an estimate made whether the identified user needs can be satisfied using the current technology.
(ii) Whether the proposed system is cost effective.
(iii) Whether it is possible to develop the system within the budgetary and time constraints.
(g) Suggestions for preparing an SRS Document:
(i) Only specify external system behavior.
(ii)Specifying the constraints on implementation.
(iii)It should record for thought about the life cycle of the system.
(iv) It should characterize acceptable responses to the undesired events.
I hope this Computer Science Study Material for Gate will be beneficial for gate aspirants. Or computer science students.