Aims and Learning Outcomes

The project modules are designed to provide an opportunity for the expression of individual energy and ability in completing a significant item of work related to the aims and objectives of the course.

For General Computing Projects and Software Engineering Projects, this must include the creation of a significant computing product and may also involve practical investigation of a research question.  For Investigative Projects, it will focus on the practical investigation of a research question, using skills and knowledge relevant to the student's programme, and may also involve the creation of relevant deliverables.

On completion of their project module, students should be able to:

1. Construct a problem statement working from unstructured ideas.

2. Plan, schedule, monitor and control the conduct of a small project.

3. Identify and critically review relevant literature.

4. Apply appropriate skills, methods and tools to the specification and execution of a significant piece of practical computing research or product development relevant to the student's programme.

5. Critically evaluate their own work

6. Communicate the findings of a small project by verbal presentation / demonstration and written report.

ASSESSMENT AND DELIVERABLES

Deliverables

The deliverables required for project marking are:

• A project report (including relevant product documentation or other deliverables as appendices),
• A product (for Software Engineering and General projects only), or
• Agreed deliverables to support and illustrate investigative work (Investigative project only)
• A viva.

The contribution of these to the module mark is shown in the marking scheme for each type of project.  Full details of the requirements for the project report can be found in the marking schemes and further advice is given in the sections of this handbook that deal with the report.

The standard formatively assessed and ethics deliverables are:

A Project Initiation Document,

A Terms of Reference document,

An ethics form

• A risk assessment form, if health and safety risks have been identified
• A draft of the analysis part of the project report and associated deliverables (e.g. a requirements specification).
• An evidence folder containing your logbook, all copies of data etc.

These are required to provide formative feedback, for effective project management, and to ensure that ethical and safety guidelines are followed.

After the TOR Review and before the due date, hand in copies of the following to the submission desk:

• Your finalised, signed, ethics form. This should contain any changes requested at your TOR review and should have been signed to show that it has been reviewed and agreed.
• Final version of risk assessment form - if your supervisor said that you needed this. Again, this should be the version after the review and any requested changes. (Make sure you keep copies for yourself and your supervisor.)

If handing in both the above, please don't staple the two documents together as they have to be separated by the office. 

Main Report Submission

When submitting the project report and any product, you should submit the following:

-Two bound copies of your project report, in the standard covers available from the submissions office.

-Two copies of a CD containing (in separate, clearly labelled directories):

• An electronic copy of your report
• The product, or agreed deliverables from Investigative projects.
• Any supporting data or other evidence not included in the printed report.

The above are handed in at the submission desk.  You must also submit

An electronic copy of your report (including appendices)

Please write whether this is a General Computing Project, Investigative Project or Software Engineering Project on the report cover, under the title.

One copy of the CD should be firmly and safely secured (for example in a wallet) inside the back cover of each copy of the report.

For a software product or software which is an investigative project deliverable, your CD should contain the source code, plus any relevant data files and other product deliverables, together with anything else that you needed to give your demonstration of the product; excluding system software such as operating systems, compilers, web servers, etc.  The product directory should include a "readme.txt" file that specifies the environment in which your product is meant to run and any other relevant information. Include in the "readme" file instructions on how to load and start your product.  If you can create an executable version of your product that can be set up to automatically self-load and run from its directory, you should do so.

Attachment:- Assignment.rar