Skip to content

Lab 2: Requirements Analysis

Lab 2 — Requirements Analysis & Specification

Weeks 3–5

Define the requirements of your software system. By the end of this lab, you'll have a clear ontology of your project — use cases, user stories, acceptance criteria, and a requirements specification.

Checklist

  • Project Progress Report (5 pts) — summary of meetings, decisions, and status
  • User Stories with Acceptance Criteria (30 pts) — each team member contributes at least one; include names and contribution percentages
  • Use Case Specifications (35 pts) — for each user story document: name, authors, actors, entry conditions, exit conditions, flow of events
  • Use Case Diagrams (30 pts) — created with a professional tool (Draw.io, Lucidchart — hand-drawn or Office Suite diagrams get 0)
  • Meeting minutes for all team and mentor meetings

Key Deliverables

Item Points
Requirements Analysis (all parts) 100

Resources

User Stories & Acceptance Criteria: - User Stories with Examples (Ones) - Atlassian: User Stories - Atlassian: Acceptance Criteria

Use Cases & UML: - OpenUP: Use-Case Specifications - Larman: Applying UML and Use Cases - UML Diagrams: Use Case Diagrams - Creately: Use Case Diagram Tutorial

Notes

  • 7-day grace period with 10% penalty for late submissions
  • Individual: Each team member MUST complete the Lab 2 Peer- and Self- Assessment or receive 0 for this assignment