WEB-BASED CRUD APP

WEB-BASED CRUD APP

1. Criteria

   • Self-determied
     • SDC 1: Adding a "time gamed" section in player account details helps track their gaming screentime.
       • By incorporating a "time gamed" section within the player account details, it enables users to meticulously monitor and keep track of the total screentime they have dedicated to gaming, thereby providing them with insightful data about their gaming habits.
     • SDC 2: Integrating an achievements portal allows players to view their accomplishments.
       • By integrating an achievements portal for players, they are able to view and reflect upon their accomplishments, creating a comprehensive record of their successes and milestones in the gaming world.
   • Prescribed
     • PC1. Requires a successful login before retrieving and displaying the users personal account information
       • To view account details, the database must prompt for a username.
       • To access confidential user information, the database must require password entry.
       • The database must provide an option to reset passwords through a "forgot password" feature.
     • PC2. Ensure data entered by the user is validated before it is added to the database
       • Users should be able to review their data before finalizing and submitting updates to the database.
       • The database must include a user’s email address to facilitate password resets.
       • The database must feature an option to display a user's secret question if password reset attempts fail.
     • PC3. Meet all Data Requirements
       • It must comply with all data storage requirements, including user detail storage.
       • The database should support access and modifications via HTTP requests.
       • It must be capable of storing information about game libraries, such as game names, ratings, purchase dates, and hours played.
     • PC4. Meet all User Interface Requirements
       • The Landing page should include buttons for Signup and Login to fulfill user interface requirements.
         • Both forms should have validation rules to ensure proper data entry.
       • The Signup button must direct users to a registration form.
         • The Login button must direct users to a login form.
           • After successful Signup or Login, users should be redirected to a User Profile page that displays and allows updates to their information, such as gamer tag and email.

2. User Problem

   • User Problem 2
     • Cheryl, a 73-year-old retiree, needs a basic interface to monitor her gaming hours for health check-up since she has issues with memory, and she uses the application to remind her the time she spends on gaming. The application must be especially user friendly for elder, less computer literate people.
   • User Problem 1
     • Geoff, a 25-year-old university student, needs a fast method of recording and revising his gaming performance without going through several sub-menus. He looks for features that give statistics of the games quickly, which is in line with his desire to compete.

3. Impacts

   • Social
     • Productivity Increase
       • May result in more efficient work processes, enabling individuals to focus on higher-value tasks.
     • Efficient Collaboration
       • Can enhance teamwork and communication, positively impacting both professional and personal relationships.
   • Pesonal
     • Managment of Information
       • CRUD operations allow individuals to easily input, view, edit, and delete financial transactions, aiding in better money management.
     • Empowerment
       • Users can perform data-related tasks independently without requiring extensive programming or database management skills.
     • Privacy and Data security
       • Can help people protect their private data.
   • Economical
     • Business Oppurtunities
       • Can enable businesses to offer new services or expand their customer base, potentially driving revenue growth and expansion opportunities.
     • Saving Costs
       • Can decrease the need for physical storage space, leading to potential cost savings.

4. DATA

   • Data Types
     • String
       • A data type used in programming, that is used to represent text rather than numbers
     • Integer
       • A data type used to represent real numbers that do not have fractional values. Its also used for fields like ID'S
     • Primary Key
       • The column or columns that contain values that uniquely identify each row in a table
   • Data Required to Login/Signup
     • Username
     • Password
     • Email
     • Date of Birth
     • First Name
     • Last Name

5. Validation Rules

   • Format Validation
     • Verifies that data matches a specific format, such as an email address validation.
   • Range Validation
     • Ensures numbers fall within a specified range.
   • Length and Size Validation
     • Imposes a maximum character limit on text fields.
   • Required Field Validation
     • For creating or updating specific fields.
   • Data type Validation
     • Ensures that the data entered into fields matches the expected data type.
   • Unique Value Validation
     • Typically used for fields like usernames, email addresses, or identification numbers.

6. Contraints/ Limitations

   • Time
     • Scheduled tasks
       • Data Consistency
         • Performance
   • Skills
     • Data Integrity
       • Security
         • User Experience
   • Coding Environment
     • Development efficency
       • Team Skill
         • Security and User Details
           • Costs