Skip to main content

What is SRS

SRS is the detailed description regarding the discussion with client as per the requirement. It include the complete process that how the product will flow, what kind of technology we will use to develop the software, what are the strategy we follow.

basically SRS is the complete document that help the Developer, Manager, QA Manager and all other user who are taking part to develop the software.


In other terms we can say that A software requirements specification (SRS) is a description of a software system to be developed, laying out functional and non-functional requirements, and may include a set of use cases that describe interactions the users will have with the software. The software requirements specification document enlists enough and necessary requirements that are required for the project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed or being developed. This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software.
  • Introduction
  • Purpose
  • Definitions
  • System overview
  • References
  • Overall description
  • Product perspective
  • System Interfaces
  • User Interfaces
  • Hardware interfaces
  • Software interfaces
  • Communication Interfaces
  • Memory Constraints
  • Operations
  • Site Adaptation Requirements
  • Product functions
  • User characteristics
  • Constraints, assumptions and dependencies
  • Specific requirements
  • External interface requirements
  • Functional requirements
  • Performance requirements
  • Design constraints
  • Standards Compliance
  • Logical database requirement
  • Software System attributes
  • Reliability
  • Availability
  • Security
  • Maintainability
  • Portability
  • Other requirements

Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

Structural Testing

Structural Testing is the type of testing in which user should have the knowledge of the code because in this testing user need to check the structure of the system. Structural Testing is White Box Testing.