Reference no: EM132952461
CO4703 Database Implementation - University of Central Lancashire
Learning Outcome 1. Implement a functional relational database, giving consideration to integrity and validation constraints, using appropriate database environment
Learning Outcome 2. Apply and justify database design techniques for the construction of a conceptual data model
Learning Outcome 3. Critically review work with respect to underpinning theories
Task 1
Use Oracle Forms to create a database application. This application is based on the following table types, with primary keys underlined and foreign keys in italics:
Student
|
|
netId surname forename address
cCode
|
10 char maximum (e.g. Bond_J) 20 char maximum
20 char maximum
50 char maximum
7 char (e.g. C100001)
|
(course code)
|
cYear
|
1 digit number (range 1,2,3)
|
(course year)
|
dob
|
date
|
(date of birth)
|
Assessment
|
|
|
aCode
|
10 char maximum
|
(assessment code)
|
moduleCode
|
6 char
|
(e.g. CO4703)
|
type
|
20 char maximum
|
(e.g. examination)
|
weighting author
dateOfAssessment
|
number; always no greater than 1 20 char maximum
date
|
(e.g. 0.5, i.e. 50%)
|
Result
|
|
|
rNo number (5 digits)
netId 20 char maximum
aCode 10 char maximum
mark number (an integer from 0 to 100 inclusive)
marker 20 char maximum
You are expected to create these tables using SQL and then populate them with appropriate and sufficient test data of your own (hint: use varchar2 for netId and other variable length character strings).
To gain a pass mark for task 1 you will achieve basic functionality for forms A, B and C as outlined below. To gain higher marks you will create more user-friendly forms (e.g. good layout, use of buttons and clear messages) ), and will achieve the functionality as italicised for each form.
Form A - Create/Amend a student
1. Enter details; all alphabets should be in upper case automatically
2. Save a new record
3. Year should be 1 to 3 only (inclusive)
4. Date of birth (they should be on or past their 18th birthday and on or before 30th birthday)
5. Buttons that perform functions (SAVE, CLEAR, DELETE etc.)
6. A list of values for the course code (based on existing codes in your data)
7. Any other functionality you deem to be appropriate
Form B - Display a student's assessment result details
A two block form showing full details of a student and all the assessment results she/he has.
1. Enter a netId and the basic result details are displayed
2. This form is read only and updating should be disallowed
3. netId is selected from a list of values
4. For each assessment mark, the assessment type should be displayed
5. Display the mean mark for the student
6. Addition of functional buttons
7. Any other functionality that you deem to be appropriate
Form C - Menu
1. Two buttons which call up Forms A and B
2. When Forms A and B are exited, control should pass back to the menu
3. A password is required for form A (but not B). Form A should be accessed only if the correct password is entered.
4. Any other functionality that you deem to be appropriate.
For Task 1, you should submit relevant and detailed documentation in a word-processed file demonstrating the design and implementation of the above three forms. The documentation should have the following; you may include additional items that you deem to be appropriate.
1. SQL table creation and insertion statements for all tables.
2. For each of the functions listed above under Form A, B and C, explain how the function is implemented. Show and explain trigger codes and other techniques (list of values, alert etc.) wherever appropriate.
3. Include screenshots to illustrate your explanation wherever appropriate.
Task 2
(a) Design a relational database for the table fragment shown on the next page.
You should assume that the data shown in the table is a typical snapshot of data for these records and demonstrates all the enterprise rules which apply, even though some rules may be simpler than those in reality.
Normalise this table into Third Normal Form showing the intermediary stages of First and Second Normal Form. Primary keys and foreign keys in all the three forms should be indicated clearly. You are expected to start the normalisation process by first choosing the property address alone as a primary key. Your normalised tables should only include the attributes shown in the table fragment; do not add any new attribute.
Justify your solution to this problem.
(b) Critically evaluate normalisation as a technique for database design. For each advantage or disadvantage identified, you should use the Property4Sale Ltd data to illustrate and explain it. You may extend these data in order to identify suitable examples to illustrate your point, however you should only do so if the current data do not provide for such examples.
The evaluation should not exceed 500 words (excluding the list of references).
References must be listed in the end and cited within your evaluation using a consistent format such as Harvard Refencing.
Attachment:- Database Implementation.rar