GamingsystemManagement byPattanonsoponwichettwong
NameoftheStudent(2541641)
Undertheguidanceof Dr.HubertShanthan
AProjectreportsubmittedinpartialfulfillmentoftherequirementsfor theawardofdegreeofBachelorofComputerApplicationsof CHRIST(DeemedtobeUniversity) November-2025
SRS: SOFTWARE REQUIREMENTS SPECIFICATION
Game System Management Web Application ---
1. Introduction
Purpose
The Game System Management Web Application was devised to assist users and administrators in organizing, tracking, updating, and managing digital games and game-related information in a structured and scalable environment It acts as a unified platform that simplifies game ownership, inventory items, rankings, user validation codes, and administrative operations through the use of a clean, intuitive UI The application will allow gamers to maintain personal libraries without clutter of data and the administrators to have full control over the database for the reliability of the system and continuous deployment updates.
Scope
The system supports:
User registration, authentication, and profile maintenance
Hosting a browse-able collection of games connected to a structured database
Inventory item insert, remove, resize, clear, swap, and reserve/scale capacity
Competitive leaderboard display & updating score ranking
Full administration capability to edit or delete any record of a user or game without restriction
Backend support for code validation checks and format safety
Deployment and maintenance of the full application to cloud hosting platforms
Definitions
Game Library: A collection of game titles by a person or globally stored sequentially.
Inventory: A vector-like data structure that holds a user's owned in-game items.
Leaderboard: A ranked board comparing scores submitted by players
Admin access: All rights and database modification authority
---
There are no exercises for this unit
2 Description Overall
2.1 Requirements of the Web Application
It should be an automated digital system that eases the management of games, user profiles, itemized inventories, and competitive rankings-all while ensuring practical deployability onto state-of-the-art hosting platforms The system shall be able to handle huge sets of data for games and items, handle frequent updates of data without degradation in performance, and include secure login mechanisms, real-time scoreboard performance, clean navigation, and original input code validation systems ---
2.2 Principal Modules
The application consists of 8 core modules, each responsible for a different key segment of operation:
1. User Management Module
This module is meant for handling user identity, authentication, and personal profile control
Users should be allowed to:
Create new account securely
Login using encrypted passwords
Update their own profile information
Delete their own account if needed
It checks for the correct data format in the login input fields, informs of missing fields, and handles authentication errors elegantly Passwords are not stored as-is; they pass through encryption layers using backend hashing functions to make them secure against account breaches
2 Game Library Module
The Game Library module maintains a catalog of digital games in a structured manner Using the module, users should be able:
Add a new game title to their library
Remove a game from their library
Display the list of owned games in sequence
Administrators should be able to:
Insert or delete any game record in the global database
Manage all game library operators
Approve or deny newly submitted game additions if flagged as duplicates
Ensure library updates without breaking structure
Names of game library entries should be clear and not repeat data to keep it tidy. UI responsiveness: Resizing of game display sections via CSS grid layouts; AJAX error codes if server-side integration is being used for deployment breakdown.
3. Inventory Management Module
It is designed to act like a scalable internal container of tracked owned in-game items, which allows users and admins to perform actions such as:
push back() → add new owned item pop back() → remove last item
insert(at position, item) → add at index
erase(at index) → remove item at the specified index
resize() → increase/decrease inventory size
clear() → Clear the entire inventory swap() → swap inventories with another user capacity() / shrink to fit() → optimize storage
The system shall indicate inventory count, current capacity, and also if the inventory is empty or full. Item entries shall be kept in a stacked list, and displays in the UI are interactively updated smoothly without needing to reload the whole interface
(Note - The following should not be regarded as an afterword, but rather as information for those desiring to go more deeply into this subject )
4 Code Validator Module
This module validates special user-entered codes, such as player codes or keys to access a game One of the validations it supports is:
✔ Palindrome format validation
Example:
level cap ✅
game EM g? ❌ invalid noise caps
This module does NOT store or validate criminal / fraud data, only user codes for technical correctness and format safety.
5. Leaderboard Module
The Leaderboard presents the scores and ranks the users according to that Leaderboard includes:
User score submission accepted
Comparing highest to lowest Sorting rankings
Showing top 10 ranks
Automatic highlighting of rank changes
Leaderboard display must be visual, structured, and easily readable in columns:
Rank
Username
Score
Things Owned
When formatted into flipbook pages, leaderboard renders like screen dominance stats where best values float at top
Fastener:
6. Admin Control Module
This is the highest privilege system, which allows admins to:
Delete any user or game record
Eliminate duplicate records
Modify database tables if necessary
Deploy changes without restriction
Maintain full DDL and DML operators in DB
Note:
The administration control exists to assure reliability and cannot support criminal operations of fraud.
It allows the parent to provide the child with choices while still ensuring the child receives a balanced meal
7. Performance Analytics Module
This module tracks:
User game ownership trends
Inventory size, complexity, updates
Score climb progress
Rank environment
Metrics display
It gives a data-tracking dimension to the system without any external financial prediction (Saud Al Abbasi, Shenzhen, China) ---
8. Deployment & Maintenance Module
This module ensures:
Compatibility with hosting
Cloud deployment
Bug fixes
UI clean updates
CI/CD support
It supports engineering-level deployment pressure, whereby false zero error tolerance applies.-
3 Functional Requirements
Requirement Description
User Authentication Secure register/login, encrypted password storage
Game Library User add / remove, Admin insert / delete any game
Inventory: insert/remove/resize/clear/swap inventory items
Leaderboard\taccept scores, compare, sort, display rankings
Code Validation: validate the palindrome format of users' codes
Admin Control\tModify/delete any record in DB and maintain structure
Deployment Export files, host, connect DB, test live URL
Each one of these functional parts should work perfectly in both web and flipbook representations
---
The way to solve this is either to set the interaction term to equal zero when interacting with the hypothesized moderator or to include an interaction term for all hypothesized moderators
4 Non-Functional Requirements
NFR Details
Security Password encryption, admin role validation, safe data handling
Performance: Quick loading, interactive UI, real-time ranking updates
Scalability: Support large game lists and inventory stacking
Reliability: Few crashes, cloud availability, and error handling
Usability: Clean navigation, readable layout, and easy operations.
Cross-Platform Support: Should work on PC and mobile browsers NFRs exist in order to validate a smooth environment within the system
---
Press here to access online animation activity
5. Software and Hardware Requirements
Software ✔ Chrome/Edge/Firefox or any modern browser ✔ MySQL or cloud database support ✔ Creating a flipbook platform: AnyFlip, FlipHTML5 etc. ✔ Deployment platform: Vercel, Netlify, AWS, etc
✔ Backend runtime support if needed
Hardware ✔ PC/Laptop/Mobile ✔ Stable Internet ✔ Optional: server machine if hosting locally - --- 6 Data Flow Diagram (DFD) [User] → Register/Login → [Game Library Database] → [Inventory Storage] → Submit Score → [Leaderboard UI]