Foundation Degree IT Project Milestone 3: Implementation, Testing and Evaluation
Objectives Richard Hancock2 Have an awareness of what to document during implementation Be aware of what content could be included in a test plan Be aware of what content can be included in the project evaluation *** 11/09/2015
Implementation Richard Hancock3 Description of how the solution is realised Selection of implementation method should be described and justified – essentially describe what the step by step activities you performed are to bring about the system you designed Discussion of technology used and how this was applied You may have discussed the technology in MS2, so spend more time here describing how it was used, not why it was used Reference design considerations and discuss how particular technologies/software were used to implement these features How design was converted to a working system You may have changed things as you implement your system from the design, so describe those changes and why the changes were made This needs to relate well to MS2, so make sure you reference particular instances in MS2 that have changed 11/09/2015
Implementation Richard Hancock4 Discussion of what was successfully implemented and what was not, and any key features of a challenging nature that involved more work than originally anticipated This is a good area to sing your praises if you found something particularly difficult in your project to do, that was perhaps beyond your skill to complete, but you got it working anyway That which has been successful should relate to the system objectives and system requirements defined in MS2 System documentation User manual Administrator information Technical support Annotated screen shots Comments in any code 11/09/2015
Testing Richard Hancock5 Testing should address the evaluation of the solution against its objectives and success criteria Think about how you are going to test your implementation Describe the testing strategy and choice of testing method Include planning and application of the tests You must design your tests and then apply the tests and document the results Draw conclusions from the results and any modifications to the design and implementation that may be recommended If you decide that in another version of your implementation changes need to be made as a result of your testing then describe what needs to be changed and why 11/09/2015
Evaluation Richard Hancock6 Evaluation deals with success of project in academic terms, compared to the success criteria for the solution Evaluate the degree of success in carrying out the project Exactly how successful has the project been at solving the initial objectives or requirements; or was it a total disaster? What you have learned by doing the project Time management skills Organisational skills Skills in the use of technology Research skills Writing skills Presentation skills 11/09/2015
Evaluation Richard Hancock7 Things you would do differently if project were to be repeated and any extra features you would recommend Look back at your testing and sum up any changes that would be necessary based upon the testing results Value of the learning process to you and the extent to which the project has added to the students professional and academic expertise Talk about the skills you have developed and how you intend to put them to use in your professional life and future career planning Gantt chart reflection - the actual time plan compared to the original time plan Did you stick to plan? If not, why, and how did you keep on target. Or didn’t you? Use your original Gantt charts (MS2) and compare these with updated ones in MS3 11/09/2015
Summary Richard Hancock8 Document your implementation as you carry it out using notes Make sure you make references to the design as you implement the system and document it As you implement something, test it and document the results Evaluate the whole project experience, not just a part of it Be realistic about your performance *** 11/09/2015
Richard Hancock9 End! 11/09/2015