1 / 14

INFO4

INFO4. Coursework. Design and planning for implementation. Deadline: 20 th December 2013. REMEMBER. The marks for Background and analysis lock down on 20 th Dec and are sent to the board. After this date changes can be made to these sections but the marks CANNOT.

bridie
Download Presentation

INFO4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. INFO4 Coursework

  2. Design and planning for implementation Deadline: 20th December 2013

  3. REMEMBER • The marks for Background and analysis lock down on 20th Dec and are sent to the board. After this date changes can be made to these sections but the marks CANNOT

  4. Design and planning for implementation • Alternative design solutions • There will never be one way in which the solution can be created, there will be different software solutions, different ways of doing this. Check the client requirements. These all need producing and then the final decision justifying • Consider the different logical approaches to solving the problem • All designs should be implementation free

  5. Design and planning for implementation • Design work • Having come up with a design for the problem now you need to produce draft designs which you then take to your client for approval • Once approval has been given final designs need to be produced • Remember a good design is one that can be given to someone else and they can produce what you had in mind

  6. Alternative design solutions • Investigate alternative designs • Think about different ways of solving the problem not just different software • Remember it is a solution design then a detailed design • Each must be considered and evaluated objectively in relation to the client’s requirements

  7. Requirement-to market a wider audience • Sarah says she wants to increase the market for her specialist sausage business • Possibilities • Website: static or dynamic • local papers of magazines • TV/radio • Advertising channels • Tweets • Blogs • Social networking sites • SMS messages • Apps

  8. Design tips • Designs should be produced which can be discussed/shown to a client • Should e for what the solution must do/produce and NOT for how it will be built • Should concentrate of designs for agreed deliverables • Must be discussed with and approved by the client BEFORE proceeding • Designs should be prototypes

  9. Design and planning for implementation • Plan for implementation, testing and installation • Produce a Gantt chart for this

  10. Design and planning for implementation • Training requirements • Taking on board the user skills that you wrote about previously and the designs explain what training is needed and how it is to be carried out • There will be different types of training for different users • Relate to INFO3 work on training • Also link to support work in INFO3

  11. Design and planning for implementation • Testing strategy and test plan • Explain how you are going to test the system

  12. Design and planning for implementation • A plan for: • Implementing • Testing • Installing/introducing the solution • Any training • Has been produced which includes expected durations as well as deadlines. How the plan meets the client’s requirements and the needs of the user is explained.

  13. Testing strategies • A strategy for planned testing of the effectiveness of the implemented system that has been justified • When testing in the intended environment is not possible, testing in a simulated environment will be acceptable providing that it has been explained and justified in the testing strategy • Testing should concentrate on the testing of complete processes and the system as a whole. Evidence of functional or unit tests, for example for validation or for backing up of one file is NOT required.

  14. Where to next? Client requirements Proposed system including deliverables, impacts and benefits Evaluation Criteria Quantitative Qualitative Testing

More Related