Module Rationale and Content

18. This should be as objective as possible. The proposer may have a very clear sense of a module's intended value and outcomes but this may be less apparent to an observer from outside the discipline.

• Academic rationale: This should provide background information, e.g. the intention to fill a gap in the portfolio of modules and/or skills; a goal to improve the employability of students, or to enhance their ability to handle complex issues with a range of academic/technical skills. Some specific objectives may be included e.g. relating to the expectation that the proposed programme will meet professional accreditation requirements or the module will help meet revised requirements; that students will have more up-to-date ICT skills or that they will have wider ICT skills that can be updated regularly in employment or through further study. This information will not appear in the module database.
• Brief Description: This should be a brief summary, aimed at the student audience, of the content of the module (no more than 150 words). This information will appear in the module database.
• Content: This information will appear in the module database. The information needs to be reasonably detailed and should include the topics to be covered and provide an indication of the proportion of time and the type of delivery to be expected such as lectures, seminars and or other forms of delivery. If colleagues are overly prescriptive when setting out the course content, it may restrict their ability to make amendments to individual lectures or seminars in response to developments in the field or module evaluations. The detailed week-by-week plan setting out lectures, seminars etc. can be published on Blackboard, in module handbooks or equivalent as aspects of the delivery may change from year to year without change to actual content which would require approval via the APEX Module Management system.