STI WEST NEGROS UNIVERSITY

Burgos St., Bacolod City 6100

COLLEGE OF INFORMATION and COMMUNICATIONS TECHNOLOGY

First Semester, AY 2024-2025

INTE1024: Event-Driven Programming

Final Examination/Date:_________

Group Leader: COURSE

SCORE:
Group Members: SECTION

System Development with Database Implementation

Objective:
Create a system or application using your preferred UI Framework, with the integration of a database (MySQL, PostgreSQL, MariaDB, or any
database of your choice). This project will showcase your programming and database management skills. The system GUI, depending on your
group's expertise.

Presentation Guidelines:
You may present your final system/application on the following dates:
- December 9, 10 , 11, 13, 2024
- Time: 1:00 PM to 4:00 PM

You are encouraged to schedule your presentation on any of these dates if you wish to present early.

Important Deadline:
Your final system/application must be submitted no later than December 13, 2024, at 08:30 PM.

Instructions

1. System Requirements:
The system must address a real-world problem or provide a useful function.
 Integrate a database for data storage and retrieval.
 The database should have at least three related tables.
 Include basic CRUD operations (Create, Read, Update, Delete).

2. Technology Options:
 Programming language: Any language of your preference (e.g., Python, C#, Java, PHP).
 Database: MySQL, PostgreSQL, MariaDB, or any suitable database.
 Tools: You may use MS Access, Workbench, or any database tool of your choice.
 You are allowed to use the tools of your choice (Visual Studio, Eclipse, IntelliJ, etc.) for programming.
 You must follow the provided instructions and ensure the system implements basic CRUD (Create, Read, Update, Delete) operations on the
database.

3. Group Requirements:
 Each group must consist of 3 to 4 members.
 Roles and Contributions: Each member must take a specific role (e.g., Developer, Database Designer, Tester, Documenter). Document these
roles in your submission.
 A progress report must be submitted weekly. Use the provided format for tracking.

4. Progress Report Format:

As you work on the project, you must record your progress weekly and submit a report showing your progress each week. This must include any
problems encountered and solutions implemented.

5. Roles:
 Every group member must contribute to a distinct part of the project. For example, one person may handle database design, another the
frontend GUI, and another the backend logic.
 A role allocation document must be submitted as part of your progress report.

6. No Outsourcing:
 Do not hire anyone to complete the project for you. The work should be done entirely by your group members.
 Any group found outsourcing their work will be disqualified.

7. PowerPoint Presentation:
At the end of the project, each group must create a PowerPoint presentation summarizing the following:
 Overview of the system/application
Tools: Presentation slides (e.g., PowerPoint, Google Slides, Canva).
Include the objectives, key features, and intended users of your system.
 Database design and structure
Tools: ER diagram creation tools (e.g., Lucidchart, Draw.io, MySQL Workbench).
Present the database structure, including ER diagrams and table schemas.
 Screenshots or demo of the application

INTE1024: Event-Driven Programming Course Instructor(s): Page 1 of 4

Final Examination AY 2024-2025 John Emmanuel L. Genoguin , Klent John Decena Juaniza , Joao Roumil G. Vergara CpE
 Tools: Screen capture software (e.g., Snipping Tool, ShareX) for screenshots or Screen-sharing tools for live demos (e.g., Zoom, Microsoft
Teams).
 Contribution of each group member (roles and tasks completed)
Tools: A summary table or slide outlining each member's roles and completed tasks.
Optionally, use project management tools (e.g., Trello, Asana) to provide evidence of contributions.

8. Submission:
Submit your code, documentation, database scripts, and PowerPoint presentation as a single zipped folder via email or the designated
submission platform.

Progress Report Format:

Each group must submit a weekly progress report (starting from the 1st week of work until submission). Use the following format for
the progress report and role allocation:

Week/ Assigned Solutions

Date Name Tasks Completed Tasks Pending Challenges Faced
Day Role Implemented
Database Created ER diagram, Design queries Database relations Refined the
Week 1 (Insert Date) John
Design created tables for CRUD unclear relationships
Frontend Designed GUI layout, Code forms No connection to Implemented DB
Week 2 (Insert Date) Jane
Development started coding and buttons DB yet connection

System Quality Rubric(GUI-based):

Criteria Excellent Good Needs Improvement Score

All CRUD operations work flawlessly Most CRUD operations work with Major bugs or incomplete
Functionality with no bugs in the system. minor bugs. CRUD operations.
36% - 40% 20% - 35% 0% - 19%
Database schema is logical, efficient, Poor database design, lacks
Database schema has minor flaws or
and normalized with detailed normalization or logical
Database Design lacks some details in design.
documentation. structure.
18% - 20% 10% - 17% 0% - 9%
The GUI is highly user-friendly, The GUI is functional but lacks GUI is not functional or
User Interface
responsive, and polished. polish or usability issues. very user-unfriendly.
(GUI)
18% - 20% 10% - 17% 0% - 9%
System is secure, handles errors Some error handling is implemented Poor or no error handling or
Security and gracefully, and prevents common but there are gaps in security or error security measures.
Error Handling vulnerabilities. prevention.
18% - 20% 10% - 17% 0% - 9%
Code is clean, well-organized, follows Code is organized but lacks some Code is poorly structured
Code Structure
best practices, and is well-commented. clarity or proper documentation. and lacks adequate
and
documentation.
Documentation
9% - 10% 5% - 8% 0% - 4%

System Quality Rubric(Console-Based):

Criteria Excellent Good Needs Improvement Score

All CRUD operations work flawlessly Most CRUD operations work with Major bugs or incomplete
Functionality with no bugs in the system. minor bugs. CRUD operations.
36% - 40% 20% - 35% 0% - 19%
Poor database design, lacks
Database schema is logical, efficient, and Database schema has minor flaws or
Database normalization or logical
normalized with detailed documentation. lacks some details in design.
Design structure.
18% - 20% 10% - 17% 0% - 9%
The GUI is highly user-friendly, The GUI is functional but lacks GUI is not functional or
User Interface
responsive, and polished. polish or usability issues. very user-unfriendly.
(GUI)
18% - 20% 10% - 17% 0% - 9%
System is secure, handles errors Some error handling is implemented Poor or no error handling
Security and
gracefully, and prevents common but there are gaps in security or or security measures.
Error
vulnerabilities. error prevention.
Handling
18% - 20% 10% - 17% 0% - 9%
Code Code is clean, well-organized, follows Code is organized but lacks some Code is poorly structured
Structure and best practices, and is well-commented. clarity or proper documentation. and lacks adequate
Documentatio documentation.
n 9% - 10% 5% - 8% 0% - 4%

PowerPoint Presentation Rubric:

Criteria Excellent Good Needs Improvement Score
Clear, logical explanation of the system, Content is mostly clear, with minor Content is unclear, incomplete,
Content
database, and roles; all points addressed. gaps or missing points. or poorly explained.
Clarity
36% - 40% 20% - 35% 0% - 19%
Slides are functional, but lack design
Well-designed, visually appealing slides Slides are poorly designed or
Design and consistency or minimal use of
with appropriate use of graphics. lack visual appeal.
Visuals visuals.
18% - 20% 10% - 17% 0% - 9%

INTE1024: Event-Driven Programming Course Instructor(s): Page 2 of 4

Final Examination AY 2024-2025 John Emmanuel L. Genoguin , Klent John Decena Juaniza , Joao Roumil Vergara, CpE
 Excellent explanation of the technical Adequate explanation of technical Lacks technical depth or clear
Technical
aspects of the system and database. aspects, but lacks depth or clarity. explanation of system/database.
Depth
18% - 20% 10% - 17% 0% - 9%
Clear and detailed breakdown of Most contributions are outlined but No clear breakdown of
Team individual contributions, showing with limited details or unclear individual contributions or
Contribution teamwork. distribution. inaccurate details.
9% - 10% 5% - 8% 0% - 4%
Delivery is clear but lacks Delivery lacks clarity,
Clear, confident, and professional
Presentation confidence or professionalism; confidence, or professionalism;
delivery; excellent use of slides.
Skills occasional reliance on slides. over-reliance on slides.
9% - 10% 5% - 8% 0% - 4%

Below is a breakdown of the assessments using the PowerPoint Presentation Rubric and GUI-Based or Console-Based Rubric, with
specific point allocations for each seatwork, quiz, and task performance.

Task Performance Assessment Breakdown

Total
Assessment Criteria Description
Points
Functionality 20pts Smooth operation of the application, all functionalities working properly.
Database Integration 15pts Seamless integration with the database for data operations (CRUD).
Task Error Handling &
5 pts Proper validation for user inputs and graceful error handling.
Performance 1 Input Validation
Code Structure and Clean, organized, and well-commented code that follows programming best
5pts
Organization practices.
Functionality 20pts Full functionality of the application with no major bugs or errors.
Database Integration 15pts Successful integration of database for CRUD operations.
Task Error Handling & Validation and error handling for unexpected inputs, with informative
5 pts
Performance 1 Input Validation feedback.
Code Structure and
5pts Code is readable and logically structured with appropriate documentation.
Organization

Quizzes Breakdown

Total
Assessment Criteria Description
Points
Content Clarity 10pts Clear and concise answers, well-structured responses.
Quiz 1 Design and Visuals 5pts Answer presentation is organized and visually clear.
Technical Depth 5 pts Detailed explanation of technical aspects related to programming or systems.
Content Clarity 10pts Clear, precise answers that reflect understanding of the topic.
Quiz 2 Design and Visuals 5pts Visually clear, organized answers.
Technical Depth 5 pts Strong explanation of technical terms or concepts.

Seatwork Breakdown

Total
Assessment Criteria Description
Points
Content Clarity 10pts Clear and logical explanation of the system, database, and roles.
Seatwork 1 Design and Visuals 5pts Well-designed, visually appealing slides with appropriate use of graphics.
Technical Depth 5 pts Explanation of the technical aspects of the system and database.
Content Clarity 10pts Detailed explanation of the system’s functions and interactions.
Design and Visuals 5pts More detailed design, well-organized slides with visuals.
Seatwork 2
Deeper dive into the technical elements, showing knowledge of the
Technical Depth 5 pts
programming language used.

Total Assessment Breakdown for PowerPoint and GUI-Based or Console-Based Application Rubrics:

Assessment Points Total Points

Seatwork 1 20pts
Seatwork 2 30pts
Quiz 1 20pts
Quiz 2 20pts
Task Performance 1 50pts
Task Performance 2 50pts
Total 100pts

INTE1024: Event-Driven Programming Course Instructor(s): Page 3 of 4

Final Examination AY 2024-2025 John Emmanuel L. Genoguin , Klent John Decena Juaniza , Joao Roumil Vergara, CpE
 Week/Day Date Group Member Name Assigned Role Tasks Completed Tasks Pending Challenges Faced Solutions Implemented

Weekly/Daily Report(starting from the 1st week/day of work until submission)

Example of roles:

 Project Manager  System Architect  Technical Writer  Documentation Specialist

 Lead Developer  Quality Assurance Tester  Researcher  Technical Support Specialist
 Front-End Developer  Version Control Manager  Systems Analyst
 Back-End Developer  Security Specialist  Application Support Specialist
 UI/UX Designer  Integration Specialist  Performance Tester

INTE1024: Event-Driven Programming Course Instructor(s): Page 4 of 4

Final Examination AY 2024-2025 John Emmanuel L. Genoguin , Klent John Decena Juaniza , Joao Roumil G. Vergara CpE