Skip to content

Milestones

List view

  • D5: Live presentations/demonstrations

    Overdue by 3 year(s)
    •
    Due by November 22, 2022
    •0/3 issues closed
    0% complete3 open0 closed

  • D4: Test suite

    Overdue by 4 year(s)
    •
    Due by November 24, 2021
    •1/1 issues closed
    100% complete0 open1 closed

  • D3: Working demonstrator

    <p>This Deliverable is a working demonstrator - that is, an implementation of what you designed. A couple of notes:</p><ul><li>the demonstrator can be considered a first \"minimum viable product\" (MVP); something that runs, something that resembles what you designed. Obviously, marking will be affected by (a) the divergence of what you designed, and (b) the level of completeness of the MVP.</li><li>You don't have to submit the source code; a link to a repository in GitLab or GitHub would do fine. Please put the link in the documentation that you submit.</li><li>Issue (a) can be addressed by updating documentation (D1, D2) to address that divergence, or alternatively, by creating an additional document that could be considered a chapter on \"Implementation\", in which you outline how the design was implemented, and how that changed from the original design.</li><li>Issue (b) can be addressed by demonstrating the most important features; for example, \"log-in\" functionality that might be part of some projects is typically not the most interesting aspect of any project, so perhaps that could be skipped in the first instance.&nbsp;</li><li>part of the submission should be a screencast (a video) in which you demonstrate the functionality. I won't be running your software myself, so marking will be based on what you present. One useful tool could be Screencast-o-matic (<a href=\"https://screencast-o-matic.com/\" target=\"_blank\">https://screencast-o-matic.com/</a>) but other tools could be used to (e.g. I use QuickTime for screen recordings). In previous years, teams have used subtitles or a voice-over to \"talk the viewer through\".&nbsp;</li><li><span style=\"text-decoration: underline;\"><strong>Do NOT copy the whole source code in a</strong><strong> document</strong></span>! You may include <span style=\"text-decoration: underline;\"><strong>key snippets</strong></span> of code as part of the implementation chapter, but you don't have to.&nbsp;</li><li>Typically you can point out which parts of the design were implemented in which source code files, for example.&nbsp;</li></ul><p>In sum, this deliverable is the cumulative result of D1, D2, and D3. The \"D3\" part is a chapter called \"Implementation\" in which you explain how the design (laid out in chap 2) was implemented; which technologies were used,&nbsp; which files implemented what functionality, etc. Here you can also include the link to the source code.</p><p>&nbsp;</p>

    Overdue by 4 year(s)
    •
    Due by November 12, 2021
    •11/11 issues closed
    100% complete0 open11 closed