Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 34 views

    Checklist - SRS Review

    Uploaded by

    learnit learnit
    The document is an SRS review checklist used to evaluate a software requirements specification document. It contains questions to check for document control procedures, an overview of requirements, organization and completeness, correctness, quality attributes, traceability, and special issues. Reviewers would use the checklist to validate requirements by ensuring things like no conflicts, all requirements are testable, interfaces are described, and non-functional needs around performance, security are specified.

    Copyright:

    © All Rights Reserved
    Download as XLS, PDF, TXT or read online from Scribd

    Checklist - SRS Review

    Uploaded by

    learnit learnit
    34 views2 pages
    The document is an SRS review checklist used to evaluate a software requirements specification document. It contains questions to check for document control procedures, an overview of requirements, organization and completeness, correctness, quality attributes, traceability, and special issues. Reviewers would use the checklist to validate requirements by ensuring things like no conflicts, all requirements are testable, interfaces are described, and non-functional needs around performance, security are specified.

    Original Description:

    Checklist_SRS Review

    Original Title

    Checklist_SRS Review

    Copyright

    © © All Rights Reserved

    Available Formats

    XLS, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document is an SRS review checklist used to evaluate a software requirements specification document. It contains questions to check for document control procedures, an overview of requirements, organization and completeness, correctness, quality attributes, traceability, and special issues. Reviewers would use the checklist to validate requirements by ensuring things like no conflicts, all requirements are testable, interfaces are described, and non-functional needs around performance, security are specified.

    Copyright:

    © All Rights Reserved
    Download as XLS, PDF, TXT or read online from Scribd
    Download as xls, pdf, or txt
    34 views2 pages

    Checklist - SRS Review

    Uploaded by

    learnit learnit
    The document is an SRS review checklist used to evaluate a software requirements specification document. It contains questions to check for document control procedures, an overview of requirements, organization and completeness, correctness, quality attributes, traceability, and special issues. Reviewers would use the checklist to validate requirements by ensuring things like no conflicts, all requirements are testable, interfaces are described, and non-functional needs around performance, security are specified.

    Copyright:

    © All Rights Reserved
    Download as XLS, PDF, TXT or read online from Scribd
    Download as xls, pdf, or txt
    of 2

    SRS Review Checklist

    Project Code:
    Version of the work product:
    Reviewer(s):
    Review date: <DD-MMM-YY>
    Work product' size:
    Effort spent on review (person-hour)

    Question Yes No N/A Note


    Document Control
    Verify whether document control procedures have been followed by
    checking for the following:
    Does the title page contain the document name, version number, FPT
    name and logo, project code, document code and issued date?
    Does the header and footer correctly specify the name, and version of the
    document?
    Does the page – numbering scheme indicate the total number of pages in
    the document?
    Have details been entered in the ‘Approval’ and ‘Reviewers’ fields in
    Signature page?
    Is the history traceable?
    Are all documents checked Spelling and Grammar in MS Word or similar
    tools?
    Overview
    Are the system objectives stated clearly?
    Are requirements documented in a readable form:
    1. Requirements are grouped logically
    2. Requirements are described in sufficient detail
    3. Requirements are stated precisely
    4. Diagrams are simple
    Organization and Completeness
    Are all internal cross-references to other requirements correct?
    Do the requirements provide an adequate basis for design?
    Is the implementation priority of each requirement included?
    Are algorithms intrinsic to the use-case defined?
    Is any necessary information missing from a requirement? If so, is it identified as to-
    be-determined marker
    Is the expected behavior documented for all anticipated error conditions?
    Correctness
    Do any requirements conflict with or duplicate other requirements?
    Is each requirement verifiable (such as by review, testing, demonstration, or
    analysis)?
    Is each requirement in scope for the project?

    Can all of the requirements be implemented within known constraints?


    Are any specified error messages unique and meaningful
    Quality attributes
    Are all performance objectives properly specified?
    Are all security and safety considerations properly specified?
    Are other pertinent quality attribute goals explicitly documented and quantified, with
    the acceptable trade-offs specified?
    Traceability
    Is each requirement uniquely and correctly identified?
    Is each software functional requirement traced to a higher-level requirement (ex.
    System requirement or use case)?
    Special Issues
    Are all requirements actually requirements, not design or implementation solutions?

    03e-CL/PM/HDCV/FSOFT 1/5 Internal use 1/2


    Question Yes No N/A Note
    Document Control
    Are the time-critical functions identified and their timing criteria specified?
    External interfaces
    Check whether interfaces with other systems are described
    Operating environment
    Hardware
    Check whether the required hardware is described
    Software
    Check whether specific software requirements are documented
    Network
    Check whether networking Issues and connectivity requirements are documented

    Communication
    Check whether specific communication requirements are documented
    Special user requirements
    Multi Language support
    Is any security required?
    Check whether availability requirements are documented
    Audit Trail
    Transaction Volume & Data Volume
    Backup & Recovery
    Legal
    Data Migration
    Data Retention*
    Installation
    User Training
    User Manual & Help

    For QA checking
    Does SRS cover all requirements in Specs and Q&A list?
    How many items in SRS are TBD?
    Are TBD requirements recorded in Q&A list to clarify with customer?
    If TBD requirements are more than 10%, does Project Director approve SRS?
    Check review comments, if comments are not available, must request Project
    Director to review and approve SRS.

    <Add more rows if needed>

    * Comments

    * Suggestion

    [ ] - Pass
    [ ] - Review again
    [ ] - Other

    03e-CL/PM/HDCV/FSOFT 1/5 Internal use 2/2

    You might also like