Note: This unit version is currently being edited and is subject to change!

COMP9220: Object-Oriented Design (2019 - Semester 1)

Download UoS Outline

Unit: COMP9220: Object-Oriented Design (6 CP)
Mode: Normal-Day
On Offer: Yes
Level: Postgraduate
Faculty/School: School of Computer Science
Unit Coordinator/s: A/Prof Scholz, Bernhard
Session options: Semester 1
Versions for this Unit:
Campus: Camperdown/Darlington
Pre-Requisites: None.
Prohibitions: COMP5028 OR INFO3220.
Brief Handbook Description: This unit introduces essential object-oriented design methods and language mechanisms, especially the principles of modelling through Rational Unified Process and agile processes using Unified Modeling Language (UML) and Java or C++, both of which are industry standard. Students experience the process of object-oriented analysis, object-oriented design, implementation and testing by building a real-world application. Java or C++ is used as the implementation language and a special emphasis is placed on those features of Java or C++ that are important for solving real-world problems. Advanced software engineering features, including exceptions and namespaces are thoroughly covered.
Assumed Knowledge: INFO1103 OR INFO1113 OR COMP9103. Students enrolled in COMP9220 are assumed to have Java or C++ programming experience (or equivalent experience in another object-oriented programming language). This unit does have assessments with complex coding tasks.
Department Permission Department permission is required for enrollment in this session.
Timetable: COMP9220 Timetable
Time Commitment:
# Activity Name Hours per Week Sessions per Week Weeks per Semester
1 Lecture 2.00 1 13
2 Tutorial 1.00 1 13
3 Independent Study 9.00 1 13
4 Project Work - own time 6.00 1 13
T&L Activities: Tutorial: Tutorial

Independent Study: Reading relevant text book chapters, doing take-home quizzes or homework

Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.

(4) Design (Level 3)
1. Understand how to analyze a problem based on user requirements
2. Transform the domain-model from your analysis into an effective object-oriented design.
3. Understand how and when to use a few important GoF design patterns.
(2) Engineering/ IT Specialisation (Level 3)
4. Construct one or more models of the problem space and express the results of analysis in proper UML diagrams.
(1) Maths/ Science Methods and Tools (Level 3)
5. Understand the principles of quality object-oriented design and apply them through out the design stage
Assessment Methods:
# Name Group Weight Due Week Outcomes
1 Lab Skills No 10.00 Multiple Weeks 1, 2, 3, 4, 5,
2 Assignment No 5.00 Week 4 2, 3, 4,
3 Quiz No 5.00 Week 5 1, 2,
4 Assignment No 5.00 Week 7 2, 3, 4,
5 Quiz No 5.00 Week 8 1, 2, 4,
6 Assignment No 10.00 Week 10 2, 3, 4,
7 Assignment Yes 10.00 Week 12 1, 2, 3, 4, 5,
8 Final Exam No 50.00 Exam Period 1, 2, 3, 5,
Assessment Description: Assignment: (Individual) Practical Object-Oriented Design and Implementation assignment.

Assignment: (Individual) Practical Object-Oriented Design and Implementation assignment.

Assignment: (Individual) Practical Object-Oriented Design and Implementation assignment.

Assignment: Practical Object-Oriented Design and Implementation assignment.

Quiz: Course content pre-exam quiz.

Quiz: Course content pre-exam quiz.

Final Exam: Final Exam (open book)
Grading:
Grade Type Description
Standards Based Assessment Final grades in this unit are awarded at levels of HD for High Distinction, DI (previously D) for Distinction, CR for Credit, PS (previously P) for Pass and FA (previously F) for Fail as defined by University of Sydney Assessment Policy. Details of the Assessment Policy are available on the Policies website at http://sydney.edu.au/policies . Standards for grades in individual assessment tasks and the summative method for obtaining a final mark in the unit will be set out in a marking guide supplied by the unit coordinator.
Minimum Pass Requirement It is a policy of the School of Computer Science that in order to pass this unit, a student must achieve at least 40% in the written examination. For subjects without a final exam, the 40% minimum requirement applies to the corresponding major assessment component specified by the lecturer. A student must also achieve an overall final mark of 50 or more. Any student not meeting these requirements may be given a maximum final mark of no more than 45 regardless of their average.
Policies & Procedures: IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism.

In assessing a piece of submitted work, the School of Computer Science may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so.

Other policies

See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.
Recommended Reference/s: Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
Note on Resources:

Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp

Week Description
Week 1 Introduction, course overview, Object-Orientation
Week 2 Object-Orientation and Java
Week 3 UML
Week 4 Analytical Modelling and Design Modelling
Assessment Due: Assignment
Week 5 Design Modelling and Mapping
Assessment Due: Quiz
Week 6 Design Pattern
Week 7 Design Pattern
Assessment Due: Assignment
Week 8 Design Pattern
Assessment Due: Quiz
Week 9 Design Pattern
Week 10 Design Pattern
Assessment Due: Assignment
Week 11 Design Pattern
Week 12 Design Pattern
Assessment Due: Assignment
Week 13 Course Revision
STUVAC (Week 14) This week is left free for independent study
Exam Period Any Exam or Quiz worth more than 30% of the final assessment will be scheduled in this two week period.
Assessment Due: Final Exam

Course Relations

The following is a list of courses which have added this Unit to their structure.

Course Year(s) Offered
Master of Professional Engineering (Software) 2015, 2016, 2017
Graduate Diploma in Computing 2015, 2016, 2017
Graduate Diploma in Health Technology Innovation 2015
Graduate Diploma in Information Technology 2015, 2016, 2017
Master of Health Technology Innovation 2015
Master of Information Technology 2015, 2016, 2017
Master of Information Technology Management 2015, 2016, 2017
Master of IT / Master of IT Management 2015, 2016, 2017

Course Goals

This unit contributes to the achievement of the following course goals:

Attribute Practiced Assessed
(6) Communication and Inquiry/ Research (Level 3) No 0%
(7) Project and Team Skills (Level 3) No 0%
(8) Professional Effectiveness and Ethical Conduct (Level 3) No 0%
(5) Interdisciplinary, Inclusiveness, Influence (Level 3) No 0%
(4) Design (Level 3) No 71.15%
(2) Engineering/ IT Specialisation (Level 3) No 12.33%
(3) Problem Solving and Inventiveness (Level 3) No 0%
(1) Maths/ Science Methods and Tools (Level 3) No 16.5%

These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.