Functional Requirements Documentation

Functional requirements documentation

Creation of functional (business) requirements documentation (FRD) is beyond of scope of this guide. Documentation format and contents are different for every project or author. OriginTrail does not require any specific format or methodology for this issue as it will not be in direct contact with it.

The functional requirements document (FRD) is a formal statement of an application's (in our case implementation project) functional requirements. It serves the same purpose as a contract. The developers agree to provide the capabilities specified. The client agrees to find the product satisfactory if it provides the capabilities specified in the FRD.

FRD document can also be created in several iterations where each iteration should be confirmed by affected shareholders.

Main goals of FRD:

• Create detailed description of project, project goals, use cases etc.
• Define and make consensus what should be done by each stakeholder for project success on their common language.
• Establish mutual understanding of DC and SP (or more of them) of goals, requirements and project success metrics.

Please keep in mind that FRD document is aimed towards mutual understanding of DC and SP. This document should be primary source for final solution architecture. All technical and development specific details regarding implementation that cannot be useful or understandable for DC should be part of the separate technical document that is aimed for another audience. Also, some SP will perform consulting part of the project, while other SP can perform technical development.

FRD document is the final deliverable of the consulting part of the project and main foundation for the next stages.