SlideShare a Scribd company logo
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 Documentation Full 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 Evidence that some testing of implementation has been carried out. Testing of processes in the implementation has been carried out. 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 Testing of the implantation has been completed but the candidate only. Testing of the implementation has involved the candidate and the client. 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 Some documentation of the implemented solution has been provided. Comprehensive documentation of the implemented solution has been provided. 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 Documentation has been provide that partly describes the implemented solution. 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 Documentation is understandable by the candidate. Documentation is appropriate for the identified client / users

More Related Content

PPT
2 Analysis & Deliverables
PPT
5 evaluation of the implemented solution
PPT
Requirement Management 1
PPT
5 evaluation of the implemented solution
PPT
Requirement Management 2
PPT
Software measurement lecture 7
PPT
The role of the quality group in software development lecture 4
PPTX
Crud and jad
2 Analysis & Deliverables
5 evaluation of the implemented solution
Requirement Management 1
5 evaluation of the implemented solution
Requirement Management 2
Software measurement lecture 7
The role of the quality group in software development lecture 4
Crud and jad

What's hot (17)

PDF
Test case format
PPTX
Acceptance testing
PPTX
Requirements validation - requirements engineering
PDF
Case study on Banking Software Testing - FINACLE : UAT
PPTX
An Overview of User Acceptance Testing (UAT)
PPT
Requirement Management 3
PPTX
Software engineering
PPTX
Building a software testing environment
PPT
Product Design & Development
PPTX
Defining software testing
DOCX
Mit104 software engineering
PPTX
SYSTEM DEVELOPMENT LIFE CYCLE
PPT
Lecture 10 understanding requirements (2)
PPTX
Requirements engineering@mahmud@
PDF
Software Testing : Quality Assurance (QA) v/s Quality Control (QC) : Definiti...
PPTX
Software Product Line
PPTX
Problems and challenges related to qa outsourcing
Test case format
Acceptance testing
Requirements validation - requirements engineering
Case study on Banking Software Testing - FINACLE : UAT
An Overview of User Acceptance Testing (UAT)
Requirement Management 3
Software engineering
Building a software testing environment
Product Design & Development
Defining software testing
Mit104 software engineering
SYSTEM DEVELOPMENT LIFE CYCLE
Lecture 10 understanding requirements (2)
Requirements engineering@mahmud@
Software Testing : Quality Assurance (QA) v/s Quality Control (QC) : Definiti...
Software Product Line
Problems and challenges related to qa outsourcing
Ad

Viewers also liked (9)

PPT
It4 Coursework Help
PPTX
CPD Presentation
PPT
parent revision guide
PPTX
1.10 evaluation
PPTX
AS ICT INFO 1 - AQA Examination Revision
PPTX
AQA AS ICT INFO2 Revision
PPTX
AQA INFO 1 – Sample Work Requirements
PPTX
2.1 ict systems and components
PPT
AQA AS ICT INFO1 Revision
It4 Coursework Help
CPD Presentation
parent revision guide
1.10 evaluation
AS ICT INFO 1 - AQA Examination Revision
AQA AS ICT INFO2 Revision
AQA INFO 1 – Sample Work Requirements
2.1 ict systems and components
AQA AS ICT INFO1 Revision
Ad

Similar to 4 testing & documentation of the implementation (20)

PPTX
Hi600 ch12_text_slides
PPTX
3.8 development methods
PPT
Requirements
PPT
Systems Life Cycle
PPT
Chapter 10
PPTX
Document Control in FDA Regulated Environments - When and how to automate
DOCX
CHAPTER 11 ManagingSystemsImplementationChapter 11 describ.docx
PPTX
Paripoorna concept to deployment v 1.0
PPT
Cmmi adptando cmmi a proyectos pequeños weinberg[1]
PPT
The information systems life cycle
PPT
Software design methodologies
PPS
Sanjeevi's SDLC Guest Lecture in Anna University campus at AU-PERS Centre (Ye...
PPT
Unit-1 object oriented systems(OOSD) .ppt
PPTX
Adv prod tools assgn5
PPTX
Requirements engineering
DOC
Manual Testing Notes
PPT
Software Production Layout_Se lect7 btech
DOC
Complete guide to manual testing@uma
DOC
Complete testing@uma
DOC
Manual testing
Hi600 ch12_text_slides
3.8 development methods
Requirements
Systems Life Cycle
Chapter 10
Document Control in FDA Regulated Environments - When and how to automate
CHAPTER 11 ManagingSystemsImplementationChapter 11 describ.docx
Paripoorna concept to deployment v 1.0
Cmmi adptando cmmi a proyectos pequeños weinberg[1]
The information systems life cycle
Software design methodologies
Sanjeevi's SDLC Guest Lecture in Anna University campus at AU-PERS Centre (Ye...
Unit-1 object oriented systems(OOSD) .ppt
Adv prod tools assgn5
Requirements engineering
Manual Testing Notes
Software Production Layout_Se lect7 btech
Complete guide to manual testing@uma
Complete testing@uma
Manual testing

Recently uploaded (20)

PPTX
Final Presentation General Medicine 03-08-2024.pptx
PPTX
Microbial diseases, their pathogenesis and prophylaxis
PDF
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
PDF
102 student loan defaulters named and shamed – Is someone you know on the list?
PPTX
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
PPTX
Institutional Correction lecture only . . .
PPTX
Introduction-to-Literarature-and-Literary-Studies-week-Prelim-coverage.pptx
PDF
STATICS OF THE RIGID BODIES Hibbelers.pdf
PDF
2.FourierTransform-ShortQuestionswithAnswers.pdf
PDF
Computing-Curriculum for Schools in Ghana
PPTX
Lesson notes of climatology university.
PPTX
Cell Structure & Organelles in detailed.
PDF
O7-L3 Supply Chain Operations - ICLT Program
PPTX
Tissue processing ( HISTOPATHOLOGICAL TECHNIQUE
PDF
Chinmaya Tiranga quiz Grand Finale.pdf
PDF
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
PPTX
master seminar digital applications in india
PPTX
Presentation on HIE in infants and its manifestations
PPTX
human mycosis Human fungal infections are called human mycosis..pptx
PPTX
Pharma ospi slides which help in ospi learning
Final Presentation General Medicine 03-08-2024.pptx
Microbial diseases, their pathogenesis and prophylaxis
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
102 student loan defaulters named and shamed – Is someone you know on the list?
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
Institutional Correction lecture only . . .
Introduction-to-Literarature-and-Literary-Studies-week-Prelim-coverage.pptx
STATICS OF THE RIGID BODIES Hibbelers.pdf
2.FourierTransform-ShortQuestionswithAnswers.pdf
Computing-Curriculum for Schools in Ghana
Lesson notes of climatology university.
Cell Structure & Organelles in detailed.
O7-L3 Supply Chain Operations - ICLT Program
Tissue processing ( HISTOPATHOLOGICAL TECHNIQUE
Chinmaya Tiranga quiz Grand Finale.pdf
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
master seminar digital applications in india
Presentation on HIE in infants and its manifestations
human mycosis Human fungal infections are called human mycosis..pptx
Pharma ospi slides which help in ospi learning

4 testing & documentation of the implementation

  • 1. Coursework Guidance Info 4 Mark allocation in GREY
  • 2. Testing & Documentation of the Implementation (13) Evidence of Testing (3) Evidence of Developer and User Testing (3) User Documentation Full system help guide (3) Maintenance & Further Development (2) User agreement of user docs (2)
  • 3. 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.
  • 4. Evidence of Testing Evidence that some testing of implementation has been carried out. Testing of processes in the implementation has been carried out. Evidence that the whole solution has been tested.
  • 5. 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.
  • 6. Evidence of Developer and User Testing Testing of the implantation has been completed but the candidate only. Testing of the implementation has involved the candidate and the client. The candidate has shown clear evidence that the testing has involved both the client and potential users of the solution.
  • 7. 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
  • 8. User Documentation Full system help guide Some documentation of the implemented solution has been provided. Comprehensive documentation of the implemented solution has been provided. Comprehensive documentation of the implemented solution has been provided that is appropriate for the project.
  • 9. 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
  • 10. Maintenance & Further Development Documentation has been provide that partly describes the implemented solution. Comprehensive documentation of the solution has been provided that would allow the implemented solution to be used / maintained or developed further.
  • 11. 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?
  • 12. User agreement of user docs Documentation is understandable by the candidate. Documentation is appropriate for the identified client / users