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
| |||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||
Indicative Reading List
| |||||||||||||||||||||||||||||||||||||||||||
Other Resources None | |||||||||||||||||||||||||||||||||||||||||||