Course Title: Design a database

Part B: Course Detail

Teaching Period: Term1 2020

Course Code: COSC7371C

Course Title: Design a database

School: 650T Vocational Business Education

Campus: City Campus

Program: C5395 - Diploma of Information Technology

Course Contact: Val Christou

Course Contact Phone: +61 3 9925 5076

Course Contact Email: val.christou@rmit.edu.au


Name and Contact Details of All Other Relevant Staff

Course Leader: Chandra Nannegari  

chandra.nannegari@rmit.edu.au   

+61 3 9925 1657

Dr. Han Catherine Lin

han.lin@rmit.edu.au

+61 3 9925 1336

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

This unit describes the skills and knowledge required to establish client needs and technical requirements and to design a database that meets those requirements.

It applies to individuals employed as database administrators and designers who are required to design databases.


National Codes, Titles, Elements and Performance Criteria

National Element Code & Title:

ICTDBS502 Design a database

Element:

1. Determine database requirements

Performance Criteria:

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

Element:

2. Develop a logical data model

Performance Criteria:

2.1 Identify the attributes and determine the data types 2.2 Undertake the normalisation of attributes 2.3 Develop an entity-relationship (ER) diagram in order to clarify the cardinality of relationships 2.4 Document attributes, normalised data, and the ER diagram 2.5 Forward documentation to the client for confirmation

Element:

3. Design the data structures

Performance Criteria:

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

Element:

4. Design queries, screens and reports

Performance Criteria:

4.1 Design the 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 the physical design with the conceptual model, or user-needs analysis 4.5 Incorporate changes as required

Element:

5. Design access and security systems

Performance Criteria:

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

Element:

6. Confirm the database design

Performance Criteria:

6.1 Identify the database backup and recovery requirements 6.2 Develop and document the database backup and restore procedures 6.3 Submit the database, and documentation, to the client for final approval


Learning Outcomes



Details of Learning Activities

A range of learning activities are planned for this course including self-paced and collaborative classroom based activities.

 

Learning activities will include laboratory-based sessions on a variety of topics as shown in the weekly breakdown.  Learning activities will generally consist of practical computer exercises based on teacher handouts.  Students should attend all sessions.

 

Students will also be expected to undertake work on a small database project and other activities for homework.

 

The collaborative classroom based activities will include group discussion, group problem solving activities and opportunities to practice your skills in a simulated/real workplace environment.

 

We expect you to participate and contribute in all scheduled learning activities.


Teaching Schedule

The Teaching Schedule for this course is as follows:

 

Induction Session

Prior to training commencement a program level induction session will be conducted that comprises the following:

  • Program overview and requirements
  • MyRMIT/Blackboard
  • Overview of assessment requirements
  • Pre-Training Review including:
    • Recognition of Prior Learning and Credit Transfers
    • Assessment of current skills and knowledge
  • Competency/Grading Criteria
  • Plagiarism
  • Appeals
  • Extensions
  • Feedback
  • Privacy
  • Submission requirements
  • Resubmission policy
  • Where to get support
  • Student responsibilities


 

Please note that this course, ICTDBS502 - Design a database, is co-delivered and co-assessed holistically along with ICTICT509 - Gather data to identify business requirements.

 

The nominal hours associated with this are a guide only and represent the total teaching time and student effort required to successfully complete the course.  This may include not only scheduled classes but also the amount of effort required to undertake, evaluate and complete all assessment requirements, including any non-classroom activities

 

Semester 1, 2020

Week

Week Beginning

Topic

Learning Materials and Activities

Assessment Remarks

1

10th Feb 

Introduction to DB design
•  Course introduction & overview. Relational database concepts.
•  Introduction to Access. Web forms & data entry. 2-table relationships  

Introduction to the course including:
•  Course requirements
•  Course support documents
•  Course Canvas access
•  Accuracy of enrolment
•  Assessment requirements/Cover Sheets
•  Reminder re Plagiarism
•  Reminder re Appeals
•  Extensions/Re-submissions
•  Feedback in this courser
•  Reminder re submission requirements
•  Getting help

ACTIVITY 1 - Implementing a one-table database - Real world examples.

ACTIVITY 2 - Implementing a two-table database  (including forms and sub-forms) with sample data in MS Access. 

ACTIVITY 3 - Implementing  a second database  (including forms and reports) with sample data in MS Access.

 

2

17th Feb

Key sources of data. Business rules.
Basic ERDs. 1:M relationships & foreign keys

ACTIVITY 1 - Design and implement simple two-table databases. 

ACTIVITY 2 - Preliminary discussion of the Team Database Project

Project Specifications issued.                                                                     
Project Teams selected

3

24th Feb

Business documents & business rules.
More on ERDs: M:N relationships & bridging tables

ACTIVITY 1 - Design and implement databases for more complex scenarios with many to many relationships: 

ACTIVITY 2 - Further discussion of the Team Database Project: What is the Team Database Proposal?

 

4

2nd Mar

Gathering data. Referential integrity.
Building up complex ERDs

ACTIVITY 1 - Spot Test 1 (Time: 45 minutes max. It does not count!).

ACTIVITY 2 - Draw the ERD for the car rental problem (Q1) and implement it with sample data: 

ACTIVITY 3 - In teams work on the Team Database Proposal

ASSESSMENT (Project) - DATABASE PROPOSAL (upload to canvas) due

5

9th Mar

SQL Server installation & tables. Intro to security. DB requirements & design improvements

ACTIVITY 1 - Installing SQL Server Express. 

ACTIVITY 2 - Creating a simple three-table DB in SQL Server.

You should also install the Northwind and Pubs databases.

 

6

16th Mar

Developing questions. Conceptual, logical & physical models. Forms & sub-forms

ACTIVITY 1 - Creating forms and sub-forms step-by-step.

ACTIVITY 2 - Creating a form and a sub-forms with line totals and a grand total (not easy!) 

ACTIVITY 3 - Working on the Individual DB Design Draft

ASSESSMENT (Project) - Individual Design (submit printed copy in class to teacher) Draft due

7

23rd Mar

Analysing data. Suitable data types.
Redundancy, dependencies & normalisation

ACTIVITY 1 - Splitting tables and placing the fields into the correct tables to normalise the database.

ACTIVITY 2 - Working on the Individual DB Design Draft. 

 

8

30th Mar

Data integrity & data validation.
Groupable data. Forms & reports

ACTIVITY 1 - Looking at cascades, data validation, reports etc.

ACTIVITY 2 - Working on the Individual DB Design Update

ASSESSMENT (Project) - Individual Design (upload to Canvas) Update due

9

6th Apr

SQL Server security: logins, database roles & permissions. Class work on project

ACTIVITY 1 - Using SQL Server database roles set database-wide permissions.

ACTIVITY 2 - Using SQL Server object permissions.

ACTIVITY 3 - Team work on your Team DB Design Part 1.

 

 

Break (Thursday 9th April to Wednesday 15th April - inclusive)

10

20th Apr

Backup & restore procedures in SQL Server 
Review of client requirements. Data dictionaries

ACTIVITY 1 - Creating backup in SQL Server and performing a restore. 

ACTIVITY 2 - Try to finalise your Team DB Design (Part 1). 

ASSESSMENT (Project) - Team Design (submit printed copy in class to teacher) due

11

27th Apr

Review of normalisation.
Class work on project & documentation

ACTIVITY 1 - Breaking tables up to reflect the underlying dependencies.

ACTIVITY 2 - Start work on your Team DB Design (Part 2).

 

12

4th May

Format of security & backup plans.
Class work on project & documentation

ACTIVITY 1 - Spot Test 3 (Time: 45 minutes max. It does not count!). 

ACTIVITY 2 - Creating reports. 

ACTIVITY 3 - Keep working on your Team DB Design (Part 2). .

ASSESSMENT (Project) - DATABASE DESIGN (upload to canvas) due

13

11th May

Reports with grouped data.

Revision for Skills Review Quiz

ACTIVITY 1 - Revising for the three-part (open-book) multiple choice test next week. 

ACTIVITY 2 - Keep working on your Team DB Design (Part 2).

 

14

18th May

Project submission & demonstrations

ACTIVITY 1 - Resits for the three-part (open-book) multiple choice test. 

ACTIVITY 2 - Work on the Team DB Implementation (One form and one report each). 

ASSESSMENT (Project) - DATABASE IMPLEMENTATION due (upload to canvas)

15

25th May

Skills Review Quiz conducted.

ACTIVITY 1 - Sit the three-part (open-book) multiple choice test. 

Skills Review Quiz - Online

16

1st Jun

Re-submission of work if required.
Course & assessment feedback

VERY IMPORTANT: Make sure that you check with your teacher that you have submitted ALL components of the Team DB Project.

 

 


Learning Resources

Prescribed Texts


References


Other Resources

Other Resources

You will need laptop with charger for each class 

You may also refer to various media, websites, textbooks and e-books as indicated in Canvas


Overview of Assessment

In order to achieve competency in this unit, you must provide:

Performance Evidence

 Evidence of the ability to:

  • identify and confirm client requirements for a database application
  • design database elements including:
  • structure
  • indexes
  • queries
  • screens
  • reports
  • design secure access to the database
  • confirm final database design with the client.

Knowledge Evidence

To complete the unit requirements safely and effectively, you must:

  • explain the process of data analysis, particularly in determining data types and data structures, query and report design
  • describe the data modelling related to developing the conceptual data model
  • explain how data redundancy is identified
  • describe database management system (DBMS) fundamentals, particularly during the design phase
  • explain encryption and authentication as these apply to database security features
  • outline the functions and features of data types, and data structures
  • describe the functions, and features, of databases
  • describe logical design concepts, particularly those related to designing data structures, queries screens and reports
  • outline the object model design concepts, particularly those related to designing data structures, queries, screens and reports
  • explain the term ‘scalability’ as it applies to databases.

 Assessment Conditions

Assessment must be conducted in a safe environment where evidence gathered demonstrates consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the database field of work, and include access to:

  • equipment and materials
  • current industry accepted database software
  • network or other system for remote or multi-user access
  • business requirements
  • computer-aided software engineering (CASE) or diagramming software.

You are advised that you are likely to be asked to personally demonstrate your assessment work to your teacher to ensure that the relevant competency standards are being met.

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 Tasks

Please note that this course, ICTDBS502 - Design a database, is co-delivered and co-assessed holistically along with ICTICT509 - Gather data to identify business requirements.

 

Performance evidence

 

Evidence of the ability to:

  • identify and confirm client requirements for a database application
  • design database elements including:
    • structure
    • indexes
    • queries
    • screens
    • reports
  • design secure access to the database
  • confirm final database design with the client.

 

 

Knowledge Evidence

 

To complete the unit requirements safely and effectively, the individual must:

  • explain the process of data analysis, particularly in determining data types and data structures, query and report design
  • describe the data modelling related to developing the conceptual data model
  • explain how data redundancy is identified
  • describe database management system (DBMS) fundamentals, particularly during the design phase
  • explain encryption and authentication as these apply to database security features
  • outline the functions and features of data types, and data structures
  • describe the functions, and features, of databases
  • describe logical design concepts, particularly those related to designing data structures, queries screens and reports
  • outline the object model design concepts, particularly those related to designing data structures, queries, screens and reports
  • explain the term ‘scalability’ as it applies to databases.

 

Assessment Conditions

 

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the database field of work, and include access to:

  • equipment and materials
  • current industry accepted database software
  • network or other system for remote or multi-user access
  • business requirements
  • computer-aided software engineering (CASE) or diagramming software.

 

 

You are required to complete 2 assessmentsYou must successfully complete all sections of each assessment task to be deemed competent in this unit.

 

NOTE:  Details about specific tasks and assessment criteria will be included in the Cover Sheet(s) for each task.

 

ASSESSMENT 1 - Database Project

 

For this assessment task you will be asked to plan and develop a small business database for an on-line business from scratch in consultation with key stakeholders.  You will first need to identify information sources, gather data and confirm key client database requirements. You will work in a team to manage this project efficiently.

 

In order to be deemed competent in this task you will be expected to demonstrate proficiency in a variety of areas including the following key areas:

  • Skills in gathering and analysing data to determine requirements
  • Ability to produce ERDs for a wide variety of scenarios
  • Ability to create Access data structures to test your designs
  • Ability to normalise your tables to store data effectively
  • Ability to create objects such as forms and reports
  • Documentation of security and recovery procedures

 

Students will receive feedback or confirmation at each stage in relation to client requirements.  In many cases changes or modifications will be required.  It is therefore vital that any design documentation and other work required for each stage be submitted in a timely manner.

PROJECT PROPOSAL (Team submission) - DUE WEEK 4

    • A description of team member responsibilities and communication plan
    • An outline of the business operations, as well as purpose and scope of database project
    • A description of key business processes such product sales, stock control and ordering
    • A list of key business rules and particular design requirements
    • A timeline for project stages or deliverables, including a simple Gantt chart
    • Copies of sample business documents eg. Web forms or reports from an existing system

DATABASE DESIGN (Individual & team components) - DUE WEEK 12

    • Individual Design Draft - Draft Due Week 6
      • First draft of ERD (with cardinalities) created in VISIO with Access Relationships
    • Individual Design Update - Due Week 8
      • Updated ERD & Access Relationships (for client confirmation after normalisation)
      • Some sample data inserted into tables in Access
    • Team Design - Draft Due Week 10
      • ERD and Relationships for whole group (final conceptual & logical models)
      • Data structures implemented eg. keys, constraints, indexes & validation rules
    • Team Design – Update Due Week 12
      • Data dictionary & business rules finalised (physical model)
      • Client requirements validated. Questions on client requirements

DATABASE IMPLEMENTATION (All individual & team components) - Due Week 14

    • Final version of database with sample data entered as required
    • Queries, forms and reports as specified (Individual Submission)
    • Final project documentation including security, backup & recovery procedures

You will receive feedback at the end of each stage, including this stage.  In some cases changes or modifications will be required.

It is therefore vital that any design documentation and other work required for each stage be submitted by the due date, as per the Teaching Schedule.

In some cases printouts may be required.  You will also be expected to retain soft copies of any documents submitted.

 

ASSESSMENT 2 - Skills Review Quiz  (Conducted in Week 15)

 

For this assessment task you will need to analyse data models and design data structures, forms and reports for some simple scenarios.  You will be able to review and verify your designs on your computer with reference to Web and other resources including DBMS software.

 

You will also be questioned on the information sources (eg. key documents & questions) as well as techniques used in gathering data, such as reviewing reports.  You will also need to be able to analyse simple data to in order to confirm database requirements.

 

Some knowledge of security and data recovery concepts and procedures will also be required.

 

To be deemed competent in this task, which is in the form of a three-part online quiz, you will be expected to demonstrate your knowledge of the skills and concepts covered in all sections of the course.


Assessment Matrix

The Assessment Matrix that maps all assessments to the critical aspects of evidence, skills, knowledge and elements of competency will be available from the teacher.

Other Information

Submission Instructions

This part of the project is to be submitted by all of the team members on Canvas.  Please complete all details on the cover page so that it can be attached to the front of your documentation. 

Late submissions of work required for any stage of this project will be eligible for grading at CAG (competency Achieved) level only.

 

General Points

  • All documents are to be presented in portfolio form ie. a folder of documents submitted on Blackboard
  • Each document should include a header (eg with the name of the document and team members' names) and a footer (eg with the date and page number).
  • All team members must sign the assessment cover sheet(s).
  • Soft copies are to be retained by all team members as backups.  Google Docs is preferred.
  • RMIT academic discipline procedures will apply in cases of plagiarism.  Students should use Turnitin to avoid plagiarism.

Submission Requirements

 

Assessment tasks need to be submitted via the Learning Hub (Blackboard).

 

You should:

  • Ensure that you submit assessments on or before the due date.
  • 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.

 

 

Late Submission Procedures

 You are required to submit assessment items and/or ensure performance-based assessment is completed by the due dates. 
If you are prevented from submitting an assessment item on time, by circumstances outside your control, you may apply in advance to your teacher for an extension to the due date of up to seven calendar days.

More Information: https://www.rmit.edu.au/students/student-essentials/assessment-and-exams/assessment/extensions-of-time-for-submission-of-assessable-work
Form to use: http://mams.rmit.edu.au/seca86tti4g4z.pdf

Special Consideration Procedures

Where an extension of greater than seven days is needed, you must apply for special consideration. Applications for special consideration must be submitted no later than two working days after the assessment task deadline or scheduled examination

More Information: https://www.rmit.edu.au/students/student-essentials/assessment-and-exams/assessment/special-consideration
Online special consideration link: https://specon.rmit.edu.au/specon/

Resubmissions

If you are found to be unsuccessful in a Course Assessment Task, you will be allowed one resubmission only. Your teacher will provide feedback regarding what you need to do to improve and will set a new deadline for the resubmission.

If you are still not meeting the assessment requirements you must apply to your Program Manager in writing outlining the steps you will take to demonstrate competence in your course. Your submission will be considered by the Program Team and you will be advised of the outcome as soon as possible.

Adjustments to Assessment

In certain circumstances students may be eligible for an assessment adjustment. For more information about the circumstances under which the assessment arrangements might be granted please access the following website.

More Information: https://www.rmit.edu.au/students/student-essentials/assessment-and-exams/assessment/adjustments-to-assessment

Marking Guide (Courses delivered in accordance with competency-based assessment):

You must demonstrate that you have all the required skills/knowledge/elements in the unit of competency you are studying. You will receive feedback on each assessment task that will inform you about your progress and how well you are performing.

CA       Competency Achieved

NYC    Not Yet Competent

DNS    Did Not Submit for assessment

Course Overview: Access Course Overview