Previous Lecture | lect14 | Next Lecture |
lect14, Mon 11/15
Project Progress and Documentation, (UML)
Announcements
- No new homework assignment for the moment (one more may come). Focus on projects!
- Project documentation ongoing in three major documents:
- A fourth important document is the Github README.md, which should explain the code folder hierarchy and guide through the implementation effort
- Project presentations (Final exam slot, December 6th, 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
High-level SW Design Concepts, UML Diagrams
- There is no requirement for using UML in your design documentation!
- Slides: Design and UML
Today: Work in Breakout Groups
- Standup
- Continue lab07
- Start Manual by identifying high-level Task/User Flow
- Continue Design Document (new Section on documenting UI Design choices)
- Retro 3 (Wed, Nov 17, or today, or outside of class)