Database Coursework
Access Resources - Tutorials and other help
GCSE ICT - an excellent site, of great help to anyone tackling a GCSE ICT project
A Guide to Database projects from Thorpe St Andrew School
|
Project Ideas: Possible projects include: |
||||
| video library | garage | nursery | newsagent | milk round |
| hair dresser | farm | dentist | vet | stables |
| mail order business | accountant | pharmacist | music collection | tourist attractions |
| travel agent | coach hire business | driving school | social club | sports club |
| solicitor | dating agency | optician | builder | beauty salon |
| computer games | stock | restaurant | kennels | employees |
1. Identify (5 marks)
Explain your problem and name your end-user
Who are you creating this database for? What is that person's requirements? What data will you be using? What is the outputted information that you need to produce?
It is very important that you are as detailed as possible when it comes to describing your problem. Your user needs to list several specific requirements that will allow you to carry our an "extension task".
| Example:
My uncle Eric is the manager of a cheese shop. He is completely disorganised and he is always losing important files and scraps of paper. Auntie Ethel bought him a PC for Christmas and I would like to produce a database for him that will make his business more efficient. I have talked to Eric about the cheese shop and he has given me these requirements:
|
Say why you are going to use a computer to solve the problem. How will the computer be faster, more accurate, cheaper etc. when compared to the traditional manual method e.g. compare a database to a filing cabinet or card file system.
Instead of storing files in a database, you could use a "manual system" i.e. a card file or a filing cabinet. The problems with a manual system would be that only one person could look at a file, people would have to walk to the room where the filing cabinet is kept and it is much more difficult and slower to search or sort files in a filing cabinet.
The disadvantage of computerised databases are that they require training to use and to produce, they rely on electricity and there are security concerns about databases on networks (people can "hack" them).
List at least three "quantitative objectives". These must be objectives that can be measured.
Base these on your user's requirements. Make sure you set yourself measurable objectives.
2. Analyse (9 marks)
Explain the data collection, input and processing that will occur?
What will your data be?
Where will it come from? (What form of data collection will you use?)
How will your data be manipulated? (what fields, queries and reports will you create?)
What will your backup strategy be?
You explain how you will avoid losing your work. How often will you backup? What media will you backup to? How long will the backup take?
What will your security policy be?
You should say whether or not you will be affected by the Data Protection Act.
Will you enter real or fictitious data?
Will you need to password-protect the database?
How will you ensure that the end-user does not delete vital data?
What hardware and software will you use and why?
Hardware available to you includes a PC (computer, monitor, keyboard, mouse), a black laser printer, a colour laser printer, a colour inkjet printer, scanner, digital camera, the Internet. Software includes Word, Access, Excel, Internet Explorer, etc.
Say, in detail, why you have chosen the software you have selected. For example, why have you chosen Access instead of Excel or Word. What advantages does Access have over other database software?
Excel can be used as a database but it has severe limitations. In Access, you can do complex searches (called "Queries", produce quality Reports and convenient data entry forms. You can also improve your database by making it "relational". Excel is more suited to performing calculations or "data modelling" functions.
A relational database application such as Access is better than a Flat File database program, such as Information Workshop or Excel because it can mean spending less time on data entry and fewer errors.
Define file formats for all the files that you are going to produce in this project.
Access saves files in MDB (Microsoft Database) format. It compresses all your tables, forms, queries and reports into a single file.
What will your output be?
Sometimes it will be sufficient for your user to see information on the screen but, on other occasions, s/he may need a printed report. Explain what reports you will produce. Say what form of output is appropriate to each of your objectives?
Draw a flowchart to illustrate the flow of data. You should illustrate the sequence of operations needed to solve the problem.
Instructions here:
How to Draw a Systems Flowchart
You can use a flowchart stencil or you can do a flowchart in Word by clicking View / Toolbars / Drawing. The Drawing toolbar includes all the flowchart shapes.
Remember that you are trying to illustrate the flow of data i.e. what are the inputs, processes and outputs?
3. Design (9 marks)
Produce some rough sketches of data entry forms and table relationships to illustrate three different designs for your database.
You must say which design you prefer and why.
Produce a detailed and annotated diagrams for your chosen design.
You must show table structures, data validation details, sorts, queries, data entry forms, reports and relationships.
Show your design to your end-user and ask him/her to comment on it.
Say what changes you will make as a result of these comments.
List, in order, the tasks you have to complete. Break down big tasks into sub-tasks. Say what time-scale you are working to.
Produce a detailed action plan.
Devise a test plan
Produce a table like the one below and fill in all columns except the "Actual Result" column.
Plan at least 10 tests.
For further guidance see the guide on Testing a GCSE Project (word document)
Also see: Example Database Test Plan
You should test things like queries, reports, data validation features, printing, combo boxes.
| Test No. | Purpose of Test | Test Data | Expected Result | Actual Result |
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 |
4. Implement (12 marks)
You must show that you have solved your "problem".
During this process, you must:
Annotate, Annotate, Annotate
On each piece of printed out work, you should write what you did and how you did it. Say what features of the program you used. Say what buttons you pressed and what menu items you selected. The more you can explain your work, the more convinced the examiner will be that you know what you're doing.
Do a screenshot of your work by pressing ALT+Print Screen and then pasting into Word. Remember to annotate the print-out.
Print out evidence to show all queries, forms, tables, reports and macros that you produced.
See further Implementation Guidance
Show the progression of your work
Save your draft copies! When you make mistakes, you should show how you corrected mistakes.
Follow your Test Plan.
Reproduce your test plan. This time, fill in the "actual result" column. Provide evidence to show how you carried out each test.
It is very important that you compare "expected results" with "actual results"
For further guidance see the guide on Testing a GCSE Project (word document)
Write about any corrections you made as a result of your testing.
Compare your original design with your final outcome.
Explain any differences.
5. Evaluate (5 marks)
Evaluate each of your original "quantitative objectives". Did you achieve them?
What technical problems did you encounter?
Explain any changes to your original design.
Supply evidence that the end-user has seen your work and supplied comments.
Say what you think of the end-user's comments.
How could your work be improved/extended?
Remember the marks for spelling, punctuation and grammar!