GROUP 1

ICpEP.se - NwSSU Chapter Student Yearbook Management System A.Y. 2023-2024

WEEK 1 PROGRESS

AIM: To develop problem statements for a student yearbook management system.

Problem Statement:
The lack of a centralized digital platform also hinders collaboration and accessibility for
students, faculty, and staff involved in the yearbook production.

Therefore, the aim of the Yearbook Management System project is to develop a

comprehensive digital solution to streamline the creation, management, and distribution of
the student yearbook, addressing the following key challenges:

1. Manual Data Collection and Entry

2. Limited Collaboration and Accessibility
3. Inefficient Content Organization

Components:

 Problem/Challenge
1. Managing client expectations
 Solution and its implementation step
1. Client engangement and communication
 Next steps
1. Requirements Analysis and Documentation
2. Feasibility Study
3. Group/Team Alignment
4. Client validation

Roles:
 Admin (Administrative User)
System Administrator
Yearbook Coordinator
Content Moderator
 Client (End-User)
Student
Parent/Guardian
Alumni
 System (Technical Infrastructure)
Database Administrator
Developer
 Inputs (Data and Content Providers)
Photographer
Teacher/Staff
 Others
 GROUP 1
ICpEP.se - NwSSU Chapter Student Yearbook Management System A.Y. 2023-2024
WEEK 2 PROGRESS

AIM: How to find the related project or related research literature for student yearbook
management system?

Problem Statement:
In making student yearbook management system, it is important to search or to find the
related research literature/project of the project. This is what to achieve in finding good
sources of information needed:

1. Reliable Resources.
There are many resources is on the internet but it is hard to find a reliable one so it needs
to find the credibility of the information input there.

2. Chance of Improvements and Innovations.

In every research project it is expected that it has a specific limitation to what the project
can do in depends on what the researcher’s can do.

3. References.
It is more legit sources if the related research literature/project has a references or origin of
the information input in research.

4. Approved by Expert.
The research project sources is more legit if it is approved by a professionals, in that way
the source/project is being tested from those times that the research project was made.
 GROUP 1
ICpEP.se - NwSSU Chapter Student Yearbook Management System A.Y. 2023-2024
WEEK 3 PROGRESS

AIM: Preparation of Software Configuration Management and Student Yearbook

Management System.

Preparation of Software Configuration Management

 Forms basis for End User License Agreement (EULA).
 All the compatibilities of implementing the system can be known.

Software Requirements:
Operating System(OS) : Windows 10/11
Front End : HTML, CSS
Back End : My SQL Workbench
IDE used : Visual Studio Code
Language Used : Hypertext Preprocessor (PHP)

Hardware Requirements:
Processor : 11th Gen Intel(R) Core(TM) i5-1135G7 or Higher.
Ram : 8 GB
Hard Disk Drive : 256 GB
 GROUP 1
ICpEP.se - NwSSU Chapter Student Yearbook Management System A.Y. 2023-2024
WEEK 4 PROGRESS

AIM: Creation of the Flowchart for the Student Yearbook Management System.

Problem Statement: We need to develop a comprehensive flowchart to visualize the entire

process flow of Yearbook Management System works. This helps us understand how data
will be processed and managed within the system.

1. System Overview
- Identify the major components and modules of the Yearbook Management System.
- Define the relationship between different modules and their functionalities.

2. User Interaction
- Illustrate the interaction between end-users and the system.
- Define the user input/output processes for various system functionalities.

3. Data Flow
- Map out the flow of data within the system, from input to processing and storage.
- Identify data manipulation processes and data storage points.

4. Decision Points
- Identify decision points within the system and their corresponding conditions.
- Define the branching logic based on different conditions.

5. Error Handling
- Include how the system deals with errors or problems.

6. Integration
- Illustrate the integration of different software components and technologies within the
system architecture.
 GROUP 1
ICpEP.se - NwSSU Chapter Student Yearbook Management System A.Y. 2023-2024
WEEK 5 PROGRESS

Aim: To design a comprehensive student yearbook management system that facilitates

easy creation, editing, and distribution of yearbooks for educational institutions.

Target Audience:
- School administrators
- Yearbook committee members
- Students
- Parents

Features:
1. User Authentication and Authorization:
- Secure login for administrators, committee members, students, and parents.
- Role-based access control to ensure privacy and data security.

2. Dashboard:
- Personalized dashboards for each user role.
- Quick access to relevant features and statistics.

3. Yearbook Creation and Editing:

- Intuitive interface for designing yearbook pages.
- Drag-and-drop functionality for adding images, text, and other multimedia elements.
- Collaboration tools for multiple users to work on the same yearbook simultaneously.

4. Content Management:
- Ability to upload and organize photos, articles, and other content.
- Version control for tracking changes and revisions.

5. Feedback and Surveys:

- Tools for collecting feedback on yearbook drafts.
- Surveys to gather input from students and parents on yearbook content and design.

Sign up_table
Student Name (CHAR)(50)
Student ID (INT)(50)
Password (VARCHAR)(50)

Users_table
Student ID (INT)(50)
Password (VARCHAR)(50)
 GROUP 1
ICpEP.se - NwSSU Chapter Student Yearbook Management System A.Y. 2023-2024
WEEK 6 PROGRESS

Aim: To develop test cases for unit testing and integration testing.

Unit Testing Test Cases:

1. User Authentication:
- Test case 1: Verify that a valid username and password combination allows a user to log
in successfully.
- Test case 2: Verify that entering an invalid username or password results in a login
failure.
- Test case 3: Verify that the system rejects empty username or password fields.

2. Yearbook Creation:
- Test case 1: Verify that a new yearbook can be created successfully.
- Test case 2: Verify that adding a new page to a yearbook increments the total page
count.
- Test case 3: Verify that editing a page updates the page content correctly.

3. Content Management:
- Test case 1: Verify that images can be uploaded and associated with specific pages.
- Test case 2: Verify that text content can be added, edited, and formatted within a page.
- Test case 3: Verify that deleting a page removes all associated content and updates the
page count accordingly.

Integration Testing Test Cases:

1. User Authentication and Authorization:
- Test case 1: Verify that only authenticated users can access restricted features such as
editing yearbooks or managing events.
- Test case 2: Verify that user roles are enforced correctly, with administrators having
access to all features and students/parents having limited access.

2. Yearbook Creation and Content Management:

- Test case 1: Verify that changes made to yearbook content by one user are reflected for
other users viewing the same yearbook.
- Test case 2: Verify that uploading images or adding text content updates the database
correctly and displays the content on the appropriate pages.
- Test case 3: Verify that concurrent editing by multiple users does not result in data
conflicts or loss of changes.

These test cases cover a range of functionalities and scenarios to ensure that the student
yearbook management system operates smoothly and meets the requirements of all
stakeholders.