Saturday, September 16, 2006

3. Sample Template

System Requirements Specification Template

Taken from Volere. Please refer http://www.volere.co.uk for further details.

The elements of SRS are outlined below:

Project Drivers

  1. The purpose of the project
    i.User problem or background of the project effort
    ii.Goals of the project
  2. Client, customer and other stakeholders
    i.Client – the person who authorizes the development, and/or is paying for it
    ii.Customer – the person (s) who will buy the product
    iii.Other stakeholders
  3. Users of the product
    i.Hands on users – people who operate the product
    ii.Priorities assigned to users
    iii.User participation – an estimate of needed involvement in the project

Project Constraints

  1. Mandated Constraint
    i.Solution Design Constraints
    ii.Implementation Environment of the current system
    iii.Partner or collaborative applications to be used by the product
    iv.Off-the-shelf software used within the product
    v.Anticipated workplace environment
    vi.Project duration budget
    vii.Financial budget for the project
  2. Naming Conventions and Definitions
  3. Relevant Facts and Assumptions
    i.Factors that have an effect on the product but are not mandated requirements constraints
    ii.Assumption the team is making about the project

Functional Requirements

  1. Scope of the work
    i.Context of the work
    ii.Work partitioning or business use case list
  2. The scope of the product
    i.Product Boundary
    ii.Product Use Case list
  3. Functional and Data Requirements
    i.Functional requirements
    ii.Data requirements

Non-Functional Requirements

  1. Look and feel requirements
    i.Interface appearance
    ii.Style of the product
  2. Usability and Humanity Requirements
    i.Ease of use
    ii.Personalization and Internationalization requirements
    iii.Ease of learning
    iv.Understandability requirements
    v.Accessibility requirements
  3. Performance Requirements
    i.Speed and latency requirements
    ii.Safety critical requirements
    iii.Precision requirements
    iv.Reliability and availability requirements
    v.Robustness requirements
    vi.Capacity requirements
    vii.Scalability or extensibility requirements
  4. Operational requirements
    i.Expected physical environment
    ii.Expected technological environment
    iii.Partner applications
    iv.Productization requirements
  5. Maintainability and Support requirements
    i.Maintenance requirements
    ii.Special conditions for maintenance
    iii.Supportability
    iv.Adaptability requirements
  6. Security requirements
    i.Access requirements
    ii.Integrity requirements
    iii.Privacy requirements
    iv.Audit requirements
    v.Immunity requirements
  7. Cultural and Political requirements
  8. Legal requirements
    i.Compliance and Standards requirements

Project Issues

  1. Open Issues
  2. Off-the-shelf solutions
    i.Ready made products that can be bought
    ii.Ready made components suitable for this product
    iii.Other products that can be copied
  3. New Problems
    i.New problems caused by installing the product in the current environment
    ii.Affects on the installed system
    iii.Adverse effects on existing users
    iv.Limitations of the anticipated implementation environment
    v.Other problems
  4. Tasks
    i.Steps to be taken to deliver the product
    ii.Development phases
  5. Cutover
    i.Special requirements to have the existing data and procedures work in conjunction with the new product
    ii.Data to be modified/translated for the new product
  6. Risks
  7. Costs
  8. User documentation and training
  9. Waiting room
  10. Ideas for solutions

No comments: