University of Greenwich COMP1551 Application & Web Development Logbook

This document presents a solution for the COMP1551 Application & Web Development Logbook assignment, a 30% contribution to the course grade at the University of Greenwich. The assignment requires students to complete and document exercises from four labs: Statements and Methods, Objects and Classes, Sessions and Collections, and Inheritance. The deliverables include screenshots of running applications, the code written for each application (excluding generated code), a list of encountered bugs, and a comprehensive report. The solution provides detailed implementations and answers to the lab exercises, offering a complete response to the assignment requirements, which include providing all the code, screenshots and report as required by the marking criteria. The document follows the specified submission guidelines, including the PDF format and electronic submission requirements, and addresses the grading criteria which are based on documentation, design, implementation, and understanding of concepts.

Course: COMP1551 Application & Web
Development
Contribution: 30% of course
139: Application & Web Development - Logbook
- Term 1 - MAC
PDF file required
Greenwich Course Leader: Dr Elena Irena Popa Due date: 10th November 2016
This coursework should take an average student who is up-to-date with tutorial work
approximately 10 hours
Learning Outcomes:
A,B
Plagiarism is presenting somebody else’s work as your own. It
includes: copying information directly from the Web or books
without referencing the material; submitting joint coursework as an
individual effort; copying another student’s coursework; stealing or
buying coursework from someone else and submitting it as your
own work. Suspected plagiarism will be investigated and if found
to have occurred will be dealt with according to the procedures set
down by the University.
All material copied or amended from any source (e.g. internet,
books) must be referenced correctly according to the
reference style you are using.
Your work will be submitted for electronic plagiarism
checking. Any attempt to bypass our plagiarism detection
systems will be treated as a severe Assessment Offence.
Coursework Submission Requirements
 An electronic copy of your work for this coursework should be fully
uploaded by midnight (local time) on the Deadline Date.
 The last version you upload will be the one that is marked.
 For this coursework you must submit a single Acrobat PDF
document. In general, any text in the document must not be an image
(i.e. must not be scanned) and would normally be generated from
other documents (e.g. MS Office using "Save As .. PDF").
 There are limits on the file size. The current limits are displayed on
the coursework submission page on the Intranet
 Make sure that any files you upload are virus-free and not protected
by a password or corrupted otherwise they will be treated as null
submissions.
 Comments on your work will be available from the Coursework page
on the Intranet. The grade will be made available in the portal.

 You must NOT submit a paper copy of this coursework.
 All coursework must be submitted as above
The University website has details of the current Coursework Regulations,
including details of penalties for late submission, procedures for
Extenuating Circumstances, and penalties for Assessment Offences.
See http://www2.gre.ac.uk/current-students/regs for details.
Specification
This is an individual coursework
You are required to complete and upload the following pieces of work from your labs:
Element Description
1 Lab: Statements and Methods
 Part C – play with methods
2 Lab : Objects and Classes.
 Exercise 2
 Exercise 3
3 Lab : Sessions and Collections
 Part A Exercise 1, 2
 Part B
 Part C
4 Lab : Inheritance
 Part B Exercise 1
 Part B Exercise 2

Deliverables:
A report which should include a list with all required applications from the Labs specified.
You are required to:
 Provide screenshots of all the applications running.
 Provide all the code that you wrote, not the generated code (such as designer partial
classes) for each application.
 Provide a list of bugs/problems encountered

Grading Criteria
The marks are awarded as follows:
 70+ well documented work that follows the requirements both in design and implementation
to a high standard and which shows detailed critical understanding of relevant concepts with
an excellent report and demonstration.
 55%+ work that follows the requirements both in design and implementation reasonably well
and which shows good understanding of relevant concepts with a good report and
demonstration.
 40%+ work displaying minimal functionality, and generally correct use of concepts with a
reasonable report and demonstration.
 30%+ work displaying little or incorrect functionality, and a simplistic or partially incorrect
use of concepts with a poor report and/or demonstration.
 <30% work displaying no functionality, and a simplistic and incorrect use of concepts with a
very poor report and demonstration.
Marking breakdown
Element Description Marks
1 Lab: Statements and Methods
 Part C – play with methods
20 marks
2 Lab : Objects and Classes.
 Exercise 2
 Exercise 3
20 marks of which
 10 marks
 10 marks
3 Lab : Sessions and Collections
 Part A Exercise 1, 2
 Part B
 Part C
30 marks of which
 10 marks
 10 marks
 10 marks
4 Lab : Inheritance
 Part B Exercise 1
 Part B Exercise 2
20 marks of which
 10 marks
 10 marks
5 Report 10 marks