0% found this document useful (0 votes)
36 views2 pages

Artefact TOR

This requirements specification document provides an overview of a project to develop a product for a client. It outlines that the final deliverable will be a single system that meets all of the client's requirements. These requirements are presented in chronological order and indicate which phase each one belongs to. The document also defines constraints such as limitations on resources and standards. It specifies the resources available for the project including personnel and equipment. An evaluation plan is described to assess the delivered product. The sponsor is asked to sign off to confirm acceptance of the project scope.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views2 pages

Artefact TOR

This requirements specification document provides an overview of a project to develop a product for a client. It outlines that the final deliverable will be a single system that meets all of the client's requirements. These requirements are presented in chronological order and indicate which phase each one belongs to. The document also defines constraints such as limitations on resources and standards. It specifies the resources available for the project including personnel and equipment. An evaluation plan is described to assess the delivered product. The sponsor is asked to sign off to confirm acceptance of the project scope.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Artefact Title

Student Name (Student Id)


BSc Title
Requirements Specification Document

Overview
Guidance: provide background to the company and a brief overview of the work.

Product to be delivered to client


Guidance: this should specify the final deliverable which is to be produced for the client. This SINGLE
statement should encompass all requirements for the system.

Client requirements
Guidance: this outlines the list of the clients requirements in terms of product features required, and
delivery mechanisms if appropriate. Future requirements to be implement in future phases should be
listed (the “wish list”). Each requirement should be presented in chronological order. The phase to
which each requirement belongs should be shown in some way.

Constraints
Guidance These define the boundaries of the work for this specific project and typically include: Any
limitations should be described. Any limitations on access to specific resources, budget, the research
topic and standards should be included.

Resources
Guidance: These define the access and assets that will provided by the client, or available via the
university, for use during the project and typically include: the number of people who will be involved
in the project, their skills, possibly naming individual, Specific equipment, services.

Evaluation
Guidance: In this section the proposed evaluation of the artefact is outlined including the aim of the
evaluation and how the evaluation will be carried out

Sponsor Sign-off
Guidance: The sponsor is asked to sign and date the first part of the ToR. This confirms acceptance of
its content as a contract to be worked to by the student. The sponsor should not sign-off on this until
they are satisfied with the content. The sponsor is asked to focus on the practical aspects of the project
and the deliverable that is to be produced for them.

Signature (this indicates acceptance of the scope of the Date


practical component of the project)

You might also like