Part B: Course Detail
Teaching Period: Term1 2025
Course Code: ISYS7590C
Course Title: Design databases
Important Information:
Please note that this course may include compulsory in-person attendance requirements for some or all teaching activities.
It is recommended that you check your Canvas course shell closer to the course start date for details about any mandatory in-person attendance requirements.
Please be aware that the course delivery method may need to change quickly in response to evolving course requirements. Students must maintain regular communication with their teachers to stay informed about any updates.
School: 520T Future Technologies
Campus: City Campus
Program: C5402 - Diploma of Information Technology
Course Contact: Trevor Stone
Course Contact Phone: +61 3 9925 4612
Course Contact Email: trevor.stone@rmit.edu.au
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
None
Course Description
In this course you will gain skills and knowledge required to establish client needs and technical requirements and to design a database that meets identified requirements.
This course is clustered for delivery and assessment with the following unit:
ICTWEB451 Apply structured query language in relational databases
National Codes, Titles, Elements and Performance Criteria
National Element Code & Title: |
ICTDBS506 Design databases |
Element: |
1. Determine database requirements |
Performance Criteria: |
1.1 Conduct user-needs analysis with required personnel and determine database functionality requirements 1.2 Determine user-needs analysis technical requirements 1.3 Develop conceptual model of database according to organisational requirements 1.4 Submit conceptual model to required personnel 1.5 Seek and respond to feedback and make required changes |
Element: |
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 (ER) diagram and clarify cardinality of relationships 2.4 Document attributes, normalised data and ER diagram 2.5 Submit documentation to required personnel and seek and respond to feedback |
Element: |
3. Design data structures |
Performance Criteria: |
3.1 Confirm primary and foreign keys according to technical requirements 3.2 Identify referential integrity constraints and organisational business rules 3.3 Establish database management system constraints and incorporate into database design 3.4 Design and develop data validation rules, indexes and data dictionary 3.5 Document database design according to organisational policies and procedures |
Element: |
4. Design queries, screens and reports |
Performance Criteria: |
4.1 Design database according to organisational requirements 4.2 Design required queries and output reports 4.3 Compare physical design against conceptual model and user-needs analysis 4.4 Incorporate all required changes into database design |
Element: |
5. Design access and security systems |
Performance Criteria: |
5.1 Review existing business security plan and use as design base 5.2 Design database password and access system 5.3 Identify multiple-user requirements 5.4 Develop required organisational access profiles |
Element: |
6. Confirm database design |
Performance Criteria: |
6.1 Determine database backup and recovery requirements 6.2 Develop and document database backup and restore procedures 6.3 Submit database and documentation to required personnel 6.4 Seek and respond to feedback from required personnel 6.5 Obtain final task sign off from required personnel |
Learning Outcomes
On successful completion of this course the candidate will demonstrate the ability to complete the tasks outlined in the elements, performance criteria and foundation skills of this unit.
Details of Learning Activities
A range of learning activities are planned for this course including self-paced and collaborative classroom based activities.
The collaborative classroom based activities will include theory sessions, practical lab sessions, tutorial sessions, and out-of-class research and homework. We expect you to participate and contribute in all scheduled learning activities
Teaching Schedule
The proposed teaching schedule for ICTDBS506 is detailed below:
Semester 1. 2025Week Date TopicAssessment / Learning activitiesWeek 1 | 10-16 February | 1. Determine database requirements |
1.1 Conduct user-needs analysis with required personnel and determine database functionality requirements 1.2 Determine user-needs analysis technical requirements |
Week 2 | 17-23 February | 1. Determine database requirements |
1.3 Develop conceptual model of database according to organisational requirements 1.4 Submit conceptual model to required personnel 1.5 Seek and respond to feedback and make required changes Assessment 1 - Stage 1 released |
Week 3 | 24 Feburary-2 March | 2. Develop logical data model |
2.1 Identify attributes and determine data types 2.2 Undertake normalisation of attributes |
Week 4 | 3-9 March | 2. Develop logical data model |
2.3 Develop entity-relationship (ER) diagram and clarify cardinality of relationships 2.4 Document attributes, normalised data and ER diagram 2.5 Submit documentation to required personnel and seek and respond to feedback |
Week 5 | 10-16 March | 3. Design data structures |
3.1 Confirm primary and foreign keys according to technical requirements 3.2 Identify referential integrity constraints and organisational business rules Assessment 1 - Stage 1 due |
Week 6 | 17-23 March | 3. Design data structures |
3.3 Establish database management system constraints and incorporate into database design 3.4 Design and develop data validation rules, indexes and data dictionary 3.5 Document database design according to organisational policies and procedures Assessment 1 - Stage 2 released |
Week 7 | 24-30 March | 4. Design queries, screens and reports |
4.1 Design database according to organisational requirements 4.2 Design required queries and output reports |
Week 8 | 31 March - 6 April | 4. Design queries, screens and reports |
4.3 Compare physical design against conceptual model and user-needs analysis 4.4 Incorporate all required changes into database design Assesment 1 - Stage 2 due |
Week 9 | 7-13 April | 5. Design access and security systems |
5.1 Review existing business security plan and use as design base 5.2 Design database password and access system Assesment 1 - Stage 3 released |
Week 10 | 14-20 April | 5. Design access and security systems |
5.3 Identify multiple-user requirements 5.4 Develop required organisational access profiles
|
Mid-Semester Break | 18-25 April |
|
|
Week 11 | 28 April - 4 May | 6. Confirm database design |
6.1 Determine database backup and recovery requirements 6.2 Develop and document database backup and restore procedures |
Week 12 | 5-11 May | 6. Confirm database design |
6.3 Submit database and documentation to required personnel 6.4 Seek and respond to feedback from required personnel 6.5 Obtain final task sign off from required personnel Assessment 1 - Stage 3 due |
Week 13 | 12-18 May | 1. Identify database requirements |
1.1 Determine information required from database 1.2 Identify tables holding this information Assessment 2 released |
Week 14 | 19-25 May | 1. Identify database requirements |
1.3 Identify primary keys in these tables 1.4 Identify relationships between these tables including foreign keys |
Week 15 | 26 May - 1 June | 2. Build and implement SQL in relational databases |
2.1 Identify and build SQL statements according to task requirements 2.2 Create tables in a database using SQL statements 2.3 Create primary and foreign keys required in database table |
Week 16 | 2-8 June | 2. Build and implement SQL in relational databases |
2.4 Manipulate data in a database using SQL statements 2.5 Query database using SQL statements 2.6 Retrieve information from database using written SQL statements Assessment 2 due |
Week 17 | 9-15 June | 3. Test and verify SQL results |
3.1 Construct test data and test SQL statements according to organisational procedures 3.2 Determine expected results of SQL statements |
Week 18 | 16-22 June | 3. Test and verify SQL results |
3.3 Verify result of constructed SQL statements against expected results and document findings 3.4 Confirm task requirements are met and obtain sign-off from required personnel |
*Please note that this timeline is subject to change based on semester requirements. We recommend checking your Canvas course shell regularly to stay updated with the latest schedule.
Student directed hours involve completing activities such as reading online resources, assignments, individual student/teacher course-related consultation. Students are required to self-study the learning materials and complete the assigned out of class activities for the scheduled non-teaching hours.
Learning Resources
Prescribed Texts
References
Other Resources
Software Requirements:
Microsoft Office (Word, Access)
Microsoft Visio (To Create ER Diagrams)
XAMPP (MySQL & Web Server) - Open Source Software
Virtual Box- Open Source Software
Overview of Assessment
Assessment for this course is ongoing throughout the semester. Your knowledge and understanding of course content is assessed through participation in class exercises and various types of assessments.
Full assessment briefs will be provided and can be found on CANVAS.
Assessment Tasks
This unit has the following assessments:
- Task 1 Case Study
- Stage 1
- Stage 2
- Stage 3
- Task 2 Practical Assessment
Feedback
Feedback will be provided throughout the semester in class and/or online discussions. You are encouraged to ask and answer questions during class time and online sessions so that you can obtain feedback on your understanding of the concepts and issues being discussed. Finally, you can email or arrange an appointment with your teacher to gain more feedback on your progress.
You should take note of all feedback received and use this information to improve your learning outcomes and final performance in the course.
Assessment Matrix
Element |
Performance criteria |
|
|
|
|
Assessment 1: Product - Case Study (Database Design & Implementation) - Stage1-3 |
Assessment 2: Practical -SQL Relates to clustered unit COSC7395C* |
1. Determine database requirements |
1.1 Conduct user-needs analysis with required personnel and determine database functionality requirements |
STAGE 1 (2) |
|
1.2 Determine user-needs analysis technical requirements |
STAGE 1 (3,4) |
|
|
1.3 Develop conceptual model of database according to organisational requirements |
STAGE 2 (1) |
|
|
1.4 Submit conceptual model to required personnel |
STAGE 2 (2) |
|
|
1.5 Seek and respond to feedback and make required changes |
STAGE 1 (4,5) |
|
|
2. Develop logical data model |
2.1 Identify attributes and determine data types |
STAGE 2 (4c) |
|
2.2 Undertake normalisation of attributes |
STAGE 2 (4b) |
|
|
2.3 Develop entity-relationship (ER) diagram and clarify cardinality of relationships |
STAGE 2 (1) |
|
|
2.4 Document attributes, normalised data and ER diagram |
STAGE 2 (4) |
|
|
2.5 Submit documentation to required personnel and seek and respond to feedback |
STAGE 2 (3,4) |
|
|
3. Design data structures |
3.1 Confirm primary and foreign keys according to technical requirements |
STAGE 3 (2c) |
|
3.2 Identify referential integrity constraints and organisational business rules |
STAGE 2 (4d) |
|
|
3.3 Establish database management system constraints and incorporate into database design |
STAGE 2 (4a) |
|
|
3.4 Design and develop data validation rules, indexes and data dictionary |
STAGE 2 (4c) |
|
|
3.5 Document database design according to organisational policies and procedures |
STAGE 2 (4g) |
|
|
4. Design queries, screens and reports |
4.1 Design database according to organisational requirements |
STAGE 3 (1,2,3) |
Task 1 |
4.2 Design required queries and output reports |
|
Task 3 |
|
4.3 Compare physical design against conceptual model and user-needs analysis |
STAGE 2 (4e) |
|
|
4.4 Incorporate all required changes into database design |
STAGE 2 (4g) |
|
|
5. Design access and security systems |
5.1 Review existing business security plan and use as design base |
STAGE 1 (2,3) |
|
5.2 Design database password and access system |
STAGE 3 (6) |
|
|
5.3 Identify multiple-user requirements |
STAGE 1 (2,3) |
|
|
5.4 Develop required organisational access profiles |
STAGE 1 (4c) |
|
|
6. Confirm database design |
6.1 Determine database backup and recovery requirements |
STAGE 3 (5a,5b) |
|
6.2 Develop and document database backup and restore procedures |
STAGE 3 (5c) |
|
|
6.3 Submit database and documentation to required personnel |
STAGE 3 (5c, 6) |
|
|
6.4 Seek and respond to feedback from required personnel |
STAGE 2 (2) STAGE 2 (3) |
|
|
6.5 Obtain final task sign off from required personnel |
STAGE 3 (7, 8) |
|
Other Information
Credit Transfer and/or Recognition of Prior Learning (RPL):
You may be eligible for credit towards courses in your program if you have already met the learning/competency outcomes through previous learning and/or industry experience. To be eligible for credit towards a course, you must demonstrate that you have already completed learning and/or gained industry experience, that is:• Relevant
• Current
• Satisfies the learning/competency outcomes of the course
To find more information about credit transfer and RPL, please refer to the following link: https://www.rmit.edu.au/students/my-course/enrolment/apply-for-credit
Study and Learning Support:RMIT University Library provides free study support services and resources to help you build your academic skills.
Study and Learning Centre (SLC) provides free learning and academic development advice to you. Services offered by SLC to support your numeracy and literacy skills are:
• Assignment writing, thesis writing and study skills advice
• Math and science developmental support and advice
• English language development
Equitable Learning Services (ELS):
The Equitable Learning Services team (ELS team) supports and creates equal opportunities for students with a disability, long-term illness and/or mental health condition. We also support primary carers.
ELS works in partnership with students to create an Equitable Learning Plan. Your plan is tailored to you, supports your needs and establishes how RMIT can provide ongoing assistance so you can access and participate in your studies. The ELS team can assist you to manage your Equitable Learning Plan.
To find more information about services offered by Equitable Learning Services (ELS), please refer to the following link: https://www.rmit.edu.au/students/support-services/equitable-learning
Extensions and Special Consideration
Extensions:
• Extensions are available for unforeseen circumstances of a short-term nature.
• Applications must be submitted to the school at least one working day before the due date of the assessment.
• Extensions can be approved for up to 7 days past the due date for an assessment. (Where students need an extension exceeding 7 days, they must instead apply for special consideration.)
Special Consideration:
• An application for special consideration is made in advance of an assessment wherever possible, but will normally be accepted within five working days after the assessment date. For more information, see the Special Consideration page of the RMIT website.
Plagiarism:Plagiarism is a form of cheating and it is very serious academic offence that may lead to expulsion from the University.
Please Refer: www.rmit.edu.au/academicintegrity to find more information about plagiarism.
Other Information:
All email communications will be sent to your RMIT email address and you must regularly check your RMIT emails.
Course Overview: Access Course Overview