User Story: Update Readme

[DeeMcCart]

EPIC:

As a system designer I can clearly explain site purpose, features and design so that the intention and delivered site can be understood by an assessor

Assumptions:

• The site is pretty much in place, just needing some final tweaks (!!)

Acceptance Criteria

• Readme contains all necessary sections

Tasks

• [x] Task1 User story x reference to features
• [x] Task2 Features section
• [x] Task3 Validataion docs
• [x] Task4 Deployments Section

[DeeMcCart]

14/11/23 1 hour on wireframe updates and double checking user stories; several hours on validation screenprints 18/11; however moving this into Sprint9 for completion Task2 Features: 20/11/23 put some shape on this Task2: Features: ONGOING 20-21-22/11/23 12 hours on this including screenprints Task2: Features: 3 hours additional on cleaning up broken links and streamlining text etc DONE (inadequately) for project submission 23/11/23 - looked back and there is still a lot of stream-of-conciousness stuff in the readme, and the validation section doesn't reflect the testing I did with multiple users and the many issues that were encountered and resolved. I think its just a reflection that this is genuinely a large project with a big scope (product design, development, data gathering & content development). Probably best to treat this as a watershed, if i didnt have a deadline then I would still be working and adding new exciting features. The features section of the readme is quite strong, and I've included it as a 'help' link within the site as I think its reasonably readable for end users trying to understand how the site hangs together. QED (for now)!!!!