CS project notes 1 Notes for Final Project Dissertation .docx

CS project notes 1
Notes for Final Project Dissertation
This document contains an overview of the marking scheme for
projects with some notes that should be useful
for planning, executing and writing up your final project
dissertation. This should be useful for anyone taking a
project module but is aimed in particular towards students in the
Computer Science course group (CS, CGT).
1 Marking Criteria
Title – Meaningful, descriptive but not too long (must not
promise anything that you do not deliver)
Abstract – brief overview of what you did (last thing to be
written)
Introduction (10%)
State the hypothesis and aims, background to subject leading to
a definition of the 'problem' or
'application domain' for your work, what you hope to achieve
(i.e. what aspect you are addressing with
your work) and how you intend to go about it (more details in
the methodology section).
Make sure you have appropriate title and achievable aims
Use of Literature (15%)
Can be in its own section but 'use of literature' applies to whole
document. Brief description i.e. (a
single paragraph) of 4 – 10 key texts (but this number rather
depends on the work you are doing) where
you say what was useful for your work. Also remember to use
citations throughout your work as you

introduce ideas and make claims that need support. Overview
of alternative approaches and software
can also go here or in the introduction.
Methodology (20%)
Rational for approach, i.e. why use this way of solving the
problem?
Design (often big enough to be its own section) provide
specification, description and diagrams.
Marks given for originality and difficulty of task
Implementation and results (15%)
Description of functionality and provision of evidence (testing).
Make sure you are clear about what resources you have used
and what is 'your' contribution.
Summary of test output (raw data mostly in appendices)
Can also provide screen capture video clips and snapshots
Usefulness and usability for intended audience.
Discussion – what has your work demonstrated, how has this
effected the target problem / application
area.
Discussion (20%)
Interpretation of results
Evaluation of approach
Wider implications of work
Discussion – what has your work demonstrated, how has this
effected the target problem / application
area. This will need to link to other work / applications so you
may need to reference some of the
literature and/or add to your references with some more
research.
Conclusion (10%)
Brief summary of what has been achieved, Critical appraisal of

work and future work / improvements
to be made.
Presentation (15%) - discuss with project supervisor, here are
some general suggestions.
Layout, use of English, spelling, grammar, academic style,
binding, Turnitin report.
Use page numbers, numbered headings and sub-headings,
contents list for headings and figures,
running headers with chapter title and appendices.
Code printed out to fit the page – may print quite small (8pt
fixed font) to fit lines onto the page, colour
printing can help. Make sure you have plenty of comments and
highlight your work.
2 copies (of everything) comb bound with cover sheet and
declaration.
CD / DVD with source code and executable, test results,
instructions for installation and running, whole
text of the report, attached in a proper stick-on CD container
(available from SU shop).
CS project notes 2
pdf of your poster on the CD/DVD, and an A4 'thumnail' output
in an appendix.
Include a packing list in an appendix that says what is on the
CD/DVD.
References (5%)
Harvard referencing style (use library resources to see how this
is done). Good number and quality i.e.
refereed journals - you can use Google Scholar but a better
resource is the library search which allows
you to use keywords and select 'journal articles' as a filter, so

you can go directly to a full text online
version of the paper.
Interim report (5%)(mid semester 1)
Includes project proposal, which includes a project outline with
an overview of the proposed
methodology, references to support your approach and justify
what you are doing, how you intend to
evaluate your work and an implementation plan. Also includes
PDP (CV and exit plan).
Poster (15%) (due mid semester 2)
Single A3 sheet that graphically displays what you have
undertaken and preliminary results. Get this
produced in good time, show rough draft to your supervisor.
2 Other marking considerations
Other aspects which are implicitly taken into consideration in
the marking process.
Difficulty of task
If the task is easy it has to be done very well, even then you
may find that there is not a great deal to say
about the topic. A difficult task may only need a 'proof of
concept' implementation to get good marks.
Scope of task

Has something obvious been left out? Write up may need to
mention alternative approaches and current
state of research.
Management
How much of the work was independently guided by the student
and how much had to be directed by
the supervisor. Did student show up to supervision meetings,
take notes, keep in touch by email, have a
development plan that was regularly updated.
Log book
This is not marked as such but can provide valuable support
your claims for originality and
management of the process. Recommend that you have a hard
back A4 book into which you put rough
thoughts, diagrams, diary of progress, action points arising from
supervision meetings and emails, test
results etc.
Plagiarism
You will need to run your project through Turnitin and show
that you have by this by submitting a
receipt with your project. You can re-submit your work more
than once and it is good at helping you
spot problems with referencing and quotations.
A less known problem is self plagiarism – if you include work
that you have done elsewhere or
submitted in another module for assessment you cannot get
credit for it in the project. If you need to
include the work you can reference it as you would for any

other resources that you may use from other
sources. Any issues about re-using work should be discussed
with your supervisor.
CS project notes 3
3 The project Process
Help from supervisor
You should expect to meet with your supervisor between 4 – 6
times each semester (but use of email
may reduce the need for face to face discussion). You can ask
your supervisor to look at parts of your
work.
Outline Time-line
You will already have a project plan from your initial proposal,
although this starts as a bit of a guess it
is useful to measure your progress against the deadlines and
milestones you create for your project.
That way you will notice and be able to react to significant over
or undershoot for your project. Each
project will be different but the key phases for a typical project
are outlined below. Remember to be
realistic – 8 hours of actual work a day is hard to achieve.
Allow time for other modules and
assessments, breaks, holidays, work and family commitments.

May (end of second year before you start your project) –
Start to think of topics that interest you, consider the sort of
project you want to do
software development, (more doing than thinking)
technical analysis and testing
evaluation and discussion (more thinking than doing)
comparison of techniques or application of an approach to a
particular problem.
Consider how this fits with your experience and future career.
June – September
Read around your topic area, collect references for lit review
Consider implementation choices, test out feasibility with small
development projects and 'getting
started' tutorials.
Email ideas to lecturers for feedback and suggestions
Look for project ideas from external organisations, companies,
clients and even family.
September – November
Prepare and hand in initial proposal, plan
Continue to talk with lectures to refine your plan
Allocation of supervisors (this does not rule out talking to other
staff for technical advice).
Detailed project plan agreed with supervisor
November – December
Design – methodology and system design (e.g. Bohem Spiral
model + UML diagrams)
Detailed specification and outline test plan

Complete feasibility and make sure any potential 'show
stoppers' have been investigated e.g can
component 'a' send data to component 'b'?
Finish learning and introductory tutorials for the technology,
design methods and data analysis
techniques you are going to use.
If any kind of questionnaire is going to be used for evaluation
start to research what questions, to whom
and how you are going to contact your audience.
December - February
Main time for implementation and software development or data
collection, analysis work.
January should be uninterrupted work on your project, time
spent on this has a significant effect on
what you can achieve in your project and therefore your final
degree classification.
February – March
Complete implementation, initial testing and final 'tweaks' to
software.
CS project notes 4
Start to gather usability data,
Collect, collate and analyse information from questionnaires.
March – April
Start Write up

Early on in the write up process is a good idea to create an
extended table of contents i.e. write the
headings you intend to use with a sentence or two as to what
they will contain, as well as a rough guide
to word count.
Using, testing, gathering usability data.
April – May
Hand-in is typically late April or early May, be sure to leave
enough time for write up. Two weeks is a
minimum, having longer means you can reflect more on the
results and may even have time for last
minute tweaks and experiments to fill in holes in data collection
– but only once you have the bulk of
your write up finished to a 'hand-in' level of presentation.
Send samples of your write up to your supervisor. Supervisors
can comment on a portion of your work
but the rules forbid them giving detailed feedback on the whole
work or engaging in an iterative
process of incremental improvements.
Department: Computing and Technology

Module Code: MOD002602
Level: 5
Academic Year: 2015/16
Semester: 1
2
Table of Contents
1. Key Information
...............................................................................................
...... 3
2. Introduction to the Module
..................................................................................... 3
3. Learning Outcomes and Outline Delivery
.............................................................. 4
4. Assessment
...............................................................................................

............ 5
5. Learning Resources
..............................................................................................
7
6. Report on Last Delivery of the Module
................................................................... 8
7. Links to Other Key Information
.............................................................................. 9
3
1. Key Information
Module Title: Computing Research Methods
Module Leader: Mike Hobbs
Com 307 Cambridge campus:
Extension: 2427 (direct dial 0845 196 2427)
Email: [email protected]
Every module has a Module Definition Form (MDF) which is
the officially validated record of the module.
You can access the MDF for this module in three ways via:
ule Catalogue at
www.anglia.ac.uk/modulecatalogue

www.anglia.ac.uk/modules
All modules delivered by Anglia Ruskin University at its main
campuses in the UK and at Associate
Colleges throughout the UK and overseas are governed by the
Academic Regulations. You can view
these at www.anglia.ac.uk/academicregs. An extract of the
Academic Regulations, known as the
Assessment Regulations, is available at this website too (all
new students will have received a printed
copy as part of their welcome pack).
In the unlikely event of any discrepancy between the Academic
Regulations and any other publication,
including this module guide, the Academic Regulations, as the
definitive document, take precedence
over all other publications and will be applied in all cases.
2. Introduction to the Module
The main aim of this module is to provide students with
experience of topic specific research and the analysis and
application of that work in order to carry out a computer science
based project in their final year.
The module focuses on the selection of a suitable project and
the supporting skills such as: use of relevant
sources of published information; carrying out a literature
survey on the subject of the planned project; the
writing of a literature review and project plan; and instruction
in appropriate research and analysis methods.
Students will also be instructed in assessing the risk, hazard,
ethical and legal considerations of the work to be
undertaken.
.

http://www.anglia.ac.uk/modulecatalogue
http://www.anglia.ac.uk/modules
http://www.anglia.ac.uk/academicregs
4
3. Learning Outcomes and Outline Delivery
The learning outcomes for this module are:
arch and its relevance to their
future studies.
research and experimentation.
identification and resolution, and to
develop their skill set accordingly.
techniques / methods for their resolution
in a considered manner.
Wk Lecture Seminar/Workshop Resources
1
Introduction to module and

Topic selection, project
assessment criteria.
(Monday wk 1 intro to module)
Skills audit
2
What is research? The nature
and types of research
“What is research” exercise
Idea evaluation techniques
3
Research skills using
literature, references and the
literature review
Literature review examples and
discussions.
4
Using literature, project
writing tips – document

driven development.
Using Literature for your research.
5
Qualitative and Quantitative
Research methods
Identifying appropriate research
methods
6 Time management, project
planning, milestones and
GANTT charts
Time planning - setting milestones and
monitoring progress.
Submit Initial Proposal by
Friday 11th March (20%)
7
Data collection and analysis
Analytical methods I
Data Analysis exercises I – thinking
about data.
EASTER BREAK Monday 21st to Friday March 1st April

8
Data collection and analysis
Analytical methods II
Data Analysis exercises II – statistical
tests
9
Software development
Methodologies and design
One to one Session – review initial
project proposal.
10
Critical reflection and
conclusions
One to one Session – review initial
project proposal.
11
Ethics and the project ethical
approval process.

Ethical and responsible project practice.
Complete online Ethics
training, include certificate
in final report. (5%)
12
Starting your project, what
to do over the Summer.
Finish online Ethics Training
Final Hand in Wednesday
11th May
5
4. Assessment
Assessment Information Sheet(s):
DESCRIPTIVE
TITLE
Initial Report Assessment

Element
010
DETAILS ABOUT
THE
ASSESSMENT
Title, aims, outputs and evaluation methods and outline research
provide
evidence to support the project and enable the more detailed
final project
proposal to be written with confidence.
Learning Outcomes 1 - 4 Weighting 20 % Marking
Approach
Fine Grade
WHAT IS BEING
SUBMITTED
Report – 1,000 words Qualifying
Mark
30%
SUBMISSION Date: 11/03/16 Time: 14:00 Location Turnitin
MARKER(S): Mike Hobbs
MODERATOR(S): E. Brown
FEEDBACK By Date: 25/03/16 Where to get your
feedback

Turnitin
DESCRIPTIVE
TITLE
Project Proposal Assessment
Element
010
DETAILS ABOUT
THE
ASSESSMENT
Submit a description, literature review and plan of action for
your final year
project. Include ethical training certificate and online data
analysis exercise
results as appendices.
Learning Outcomes 1 - 4 Weighting 80 % Marking
Approach
Fine Grade
WHAT IS BEING
SUBMITTED
Report and project plan – 2,000 words Qualifying
Mark
30%

SUBMISSION Date: 11/05/16 Time: 14:00 Location Turnitin
MARKER(S): Mike Hobbs
MODERATOR(S): E. Brown
FEEDBACK By Date: 16/06/16 Where to get your
feedback
Turnitin
Initial report (20%) Friday 13th March, via Turnitin class
exercises (1,000 words equivalent)
Key parts of this will be covered in the class exercises so by the
time you have to submit you will have practiced
and demonstrated the skills needed and received feedback in the
class.
method for evaluation (5%)
ckground with references to
the context of the project and
the techniques / theoretical underpinnings of the proposed
approach. (5%)
– identifying research that will provide evidence
that your approach is
achievable and to enable you to complete the more
comprehensive Project Proposal.
(5%)

6
Final Project Proposal (80% of module) 2000 words equivalent.
Hand In Date: Wednesday 13th of May
Mark scheme –
Title and Aims [5 marks]
Previous work / Background / literature review [20 marks]
Methodology / process and data analysis techniques [20 marks]
Design / requirements / technology [10 marks]
Time table / project plan [10 marks]
Ethics Training completion certificate [5 marks]
Presentation, use of references [10 marks]
(Please check out the detailed mark-scheme with generic
feedback available on the VLE)
As well as the content this will be marked on the presentation,
good use of English, proper use of Harvard
references, use of headings, sub-headings, lists and diagrams.
4.1 Submission
All coursework assignments and other forms of assessment must
be submitted by the published
deadline which is detailed above. It is your responsibility to
know when work is due to be submitted –

ignorance of the deadline date will not be accepted as a reason
for late or non-submission.
All student work which contributes to the eventual outcome of
the module (ie: if it determines whether
you will pass or fail the module and counts towards the mark
you achieve for the module) is submitted
via Turnigin/Grademark for the Cambridge Delivery and the
local equivalent of the iCentre for other
deliveries using the formal submission sheet. Academic staff
CANNOT accept this work directly from
you.
Any late work (submitted in person, by post or by
Turnigin/Grademark ), will NOT be accepted and a
mark of zero will be awarded for the assessment task in
question.
You are requested to keep a copy of your work.
Submission process via Turnitin/Grademark®
You will have received an email to your STUDENT email
account, informing you that you’ve enrolled in a
Turnitin/Grademark® class for this module. When you log into
Turnitin/Grademark®, you will see
information about the module, such as the start date, due date
and time (GMT) for your assignment, and
the latest date on which your results will be made available
(post date), will be given. Once the post date
has passed, you will be able to view your feedback and grade.
PLEASE NOTE:
You will only have one opportunity to submit to this
Turnitin/Grademark® class so make sure that what
you submit is the work you want to be marked. If you submit a

draft it cannot be removed and will be
marked. If you submit to the wrong class, or the faculty
Turnitin® site that you use for generating an
originality report, it will be treated as a non-submission and
recorded as a fail. Neither of these are
subject to mitigation or academic appeal.
Please submit before the due date and time given. This is given
as Greenwich Mean Time (GMT)
adjusted for daylight savings, so please work out, in advance,
your local time difference. The submission
time is the point at which the document finishes uploading, not
when it starts. There is sometimes
substantial time needed to submit work in this way, depending
on the use being made of the system, so
it is not recommended to leave electronic submission to the last
minute.
More detailed information on using Turnitin/Grademark® is
available on the VLE, at
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Home.asp
x.
Feedback on your work
You are entitled to feedback on your performance for all your
assessed work. For all assessment tasks
which are not examinations, this is provided by a member of
academic staff completing the assignment
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Home.asp
x
7

coversheet on which your mark and feedback will relate to the
achievement of the module’s intended
learning outcomes and the assessment criteria you were given
for the task when it was first issued. This
feedback may be completed electronically and sent directly to
your Anglia Ruskin e-mail account.
Anglia Ruskin is committed to providing you with feedback on
all assessed work within 20 working days
of the submission deadline or the date of an examination. This
is extended to 30 days for feedback for a
Major Project module (please note that working days excludes
those days when Anglia Ruskin University
is officially closed; e.g.: between Christmas and New Year).
On occasion, you will receive feedback and marks for pieces of
work that you completed in the earlier
stages of the module. We provide you with this feedback as
part of the learning experience and to help
you prepare for other assessment tasks that you have still to
complete. It is important to note that, in
these cases, the marks for these pieces of work are unconfirmed.
This means that, potentially,
marks can change, in either direction!
Marks for modules and individual pieces of work become
confirmed on the Dates for the Official
Publication of Results, which can be checked at
www.anglia.ac.uk/results.
5. Learning Resources
[email protected] for this module reading materials will be
found at :
http://readinglists.anglia.ac.uk/modules/mod002602

Resources Notes
Key text
Dawson, C.W., 2009, Projects in Computing and Information
Systems – A Students Guide Second Edition, Addison
Wesley.
Book available in the library as is the first
edition which is a suitable alternative.
Books
Creswell. J.W., 2009, Research design: qualitative,
quantitative and mixed method approaches, 3rd Ed Sage.
Walliman, N., 2011, Your Research Project, designing and
planning your work. 3rd Edition, Sage.
Weaver, P.L., 2004 Success in your project: a guide to
student development projects, Financial Times Prentice Hall.
Johnston, A.,K., 2003 Hacker's guide to project
management, 2nd Ed Oxford Utterworth-Heinemann
One of many good books relating the actual
methods used in research for data analysis.
Available in the library, 2nd Edition also suitable.

Book available in the library, provides a
readable and interesting account of the project
process.
Provides aspects on the software development
process.
A readable overview of the main project
management / software methodology
techniques and how they should be applied.
Faculty library [email protected]
Link to the University Library catalogue and Digital Library
http://libweb.anglia.ac.uk/
Link to Harvard Referencing guide
http://libweb.anglia.ac.uk/referencing/harvard.htm
http://www.anglia.ac.uk/results
mailto:[email protected]
http://readinglists.anglia.ac.uk/modules/mod002602
https://webmail.anglia.ac.uk/owa/redir.aspx?C=x4giGQeT-
kKjYqEJMBK1JjuayRyTAs8IRnA71fQiSijBLG8rnExvb6C6Zs_
HOuXrsplNJ7SDHtc.&URL=mailto%[email protected]
http://libweb.anglia.ac.uk/
http://libweb.anglia.ac.uk/referencing/harvard.htm

8
6. Report on Last Delivery of the Module
MODULE REPORT FORM
This form should be completed by module tutors (where there is
more than one delivery) and forwarded to Module Leaders who
compiles the results on to one form for use at the Programme
Committee and other methods of disseminating feedback to
students.
Module Code and Title: MOD002602 Computing Research
Methodologies
Anglia Ruskin Department: CAT
Location(s) and Enrolment Numbers C-1 94, WA1 – 12, PE1
19, HEL 5
Academic Year: 2014/15 Semester/Trimester: SEM 2
Module Leader: Mike Hobbs
Student Achievement Provide a brief overview of student
achievement on the module as evidenced by the range of marks
awarded. A
detailed breakdown of marks will be available at the
Departmental Assessment Panel.
From the main delivery at Cambridge:
>=70 3 students
60 – 69 18 students

50 -59 19 students
40 – 49 22 students
< 40 11 students
No submission from 4 students
The average mark is OK but a little low since some students
failed to implement advice given in the initial report
when it came to the main assessment.
Feedback from Students Briefly summarise student responses,
including any written comments
See attached sheet for student feedback.
The MEQ analysis improved since the last presentation but is
still not where we would like it. It is well known that
Research methods is delivered in many subjects at many
universities and is often not regarded as essential by students,
which was reflected in feedback.
Module Leader/Tutor’s Reflection on Delivery of the Module,
including Response to Feedback from Students
(including resources if appropriate)
A key problem from the outset was student engagement with a
module that is perceived as peripheral to their studies so
every effort will be made to link the work done in the module
with practical project work to support their final project.
Developments during the current year or planned for next year
(if appropriate)
The number of small assessments will be reduced and phased in
slightly later in the module. We will try to focus more on
what makes a good project rather than the more general research

skills.
External Examiner’s Comments State whether the external
examiner agreed the marks and/or commented on the module
9
7. Links to Other Key Information
Assessment Offences: As an academic community, we recognise
that the principles of truth, honesty
and mutual respect are central to the pursuit of knowledge.
Behaviour that undermines those principles
weakens the community, both individually and collectively, and
diminishes our values. There is more
information on these principles, and the types of Assessment
Offences, available here. Penalties for
poor academic practice can be severe so ensure you are aware of
what is expected and how to
reference correctly.
In cases where the Module Leader suspects that the assignment
submitted is not the work of the
student, and may have been produced by another person, the
Module Leader informs the Director of
Studies of the suspicion of an assessment offence. In the
process of considering the academic integrity
of the work, the Director of Studies may invite the student to a

meeting, with the Module Leader, to
answer questions about the assignment.
There is a Guide to Good Academic Practice available.
Attendance Information: Attending all your classes is very
important and one of the best ways to help
you succeed in this module. Details on Attendance
Requirements.
Assessments and TurnitinUK: TurnitinUK is used for submitting
the majority of your assessments, it is
important that you read the information on preparing your
assignment.
Information on submitting your assignment must be read and
guidelines adhered to, please ensure you
read:
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Quick-
Start.aspx
The direct link to TurnitinUK is: http://www.turnitinuk.com
Examinations: Examinations are held in January
(semester/trimester 1), May (semester/trimester 2)
and in August (trimester 3). All examinations are scheduled by
the Examinations Unit, the dates and
locations will be posted on the following website:
http://web.anglia.ac.uk/anet/students/exams/
External Examiners: An up-to-date list of external examiners is
available to students and staff at
http://www.anglia.ac.uk/eeinfo The external examiner for this
module is in the Computing and
Technology Departmental Assessment Panel. These are
academic examiners from other institutions

who independently approve and confirm the quality and
standard of our modules and assessments.
Feedback in TurnitinUK: Link to more details on the viewing
feedback is here:
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Feedback.
aspx
How is My Work Marked and Flowchart of Anglia Ruskin’s
Marking Process: After you have
handed your work in or you have completed an examination,
Anglia Ruskin undertakes a series of
activities to assure that our marking processes are comparable
with those employed at other universities
in the UK and that your work has been marked fairly, honestly
and consistently. Information about this
process is available here.
Module Evaluation: During the second half of the delivery of
this module, you will be asked to complete
a module evaluation questionnaire to help us obtain your views
on all aspects of the module, more about
this process is included here.
Reading Lists: These are now all available online:
http://readinglists.anglia.ac.uk, or follow the direct
link in this guide or on the VLE.
Re-assessments: Re-assessment dates will be stated on e-vision,
you can check the specific date your
re-assessment assignment is due in on: http://e-
vision.anglia.ac.uk or alternatively, if it is an
examination, these are scheduled by the Examinations Unit, the
dates and locations will be posted on
the following website:

University Generic Assessment Criteria: The level for this
module is given on the front page of this
guide. Information on the criteria that the university uses to
mark your work at this level can be found
here [word document].
http://www.anglia.ac.uk/modguide4.aspx
http://anglia.libguides.com/plagiarism
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Preparing
%20my%20Assignment.aspx
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Quick-
Start.aspx
http://www.turnitinuk.com/
http://www.anglia.ac.uk/eeinfo
https://vle.anglia.ac.uk/sites/LTA/Grademark/Content/Feedback.
aspx
http://readinglists.anglia.ac.uk/
http://e-vision.anglia.ac.uk/
http://www.anglia.ac.uk/criteria
http://www.anglia.ac.uk/criteria
SID:
Computing Research Methodologies Initial Project Proposal
Check List
(This is a draft proposal and can be changed– we will be

looking for reasonable suggestions rather than a cast iron
project specification - feedback from this and the one-to one
session should improve your project proposal)
Title (around 5 to 9 words but can be a little longer or shorter)
Aims (what do you hope to achieve in broad terms)
Research (describe the key papers and website you have found
to support your project using Harvard citations with
bibliographic details in the reference section)material you are
using but cite the references use references)
Methodology (the steps you are going to carry out and an
indication of the kind of methodology this approach belongs to
– quite often different parts will fit with different
methodologies)
Evaluation (how will you test, compare and provide critical
analysis of your work?)
Deadlines (Split into the main tasks with elapsed time and dates
or semester teaching weeks)
Resources (software / hardware)
Benefits / Rationale / Why? (what might be novel, interesting,
different or helpful)
Risk Factors (what might go wrong or not happen to threaten
your project?)
WORD COUNT:
References (Harvard format bibliographic details)
Page no: 2
Computing Research Methodologies Project Initial Proposal
Check List
SID:

Date
Title
The Chaotic Laboratory – Can a virtual world inform real world
learning?
Aims
To create a facility in Second Life to test the idea that
interactive simulation can be used to improve health and safety
awareness for trainee science teachers.
Research
Articles supporting the concept of using Virtual worlds to teach
skills in the real world:
Bainbridge, W.S., 2007. The Scientific Research Potential of
Virtual Worlds. Science, Vol. 317, No. 5837, pp. 472-476.
Billinghurst, M. and Dünser, A., 2012. Augmented Reality in
the Classroom. Computer, Vol. 45, No. 7, pp. 56-63.
Borrows, P., 2006. Health and safety in science education. In
Wood-Robinson, V., (Ed.) ASE Guide to Secondary Science
Education. Hatfield: Association for Science Education.
Open University, 2008. Researching Learning in Virtual
Environments - ReLIVE08, [Online] Available at:
http://www.open.ac.uk/relive08/ [Accessed 1 July 2012].
An Existing example:
London Metropolitan University, Clipper Logistics Group Ltd,
The Chartered Institute Transport and Logistics (UK) and
Anglia Ruskin University, 2011. The 3D Warehouse. [Online]
Available at:
http://learning.londonmet.ac.uk/epacks/clipper/website/
[Accessed 27 June 2012].
Main development environment resource:

Linden, 2012, Second Life software, Linden Research Inc.,
[Online] Available at: http://lindenlabs.com [Accessed 26 June
2012].
Methodology
Build a virtual laboratory to simulate real world incidents.
(Construction)
Record and control interaction from participants.
(Observational)
Evaluate with testers and questionnaire. (Hermeneutic /
Empirical analysis)
Evaluation
Personal view from education dept expert. (phenomenological)
Heuristic usability test. (Empirical)
Testing with cohort of trainee science teachers and
questionnaire. (Quantitative data for qualitative research)
Deadlines
(deliverable deadline, based on semesters)
Requirements capture from expert from education dept. (wk 1)
Outline design and story board for key training events (wk 4)
Implementation of laboratory in second life (wk10)
Implementation of HTTP web site (sem 2 wk 2)
Initial Testing (sem 2 wk 4), final testing (sem2 wk 6),

First draft of write up (sem2 wk9)
Resources
Second Life account, MySQL / PHP web server.
Open Sim server. Survey Monkey questionnaire account.
Benefits / Rationale /
Improve / supplement teacher training without increasing the
demands on limited facilities.
Risk Factors
Ethics approval for testing, getting sufficient test subjects
willing to participate, time and skills to build resources, rely on
external hosting of test system (i.e. Second Life may go offline
or change radically). Data protection issues for subject data (SL
is in USA and needs to know who owns which avatar).

CS project notes 1 Notes for Final Project Dissertation .docx

Recommended

Recommended

More Related Content

Similar to CS project notes 1 Notes for Final Project Dissertation .docx

Similar to CS project notes 1 Notes for Final Project Dissertation .docx (20)

More from annettsparrow

More from annettsparrow (20)

Recently uploaded

Recently uploaded (20)

CS project notes 1 Notes for Final Project Dissertation .docx