Monday, 17 December 2012
Thursday, 13 December 2012
Monday, 10 December 2012
Wednesday, 28 November 2012
P1 (Unit 43)
Animation/Transitions -Animations are the moving types of images which are also called GIFS. They can be used to catch audience's attention or they can even give a certain important piece of information. They can be useful for the media department since media consists of animations and graphic images. The purpose of animations is to entertain and grab people's attention and they can also show an important piece of information. They can be used both on MACS and PCs and they can be both created on them as well. They can be advertised mostly on web-pages but they can also be found on digital posters and computer games. Transitions are mainly used to entertain and make the presentation look more interesting, they don't have a specific and important purpose.
Text - Text is mainly the source of information that is essential to be put in since images won't be enough to explain something to people. It's purpose is to present information. Text can be used anywhere on the web-pages, posters, presentations, video games..etc. The most useful things about the text is the person can make their information stand out as more as possible. Text is one of the ways to grab audience's attention because you can change the font, colors and the sizes of the text. It can be used on any platform since text is needed pretty much everywhere. This is going to help me a lot with my department because that way I can give a lot of information about the department and it's main features.
Navigation -Navigation is the way of how you navigate around a web-site. This is very important since the website creator would have to make their website as easier to navigate around in as possible. There are lots of things that are linked with navigation. Hyperlinks, images and flash buttons helpful in this case because they will help to navigate around a certain area. This is going to be useful for my project since I am going to make my own draft of the website and I will design pages that are going to link to specific areas and give me certain information about the department. Navigation again can be used on any platform and anywhere since it's part of the Internet and websites.
Logo/Graphics - Logos and graphics are also the types of images that can be used in order to represent some sort of information or even the name of the group/company or the name of the department. The media department would use those to represent their name in a graphic logo. The aim of the logos are to catch the viewer's attention and to get the interested in the department. Logos can also be used anywhere on the websites, presentations or posters.
Images - Images are also very important and they can be used to illustrate pictures of the department or things to do with the department and information. This can be used as entertainment and they can present some examples of work of the Media department by the the students.
Videos - For the Media department, videos would be ideal to use on the website since it is also one of the moving images, information sources. I can film a lot of things that are to do with media and then use it to represent the department and to show people the exact things that students do on this subject.
Sounds/Audio- Sounds and audio is very important since it helps people to navigate around the website. If people have some sight problems, then they can hear the audio. This will be mostly helpful for the Music department since it can play out certain songs and pieces of work that has been created by someone.
Audience/purpose- The main audience for the Media Department would be aimed at the students that haven't worked with this subject and by going on the website that I will be creating, they will be able to get all the information they want about the department and the things that are included with it. The students that have never experienced this subject would now be able to get a slight grasp of it by looking at all the information that is given and they can make their own conclusions from there.
Tuesday, 13 November 2012
M2
Those are the screenshots of how I created a query. I went to create, query design, selected the table that I wanted to append the query to, clicked add then close. After I have chosen all the fields that I want to show up in the table, I had to append my query by clicking append to. I had to click the table that I wanted all the information to go to, then click run. I then had to click yes on a few more tables that popped up to confirm that I wanted to append to the table and then I had to save my query.
P7
|
The functionality
type
|
Expected outcome
|
Actual outcome
|
|
Validation
|
All the validation
rules that has been set are supposed to work when the fields are filled in.
|
Everything worked
|
|
Error capture
|
Error capture is
making the database able to capture the errors that may happen and it will
stop any progress in the database.
|
The database is able
to capture errors without problems.
|
|
Error messages
|
You put a special
error message to let the person know of a certain error if the fields in the
table aren’t fully filled in. The error message could say ‘Please fill in all
the fields’. Also, when you try to put an age limitation and someone puts an
age below what you can have, you have an error message popping up saying
‘sorry too young’.
|
My error messages
are fully working when the fields aren’t fully filled in or the age is below
of what it actually has to be.
|
|
Successful entry
|
When you register a
new member and it successfully appears on the table of all members.
|
Works completely
fine and all the entries are successful.
|
|
Manipulation of
normal data
|
Using the append
queries to move data around the database in to the right place.
|
Everything works
with my database as I have created queries and appended them in to the right
places.
|
Wednesday, 24 October 2012
Tuesday, 23 October 2012
Tuesday, 16 October 2012
Tuesday, 9 October 2012
Tuesday, 18 September 2012
D1
There is a range of common errors that happen in database design; incorrect data types, accidental deleting of fields, renaming incorrectly, validation and null values.
Deletion of fields
If you accidentally deleted a field, you can back up the database registration if you have it saved from the last time. That way, you can continue from your last check point without losing too much work. Also, you would need to make sure that the right person will be editing your database. The person has to have experience with databases because then they're not gonna delete anything or make mistakes. The person that doesn't have much experience can just add information to the database without having an actual edit bar where you can make some complicated mistakes.
Incorrect data types & Renaming incorrectly
For incorrect data types and renaming incorrectly, you can set up some input masks. You can set it up so it only has to have a certain type of character typed in. For example you can set it up, so you can only write letters in or you can set it up with digits. You can also have a drop down choices/menu. For example if you have a variety of movie genres put together you can just choose from the list (horror, comedy, drama...etc) without typing it in every time. These ways help avoiding renaming things incorrectly.
Validation
You can create validation rules that will limit you with certain amount of letters or digits that you can place in the table. It can check if the data's too long or short. For example, if you were to put a password in, some require a certain amount of characters (6-10 with includes at least one letter or a number). Validation rules would help you to set it up. Other examples of validations are check digit the last two or one digit in a code are used to check the other digits are correct, format check checks the data in the right format, length check checks if the data isn't too long or short, look up table looks up acceptable values in the table and spell check checks if the spelling is correct.
Null values
You can also set up validation rules. If you're filling up a registration form you would have to make sure that every space has been filled in with information, it is not good leaving some boxes empty. Therefore you can also set up an error message so if someone is gonna be leaving one of the boxes empty, you would have an error message popping up asking you to fill up the empty spaces.
Deletion of fields
If you accidentally deleted a field, you can back up the database registration if you have it saved from the last time. That way, you can continue from your last check point without losing too much work. Also, you would need to make sure that the right person will be editing your database. The person has to have experience with databases because then they're not gonna delete anything or make mistakes. The person that doesn't have much experience can just add information to the database without having an actual edit bar where you can make some complicated mistakes.
Incorrect data types & Renaming incorrectly
For incorrect data types and renaming incorrectly, you can set up some input masks. You can set it up so it only has to have a certain type of character typed in. For example you can set it up, so you can only write letters in or you can set it up with digits. You can also have a drop down choices/menu. For example if you have a variety of movie genres put together you can just choose from the list (horror, comedy, drama...etc) without typing it in every time. These ways help avoiding renaming things incorrectly.
Validation
You can create validation rules that will limit you with certain amount of letters or digits that you can place in the table. It can check if the data's too long or short. For example, if you were to put a password in, some require a certain amount of characters (6-10 with includes at least one letter or a number). Validation rules would help you to set it up. Other examples of validations are check digit the last two or one digit in a code are used to check the other digits are correct, format check checks the data in the right format, length check checks if the data isn't too long or short, look up table looks up acceptable values in the table and spell check checks if the spelling is correct.
Null values
You can also set up validation rules. If you're filling up a registration form you would have to make sure that every space has been filled in with information, it is not good leaving some boxes empty. Therefore you can also set up an error message so if someone is gonna be leaving one of the boxes empty, you would have an error message popping up asking you to fill up the empty spaces.
Monday, 17 September 2012
M1
Referential Integrity:
Referential integrity is how the databases are linked together to make sure that the references between are valid and intact. Referential integrity is usually enforced by the combination of a primary and a foreign key. For example, customer numbers in a customer file are the primary keys, and customer numbers in the order
file are the foreign keys. If a customer record is deleted, the order records must also be deleted; otherwise they are left without a primary reference. There are many benefits of defining referential integrity in a database: improved data quality, faster development, fewer bugs and consistency across applications.
Primary Key: Every time you put in data inside a relational table, you would need an easy way to identify each row that will be stored in the table. For that you would need to use a primary key. The value that this key holds should be unique for each record in the database. For example if you were to have a table named 'Employees' that contains personal information, you'd need to select an appropriate primary key that would uniquely identify each employee. Typing in the name wouldn't be really appropriate because there can obviously be people with the same names involved. So you would use an unique employee ID. That way you could list more and more people in your table using little unique ID's. Also that way you won't have anything mixed up.
Foreign Key: The foreign key is a unique field in a database that another table will use to access information, such as a "look up" table. It's information related with a primary key in another table. It makes it easier to find information about a certain aspect.
One-to one relationships: In one-to one relationship, each row is in one database table is linked to 1 and only 1 other row in another table. In one-to one relationship between table A and table B, each row in table A is linked to one of the rows in table B. The number of rows in table A must be equal to the number of rows in table B. For example, a person would have only one specific identity document that will belong only to them. Therefore one of the tables will have the name of the person and it would be linked with their ID document. No other links would be involved.
One-to many relationships: Those are the most common types of the database relationships. They occur when each record in the first table corresponds to one or more records in th second table but each record in the second table corresponds to only one record in the first table. For example in elementary school the relationship between the teacher and the students will most likely be one-to many, since the class has one teacher but the teacher might have multiple classes.
Many to many relationships: Those occur when each record in the first table corresponds to 2 or more records in the second table and the each record in the second table can correspond to 2 or more records in the first table. For example the relationship between a teacher and courses would most likely be many-to many since most teachers can teach more than one course and each course can have more than one teacher.
file are the foreign keys. If a customer record is deleted, the order records must also be deleted; otherwise they are left without a primary reference. There are many benefits of defining referential integrity in a database: improved data quality, faster development, fewer bugs and consistency across applications.
Primary Key: Every time you put in data inside a relational table, you would need an easy way to identify each row that will be stored in the table. For that you would need to use a primary key. The value that this key holds should be unique for each record in the database. For example if you were to have a table named 'Employees' that contains personal information, you'd need to select an appropriate primary key that would uniquely identify each employee. Typing in the name wouldn't be really appropriate because there can obviously be people with the same names involved. So you would use an unique employee ID. That way you could list more and more people in your table using little unique ID's. Also that way you won't have anything mixed up.
Foreign Key: The foreign key is a unique field in a database that another table will use to access information, such as a "look up" table. It's information related with a primary key in another table. It makes it easier to find information about a certain aspect.
One-to one relationships: In one-to one relationship, each row is in one database table is linked to 1 and only 1 other row in another table. In one-to one relationship between table A and table B, each row in table A is linked to one of the rows in table B. The number of rows in table A must be equal to the number of rows in table B. For example, a person would have only one specific identity document that will belong only to them. Therefore one of the tables will have the name of the person and it would be linked with their ID document. No other links would be involved.
One-to many relationships: Those are the most common types of the database relationships. They occur when each record in the first table corresponds to one or more records in th second table but each record in the second table corresponds to only one record in the first table. For example in elementary school the relationship between the teacher and the students will most likely be one-to many, since the class has one teacher but the teacher might have multiple classes.
Many to many relationships: Those occur when each record in the first table corresponds to 2 or more records in the second table and the each record in the second table can correspond to 2 or more records in the first table. For example the relationship between a teacher and courses would most likely be many-to many since most teachers can teach more than one course and each course can have more than one teacher.
Thursday, 12 July 2012
Subscribe to:
Comments (Atom)




