Excel templates

Functional requirements document template Excel


Télécharger Functional requirements document template Excel

★★★★★★★★★★3.5 étoiles sur 5 basé sur 1 votes.
Votez ce document:

Télécharger aussi :


Functional requirements document template Excel

This article provides details of functional requirements document template Excel that you can download now.

Microsoft Excel software under a Windows environment is required to use this template

These functional requirements document template Excel work on all versions of Excel since 2007.

Examples of a ready-to-use spreadsheet: Download this table in Excel (.xls) format, and complete it with your specific information.

To be able to use these models correctly, you must first activate the macros at startup.

The file to download presents four templates Functional requirements document template Excel:

  • Excel template simple agile user story
  • Excel template website technical specification template
  • Requirements Matrix Template
  • Template requirements traceability Matrix

The requirements within this document are meant to be solution independent. They are intended to provide a statement of what the solution is to do and how well it should do it but not of how it will be implemented.



Approval of this document along with the associated Service Specification Overview (if provided) is taken as confirmation that our understanding of the requirements and business rules is correct.

Instructions:

The table (see Matrix Grid tab) identifies fields for:

  • “Unique Number” – Provide a unique identifier for each requirement to allow for tracing against project deliverables and testing activities. The naming convention can be as simple (1, 2, 3, etc.) or complex (e.g. multiple unique codes to identify the requirement by project, business unit, functional purpose, date added, SME assigned, etc.) as needed for your specific project. Documents that have more complex identifiers with unique coding should also include a legend for document reviewers.
  • “Description” – a brief description of the requirement sufficient for the reader and project team to understand its purpose and how it will impact the final functionality of the project/product.
  • “Requirement Origin” – name of the individual, role, organization, document etc. from which the requirement was originated. This will ensure that all the appropriate parties have been notified and consulted if a requirement needs to be better understood, revised and/or eliminated during the course of the project.
  • “Business Priority” – examples of categorization would be High, Medium and Low; or Critical, Must Have and Nice to Have; Mandatory, Standard, Custom, Unnecessary. A legend must be provided to assist the reader and maintain consistency throughout the project.
  • “Technical Priority” – examples of categorization would be High, Medium and Low; or Critical, Must Have and Nice to Have; or Complex, Moderate and Simple. A legend must be provided to assist the reader and maintain consistency throughout the project.
  • “Estimate (cost, time)” – Initial requirements identified could be designated as In Scope to show that they have been included in the original baselined activity schedule. As requirements are either added or deleted, it will become necessary to capture the cost and time associated with each in order to fully realize the impact on the project cost and schedule remaining.
  • “Phase, Release, Iteration” – Initial requirements should be identified as “in scope” or “out of scope” for project scheduling and costing. If the implementation will contain multiple phases or releases, requirements can further broken down into the appropriate work phase or release. This field can also be used to capture requirements that are identified during the course of the project for future enhancements and/or upgrades. By capturing the information in one document that is reviewed and confirmed throughout the project, all stakeholders will remain informed as to final project/product functionality.

Other fields can be added as needed for your specific project.





0