Skip to content
Brian Lin edited this page Feb 21, 2024 · 18 revisions

Welcome to the 402-Payment-Required wiki!

graph LR;
    A([Project Part 0]) --> B([Project Part 1]);
    B --> C([Project Part 2]);
    C --> D([Project Part 3]);
    D --> E([Project Part 4]);
    style A fill:#53fc7b,stroke-width:4px,color:#3d3d3d;
    style B fill:#53fc7b,stroke-width:4px,color:#3d3d3d;
    style C fill:#53fc7b,stroke-width:4px,color:#3d3d3d;

Reference for Risk Level

The risk level is estimated by the importance of each task (feature) towards the app. According to the scenario:

John, an event organizer, opens the QRCheckIn app for an upcoming tech conference. He generates a unique QR code for the event. As attendees arrive, they use the app to scan the QR code, automatically checking them into the conference. The app updates John's dashboard in real-time, showing the current attendance. John can also send push notifications to all attendees through the app.

High Risk Level

  • This means this task is extremely important to complete
  • Most of the tasks under this category are required features for the app to be able to run

Medium Risk Level

  • This means this task is somewhat important to complete
  • Most of the tasks under this category are not essential (to run) to the app but are important to have

Low Risk Level

  • This means this task is not important to complete (an add on feature)
  • Most of the tasks under this category are not as important, but they are nice to have

Reference for Story Point

Story Point is the estimated time to finish a task (feature).
It is estimated by how complex each task is, how much extra resources are needed (to learn), and how much understanding we have for each task.

Story Point 1

  • means this task takes 1 hour or less to complete

Story Point 3

  • means this task takes 3 hours or less to complete

Story Point 5

  • means this task takes 5 hours or less to complete

Story Point 8

  • means this task takes 8 hours or less to complete

Story Point 8+

  • means this task takes 8 or more hours to complete

Eclass Project Description

Create an event management system where attendees check in using QR codes on their mobile devices. Organizers can track attendance, manage event details, and send notifications.

Project Part 3

eclass requirements
Deadline:

Friday, 8 March 2024, 4:00 PM

Todo:

  • Code Base of Prototype
  • Code Documentation
  • Test Cases
  • Object-Oriented Design
  • Product Backlog
  • User Interface Mockups and Storyboard Sequences
  • Sprint Planning and Reviews
  • Demonstration

Project Part 2

eclass requirements
Deadline:

Friday, 16 February, 4:00 PM

Done:

Clone this wiki locally