Deliverable Name | Translations | ![]() |
||||||||||||||
Technical Brief |
|
|||||||||||||||
Keywords | ||||||||||||||||
Technical dependencies and constraints. | ||||||||||||||||
Description | ||||||||||||||||
The Technical Brief is derived from the Technical Strategy, if existent. It describes existing systems that are of importance to the project (architecture, integration possibilties, future plans, etc.) as well as technical aspects of on-going or planned projects that are relevant to this project. The Communicative Brief, Technical Brief and Client Description can be described in the same document to help all project members to understand the most basic input to the project. |
||||||||||||||||
Approval | ||||||||||||||||
The Client Project Team approves the Technical Brief. |
Recommended Storage | Timing | Responsibility | ||
\<Client>\<Project>\Definition\ | Definition | |||
Templates | Important input from | Important input to | ||
|