DCU Home | Our Courses | Loop | Registry | Library | Search DCU


Module Specifications

Archived Version 2013 - 2014

Module Title OO Analysis and Design
Module Code CA314
School School of Computing

Online Module Resources

Module Co-ordinatorDr Liam TuoheyOffice NumberL2.36
NFQ level 8 Credit Rating 5
Pre-requisite None
Co-requisite None
Compatibles None
Incompatibles None

This module introduces students to the main ideas in object-oriented analysis and design, and gives them practical, team-based experience in applying these ideas, using UML and an appropriate toolset.

Learning Outcomes

1. Apply the O-O approach to analyse and design small-scale systems, starting from an initial statement of requirements
2. Demonstrate a detailed practical knowledge of the main elements of the Unified Modeling Language (UML)
3. Understand the main software verification activities, particularly of testing for O-O systems
4. Develop and implement system tests based on use cases
5. Understand, in practical terms, key processes and constraints arising in software development by a team, from initiation to system test and demonstration
6. Participate effectively as a (junior) team member within a software develpment team

Workload Full-time hours per semester
Type Hours Description
Lecture24No Description
Tutorial6No Description
Total Workload: 30

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

Essential differences between a functional and an O.O. approach to analysis and design.

Use Case models.

Class Models.

Modelling interaction between classes (e.g. collaboration diagrams, sequence diagrams).

Modelling state and activity ( e.g. STATECHARTS, Activity Diagrams).

OCL (informally)

O.O. Analysis and design process (e.g. 'Unified Method').

Tools to support O.O. Analysis and Design ( e.g. Rational Rose, WithClass 2000).

Testing, esp. system tests based on use cases & O-O considerations

Assessment Breakdown
Continuous Assessment25% Examination Weight75%
Course Work Breakdown
TypeDescription% of totalAssessment Date
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
Indicative Reading List

  • Stevens, P., Pooley, R.: 0, Using UML: Software Engineering with Objects and Components, First "update" edition or later editions, Addison Wesley,
  • Stiller, E., LeBlanc, C.: 2002, Project-based Software Engineering. An object-oriented approach, Addison Wesley,
  • Braude, E.: 2004, Software Design. from programming to architecture, Wiley,
  • Bruegge, B., Dutoit, A.H.: 2004, Object-Oriented Software Engineering. Using UML, Patterns, and Java, Second, Various chapters, particularly 1-5, Pearson/Prentice-Hall,
  • OMG: 0, OMG Unified Modeling Language Specification, For reference only,
Other Resources

Programme or List of Programmes
CASEBSc in Computer Applications (Sft.Eng.)
ECSAStudy Abroad (Engineering & Computing)
ECSAOStudy Abroad (Engineering & Computing)