Project Handbook 
P​ROJECT​ A​ ND​ P​ROFESSIONALISM​ ​WITH​ C​OMPUTER​ S​CIENCE​ A​ RTIFACT 
(6CS020) 

1 
 Table Of Contents 
Project - Professionalism and Project Module 4 

Project Types 4 

BCS Requirements 4 

British Computer Society (BCS) – Chartered Institute for IT Accreditation 5 

Copyright 5 

Ethical Considerations Form 6 

Professionalism and Project Submissions and Assessments 6 

Assessment 1 6 

Assessment 2 7 

Supervisors and Readers 9 

Guidelines for Supervisors and Readers 9 

Resit and Retake Requirements 10 

Appendix - Project Example Types 11 

Example1 – Software and/or Hardware Solution (Prototype) 11 

Example2 – Design and Testing (Complex system) 12 

Appendix - Project LogBook Entry Template 13 

Appendix – Project Proposal Report - Pass/Fail 14 

Project Proposal Format/template 15 

Appendix - SUPERVISORS' Project Proposal Report Marking/Feedback Sheet (0%). 17 

Appendix - Project Presentation Feedback Form 18 

Appendix – Project Poster Assessment 2.1 (10%) 19 

Guideline for Poster Presentation 19 

Appendix - Project Poster Assessment 2.1 (indicative 10%) Marking and Feedback Sheet 21 

Appendix - Final Project Report Structure 22 

Appendix  -  SUPERVISORS’  Project  Report  and  Project  Management  (including  artifact  and 

2
Poster) Marking Sheet 24 

Appendix  -  READERS’  Project  Report  and  Project  Management  (including  artifact  and Poster) 
Marking Sheet 26 

Appendix. Final Project Report Title and Declaration Sheet 27 

Assessment 1: Professionalism Marking/Feedback Sheet (25%) 29 

Appendix. University Performance Descriptors FINAL 30 

 
 
 
   

3
1. Project - Professionalism and Project Module 
Please note that this handbook ONLY covers the Project part of the module.  

The  project  subject  matter  ​must  be related/appropriate to the course being studied. The nature 

of  the  project  will  be  ​to  address  an  academic  issue  and  ​answer  an  academic  question​.  The 
project could be centred on:  

1.1. Project Types 

○ The development of a software or hardware solution development or, 
○ Investigation of an algorithm, 
○ Create a testable design for a complex system,  
○ Comparison between the existing system with complex comparison tools  

All  students  must  follow  the  development  life-cycle,  with  the  aim  of  producing  an  artifact.  A 
typical  artifact  could  be  a  software  or  hardware  prototype  or  an  algorithm developed to meet a 
specification,  the  artifact  will  be  used  to  answer  the  academic  question.  Must  provide  a 
justification of tools and techniques used throughout the project. 

1.2. BCS Requirements 

In  order  to  pass  the  Module,  a  Student  MUST  meet the requirements of the BCS (The Chartered 
Institute of IT), see details below. 

○ The Project must be practical and problem-solving in nature;  

○ The Project must include an artifact; 
○ The Project must include the development cycle, including testing; 
○ The Project must justify development tools and techniques; 
○ The Project must be related to your course of study; 
○ Students  must  produce  a  Project  Poster  which  will  be  used  as  a  dissemination 
document and act as a visual presentation of the project. 
 
Students  will  also  be  required  to  include  ​additional  relevant  supporting  work  in  order  to 
demonstrate  the  quality/accuracy  of  the  work  produced,  to  validate/test  what  has  been 
discovered and to demonstrate understanding. 

All  students  will  be  allocated  a  supervisor  who  will  act  as  a  mentor  for  the  project.  The 
supervisor  will  also  be  responsible  for  marking  the  project.  Students  must  attend  ​regular 
supervised project meeting. 

All  projects  will  be  allocated  a  Reader.  The  role  of  the  Reader  is  to  offer  additional  support  to 
the project as a whole and to also mark the final project submission. 

All  students  are  required  to  produce  a  report  of  the  work  carried  out.  Report  is  to  act  a​s  a 
container  for  all  the  work  carried  out  on  the  project.  Report  must  include:  ​a  Literature  review, 

4
 details  of  the  artifact  produced,  address  the  academic  question,  other  relevant  supporting 
work,  conclusions  and  critical  evaluation  of  all  work  carried  out​, further details can be found in 
the project lectures and in this handbook. 

Project  management  skills  must  be  demonstrated  ​throughout  the  project.  Students  are 
expected  to  attend ​all supervised sessions with their supervisor, this will enable your supervisor 
to  monitor  progress  on  the  project.  A  log  book  entry  template  is  shown  in  ​Error!  Reference 
source  not  found..​.  You  are  also  expected  to  produce  a  plan  for  your  project  in  the  form  of  a 
Gantt chart and show your progress on the project. 

2. British  Computer  Society  (BCS)  –  Chartered  Institute  for  IT 

Accreditation 
The  course  (including  the  Professionalism  and  Projects  module)  is  BCS accredited, this means 
that  you  can  apply to join the BCS without having to pass the BCS entrance examinations - there 
is a fee involved. Y​ ou must pass the projects module at the first attempt (no resit). 

BCS  accreditation  is the recognition by the BCS professional body that a student graduated with 

a  BCS  accredited  degree  and  has  obtained  all  the  necessary  academic  requirements  for  being 
entitled  to  register  as  Chartered  or  Incorporated  Engineer  (CEng/IEng)  at  the  BCS  professional 
institution.  Students  with  BCS  accredited  degrees  will  not  be  required  to  undertake  further 
academic  examinations  by  the  BCS  institution  when  they  apply  to  register  as  a  chartered  or 
Incorporated Engineer (CEng/IEng). 

The  BCS  expects  a  substantial  project  to  provide  a  major contribution to the computing-related 

practical  abilities  which  the  students  should  acquire.  It  is  expected  to  be  a  problem-solving 
project,  and  it  is  desirable  that  it  should  meet  a  real  need  in  an  industrial  or  research  context 
and  have  an  identifiable  client other than the student.  This may be interpreted as some or all of 
the  systems  life  cycle.  In  the  project,  students  are  expected  to  apply  the  principles,  skills,  and 
tools to which they have been introduced throughout the course.  

In order to be eligible to apply form accreditation the project must be passed at the first attempt 
(no resit) 

3. Copyright 
It  is  acknowledged  that  the  author  of  any  project  work  shall  own  the  copyright.   However,  by 
submitting  such  copyright  work  for  assessment,  the  author  grants  to  the University a perpetual 
royalty-free  license  to  do  all  or  any  of  those  things  referred  to  in  section  16(i)  of  the Copyright 
Designs  and  Patents  Act  1988  (via:  to  copy  work;  to  issue  copies  to  the  public;  to  perform  or 
show or play the work in public; to broadcast the work or to make an adaptation of the work). 

5
 4. Ethical Considerations Form 
Within  the  project  registration  form,  there  is  a  short  set  of  ethical  approval  questions.  Please 
make  sure  that  you  download  the  form  and  ​complete  before  the  end  of  Week  3  and  submit  to 
the assignment tab on Canvas. 

5. Professionalism and Project Submissions and Assessments  

Dates of submission are shown in the grid at the beginning of this Handbook. 

Important​: In order to pass the module you must pass both Assessment 1 and Assessment 2. 

5.1. Assessment 1 
○ Summative - Professionalism Assessment 1 (25%)  
○ Formative - Project - Project Registration Form (PRF) 
○ Formative- Project Proposal Report- PPR (Pass/Fail) 
○ Summative- Presentation slide(s) (Pass/Fail) – (5 min max, 4-5 slides max) 
○ Formative - Ethical Considerations Form 
○ Formative - Supervisor and Reader review of presentation 
 
The module team reserves the right to change the allocated supervisor of a project. 

The  purpose  is  to  capture  project  information  (interests)  to enable the module team to allocate 

a  supervisor.  It  is  important  to  submit  this  form  on  time.  This  will  take  the  form  of  a  project 
proposal  report,  to  be  submitted  via  Canvas.  Two  submission  attempts  are  allowed  in  order  to 
obtain  a  Pass  grade.  If  a  Pass  grade  cannot  be  obtained,  by  the  start  of  week  6,  the  student 
MUST contact the module leader. Further details are available in the Appendix. 

A  BCS  requirements  check  will  be  made  to  ensure  that  the  project  is  likely  of  meeting  the 
requirements. 

If  your  project  requires  ethical  approval  a  separate  form  must  be  completed  which  will  be 
evaluated by the Faculty Ethics Committee. You should discuss this with your supervisor. 

Contents  to  include:  Overview  of  the  project  and  progress  made.  The  Objective  is  to  discover 
projects in difficulty and create an action plan. 

6
5.2. Assessment 2 
○ Formative - Draft Report ( No grade will be provided) 
○ Summative - Project Report (75%) 
○ Summative  –  Project  Management  document  (logbook,  Gantt  chart,  Tracking 
Gantt chart, project management docs) 
○ Summative  -  Project  Poster  Assessment  2.1  (10%,  mark  included  in  final  project 
mark) 
○ Summative - Project Demonstration (artifact) 
 
Used  as  a  dissemination  document  and  act  as  a  visual  presentation  of  the  project.  Further 
details are provided in the lecture notes and in the Appendix. 

The  demonstration  is  a  compulsory  part  of  the  project.  ​You  must  arrange  a  demonstration  of 
your artifact before leaving the University. 

Note: You should continue working on your project while your draft is being read. 

Final  project  report  and  project  management  document  assessment  is  A  SUMMATIVE 
assessment. 

An  electronic  copy  must  be  submitted  to  Canvas.  Check  with your supervisor and reader to see 
if  they  require  a  hard  copy,  if  required  submit  to  the  registry,  YOU  MUST  STILL  SUBMIT  AN 
ELECTRONIC VERSION TO Canvas. 

The  detailed  structure  and  contents  will  be  individual  to  the  project  but  must  contain  sections 
on  Literature  review,  the  design,  development,  and  testing  of  a  suitable  artifact,  conclusions, 
and  critical  evaluation.  A  typical  structure  of  a Final Report and writing style details is shown in 
the Appendix. At all times be guided by your supervisor. 

The  average word count for the Final Report is expected to be approximately 10000 words, 8000 
-  12000  words  is  acceptable. If the word count is significantly different then you should discuss 
this with your supervisor. 

All  Final  project reports will be submitted to Turnitin (TII), plagiarism detection software. Please 

visit ​http://www.wlv.ac.uk/default.aspx?page=27457 

The UoW - Web site for Guidance and Support for Turnitin.  

​ ttp://www.wlv.ac.uk/default.aspx?page=27461​" 
h

Do  not  include  the  proposal  or  any  project  management  details  here  –  Turnitin  will  detect 
similarities to other students work.  

7
Project Management 

A  SUMMATIVE  assessment.  An  electronic  copy  submitted  to  Canvas.  No  hard  copies  are 
required.  A  separate  document  and  submission  should  be  used to include project management 
details  in  order  to  demonstrate  that  the  project  has  been  successfully  managed.  ​Students  are 
expected to attend​ all​ supervised sessions with their supervisors. 

The  details  of  project  management  should  include  as  a  minimum:  The  logbook  entries,  initial 
and  final  Gantt  chart,  agreed  with  changes  to  the  project,  etc.  You  may  wish  to  comment upon 
your project management in the critical evaluation section of the final report. 

A log book entry template can be found in the Error! Reference source not found. 

8
 6. Supervisors and Readers 
6.1. Guidelines for Supervisors and Readers 
The following is a set of guidelines outlining the duties of supervisors and readers. 

1. A  member  of  staff  will supervise a number of students. Supervision may be a group or 

individually based. 
2. It  is  strongly  recommended  that  supervisors  keep  a  record  of  student’s  attendance, 
progress  and  log  books  for  each  supervised  session.  SAMS  is  an  excellent  place  to 
record meetings. 
3. Format of the session: Supervised sessions may be individual or group based. 
4. Project  progress  discussion:  Consider  Gantt  chart,  problems,  and  progress.  Provide 
support and guidance to the student. 
5. Supervisors should check students’ logbook entries. 
6. Requirements of supervisors: 
6.1. Supervisors  will  be  available  and  meet  with  students  for  all  supervision 
sessions.  If  unable  to  attend  the meeting supervisors should contact the 
Reader in the first place. 
6.2. Supervisors  are  required  to act as a mentor to students. To offer support 
and advice and to guide the students through the project process. 
6.3. Supervisors  are  required  to  monitor  and  record  the  progress  of  the 
student,  check  logbook  entries  and  notify  the  module  leader  of  any 
significant problems/issues (i.e. students not attending). 
6.4. If  possible,  supervisors  are  required  to  offer  subject-specific  advice  in 
the  subject  area  of  the  project.  Where  this  is  not  possible  supervisors 
should direct students to other staff/resources for additional support. 
6.5. Supervisors  are  required  to  mark  and  provide  feedback  on  all 
submissions  and  assessments  submitted  by  the  student  as  guided  by 
the  module  leader.  All  project  final  reports  must  be  submitted  to 
‘Turnitin’,  the  University  preferred  the  plagiarism  detection  system.  If 
academic  misconduct  is  suspected  it  is  the  responsibility  of  the 
supervisor  to  submit  all  necessary  paperwork  to  the  school  office  and 
notify  the  module  leader.  A  result  of  AM  (Academic  Misconduct  -  under 
investigation)  should  be  submitted  on  the  mark  form  as  required.  All 
results  are  to  be  uploaded  to  Canvas  and  only  emailed  to  the  module 
leader under exceptional circumstances. 
6.6. Supervisors  and  readers  are  required  to  attend  the  project  presentation 
and artifact demonstration. 
6.7. Unplanned  supervisor  absences  will  be  covered  as  per  the  module 
absence cover process. 

9
 7. Requirements of readers 
7.1. Readers  are  required  to  provide  supervised  sessions  for  the  student  in 
exceptional circumstances when the supervisor is not available. 
7.2. Readers  are  required  to  attend  the  short  presentation  of  the  student's 
project and offer support and advice. 
7.3. Readers  are  required  to  attend  the  artifact  demonstration, mark the final 
report  and  provide  additional  support  for  the  project.  The  reader  is 
required  to  enter  all  marks,  feedback  and  associated  documentation  to 
Canvas, before the deadline for entering marks into registry systems. 

7. Resit and Retake Requirements 

All  students  will  be  provided  with  feedback  on  their  Final  Project  Report  and  Project 
Management  document  submission.  If  you  fail  to  obtain  feedback  please  contact  your 
supervisor as soon as possible. 

Students  who  are  awarded  <40%  for their final project submission will have additional feedback 

as  to  the  specific  areas  of  the  project  that  failed  to  meet  the  minimum  pass  requirements  for 
the project.   

Students  with  <40%  will  have  the  opportunity  to  do  further  work  on their project and resubmit a 
revised  version  of  their  project  (report/artifact)  during  the  resit  period.  Students  may  also  be 
requested by their supervisor to participate in an additional demonstration. 

  ​If  a  student  is  required  to  retake  ​the  project,  they must complete the entire process again with 

a  ​new  project  and  must  submit  all  assessments,  including  those  that  have  previously  been 
awarded passing mark. 

Resit  dates  will  be  provided  on  the  Canvas  topic  (if  not  available  please  contact  the  module 
leader) 

10
 8. Appendix - Project Example Types 
The  following  examples  of  projects  are  intended  to  demonstrate  a number of different types of 
acceptable projects​.  

8.1. Example1 – Software and/or Hardware Solution (Prototype) 

A student will have an academic issue to investigate. Typical questions could include: 

● Implementing software and/or hardware solution to a problem 

● A comparison of software algorithms 
● A comparison of hardware designs 
It  is  anticipated  that  a  detailed  design  and  testing  phase  would  be  required  for  the  software 
and/or  hardware  solutions.  The design phase would lead to an artifact in the form of a software 
and/or hardware prototype. 

Generic Pattern 

In order to demonstrate the quality and accuracy of the prototype, testing would be required. 

[Sample] Academic Question:  

Is there a more effective approach to implementing a Web-Based Auction site? 

Aims and Objectives:  

What is the main objective to devise this system?  

Process​:  

○ Using/justifying/demonstrating the development life cycle.  

○ Research auction sites,  
○ Analysis/investigation of existing systems, 
○ Determine software/user requirements,  
○ Design solution(s) using the most appropriate tools and techniques,  
○ Design testing methods, Implement and testing the prototype. 
○ artifact: Prototype Website - Design, implementation, and testing.
Report:  

To  contain  details  of  the  literature  review.  Include  compare/contrast/evaluation  of  material 
found,  otherwise  it  is  simply  a  list  of  material  found.  Analysis  and  Specification,  artifact  – 
Design,  implementation  and  testing  details.  Answer  to an academic question from the research 
and  results  of  the  prototype.  Also  include  justification  of  approach  adopted  and  value  of  the 
final design, Testing, Conclusions. Critical evaluation, etc. Project management details. 

11
8.2. Example2 – Design and Testing (Complex system) 
** Important - The system must be of suitable complexity ** 

A  student  will  have  an  academic  issue  to  investigate.  Typical  questions  could  include  finding 
the  most  suitable  design  for  a  software  solution,  a  comparison  of  designs  for  a  software 
solution.  Requirements  can  be  provided  to  the  students,  or  determine  through  requirements 
gathering  by  the  student.  The  student  will  select  a  suitable  design  method,  design  the solution 
to  the  problem,  and  undertake  the  testing  of  the  design  produced.  ​It  is  anticipated  that  the 
design  would  be  of  significant  complexity  to  meet  the  requirement  of the BCS. ​The design and 
testing phase would produce an artifact possibly in the form of a design and testing document​. 

Generic pattern 

[Sample] Academic Question:  

What is the most effective design for a unified staff workshop marking system? 

Aim and Objectives:  

Project dependent. 

Process:  

Research  University’s  information  requirements,  design  methods,  similar  systems,  select  an 
appropriate  design  method  for  the  project,  build  a  suitable  design  for  the  problem  (data 
manipulation and interfaces), and provide suitable and relevant testing for the design.  

artifact:  

A design and testing document for the current and proposed design. 

Report:  

Literature  review/research  (all  Projects),  the  artifact  -  design,  and  testing document. Answer to 

an  academic  question  using  the  design  and  testing  document.  Justification  of  design  and 
testing  approaches  used,  etc.  Critical  evaluation  (all  projects).  Project  management details (all 
projects). 

** Important - The system must be of suitable complexity ** 

12
9. Appendix - Project LogBook Entry Template 
Student Name: Supervisor:
Student No: Date:
 

Date:  

Meeting Agenda: 

1. To discuss the similar existing system 

2. To discuss the potential programming language for the proposed system 
3. Agenda 3 
4. Agenda 4 

Any Deliverable:  

1. SRS Document 
2. Or, Prototype 
3. testing module 
4. subsystem 

Feedback from Supervisor: 

- You  might  want  to  look  for  a more existing system. The system (XYZ) provided is a very 

good one for the reference, do study more on that.  
- For  this  kind  of  system,  you  have  chosen  PHP  programming  language  which  might  be 
the option, so go ahead and you can achieve your system requirement.  

Tasks for Next meeting: 

- To come up with the demo of a simple login feature required for your system.  

** Note: There should be at least 15 Logbooks. **  

   

13
10. Appendix – Project Proposal Report - Pass/Fail 
Supervisor:  - Complete  the  marking/feedback  sheet  provided  and  upload  the  marking  sheet 
to Canvas. 
Module Leader:  - Check results entered and feedback sheets. 
 

Important notes on  

- The word count should be approximately 2000-3000 words. 

- The  project  proposal  report  should  be  produced  as  a  result  of  discussions  with  your 
supervisor. Please refer to the marking sheet provided as a guide to completing Report. 
- The Report should be written in a professional style. 
- Please refer to the marking sheet provide for additional information. 
- If  you  fail  to  pass  this  proposal  you  have  the  opportunity  to  submit  again.  If you do not 
pass by the allocated window of time, consult to your project coordinator  
- Please  be  aware  of  the  Supervisor's  checklist  to  cover  the  British  Computer  Society 
(BCS)  accreditation  requirements,  this  can  be  found  on  the  Supervisor's  marking  sheet, 
(in the Appendix) 

- If  your  client  is  an  ‘external’  person  or  body  you  will  need  to  complete  an  external 
agreement form. You will still require a supervisor from the University. 

14
10.1. Project Proposal Format/template 
The project proposal report should be arranged under the following sections: 

1. Front Page: STUDENT DETAILS 

a. Provide a front sheet to the proposal to include the following: 
i. Full Name (Surname, Forename(s)) 
ii. Student Number 
iii. Award/Course 
iv. Your University email address 
v. Full name of your Supervisor and Reader (if known) 
vi. Date of submission 
b. Table of Contents Page 
2. SECTION 1: STATEMENT OF PROJECT DETAILS 
a. Provide a statement of the project details only. 
b. Project Title 
c. Academic Question  
d. Aims/Objective (provide a list) - SMART objective  
e. Artifact (proposed) to be developed ​(in brief) 
3. SECTION 2: PROJECT PROPOSAL (Main Section of Report) 
a. Background  to  the  project  including  why  you  have chosen the project. Explain in 
detail what you intend to do.  
b. Provide further details of the academic question. 
c. Initial Research into sources of information (Literature Review) 
i. Please  note  that  the  Initial  Research  into  sources  of information is not a 
full  Literature  Review,  ​(A  full  Literature  Review  will  be  required  for  the 
final project report). 
ii. The  Initial  Research  into  sources  of  information  is  used  to  obtain  a 
better/clearer  understanding of the project at a very early stage​, it can be 
used  to  refocus  or  define  the  project  at  an  early  stage,  whereas  the 
literature  Review  is  a  review  of  all  the  relevant  material  to  show  that  a 
project  is  founded  upon  an  academic  basis  and  can  be  used  to  help 
solve/execute the actual project​. 
iii. The  Initial  Research  into  sources  of  information  can  in part be similar to 
an  Annotated  Bibliography.  It  is  a  brief  account  of  the  material 
discovered,  on  a  given  topic,  at  an  early  stage  of  a  project.  You  are  not 
accepted  to  have  fully  read  all  the  material  discovered  but  to  have  an 
overview  of  the  contents  of  the  material.  It  should  enable  you  to  judge 
the  relevance  and  value  of  the  material  discovered  in  your  project.  The 
Initial  Research  into  sources  should  be  as  broad  as  possible  covering  a 
range  of  different  sources.  The  initial  research  may  consist  of  a  sample 
of  the  material  discovered  so  far,  you  are  not  expected  to  have 

15
 discovered all sources at this stage. 
iv. It  can  be  presented  as  a  list  of  research  sources  discovered,  including 
concise  descriptions  and  evaluations  of  each  source  explaining  what  it 
contains and how it may be used in the project. 
v. You  should  provide  sufficient  detail  to  show  that  you  understand  the 
contents  of  the  sources  discovered.  The  sources  should  be  fully 
referenced as per the University guidelines. 
d. Artifact (proposed) 
i. Does the system all the components (design, development, and testing) 
1. Design:  what  different  design/modeling  techniques  are  you 
intending to use? 
2. Development:  What  technology/tools  (programming  language, 
tools (IDE, framework, hardware, third-party libraries …) 
3. Testing:  What  is  your  intended  testing  plan  (validation, 
verification).  What  kind  of  testing methodology are you intending 
to use (Unit testing - what framework for unit testing and such) 
ii. It  is  very  important  that  you  provide  a  clear  vision  of  your  final  artifact 
(may change throughout the development of the project. 
iii. Justification  of  the  artifact  (how  does  it  relate  to  the  academic 
question), consideration of other artifacts.  
iv. Provide  details  of  all  planned  testing  (Just  the  rough estimation of time, 
Full detailed planning will be carried out after the proposal is passed). 
e. Justification  of  the  Methodology  you  plan  to  use  (this  methodology  can  be 
changed later on). 
f. Plan/Schedule 
i. How  you intend to develop the artifact (the use of the development cycle, 
tools, and techniques planned to be used). 
ii. Provide  a  detailed  provisional  plan/schedule  identifying  major 
milestones  and  interim  deliverables, in the form of a Gantt chart. Provide 
a description of the tasks of the Gantt chart.  
g. References and Bibliography 
i. All cited articles should be listed alphabetically in Harvard Style 
4. SECTION 3: ADDITIONAL INFORMATION: 
a. Ethical Considerations Form  
i. If  required  by  the  project  approval  panel  complete  the  ethical 
considerations form with your supervisor and submit to Canvas. 
b. Resources: 
i. Identify  any  ‘special’  hardware  or  software  requirements  of  the 
dissertation.  
ii. Identify any other resources required to complete the dissertation 
c. Client: 
i. If your supervisor is to act as the client then state the name of your   

16
11. Appendix - SUPERVISORS' Project Proposal Report
Marking/Feedback Sheet​ (0%).  
Module  Code:  6CS020  Professionalism  and  Project  (40  Credit)  ​Marking  and  Feedback 
Sheet - PASS/FAIL 

Student No:  Student Name: 

Supervisor:  Date: 
 

Assessment    Comments 
Criteria  
BCS Check  ● The  project  must  be practical and problem-solving in   
  nature.   
● Typical artifacts: 
● Software/hardware/system(s)  development  to 
produce a fully working  or  prototype  based  system 
OR 
● The implementation of a suitable  algorithm 
OR 
● The  development  of  testable  design  of  suitable 
complexity? 
● Is the project related to the course of study? 
● Includes design, development, and testing? 
Report   Introduction:   
  Background to the project, what you intend to do.  
consider Details/clear/level of understanding/etc. 
  Initial research into sources of information:   
Consider Range and quality: 
Up to date, papers, articles, web, etc.   
  Report:   
consider Structure, Spellings/grammar.   
References. 
  Project Plan   
Consider Level of detail, Planning. 
Milestones and interim deliverables 
The artifact  artifact:   
(Proposed) 
consider  Meets  BCS  accreditation,  Level  of  detail  provided, 
appropriate to the project, justification of the artifact. 

Planned Development - analysis, design, testing. 

17
12. Appendix - Project Presentation Feedback Form 
Project Recovery Action Plan (for projects in difficulty) 

Supervisor/Reader/Student  Important.  This  form  is  to  be  completed as a result of identifying a 'project in 

difficulty'  at  the  Project  presentation.  The  Supervisor,  Reader,  and  student 
should meet to complete the action plan below. 
The plan should be uploaded to Canvas 
 

Last Name:   
   
First Name:   
 
Student No:   
 
 

PASS / FAIL *  If FAIL, supervisor should create a recovery plan for the student below. 
Please delete   
   
 

Task  Deliverable  Date 

     
 
 
     
 
 
     
 
 
     
 
 
     
 
 
     
 
 
     
 
 
 

18
13. Appendix – Project Poster Assessment 2.1 (10%) 
Student:  This is a Summative assessment to be submitted via Canvas.  
Supervisor:  You  should  indicate  your  marks  and  add  comments  for  each  section  electronically  on 
the  marking/feedback  sheet.  It  is  recommended  to  use  the  Word  Text Highlight Colour 
to indicate your mark for each section. 
Upload both the Marking/Feedback Sheets via Canvas. 
Module Leader:  Check all markings and uploads. 
 

Please  ensure  that  you  are  familiar  with  how  to  produce  a  poster  by  referring  to  the  project 
lectures and having research into poster development and presentation. 

Use the following links as a guide only. 

1. http://www.youtube.com/watch?v=m02leV4gxgE
2. http://www.ncsu.edu/project/posters/
3. https://www.google.co.uk/search?q=computer+science+project+posters&client=safa
ri&hl=en-gb&tbm=isch&tbo=u&source=univ&sa=X&ei=3mYmUp60N8zY0QWbnoDYD
A&ved=0CCsQsAQ&biw=1024&bih=672
4. http://www.youtube.com/watch?v=h8_oi7g6CaQ

13.1. Guideline for Poster Presentation 

The  Project  Poster  is  to  be  used  as  a  dissemination  document  for  the  project  and  to  act  as  a 
visual presentation of the project. 

The  poster  should be created on a ​single A1 (approx.) sized poster that ​summarises the project. 

Free A1 PowerPoint poster templates can be found on the Web. 

You should try to avoid copying large sections of text from your final project report. 

As a minimum the Final Project Poster should include: 

- Your name and id, Your supervisor’s name, Title, and academic question  
- Introduction to topic 
- Evidence of research (with Harvard referencing) 
- Planned aims and objectives. 
- Development of the artifact 
- Testing approaches 
- Details of the final artifact 
- Summary of conclusions including the answer to the academic question.  
- Evidence of planning and managing the project 

19
 - Evaluation of: 
o Your product 
o project process 
- References 

   

20
14. Appendix  -  Project  Poster  Assessment  2.1  (indicative 
10%) Marking and Feedback Sheet 
Module Code: 6CS020 Professionalism and Project (40 Credit)   
Note:  Marks  are  not  mechanically  calculated  but  are  a  matter  of  academic  judgment  based  on 
the U
​ niversity Performance Descriptors FINAL ​which can be found in the appendix 

Student No:  Student Name: 

Supervisor:  Date: 

Assessment Criteria  Comments 

Contents   
consider  minimum  requirements  as  specified  in 
the assessment: 
Your  name  and  id,  Your  supervisor’s  name,  Title, 
and academic question  
Introduction  to  the  topic,  evidence  of  research 
(with Harvard referencing) 
Planned aims and objectives. 
Development  of  the  artifact,  including  testing 
approaches 
Details of the final artifact 
Summary  of  conclusions  including  the  answer to 
the academic question.  
Evidence of planning and managing the project 
Evaluation  (evaluate  your 
product/findings/project process) 
References 
Style and Presentation   
consider Good flow to the poster   
Good  visual  presentation  -  use  of  colours  and 
graphics 

   

21
15. Appendix - Final Project Report Structure 
The  structure  and  contents  of  the  Final  Report  may/will  vary  due  to  the  nature  of your project - 
see your supervisor. 

Word Count - 10000 words average, 8000 - 12000 acceptable. 

Title and Declaration sheets (2) – available in the appendix 

1. Abstract 
2. Contents page including 
2.1. Main TOC 
2.2. List of Tables 
2.3. List of Figures 
3. Introduction 
3.1. Academic question 
3.2. Aims and objectives 
3.3. Brief details of the artifact produced and background to the project 
3.4. Scope and limitations of the project 
3.5. Introduce the structure of the report. 
4. Literature Review 
Research/investigation from which the remainder of the report is based upon. Include all 
key literature you have found. You are not trying to answer the academic question in this 
section. It is the basis to answer the academic question. Compare, contrast and evaluate 
what is found - show understanding. Create a discussion where possible. ​Present at least 3 
similar system you have studied (The study of similar system also acts a literature review) 
5. The Main body of Report in sections 
5.1. Full details of the artifact 
5.2. Development of the artifact 
5.3. Testing at all stages. (approaches, methods, results) 
6. Supporting information (​ if required) 
7. Answering the academic question. 
7.1. Should not be a simple statement but a section(s) where all issues from the research, 
results from the artifact are considered.  
7.2. Justification of your answer using your research, artifact and supporting information. 
8. Conclusions 
8.1. Including a reference to the initial aims of the project and academic question. 
8.2. What has been discovered 
8.3. What conclusions can be drawn from your report? 
9. Critical evaluation of the p​ roduct ​(Critical evaluation of the following) 
9.1. Final report 
9.2. Software 
9.3. Findings 

22
 9.4. Process​ - planning, management, quality of sources found, etc. You should also include 
a section on ​Self-reflection​. 
10. References and Bibliography 
11. Appendices 

23
16. Appendix  -  SUPERVISORS’  Project  Report  and  Project 
Management (including artifact and Poster) Marking Sheet  
Note.  ​Marks  are  not  mechanically  calculated  but  are a matter of academic judgement based on 
the U
​ niversity Performance Descriptors FINAL ​which can be found in the appendix 

Student No:  Student Name: 

Supervisor:  Date: 

Assessment Sections Criteria Percentage C

Project Poster Carried forward from Poster marking sheet (10%)
Assessment
Turnitin Score Add comments if >20% ​Add TII%

BCS Requirements Have requirements been met? Yes/No

Level of Challenge.
consider Difficulty/depth/breadth, Information readily available
Report & Report Structure.
Management consider Abstract, contents page, Abstract, use of appendices
Completeness, clear and well structured. Logical. Answering the Academic Question,
(Must pass) addressing the aims and objectives of the project.
Literature Search and Review
Consider Range, quality, and relevance of research.
Comparison, evaluation, synthesis of information, discussion-based, etc.
Shown understanding of literature produced
Conclusions and Critical Evaluation​.
consider To include addressing Aim and objectives of the project.
Evaluation of artifact and process. Strengths and weaknesses. Balanced argument.
Supporting information used
Report Presentation
consider Thoughts & ideas clearly expressed.
Grammar & spelling accurate. Fluent writing style.
References and Bibliography
consider References consistent and accurate. Harvard system correctly used.
Logbook / Project Management
consider Management skills demonstrated.
Detailed log book. Evidence of planning. Attendance at meetings.
The artifact artifact - Report-Specific Contents
(Must pass) consider Complete and relevant. Quality and challenge of the artifact.
Includes analysis, design, and testing of the artifact
 

Resit Details
(Required in all cases
for a failed project).
Please include
specific details for the

24
student to address
for the resit
 

25
17. Appendix  -  READERS’  Project  Report  and  Project  Management 
(including artifact and Poster) Marking Sheet  
  ​Note.  ​Marks  are  not  mechanically  calculated  but  are  a  matter  of academic judgment based on 
the U
​ niversity Performance Descriptors FINAL ​which can be found in the appendix 

Student No:  Student Name: 

Reader:  Date: 

Assessment Criteria
Sections
Project Poster Carried forward from Poster marking sheet (10%) - see supervisors mark awarded on Canvas.
Assessment
BCS Have the requirements been met?
Requirements
Level of Challenge.
consider Difficulty/depth/breadth, Information readily available
Report & Report Structure.
Management consider Abstract, contents page, Abstract, use of appendices
Completeness, clear and well structured. Logical. Answering the Academic Question, addressing the aims and objectives o
(Must pass) the project.
Literature Search and Review
consider Range, quality, and relevance of research.
Comparison, evaluation, synthesis of information, discussion-based, etc.
Shown understanding of literature produced
Conclusions and Critical Evaluation​.
consider To include addressing Aim and objectives of the project.
Evaluation of artifact and process. Strengths and weaknesses. Balanced argument.
Supporting information used
Report Presentation
consider Thoughts & ideas clearly expressed.
Grammar & spelling accurate. Fluent writing style.
References and Bibliography
consider References consistent and accurate. Harvard system correctly used.
Logbook / Project Management
consider Management skills demonstrated.
Detailed log book. Evidence of planning. Attendance at meetings.
The artifact artifact - Report-Specific Contents
(Must pass) consider Complete and relevant. Quality and challenge of artifact. Includes analysis, design and testing of the artifact
 

   

26
18. Appendix. Final Project Report Title and Declaration Sheet 
Student Name: 

Student Number:  

Location/Site:  

Module Code:  6CS020 

Module Name:  Project and Professionalism 

Project Title:  

Supervisor Name: 

Reader Name: 

Submission Date: 

(The date you handed in the assessment) 

Award Title:  

(Award Title for your project, if in doubt refer to your course/Module Registration) 

27
Declaration Sheet 

(Presented in partial fulfillment of the assessment requirements for the above award.) 

This  work  or  any  part  thereof  has  not previously been presented in any form to the University or 

to  any  other  institutional  body  whether  for  assessment  or  for  other  purposes.  Save  for  any 
express  acknowledgements,  references  and/or  bibliographies  cited  in  the  work.  I  confirm  that 
the intellectual content of the work is the result of my own efforts and of no other person. 

It  is  acknowledged  that  the  author  of  any  project  work  shall  own  the  copyright.  However,  by 
submitting  such  copyright  work  for  assessment,  the  author  grants  to  the University a perpetual 
royalty-free  license  to  do  all  or  any  of  those  things  referred  to  in  section  16(I)  of  the Copyright 
Designs  and  Patents  Act  1988.  (viz.  to  copy  work;  to  issue  copies  to  the  public;  to  perform  or 
show or play the work in public; to broadcast the work or to make an adaptation of the work). 

Student Name (Print): 

Student Number: 

Signature: ……………………………………..……. Date: ………………… 

(Must include the unedited statement above. Sign and date) 

Please use an electronic signature (scan and insert) 

   

28
19. Assessment 1: Professionalism Marking/Feedback Sheet (25%) 
Topics covered: Professionalism, code of conduct, ethics, legal issues, social aspects. 
** Must pass this assessment to pass the module overall 
Note.  ​Marks  are  not  mechanically  calculated  but  are  a  matter  of  academic  judgement  based  on  the  University  Performance 
Descriptors 

Student No: Student Name: Mark (100%)

Marker: Date:

Assessment Criteria Comments

Part 1. Structured Notes

(40%). Quality and
completeness of notes to the
tutorial questions.
Part 2. Slideshow (60%).
Students' notes clearly used
as the main source of the
presentation. (Do not simply
copy material from the
lectures/tutorials, the main
sources should be the student
notes)

How well do the presentation

address the aim and key
issues of the question?

Is the presentation coherent

and consistent?

Quality of notes added to

each slide.

Resit Details Add here...

(Required in all cases for a
fail).
Please include specific
details for the student to
address for the resit
 

29
20. Appendix. University Performance Descriptors FINAL 
  General and specific descriptors 
Use as appropriate to the criteria shown on the marking sheet. 
90-100%  Exceptional  level  of  analysis,  showing  deep  critical  engagement  with  a  comprehensive  range 
Outstanding  of  contextual  material.  Demonstration  of  independent  thought  resulting  in  highly  original  or 
creative  responses  to  the  assignment.  Provision  of clear evidence of understanding of current 
scholarship  and research based on an extensive range of relevant sources. The Extreme clarity 
of structure demonstrating the complete focus of the argument. 
No obvious errors in referencing or grammar or syntax as appropriate 
80-89%  Excellent  links  between  relevant  ideas,  theories,  and practice. Evidence of clearly independent 
Excellent  scholarship  and  the  ability  to  engage  critically  and  analytically  with  a  wide  range  of 
contextually relevant resource material.  
Demonstration  of  original  insights,  supported  by  an  extremely  well  structured  overall 
argument.  
Very few errors in referencing or grammar or syntax as appropriate 
70-79%  Very  good  links  between  a  range  of  different  ideas  and  theories.  Places,  issues  in  a  wider 
Very Good  context.  Evidence  of  a  clear  understanding  of  a  range  of  relevant  theories  and  application  of 
these appropriately. Independent ideas, well-argued and supported.  
Few errors in referencing or grammar or syntax as appropriate. 
60-69%  Clear  links  between  theory  and  practice.  Good  coverage  of  assignment  issues.  Full 
Good  understanding of core issues.  
Evidenced level of understanding of appropriate theory and concepts.  
Some small repeated errors in referencing or grammar or syntax as appropriate 
50-59%  Identifies  main  issues  and  relevant  theory.  Coverage  of  most  of  the  assignment  issues. 
Competent  Competent application of relevant theory and states obvious links to practice.  
Some repeated errors in referencing or grammar or syntax as appropriate. 
40-49%  Makes few links between theory and practice. Answers questions in a very basic way.  
Pass  Describes relevant theory accurately, and some relevant ideas offered.  
Limited coherence of structure. 
30-39%  Some learning outcomes and/or assessment criteria not met.  
Fail  Inadequate  content  with  issues  not  addressed;  insufficient  evidence  of  understanding  of 
relevant  theory  and concepts and only partial understanding shown. Very limited application of 
theory. The Use of extensively quoted passages is evident.  
Evidence  of  sufficient  grasp  of  learning  outcomes  to  suggest  that  the  student  will  be  able  to 
retrieve the module on resubmission. 
20-29%  No learning outcomes fully met.  
Fail  No  demonstration  of  adequate knowledge or understanding of key concepts or theories. There 
is no recognition of the complexity of the subject. 
10-19%  Little  attempt to engage with assignment brief and has not met learning outcomes. Inadequate 
fail  demonstration of knowledge or understanding of key concepts, theories or practices. 
0-9%  No real attempt to address the assignment brief or learning outcomes. 
fail 
 

30
 

31