Registry

Module Specifications

Current Academic Year 2012 - 2013
Please note that this information is subject to change.

Module Title	OO Design and Implementation
Module Code	CA212
School	School of Computing
Online Module Resources
Module Co-ordinator	Semester 1: Donal Fitzpatrick Semester 2: Donal Fitzpatrick Autumn: Donal Fitzpatrick
Module Teacher	Donal Fitzpatrick
NFQ level	8	Credit Rating	5
Pre-requisite	None
Co-requisite	None
Compatibles	None
Incompatibles	None

Description

This course introduces programming in C and C++. All aspects of the C++ language are introduced as well as professional coding techniques. The UML notation is introduced as a design notation (Class and State Diagrams).

Learning Outcomes

1. Design software systems using the Object-Oriented programming paradigm.
2. Specify simple software systems using the UML notation.
3. Implement software systems using the C++ programming language.
4. Utilise existing c++ libraries of datastructures in order to employ the philosophy of software reuse
5. Apply problem-solving techniques to novel scenarios
6. Communicate design work in a formal manner while citing the work of others which has contributed to the students's own work.

Workload	Full-time hours per semester
*Type*	*Hours*	*Description*
Total Workload: 0

All module information is indicative and subject to change. For further information,students are advised to refer to the University's Marks and Standards and Programme Specific Regulations at: http://www.dcu.ie/registry/examinations/index.shtml

Indicative Content and Learning Activities

Basic I/O.
Control Flow.

Iteration and Recursion.
Arrays.

Functions and parameters.
Pointers and references.

Structs.
Classes.

Constructors & Destructors.
Const.

Revision of Object-Oriented concepts and terminology.
Modelling with UML.

Inheritance in C++.
Friends.

Operator overloading.
Files.

Abstraction, Coupling and Cohesion.

Assessment Breakdown
Continuous Assessment	30%	Examination Weight	70%

Course Work Breakdown
Type	Description	% of total	Assessment Date
Assignment	The students will be presented with a medium-scale exercise which will enable them to design, implement and test a software system. It is recommended that this should be carried out in teams of two or three persons; thereby mirroring real-world scenarios where software is developed in teams.	50%	Once per semester

Reassessment Requirement
Resit arrangements are explained by the following categories; 1 = A resit is available for all components of the module 2 = No resit is available for 100% continuous assessment module 3 = No resit is available for the continuous assessment component
This module is category 3

Indicative Reading List