COMP SCI 1102 - Object Oriented Programming
North Terrace Campus - Semester 1 - 2022
General Course Information
Course Code COMP SCI 1102 Course Object Oriented Programming Coordinating Unit Computer Science Term Semester 1 Level Undergraduate Location/s North Terrace Campus Units 3 Contact Up to 6 hours per week Available for Study Abroad and Exchange Y Incompatible COMP SCI 2009, COMP SCI 1202, COMP SCI 2202, COMP SCI 2202B Assumed Knowledge COMP SCI 1101, COMP SCI 1201, ENG 1002, MECH ENG 1100, MECH ENG 1101, MECH ENG 1102, MECH ENG 1103, MECH ENG 1104 or MECH ENG 1105; SACE Stage 1 Mathematics or equivalent Course Description This course introduces the concepts of object-oriented programming to students with a background in the procedural paradigm. The course begins with a brief review of control structures and data types with emphasis on structured data types and array processing. It then moves on to introduce the object-oriented programming paradigm, focusing on the definition and use of classes along with the fundamentals of object-oriented design. Other topics include an overview of programming language principles, simple analysis of algorithms, basic searching and sorting techniques, memory management, an introduction to software engineering issues, and ethics in software development.
Course Coordinator: Dr Feras DayoubLecturer: Dr Rita Garcia
The full timetable of all activities for this course can be accessed from Course Planner.
Course Learning OutcomesOn successful completion of this course students will be able to:
1 Explain the steps in creating an executable program for a computer, including the intermediate representations and their purpose. 2 Manipulate binary patterns and understand the use of binary to represent numbers. 3 Apply good programming style and understand the impact of style on developing and maintaining programs. 4 Effectively use a version control system and the Linux command line tools for incremental development. 5 Explain the benefits of object oriented design and understand when it is an appropriate methodology to use. 6 Design object oriented solutions for small systems involving multiple objects. 7 Implement, test and debug solutions in C++. 8 Identify the relative merits of different algorithmic designs. 9 Independently find and interpret discipline related documentation. 10 Explain the relevance of ethics in the context of Software Engineering.
The above course learning outcomes are aligned with the Engineers Australia Stage 1 Competency Standard for the Professional Engineer.
The course is designed to develop the following Elements of Competency: 1.2 1.3 1.4 1.5 1.6 2.1 2.2 2.3 2.4 3.1 3.5 3.6
University Graduate Attributes
This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:
University Graduate Attribute Course Learning Outcome(s)
Attribute 1: Deep discipline knowledge and intellectual breadth
Graduates have comprehensive knowledge and understanding of their subject area, the ability to engage with different traditions of thought, and the ability to apply their knowledge in practice including in multi-disciplinary or multi-professional contexts.
Attribute 2: Creative and critical thinking, and problem solving
Graduates are effective problems-solvers, able to apply critical, creative and evidence-based thinking to conceive innovative responses to future challenges.
Attribute 3: Teamwork and communication skills
Graduates convey ideas and information effectively to a range of audiences for a variety of purposes and contribute in a positive and collaborative manner to achieving common goals.
Attribute 8: Self-awareness and emotional intelligence
Graduates are self-aware and reflective; they are flexible and resilient and have the capacity to accept and give constructive feedback; they act with integrity and take responsibility for their actions.
Required ResourcesAll required resources for this course will be provided online via the MyUni platform.
The course website provides links to a number of online resources to assist students in learning programming in C and C++. For those students who would also like to have a text book, we would recommend the following:
"Problem Solving with C++", 9e Global Edition, Walter Savitch, ISBN-13:9781292018249, Addison-Wesley, 2015.
Links to all course materials, assignment descriptions, announcements, etc. are available through Canvas (MyUni). You will find a link to Canvas (MyUni) on the University website.
It is your responsibility to regularly check for notices and to participate in online activities.
Learning & Teaching Activities
Learning & Teaching Modes
This course has three contact activities: lectures, practicals and workshops. Each of these activities is used to support and build on each other, they do not repeat material.
Lectures will be used primarily to introduce the core theoretical material of the course - these will be recorded online in echo 360 shortly before each lecture session. A live structured Q&A session will be held to review content and answer questions.
The practicals are focussed on developing core programming skills in C++ both individually and collaboratively. They will include a small number of individual practical exams. You should also spend a significant amount of time on programming outside of these sessions.
The workshops are hands on collaborative sessions with groups of students sharing computers working on activities that may reinforce lecture material or introduce key skills required by the practicals.
The ethics exercise covers an aread of ethics relevant to Software Engineering.
The information below is provided as a guide to assist students in engaging appropriately with the course requirements.Students are expected to spend 10-12 hours per week on this course.
There will be 5-6 hours contact time for learning and teaching activities and students will be working in groups and individually 3-5 hours to carry out the required learning and teaching activities for acquiring the expected knowledge, understanding, and skills in this course.
Learning Activities Summary
The topics covered will include:
- Basics of Computer Architecture
- Arrays and Pointers
- Programming Languages, Grammars, Compiling
- Object Oriented Design
- Classes, Objects, Inheritance
- Abstract Classes, Polymorphism
- Planning, Design
- Computational Complexity
- Sorting, Searching
- Theory of Computation
- Algorithmic and Problem Solving Strategies
- Ethics in Software Engineering
The University's policy on Assessment for Coursework Programs is based on the following four principles:
- Assessment must encourage and reinforce learning.
- Assessment must enable robust and fair judgements about student performance.
- Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
- Assessment must maintain academic standards.
Assessment Task Weighting (%) Individual/ Group Formative/ Summative Due (week)* Hurdle criteria Learning outcomes 4 Practicals 20 Group Summative weeks 1, 2, 4, 6 3. 4. 6. 7.
(weeks 8 to 11)
10 Group Summative week 11 3. 4. 6. 7. 4 Practical Exams 27 Individual Summative weeks 3, 5, 7, 12 3. 4. 6. 7. online ethics exercise 3 Group Summative week 11 9. 10. workshops 5 Group Summative weeks 1 to 12 2. 3. 4. 6. 7. final written exam 35 Individual Summative Min 40% 1. 2. 3. 5. 6. 8. 9. 10. Total 100
This assessment breakdown is registered as an exemption to the University's Assessment for Coursework Programs Policy. The exemption is related to the Procedures clause(s):
This course has a hurdle requirement. Meeting the specified hurdle criteria is a requirement for passing the course.
Details of the Australian Computer Society's Core Bode of Knowledge (CBOK) can be found in The-ACS-Core-Body-of-Knowledge-for-ICT-Professionals-CBOK
Assessment Related RequirementsHurdle Requirement: If your overall mark for the course is greater than 44 F but, your mark for the final written exam is less than 40%, your overall mark for the course will be reduced to 44 F.
Assessment DetailIndividual practical exams will take place in the practical sessions of weeks 3, 5, 7 and 12. Marks for each practical exam will be awarded by GradeScope, the web submission system, based on functionality.
In the workshop of weeks 4, 6 and 8, the previous week's practical will also be marked by practical demonstrators who will be able to give some individual feedback. No marks will be awarded if no one in a group attends the workshop in which the additional assessment takes place.
All other practicals can be undertaken individually or in a group of up to three students. A mechanism for registering groups will be provided so that only one student from each group needs to submit the work. Marks for these practicals will be awarded by the web submission system based on functionality.
In the workshop in week 12 the practical covering weeks 8 to 11 will also be marked by practical demonstrators who will be able to give some individual feedback. No marks will be awarded if no one in a group attends the week 12 workshop in which the additional assessment takes place.
Workshops will be undertaken in groups of up to three students. A mechanism for registering groups will be provided for each workshop. Marks for workshops will be awarded by the web submission system based on functionality provided that the submission is made whilst attending a workshop session.
If tutorial submissions are made by the Sunday before each tutorial session, some individual feedback will be provided. Tutorials do not contribute to the final mark for the course.
Small Group Discovery projects will be assessed as a group based on participation, presentations and/or a final report.
The final examination will assess all of the skills developed during the course and your ability to apply them as an individual.
SubmissionSubmission details for all activities are available on MyUni but the majority of your submissions will be online and may be subjected to originality testing through Turnitin or other mechanisms. You will receive clear and timely notice of all submission details in advance of the submission date.
Grades for your performance in this course will be awarded in accordance with the following scheme:
M10 (Coursework Mark Scheme) Grade Mark Description FNS Fail No Submission F 1-49 Fail P 50-64 Pass C 65-74 Credit D 75-84 Distinction HD 85-100 High Distinction CN Continuing NFE No Formal Examination RP Result Pending
Further details of the grades/results can be obtained from Examinations.
Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.
Final results for this course will be made available through Access Adelaide.
The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.
SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.
- Academic Integrity for Students
- Academic Support with Maths
- Academic Support with writing and study skills
- Careers Services
- International Student Support
- Library Services for Students
- LinkedIn Learning
- Student Life Counselling Support - Personal counselling for issues affecting study
- Students with a Disability - Alternative academic arrangements
- YouX Student Care - Advocacy, confidential counselling, welfare support and advice
Policies & Guidelines
This section contains links to relevant assessment-related policies and guidelines - all university policies.
- Academic Credit Arrangements Policy
- Academic Integrity Policy
- Academic Progress by Coursework Students Policy
- Assessment for Coursework Programs Policy
- Copyright Compliance Policy
- Coursework Academic Programs Policy
- Elder Conservatorium of Music Noise Management Plan
- Intellectual Property Policy
- IT Acceptable Use and Security Policy
- Modified Arrangements for Coursework Assessment Policy
- Reasonable Adjustments to Learning, Teaching & Assessment for Students with a Disability Policy
- Student Experience of Learning and Teaching Policy
- Student Grievance Resolution Process
Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.
The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.