Course Title: Apply introductory object-oriented language skills

Part B: Course Detail

Teaching Period: Term2 2015

Course Code: COSC6113C

Course Title: Apply introductory object-oriented language skills

School: 650T Vocational Business Education

Campus: City Campus

Program: C5300 - Diploma of Information Technology

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.

This unit is delivered using a blend of classroom based and self-paced learning activities.


National Codes, Titles, Elements and Performance Criteria

National Element Code & Title:

ICAPRG406A 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
1.2 Select and use language data types, operators and expressions to create clear and concise code
1.3 Use the appropriate language syntax for sequence, selection and iteration constructs
1.4 Use a modular programming approach within member or function logic
1.5 Apply arrays, including arrays of objects to introductory programming tasks
1.6 Use standard-array processing algorithms
1.7 Use the facilities of the language to read and write data from and to text files and record outcomes

Element:

3. Debug code

Performance Criteria:

3.1 Use an integrated development environment, in particular the language debugging facilities, to debug code
3.2 Interpret compiler or interpreter messages to resolve syntax errors and use debugging techniques to resolve logic errors.

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
4.2 Apply internal documentation to all code created and use documentation tools available in the target language when documenting activities

Element:

5. Test code

Performance Criteria:

5.1 Create and conduct simple tests to confirm code meets design specification
5.2 Document the tests performed and results achieved

Element:

6. Create an application

Performance Criteria:

6.1 Develop a solution when provided with a basic object-oriented design document
6.2 Refer to appropriate documentation for the language

Element:

2. Apply basic object-oriented principles in the target language

Performance Criteria:

2.1 Implement a class that contains primitive member or instance variables
2.2 Implement a class that contains multiple options for object construction
2.3 Implement a class that uses user-defined aggregation (object instance or member variables)
2.4 Use the facilities provided in the language to implement inheritance to at least two levels of depth
2.5 Use polymorphism at a simple level through inheritance to enable easy extension of code.


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

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:
o Recognition of Prior Learning and Credit Transfers
o Assessment of current skills and knowledge
• Competency/Grading Criteria
• Plagiarism
• Appeals
• Extensions
• Feedback
• Privacy
• Submission requirements
• Resubmission policy
• Where to get support
• Student responsibilities

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.

Week

Week Commencing Topics Assessment
1 06/07/15

Introduction to the Course including:
• Course requirements
• Course support documents
• Course Blackboard access
• Accuracy of enrolment
• Assessment requirements/Cover Sheets
• Reminder re Plagiarism
• Reminder re Appeals
• Extensions/Resubmissions
• Feedback in this course
• Reminder re submission requirements
• Getting help
Introduction to COSC6113C - Programming

 
2 13/07/15 IDE, Installing JDK, using variables, Data types, operators and Java syntax  
3 20/07/15 Selection and repetition statements Assessment 1: Project specifications issued
4 27/07/15 Introduction to Object Oriented programming, classes, objects, attributes and methods  
5 03/08/15 UML Class diagrams, relationships - aggregation Project draft check and feedback
6 10/08/15 Project Submissions and feedback Assessment 1: Project Stage 1 due
7 17/08/15 Getting input, Strings, API’s, Arrays and ArrayLists  
8

24/08/15

Inheritance  
Mid-Semester Break (Monday 31st Aug to Friday 4th Sept – dates included)
9 07/09/15 Revision and preparation for Assessment 2  
10 14/09/15 Assessment 2: Skills review (held in class rooms) Assessment 2: Skills review
11 21/09/15 Project work Project draft check and feedback
12 28/09/15 Project Submissions and feedback Assessment 1: Project Stage 2A due
13 05/10/15 Introduction to creating mobile applications  
14 12/10/15 Creating mobile applications – a case study  
15 19/10/15 Project Work  Assessment 1: Project Stage 2B due
16 26/10/15 Feedback & review, re-submissions 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

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

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.


Assessment Tasks

Critical aspects of assessment
Evidence of the ability to:
• use an application program to design and build standard reusable software modules in response to a design specification
• generate code documentation
• undertake testing to confirm that the created application meets the original specification and solves original problem.

You are required to complete 2 assessments. You must successfully complete Assessment 1 and Assessment 2 to be deemed competent in this unit.

Assessment 1: Project (Due Dates: Weeks 6,12 and 15)

This is a major project which is assessed progressively in 2 stages as Project Stage 1(week 6) and Projects Stage 2A(week 12) and Project Stage 2B(week 15).
Note: Late submissions of work required for any stage of this project will be eligible for grading at CAG (Competency Achieved) level only.

Project Description / 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 two (2) stages involved in submitting your task. As part of work integrated learning (WIL) you will be developing a mobile application in stage 2 for a small business.
Stage 1 deliverables (Due Week 6):
• A UML class diagram of all classes, their attributes, methods, etc., and showing their relationships to one another.
• The entire java source code.
Stage 2 deliverables:
Part A:(Due Week 12)
• A UML class diagram of all classes (including all subclasses and driver classes), their attributes, methods, etc., and showing their relationships to one another. This diagram should also show which tiers the classes are in.
• The entire java source code showing inheritances and object oriented concepts.
Part B:(Due Week 15)
• As part of learning to create an application you will be developing a mobile application for a client. The tools, details and specifications will be provided by your teacher on behalf of the client.


Assessment 2: Skills review (Test) - Done in labs in week 10
This is a part theory and part practical test where students will be asked to design and develop a small application in Java using object-oriented concepts. This assessment is done under a supervised time-bound condition.
 


Assessment Matrix

The Assessment Matrix that maps all assessments to the critical aspects of evidence, skills, knowledge and elements is available in the VBE Learning & Assessment Tool for this course

Other Information

Submission Requirements

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 each assessment task 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.
• Projects must be submitted via the learning hub (Blackboard). 

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: http://www.rmit.edu.au/students/assessment/extension

Form to use: http://mams.rmit.edu.au/seca86tti4g4z.pdf

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: http://www.rmit.edu.au/browse;ID=g43abm17hc9w

Form to use: http://mams.rmit.edu.au/8a5dgcaqvaes1.pdf

Resubmissions (VET Programs):

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. The highest grade you will receive if your resubmission is successful is “CAG”.

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: http://rmit.edu.au/browse;ID=7usdbki1fjf31

Marking Guide (Competency):
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.

Marking Guide (Grading)
After achieving competency we then grade your performance in the unit and you will achieve one of the following grades:

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