What is software requirement specification, Software Engineering

Q. What is Software requirement Specification (SRS)? Why is it important? List the characteristic of a good quality SRS?

Ans: (SRS) Software Requirement Specification Document is the output of obligation analysis stage o the software development life cycle. It documents all kinds of requirements and constraints imposed on the end product. This document is important for the reason that it is used in all the successive stages of SDLC. Any error introduced here will consequence in to incomplete and bad quality product. The characteristics of a superior quality SRS are:

1) Correctness

2) Completeness

3) Verifiability

4) Traceability

5) Design Independent

6) Understandable by customer

7) Consistency

8) Unambiguousness

9) Ranking for importance and/ or stability

10) Modifiability

Posted Date: 7/26/2013 3:25:35 AM | Location : United States







Related Discussions:- What is software requirement specification, Assignment Help, Ask Question on What is software requirement specification, Get Answer, Expert's Help, What is software requirement specification Discussions

Write discussion on What is software requirement specification
Your posts are moderated
Related Questions

I need help creating a DFD for an assignment. Is there anyway you could help?

Explain the Iterative Model Every release of Iterative Model is developed in a specific, fixed time period known as iteration. Each iteration focuses on a certain set of requir

(i) Concept definition of Quality Control and Quality Assurance (ii) Tools used in quality control (iii) Acceptance sampling and process control (iv) Statistical tools for

The sudden and finish failure of a computer system or component.

1. An orderly development of testing in which software elements, hardware elements, or both are joined and tested, to check out their interactions, unless the entire system has bee

Explain the term in brief- Test Script and Test Specification: Test Script: - It is generally used to refer to instructions for a particular test which will be carried out

How to interpret software metrics(any metrics)...i need an example


Test Build Managers, System Administrators and Database Administrators deliver new software versions to the test environment, install the application's software and apply software