FACULTY OF SCIENCE AND ENGINEERING

School of Engineering and Computer Science

UNDERGRADUATE
SUBJECT HANDBOOK

COMPUTER SCIENCE

2016/17

This handbook is available on request in alternative

formats from the Computer Science Office
1
Contents
1 Welcome ........................................................................................................................ 4
2 General Information about Computer Science ............................................................... 4
2.1 Staff ........................................................................................................................ 4
2.2 Quality Officer ......................................................................................................... 4
2.3 Overseas Student Adviser ...................................................................................... 4
2.4 Disability Liaison Officer .......................................................................................... 4
2.5 Module Leaders ...................................................................................................... 5
2.6 Staff Locations ........................................................................................................ 5
2.7 Accommodation ...................................................................................................... 7
2.8 Robert Blackburn Accommodation .......................................................................... 8
2.9 Noticeboards........................................................................................................... 9
2.10 Computer Science Office ........................................................................................ 9
2.11 Access to Computer Science Facilities ................................................................... 9
2.12 Access to Staff ........................................................................................................ 9
2.13 Sickness and Absence .......................................................................................... 10
2.14 Borrowing of Final Year Projects Dissertations from the Computer Science Library ......... 10
2.15 Computer Facilities Provided for Your Use ........................................................... 10
3 Individual Programmes Regulations ............................................................................. 11
Weighting of Module Marks and Stages ................................................................ 12
Advice Regarding Resits in Modules Passed by Compensation............................ 12
4 Approach to Learning, Teaching and assessment........................................................ 13
Software Engineering Code of Ethics and Professional Practice ........................... 13
Three Year Degrees ............................................................................................. 13
Four Year Degrees ............................................................................................... 13
Degree Programme Content ................................................................................. 15
Work Load ............................................................................................................ 22
Submission of Coursework ................................................................................... 22
Coursework Feedback .......................................................................................... 23
5 Quality ......................................................................................................................... 24
Student Representation ........................................................................................ 24
Year Group Meetings (Mid-Trimester Review) ...................................................... 25
Module Evaluation ................................................................................................ 25
Comments and Issues of an Academic Nature ..................................................... 25
The Quality Review Process ................................................................................. 27

2
 Student Quality Feedback Loop ............................................................................ 28
6 External Examiner........................................................................................................ 29
7 Information on Professional Bodies .............................................................................. 29
British Computer Society Events ........................................................................... 29
8 Prizes ........................................................................................................................... 30
9 Postgraduate Study ..................................................................................................... 30
10 Safety .......................................................................................................................... 30
Annexe 1: Resits in Modules Passed by Compensation...................................................... 31
Annexe 2: Software Engineering Code of Ethics and Professional Practice ........................ 32
Annexe 3: Practical Work .................................................................................................... 34

3
1 Welcome
Computer Science is a thriving subject here at Hull, providing a range of degree programmes
for over 850 undergraduate and 50 postgraduate students. With cutting edge technologies
and direct access to research active staff, we offer a broad range of specialisms in teaching.
We provide a variety of extra-curricular activities and opportunities to enable students to
extend their experience and personal development, supported with our academic support
tutors. Whilst we are one of the largest subjects, we still focus on students and providing a
friendly environment where individuals can achieve their potential.

Computer Science is part of the School of Engineering and Computer Science, and which sits
within the Faculty of Science and Engineering.

2 General Information about Computer Science

2.1 Staff

The staff complement for 2016/17 is:

Academic Staff: 2 Professors, 1 Reader, 1 Academic Manager, 5 Senior Lecturers,

21 Lecturers, 1 Research Lecturer

Support Staff: 1 Administrator, 1 Computer Services Manager, 1 Research Support

Officer, 1 IT Specialist, 4 Secretaries

SEED Software Staff: 1 Support Manager, 2 Senior Software Developers (and 5

Undergraduate Interns)

HIVE Staff: 1 HIVE Manager, 1 HIVE Senior Researcher and Technical Lead
(and 7 Undergraduate Interns)

In addition there are a number of postgraduate research workers engaged on various projects.
Staff names and room numbers are listed on page 5.

2.2 Quality Officer

Eur Ing Tompsett is our Quality Officer who will respond to matters raised by students on any
matter concerning the quality of our undergraduate degree programmes and the teaching
associated with them.

Contact details: Room 336, email [email protected], telephone 465222.

2.3 Overseas Student Adviser

Dr Bing Wang is our Overseas Student Adviser, who can be approached directly by any
overseas student who wants advice on any topic.

Contact details: RB-246, email [email protected], telephone 465767.

2.4 Disability Liaison Officer

Amanda Millson is our Disability Liaison Officer, who acts as a contact point for disabled
students and distributes information about individual disabled students support requirements
to appropriate staff.

4
Contact details: RB-315, email [email protected], telephone 465205.

2.5 Module Leaders

Each module has a leader who is responsible for the overall content, delivery and assessment
of the module. If you have any problems with a specific module, your first point of contact is
the module leader.

2.6 Staff Locations

Computer Science (3rd Floor, Robert Blackburn Building)

Computer Science Office and Enquiries: Email Tel Room

Helen M El-Sharkawy (Secretarial Team Leader/PA to h.m.el-sharkawy 465951 308

Director, The Digital Centre)
Sally Byford (Secretary) (part-time) s.byford 465067 308

Jo Clappison (Secretary) (part-time) j.clappison 465067 308

Lynn Morrell (Secretary) (part-time) lynn.morrell 465067 308

Mark A Bell (Computer Services Manager and Safety m.a.bell 465340 329
Officer)
Mike Bielby (Research Support Officer) m.s.bielby 466948 352

Dr Leonardo Bottaci (Senior Lecturer) l.bottaci 465949 303A

Dr Mike Brayshaw (Lecturer) m.brayshaw 465976 303F

Dr David Chalupa (Lecturer) d.chalupa Swale House

Dr Yongqiang Cheng (Lecturer and Director of y.cheng 466572 325

Postgraduate Research Studies)
Mr Alan Dalgairns (Seed Support Manager) a.dalgairns Enterprise
Centre
Dr Darryl Davis (Senior Lecturer and Director of d.n.davis 466469 318
Research)
Dr Bailin Deng (Lecturer) b.deng Swale House

Dr Nina Dethlefs (Lecturer) n.dethlefs 465079 333

Dr Kevin Elner (Lecturer) k.elner 465124 337B

Dr Amadou Gning (Lecturer) e.l.gning 465285 303H

Dr Neil A Gordon (Senior Lecturer and Head of Subject n.a.gordon 465038 303D
Group)
Dr David Grey (Lecturer( (part-time) d.j.grey 465910 311B

Simon Grey (Lecturer) s.grey 465042 303E

Andrew Hancock (IT Specialist) andrew.hancock 466046 329

Professor Ken Hawick (Professor and Director, The k.a.hawick 465181 338
Digital Centre)

5
 Dr Chandra Kambhampati (Reader in Computer c.kambhampati 465744 337
Science)
Dr Qingde Li (Lecturer) q.li 465212 334

Dr Xinhui Ma (Lecturer) xinhui.ma 466601 348

Dr Nikos Matragkas (Lecturer) n.matragkas 465286 311C

Darren McKie (Lecturer) d.mckie 465677 311A

Amanda Millson (Administrator and Examinations a.millson 465205 315

Officer) (part-time)
Professor Yiannis I Papadopoulos (Professor) y.i.papadopoulos 465981 305

Dr David Parker (Lecturer) d.j.parker 465696 311D

Dr Jon Purdy (HIVE Manager) j.h.purdy 465016 339A

Dr John Rayner (Lecturer) (part-time) j.d.rayner 465622 303B

Dr Peter Robinson (Academic Manager) p.a.robinson 465228 303C

Dr Septavera Sharvia (Lecturer) s.sharvia 466534 327

Dr Jan Springer (Lecturer) j.springer 465371 319

Eur Ing Brian C Tompsett (Lecturer and Quality Officer) b.c.tompsett 465222 336

Dr Alex Turner (Lecturer) alexander.turner 465994 303G

Warren Viant (Senior Lecturer) w.j.viant 465289 326

Dr Amadou Gning (Lecturer) e.gning 465285 303H

Dr James Walker (Lecturer) j.a.walker Swale House

Dr Bing Wang (Lecturer and Overseas Student Advisor) b.wang 465767 246

James Ward (Research Lecturer) j.w.ward 465016 339A

Dr Jason Wood (HIVE Senior Researcher and jason.wood 466948 349

Technical Lead)
Dr Helen Wright (Senior Lecturer) (part-time) h.wright 465247 351

Some staff are based in Swale House or the Enterprise Centre as indicated above and should
be contacted by email.

When emailing staff, use the relevant email name shown above followed by @hull.ac.uk

Students must only use their University email account when contacting staff as emails
from other addresses may be automatically redirected into junk mail folders, may not
be delivered, or may have attachments deleted.

6
2.7 Accommodation

Computer Science currently occupies the third floor of the Robert Blackburn Building, as
shown on page 8 as well as part of the second floor together with part of the Enterprise Centre
and Swale House.

2.7.1. Laboratories

Babbage Laboratory 420

Backus Laboratory 316

Cray Laboratory 321

Design Laboratory 312

Dijkstra Laboratory 203

Engelbart Laboratory 352

HIVE Research Laboratory 339

Hopper Laboratory 203a

Pascal Laboratory 324

Ritchie Laboratory 300

Turing Laboratory 335

Undergraduate Laboratory 052, Ground Floor, Fenner Building

(large)

Undergraduate Laboratory 065, Ground Floor, Fenner Building

(small)

Von Neumann Laboratory 320

Wilkes Laboratory 177, 1st Floor, Fenner Building

7
2.8 Robert Blackburn Accommodation

Cray Lab (RBB-321)

Design Laboratory (RBB-312)

Social Area

Computer Science Office (RBB-

308)

Lecture Theatre D (RBB-LTD)

8
2.9 Noticeboards

There is one noticeboard for each year and additional boards for general notices, careers,
postgraduate study information etc. The majority of these boards are sited near the central
seating, outside RB-309A (see Computer Science Accommodation Plan). Students should
make a point of checking the relevant noticeboards regularly, as this is one of the main
channels for new or revised information about coursework, tutorials, lecture changes and
many other occasional events during the year. Email is also used extensively to communicate
with students and should be checked daily. It should be noted that staff will only send
messages to students University email accounts. Students should also regularly consult
Canvas for electronic copies of some announcements; specifically the relevant Canvas page
for each module: https://canvas.hull.ac.uk

2.10 Computer Science Office

The Office is open for student access at the following times:

During Trimester 1 and 2:

9.00 5.15 pm (Monday-Thursday); 9.00 4.15 pm (Friday)

During Vacations and Trimester 3:

9.00 12.30 pm and 1.45 4.30 pm (Monday-Friday)

Students may be directed to the Computer Science Office for a variety of individual
administrative requirements as they arise.

2.11 Access to Computer Science Facilities

The Robert Blackburn Building is open to all students between 8.45 am and 5.30 pm Monday
to Friday only during normal trimester time. Outside these times access is restricted to staff
and postgraduate students (taught and research) with the exception of FEN-052 which is a 24
hour laboratory (unless the University is closed) and is available to all Computer Science
students. Anyone working after 5.30pm or at weekends must telephone security on 6868 to
book in, and again on leaving.

2.12 Access to Staff

To enable students to be able to get support, all members of staff operate an office drop-in
hours system: with published availability on their office door. You may drop-in during these
times with general queries.

You may also contact staff members to make an individual appointment to meet outside of
those office times, either by email or in person.

Staff members may be able to assist with drop-in meeting beyond the above, but this will
depend on their other commitments: there are times when staff will not be in their offices since
they have teaching, research and other administrative commitments, or may be in their offices
but are not available to meet.

In cases where you need to see a member of staff URGENTLY, and that person cannot be
located, you should go to the Computer Science Office to ask the secretarial staff about the
person's whereabouts. In urgent cases, if the member of staff required is not available, then
the Director of Undergraduate Studies (Dr David Grey) or the Subject Lead (Dr Neil Gordon)
may be approached by contacting the secretarial staff who have access to their diaries.

9
2.13 Sickness and Absence

If you are absent from university you are instructed to tell us by phone or email as well as by
completing a Personal Unavoidable Absence Form (green form), available from the Computer
Science Office (RB-308). Please complete and return it to the Computer Science Office. The
form is for absences of between 1 and 7 calendar days. Please note that a doctor's note will
be required for absences of more than 7 days. For further information see:

http://www2.hull.ac.uk/student/studenthandbook/academic/absence.aspx.

In the case of any Tier 4 Visa student planning to be absent from university they MUST
complete the Tier 4 Visa Authorised Absence Form before travel. Please note the university
will not currently authorise more than 42 days absence (per academic year).

2.14 Borrowing of Final Year Projects Dissertations from the Computer Science
Library

Undergraduate students are allowed to borrow previous students final year project reports. A
maximum of two reports per student can be borrowed and the maximum borrowing time is one
month. Students can extend the borrowing time, on a month by month basis, provided that
there is not a waiting list for the project(s) they have borrowed. To renew the project report,
the report should be brought into the Computer Science Office and a revised date will be
authorised.

Keys for the project cabinets in the Computer Science Library are only available from the
Computer Science Office between the following times: Monday-Friday 10.00 am to 12.00 noon
and 2.00 pm to 4.00 pm. Students will be asked to leave their student registration card in the
Computer Science Office in return for the keys being issued to them.

2.14.1. Accessing Online Final Year Projects Dissertation

Students can access an archive of Final Year Project Reports from the Universitys Digital
Repository. Students may search by year, title, and name and download individual final year
project reports. The site can be accessed via the following web address or via the 08341
module site on SharePoint:

https://edocs.hull.ac.uk/muradora/browse.action?parentId=hull:665&type=1

http://intra.net.dcs.hull.ac.uk/student/modules/08341/default.aspx

2.15 Computer Facilities Provided for Your Use

We provide a range of computing facilities to support teaching and research. The main
teaching facilities outlined below comprise PCs running Windows 10. All laboratories are
supported by gigabit networking, laser printers, audio visual facilities and are air-conditioned.

2.15.1. Computing Hardware and Laboratories

Computer Science students have access to the following computing facilities:

The Science Computer Suite contains in total 172 high performance PCs running Windows
10. The laboratory is situated on the ground floor of the adjacent Fenner building (FEN-
052 & FEN-065). The majority of formal laboratory sessions will take place in this
laboratory. FEN-052 houses 142 PCs whilst FEN-065 houses 30 PCs.

10
Computer Science also hosts three specialised computing laboratories all running Windows
10 with dual screens:
The Wilkes Laboratory, containing 32 PCs, situated on the first floor of the Fenner
Building (FEN-177). This room hosts the Computer Sciences games development kits
including:
16 Playstation (PSP) development kits
16 Kinects
4 Playstation 3 development kits
1 Xbox
1 Wii U Development kit
3 PS4 development kits
1 PS Vita development kit
The Hopper Laboratory, containing 32 PCs, is situated on the second floor of the Robert
Blackburn Building (RB-203A).
The Cray Laboratory, containing 24 PCs, situated on the third floor of the Robert
Blackburn Building (RB-321). This room has been upgraded with heat exchangers to
provide a low-carbon-footprint comfortable working environment and forms a part of
Higher Education Carbon Management Programme.

We ask that students do not eat and drink in PC laboratories. The provision of a clean,
comfortable working environment is important to us. Please clear up any surplus materials to
the bin when leaving a workstation so that the next user is not inconvenienced.

Please report any faults or concerns with equipment, furniture or the laboratories generally
using one the methods displayed in each laboratory. We appreciate your feedback and
constantly strive to provide a better experience.

If you require any ICT assistance please contact the ICT Service Desk:
In person at the ICT Service Desk, Applied Science Building.
Email: [email protected]
Telephone: (01482) 46 2010
Twitter: @hulluni_ict
Hours of operation: Monday to Thursday 8:30 to 17:30, Fridays 08:30 to 16:30

2.15.2. Networked Data Store

Each student will be allocated a networked drive (mapped as G: on a networked PC). This is
a high-availability backed-up area in which you may safely store your work and documents. In
addition, each student will also be allocated a subversion repository to enable them to learn
about using source control. It is expected that all students will use SVN.

3 Individual Programmes Regulations

General regulations relating to your degree programme can be found in section 6.13 of the
Faculty level Student Handbook.

Students on Computer Science degree programmes must note the following:

A module assessed on a project/dissertation cannot be passed by compensation for
Honours and Integrated Masters degree programmes.
Compulsory computer science foundation year modules cannot be condoned or
compensated.

11
 A student at the Honours stage of an Integrated Masters (MEng) programme may only
progress to the Masters stage if they have achieved the equivalent of a BSc (Hons) degree
classification of 2.2 or above. If not they will be transferred to the corresponding BSc
Honours degree and graduate.
Any student, except those studying Integrated Masters programmes, can transfer on to the
Industrial Experience or Study Abroad variant of their programme provided that they can
secure an approved industrial placement or an approved year of study at a recognised
overseas university. Students who fail the Industrial Experience or Study Abroad year are
required to transfer back to the BSc Honours degree without the Industrial Experience or
Study Abroad.
A stage average of at least 50% in the second year of an Honours programme is
required to transfer to the equivalent Integrated Masters programme.
Integrated masters students who have a Diploma stage average of less than 50%
but have sufficient credits to progress, will be transferred to the Honours Stage of
the corresponding BSc Honours degree.

Weighting of Module Marks and Stages

Each module is weighted by the credit value of the module (e.g. a 20 credit module is weighted
20). The module mark is multiplied by the weight; such products are summed over all modules
for that stage of the programme; then, divided by the total of the weights to give the weighted
average for that year/stage.

The Pre-Certificate and Certificate stage of an Honours/MEng degree programme will not be
counted towards the classification. This does not mean that the first year assessments are
unimportant - remember that these assessments have to be passed in order to gain the
credits to satisfy the criteria for progression.

The performances at the post-Certificate stages are weighted as follows:

Diploma Post-Diploma Honours Masters

3 year BSc programmes 30% - 70% -

4 year BSc programmes 27% 10% 63% -
Direct Entry Final Year 0% - 100% -
MEng 15% - 25% 60%
Direct Entry Final Year who 0% - 40% 60%
transfer to MEng

The profile of performances in individual modules achieved by each candidate will be

considered by the Board of Examiners, together with documentary evidence supplied for
special cases, before recommending the class of degree to be awarded.

Advice Regarding Resits in Modules Passed by Compensation

Except the Pre-Certificate stage, the Universitys Undergraduate Programme regulations allow
up to 40 credits to be passed by compensation at each stage (year of study) of your degree,
subject to various conditions having been met. However, to be awarded an Honours or
Ordinary degree, a student must have a total of no more than 60 credits of modules overall
passed by compensation (or condoned in the final year). Due to this 60 credit restriction, the
Computer Science has published some advice (see Annexe 1).

12
4 Approach to Learning, Teaching and assessment
All of our degree programmes, while differing in detail, share the same general structure. Each
degree involves three or four years of academic study and leads to either a classified Honours
Bachelor of Science (BSc) or a Master of Engineering (MEng). There are Ordinary degree
schemes for which students are considered when they are unable to satisfy the progression
requirements of an Honours degree.

Details of Computer Sciences undergraduate degree programmes and their associated

learning outcomes; along with individual module specifications can be accessed at
www.courses.hull.ac.uk and on the universitys website at
http://www2.hull.ac.uk/science/computer_science/undergraduate/courses.aspx.

The single subject degree programmes share a significant number of modules. In the first
year of all the single subject degrees, a common core provides a broad computer science
based education that includes a grounding in both software engineering and information
systems. Specialisation begins in the second year and is built on in the third year; which is
about 20-30% of the curriculum.

Software Engineering Code of Ethics and Professional Practice

In the process of becoming a professional software engineer it is important to understand not

just the process of software development but the social, ethical and legal aspects of the
profession. Annexe 2 sets out the ACM and IEEE (two international bodies representing the
computing profession) approved Software Engineering Code of Ethics and Professional
Practice.

Three Year Degrees

The Computer Sciences three year degrees comprise six trimesters of study and assessment
and are structured into three stages, namely: Certificate, Diploma and Honours. Degrees are
offering in the following:

BSc Computer Science Admission pre and post 2016/17

BSc Computer Science (Software Engineering) Admission from 2016/17
BSc Computer Science for Games Development Admission from 2016/17
BSc Computer Science (Embedded Systems) Admission from 2016/17
BSc Computing Admission from 2016/17
BSc Software Development Admission pre- 2016/17
BSc Computer Science with Games Development Admission pre- 2016/17
BSc Computer Systems Engineering Admission pre- 2016/17
BSc Information Systems Admission pre- 2016/17

Four Year Degrees

Degrees including a foundation year:

Computer Science runs four year degrees across all of its programmes for students who have
not yet achieved the entry requirements for the three year degree programmes, but who are
qualified to enter the University. The first year (Foundation Year) is coordinated between a
number of schools within the Faculty to provide students with a strong foundation for later
studies.

Students on the four year degree programmes take the foundation year and then feed into the
structure of the corresponding three year programmes. The four year degree programmes

13
comprise eight trimesters of study and assessment and are structured into four stages: Pre-
Certificate, Certificate, Diploma and Honours.

Sandwich Degrees:
Computer Science also runs four year sandwich degrees across all of its programmes. The
third year of these courses will be spent on a relevant industrial placement or at an overseas
university. The first, second and fourth years correspond to the years of the three year
degrees. Students already on the corresponding three year degree programmes can apply
for transfer to the four year with Industrial Experience or with Study Abroad degrees.

We believe that a year of relevant work or study is beneficial for students and active
encouragement will be given to students who wish to spend their third year in this way, by
supporting requests from students currently enrolled on the three year programmes to transfer
to the four year sandwich courses.

Whilst it is the students responsibility to gain a suitable placement, the Computer Sciences
Industrial Liaison and Placement Officer delivers a series of compulsory lectures to students
interested in securing an industrial placement. The University Careers and Employability
Service also assists in advertising internships whilst we also offer a number of SEED and
HIVE internships each year.

Students are advised to discuss their placement with the Industrial Liaison and Placement
Officer early in the first trimester of the second year of their course and no later than the end
of week 4 of that trimester. Each case must be approved, to determine that the industrial
placement is appropriate, that the student's progress to date has been satisfactory.

With regard to students wishing to spend a year of study abroad, the University has a
dedicated Study Abroad and Exchange Unit which assists student wishing to study overseas.
http://www2.hull.ac.uk/international/exchange__study_abroad.aspx

MEng Degrees:
Computer Science offers four year MEng degrees in Computer Science, Computer Software
Development, Computer Science (Software Engineering), Computer Science with Games
Development, Computer Science with Games Development, Computer Systems Engineering
and Computer Science (Embedded Systems). The first three years of these programmes
correspond to the three year BSc degrees. An additional Masters year covers more advanced
topics relevant to the degree title plus a 40 credit Commercial Development Practice module
which gives students industrial experience through working on real commercial software
development projects.

MEng Computer Science Admission pre and post 2016/17

MEng Computer Science (Software Engineering) Admission from 2016/17
MEng Computer Science for Games Development Admission from 2016/17
MEng Computer Science (Embedded Systems) Admission from 2016/17
MEng Computer Software Development Admission pre 2016/17
MEng Computer Science with Games Development Admission pre- 2016/17
MEng Computer Systems Engineering Admission pre- 2016/17

The relationship between years, trimesters and parts of the degrees is illustrated in Figure 1
overleaf.

14
Pre-Certificate Certificate Diploma Honours Masters
Trimester 1 Trimester Trimester Trimester Trimester Trimester Trimester Trimester Trimeste
1 2 1 2 1 2 1 r2
Year 0 Year 1 Year 2 Year 3 Year 4 (MEng)
Level 3 Level 4 Level 5 Level 6 Level 7
Figure 1: The relationship between years, trimesters and parts of the degree.

Degree Programme Content

Pre-Certificate Stage

The Pre-Certificate stage contains a number of modules to enable students transition to

Higher Education and to studying here at the University of Hull. The lectures, workshops and
other activities will develop students academic skills and subject knowledge. Alongside this,
students will have the opportunity to strengthen and develop other talents, perhaps with extra-
curricular activities such as those offered by Computer Science (Three Thing Games and
Really Useful Seminars) and through the Student Union.

The aims of the Foundation Year are to:

Provide students with a foundation of scientific, intellectual and investigative skills and
knowledge on which to build during the later stages of their programmes.
Develop a reflective and adaptive approach to study.
Provide students with sufficient mathematics knowledge and understanding for successful
progression through the Certificate, Diploma and Honours stages of their programme.
Provide a challenging and rewarding learning experience for all students and to foster the
development of an enquiring, open-minded and creative attitude through a mix of formal
teaching, discussion and practical experience.

4.4.1.1 Modules

All Degree
Credits
Programmes

Trimester 1 (3 modules taken)

06061 Preparing for Learning in Higher Education 20 C

03008 Foundation Maths 1 20 Opt1

03007 Foundation Maths A 20 Opt2

08014 Fundamentals of Computing 20 C

Trimester 2 (3 modules taken)

03007 Foundation Maths 2 20 Opt1

03008 Foundation Maths B 20 Opt2

08015 Web Skills and Technologies 20 C

08031 Computer Science in Context Group Project 20 C

15
NOTES:
C indicates module is compulsory.
Opt1/Opt2 students will be allocated to either Maths 1 & 2 or Maths A & B modules.
There may be occasions when changes to the published programme structure or module
content may need to be made due to unforeseen circumstances, e.g. long-term staff
illness.

4.4.1.2 Assessment

The assessment of a module and obtaining credits for that module is usually based on a
combination of the mark for the written examination paper and the mark obtained from the
assessed coursework and tests/practicals associated with the module. Each modules
assessment strategy is available via the module page of SharePoint or
www.courses.hull.ac.uk. Submission of coursework and attendance at tests and exams
essential. Examination papers at the Pre-Certificate Stage may be 1 to 2 hours in length and
take place at the end of the trimester in which the module is given.

Certificate Stage

The Certificate Stage/year 1 of our degrees addresses fundamentals of computer science and
provides an introduction to computing systems, software engineering, information systems
and management.

4.4.2.1 Modules

All degree
Credits
programmes

Trimester 1 (3 modules taken)

08133 Programming 1 20 Opt1

08135 Programming Paradigms 20 Opt2

08136 Quantitative Methods for Computing 20 C

08131 Computer Systems 20 C

Trimester 2 (3 modules taken)

08134 Programming 2 20 Opt1

08016 Software Project Based Learning 20 Opt2

08112 Software Engineering and Human Computer Interaction 20 C

08137 Computer Science: the Challenge for Sustainable

20 C
Computing

NOTES:
C indicates module is compulsory.
Students must study both modules in option group Opt1 or in option group Opt2. The
choice of which option group they study depends on their prior level of programming
experience and is determined by a programming diagnostic test held in the first week of
trimester 1.

16
 There may be occasions when changes to the published programme structure or module
content may need to be made due to unforeseen circumstances, e.g. long-term staff illness.

4.4.2.2 Assessment

The assessment of a module and obtaining credits for that module is usually based on a
combination of the mark for the written examination paper and the mark obtained from the
assessed coursework and tests/practicals associated with the module. Each modules
assessment strategy is available via the module page of SharePoint or
www.courses.hull.ac.uk. Submission of coursework and attendance at tests and exams
essential. Examination papers at the Certificate Stage are usually 1-2 hours in length and
take place at the end of the trimester in which the module is given, some may be paper based
whilst others are online exams. Exams for year long modules take place at the end of
Trimester 2.

Diploma Stage

The Diploma Stage/year 2 of our degrees provides a broader and deeper coverage of
computer science, software engineering, information systems and management topics. It also
introduces some application oriented topics which can lead onto more advanced courses at
the Honours Stage.

4.4.3.1 Modules

Credits CS SD GD CSE IS

Trimester 1 and 2 (2 modules taken)

08226 Artificial Intelligence 20 Opt - C - Opt

08227 Advanced Programming 20 Opt C C C -

08232 Database Techniques 20 Opt C - - C

08249 Electronics and Interfacing 20 Opt - - C -

Free elective 20 Opt - - - Opt

Trimester 1 (2 modules taken)

08220 Systems Analysis Design and Process 20 C C C C C

08240 2D Computer Graphics and User Interface

20 Opt Opt C C -
Design

08245 Information Systems and User Interface Design 20 Opt Opt - - C

Trimester 2 (2 modules taken)

08214 Simulation and 3D Computer Graphics 20 Opt1 - C - -

08221 E-Commerce and E-Business 20 Opt1 - - - Opt

08230 Software Engineering 20 Opt1 C - C Opt

17
08241 Networking and Games Architecture 20 Opt2 - C Opt -

08246 Networking and Web Technologies 20 Opt2 C - Opt C

NOTES:
C indicates module is compulsory.
Opt indicates that the module is optional. It may be attended if the prerequisites stated in
the module details have been satisfied.
Opt1/Opt2 students cannot choose more than 1 option from the same option group.
- indicates a module that cannot be taken for that particular degree programme.
An Ordinary degree student will choose modules from the corresponding Honours degree,
including any modules from the Certificate stage for which credits have not been obtained.
An Ordinary degree student must obtain at least 180 credits by the end of the second year.
Students must still register for 120 credits.
There may be occasions when changes to the published programme structure or module
content may need to be made due to unforeseen circumstances, e.g. long-term staff illness.

4.4.3.2 Assessment

The assessment of a module is usually based on a combination of the mark for the written
examination paper and the mark obtained from the assessed coursework and practicals
associated with the module. Each modules assessment strategy is available via the module
page of SharePoint or www.courses.hull.ac.uk. Submission of coursework is essential.
Examination papers at the Diploma Stage are usually 1-2 hours in length and take place at
the end of the trimester in which the module is given, some may be paper based whilst others
are online exams. Exams for year long modules take place at the end of Trimester 2.

Post-Diploma Stage (Year in industry or study abroad)

Students taking a formal year out in industry must attend a series of timetabled compulsory
lectures delivered by the Industrial Liaison and Placement Officer during their second year.

Students wishing to undertake a year of study abroad must engage with the universitys Study
Abroad and Exchange Unit during trimester 1 of their second year for help in finding a study
abroad placement http://www2.hull.ac.uk/international/exchange__study_abroad.aspx. All
students should also read the year in industry or study abroad handbook published on Canvas
within the 08323 and 08325 sites.

4.4.4.1 Modules

All with industrial

All with study
experience
Credits abroad
degree
programmes
programmes

Trimester 1 and 2 (1 double module taken)

08323 Study Abroad 120 C -

08325 Year in Industry/Commerce 120 - C

18
4.4.4.2 Assessment

Details of the method of assessment for the year out in industry can be found on the
universitys module catalogue: https://www.courses.hull.ac.uk/.

Honours Stage

For the Honours Stage/year 3 of the single subject degrees, a student takes a number of core
modules and selects further modules so that 120 credits are taken in total. The core modules
for each degree ensure that students study topics particularly appropriate to their degree at
an advanced level and carry out a substantial individual project. The options provide for further
specialisation by allowing a student to choose topics from computer science, software
engineering, information systems and various application domains where he/she wishes to
acquire a deeper understanding. Many of these modules reflect the research interests of the
Computer Science staff.

4.4.5.1 Modules

Credits CS SD GD CSE IS

Trimester 1 and 2 (1 double module taken)

08130 IT Internship 40 - - - - Opt1

08341 Development Project 40 C C C C Opt1

08244 Communicating and Teaching

Computing (University Ambassadors 20 Opt Opt Opt Opt Opt
Scheme)

Trimester 1 (2 modules taken)

08335 Advanced Software Engineering 20 - C - Opt Opt

08338 Data Mining and Decision Systems 20 Opt - - - C

08343 Commercial Game Development

20 - Opt C - -
Process

08347 Virtual Environments 20 Opt - - - -

08348 Languages and Compilers 20 Opt Opt - Opt -

08026 Embedded Systems Development 20 - - - C -

08356 Games Programming and

20 - - C - -
Advanced Graphics

26390 Strategic Management 20 - - - - Opt

31011 Psychology and Work 20 - - - - Opt

Trimester 2 (2 modules taken)

19
08027 Mobile Devices and Applications 20 Opt C Opt Opt Opt

08334 Starting and Managing a High-Tech

20 Opt - - - C*
Business

08336 Neural, Emergent and Agent

20 Opt - Opt Opt -
Technology

08346 Distributed Systems Programming 20 Opt C Opt Opt Opt

08023 Visualization 20 Opt - Opt - -

26327 Information Systems in Accounting

20 - - - - Opt
and Finance

NOTES:
C indicates a module is compulsory.
Opt indicates a module is an option. It may be attended if the prerequisites stated in the
module details have been satisfied.
Honours students must ensure that they take a minimum of 100 credits at level 6; the
remaining 20 credits may be at level 5.
Students selecting 08244 must drop a 20 credit Trimester 1 or Trimester 2 module,
thereby weighting their honours stage either 50:70 or 70:50.
- indicates a module which cannot be taken for that particular degree programme.
Students who enter the third year of the degree programme as Ordinary degree students,
must select modules from the corresponding Honours programme, such that by the end
of their final year they have 300 credits including at least 60 at level 6. If an Ordinary
degree students wants to top up to honours at the end of the year, they must ensure they
have passed all core modules from Years 1, 2 and 3 and achieved a final stage average
of at least 60%.
There may be occasions when changes to the published programme structure or module
content may need to be made due to unforeseen circumstances, e.g. long-term staff
illness.

4.4.5.2 Assessment

The assessment of a module, and hence obtaining the credits for that module, is usually based
on a combination of the mark for the written paper and the mark obtained for the assessed
coursework. Each modules assessment strategy is available via www.courses.hull.ac.uk.
Level 6 examination papers at the Honours Stage are usually 2 hours in length and take place
at the end of the trimester in which the module is given.

Assessment of the individual project (08341/08349) is outlined in the Project Handbook

available on the 08341 canvas site.

Masters Stage

For MEng students, the Masters Stage provides a more advanced coverage of specialist
computing topics relevant to the title of the degree. The majority of these modules reflect the
research interests of the Computer Science staff. In addition, students gain experience of
working as part of a team to implement solutions for real customer needs by working on
industrial based projects. Students will gain valuable practical experience of team working,

20
customer liaison, requirements elicitation, software design, software implementation and
testing, maintenance and debugging, planning and project management.

4.4.6.1 Modules

Credits CS SD GD CSE

Trimester 1 and 2 (1 double module taken)

08911 Commercial Development Practice 40 C C C C

Trimester 1 (2 modules taken)

08975 C++ Programming and Design 20 Opt1 - C C

08025 Real-time Graphics 20 Opt1 - C C

08352 Component Based Architectures 20 Opt2 C - -

08020 Maintaining Large Software Systems 20 Opt2 C - -

Trimester 2 (2 modules taken)

08024 Simulation and Concurrency 20 Opt1 - C C

08974 Advanced Rendering and Artificial Intelligence 20 - - C -

08022 Robotic Systems and Artificial Intelligence 20 - - - C

08019 Distributed Applications 20 Opt2 C - -

08018 Trustworthy Computing 20 C C - -

NOTES:
C indicates module is compulsory.
Opt indicates that the module is optional. It may be attended if the prerequisites stated
in the module details have been satisfied.
Opt1/Opt2 students must choose either the graphics pathway (Opt1) or the distributed
systems development pathway (Opt2).
- indicates a module that cannot be taken for that particular degree programme.
There may be occasions when changes to the published programme structure or module
content may need to be made due to unforeseen circumstances, e.g. long-term staff
illness.

4.4.6.2 Assessment

The assessment of a module is usually based on a combination of the mark for the written
examination paper and the mark obtained from the assessed coursework and practicals
associated with the module. Each modules assessment strategy is available via the module
page of SharePoint or www.courses.hull.ac.uk. Examination papers at the Masters Stage
(level 7) are usually 2 hours in length and take place at the end of the trimester in which the
module is given.

21
 Work Load

A student's work load in each trimester comprises a mixture of lectures, associated tutorials,
practical activities and scheduled practical laboratories. In the first year, (Pre-Certificate and
Certificate stage) the associated practical work is largely provided through formal laboratories.
To provide reinforcement of lectured material, assessment of set course work is undertaken
for each lecture based module. This is often supplemented by tutorial groups which meet
regularly to discuss matters relating to lectures and practical work.

Diploma stage modules are supported by tutorials, demonstrations where appropriate, and
assessed course work, much of which includes practical work in the computing laboratories.

Honours stage taught modules have an assessed coursework element, although the individual
project is the major component of the assessment of the practical abilities of students at this
stage. The teaching staff are the main originators of projects, but projects from industry and
students are also welcomed. The aim of the project is to draw together the knowledge
gathered during the previous years and to demonstrate the students technical and
engineering competence in an area relevant to computing.

Masters stage taught modules have an assessed coursework element although the
Commercial Development Practice module is the major component of the assessment of the
practical abilities of students at this stage. The aim of this module is to give students
experience in the skills and practices of commercial software development by allowing them
to work on real commercial software development projects.

A summary of the practical work for each stage is available in Annexe 3.

Submission of Coursework

Students are not entitled to expect module staff to read drafts of assessed work prior to
submission. Each assessment description details if submission is via hard copy or electronic
copy.

Electronic Submissions

Module lecturers will request electronic submission (via Canvas, SVN, and/or TurnitinUK) of
coursework, instructions for which will be detailed in the assessment description document
that is published via the relevant Canvas site.

Hard Copy

A locked white wooden post box is provided outside the Computer Science Office (RB-308)
for hard copy submission of a small number of coursework assignments (generally maths
assignments). Coursework must NOT be handed to OR emailed to staff.

Submission Requirements

Students must ensure that they adhere to the exact submission requirements set out in
the assessment description for each piece of coursework.
Students should take into account possible long print queues or printer problems just
before a submission deadline, and print out work well in advance of the hand-in time.
Where runnable code is a submission requirement of an assignment, students MUST
ensure that the code can be run on computer science computers.
All coursework must be handed in/submitted no later than the time and date set by the
module lecturer.

22
 The online submission methods (e.g. Canvas) record the exact time and date of students
submissions. Regardless of submission method late submissions will be penalised. It is
therefore essential that you submit your coursework by the specified deadline unless an
extension has been given.
The coursework white box will be emptied on the day and at the time coursework is due
with students issued with email receipts of their submission.
When a coursework description specifies that the work will be uploaded to TurnitinUK
students should only submit Word, RTF or PDF files, unless otherwise stated in the
coursework description. They must NOT compress these i.e. do NOT submit ZIP or other
archive formats.
A student will receive a late penalty if they request permission to resubmit the correct
coursework/file having discovered they have uploaded the wrong coursework (for example
to Canvas).

Coursework Demonstrations

Any student who fails to attend their allotted individual demonstration slot will have their
mark for the entire ACW capped at 40%.
Any student who fails to attend their allotted group demonstration slot will have their mark
for the entire ACW reduced by 10% (of the maximum available marks for that coursework).
If a student has legitimate reasons why they missed the demonstration, they are required
to submit a mitigating circumstance form ticking absence with good cause (AGC).
This penalty is in-line with the new policy on attendance, and promotes expectations of
professionalism during demonstrations.

N.B Whilst some coursework demonstrations may not attract marks they remain compulsory
as the demonstration will be used to inform the marking of the students work as well as give
the student an opportunity to demonstrate they have attempted the coursework.

4.6.4.1 Project/Dissertation Demonstrations

Any student who fails to attend their allotted dissertation demonstration slot will have a
mark of zero recorded for their demonstration.
If a student has legitimate reasons why they missed the demonstration, they are required
to submit a mitigating circumstance form ticking absence with good cause (AGC).
This penalty is in-line with new policy on attendance, and promotes expectations of
professionalism during demonstrations.

Coursework Feedback

Feedback will be provided in the following form(s):

Examinations
Marks and comments are written directly onto the scripts by the examiners.
Academic Support Tutors have information on the marks you obtained for individual
questions and may recommend you consult an examiner about your script, if this is
warranted.
General feedback may also be provided to the class, during a feedback session.

Exam Tests (completed in labs)

Marks and comments are written directly onto any paper based class test submissions and
returned to students within 4 trimester weeks of the test.

23
 For exam tests completed using Canvas instant feedback in the form of marks is normally
given within 24 hours (unless the online exam is the last piece of assessment and
completed during one of the exam periods) whilst general feedback may also be provided
to the class.
Indicative answers may be provided to supplement the above.
General feedback may also be provided to the class, during a feedback session.

Coursework (one of the following will be used) with feedback returned with the work within 4
trimester weeks from the date of submission,

Feedback sheet.
Mark sheet.
Annotation.
General feedback may also be provided to the class, during a feedback session.

Demonstrations
Verbal feedback will be provided, which the student can record on a feedback sheet.

Presentations
Feedback sheet.

Assessment feedback is not an opportunity for a student to challenge the mark awarded. This
mark is established on the basis of a properly managed assessment process and is not an
item for debate during any feedback session.

The academic judgement of staff is challenged by other academics, e.g. the examination
board and the external examiner. In general, marks are only adjusted if there has been a
failure of the marking process itself. Notwithstanding this guiding principle, staff may explain
individually to a student how the marking scheme has been applied to their work with
clarification relating to feedback available to students on request.

A student may identify what they consider to be an error in the assessment description. Any
such query must be made as soon as possible and certainly before the assessment is marked.
A student who feels that they have misunderstood an assessment description must consider
carefully if the fault lies with the description or their interpretation.

Please note that an assessment is set in the context of the learning outcomes for the module
and does not, by itself, constitute a definitive specification of the assessment. If there are any
doubts as to the relationship between what the student has been asked to do and the module
content, this should be taken up with the member of staff who set the assessment. As in any
examination, understanding the question is part of the assessment process.

In case of any subsequent dispute, query, or appeal regarding your coursework, you are
reminded that it is your responsibility to produce the assignment in question. Module marks
remain provisional until approved by the Module Board of Examiners.

5 Quality
Student Representation

Students play an important part in computer sciences review process and provide feedback
on the curriculum and its delivery in a variety of ways. Computer Sciences Curriculum
Committee, which is responsible for the content and quality of our programmes and modules,

24
has undergraduate and postgraduate student membership, giving students a direct role in the
review process.

In addition to representation on Curriculum Committee, we explicitly seek student input to its

curriculum review process by the Year Group Meetings, and Staff-Student Committee. Items
raised through Year Group Meetings and Staff-Student Committee, are reviewed by the
Curriculum Committee and a report presented to Learning and Teaching Committee and to
the next Staff-Student Committee meeting.

Students with suggestions for development of the present degrees or constructive criticism of
any aspect of the degree programmes can do so by any of the means outlined above or by
contacting the Director of Undergraduate Studies (Dr Grey) directly.

Year Group Meetings (Mid-Trimester Review)

Year Group Meetings, to discuss the overall quality of the first, second and final years of our
degree programmes, are held each trimester. The meetings are informal and are open to all
students in the year group plus relevant academic staff. Meetings are typically driven by the
students and discuss issues in more detail than is possible through other means, such as the
Staff-Student Committee. Notes are taken and distributed to all staff, and, where matters of
policy are concerned, can be brought to the Staff-Student Committee. Reports of the meetings
are posted on the Quality Information noticeboard and the on-line Quality noticeboard at
http://intra.net.dcs.hull.ac.uk/quality/default.aspx

Module Evaluation

The standardised approach to module and teaching quality evaluation is an important part of
the Universitys quality assurance and enhancement system. The aim of obtaining module
level feedback from students is to enhance the student experience by identifying and acting
on areas that need to be addressed, as well as identifying and sharing good practice across
relevant programmes.

Module Evaluation Questionnaires (MEQs) are distributed in lectures to students at the end of
the delivery of each module. Students are asked to complete the questionnaires during the
lecture and to return them anonymously to allow module leaders to critically reflect on the
feedback (both quantitative and qualitative). This critical reflection serves as a means of
recording the reflection which has taken place, setting out actions which will be taken as a
result of that reflection, which includes the dissemination of good practice across the
programme(s)/school.

This critical reflection of module and teaching quality evaluations is part of a wider module
review process which includes consideration of module assessment and retention data,
external examiner comments as well as collated student evaluation results.

Staff use the MEQs to publish module reviews, commenting upon the feedback received and
proposing module changes in light of the review. Both the MEQs and module reviews are
published to students via computer sciences Quality Site.

Comments and Issues of an Academic Nature

A major aim of Computer Science is to ensure that our teaching is of high quality. However,
we are not perfect and for a variety of reasons there may be lapses in the quality of our
teaching and its organisation.

25
Students are encouraged to approach the member of staff concerned in the first instance. If
students feel their matter has not been dealt with satisfactorily, they should approach the
Quality Officer (Eur Ing Tompsett). If the Quality Officer is not available, students can contact
the Director of Undergraduate Studies (Dr Grey), Academic Manger (Dr Robinson), Head of
Computer Science (Dr Gordon), their Academic Support Tutor, or bring the matter, less rapidly,
before the Staff-Student Committee for a more open discussion. If you are dissatisfied with
Computer Sciences handling of any matter you can make a formal complaint, firstly to the
Faculty of Science and Engineering and subsequently to the University Complaints
Investigation Officer.

Issues of a personal nature should be made, at the earliest opportunity, to your Academic
Support Tutor, the Director of Studies or the Head of Subject as you think appropriate.

26
 The Quality Review Process

Student Feedback Student Feedback

Student Feedback
Class feedback
Module Evaluation Questionnaires (MEQs) Programme
Staff-Student Committee Questionnaire
Staff-Student Committee Reviews
Mid-Semester Module Review
Mid-Trimester Reviews
Forums
Forums

Programme Review
Module Managers
Feedback
Module Review
Programme Review

External Review
Subject Review
Quantitative Data
External Feedback
External examiner

Programme Review
Curriculum Module Reviews Learning and Teaching
Subject Review Committees Committee
(Operational) (Policy and Strategy)
Strategy and Policy

External Feedback
Industrial Liaison Panel
External Examiner
Accreditation

Quantitative Data
Entry Qualifications
Retention
Achievement
Destination

University/Faculty
Policies,
Regulations and
Guidelines

27
 Student Quality Feedback Loop

Available to students Students

Staff

On-Line
Module Review
Forums
Form
(Trial)

On-Line and
Module Class
MEQs individual responses
Feedback
Reviews

Statistics Quality Incident Book,

Issues

Students
Staff-Student
Committee Mid-Semester
Reviews
Quality
Officer Curriculum
Student Reps

Programme Year Student Reps

Reviews

Curriculum
Committee

28
6 External Examiner

The External Examiner will be a member of staff of another University or similar body who is
experienced in the subject area of your programme of study. The role of the external examiner
is to assure the standard of your award when compared to similar awards of other institutions,
to assure the integrity of the assessment process and to comment on the quality of the learning
opportunities given by the University.

Details of the external examiner who oversees your programme are listed below. You should
not contact the external examiner directly. Hull University Union, Course Representatives and
Student Representatives work with the University to oversee the management of Quality and
Standards of the Universitys programmes, including external examiner reports. You are
encouraged to liaise with your Course Representative and Hull University Union.

Computer Science

BSc/MEng Computer Science, BSc Information Systems, BSc Computing: Professor David
Walker, University of Cardiff

BSc/MEng Computer Software Development, Computer Science (Software Engineering),

Computer Science with Games Development, Computer Science for Games Development,
Computer Systems Engineering, Computer Science (Embedded Systems): Dr Andreas
Mauthe, University of Lancaster

7 Information on Professional Bodies

The British Computer Society (BCS) is the professional institution which accredits computer
science degree programmes in this country. The BCS is a member of the Engineering Council
which has been chartered by the Government to regulate the engineering profession.
Following the last BCS accreditation visit in 2012 all our established BSc and MEng degrees
were awarded full exemption from the BCS Professional Examination as well as partial CEng
accreditation. This is the highest award that three-year Honours courses can achieve.

Computer Science is proud of having its degrees accredited by the appropriate professional
institution. Students should realise the importance of this to their professional development.
Not only are you working towards an Honours degree but also that qualification can lead onto
professional qualifications. To emphasise the importance of the Society, the Computer
Science pays for student membership of the BCS for each student registered on one of its
degrees.

British Computer Society Events

The local branch of the British Computer Society meets regularly, sometimes in the University,
and welcomes student members of the Computer Science. Details of meetings are placed on
the BCS noticeboard outside the Computer Science Office and on the BCS Humberside
Branch web pages. The BCS Humberside branch also awards the University of Hull Computer
Science MSc prize each year. Eur Ing Brian Tompsett is on the BCS Humberside Branch
Committee and can be contacted for information about student membership and meetings of
the local Branch. Details of local branch meetings and other activities are on the web page
at http://www.humberside.bcs.org/. Further information on the BCS at national level can be
found at http://www.bcs.org/.

29
8 Prizes

In addition to a number of Faculty level prizes which are outlined in section 6 of the Student
Handbook, there are a number of subject level prizes which are normally awarded each
year.

Please note that the list of prizes is under review and may therefore change.

Computer Science
Computer Science Prize (awarded to the finalist with the best all round result, usually
requiring a first class performance)
G B Cook Prize in Computing: Best Project in the Honours Stage
G B Cook Prize in Computing: Outstanding Performance in the Honours Stage
G B Cook Prize in Computing: Outstanding Performance in the Diploma Stage
Computer Science Achievement Award

9 Postgraduate Study

The School offers opportunities for postgraduate study and research in a range of topic areas,
leading to MSc and PhD degrees by thesis.

A presentation on postgraduate study (MScs and PhDs) is given to final year students in the
spring of each year. Finalists requiring more information prior to this, for example more
detailed description of current research projects or MSc programmes, should consult the Web
at:
http://www2.hull.ac.uk/prospectus/postgraduatesubjectbrochures.aspx
http://www2.hull.ac.uk/science/phd.aspx
http://www2.hull.ac.uk/science/computer_science/research.aspx.

10 Safety
A health and safety form will be completed by students during induction, which is designed to
identify any problems students have which may affect their safety in gaining access to and
performing laboratory work. The information provided by students on this form is regarded as
confidential by the Safety Officer.

Safe Use of PCs and Computer Terminals

Do not use any computer equipment which appears to be unsafe; you have a responsibility in
law to report any items which are, or appear to be, unsafe.

Incorrect use of computer equipment may lead to eye, upper limb or back disorders. If any
discomfort is experienced while using PCs and computer terminals, please inform the
Computer Science Safety Officer immediately.

Before using PCs and computer terminals, position the chair, keyboard and screen so that a
comfortable working position is achieved. Sit straight in the chair and don't rest wrists on the
edge of the table. Don't use the equipment for extended periods; the current recommended
guideline is a 5 minute break for every 30 minutes.

30
Annexe 1: Resits in Modules Passed by Compensation

The Universitys Undergraduate Programme regulations allow up to 40 credits to be passed

by compensation at each stage (year of study) of your degree, subject to various conditions
having been met. However, to be awarded an Honours or Ordinary degree, a student must
have a total of no more than 60 credits of modules overall passed by compensation (or
condoned in the final year). Due to this 60 credit restriction, Computer Science has the
following advice:

Students at the end of the Certificate Stage

Computer Science strongly recommends that all students take resits in any module that has
been passed by compensation (modules in this category will be marked PC on your
notification of results which you will receive in July).

If you take the resits as recommended and get lower marks, your original marks (i.e. the higher
of the two) will stand as compensatable. If you pass the resits, you will still have the full
allowance of 60 credits available for compensation/condonement if needed in future years.

Students at the end of the Diploma Stage

Computer Science strongly recommends that students try to reserve 40 of the 60 credits which
can be passed by compensation/condonement for the final year. We do not want you to be in
a situation whereby you cannot graduate because you have too many credits in the
compensatable range.

Any student with a total of more than 20 credits passed by compensation, whether carried
forward from the Certificate Stage and/or from the Diploma Stage, is strongly recommended
to take resits in all Diploma Stage modules which have been passed by compensation
(modules in this category will be marked PC on your notification of results which you will
receive in July).

Should you take resits and get lower marks, your original marks (i.e. the higher of the two) will
stand.

MEng students at the end of the Honours Stage

Computer Science strongly recommends that students try to reserve 40 of the 60 credits which
can be passed by compensation/condonement for the final Masters year. We do not want you
to be in a situation whereby you cannot graduate because you have too many credits in the
compensatable range.

Any student with a total of more than 20 credits passed by compensation, whether carried
forward from earlier stages and/or the Honours Stage, is strongly recommended to take resits
in all Honours Stage modules which have been passed by compensation (modules in this
category will be marked PC on your notification of results which you will receive in July).

Should you take resits and get lower marks, your original marks (i.e. the higher of the two) will
stand.

If you are in any doubt about the above advice, you should contact the Director of
Undergraduate Studies, the Examinations Officer or your personal supervisor for clarification.

Please note that final year direct entrant students are not permitted condonement and must
therefore pass 120 credits to achieve an honours degree.

31
Annexe 2: Software Engineering Code of Ethics and Professional
Practice

Introduction
In the process of becoming a professional software engineer it is important to understand not
just the process of software development but the social, ethical and legal aspects of the
profession.

As a guide for the software engineering profession, the ACM and IEEE (two international
bodies representing the computing profession) have approved a code of practice. This code
of practice comes in two versions, the shorter of which is presented below and a full code
available at: (http://intra.net.dcs.hull.ac.uk/student/ug/Handbooks/Forms/AllItems.aspx and
http://www.acm.org/about/se-code)

Code of Practice (short version)

The short version of the code summarizes aspirations at a high level of the abstraction; the
clauses that are included in the full version give examples and details of how these aspirations
change the way we act as software engineering professionals. Without the aspirations, the
details can become legalistic and tedious; without the details, the aspirations can become high
sounding but empty; together, the aspirations and the details form a cohesive code.

Software engineers shall commit themselves to making the analysis, specification, design,
development, testing and maintenance of software a beneficial and respected profession. In
accordance with their commitment to the health, safety and welfare of the public, software
engineers shall adhere to the following Eight Principles:
1. PUBLIC - Software engineers shall act consistently with the public interest.
2. CLIENT AND EMPLOYER - Software engineers shall act in a manner that is in the
best interests of their client and employer consistent with the public interest.
3. PRODUCT - Software engineers shall ensure that their products and related
modifications meet the highest professional standards possible.
4. JUDGMENT - Software engineers shall maintain integrity and independence in their
professional judgment.
5. MANAGEMENT - Software engineering managers and leaders shall subscribe to and
promote an ethical approach to the management of software development and
maintenance.
6. PROFESSION - Software engineers shall advance the integrity and reputation of the
profession consistent with the public interest.
7. COLLEAGUES - Software engineers shall be fair to and supportive of their
colleagues.
8. SELF - Software engineers shall participate in lifelong learning regarding the practice
of their profession and shall promote an ethical approach to the practice of the
profession.

These 8 statements become a lot clearer once you read the full code of practice.

Student perspective

The original code has been presented here as it is important that you are exposed to it, as it
will provide the foundations for your future career. No attempt has been made to alter it to a
student perspective, as this could lead to confusion. Instead, whilst studying at Hull you should
consider the following:
PUBLIC the staff and students at the University, as it is unlikely that your software
will impact the general public.

32
 CLIENT AND EMPLOYER Computer Science staff and fellow students. Obviously,
sponsored students may also have an employer.
PRODUCT your assessed course work, practical work or examinations
MANAGEMENT during group work, when you are assigned as team leader.

33
Annexe 3: Practical Work

1. Attendance

Students will be expected to log in to PCs in compulsory labs to record their attendance.
Failure to attend or to log in will result in the issuing of cause for concern emails, which can
escalate to attendance warnings and, ultimately university warnings.

2. Certificate Stage (Year 1)

The practical work is intended to reinforce the material taught in lecture based modules. This
work provides students with the opportunity to develop skills in programming, software
engineering, information structures and small business systems; to familiarise them with the
software interface to hardware, and in logic design.

The objectives of the programming coursework are twofold. The first is to allow students to
practise design, implementation and testing of well-structured programs. The initial
programming language used is C#. A number of exercises are attempted, using the concepts
introduced in associated lectures. The second objective is to give students an appreciation of
implementing software as part of the software liFEN-cycle.

There is also coursework associated with most lecture based modules. The type of
coursework depends upon the module it supports. The coursework aims to reinforce the
content of the lectures and to allow the students to apply relevant methods and techniques.
Work undertaken may involve essays, background reading, review and critical assessment,
paper based exercises or small assignments in computer laboratories. Much, or all, will be
assessed.

Software engineering team projects are undertaken by all students during the calendar year.
The main objective is to apply the software engineering methods and techniques introduced
in lectures to a software development project. But additionally, the project allows students to
develop their communication, teamworking and management skills and to give an insight into
the complexities of `programming in the large'.

3. Diploma Stage (Year 2)

There is assessed coursework associated with each lecture based module. It provides
reinforcement of the techniques and methods introduced in lectures and experience with
related software tools. The coursework undertaken may involve essays, paper based
exercises or practical assignments in computer laboratories. A Software Laboratory is
organised in which demonstrators give support for computer-based assignments deriving from
various modules.

The requirements and analysis phases of the Software Engineering Team Project is
undertaken in Year 2. Each team gives a presentation at the end of the week to all other
teams and to staff who have acted as clients. The objective of a teams presentation is to
convince the audience that this team has the best design and should be awarded the contract.

4. Honours Stage (Year 3)

As for earlier stages, assessed coursework is associated with each lecture-based module, but
the major element of practical assessment in the Honours Stage is the major individual project
worth 40 credits or the IT internship module (08130) for Information Systems students.

34
The project module has several objectives and benefits, chiefly to allow students to show their
all-round ability to tackle a substantial piece of computer-related investigation or software
design and development work, to demonstrate project- and time-management skills and to
bring the task to a successful conclusion with a quality report and presentation. Within this
overall context however, the actual work done can vary widely between different projects. A
glance at lists of past projects allocated (see the 3rd year noticeboard or web) will indicate the
variation of topics, according to the differing interests both of students and staff, and current
research areas in computer science.

Project topics and project supervisors are normally allocated to students during trimester 2 of
the second year (including students on an industrial or study abroad year out), or during the
summer preceding final year for students joining computer science for their final year only.
Students may propose their own project topic, but a range of topics suggested by academic
staff are also made available to choose from. Full information on the process of choice and
allocation is explained to Diploma Stage students early in trimester 2, but it is never too early
to begin to think about possible topics and to seek advice from potential project supervisors
amongst the lecturing staff.

As soon as students have their topic and project supervisor confirmed, the first project meeting
should be arranged and work commenced. This should occur before the end of trimester 2 of
the Diploma stage for the majority of students, so preparatory reading and background studies
can start during the summer vacation. For all students, a Project Supervisor meeting must
take place urgently at the beginning of the final year, to progress work and prepare the first
formal deliverable.

Projects are assessed through several mechanisms in addition to the Final Report and
Presentation (which are delivered towards the end of trimester 2).

The IT Internship module enables students to gain experience in the skills and practices of
commercial software development by working on real commercial software development
projects provided by Seed Software, computer sciences reach-out project which provides
commercial software development services to customers with bespoke software development
needs. Students work in teams with MEng students to implement solutions for real customer
needs gaining practical experience of team working, customer liaison, requirements elicitation,
software design, software implementation and testing, maintenance and debugging, planning
and project management.

5. Masters Stage (Year 4 MEng only)

As for the earlier stages, assessed coursework is associated with each lecture-based module.
Practical work is carried out on both an individual and team basis and is largely laboratory
based.

In addition to practical work associated with the lecture-based modules, all MEng students
undertake the 40 credit Commercial Development Practice module in their final year. This
module enables students to gain experience in the skills and practices of commercial software
development by working on real commercial software development projects provided by Seed
Software, computer sciences reach-out project which provides commercial software
development services to customers with bespoke software development needs. Students
work in teams to implement solutions for real customer needs gaining practical experience of
team working, customer liaison, requirements elicitation, software design, software
implementation and testing, maintenance and debugging, planning and project management.

35