| Module Title |
OO Analysis & Design |
| Module Code |
CSC1046 (ITS: CA314) |
|
Faculty |
Computing |
School |
Engineering & Computing |
|
NFQ level |
8 |
Credit Rating |
5 |
|
|
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 |
|---|
| Lecture | 24 | No Description | | Tutorial | 6 | No Description |
| Total Workload: 30 |
|
|
| Section Breakdown | | CRN | 10225 | Part of Term | Semester 1 | | Coursework | 0% | Examination Weight | 0% | | Grade Scale | 40PASS | Pass Both Elements | Y | | Resit Category | RC1 | Best Mark | N | | Module Co-ordinator | Sunder Ali Khowaja | Module Teacher | |
|
| Assessment Breakdown |
| Type | Description | % of total | Assessment Date |
|---|
| Project | Part 1 of an extended team-based SW development project (only the main approximate timing is specified) | 12% | Week 6 | | Project | Part 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 | | Formal Examination | End-of-Semester Final Examination | 75% | End-of-Semester |
| Reassessment Requirement Type |
Resit arrangements are explained by the following categories;
RC1: A resit is available for both* components of the module.
RC2: No resit is available for a 100% coursework module.
RC3: No resit is available for the coursework component where there is a coursework and summative examination element.
* ‘Both’ is used in the context of the module having a coursework/summative examination split; where the module is 100% coursework, there will also be a resit of the assessment
|
|
Pre-requisite |
None
|
|
Co-requisite |
None |
| Compatibles |
None |
| Incompatibles |
None |
|
|
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
Books:
- 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,
Articles:
None |
Other Resources
None |
|
|
|
|
