207assign3 toast

[ToastedToast00]

Pull Request Summary — Assignment 3: Features and Use Cases

This pull request extends the design work established in Assignment 2 by defining the system‑level capabilities and actor‑driven goals required for Assignment 3. While Assignment 2 focused on distributing responsibilities across core domain objects through CRC cards, this assignment shifts to describing what the system must provide (features) and what users and administrators aim to accomplish (use cases). The additions in this PR build directly on the domain concepts identified earlier while avoiding overlap with existing team contributions.

Additions in this PR

• Added a new set of features to docs/analysis/features-and-usecases.md that expand the platform’s safety, moderation, support, and account‑management capabilities.
• Added nine unique use cases aligned with these features, each written as an actor‑goal statement.
• Added a traceability table mapping each use case to the feature(s) that support it.
• Added a personal use case diagram illustrating the interactions between actors and the use cases contributed in this PR.

Features Added

These features complement the existing system capabilities defined by the group and reflect areas not previously covered:

• User Blocking and Safety Controls
• User Reporting System
• Support Ticket System
• Game Progress Tracking
• Notification Preferences Management
• Role and Permission Management
• Account Recovery
• Privacy and Visibility Settings

Use Cases Added

The following use cases were introduced to represent user and admin goals associated with the new features:

• UC1: User Blocks Another User
• UC2: User Reports Another User
• UC3: User Submits a Support Ticket
• UC4: User Views Game Progress
• UC5: User Updates Notification Preferences
• UC6: Admin Assigns User Roles
• UC7: Admin Moderates User Reports
• UC8: User Recovers Account
• UC9: User Adjusts Privacy Settings

Traceability and Diagram

A traceability matrix was added to show how each use case maps to one or more system features.
A personal use case diagram was also included to visually summarize the relationships between actors and the use cases contributed in this PR.

Relationship to Assignment 2

The features and use cases introduced here build on the domain structure defined in Assignment 2. Concepts such as User, SupportRequest, Game, and PermissionPolicy informed the selection of features and ensured consistency across the design process. This assignment continues the progression from object‑level responsibilities to system‑level behavior and actor goals.

[rachelkingCPTC]

Your features and use cases look good, but I do think you could have produced a more professional use case diagram. Your System should be a box surrounding your use cases, and your actors should be represented by some kind of user-looking icon. It's hard to read which actor is responsible for what.

[rachelkingCPTC]

Good level of detail on these use cases