Deliverable Name | Translations | ![]() |
||||||||||||||
Requirements Specification |
|
|||||||||||||||
Keywords | ||||||||||||||||
System's content and functionality. | ||||||||||||||||
Description | ||||||||||||||||
The Requirements Specification shall make sure that the client and Framfab agree on what product is to be delivered. The Requirements Specification shall make sure that the client and Framfab can state that a product has been delivered according to the specification. Together with the Project Definition and Project Manual, the Requirements Specification forms a solid contractual base for the project's next steps. The Requirements Specification is the basic information for design and development, and is therefore a reference document for the whole project team. The requirements are a description of what shall be done, so the system can meet the need of the client. How the requirements will be implemented is described in the deliverables from the Elaboration phase. It is important that the requirements are documented to make sure that it is possible to state if the client has recieved what he/she aksed for and has paid for. Requirements can be of different categories. Communicative requirements are defined using 1. Functional requirements.
2. Non-functional requirements. a. Facility requirements: How does the user want to use the system, e.g. available 24 hours a day. Seven days a week. Amount of data. Where will the system be hosted and maintained. b. Scalability requirements: The system shall be implemented in different countries; the system shall be prepared for future services and functions. The system shall be integrated in the future with other systems. c. Integration requirements: Shall the system load data from or send data to another system? Shall the system run on a given platform? d. Security requirements Describe the requirements regarding access and availability. f. Data & Information requirements E.g. which information shall be present from the system? Which information is to be stored? Which information is necessary to give to the system? Of what use is the information? |
||||||||||||||||
Approval | ||||||||||||||||
The Client and the Steering Committee shall approve the Requirements Specification. |
Recommended Storage | Timing | Responsibility | ||
\<Client>\<Project>\Definition\ |
Definition Elaboration |
Project Business Development | ||
Templates | Important input from | Important input to | ||
|
The Client |
Project Description
![]() Functional Specification ![]() Project Plan ![]() MS Project Plan ![]() |