1 / 14

Design and Planning for Implementation

Design and Planning for Implementation. Section 3 – INFO 4. Specification. Evidence of investigating alternative d esign solutions Amplification : should include investigating options to all elements of an ICT system as appropriate to the project

akamu
Download Presentation

Design and Planning for Implementation

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. Design and Planning for Implementation Section 3 – INFO 4

  2. Specification • Evidence of investigating alternative design solutions • Amplification: should include investigating options to all elements of an ICT system as appropriate to the project • Draft design work: to be able to discuss with client • Final design work: From which to implement • Plan for implementation, testing and instalment, including proposed timescales • Training requirements for the new system: This may include the documentation required to train the users • Testing strategy: Should set out what testing is necessary, who will do it, when and where. You should describe here any constraints on live testing the requires a simulated environment to be used • Test Plan: The tests that will be undertaken, what the tests are testing, the order in which the tests will be completed.

  3. What do I need to design? • User Interface – Menus and navigation considered to make the solution user friendly. How will the user access the forms/features? • Error Messages • Inputs – lists of inputs and stored data needed to accomplish objectives • Processes – A list of what happens to the inputs to turn them to outputs • Outputs – a list of reports or other outputs your system should produce • Testing • Structure of solution • Procedures to use the solution

  4. Justification for the chosen solution • Give reasons why you have chosen one design over another design • A list of the advantages and disadvantages for each design is essential • Always check with your client

  5. Hardware Requirements • Describe the minimum hardware requirements for the new system, including any peripherals

  6. Project Plan • More detailed plan than the one done in the analysis section • Prepare a plan, list and prioritise how you will complete the project (including the start and end dates) • Describe the sub-tasks that needs to be completed and include a Gantt chart or something similar • Include the training and installation of the system

  7. Testing strategy and plan • Designed to ensure that your solution does what it is supposed to do • Think about how you are going to test the system • Draw up a testing plan that shows that you have carefully chosen your test data and tested each module thoroughly • Test plan must be comprehensive and devised so that it tests your client’s requirements • It should include the testing of the system as a whole and the users’ test of the system

  8. Test Strategy • It’s a plan of the testing for your solution • You have to describe what you are going to test, the order of testing , the type of test that you are going to use and what data you need to enter before testing can take place • The testing should match the requirements specification i.e. It does what it is meant to do

  9. Different types of testing • Unit testing • Integration testing • System testing – testing data right through the system going through every path e.g. In the client’s environment • User Testing: Get client to test the system and then using a questionnaire with comments about the solution • At the end of the design process, you should go back to the client and see whether what you have produced matches their requirements

  10. Test Plan • Should contain detailed plan of every test that you intend to carry out • You should include inputs, processes and outputs

  11. Summary • Use easy navigation so that your design is usable in client’s environment • Hide the complexities of the software • Your finished design may not be the final design as client may change their mind which then means you have to change your design • All changes must be noted, redrawn and justified • All designs must be clear to read and understand so that someone else could take your designs and easily produce your solution

  12. Summary: What do I need for design and Planning for Implementation • Evidence of investigating alternative solutions: Could involve different types of software that could be used to produce the solution or alternative approaches • Draft design work: Accurate designs need to be drawn up and fully annotated to show the client/user how the system will look • Final design work: the developer should meet the client and discuss the designs and changes made to meet the requirements of the client • Developer should then create the final, detailed designs for the solution

  13. Summary: What do I need for design and Planning for Implementation • Plan for implementation, testing and installation, including proposed timescales: the final version of the project plan, showing how the solution is going to be implemented, tested and installed. A Gantt chart or some other timescale device should be used at this point to show the timetable for completion discussed with the client • Training requirement for the new system: Should include planning for the training and would include any documentation that you will be creating for the training and the user

  14. Summary: What do I need for design and Planning for Implementation • Testing Strategy: Laid out in a logical order, stating who will be involved in the particular stages. A broad description of what is being tested, as well as how it is to be tested. • Testing plan: This would include the tests that have to be carried out, what is being tested and the order in which they are to be tested.

More Related