Deliverable Name | Translations | ![]() |
||||||||||||||
Functional Specification |
|
|||||||||||||||
Keywords | ||||||||||||||||
Actors, Use-Cases, Functionality, Use-Case Specification, Glossary | ||||||||||||||||
Description | ||||||||||||||||
The Functional Specification is a model of the system's intended functions and its environment, and it serves as a contract between the client and the developers. It comprises a set of all use-cases for the system, together with the set of all actors, so that all functionality of the system is covered. It's is first developed as a broad description of all the required functionality with a subset at a more detailed level. The person responsible for project technology together with the person responsible for usability decides which subset that initially needs to be detailed, since that subset is used to elaborate the system's architecture. By the end of Elaboration, the Functional Specification will be fully detailed. |
||||||||||||||||
Approval | ||||||||||||||||
The Client Project Team approves the Functional Specification. |
Recommended Storage | Timing | Responsibility | ||
\<Client>\<Project>\Elaboration\ | Elaboration |
|
||
Templates | Important input from | Important input to | ||
|