Guidelines for Computer Programming 2 and Fundamental of Database Project

As the culminating requirement for the Computer Programming 2 and Fundamental of Database
course, students are entrusted with the task of conceptualizing, developing, and executing a
Database System tailored for a company or startup organization. This project places particular
emphasis on refining skills in database design, modeling, and the practical application of SQL
using MySQL/MariaDB-MySQL.
The project encompasses the following components:

 Project Report
 Project Output
 Project Presentation
1. Project Report
The project report serves to articulate the concept behind your proposal, its relevance, and the
comprehensive study supporting your proposal case. The report adheres to the APA style format
and comprises the following outline:
Title Page - Includes the title of the proposed system and the names of team members.
Table of Contents
Chapter 1. Introduction
The introduction sets the context for your project, offering background information, the
purpose of the database, and its significance. Provides an overview of the context in
which the database will operate. Explain the necessity for the database and its intended
improvements over existing systems or processes.
Objectives - Outlines the specific goals and objectives of the database project,
elucidating the problems it aims to solve and the benefits it will deliver to users or
stakeholders.

Scope and Limitation - Defines the scope of the project, including intended users, data
to be stored, and functionality to be implemented. Highlights any limitations or
constraints impacting the project.
Chapter 2. Database Design
This section showcases the design of the database, encompassing its structure, tables,
relationships, and normalization.
Entity-Relationship Diagram (ERD) - Presents an ERD to visually represent the
entities, attributes, and relationships in the database schema. Expounds on the rationale
behind the design choices.
Database Schema - Provides a detailed description of each table in the database
schema, including its purpose, primary keys, foreign keys, and attributes. Discusses any
constraints or rules applied to the data.
 Normalization - Explains the normalization process employed to minimize redundancy
and enhance data integrity. Discusses the attained normal forms and any trade-offs
made during normalization.
Data Dictionary - The data dictionary serves as a comprehensive reference for all
elements of the database schema.
Chapter 3. GUI Design
This section explains the design of the graphical user interface (GUI) for interacting with the
database.
User Interface Components - Identifies various GUI components such as forms,
menus, buttons, and reports. Describes their functionalities and how they facilitate
interaction with the database.
Mockups or Wireframes - Includes mockups or wireframes of the GUI to illustrate
layout, navigation flow, and visual design. Explains any applied user interface principles
or design patterns.
Chapter 4. Conclusion
The conclusion encapsulates key findings, challenges, and lessons learned from the database
project.
References

List any external resources, books, websites, or papers referenced during the project.

Fonts

Title: Arial Black, 16pt

Members List: Arial Black, 14pt
Headings: Arial Black, 12pt
Body Text: Arial,12pt

Paper: Letter

Margins:

Top and Bottom Margins: 1 inch (2.54 cm) each.

Left and Right Margins: 1 inch (2.54 cm) each.

2. Project Output

Compile all components of the project output, including the actual running system, database
design documentation, and testing results, into a google drive and provide the link for checking.
3. Project Presentation

 Prepare a 10–15-minute presentation that provides an overview of the project, including

objectives, design, implementation, and outcomes.
 Organize the presentation into logical sections, such as introduction, database design,
GUI design, and conclusion.
 Begin with an introduction to the project, providing background information, objectives,
and scope.
 Present the database design, including entity-relationship diagrams, schema
descriptions, and normalization process.
 Showcase the implemented database system, highlighting key features, functionalities,
and data population.
 Demonstrate the testing and validation process, discussing any challenges encountered
and how they were addressed.
 Conclude the presentation with a summary of achievements, lessons learned, and future
directions for the project.

Project Report Rubrics

Criteria Excellent (4) Good (3) Fair (2) Needs
Improvement (1)
Introduction - Clearly sets the stage - Provides - Offers some - Lacks
for the project, adequate background comprehensive
providing background information, background
comprehensive information, purpose, and information,
background purpose, and significance of the purpose, and
information, purpose, significance of the project. - Articulates significance of the
and significance. - project. - Articulates the objectives of the project. - Unclear
Clearly articulates the the objectives of database project to or missing
objectives of the the database some extent. - objectives of the
database project. - project. - Defines Defines the scope, database project. -
Defines the scope with the scope but lacks clarity in Scope is poorly
clarity and precision. adequately. some aspects. defined.
Database - Presents a well- - Presents an ERD - Presents an ERD - ERD lacks clarity
Design developed ERD with with clear entities, with some clarity but or is missing. -
clear entities, attributes, and may lack detail in Description of the
attributes, and relationships. - entities, attributes, database schema
relationships. - Provides a or relationships. - is unclear or
Provides a thorough description of the Provides a incomplete. -
description of the database schema, description of the Explanation of
database schema, including primary database schema, normalization
including primary keys, keys, foreign keys, but may lack process and
foreign keys, and and attributes. - completeness or achieved normal
attributes. - Offers a Explains the clarity. - Offers a forms is
detailed explanation of normalization basic explanation of inadequate or
the normalization process and the normalization missing.
process and achieved achieved normal process and
normal forms. forms adequately. achieved normal
forms.
GUI Design - Presents a well- - Presents a GUI - Presents a GUI - GUI lacks clarity
designed GUI with with clear with some clarity but or is missing. -
 clear components, components, may lack detail in Mockups or
layout, and navigation layout, and components, layout, wireframes are
flow. - Provides navigation flow. - or navigation flow. - unclear or
detailed mockups or Includes mockups Includes mockups incomplete. -
wireframes illustrating or wireframes or wireframes but Discussion of UX
the GUI design. - illustrating the GUI may lack considerations is
Discusses UX design. - Discusses completeness or inadequate or
considerations UX considerations clarity. - Discusses missing.
comprehensively. adequately. UX considerations
briefly.
Conclusion - Provides a - Provides a - Provides a basic - Summary of
comprehensive summary of summary of achievements,
summary of achievements, achievements, challenges, and
achievements, challenges, and challenges, and lessons learned is
challenges, and lessons learned. - lessons learned. - inadequate or
lessons learned. - Offers reflections Offers limited missing. - Lacks
Offers insightful on the project. - reflections on the reflections on the
reflections on the Mentions future project. - Mentions project. - Future
project. - Outlines clear directions for the future directions directions are
future directions for the project. briefly. unclear or missing.
project.

Project Output Rubric:

Criteria Excellent (4) Good (3) Fair (2) Needs
Improvement (1)
Database - Implements a fully - Implements a - Implements a - Implements a
Implementation functional database database system database system database system
system that meets that mostly meets with some with significant
all specified specified deficiencies in deficiencies in
requirements. - requirements. - meeting specified meeting specified
Demonstrates Demonstrates requirements. - requirements. -
proficiency in SQL competency in SQL Demonstrates Demonstrates
and database and database basic limited
management. management. understanding of understanding of
SQL and database SQL and database
management. management.
Data Integrity - Ensures data - Maintains data - Demonstrates - Lacks effective
integrity through integrity through the some efforts measures for
appropriate use of use of primary towards maintaining data
primary keys, keys, foreign keys, maintaining data integrity. - Data
foreign keys, and and normalization integrity but may validation is
normalization techniques. - have some inadequate or
techniques. - Implements basic deficiencies. - missing.
Handles data data validation. Limited data
validation validation
effectively. implemented.
Documentation - Provides - Provides - Provides basic - Documentation is
comprehensive documentation for documentation for inadequate or
documentation for the database the database missing. - Lacks
 the database system, including system but may clarity or
system, including schemas, scripts, lack completeness organization.
schemas, scripts, and user manuals. - or clarity. -
and user manuals. - Documentation is Documentation
Documentation is clear and organized may lack
clear, organized, but may lack some organization.
and well-structured. detail or structure.

Project Presentation Rubric:

Criteria Excellent (4) Good (3) Fair (2) Needs
Improvement (1)
Content - Presents clear and - Presents information - Presents - Presents
concise information about the project information about information about
about the project, adequately, covering the project but may the project
including objectives, objectives, design, lack clarity or detail unclearly or
design, implementation, and in some areas. - inadequately. -
implementation, and outcomes. - Demonstrates Demonstrates lack
outcomes. - Demonstrates good basic of understanding
Demonstrates in- understanding of the understanding of of the subject
depth knowledge of subject matter. the subject matter. matter.
the subject matter.
Organizatio - Organizes the - Organizes the - Organizes the - Presentation
n presentation logically presentation presentation but lacks organization
with clear transitions reasonably well with may lack clear and clear
between topics. - some transitions transitions transitions
Uses visual aids between topics. - between topics. - between topics. -
effectively to enhance Visual aids are used Visual aids may be Visual aids are
understanding. adequately. underutilized or missing or
lacking. ineffective.
Delivery - Delivers the - Delivers the - Delivers the - Delivery of the
presentation presentation with presentation but presentation is
confidently and confidence and may lack unclear or lacking
articulately. - Engages clarity. - Engages the confidence or confidence. - Fails
the audience audience adequately. clarity in delivery. - to engage the
effectively through Audience audience
verbal and non-verbal engagement is effectively.
communication. limited.