4 testing & documentation of the implementation

1,151 views

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,151
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

4 testing & documentation of the implementation

  1. 1. Coursework Guidance Info 4 Mark allocation in GREY
  2. 2. Testing & Documentation of the Implementation (13) <ul><li>Evidence of Testing (3) </li></ul><ul><li>Evidence of Developer and User Testing (3) </li></ul><ul><li>User Documentation </li></ul><ul><ul><li>Full system help guide (3) </li></ul></ul><ul><ul><li>Maintenance & Further Development (2) </li></ul></ul><ul><ul><li>User agreement of user docs (2) </li></ul></ul>
  3. 3. Evidence of Testing <ul><li>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. </li></ul>
  4. 4. Evidence of Testing <ul><li>Evidence that some testing of implementation has been carried out. </li></ul><ul><li>Testing of processes in the implementation has been carried out. </li></ul><ul><li>Evidence that the whole solution has been tested. </li></ul>
  5. 5. Evidence of Developer and User Testing <ul><li>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. </li></ul>
  6. 6. Evidence of Developer and User Testing <ul><li>Testing of the implantation has been completed but the candidate only. </li></ul><ul><li>Testing of the implementation has involved the candidate and the client. </li></ul><ul><li>The candidate has shown clear evidence that the testing has involved both the client and potential users of the solution. </li></ul>
  7. 7. User Documentation Full system help guide <ul><li>Comprehensive documentation of the solution. Must be an easily accessible guide to a range of users. </li></ul><ul><li>How to install it. </li></ul><ul><li>How to use it. </li></ul><ul><li>How to back up. </li></ul><ul><li>FAQs </li></ul><ul><li>etc </li></ul>
  8. 8. User Documentation Full system help guide <ul><li>Some documentation of the implemented solution has been provided. </li></ul><ul><li>Comprehensive documentation of the implemented solution has been provided. </li></ul><ul><li>Comprehensive documentation of the implemented solution has been provided that is appropriate for the project. </li></ul>
  9. 9. Maintenance & Further Development <ul><li>How is the system maintained? </li></ul><ul><ul><li>Steps for managing the system. Checking back ups are successful etc. </li></ul></ul><ul><li>In what ways could the system be developed in the future? </li></ul><ul><ul><li>Extensions to the system </li></ul></ul><ul><ul><li>New modules that will add to the system </li></ul></ul>
  10. 10. Maintenance & Further Development <ul><li>Documentation has been provide that partly describes the implemented solution. </li></ul><ul><li>Comprehensive documentation of the solution has been provided that would allow the implemented solution to be used / maintained or developed further. </li></ul>
  11. 11. User agreement of user docs <ul><li>Client feedback about the user docs. Is it suitable for the system and for all users? Does it provide suitable support to new users? </li></ul>
  12. 12. User agreement of user docs <ul><li>Documentation is understandable by the candidate. </li></ul><ul><li>Documentation is appropriate for the identified client / users </li></ul>

×