COMP390/3/4/5 Final Year Project Design

20
Final Year Project COMP39X COMP390/3/4/5 Final Year Project Design Darek Kowalski http://www.csc.liv.ac.uk/~comp39x/2012-13

description

COMP390/3/4/5 Final Year Project Design. Darek Kowalski http://www.csc.liv.ac.uk/~comp39x/2012-13. Submission Deadlines. Specification (10%):Thu 18.10.12 noon Design documentation:Fri 16.11.12 noon Design presentation:Mon 19.11.12 - (whole design stage 15%)Fri 30.11.12 - PowerPoint PPT Presentation

Transcript of COMP390/3/4/5 Final Year Project Design

Final Year ProjectCOMP39X

COMP390/3/4/5Final Year ProjectDesign

Darek Kowalskihttp://www.csc.liv.ac.uk/~comp39x/2012-13

Final Year ProjectCOMP39X

Submission Deadlines Specification (10%): Thu 18.10.12 noon Design documentation: Fri 16.11.12 noon Design presentation: Mon 19.11.12 -

(whole design stage 15%) Fri 30.11.12 Interim Report: Fri 15.02.13 Demonstration (15%): Mon 22.04.13 –

Fri 26.04.13 Dissertation (60%): Thu 9.05.13 noon

2

You should make yourself available during the weeks for design presentation &

demonstration

Final Year ProjectCOMP39X

Project Stages Four phases

Phase 1: Specification (3.5 weeks)Phase 2: Design (4.5 weeks)Phase 3: Implementation & Testing (11 weeks)Phase 4: Demonstration & Dissertation (3

weeks)

3

w1 w2 w3 w4 w5 w6 w7 w8 w9 w10 w11 w12

Sem 1

Sem 2

specificationdocument

designdocument

designpresentatio

n

demonstration dissertation

interim report

Final Year ProjectCOMP39X

Design (15% of total mark) Purpose

To record the research and analysis doneTo detail the design of the system to be builtTo detail the design of evaluation

Design Documentation: due 16.11.12 noonOne copy to Student Office, one pdf via E-project

Design Presentation: 19.11.12 – 30.11.1215 minutes including questionsYou must make yourself available during the two

weeks 4

Final Year ProjectCOMP39X

Design Structure Summary of Proposal

DesignDesign of systemDesign of evaluation

Review against PlanGantt Chart showing what has been

completed, progress to date & any necessary changes

5

Final Year ProjectCOMP39X

Summary of Proposal Statement of background, aims and objectives

design document should be self-contained

Highlight changes to original specificationwhat changes are needed and why? justification is important

Summary of research and analysis done so farsummary of what you have read, tested (e.g.,

technical issues)? how outcomes affect the design?any analysis done? and their implications

6

Final Year ProjectCOMP39X

Design Typically should include

description of anticipated componentsdescription of data structures to be usedalgorithms to manipulate these data

structuresdesign of interfacesdescription of evaluation of system

Presentation gives a summary

Documentation gives all details7

How much details? Ask yourself: Will other people be able to implement the system by following your

design?

Final Year ProjectCOMP39X

System Design Object-oriented methodology

Traditional design methodology

Empirical investigation of hypothesis

Devising new algorithms

Others…

8

Final Year ProjectCOMP39X

Example – OO design use-case diagram

interaction chart

list of objects, attributes & methods

pseudo code of main methods

interface design

9

•use cases (actions)•actors•association•system boundary

•how components interact•information flow

•and necessary data structures

•make reference to the objects listed

•create using Java OR•draw in Word

Final Year ProjectCOMP39X

data dictionaries

system boundary diagram

ER diagram

logical/physical table structure

transaction matrix

pseudo code of main methods

interface design

etc

Example – Traditional Design

10

•entities & relationships•type of relationship

Data Flow Diagram•normalisation applied?

•process vs data•A / D / R / U•create using the language to be employed OR•draw in Word

Final Year ProjectCOMP39X

Example – Empirical Investigation Expect to see these IN

ADDITIONstatement of hypotheses to be

testeddescription of test data to be usedexperiment design: experiments to

be performed, any control to be usedhow the results will be analysed,

including any statistical techniques that will be used

anticipated conclusions11

For this type of project, design of evaluation is very

important

Final Year ProjectCOMP39X

Example – Devise New Algorithms Expect to see these IN ADDITION

description of problem to be solvedexisting algorithms of related

problem and a critical evaluationapproach to be used to solve the

problemhow the new algorithms will be

analysed, including mathematical and experimental analysis

details of mathematical/experimental analysis 12

system design required here

For this type of project,

literature review and design of

evaluation is

important

Final Year ProjectCOMP39X

Others… It is possible to use a combination of the

above approaches

Different projects may follow different ways

Seek advice from your supervisor which approach best suits your project

13

Final Year ProjectCOMP39X

Evaluation Design What criteria to evaluate system?

E.g., specification satisfied?number of features completeduser friendlinessusers' feedback, etc.

How to assess these criteria?

Who are involved in evaluation?

What testing?

What conclusion expected?14

Final Year ProjectCOMP39X

Resources Project webpage

http://www.csc.liv.ac.uk/~comp39x/2012-13especially guidelines for each assessment

Research papers

Books / Lecture NotesChristian W. Dawson: Computing Projects: A

Student's Guide, Prentice Hall, 2000. COMP208/214/215/216, COMP201, COMP207, etc.

The Web

Your project supervisor 15

Final Year ProjectCOMP39X

Assessments

Supervisor 2nd Supervisor

Industrial sponsor

DesignWBL

Normally you will receive email from the 2nd supervisor the week before telling you the date/time/venue for your presentation

You should reply to confirm recipient WBL project: consult Clare Martindale for

arrangement

Final Year ProjectCOMP39X

Assessment Form Snapshot of the form, available at

webpage

17

Final Year ProjectCOMP39X

Late Submission According to University standard penalties

5 marks deducted for each working day of lateness

Up to a maximum of 5 working days

Work received after 5 working days will receive a mark of 0

For any mitigating circumstances you should contact supervisor first (recommended) submit mitigating circumstances form with evidence

to the Student Office asap decision will be communicated to you shortly after 18

Final Year ProjectCOMP39X

Coming Lectures 4 lectures (or more)

Introduction & Specification week 1, Thursday 29 September 2011

Design week 4, today

How to proceed to design & implementation TBD

Demonstration & Dissertation semester 2

19

Final Year ProjectCOMP39X

Submission Deadlines Specification (10%): Thu 18.10.12 noon Design documentation: Fri 16.11.12 noon Design presentation: Mon 19.11.12 -

(whole design stage 15%) Fri 30.11.12 Interim Report: Fri 15.02.13 Demonstration (15%): Mon 22.04.13 –

Fri 26.04.13 Dissertation (60%): Thu 9.05.13 noon

20

You should make yourself available during the weeks for design presentation &

demonstration