Skip to document

Lesson 6 - Evaluation Structure A and B

structure
Subject

Information Technology

84 Documents
Students shared 84 documents in this course
Academic year: 2023/2024
Uploaded by:
Anonymous Student
This document has been uploaded by a student, just like you, who decided to remain anonymous.
Bede Academy

Comments

Please sign in or register to post comments.

Preview text

Part A evaluation – tips:

Criteria will change but general concept:

1. How well your database structure has minimised data duplication and how well your

database structure meets these requirements:

What is data duplication?

What is normalisation?

Flat file database – created into 2 3 or 4 tables all linked together

In the sample of data you were given in the task – what data was repeated?

What problems does repeated data cause?

Explain the types of relationships that you uses – 1-1, - M, referential integrity

What Primary Keys did you use, what is the purpose of a PK? Why is it okay to repeat this?

What Foreign/Composite keys did you use? Why is it okay to repeat this?

●Entities (not Tables)

●Attributes (not Fields)

●Tuples (not Records)

●One to Many

●Normalisation to prevent Data Redundancy

●Data Duplication and Data Inconsistency

●Enforce Referential Integrity

●Primary Key

●Foreign Key

●Composite Key

2. Did you do everything that was required of you in the task– general summary of

Strengths and Weaknesses

3. Conclusion

Evaluation Part B - Break it down into evaluating the 2 forms:

Form 1 – normally the simple form:

What was good about the form:

Easy to use

Simple data Entry/colour scheme/title

What did it allow you to do

What Buttons did you use, what drop down boxes, what validation?

Did you include instructions – if so why?

Are the PK and FK labelled clearly?

Explain the code or macros you used and why – error messages etc

General summary with Strengths and Weaknesses

Form 2 – normally the complex form:

Ease of use and user friendly

Did it match the same format as form one?

What did it allow the user to do

Why did you use certain fields over others? Automatically assign the data

What code and macros were used

What was required on the form – was this clear to see

When you tested the form did it show any errors

What happened when you submitted an entry – did it all work

What would you have changed?

User

User friendly

Accessibility

Intuitive

Ease of use

Size of text

Size of button

Layout

Colour

Font Style/Size

Instructions

Disable ID Field.

Beaches Evaluation- Part B

A record will not save in the donor table without a donor’s surname and a donor’s email

address this is an advantage because it means that when people an entering data into the

database they have to enter in the data in which is necessary Surname and email address is

a necessity because the business will need to know who the donor is so that they can

contact them or have their data on their database. A disadvantage of this is that for some

people who are wanting to be a donor may not have the data which is needed. We did a

validation rule that the field is a required field which means that the data has to be entered

and will not save unless the data is entered. They want the database to not save in the

donor table without a donor’s surname and email address and it does do this means that

the database work efficiently

A record will save in the donor table if the donor’s details are present and valid this is an

advantage because it means that all the data which is entered by new donors their data will

be saved to the database and that they then hold data on the particular person in case they

need to email or contact the donor. A disadvantage of this is that the data may say that it is

not valid due to the database being too incentive meaning that about the email address it

may say it is invalid. Add a save button so that the data will be added to the database as

long as all the fields which are required are entered. The database will save in the donor

table if the donor’s details are present and valid this means that the new data can be saved.

In the donation table on the Donation date I added in the default value =Now () this

therefore means that for every data which is entered into the database the date that it is on

that day will be automatically entered. This is an advantage because it means that for the

people who are unsure on the date this will be automatically entered for them. The form

will automatically update todays date this is what they wanted the database to do, because

they do not have to enter the data.

After the donation amount is input and the update button clicked the total donations and

status will update to show any changes. This is so that all the data is up to date and is

entered and updated as often as it is needed so by the person entering the data clicking on

the save button therefore this will all be automatically saved to the database. They want the

database to donation amount is input and the update button clicked the total donations and

status will update to show any changes, the database does these tasks which it is thought

for it do it.

Was this document helpful?

Lesson 6 - Evaluation Structure A and B

Subject: Information Technology

84 Documents
Students shared 84 documents in this course
DegreeGrade:

Sixth Form (A Levels)

A1 - AS Level
Was this document helpful?
Evaluation tips A and B
Part A evaluation – tips:
Criteria will change but general concept:
1. How well your database structure has minimised data duplication and how well your
database structure meets these requirements:
What is data duplication?
What is normalisation?
Flat file database – created into 2 3 or 4 tables all linked together
In the sample of data you were given in the task – what data was repeated?
What problems does repeated data cause?
Explain the types of relationships that you uses – 1-1, - M, referential integrity
What Primary Keys did you use, what is the purpose of a PK? Why is it okay to repeat this?
What Foreign/Composite keys did you use? Why is it okay to repeat this?
●Entities (not Tables)
●Attributes (not Fields)
●Tuples (not Records)
●One to Many
●Normalisation to prevent Data Redundancy
●Data Duplication and Data Inconsistency
●Enforce Referential Integrity
●Primary Key
●Foreign Key
●Composite Key
2. Did you do everything that was required of you in the task– general summary of
Strengths and Weaknesses
3. Conclusion
Evaluation Part B - Break it down into evaluating the 2 forms: