Software requirement - Created by system analyst after requirements are collected

Discussion

• Nirja Shah   -Posted on 14 Oct 15
  - SRS is a document created by system analyst after the requirements are collected from various stakeholders.
  
  - SRS defines how the intended software will interact with hardware, external interfaces, speed of operation, response time of system, portability of software across various platforms,maintainability, speed of recovery after crashing, Security, Quality, Limitations etc.
  
  - The requirements received from client are written in natural language.
  
  - It is the responsibility of system analyst to document the requirements in technical language so that they can be comprehended and useful by the software development team.
  
  - SRS should come up with following features:
  1. User Requirements are expressed in natural language.
  2. Technical requirements are expressed in structured language, which is used inside the organization.
  3. Design description should be written in Pseudo code.
  4. Format of Forms and GUI screen prints.
  5. Conditional and mathematical notations for DFDs etc.
  6. Software Requirement Validation
  
  - After requirement specifications are developed, the requirements mentioned in this document are validated.
  
  - User might ask for illegal, impractical solution or experts may interpret the requirements incorrectly.
  
  - This results in huge increase in cost if not nipped in the bud.
  
  - Requirements can be checked against following conditions -
  1. If they can be practically implemented
  2. If they are valid and as per functionality and domain of software
  3. If there are any ambiguities
  4. If they are complete
  5. If they can be demonstrated

➨ Post your comment / Share knowledge