CSCU9IS (3-month Summer Placement) Syllabus
Level 10, not credit bearing

List of Available Placements

Coordinator

Prerequisites

Learning Outcomes

Students will learn:

Contents

This module is an industrial computing science placement module. Placements run for 3 months during June, July and August. Experience gained during a placement is important for a number of reasons. It requires use of previously acquired skills and knowledge, increasing the grasp of these. It is also important to develop the ability to communicate ideas effectively. The placment provides an ideal opportunity to apply knowledge and concepts studied in previous modules in an industrial context. Working in an industrial setting will give them valuable skills and make them more employable on graduation. Students will be expected to tackle a substantial piece of work, under supervision by the industrial partner. The academic placement coordinator will stay in contact with the student and placement provider throughout the duration of the placement. It is expected that this will usually be done through electronic means. However, if the situation requires face to face meetings will be arranged.

The nature of the work undertaken will vary substantially; it is expected that the majority of the students will find placements where they will be working on software engineering and development projects. A placement might analyse, design, implement and evaluate algorithms for a scientific problem or analyse, design, implement and evaluate a substantial software solution for a problem which the placement provider or one of its clients faces. However, other placements such as in technical support are also feasible. Students will participate as members of an industrial team, as opposed to working in relative isolation.

Students are expected during their third year to take an active part, in cooperation with the placement coordinator, in securing an appropriate placement. While organising and applying for placment positions is ultimately the responsibility of the student, the university and module coordinator will assist in finding suitable placements. Students may organise their own placements, but the details must be approved by the module coordinator. Students who are unsuccessful in securing a placement position will be removed from the module at the beginning of the placement period (June).

Requirement

To obtain a grade, a student must submit the required coursework: final report (about 2000-3000 words).

The reports for placements undertaken during Summer 2017 are due by 30 September 2017. Please email your report to the module coordiantor, Dr Mario Kolberg.

This module does not have any prescribed classes. However, students are expected to comply with the attendance requirements of the placement host company.

Non-submission of any single item of assessed coursework will result in the award of No Grade for the module as a whole. If you cannot meet a deadline and have good cause, please see the coordinator to explain your situation and ask for an extension. Coursework will be accepted up to five days after the hand-in deadline (or expiry of any agreed extension) but the grade will be lowered by one grade point per day or part thereof. After five days the work will be deemed a non-submission and will receive No Grade.

Assessment

The 3-month placement is assessed on the basis of a report (of around 2000 words) produced at the end of the placement. The report will be graded as a Pass or Fail. There are no credits associated with the module, but the outcome is recorded on the student's transcript.

The report should describe the organisation the student was working with, summarise the projects in which the student was invlved, and should include a reflecttion by the student on the benefits gained comparing their industrial experience of software development against the material they have covered in taught modules. The reports submitted will be judged in terms of what was possible within a particular placement, rather than according to some absolute standard.

A typical structure of a report would include: