Embedded Files
Post Prototype Refinement of Design - 5 marks
Post Prototype Refinement of Design - 5 marks
What does it need to contain?
What does it need to contain?
Take note of the highlighted KEY words
The overall purpose of this document is to obtain feedback from competent third parties. Once you have feedback on your prototype, you will refine your designs (user interface, data dictionary, Entity Relationship Diagram, pseudocode) in this document, before continuing to develop the rest of your project.
If you produced a good original design, then your post prototype review will be brief. It should focus on any extra stuff identified which was not in your original design, OR the removal of some functionality, if your original scope was too big, OR changes to the original design as outlined above.
DO NOT change your Design document, any changes must be documented here.
Lastly, remember you are not changing anything in your VB prototype solution from this point on. Make a copy of your prototype solution, put it in your Software Development folder and continue working on this new version, after you have completed this section. The prototype solution remains unaltered and is sent to the examiner along with your final solution.
- Prototype Feedback Form
Purpose - To collect feedback from a competent third party (your CS teacher, your main user).
Create a table or feedback form with the following headings:
Usability (how easy the system is to use)
Navigation between forms
Intuitiveness (can the user work out what to do without any help?)
Help (messages, layout, headings)
Functionality (does the system do what was expected?)
Data Storage (do your textfiles store data in line with your Data Dictionary?)
Other feedback (anything else the third party comments on)
Note: You will now show your working prototype to your teacher, who will give you constructive feedback under the headings above. Type up the feedback to complete the section above.
2. Feedback Evaluation
2. Feedback Evaluation
Purpose - To describe how each piece of feedback will affect the design of the system.
Take each piece of feedback and consider how the following aspects my be affected.
Input and Output – Existing and Additional (if needed)
If any inputs & outputs have changed, or new ones are needed, you need to show your new/amended user interface designs here.Additional Data Items (or removal)
If any additional data items are necessary, you need to show your amended data dictionaries here (full tables please).Data Structure Changes
If you need NEW additional tables in your Data Dictionary Designs, you need to show them here.Additional Processes
If you have identified any new or amended processes, you need to include new and amended pseudocode here.Consideration of feedback not being taken forward to final solution
If any feedback is not going to be used to modify the design, then you must make it clear why it is being ignored.
IF you need to make changes, make sure you justify them (i.e you need to write about them too), as well as showing how these design elements have changed.
FINALLY, REMEMBER in your Prototype Evaluation (in Prototype section), you were asked to identify some of your own ideas for improvement? See last bullet below:
You now need to add your own suggestions for improvement/changes to your Feedback Evaluation above and redesign your changes.
Page updated
Report abuse