Module Details

Module Code: ELTR8018
Title: OO Design for Electronics
Long Title: Object Orientated Design for Electronics
NFQ Level: Advanced
Valid From: Semester 2 - 2019/20 ( January 2020 )
Duration: 1 Semester
Credits: 5
Field of Study: 5230 - Electronic Engineering
Module Delivered in: 1 programme(s)
Module Description: This module will develop in the student the ability to apply modern software engineering and object oriented design principles to electronic engineering software applications.
 
Learning Outcomes
On successful completion of this module the learner will be able to:
# Learning Outcome Description
LO1 describe in detail typical software development lifecycles and select the most appropriate to a particular electronic engineering application.
LO2 partition an electronics software development problem into appropriate elements and objects and design appropriate solutions.
LO3 develop object models to describe electronics software systems at both the systems and component level to guide the subsequent development.
LO4 describe and identify requirements for advanced programming concepts as would be required in electronics applications.
LO5 write software in a high level object oriented language which implements the advanced programming topics and object orientated models required.
Dependencies
Module Recommendations

This is prior learning (or a practical skill) that is strongly recommended before enrolment in this module. You may enrol in this module if you have not acquired the recommended learning but you will have considerable difficulty in passing (i.e. achieving the learning outcomes of) the module. While the prior learning is expressed as named MTU module(s) it also allows for learning (in another module or modules) which is equivalent to the learning specified in the named module(s).

Successful completion of a module in programming a high level object programming language such as C++ or Java
Incompatible Modules
These are modules which have learning outcomes that are too similar to the learning outcomes of this module. You may not earn additional credit for the same learning and therefore you may not enrol in this module if you have successfully completed any modules in the incompatible list.
No incompatible modules listed
Co-requisite Modules
No Co-requisite modules listed
Requirements

This is prior learning (or a practical skill) that is mandatory before enrolment in this module is allowed. You may not enrol on this module if you have not acquired the learning specified in this section.

No requirements listed
 
Indicative Content
Software Engineering (SW) Principles & Practice
SW engineering processes, project management concepts, requirements basics, usability systems, architecture & design reliability issues, performance, final delivery approaches.
High Level Requirements/Problem Partitioning
Requirements leading to application models, user interfaces, systems architecture, persistence, reliability.
System and Component Modelling
Use case modelling, UML, CASE Tools, applications, component design.
Case Tools to Programme Implementation
Application of models and conversion into programme code, CASE tool automation and basic systems development.
Advanced OO Programming Concepts
Exception handling/processing, process/internal synchronisation, memory protection.
Module Content & Assessment
Assessment Breakdown%
Coursework50.00%
End of Module Formal Examination50.00%

Assessments

Coursework
Assessment Type Practical/Skills Evaluation % of Total Mark 35
Timing Every Week Learning Outcomes 1,2,3,5
Assessment Description
Laboratory work: (a) develop UML models using industry standard notation and commercial tools to represent real world systems, (b) modify and develop a series of multi-threaded and multi-process systems in a commercial OO language to demonstrate, examine and correct synchronisation, communication and data protection issues in software systems.
Assessment Type Project % of Total Mark 15
Timing Week 6 Learning Outcomes 1,2,3
Assessment Description
Team project to develop a proposal for a demonstration project application including a set of requirements, user interface design and use cases for an object orientated electronics software application. Then, select an appropriate commercial software development project management model to help manage and deliver this. Finally, the team presents the above.
End of Module Formal Examination
Assessment Type Formal Exam % of Total Mark 50
Timing End-of-Semester Learning Outcomes 1,3,4
Assessment Description
End-of-Semester Final Examination
Reassessment Requirement
Repeat examination
Reassessment of this module will consist of a repeat examination. It is possible that there will also be a requirement to be reassessed in a coursework element.

The University reserves the right to alter the nature and timings of assessment

 

Module Workload

Workload: Full Time
Workload Type Contact Type Workload Description Frequency Average Weekly Learner Workload Hours
Lecture Contact Theory incl examples Every Week 2.00 2
Lab Contact Practical lab work based on various exercises and review assignments Every Week 2.00 2
Independent & Directed Learning (Non-contact) Non Contact Review of lecture notes, resources, preparation for assessment deliverables Every Week 3.00 3
Total Hours 7.00
Total Weekly Learner Workload 7.00
Total Weekly Contact Hours 4.00
Workload: Part Time
Workload Type Contact Type Workload Description Frequency Average Weekly Learner Workload Hours
Lecture Contact Theory incl examples Every Week 1.50 1.5
Lab Contact Practical lab work based on various exercises and review assignments Every Week 1.50 1.5
Independent & Directed Learning (Non-contact) Non Contact Review of lecture notes, resources, preparation for assessment deliverables Every Week 4.00 4
Total Hours 7.00
Total Weekly Learner Workload 7.00
Total Weekly Contact Hours 3.00
 
Module Resources
Recommended Book Resources
  • Alan Dennis, Barbara Haley Wixom & David Tegarden. (2015), Systems Analysis and Design: An Object-Oriented Approach with UML, 5th. Wiley, p.544, [ISBN: 978-111880467].
Supplementary Book Resources
  • Ian Sommerville. (2015), Software Engineering, 10th. Pearson, p.816, [ISBN: 978-013394303].
  • Craig Larman. (2005), Applying UML and Patterns - An Introduction to Object-Oriented Analysis and Design and Iterative Development, Third. Prentice Hall, [ISBN: 0-13-148906-2].
  • Booch, Rumbaugh, Jaconson. (2005), The Unified Modeling Language User Guide, 2nd. Addison-Wesley, p.496, [ISBN: 0321267974].
This module does not have any article/paper resources
Other Resources
 
Module Delivered in
Programme Code Programme Semester Delivery
CR_EELES_8 Bachelor of Engineering (Honours) in Electronic Engineering 8 Elective