lect13

lect13, Wed 02/28

Project Progress and Documentation, UML, UX metrics

Announcements

No new homework assignment for the moment (one more may come). Focus on projects!
Next Monday is inter-team product evaluation!
Project documentation ongoing in three major documents:
- design document started in this lab: lab07)
- user manual (started next lab, lab08)
- README.md and deployment instructions (documenting your code base and deployment from the repo.Explain the code folder hierarchy and guide through the implementation effort.)
Project presentations (Final exam slot, Thursday, March 23, 4-7pm)

Here, again, is the point percentage breakdown for grading that the teaching team plans to use for the “Final Product” 40% of the course grade.

15% Presentation
5% Idea, and Idea Refinement
25% Functionality, Quality (Reliability & Polish)
- judged by review of demonstration, user manual, peer review, teaching team testing
10% Technical Difficulty Implemented
- judged by review of code/scope taking into account team background/experience etc.
20% Implementation
- judged by review of Github code, PRs, etc.
- use the README.md to make clear the repository structure and guide through implementation effort!
15% Design Process
- judged by Design Document, Kanban Board, Meeting Logs, Github TEAM information, etc. Design Document should steer through the process.
10% Manual

Standup
Continue lab07
- Overview system architecture diagram and associated explanation
- Identifying high-level Task/User Flow
- Continue Design Document (new Section on documenting team design decisions through meeting logs)
- Prepare Evaluation Goal for Monday’s inter-team testing session
Towards next lab: New set of user stories for the “final” product that your team will deliver, and marking those stories with a label “final” (just like the label MVP that you used previously).