Course Title: Model preferred system solutions

Part B: Course Detail

Teaching Period: Term1 2011

Course Code: COSC5330C

Course Title: Model preferred system solutions

School: 650T TAFE Business

Campus: City Campus

Program: C5194 - Diploma of Information Technology (General)

Course Contact : Paul Lewis

Course Contact Phone: +61 3 9925 1615

Course Contact Email:paul.lewis@rmit.edu.au


Name and Contact Details of All Other Relevant Staff

Nominal Hours: 30

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 defines the competency required to fit a physical model into the design phase of the methodology for a small database system.


National Codes, Titles, Elements and Performance Criteria

National Element Code & Title:

ICAA5046A Model preferred system solutions

Element:

1. Review and confirm requirements information and any existing models

Performance Criteria:

1.1 Review requirements information and clarify areas that are not understood

1.2 Identify organisational standards for developing models, and check the model development method for consistency with organisational goals

1.3 Identify assumptions and incorporate into modelling process

1.4 Identify goals and resolve into tasks required to be performed to obtain the goals

1.5 Define internal tasks needed to perform identified goals

Element:

2. Resolve conflicts and inconsistencies

Performance Criteria:

2.1 Identify missed opportunities arising from previous and current model development

2.2 Identify bottlenecks, overlooked functionalities and other issues and resolve with client input as required

Element:

3. Build and test model

Performance Criteria:

3.1 Develop model based on existing architecture

3.2 Document details of model according to agreed project or organisational standards

3.3 Develop model according to project deliverables and acceptance criteria and within a determined timeframe and project constraints

3.4 Test model against the test plan

3.5 Document test data to ensure test procedures accurately and thoroughly validate performance of model

Element:

4. Ensure that the model represents a workable solution

Performance Criteria:

4.1 Ensure a consensus view of key IT stakeholders is represented in the model

4.2 Ensure the model is checked by key IT stakeholders to confirm common understanding of the model and the proposed solution

4.3 Submit the model to appropriate person for sign-off


Learning Outcomes



Details of Learning Activities

Learning activities will include laboratory-based sessions on a variety of topics as shown in the Teaching Schedule below. They 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.


Teaching Schedule

The total number of scheduled hours of teaching, learning and assessment involved in this course includes all planned activities including face to face classes, lectures, workshops and seminars, workplace visits, online learning and other forms of structured teaching and learning.

The total scheduled hours also covers the amount of effort required to undertake, evaluate and complete all assessment requirements, including observation of work performance, discussions with supervisors and others providing third party evidence and one on one and group assessment sessions with students.

Competency Elements
* All elements for this competency (elements 1 – 4) are covered each week.

WeekWeek CommencingTopics / Learning ActivitiesAssessment Tasks / Elements Covered *
17th Feb 2011Course introduction & overview. Relational database concepts. Web forms 
214th Feb 2011Business requirements. Introduction to ERDs. 1:M relationships & Foreign keysProject teams & topics selected
321st Feb 2011More on ERDs. M:N relationships & bridging tablesInitial project specifications handed out
428th Feb 2011Referential integrity. Data entry for 1:M and M:N relationshipsProject Proposal due
57th Mar 2011Building up more complex ERDs 
6

14th Mar 2011

Mon Labour Day PH

ERDs & dependenciesProject Stage 1 due
721st Mar 2011 Redundancy, dependencies & normalisation 
828th Mar 2011More on normalisationProject Stage 2 due
94th Apr 2011Review of work to date. Class work on projects  
1011th Apr 2011Data dictionaries. Database design improvementsProject Stage 3 due
 VacationMid-Semester (Easter) Break Thu 21st - Wed 27th Apr 2011
1125th Apr 2011Introduction to basic SQL including functions  
122nd May 2011Two-table queries in SQL. Table aliasesProject Stage 4 due
139th May 2011Class work on project  
1416th May 2011Revision for final testFinal Version of Project due
1523rd May 2011Final graded test conductedFinal Graded Test
1630th May 2011Course review. Assessment feedback  
Students who have been granted special consideration or are required to re-submit, will be able to submit/sit their assessment by arrangement with the class teacher in weeks 17 or 18.


Learning Resources

Prescribed Texts

There is no prescribed textbook for this course


References

Pratt, P & Adamski, J (2008), Concepts of Database Management, 6th edn, Thomson Course Technology

1423901479

Rob, P & Coronel, C (2009), Database Systems: Design, Implementation and Management, 8th edn, Thomson Course Technology

1423902017


Other Resources


Overview of Assessment

Assessment tasks will include a portfolio of in-class exercises, a group project with associated documentation, and a combined theory and practical test.

You will be provided with feedback throughout the course to check your progress.

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.


Assessment Tasks

Class Work Submissions

Student will be expected to demonstrate class work and submit screen shots of solutions to certain class exercises. Work is to be submitted within one week of the corresponding class exercise.

Database Project

  • Project Proposal: Initial draft of proposal outlining business operations, business rules & project requirements
  • Project Stage 1: First draft of Entity Relationship Diagram (ERD) created in Visio
  • Project Stage 2: Database with Relationships created in Access. Some sample data inserted into tables
  • Project Stage 3: Relationships in Access updated with tables fully normalised
  • Project Stage 4: Data dictionary finalised. Data entry completed
  • Final Version of Project: Final Access database with SQL queries. Fully-updated versions of all project documentation

 

 

 

 

Final Graded Test

This will be an in-lab practical and theory assessment. Students may be required to work on Access databases.


Assessment Matrix

ICAA5046B – Model preferred systems solutionClass Work Submissions
CA/NYC (25%)
Database Project
CA/NYC (40%)
Final Graded Test
35%
Element 1:  Review and confirm requirements information and any existing modelsYYY
Element 2:   Resolve conflicts and inconsistenciesYYY
Element 3:   Build and test modelYYY
Element 4:  Ensure that the model represents a workable solution YYY

Other Information

Competency and Grading Requirements:

To be deemed competent students must demonstrate an understanding of all elements of this competency. Assessment methods have been designed to measure achievement of each competency in a flexible manner over multiple tasks.

Students are advised that they are likely to be asked to personally demonstrate their work to their teacher to ensure that the relevant competency standards are being met.

All competency-based assessments for this course must be completed in order to achieve a CA (Competency Achieved) award.

Each assessment task will also carry a numerical weighting to be used for grading purposes. The grade applied will only be awarded if a CA has been achieved in all compulsory assessment tasks.

If a student has been assessed as NYC (Not Yet Competent) in any of the assessment tasks, the weighting will carry no value until the student has obtained a CA.

If a CA is achieved on re-assessment, a maximum mark of 50% of the original weighting will be granted for that assessment.

Re-assessments will only be granted to students who were either unsuccessful in the first attempt, or have an approved application for special consideration.

A final graded test worth 35% will be offered to students who have achieved CA.

Course Overview: Access Course Overview