Oracle Forms Database Application Assignment

Task 1: Create a Database Application with Oracle Forms

• If you have not yet made the university aware of any disability, specific learning difficulty, long-term health or mental health condition, please complete a Disclosure Form.  The Inclusive Support team will then contact to discuss reasonable adjustments and support relating to any disability.  For more information, visit the Inclusive Support site.
• If you have any other query or require further support you can contact The The Student Information and Support Centre.  Speak with us for advice on accessing all the University services as well as the Library services. Whatever your query, our expert staff will be able to help and support you. For more information , how to contact us and our opening hours visit Student Information and Support Centre.
• If you have any valid mitigating circumstances that mean you cannot meet an assessment submission deadline and you wish to request an extension, you will need to apply online prior to the deadline.

Learning Outcome

On completion of this assignment you will be expected to be able to:

1. Develop a relational database using an appropriate DBMS.
2.   Apply an appropriate technique for the construction of a conceptual data model suitable for implementation.

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:

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 mCode, and also for all 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 a more user-friendly interface (e.g. good screen layout, appropriate use of colours, use of buttons, 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 4 only (inclusive)

4.Date of birth (they should be on or past their 18th birthday)

5.Buttons that perform functions (SAVE, CLEAR, DELETE etc.)

6.A list of values for the course code (based on existing codes in the script file)

7.Any other functionality you deem to be appropriate

Form B – Display a student’s module registration details

A two block form showing full details of a student and all the modules she/he has registered.

1.Enter a netId and the basic module 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 module registration the module title and fee should be displayed

5.Display the total amount of module fees 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.

Because Task 1 is assessed through this documentation only, anything that is not included in it will not be given marks.

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 booking number 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 A2Z 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).