Course Title: Design a database

Part B: Course Detail

Teaching Period: Term1 2012

Course Code: COSC6078C

Course Title: Design a database

School: 650T TAFE Business

Campus: City Campus

Program: C5194 - Diploma of Information Technology (General)

Course Contact : Chandra Nannegari

Course Contact Phone: +61 3 9925 1657

Course Contact

Name and Contact Details of All Other Relevant Staff

Nominal Hours: 50

Regardless of the mode of delivery, represent a guide to the relative teaching time and student effort required to successfully achieve a particular competency/module. This may include not only scheduled classes or workplace visits but also the amount of effort required to undertake, evaluate and complete all assessment requirements, including any non-classroom activities.

Pre-requisites and Co-requisites


Course Description

This unit defines the competency required to establish client needs and technical requirements and to design a database that meets those requirements.

If you are undertaking this course in Melbourne from semester 2, 2012 onward your class will be held in a device-equipped teaching space. Each student group will have access to a laptop. It is however recommended that you have access to a mobile computing device to allow greater flexibility in terms of where you can work on campus both in and outside class times.

National Codes, Titles, Elements and Performance Criteria

National Element Code & Title:

ICAA5139B Design a database


1. Determine database requirements

Performance Criteria:

1.1 Meet with client and conduct a user needs analysis to determine database functionality
1.2 Analyse results of user needs analysis to identify technical requirements
1.3 Develop a conceptual model of the database
1.4 Submit conceptual model to client for review
1.5 Evaluate client feedback and make changes as required


2. Develop logical data model

Performance Criteria:

2.1 Identify attributes and determine data types
2.2 Undertake normalisation of attributes
2.3 Develop entity relationship diagram to clarify cardinality of relationships
2.4 Document attributes, normalised data and entity relationship diagram
2.5 Forward documentation to client for confirmation


3. Design data structures

Performance Criteria:

3.1 Confirm primary and foreign keys for tables
3.2 Review client business rules
3.3 Identify referential integrity constraints
3.4 Establish relevant database management system constraints and incorporate into database design
3.5 Develop validation rules for data
3.6 Design indexes and develop data dictionary
3.7 Document the database design


4. Design queries, screens and reports

Performance Criteria:

4.1 Design user interface for database, including menus, input screens and outputs
4.2 Design queries based on requirements
4.3 Design output reports based on requirements
4.4 Compare physical design with conceptual model/user needs analysis
4.5 Incorporate changes as required


5. Design access and security systems

Performance Criteria:

5.1 Review business security plan as basis for commencing access and security design
5.2 Design password and access system for database
5.3 Identify multiple user requirements
5.4 Develop client access profiles using client business model


6. Confirm database design

Performance Criteria:

6.1 Identify database back up and recovery requirements
6.2 Develop and document the database back up and recovery procedures
6.3 Submit database and documentation to client for final approval

Learning Outcomes

Details of Learning Activities

Theory presentations, practical lab classes, tutorial sessions, project plus out-of-class research and homework.

Teaching Schedule

WeekWeek CommencingTopicsAssessment
16th Feb 2012

Pre-training review:


Familiarisation with:

• Program
• Services/facilities
• Other students
• Teacher(s)
• Where to get support
• Student responsibilities
• Course requirements
• Course support documents
• Pre-reading
• Blackboard
• Overview of assessment requirements
• Grading
• Plagiarism
• Appeals
• Extensions
• Feedback
• Privacy
• Submission requirements
• Resubmission policy

Introduction to Determinants 

• Course overview. Review of relational DB concepts. Determinant & Dependencies.

213th Feb 2012Data Redundancy & Anomalies  
320th Feb 2012Steps in Normalisation. Relational Schema. Normal Forms -1NF & 2NF  
427th Feb 2012Normal Forms - 3NF. Steps in Database Development.

Class Exercise (Task 1)

Project posting (Task 2)

55th March 2012ERD concepts. Binary & Ternary relationships.  
612th March 2012ERD’s continued. Recursive relationships. IS A relationship. Class Exercise (Task 1)
719th March 2012Developing a design. Index, Data Dictionary.   
826th March 2012Business Rules, SQL – Queries - Revision  
92nd April 2012SQL – Queries – Continued Class Exercise (Task 1)
                                                                                                           Mid semester break (5 April to 11 April)
99th April 2012SQL – Queries – Continued Class Exercise (Task 1)
1016th April 2012Identification of relevant software. DBMS constraints.Stage 1: Project submission -  (ERD, RS and BR) - (Task 2)
1123rd April 2012• Access and security.
• Assessment – 2: feedback
1230th April 2012• DB design documented and confirmed
• Assessment – 2: feedback
137th May 2012

• Design Reports.

• Assessment – 2: feedback

Class Exercise (Task 1)
1414th May 2012

• Backup and recovery requirements.

• Assessment – 2: feedback

Class Exercise (Task 1)
1521st May 2012• Project submission and Demonstrations.
• Feedback on Competency (CA / NYC).
• Revision
 Stage 2: Project submission
 (Task 2)
1628th May 2012Theory & Practical TEST (Task 3 )Theory & Practical TEST (Task 3 )
174th June 2012Re-submissions if required 

Learning Resources

Prescribed Texts

Peter Rob , Carlos Coronel & Steven Morris, Database Systems: Design, Implementation & Management, 10e Edition, Course Technology.



David M. Kroenke, Database Processing: Fundamentals, Design & Implementation, 9th Edition. Prentice Hall.  


Jeffrey A. Hoffer, Prescott & Topi, Modern Database Management 9/E , Prentice Hall


Other Resources

Overview of Assessment

Students must demonstrate an understanding of all elements of competency to be deemed competent.

A range of assessment methods are used to assess practical skills and knowledge, for example:

• direct questioning combined with review of portfolios of evidence and third party workplace reports of on-the-job performance by the candidate
• review of authenticated documents from the workplace or training environment
• demonstration of techniques

Assessment Tasks

You are required to complete 3 tasks. You must successfully complete all 3 tasks to be deemed competent in this unit.

TASK 1 – Class Exercises (Due Date: Refer to Teaching Schedule)

For this assessment task you are required to complete in-class worksheets on database design aspects as per the Teaching Schedule.

TASK 2 – Project (Due Date: Week 10 & 15)

• The project provides an opportunity, to students, to demonstrate the skills they learn in this unit.
o A case study or real life project is made available to students in Week 4.
o The students will be required to submit the project in two stages (Refer weekly breakdown). Stage 1 is an individual submission while Stage 2 is a group submission.

o Stage 1:
 The students determine database requirements.
 Develop logical data model (ERD using VISIO, Business Rules, Relational Schema)
 Each student is given feedback on their project for further improvement in their model, mimicking the industry approach to a design problem

o Stage 2:
 2 or 3 students join to form a team.
 Design is optimised from stage 1.
 Design is implemented on a RDBMS platform and populated with sample data.
 SQL Queries are executed to validate the model.
 Forms and reports are designed.
 Security features are designed and applied.
 Database back-up and recovery requirements are identified and documented.

TASK 3 – Theory & Practical TEST (Due Date: Week 16)

For this assessment task you need to determine requirements, design logical data model, data structures and SQL queries under TEST conditions.

Assessment Matrix

Other Information

Submission Requirements

Assessment tasks need to be submitted via Blackboard.

You should:

• Ensure that you submit assessments on or before the due date. If your performance in the assessment is affected by unexpected circumstances, you should consider applying for Special Consideration. Information on the process and application forms is available at;ID=ls0ydfokry9rz website.
• Always retain a copy of your assessment tasks. (hard copy and soft copy)
• When you submit work for assessment at RMIT University you need to use a cover sheet that includes a declaration and statement of authorship. You must complete, sign and submit a cover sheet with all work you submit for assessment, whether individual or group work. On the cover sheet you declare that the work you are presenting for assessment is your own work. An assignment cover sheet for submission of work for assessment is available on blackboard.
• Each page of your assessment should include footer with your name, student number, the title of the assessment, unit code and title and page numbers. For example, Julie Macpherson, 324567, Task 2, OHS2345C Ensure safe workplace, Page 1 of 10.

Marking Guide (competency):

Vocational Education and Training (VET) is based on current industry needs and the focus on preparing you for the workplace. Because VET courses are informed by practical application of knowledge and skills, they are based on a system known as ‘competency based training’ (CBT). So when you are assessed in VET it is about whether you are competent to do the job, as well as having a firm grasp on the knowledge and skills required to do that job, as opposed to traditional curriculum based education settings that are often based on knowledge retention.

You need to demonstrate you are competent in each element of the unit of competency you are studying.

You will receive feedback on each assessment task that will inform you whether you are competent or not and how well you are performing. Once competent in all elements of the unit you receive a competency grading.

Please refer to the Final Grades table below.

Marking Guide (Grading)

After achieving competency we then grade your performance in the unit; this gives you the opportunity to have the level of your performance formally recognized against industry standards and employability skills.

The grading is according to the following criteria:


We are looking for a high level of ability to complete all tasks independently as per the specifications as well as demonstrating a high level of initiative in your approach to designing a well-structured database that represents the client’s business reality and provides the user with a productive business tool.


We are looking for depth of understanding of the key concepts and knowledge required to design a well-structured database. You should be able to demonstrate a thorough understanding of all applicable design principles in all the assessment tasks.


We are looking for appropriate use of technology and design tools to assist in presenting all tasks clearly and suitable for the intended clients. You also need to show an understanding of the kinds of problems that can arise in designing a well-structured database and how these might be addressed.


We expect to see ongoing progress both in document portfolio and project relevant to the unit, full utilisation of Blackboard as per course requirements and timely submission of all required assessment tasks.


We expect to see contributions to relevant discussions and scheduled group sessions. In addition your tasks should demonstrate a very good understanding of strategies for a collaborative approach towards teamwork and designing a well-structured database that meets client requirements.

Final Grades table:

CHD = Competent with High Distinction
CDI  = Competent with Distinction
CC  = Competent with Credit
CAG = Competency Achieved - Graded
NYC = Not Yet Competent
DNS = Did Not Submit for assessment

Course Overview: Access Course Overview