Previous Lecture

lect13

Next Lecture

lect13, Wed 11/10

SW Design Patterns

Announcements

• Homework assignment h08 on SW Design Patterns posted. Due next Monday. There is no requirement for using/documenting SW patterns in your design documentation!

• Still focus on your projects. Lab work on documentation (design document, user manual) is meant to get you started and to utilize cycles of team members not central to ongoing implementation efforts at any given time.

• Difference of README.md and design document:
  • The README.md describes the GitHub structure and folder hierarchy and makes sure a programmer can make sense of it. It now should link to the deployment instructions.
  • The Design Document does not need to directly relate to the repository or to deployment details. It operates on a higher level: Overall SW architecture, modules, and their interaction. It also contains the UX design documentation…
• Deployment instructions will be really important for the group peer-evaluation next week lab08.

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

SW Design Patterns

• There is no requirement for using/documenting SW patterns in your design documentation!
• Slides: Software Patterns

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)
• Possibly: start with [lab07]](https://ucsb-cs148.github.io/f21/lab/lab07/)
  • Start Manual by identifying high-level Task/User Flow
  • Continue Design Document (new Section on documenting UI Design choices)
  • Plan Retro 3 (TBA)