Algorithm for software implementation - Software Specification & Measurement

Q.  Which of the following is not defined in a good Software Requirement Specification (SRS) document?
- Published on 21 Jul 15

a. Functional Requirement.
b. Nonfunctional Requirement.
c. Goals of implementation.
d. Algorithm for software implementation.

ANSWER: Algorithm for software implementation.
 

    Discussion

  • Nirja Shah   -Posted on 06 Oct 15
    Software requirements specification (SRS)
    - It 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.

    - It establishes the basis for an agreement between customers and contractors or suppliers on what the software product is to do as well as what it is not expected to do.

    - They permit a rigorous assessment of requirements before design can begin and reduces later redesign.

    - It should also provide a realistic basis for estimating product costs, risks, and schedules.

    - The SRS 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.

    - The SRS may be one of a contract deliverable Data Item Descriptions or have other forms of organizationally-mandated content.

    - An example organization of an SRS is as follows:

    1. Introduction
    - Purpose
    - Definitions
    - System overview
    - References
    2. 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
    3. Specific requirements
    - External interface requirements
    - Functional requirements
    - Performance requirements
    - Design constraints
    - Standards Compliance
    - Logical database requirement
    4. Software System attributes
    - Reliability
    - Availability
    - Security
    - Maintainability
    - Portability
    5. Other requirements

Post your comment / Share knowledge


Enter the code shown above:
 
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)