Skip to content

– Final Project Report [TEAM]

Past due by over 5 years 100% complete

A technical report designed to:

  1. “Evaluate the extent to which the software you produced, the way your team worked, and the way the
    project was managed, were high quality.”; and
  2. “Discuss how you could have improved the quality of your software, the way your team worked, and way
    the project was managed.”.
    Note that this is a technical evaluation document, …

A technical report designed to:

  1. “Evaluate the extent to which the software you produced, the way your team worked, and the way the
    project was managed, were high quality.”; and
  2. “Discuss how you could have improved the quality of your software, the way your team worked, and way
    the project was managed.”.
    Note that this is a technical evaluation document, not a piece of reflective writing. It should be objective,
    precise and concrete. It should refer directly to the Quality Assurance Plan and the original Pitch and Project
    Plan.
    The report should be no more than 15 pages, including references and any preamble. If you wish, you may
    include appendices beyond the 15 pages, however these should only be used to provide additional evidence
    where this enhances the submission, and should be referred to, in order to establish their relevance, in the
    main text. The report itself should be self-contained as a piece of technical writing.
    You are expected to draw on learning from other modules in deciding what to include in, and
    in producing this report. The mentor and Module Tutor will be happy to provide feedback on
    your ideas about what to include and how to structure the report.

There are no open issues in this milestone.

Add issues to milestones to help organize your work for a particular release or project.

Create new issue

Or find and add issues with no milestone in this repo.