Making a great Project 2 OCR 1994/2360

Implementation This is about how you make your system. It should have enough detail for a competent user to be able to recreate you system – but no more! Keep it in proportion – this section is worth 23% or the marks, so should not be more than a quarter of your project!

Implementation Make use of screenshots to illustrate your work, but crop them or resize them. On their own they will not be enough, so add some description. Remember you are addressing a competent computer user – they should be able to at least open the software without you having to tell them how!

Implementation This section is a record of what YOU have done, so write it in the first person (eg I set up these data fields... Etc)

Implementation 1 – data structure Refer to your design and set up the fields, data types, lengths and validations you planned. Illustrate this with some screenshots and comments on why you used particular features of the software.

Implementation 1 – data structure For more than two marks, you must make at least two changes to the data structure you designed. These must be sensible changes for a good reason. For full marks you need to say why you had to make the changes.

Implementation 2 – input and output formats Refer to your design and set up the input forms you planned. Illustrate this with some screenshots and comments on why you used particular features of the software.

Implementation 2 – input and output formats Refer to your design and set up the output reports you planned. Usually you will need to create queries to make the reports from. Using parameter queries means you can use the same query to find different things. Illustrate this with some screenshots and comments on why you used particular features of the software.

Implementation 2 – input and output formats If you have planned to transfer data into mailmerged letters or labels, you need to create the letter designs here. Illustrate this with some screenshots and comments on why you used particular features of the software.

Implementation 2 – input and output formats If you have planned a switchboard or main user screen, now is the time to create it. Forms and reports can be linked using action buttons (remember queries should only be seen through their reports or forms). Letters for mailmerges can be linked using hyperlinks. When the form is complete, set it to open automatically on startup.

Implementation 2 – input and output formats For more than two marks, you must make at least two changes to the input screens and output reports or letters you designed. These must be sensible changes for a good reason. For full marks you need to say why you had to make the changes.

Implementation 3 – use software features For up to 3 marks, you don’t have to do anything extra. You just need to make sure there is some evidence that you have used at least three features of one application, eg the database, and three features of another, eg the spreadsheet or wordprocessor. BUT for full marks you must say why you have used each feature.

Implementation 4 – combine software features To get a mark for this, data must be transferred automatically from one application to another. Copy & paste does not count! You could mailmerge data from a query into a letter, or analyse a database table in a spreadsheet to create a graph

Implementation 4 – combine software features To get a second mark for this, data must be transferred automatically from one application to another for a different purpose! You could mailmerge data from a query to create mailing labels, or from a different query into a different type of letter.

Implementation complete… That’s it! You should now have created your solution to the problem and written up how you did it. Your next step will be to test your system.