Note: This unit is an archived version! See Overview tab for delivered versions.
COMP5028: Object-Oriented Design (2014 - Semester 1)
Unit: | COMP5028: Object-Oriented Design (6 CP) |
Mode: | Normal-Day |
On Offer: | Yes |
Level: | Postgraduate |
Faculty/School: | School of Computer Science |
Unit Coordinator/s: |
Dr Takatsuka, Masahiro
|
Session options: | Semester 1 |
Versions for this Unit: |
Campus: | Camperdown/Darlington |
Pre-Requisites: | None. |
Prohibitions: | 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 work in small groups to 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 name spaces are thoroughly covered. |
Assumed Knowledge: | Students enrolled in COMP5028 are assumed to have elementary Java programming experience or equivalent experience in another object oriented programming language. This unit does not have assessment with heavy coding task. But some knowledge in object-oriented programming would have big impact on learning experience. |
Lecturer/s: |
Dr Takatsuka, Masahiro
|
|||||||||||||||||||||||||
Timetable: | COMP5028 Timetable | |||||||||||||||||||||||||
Time Commitment: |
|
|||||||||||||||||||||||||
T&L Activities: | Tutorial: Tutorial Independent Study: Reading relevant text book chapters, doing take-home quizzes or homework |
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
Attribute Development Method | Attribute Developed |
Majority of the tutorials, quizzes and homework requests students to read system development cases and to produce designs that conforming to certain principles. | Design (Level 3) |
Students will learn core skills in object-Oriented analysis and design applicable to information systems in general. | Engineering/IT Specialisation (Level 3) |
This course covers modularized design, low coupling, high cohesion principles which are fundamental skills engineering. The ability to discover generalization and abstraction is also key in science discipline. | Maths/Science Methods and Tools (Level 3) |
Various case studies are used in the tutorial and quizzes. Students are expected to find case related information from the textbook and the Internet. | Information Seeking (Level 3) |
Students will work in groups in all the tutorials | Project and Team Skills (Level 3) |
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
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.
Design (Level 3)Assessment Methods: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of IT 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. |
Prescribed Text/s: |
Note: Students are expected to have a personal copy of all books listed.
|
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 |
Week 2 | Use Case Modelling |
Week 3 | Domain Modelling |
Week 4 | Domain Modelling II |
Assessment Due: Assignment | |
Week 5 | UML diagrams |
Assessment Due: Quiz | |
Week 6 | GRASP Patterns/Mapping design to code |
Week 7 | GoF Patterns I |
Assessment Due: Assignment | |
Week 8 | GoF Pattern II |
Assessment Due: Quiz | |
Week 9 | GoF Pattern III |
Week 10 | Mid-term Review, feedback on quizzes |
Assessment Due: Assignment | |
Week 11 | GoF Pattern IV |
Week 12 | Design persistence framework |
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) | 2010, 2011, 2012, 2013, 2014 |
Software Engineering / Arts | 2011, 2012, 2013, 2014 |
Software Engineering / Commerce | 2010, 2011, 2012, 2013, 2014 |
Software Engineering / Medical Science | 2011, 2012, 2013, 2014 |
Software Engineering / Science | 2011, 2012, 2013, 2014 |
Course Goals
This unit contributes to the achievement of the following course goals:
Attribute | Practiced | Assessed |
Design (Level 3) | Yes | 71.15% |
Engineering/IT Specialisation (Level 3) | Yes | 12.33% |
Maths/Science Methods and Tools (Level 3) | Yes | 16.5% |
Information Seeking (Level 3) | Yes | 0% |
Professional Conduct (Level 3) | No | 0% |
Project and Team Skills (Level 3) | Yes | 0% |
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 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.