Skip to content

Refine and Finalize Sequence Diagrams for Final Milestone #667

Description

@winterwitchy

📝 [Documentation] Refine and Finalize Sequence Diagrams for Final Milestone

Description

The sequence diagrams drafted during Milestone 1 need to be reviewed, corrected, and
finalized to accurately reflect the implemented system behavior in the Final Milestone.
This includes updating flows to match current backend endpoints, incorporating new
features (gamification, leaderboard, notifications), and ensuring consistency with the
final class diagram.

Feature / Task Details

  • Review all existing sequence diagrams against the current implementation
  • Update actor interactions and method calls to match final backend API and service layer
  • Add missing sequence diagrams for Final Milestone features (e.g. point awarding,
    badge assignment, leaderboard update, notification dispatch)
  • Ensure consistency with the Final Milestone extended class diagram (D2)
  • Resolve any contradictions between sequence diagrams and use case / class diagrams
  • Follow UML sequence diagram conventions (activation bars, return arrows, alt/opt frames)

Deliverables

  • Updated sequence diagrams for all Milestone 1 flows (authentication, report
    submission, routing, agree/disagree, admin actions)
  • New sequence diagrams covering Final Milestone features (gamification events,
    leaderboard ranking, badge award, notification flow)
  • Diagrams published to the project Wiki under the Sequence Diagrams page

Acceptance Criteria

  • All existing sequence diagrams reviewed and corrected where needed
  • New diagrams added for Final Milestone features
  • Method names and endpoint calls are consistent with the actual implementation
  • Diagrams are consistent with the final class diagram (D2)
  • All diagrams follow UML sequence diagram notation
  • Diagrams are accessible on the project Wiki
  • Documentation updated (if applicable)

Deadline

16.05.2026 21:00

Notes

Cross-check with the backend REST endpoints and service-layer method names before
finalizing. Coordinate with backend and mobile subgroups to verify actor interactions
are accurately represented.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

Fields

No fields configured for Task.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions