Previous Lecture

lect14

Next Lecture

lect14, Tue 05/18

Project Documentation, UML

Announcements

• Still no current homework assignment. Focus on projects!
• Project documentation ongoing in three major documents:
  • design document,
  • deployment instructions (both started in current lab: lab06) ,
  • user manual (to be started in lab07))
• 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, June 10th, 4-7pm)

Here is the updated 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 lab06
  • Review of Leadership Roles
  • Log Retrospective 2 experiment outcome
  • Design Document (including a high-level system diagram),
  • Deployment and Operations Document (from README),