Information Technology Reference
In-Depth Information
Project Documentation
Acceptance
Budget
Test Cases
Functional Specifications
Technical Specifications
Planning
Protocols
Directives
Status Reports
System Configuration
Fig. 4.1 Documentation structure
Additionally a documentation structure should be created to record project pro-
gress. An example structure is presented in Fig.
4.1
.
In any case it should cover the following key aspects to be taken into account,
depending on the type of project:
• Acceptance directive
• Other directives
• Schedule
• Functional specifications
• Technical specifications
• Test scripts
• System configuration
• Budget
• Protocols
• Status reports
• Acceptance results.
The main directory again is broken up into sub-structures as shown in the
example of Fig.
4.2
for different applications:
4.2.2.1 Technical Specification Phase
Special emphasis should be placed on the technical specification phase. Some
schools call technical specifications also business blueprints although the meaning
is not quite identical. We will not discuss these differences here. As already
