Requirements Template

This Requirements Template is based on the Volere Requirements Specification Template, Copyright of the Atlantic Systems Guild Inc.

It is useful for projects of any size, and is in use at thousands of organizations around the world. It is fully described in Mastering the Requirements Process (2nd Edition).

  • How to Use This Template
    • If you're interested in learning about Volere template and how to get started analysing requirements, you can go to Getting Started with the Volere Template.
    • If you just want to get started writing requirements in a Word document, you can download it here.
    • If you need help with what a specific Heading is meant to contain, you can look at the description of each one in this PDF document.
  • To look at details of any of the 5 sections below, click on the markers beneath that heading.

A copyright notice for Volere and the Atlantic Systems Guild should appear in all documents making use of it.

- 1 Project Drivers

1.1 Purpose of this Project

    • To be determined.

1.1.1 Background of the Project Effort

    • To be determined.

1.1.2 Goals of the Project

    • To be determined.

1.2 Client, Customer and Other Stakeholders

    • To be determined.

1.2.1 The Client

    • To be determined.

1.2.2 The Customer

    • To be determined.

1.2.3 Other Stakeholders

    • To be determined.

1.3 Users

    • To be determined.

1.3.1 The Hands-on Users of the Product

    • To be determined.

1.3.2 Priorities Assigned to Users

    • To be determined.

1.3.3 User Participation

    • To be determined.

1.3.4 Maintenance Users and Service Technicians

    • To be determined.

- 2 Project Constraints

2.1 Mandated Constraints

2.1.1 Solution Constraints

    • To be determined.

2.1.2 Implementation Environment of the Current System

    • To be determined.

2.1.3 Partner or Collaborative Applications

    • To be determined.

2.1.4 Off-the-Shelf Software

    • To be determined.

2.1.5 Anticipated Workplace Environment

    • To be determined.

2.1.6 Schedule Constraints

    • To be determined.

2.1.7 Budget Constraints

    • To be determined.

2.2 Naming Conventions and Definitions

    • To be determined.

2.2.1 Definitions of All Terms, Including Acronyms, Used in the Project

    • To be determined.

2.2.2 Data Dictionary for Any Included Models

    • To be determined.

2.3 Relevant Facts and Assumptions

2.3.1 Facts

    • To be determined.

2.3.2 Assumptions

    • To be determined.

- 3 Functional Requirements

3.1 The Scope of the Work

3.1.1 The Current Situation

    • To be determined.

3.1.2 The Context of the Work

    • To be determined.

3.1.3 Work Partitioning

    • To be determined.

3.2 The Scope of the Product

3.2.1 Product Boundary

    • To be determined.

3.2.2 Product Use Case List

    • To be determined.

3.2.3 Individual Product Use Cases

    • To be determined.

3.3 Functional and Data Requirements

3.3.1 Functional Requirements

    • To be determined.

3.3.2 Data Requirements

    • To be determined.

- 4 Non-functional Requirements

4.1 Look and Feel Requirements

4.1.1 Appearance Requirements

    • To be determined.

4.1.2 Style Requirements

    • To be determined.

4.2 Usability and Humanity Requirements

4.2.1 Ease of Use

    • To be determined.

4.2.2 Personalization and Internationalization Requirements

    • To be determined.

4.2.3 Learning Requirements

    • To be determined.

4.2.4 Understandability and Politeness Requirements

    • To be determined.

4.2.5 Accessibility Requirements

    • To be determined.

4.3 Performance Requirements

4.3.1 Speed and Latency Requirements

    • To be determined.

4.3.2 Safety-Critical Requirements

    • To be determined.

4.3.3 Precision or Accuracy Requirements

    • To be determined.

4.3.4 Reliability and Availability Requirements

    • To be determined.

4.3.5 Robustness or Fault-Tolerance Requirements

    • To be determined.

4.3.6 Capacity Requirements

    • To be determined.

4.3.7 Scalability or Extensibility Requirements

    • To be determined.

4.3.8 Longevity Requirements

    • To be determined.

4.4 Operational and Environmental Requirements

4.4.1 Expected Physical Environment

    • To be determined.

4.4.2 Requirements for Interfacing with Adjacent Systems

    • To be determined.

4.4.3 Productization Requirements

    • To be determined.

4.4.4 Release Requirements

    • To be determined.

4.5 Maintainability and Support Requirements

4.5.1 Maintenance Requirements

    • To be determined.

4.5.2 Supportability Requirements

    • To be determined.

4.5.3 Adaptability Requirements

    • To be determined.

4.6 Security Requirements

    • To be determined

4.6.1 Access Requirements

    • To be determined.

4.6.2 Integrity Requirements

    • To be determined

4.6.3 Privacy Requirements

    • To be determined.

4.6.4 Audit Requirements

    • To be determined.

4.6.5 Immunity Requirements

    • To be determined.

4.7 Cultural and Political Requirements

    • To be determined.

4.7.1 Cultural Requirements

    • To be determined.

4.7.2 Political Requirements

    • To be determined.

4.8 Legal Requirements

4.8.1 Compliance Requirements

    • To be determined

4.8.2 Standards Requirements

    • To be determined.

- 5 Project Issues

5.1 Open Issues

    • To be determined

5.2 Off-the-Shelf Solutions

    • To be determined

5.2.1 Ready-Made Products

    • To be determined.

5.2.2 Reusable Components

    • To be determined.

5.2.3 Products That Can Be Copied

    • To be determined.

5.3 New Problems

5.3.1 Effects on the Current Environment

    • To be determined

5.3.2 Effects on the Installed Systems

    • To be determined

5.3.3 Potential User Problems

    • To be determined

5.3.4 Limitations in the Anticipated Implementation Environment That May Inhibit the New Product

    • To be determined.

5.3.5 Follow-Up Problems

    • To be determined.

5.4 Tasks

    • To be determined.

5.4.1 Project Planning

    • To be determined.

5.4.2 Planning of the Development Phases

    • To be determined

5.5 Migration to the New Product

    • To be determined

5.5.1 Requirements for Migration to the New Product

    • To be determined.

5.5.2 Data That Has to be Modified or Translated for the New System

    • To be determined.

5.5.3 Upgrade Tools and Procedures

    • To be determined

5.6 Risks

    • To be determined

5.7 Costs

    • To be determined

5.8 User Documentation and Training

    • To be determined

5.8.1 User Documentation Requirements

    • To be determined.

5.8.2 Training Requirements

    • To be determined.

5.9 Waiting Room

    • To be determined

5.10 Ideas for Solutions

    • To be determined
  • No labels