<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Week 05 ToDos :: CS445/ECE451</title>
    <link>https://student.cs.uwaterloo.ca/~cs445/Winter2026/schedule/week05/index.html</link>
    <description>1. Watch Lecture Videos Watch the week 05 lecture videos in advance of your team meeting.&#xA;Videos Workflow Models Video Slides Quality Requirements Video Slides Conflict Management Video Slides Team Conflicts Video Slides Lecture References:&#xA;See the course Resources→References for instructions on how to access lecture references.&#xA;Karl Wiegers and Joy Beatty, Software Requirements, 3ed, Microsoft Press, 2013. Chapter 12: A picture is worth 1024 words Chapter 14: Beyond Functionality Soren Lauesen, Software Requirements: Styles and Techniques, 1ed., Pearson Education, 2001. Chapter 6: Quality Requirements 2. Updated Use Case Diagram Provide an updated Use Case diagram that includes the new use cases that were elicited with other teams in the Elicitation exerise in Week 4. Also, incorporate any feedback and suggestions for improvement that the TAs identified in your previous submission. Your models should have 5+ full use cases (don’t count sub use-cases). As before, use a diagram or modelling tool like LucidChart to create your use-case diagram. Supplement your diagram with a short description of each use case, explaining what that use case is about, and a short description of each actor. Put your use-case diagram and descriptions in the PDF file named «TeamName»_D5.pdf and submit it to LEARN.</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://student.cs.uwaterloo.ca/~cs445/Winter2026/schedule/week05/index.xml" rel="self" type="application/rss+xml" />
  </channel>
</rss>