DCU Home | Our Courses | Loop | Registry | Library | Search DCU
<< Back to Module List

Module Specifications.

Current Academic Year 2024 - 2025

All Module information is indicative, and this portal is an interim interface pending the full upgrade of Coursebuilder and subsequent integration to the new DCU Student Information System (DCU Key).

As such, this is a point in time view of data which will be refreshed periodically. Some fields/data may not yet be available pending the completion of the full Coursebuilder upgrade and integration project. We will post status updates as they become available. Thank you for your patience and understanding.

Date posted: September 2024

Module Title OO Analysis & Design
Module Code CA314 (ITS) / CSC1046 (Banner)
Faculty Engineering & Computing School Computing
Module Co-ordinatorRenaat Verbruggen
Module Teachers-
NFQ level 8 Credit Rating 5
Pre-requisite Not Available
Co-requisite Not Available
Compatibles Not Available
Incompatibles Not Available
None
Array
Description

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
ProjectPart 1 of an extended team-based SW development project (only the main approximate timing is specified)12%Week 6
ProjectPart 2 of an extended team-based SW development project (only the main approximate timing is specified). Includes final project demonstration by each team.13%Week 11
Reassessment Requirement Type
Resit arrangements are explained by the following categories:
Resit category 1: A resit is available for both* components of the module.
Resit category 2: No resit is available for a 100% continuous assessment module.
Resit category 3: No resit is available for the continuous assessment component where there is a continuous assessment and examination element.
* ‘Both’ is used in the context of the module having a Continuous Assessment/Examination split; where the module is 100% continuous assessment, there will also be a resit of the assessment
This module is category 1
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

None

<< Back to Module List