|
CC301 – Final Year Project: 2006-2007
Assessment: Final Report and Presentation/Demonstration
Student:
Degree Scheme:
Project Title:
Supervisor / Assessor:
On this form you are asked to provide assessments of various aspects of the final report and the
指导留学生商业策划书presentation/demonstration. When allocating marks please
x consider the bullet points under each heading carefully
x consult the assessment guidelines at the end of this form
x add comments in each section to explain the mark you have awarded
Please note that the expected range of marks under each heading is 30% - 80% of the available marks.
Marks may be awarded outside this range where you consider it to be appropriate, but such marks must be
explained and justified in your comments.
The project co-ordinators will review all marks to ensure consistency.
The mark awarded on this mark sheet counts for 85% of the entire mark for CC301.
TOTAL MARK / 100
COMMENTS
Major Strengths
Major Weaknesses
Other
Signature: Date:
2
1. Presentation quality of the report
Is the report well structured and easily navigable?
Does it contain headed sub-sections, TOC, page numbering, appendices, etc?
Is the report well presented and easily read?
Is effective use made of document preparation tools? Is the standard of writing good?
Comments:
Please provide further explanation if your mark
is outside the expected range of marks:
3.0 – 8.0
Threshold*
Lower Second
Upper Second
First Class
=
=
=
=
4.0 +
5.0 +
6.0 +
7.0 +
/ 10
2. Content of the report
Does the report provide a clear account of the project objectives?
Does the report provide a clear description of the work undertaken to meet the objectives?
Does the report provide a clear evaluation of the extent to which the objectives were met?
How challenging are the objectives stated in this report? (Note: not those in the original proposal.)
What level of achievement is indicated by the work presented in the report?
Does the evaluation include any suggestions for improvements and/or extensions?
What level of computer science expertise is demonstrated in the report?
What level of scholarship is demonstrated in the report?
Comments:
Please provide further explanation if your mark
is outside the expected range of marks:
10.5 – 28.0
Threshold*
Lower Second
Upper Second
First Class
=
=
=
=
14.0 +
17.5 +
21.0 +
24.5 +
/ 35
* Please refer to the attached assessment guidelines for notes about threshold achievement
3#p#分页标题#e#
3. Implementation (submitted code)
Are the programming tools/languages used appropriate to the task?
Has effective use been made of the available features of the programming tools/languages?
How much self-authored code has been presented?
What level of programming ability is demonstrated by the submitted implementation?
Comments:
Please provide further explanation if your mark
is outside the expected range of marks:
4.5 – 12.0
Threshold*
Lower Second
Upper Second
First Class
=
=
=
=
6.0 +
7.5 +
9.0 +
10.5 +
/ 15
4. Project Management
Does the report contain an adequate description of the management of the project?
Has the student described whether original objectives and/or work plan have been adhered to?
Has the student drawn any conclusions about his/her management of the project?
Do you consider that this project has been well managed?
Comments:
Please provide further explanation if your mark
is outside the expected range of marks:
3.0 – 8.0
Threshold*
Lower Second
Upper Second
First Class
=
=
=
=
4.0 +
5.0 +
6.0 +
7.0 +
/ 10
Sub-Total at Report Stage / 70
* Please refer to the attached assessment guidelines for notes about threshold achievement
4
5. The Demonstrated System
Was the system robust? Did it produce correct results?
(Where relevant) was the interface of a professional standard?
(Where relevant) did the system work correctly over the network?
To what extent did the system’s capability confirm the achievements claimed in the report?
Comments:
Please provide further explanation if your mark
is outside the expected range of marks:
4.5 – 12.0
Threshold*
Lower Second
Upper Second
First Class
=
=
=
=
6.0 +
7.5 +
9.0 +
10.5 +
/ 15
6. Oral Presentation and Questions
Was the presentation delivered clearly and within the allocated time?
Was effective use made of prepared materials (e.g. OHP, Powerpoint, etc)?
Was there an appropriate balance between overview, technical description and conclusions?
Were the project objectives made clear?
Was the work undertaken described at an appropriate level of detail?
Was there a proper evaluation of the management and outcomes of the project?
When questioned, did the student demonstrate an understanding of the relevant technical issues?
Was the student able to justify his/her design/implementation choices?
Was the student able to explain any unresolved problems?
Was the student able to make a realistic assessment of his/her management of the project?#p#分页标题#e#
Comments:
Please provide further explanation if your mark
is outside the expected range of marks:
4.5 – 12.0
Threshold*
Lower Second
Upper Second
First Class
=
=
=
=
6.0 +
7.5 +
9.0 +
10.5 +
/ 15
TOTAL MARK / 100
* Please refer to the attached assessment guidelines for notes about threshold achievement
5
ASSESSMENT GUIDELINES
1. Presentation quality of the report [10%]
Threshold achievement (4 out of 10) is established by a well structured and easily navigable report
written in an appropriate technical style. Additional marks are awarded for making effective use of
document preparation tools to produce clear text and informative tables, charts, diagrams, etc.
2. Content of the report [35%]
An assessment of the technical content of the report.
指导留学生商业策划书Threshold achievement (14 out of 35) is established by a clear account of objectives, work undertaken
and outcomes, independently of the level of difficulty. Additional marks are then awarded on the basis of
difficulty, reported achievement, evaluation of outcomes (e.g. test results), computer science expertise
and scholarship. Supervisors should note that judgements about the difficulty of the project, and the
achievement of the student, should be based on the objectives reported here, not in the original proposal.
3. Implementation (submitted code) [15%]
An assessment of the implementation submitted with the report.
Threshold achievement (6 out of 15) is established by the effective use of an appropriate programming
tool or language. Note that this permits the use of high level tools (e.g. wizards, web page editors) if they
provide an adequate solution method. Additional marks are awarded for the size and complexity of the
implementation, and the level of programming expertise demonstrated in its construction. In cases where
large amounts of code have been produced unnecessarily (e.g. because a high level tool could have
provided an equally good solution), the student might gain marks for expertise, but lose marks for a poor
choice of implementation method.
4. Project Management [10%]
An assessment of the student’s success in managing the project.
Threshold achievement (4 out of 10) is established by a clear account of planning and monitoring
activities. Additional marks are awarded for evidence of monitoring activity (e.g. a diary), and
explanations of adjustments to work plan and targets. Note that strict adherence to the original work plan
is not necessarily required, although it might be seen as evidence of good initial planning. Decisions to
modify or remove over-ambitious objectives in order to present a completed system could be regarded as#p#分页标题#e#
good management. Credit should be given for the student’s ability to reflect on these matters, as well as
the quality of the management itself.
5. Demonstrated System [15%]
An assessment of the behaviour of the implemented system.
Threshold achievement (6 out of 15) is established by the demonstration of a robust system that displays
a basic level of functionality. Additional marks based on the system’s capability will depend on the kind
of system being assessed (e.g. correct results/output, network capability, user interface, etc.). In all cases,
assessors should check the system’s capability against the achievements claimed in the report.
6. Oral Presentation and Questions [15%]
An assessment of the oral presentation and the ability of the student to answer questions
Threshold achievement (6 out of 15) is established by a properly prepared presentation that incorporates
a clear account of the problem and its solution, delivered within the allocated time. Additional marks are
awarded for a succinct account of technical issues, a full assessment of the outcomes, and some
reflection about the way the project was managed. Credit should be given for the ability to justify design
and implementation choices, discuss alternative approaches, and provide answers about the wider
context, including the management of the project.CC301 Final Year Project
Course Supervisor: Martin Waite
Room 5B.534 Tel 2254
Email waitm@essex.ac.uk
Lecture 4 : Outline Report
and
Final Report
CC301 Final Year Project
x initial proposal 9
x project plan and progress report 9
x report outline
11.30 am Wednesday week 21 21st Feb
x final report
1.30 pm Thursday week 25
x presentation
9.30 a.m. Wednesday week 30*
(Undergraduate Students Handbook pages 115 - 118)
(85%)CC301 Final Year Project
Dawson, pages 110 – 141
x Writing and Structuring Reports
x Initial Considerations
x Approaches to writing
x The Order of Writing
x Structure
x Style
x Writing Abstracts
x Data Representation
x Referencing Material and Plagiarism
x Documenting Software
This
lectureWriting and Structuring Reports
Initial Considerations
x Who is going to read it?
x your supervisor – has knowledge of your project
x 2nd assessor – has some knowledge of the area
o discuss with your supervisor the level of detail required
and what background knowledge can be assumed
x How long should it be?
x as long as it needs to be
x repetition and “padding” will lose marks
o 7,000 to 10,000 words is only a guideWriting and Structuring Reports
Approaches to writing
x Top Down
o identify structure first
o chapters, headings, sub-headings
o then start writing the text#p#分页标题#e#
x Evolutionary
o ongoing drafting
o more detail as project progresses
o usually a combination of both,
but the structured approach should dominate
Week 21
Report OutlineWeek 21 Report Outline
1. Design Overall Structure
produce a WBS style diagram or similar
2. Make Table of Contents Page
convert diagram into structured TOC
take a copy
3. Expand the copy - for each section say
approximately how long it will be
what it is going to contain
current state of completion
1 Introduction
2 Background Context
2.1
2.1.1
2.1.2
etc.
2.1.1
- approx 200 words
- overview of problem
- figure 2.3 showing …
- 70% completeWeek 21 Report Outline
Then hand in result of 2 and 3 for the Week 21 submission
Your supervisor might also want to see drafts – if so hand
them to him/her directly, not to the General Office
Structured Table of Contents
Enables your supervisor to
get an immediate overview
of your intended report.
More convenient form for
restructuring than 1000s of
words of text.
Expanded Form
Enables your supervisor to
advise you about structure,
content, emphasis, etc.
Maintain this as a document
to monitor/discuss progress
on writing your final reportWriting and Structuring Reports
The Order of Writing
identify structure
identify presentation style
draft the introduction
write the main body
conclusions
complete the introduction
write the abstract
references and appendices
finalise table of contents
proofread, check and correct
proofread, check and correct again! …. and again !!
Don’t forget to include
a section on Project
ManagementWriting and Structuring Reports
The Order of Writing
identify structure
x week 21 submission may need revisiting
x convention for section numbering, etc.
x convention for labeling tables and diagrams
identify presentation style
x page size, font style, spacing, etc.
x no Departmental requirement – ask your supervisor
x 11 point Times Roman, 1.5 spacing
is usually recommended for main text
Document structure
and presentation are
important – and they
are assessed !
Figure C.N
Chapter no figure no.Writing and Structuring Reports
The Order of Writing
draft the introduction
x maybe, maybe not
write the main body
x with the structure in place, sections don’t have to be
written in the order in which they will appear
x keep referring to your outline to make sure that the
content of each section remains focused, and you avoid
a) repetition b) omission
x keep updating your outline to monitor your progressWriting and Structuring Reports#p#分页标题#e#
The Order of Writing
conclusions
x one of the most important aspects of the report
- and one that is often sadly lacking in depth
x you should include
x an evaluation of the outcomes of the project
(measured against the original objectives)
x possible extensions to the project
x an evaluation of the way you managed the project
(maybe as a separate section)Writing and Structuring Reports
The Order of Writing
complete the introduction
x you don’t actually know what you’re
introducing until you’ve written it
write the abstract
x this an overview of the project – not the report
x single paragraph < 1 side of A4
x motivate the project, and present main conclusion
You can give an
overview of the
chapters in your
introductionWriting and Structuring Reports
The Order of Writing
references – two main approaches
Numbered “Harvard”
Cited … blah, blah [1], blah
blah blah [1,2] … blah [Smith 99], ….
Listed numerically alphabetically
from within
your text
In your
reference
section Difficult to
maintain when
adding/deleting
references
Preferred form.
Other conventions
exist – check with
your supervisorWriting and Structuring Reports
The Order of Writing
references (continued)
x strictly speaking
o the reference section contains those articles, etc.
that are cited from within the text
o the bibliography contains those articles, etc.
that have been consulted as background reading
x consult texts and/or check with your supervisor for
conventions regarding journals, conference, textbooks, etc.
x web references are volatile - always give a date
x make sure your use of a convention is consistent
According to
Dawson
Several
examples
shown in
DawsonWriting and Structuring Reports
The Order of Writing
.. and appendices
x large tables (e.g. data dictionaries, detailed schema)
x sets of user interaction diagrams
x user documentation
x other supporting documentation
Note :
x hard copy source code listings are not required
x source code should be included on the CDs
x do not include automatically generated code unless it’s absolutely
necessary – if it is, make sure you acknowledge its sourceWriting and Structuring Reports
The Order of Writing
finalise table of contents
x will have been done progressively if you have made
effective use of the report outline
proofread, check and correct
proofread, check and correct again! … and again !!
x use a spell checker – but don’ t rely on it too much
x get someone else to read your reportWriting and Structuring Reports#p#分页标题#e#
Structure
Title Page
Abstract
Acknowledgements
Table of Contents
(List of Figures and Tables)
The Actual Report
References
Appendices
(Glossary of Terms)
Include the
Appendices
Optional,
but useful
The written
chapters
Give them a
letter A, B, etc
and a name
Not much use
without page
numbers
Acronyms,
technical termsWriting and Structuring Reports
Style
more structure - beginning, middle and end
x the report has the overall structure
introduction main body conclusion
x chapters should also have a similar structure
overview main body summary
(but be careful not to get too repetitive)Writing and Structuring Reports
Style
writing
x marks are specifically allocated for standard of writing
x you must use a style that is appropriate for a technical report
x avoid
x personal pronouns (I, we, etc) – use the passive tense
x “chatty” or journalistic styles
x abbreviations (e.g. use “is not” instead of “isn’ t”)
x jargon and slang
x unnecessarily long and complicated sentences
x unnecessarily long and complicated words
The standard of writing will also influence the
指导留学生商业策划书assessor’ s overall impression of your report
K eep
I t
S imple
S tupid
|
