Referenced/Related documents

The functional specification should be referenced for confirmation on any functional (& non-functional) behaviour required for [project title].

In addition to this, the following optional documents/assets should be read in conjunction with document (assuming they have been produced and are available);

• Technical specification; details all the configuration, security, data, 3^rd party integration requirements (e.g. APIs, data feeds etc…) and architecture required in order to fulfil the functional requirements detailed in this functional specification.
• Project Proposal; a very high level overview or summary of the request for [project title] including reasons for the project, high level scope, timescales, budget, estimates and alternative options
• Business Case; similar to the project proposal, the business case builds upon and expands on information provided in the project proposal, including information such as expected benefits, high level plan for change, project risks & dependencies etc…

Any other documentation supplied or produced during requirements gathering for the project whilst may be useful information from a functional perspective, does not form part of the formal agreed/signed off documentation, and hence should only be used as supplementary information in addition to the documents/assets listed above.