DESIGNE OF APP REPORT 3

Documentation 3: Final report

Top of Form

Bottom of Form

Assignment Content

1.

Top of Form

Make sure you submit an  accessible link to your portfolio

Check your team portfolio has the following material - you will need to provide

1. Document describing your testing plan (in team or user testing) that you have conducted; Result of the tests and any analysis; Changes made on the basis of the testing

2. Description of the patterns you have developed for your interaction or information structure and evidence for this in your coding.

Build your MVP 

3. Preparation

4. From the discussion and feedback on MVP, team decides what changes need to be made and what you need to keep.

5. Run some guerrilla tests and provide more ideas to expand your scope

6. Document the changes and diagram your new MVP

7. Consider the Design Patterns used and describe there as outline to your MVP

8. Development

9. Code the MVP and regularly commit your work to your Team bitbucket repository with meaningful commit messages

10. Ensure you have the directory structure for HTML, CSS, JS, Images and other resources

11. Create new html, css and JS files and start working on them for new features

Include Analysis

Provide a short overview (up to 500 words) of the features, stories, code you used to enhance your website, what tests were most useful to you to improve your site, and any aspects of HTML5/CSS3 or javascript that were difficult for you, or that you think you did well. Say what you learnt most about in this unit.

Documentation

In a Team bitbucket repository, your code showing valid structure,

12. The latest version of your website on bitbucket.io.

In Confluence or MS Teams:

13. Group Bios,

14. Problem Statement, Assumptions and Hypothesis statement

15. Proto personas

16. Feature Hypothesis and Risk Prioritisation

17. Planned progress for next weeks and Development Responsibilities document,

18. Diagram of initial and final MVP, interactions and information flow, link to final Bitbucket.io site, W3C Compliance report

Testing and improvements

19. Document describing your testing (in team or user testing) that you have conducted; Result of the tests and any analysis; Changes made on the basis of the testing

20. Description of the patterns you have developed for your interaction or information structure (eg component cards) and evidence for this in your coding.

Team peer assessment to be completed in form provided in week 12 (or no marks assigned to students who do not submit)

This submission will include all material previously submitted in the Documentation as final submission for the Project.

Submit MVP

21. In a Bitbucket repository: your code

Bottom of Form