COMP 208/214/215/216 - PowerPoint PPT Presentation


PPT – COMP 208/214/215/216 PowerPoint presentation | free to download - id: 697f4d-ZjViY


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation

COMP 208/214/215/216


COMP 208/214/215/216 Lecture 8 Demonstrations and Portfolios – PowerPoint PPT presentation

Number of Views:15
Avg rating:3.0/5.0
Slides: 23
Provided by: CSC65
Learn more at:
Tags: comp | case | comp | management | work


Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: COMP 208/214/215/216

COMP 208/214/215/216 Lecture 8
  • Demonstrations and Portfolios

Demonstration and Portfolio
  • The demonstration is a chance to show the system
    you have built
  • To show that you have implemented your design
  • To show that you have met requirements
  • To show any interesting or unusual features
  • The portfolio is the final deliverable
  • It collects together the intermediate
  • It adds some new items
  • Final report, testing report, screen shots,
    user manual.

  • Will take place in week 11 (30 April 4 May
  • Given to your project reviewer
  • Must be booked by Monday 16 April 2012 (e-mail to
    reviewer as usual)
  • You choose the location (e.g. a lab, my office) -
    REQUIRED TIME (!) and that you write on the
    e-mail where it will be.
  • The demonstration is worth 20 of the group mark.

What should you show?
  • Features of your system
  • Data entry data modification queries and
    reports different user views
  • Choose some suitable scenarios and work through
    them to give coherence
  • New member typical query session, etc.
  • Some system internals
  • To demonstrate your familiarity with software
  • Any special features
  • Web access security features graphical
    presentation of statistics, etc.

What shouldnt you show?
  • There is no need to show everything
  • Updating one kind of record is much like another
  • One query is often much like another
  • Give the flavour, but dont get boring
  • The demonstration should be timed to last no more
    than 30 minutes
  • including questions, dialogue and discussion.
  • Make sure you practice the demonstration.
  • There is no need to submit any documents with

Your Portfolio
  • The portfolio brings together all the project
  • There are several items included, so you will
    need to work as a team to produce it
  • The portfolio must be submitted by 12 noon,
    Friday 11 May 2012 (end of week 12) to the school
  • The portfolio counts 35 of the group mark.

Portfolio Contents
  • Essentially a record of all the project work
  • A project report
  • Maximum 10 pages
  • Requirements specification
  • What was presented at the requirements review,
    modified as necessary
  • Design Documentation
  • What was presented at the design review, modified
    as necessary
  • Test Documentation
  • Some sample screen shots of your application
  • To indicate the look and feel of your system
  • A user manual
  • This can be screenshots of the full online user

The Report Should Contain
  • Details of the team members and a summary of
    their roles on the project
  • An overview of the application
  • What it does, who is intended to use it why they
    might want to use it.
  • A description of what was achieved on the project
  • An evaluation of the strengths and weaknesses of
    the project
  • Suggestions for future developments
  • A 1-page discussion of how your project related
    to the codes of practice and conduct issued by
    the British Computer Society
  • A bibliography of materials used on the project.

Report People and Roles
  • Who was on the project?
  • What did people do?
  • A matrix of major tasks and people indicating
    major and minor roles might be a good way to do
  • How was the group organised?
  • Any particular responsibilities etc.

Report Application Overview
  • Application Domain
  • Expansion of the original mission statement
  • Types of User
  • Description of the user views - who will use the
    system and why
  • Typical Queries
  • Searches performed on the database
  • Typical Reports
  • Regular provision of structured information.

Report Achievements
  • What was actually produced
  • Database compared with design
  • Queries and reports compared with requirements
  • Any extra features e.g.
  • Web interface
  • Graphical presentation of statistical information.

Report Evaluation
  • What are the good points of your system?
  • What are the weak points?
  • Things that didnt work
  • Things you would do differently
  • Things missing from requirements
  • How well did the team function?

Report Future Developments
  • Things that might be done to extend the system
  • Inclusion of other information
  • Additional functionality
  • Additional user views
  • Commercial exploitation.

Report Professional Issues
  • There are 17 items in the BCS Code of Conduct
  • Which items apply to your project?
  • Which items did you comply with?
  • Were they any items not complied with - and why?

Report Bibliography
  • It is always important to say what sources you
  • Include technical sources and any application
    domain material
  • These must be cited in the correct form
  • A forthcoming lecture will discuss how to cite

Test Documentation
  • Strategy
  • Data used size of test data selection of test
    data real or imaginary
  • System testing do the functions provided work?
  • Acceptance testing do the functions provided
    meet user requirements?
  • Results
  • Known errors
  • Requirements satisfied.

Screen Shots
  • These are intended to show what the system looks
  • Two or three should suffice for most systems
  • e.g. Introductory screen, typical entry screen,
    typical report
  • No need to show every screen, query and report
  • Just show ones which are different.

User Manual
  • Should include (as appropriate)
  • Overview of software what it does who it is for
  • hardware requirements
  • how to install the software
  • how to run the software
  • how to use the software
  • how to quit
  • Write in terms appropriate to target user.
  • The user manual may be included online as part of
    your system
  • In this case, your Portfolio should have screen
    shots of the entire user manual.

Individual Submission
  • Every student must also submit an individual
    contribution. The deadline is the same 3 pm on
    Friday 11 May 2012
  • This contains
  • A statement of what you personally learnt on the
    project (1-2 pages)
  • Technical skills
  • Project management skills
  • Group working and interpersonal skills
  • Any other skills acquired.
  • A Peer Assessment Form
  • An assessment of the contributions of team
    members - including yourself.

Moderation of Group Mark
  • The individual submissions for the team are used
    to moderate the group mark
  • Your statement of what you learnt is assessed
  • Peer assessments for the team are collated and
    additions/reductions are made according to peer
    perceived contribution.

(No Transcript)
  • The demonstration and the portfolio are
    opportunities to show and to write about what you
    have done
  • Together, these are worth 55 of the overall
  • Everyone must also submit an
  • Individual submission, comprising
  • An Individual Learning Statement a Peer Group