Q NO 1: What is meant by software requirement definition? Elaborate on its importance?Ans:
A software requirements specification (SRS) is a comprehensive description of the intended purpose andenvironment forsoftwareunder development. The SRS fully describes what the software will do and howit will be expected to perform.
An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizesthe development cost. A good SRS defines how anapplicationwill interact with systemhardware,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. Methods of defining an SRS are described by theIEEE(Institute of Electrical and Electronics Engineers) specification 830-1998.
Q NO 2: Explain varies steps involved in Requirement Engineering?Ans:
Software requirements engineering for a software development project has a few typical phases:1.
Requirements elicitation and gathering
is always a necessary step, as frequently primary internal and
external project stakeholders do not know what they want, the requirements can be deeply “hidden”
within a client organization, prior requirements may not be validated or verifiable, and even completelyincorrect. This is the phase of the project which will largely determine the success or failure of theproject.2.
is a way in which the written, prose requirements are presented in anotherformat. Although effectively doing this can prove difficult for novices, many techniques such asuse casemodeling,UMLdiagrams,user storiesanduser goalscan help system designers and requirements
engineers and business analysts represent the requirements in a more easily comprehensible or shareableform.3.
is the process whereby the requirements are checked for consistency,correctness, completeness, sufficient detail, and writing style and format.