Upload
gpiper
View
776
Download
1
Embed Size (px)
DESCRIPTION
Citation preview
Coursework Guidance
Info 4
Mark allocation in GREY
Testing & Documentation of the Implementation (13)
• Evidence of Testing (3)
• Evidence of Developer and User Testing (3)
• User DocumentationFull system help guide (3)
Maintenance & Further Development (2)
User agreement of user docs (2)
Evidence of Testing
This is where the testing planned in the previous section is carried out. All tests need to be carried out and evidenced with any corrective action justified.
Evidence of Testing
1. Evidence that some testing of implementation has been carried out.
2. Testing of processes in the implementation has been carried out.
3. Evidence that the whole solution has been tested.
Evidence of Developer and User Testing
There must be evidence of both the student and the end user / client testing the system. This shows you are including the user at all stages which is vital to ensure the system meets the requirements set out at the beginning.
Evidence of Developer and User Testing
1. Testing of the implantation has been completed but the candidate only.
2. Testing of the implementation has involved the candidate and the client.
3. The candidate has shown clear evidence that the testing has involved both the client and potential users of the solution.
User Documentation Full system help guide
Comprehensive documentation of the solution. Must be an easily accessible guide to a range of users.
How to install it.How to use it.How to back up.FAQs etc
User Documentation Full system help guide
1. Some documentation of the implemented solution has been provided.
2. Comprehensive documentation of the implemented solution has been provided.
3. Comprehensive documentation of the implemented solution has been provided that is appropriate for the project.
Maintenance & Further Development
• How is the system maintained?Steps for managing the system. Checking
back ups are successful etc.
• In what ways could the system be developed in the future?Extensions to the system
New modules that will add to the system
Maintenance & Further Development
1. Documentation has been provide that partly describes the implemented solution.
2. Comprehensive documentation of the solution has been provided that would allow the implemented solution to be used / maintained or developed further.
User agreement of user docs
Client feedback about the user docs. Is it suitable for the system and for all users? Does it provide suitable support to new users?
User agreement of user docs
1. Documentation is understandable by the candidate.
2. Documentation is appropriate for the identified client / users