Use Case Diagrams #87
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#87
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We need to document and establish what Use Cases our system has/should have. This will be an ongoing issue and will require sub-issues.
Parent Issue: #82
Use Case Diagram:
Login/Logout: Users can authenticate, gaining the appropriate access level.
Issues: #9, #57, #58, #59, #60
Quest View: Users can access a basic view without authentication.
Issues: #56
Add Cards: Users can add cards to their interface.
Issues: #68, #44, #45, #46, #47, #48, #49, #50, #23, #24, #25, #26, #27, #28
Edit Cards: Users can edit active cards (size, color, background).
Remove Cards: Users can remove active cards.
Change Style: Edit the page style (light/dark mode, text style/color, background).
Issues: #61, #62, #63, #64, #31, #32, #33, #34, #17, #18
Change User Interface: Users can create interfaces using pre-made card layouts.
Issues: #65, #66
Drawio fil för framtida ändringar
The diagram correctly portrays how the user will interact with the app. Some things might change but it is accurate for the moment. 👍