Module Details |
The information contained in this module specification was correct at the time of publication but may be subject to change, either during the session because of unforeseen circumstances, or following review of the module at the end of the session. Queries about the module should be directed to the member of staff with responsibility for the module. |
Title | PRINCIPLES OF C AND MEMORY MANAGEMENT | ||
Code | COMP281 | ||
Coordinator |
Dr FA Oliehoek School of Electrical Engineering, Electronics and Computer Science Frans.Oliehoek@liverpool.ac.uk |
||
Year | CATS Level | Semester | CATS Value |
Session 2016-17 | Level 5 FHEQ | Second Semester | 7.5 |
Aims |
|
|
Learning Outcomes |
|
At the end of the module the student should be able to analyse and explain the use of memory resources within software applications, including memory usage on the stack during function calls and heap-based dynamic memory management; |
|
At the end of the module the student should be able to use debugging tools to inspect memory usage, and to assist in the development of software; |
|
At the end of the module the student should be able to develop applications within the C programming language, including use of command-line driven C development tools; |
|
At the end of the module the student should be able to deal with underlying memory-based issues in using dynamic data-structures through the implementation and management of at least one familiar datastructure using the C programming language. |
Syllabus |
|
1 |
|
Teaching and Learning Strategies |
|
Lecture - Two 1-hour lectures per week, based on slides and interactive demonstrations. |
|
Laboratory Work - Two lab sessions per week, in which students work individually supported by demonstrators. |
Teaching Schedule |
Lectures | Seminars | Tutorials | Lab Practicals | Fieldwork Placement | Other | TOTAL | |
Study Hours |
10 Two 1-hour lectures per week, based on slides and interactive demonstrations. |
10 Two lab sessions per week, in which students work individually supported by demonstrators. |
20 | ||||
Timetable (if known) | |||||||
Private Study | 55 | ||||||
TOTAL HOURS | 75 |
Assessment |
||||||
EXAM | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
CONTINUOUS | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
Coursework | 30 hours expected fo | Semester 2 | 30 | Yes | Standard UoL penalty applies | Programming Assignment |
Coursework | 30 hours expected fo | Semester 2 | 30 | Yes | Standard UoL penalty applies | Programming Assignment |
Coursework | 30 hours expected fo | Semester 2 | 40 | Yes | Standard UoL penalty applies | Programming Assignment Notes (applying to all assessments) 3 (sets of) assessment tasks This work is not marked anonymously. Resit-arrangements: Each re-sit assessment task will be different from the original assessment, except in the case of a skills-based assessment task, but the type of assessment will be the same; the deadline for the submission of work for each re-sit assessment task will be set by the module co-ordinator and will be part of the description of the assessment task; the deadline will typically fall within the re-sit period; the description of a re-sit assessment task will be provided at least four weeks before the deadline for the submission of work for the the task. |
Recommended Texts |
|
Reading lists are managed at readinglists.liverpool.ac.uk. Click here to access the reading lists for this module. Explanation of Reading List: |