|
|
TICK |
| Purpose: |
To provide reference documentation for the long-term maintenance
of an application |
|
|
|
|
| Prepared
By:
|
Project Manager -
Analyst - |
|
|
|
|
| Contents: |
(including references to other documents) |
|
|
Systems overview |
_______ |
|
Problem solving definition |
_______ |
|
Feasibility study report |
_______ |
|
Statement of User Requirements |
_______ |
|
Solution model |
_______ |
|
System documentation |
_______ |
|
Testing strategy (including transactions types, processes
tested, data samples and test results) |
_______
|
|
Configuration manual |
_______ |
|
Change control documents |
_______ |
|
Current list of outstanding problems |
_______ |
|
Current list of outstanding requested changes |
_______ |
|
|
|
| Derivation: |
System |
|
|
System definition |
|
|
Bespoke sub-system documentation |
|
|
System files |
|
|
Development files |
|
|
Testing files |
|
|
|
|
| Target
Audience: |
Application support team |
|
|
|
|
| Quality
Criteria: |
Is the documentation clearly identified, indexed and its
location known? |
_______
|
|
Are all outstanding problems and change requests clearly
defined and documented? |
__Y/N_____
|
|
Is the documentation complete? |
__Y/N_____ |
|
|
|
| Review: |
Check all project activities are complete and properly
signed |
_______ |
|
Check that delivered system fulfils user and functional
specifications |
_______
|
|
Check that the technical aspects of the system perform
properly |
_______ |
|
Check costs and timescales against budget |
_______ |
|
Measure the benefits |
_______ |
|
Collate the learned lessons for the future |
_______ |
|
|
|
|
|
|
