Undergraduate Module Template
Section 1 Basic Module Information
Basic module information;
Module Title - Telematics
Module Code - CSCI3426
Module Version Number - 2
Credit Value - 15
Module Size - 1.00
DMU Credit Level - 3
Semester - Semester Y
SAB - CSCI - Computing
Faculty - CSE - Computing Sciences Engineering
Module Leader - Eric Goodyer
Module Pre-requisites -
Section 2 Module Definition
The definition of the module characteristics, learning outcomes and assessment.
1. Module Characteristics
Telemetry is the use of a transmission system to monitor and control remote and distributed systems.
The transmission medium may be wired, such as a CAN network as used in most modern vehicles. Or
it may be wireless, employing GSM (mobile phone) technology, Bluetooth and similar RF based data
This module provides an understanding how distributed telematic systems are designed and
implemented. This will include a detailed study of a range of telematic standards and protocols.
You will gain the skills to develop telemetry software for use in the automotive sector, and as part of a
wider pervasive network of intelligent distributed computers that are linked by wireless technology.
2. Learning Outcomes
1 Have an understanding of the concept of a distributed (pervasive) computer system. This will
include a basic understanding of the underlying physical layer found in GSM and wireless networks.
2 Will have an in-depth understanding of current wired and wireless telematic protocols.
3 Be able to develop data transfer software for use in pervasive computer systems, using current
3. Learning and Teaching Strategies
Intensive teaching through the lectures will be backed up by practical demonstrations and lab work. A
series of short tutorial questions will be used to reinforce the lecture content.
Students will have access to a CAN network to experience a wired telematic system. Students will be
required to implement basic CAN messaging, using the DMU developed can systems to implement
distributed monitoring and control. The J1939 automotive protocol will be presented as theory only;
practical implementations can form the basis of final year projects.
A BlueTooth laboratory will be used to demonstrate the underlying HCI level commands. This will be
achieved using development equipment that has been donated OKI Semiconductors Ltd. Higher level
protocols will be examined using TDK or similar modules.
Subject to securing support from Orange Mobile Communications, the BlueTooth laboratory will also
support a suite of dedicated GSM MODEMs. These will form the basis of practical coursework, and
will be used to provide final year projects.
A field trip will be arranged to the Orange House, which is a 'state of the art' building specifically
Date printed: 27 July 2012 Page 1
designed to demonstrate the power of pervasive computing networks.
The module will be examined by means of a written exam (70%) and coursework (30%).
The course work will require the students to develop a telematic system that can demonstrably monitor
and control a remote system.
4. Required Prior Learning
5. Module Syllabus
1. CAN Networking, with emphasis on vehicle telematic systems using the J1939 protocol, and
knowledge of industrial protocols such as DeviceNet.
2. Application of GSM technology for remote monitoring and control. Specific emphasis will be
the use of SMS (PDU and Text mode), GPRS and dial-up connections to transfer data.
3. Application of BlueTooth technology for wireless monitoring and control. Specific emphasis
will be placed on gaining an understanding of the BASIC HCI protocol that underpins BlueTooth, and
some higher level applications.
6. Module Key Words
Assessment: Unseen Examination 1
Duration: 120.00 Weighting: 70%
Assessment: Other Coursework 1
Duration: 0.00 Weighting: 30%
8. Assessment Rationale
The exam will assess the students' knowledge of current telematic techniques and protocols.
The course work will examine the students' ability to research telematic solutions, and to implement
them in a practical environment.
By failed component
9. Module Learning Materials
Date printed: 27 July 2012 Page 2
10. Resource Information
HESA code for module - G400 - Computer Science - 39 - Computer Software Engineering
i) Staff/Student Hours
ii) Student Numbers
Minimum and maximum student places (DMU) - -
Staff/Student ratio -
Total Cost -
Cost per Student -
iii) Learning Resources
Please describe any additional learning resources required to support this module. Please indicate
where this impact upon central university resources [Library, IT/AV services]
Access to lab Queens Room 1.01
Access to telematics Lab (to be developed using an existing PC lab or a Queens lab)
Transportation for field trip to Orange House
Course Book in preparation.
Web based learning material.
Books to follow - few and far between
11. Quality Assurance
Approval and Modification
version Control – approved version for session: module code and session first approval for this
Monitoring and Evaluation
At the end of each module, students are invited to provide feedback via a 'Module Questionnaire'. This
formally documents informal feedback already gathered throughout the year.
The module leader completes a Module Evaluation Form, reflecting on the delivery of the module and
the feedback obtained from both students and the external examiner. Any actions needed (over and
above routine maintenance from year to year) are recorded on the MEF.
The MEF is presented to the SAB (Man).
Significant issues that require action are recorded in the Programme Journal.
Date printed: 27 July 2012 Page 3
Section 3 Module Delivery Variations
This section must be completed only when the module is offered in a distinct way to different cohorts o
students. For example, a module on taxation delivered in the UK and in South Africa or a statistics
module used by both business and engineering students may need to be adapted to suit local need or
subject context. When completing this section each field should show how the generic module
information in Sections one and two is adapted.
1. Offering Definition
2. Offering Learning Strategy
3. Specific Module Content
4. Specific Assessment Issues relating to this offering
Date printed: 27 July 2012 Page 4
Date printed: 27 July 2012 Page 5