Please enable JavaScript.
Coggle requires JavaScript to display documents.
Tabletop Games (Non-functional requirements (Economical (Staff can edit…
Tabletop Games
Non-functional requirements
Economical
Staff can edit database
Cost-effective to manage
Legal
User data privacy
Aesthetics
Easy to use
Technology platform
Data security
Constraints
App development environments
Device viewing
Code and scripting limitations
User skills
Database environments
What data can be stored
Functional requirements
Data: what needs to be stored
Member record
Borrowing record
Game record
Functionality: what the app needs to do
Remove lost games from the library (game record)
Remove games that are returned to the owners (game record)
Add games to the library (game record)
Record when a game is borrowed/returned by a member (borrowing record)
Record when a member has paid their annual membership fee (member record)
Store information entered by users (member record)
Allow administrator to search for games still on loan (borrowing record)
Search for members who are behind on membership fees (member record)
Search games owned by a given member (game record)
User interface: what users will see/can do
Filter both browsing and searches based on game information
Search games by title
What games are available in the library
Enter their name and contact details
Put a hold on a game