Course Title: Apply introductory object-oriented language skills
Part B: Course Detail
Teaching Period: Term1 2012
Course Code: COSC6081C
Course Title: Apply introductory object-oriented language skills
School: 650T TAFE Business
Campus: City Campus
Program: C5194 - Diploma of Information Technology (General)
Course Contact : Radhu Punchanathan
Course Contact Phone: +61 3 99251409
Course Contact Email:radhu@rmit.edu.au
Name and Contact Details of All Other Relevant Staff
Nominal Hours: 60
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 course covers the competency required to undertake introductory programming tasks using an object-oriented programming language. Competency includes using existing tools, documentation, debugging and testing techniques in support of the programming activities.
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: |
ICAB4219A Apply introductory object oriented language skills |
Element: |
1. Apply basic language syntax and layout |
Performance Criteria: |
1.1. Demonstrate understanding and application of basic language syntax rules and best practices |
Element: |
2. Apply basic object-oriented principles in the target language |
Performance Criteria: |
2.1. Implement a class that contains primitive member/instance variables |
Element: |
3. Debug code |
Performance Criteria: |
3.1. Use an integrated development environment, in particular the language debugging facilities, to debug code |
Element: |
4. Document activities |
Performance Criteria: |
4.1. Follow organisational guidelines for developing maintainable code and adhere to the provided coding standards when documenting activities |
Element: |
5. Test code |
Performance Criteria: |
5.1. Create and conduct simple tests to confirm code meets design specification |
Element: |
6. Create an application |
Performance Criteria: |
6.1. Develop a solution when provided with a basic object-oriented design document |
Learning Outcomes
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
| Week | Week Commencing | Topics | Assessment |
| 1 | 6th Feb 2012 |
Pre-training review: • RPL • LLN 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 HTML • An HTML5 template & HTML tags • Validation of HTML pages |
|
| 2 | 13th Feb 2012 | • Class/Object Attributes • Encapsulation • Methods • Constructors & UML Class Diagrams |
|
| 3 | 20th Feb 2012 | • Flow Control in Java (Selection & Repetition/Iteration/Looping) | Major Project available to students |
| 4 | 27th Feb 2012 | • Eclipse & Debugging Techniques | Task 1: In-class worksheet |
| 5 | 5th Mar 2012 | • Revision | |
| 6 | 12th Mar 2012 (Monday, Labour Day) |
• Assessment 2 in Labs | Task 2: Theory and Practical Test |
| 7 | 19th Mar 2012 | • Arrays & Array Processing Algorithms • Testing Code |
|
| 8 | 26th Mar 2012 | • Multi-Tier Programming • Method & Constructor Overloading • Polymorphism and Cohesion & Coupling |
Task 3 - Project Progress 1 due |
| 9 | 2nd Apr 2012 | • Relationships Between Classes • Inheritance & Aggregation/Inclusion |
|
| Mid semester break (5 April to 11 April) | |||
| 9 | 9th Apr 2012 | • Relationships Between Classes • Inheritance & Aggregation/Inclusion |
|
| 10 | 16th Apr 2012 | • Text File Reading and Writing • Exceptions |
|
| 11 | 23rd Apr 2012 | • Javadoc • Eclipse – Javadoc • Program Debugging |
Task 3 - Project Progress 2 due |
| 12 | 30th Apr 2012 | • Project Work | |
| 13 | 7th May 2012 | • Revision | |
| 14 | 14th May 2012 | • Project Due | Task 3 – Final Project due |
| 15 | 21st May 2012 | • Project Review | |
| 16 | 28th May 2012 | • Review and Feedback | |
| 17 | 4th Jun 2012 | Re-submission of work if required |
Learning Resources
Prescribed Texts
Gerard Sparke, The Java Way, 3rd Edition, ISBN 978-0-646-54746-6 |
References
Kathy Sierra & Bert Bates, Head First Java, 2nd Edition, (Sebastopol: O'Reilly Media, 2005), ISBN 978-0-596-00920-5. |
|
James Overton, Simple Program Design, (Thomson Learning) ISBN 978-0-17-012895-7. |
Other Resources
Other materials will include worksheets distributed by the teacher in class and various Websites which will be indicated.
Overview of Assessment
Assessment may incorporate a variety of methods including technical requirements documentation, homework and in class exercises, written tests, practical problem solving exercises, presentations, practical tests and a final exam. Students are advised that they are likely to be asked to personally demonstrate their assessment work to their teacher to ensure that the relevant competency standards are being met. Students will be provided with feedback throughout the course to check their progress.
Assessment Tasks
You are required to complete 3 Assessments. You must successfully complete all 3 assessments to be deemed competent in this unit.
Task 1: In-class worksheet (Date: Done in labs in week 4)
For this task you are required to complete an in-class worksheet on basic Java syntax seen so far.
Task 2: Theory and Practical Test (Date: Done in labs in week 6)
This is a part theory and part practical test where students will be asked to design a UML class diagrams using object-oriented concepts and create Java programs using the correct syntax. To be deemed competent in this assessment you should be able to demonstrate all the above requirements under a supervised time-bound condition.
Task 3 – Major Project (Due Dates: End of Weeks 8, 11 and 14)
This is a major project which is assessed progressively in 3 stages as Project progress1, Project progress2 and the Final Project.
Scenario: You are a developer within a small software consulting firm and have been assigned to build a new software application for a client. Your application has to be submitted to, and approved by, your Project Leader (in this case your lab teacher). There are three (3) stages involved in submitting your task. The first stage involves submission at the beginning of class in semester week 8, Part 2 in semester week 11, and Part 3 before the end of class, in semester week 14.
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 http://rmit.edu.au/browse;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:
1. LEVEL OF INDEPENDENCE, INITIATIVE, ENTERPRISE AND PERFORMANCE OF WORK TASK
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 introductory programming tasks using an object-oriented programming language.
2. DEMONSTRATED BREADTH OF UNDERPINNING KNOWLEDGE AND A WILLINGNESS TO CONTINUE LEARNING
We are looking for depth of understanding of the key concepts and knowledge required in programming tasks using an object-oriented programming language. You should be able to demonstrate a thorough understanding of all applicable Object-Oriented concepts in all the assessment tasks.
3. TECHNIQUES & PROCESSES, TECHNOLOGY SKILLS AND PROBLEM SOLVING
We are looking for appropriate use of technology to assist in presenting all tasks clearly and suitable for the intended audience. You also need to show an understanding of the kinds of problems that can arise in managing Object-oriented programming systems and how these might be addressed..
4. WORK ORGANISATION, PLANNING AND SELF MANAGEMENT
We expect to see ongoing uploading of information into Blackboard as per course requirements and timely submission of all required assessment tasks.
5. COMMUNICATION, PEOPLE NETWORKING, LANGUAGE AND INTERPERSONAL SKILLS AND TEAMWORK
We expect to see contributions to relevant discussions in class and with your other members. We expect to see your tasks should demonstrate a very good understanding of strategies for a collaborative approach to object oriented programming in the workplace.
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
Further information regarding the application of the grading criteria will be provided by your teacher.
Course Overview: Access Course Overview