UNIVERSITY OF KENT
Guidance for the Completion of Module Specification Templates
Confirmation that this version of the module specification has been approved by the School Learning and Teaching Committee:
………27th January 2015………………………………………….(date)
MODULE SPECIFICATION
1. Title of the module
EL667 Embedded Computer Systems
2. School or partner institution which will be responsible for management of the module
Engineering and Digital Arts
3. Start date of the module
Revised version start date September 2015
4. The number of students expected to take the module
30
5. Modules to be withdrawn on the introduction of this proposed module and consultation with other relevant Schools and Faculties regarding the withdrawal
None
6. The level of the module (e.g. Certificate [C], Intermediate [I], Honours [H] or Postgraduate [M])
H
7. The number of credits and the ECTS value which the module represents
15 (7.5 ECTS)
8. Which term(s) the module is to be taught in (or other teaching pattern)
Autumn and Spring
9. Prerequisite and co-requisite modules
CO527 or EL560
10. The programmes of study to which the module contributes
BEng Electronic and Communications Engineering
BEng Electronic and Communications Engineering with a Year in Industry
BEng Computer Systems Engineering
BEng Computer Systems Engineering with a Year in Industry
MEng Electronic and Communications Engineering
MEng Electronic and Communications Engineering with a Year in Industry
MEng Computer Systems Engineering
MEng Computer Systems Engineering with a Year in Industry
BSc Computer Science
11. The intended subject specific learning outcomes
On successful completion of the module, students will have:
1. An understanding of the design and operation of embedded systems;
2. An understanding of real time software and hardware system requirements;
3. Practical experience of embedded systems based on case studies and laboratory experiments.
These outcomes are related to the programme learning outcomes in the appropriate curriculum maps as follows:
CSE/CSEwInd: A3,A8, B2,B3,B5,B7, C2-C4,C6,C8
ECE/ECEwInd: A3,A8, B2,B3,B5,B7, C2-5,C7
ECS: A2, A8, B2,B3,B5,B7, C2-5,C7
12. The intended generic learning outcomes
On successful completion of the module, students will be able to:
1. organise information clearly and coherently,
2. produce written documents
3. explore optimal and alternate solutions.
These outcomes are related to the learning outcomes in the appropriate curriculum maps as follows:
CSE/CSEwInd: D1,D5-D7
ECE/ECEwInd: D1,D5-D7
ECS: D1,D5-D7
13. A synopsis of the curriculum
Lecture Syllabus
INTRODUCTION TO MBED
Introduction to the mbed microcontroller system. Structure of the mbed, data input/output, serial communications, interrupts and timers. Compiling and downloading code to the mbed.
EMBEDDED AND REAL TIME SYSTEMS
An introduction to operating systems. Real time operating system features. Concurrent processes and priority. Synchronising processes. Hardware and operating system constraints. Deadlines and real time scheduling. Inter-task communication, message passing and threads. Multi-processor systems and redundancy. Hardware for real time. Safety critical systems. Case studies.
MICROCOMPUTER ARCHITECTURE APPLICATIONS AND PERFORMANCE
A series of case studies illustrating design and performance issues for real-time embedded systems leading to an introduction for the assignment to control a petrol engine.
Coursework
ASSIGNMENT - RTOS DEMONSTRATOR
This laboratory uses a hardware platform to develop an RTOS application and to monitor its performance.
ASSIGNMENT - MICROCOMPUTER ARCHITECTURE APPLICATIONS AND PEFORMANCE
This laboratory assignment is concerned with the control of the ignition timing of a simulated petrol engine. A microcomputer is programmed in ‘C’ to generate the spark at the appropriate time.
14. Indicative Reading List
Core Text
Shaw, AC (2001) Real-time systems and software, John Wiley, New York, Chichester
Simon, DE (1999) n embedded software primer, Addison Wesley, Boston, London
Qiu, Meikang, Li, Jiayin (c2011) Real-time embedded systems: optimization, synthesis, and networking, CRC, Taylor & Francis [distributor], Boca Raton, Fla, London
Recommended Reading
Toulson, Rob and Wilmshurst, Tim (2012) Fast and Effective Embedded Systems Design Applying the ARM mbed, Newnes ISBN 978-0-08-097768-3
Stallings, William (c2012) Operating systems: internals and design principles, Pearson, Boston (Mass), London
Stallings, William (c2010) Computer organization and architecture: designing for performance, Prentice Hall, Upper Saddle River, NJ
Valvano, Jonathan W (2011) Embedded Systems, Createspace, [Texas?]
Valvano, Jonathan W (c2012) Embedded systems: introduction to the Arm® Cortex(TM)-M3: 1, Jonathan W. Valvano, [Texas?]
Upton, Eben, Halfacree, Gareth (2012) Raspberry Pi user guide, John Wiley & Sons Ltd, Chichester.
Buttazzo, Giorgio C. (c2011) Hard real-time computing systems: predictable scheduling algorithms and applications, Springer, New York.
Background Reading
Bertolotti, Ivan Cibrario, Manduchi, Gabriele (c2012) Real-time embedded systems: open-source operating systems perspective, CRC, Boca Raton, Fla, London
Lipovski, G Jack (1988) Single- and multiple-chip microcomputer interfacing, Prentice-Hall International, London
Lea, Douglas (2000) Concurrent programming in Java: design principles and patterns, Addison-Wesley, Harlow, Reading, Mass
Athanas, Peter, Pnevmatikatos, Dionisios, Sklavos, Nicolas (2012) Embedded Systems Design with FPGAs, Springer, New York.
Williams, Rob (2006) Real-time systems development, Butterworth-Heinemann, Oxford.
15. Learning and Teaching Methods, including the nature and number of contact hours and the total study hours which will be expected of students, and how these relate to achievement of the intended module learning outcomes
There will be 20 hours of lectures and 5 support classes which support two substantive assignments.
The lectures and support classes address learning outcomes 11.1 and 11.2.
There are two assignments, both of which are undertaken in the laboratory and address learning outcome 11.3 and generic outcome 12.3; the preparation of the reports for these address the generic learning outcomes 12.1 and 12.2.
Total Contact Hours: 25
Independent Study Hours: 125
Total Study Hours: 150
16. Assessment methods and how these relate to testing achievement of the intended module learning outcomes
Assessment of this module is by assessment of the two substantive assignments (35%) and an examination (65%). The examination is 2 hours duration.
The coursework mark is proportioned as follows:
Microcomputer Architecture Assignment (50%)
Embedded Software Assignment (50%)
The assignments assess learning outcome 11.3 and generic learning outcomes 12.1, 12.2 and 12.3, while the examination covers learning outcomes 11.1 and 11.2.
The assessment and evaluation strategy has been devised to ensure that participants develop the required knowledge about fundamental concepts relating to embedded and real-time systems.
In order to obtain credit for this module, the coursework mark and the exam mark must each be greater than or equal to 30% as well as achieving the pass mark for the module.
This module will only be considered for compensation if the coursework mark and exam mark are each greater than 30%
17. Implications for learning resources, including staff, library, IT and space
None
18. The School recognises and has embedded the expectations of current disability equality legislation, and supports students with a declared disability or special educational need in its teaching. Within this module we will make reasonable adjustments wherever necessary, including additional or substitute materials, teaching modes or assessment methods for students who have declared and discussed their learning support needs. Arrangements for students with declared disabilities will be made on an individual basis, in consultation with the University’s disability/dyslexiasupport service, and specialist support will be provided where needed.
19. Campus(es) or Centre(s) where module will be delivered:
Canterbury
2
Module Specification Template (v.October 2014)