System Direction

The proposed system will be a web-based company website and applicant management
system for PIGEM Combined Facilities Support Services. It will have two sides:

External/Public Side
This side is for visitors and applicants. Visitors can view the company profile, services,
contact information, announcements, and available internet/telecom application options.
They can also apply online by filling out a structured application form, uploading
requirements, and giving consent for data processing.

Internal/Admin Side
This side is for the administrator only. The admin can manage website content, view
dashboard statistics, manage applications, review uploaded documents, update application
status, generate reports, manage notifications, change light/dark mode settings, and update
website assets such as logos, icons, banners, and images.

For Capstone Project 1, the base system should focus on the website, CMS, application
management, dashboard, reports, utilities, and database foundation. The advanced AI
features such as AI live assistant, OCR/IDP, automated scoring, IP intelligence, and deeper
automation can be included in the paper as proposed innovation, then developed further in
Capstone Project 2.

Scope and Limitations

Scope

The proposed system, titled Automated Applicant Screening System for PIGEM Combined
Facilities Support Services, is a web-based platform designed to support the company’s
online presence and improve the early-stage management of telecom service applications.
The system will provide a public website for visitors and applicants, and an internal
administrative system for authorized personnel.

The general purpose of the system is to help PIGEM present its company profile, services,
and application process online while allowing administrators to manage submitted
applications in a more organized and efficient manner. The target users of the system are
website visitors, telecom service applicants, and the company administrator. The study will
be conducted within the development period of Capstone Project 1 and will focus on
producing the proposal documentation and a functional base system prototype.

The proposed system will include the following modules:

A. Public Website Module

1. Home Page
This module displays the company’s main landing page, including the company name,
banner, short introduction, call-to-action buttons, featured services, and basic application
instructions.

2. Company Profile Module

This module presents information about PIGEM Combined Facilities Support Services,
including the company background, mission, vision, services, and contact details.

3. Services and Plans Module

This module displays the available telecom or internet-related services that applicants may
view before applying. The content will be manageable by the administrator through the
internal content management system.

4. Online Application Module

This module allows visitors to submit an online application by providing personal

information, contact details, address details, selected plan or service, uploaded documents,
and privacy consent. The application form will be based on typical telecom application
requirements such as plan selection, personal details, ID type, ID number, front and back ID
photo, selfie with ID, contact details, address, landmark, declaration, and consent, which are
also reflected in the RED Fiber application reference you uploaded .

5. Contact and Inquiry Module

This module allows visitors to view company contact information and send inquiries through
a simple contact form.

6. Privacy Consent and Declaration Module

This module displays a privacy notice, applicant declaration, and consent checkbox before
application submission. Since the system will collect personal information and document
images, consent must be clear, specific, and recorded electronically. The National Privacy
Commission defines consent as a freely given, specific, and informed indication of will, which
may be evidenced through written, electronic, or recorded means .

B. Admin Dashboard Module

1. Overview Dashboard

This module displays summary cards and graphs, such as total applications, pending
applications, applications needing correction, flagged applications, and recently submitted
applications. [Link] may be used for simple dashboard graphs because it is a simple and
flexible JavaScript charting library for modern web dashboards .

2. Application Management
This module allows the administrator to view, search, filter, and manage submitted
applications.

Sub-options:

 Application Queue

 Applicant Records

 Document Review

 Screening Results

 Status Updates

 Remarks and Correction Requests

3. Content Management System

This module allows the administrator to update selected website content without editing
the source code.

Sub-options:

 Home Page Content

 Company Profile Content

 Services and Plans

 Announcements

 FAQs

 Contact Information

 Website Assets

4. Reports Management

This module provides basic reports that help the administrator monitor applications and
system activity.

Sub-options:

 Applicant List Report

 Application Status Report

 Screening Summary Report

 Admin Activity Report

5. Utilities
This module contains support features for system settings and maintenance.

Sub-options:

 Admin Account Settings

 Light Mode and Dark Mode

 Notification Settings

 Audit Trail

 Backup and Restore

 Privacy Notice Settings

 System Preferences

C. Base Screening Module

For the 50% system prototype, the screening process will be rule-based and simple. The
system will check whether required fields are completed, required documents are uploaded,
the applicant has accepted the privacy consent, and duplicate records may exist based on
email, mobile number, or ID number.

For Capstone Project 2, this module can be improved with AI-assisted screening, OCR,
Intelligent Document Processing, and automated applicant classification. The Gemini API can
later be used through REST requests for AI-assisted review, structured responses, and
applicant guidance, since the official Gemini API supports prompt-to-response generation
through different language options and REST calls . [Link] may also be considered for
OCR because it is a JavaScript OCR library that supports text recognition from images and
can run in a browser or server environment .

Limitations

The study is limited to the development of a web-based company website and applicant pre-
screening management system for PIGEM Combined Facilities Support Services. It will not
perform final telecom account approval, official account activation, billing, payment
processing, installation scheduling, or full customer relationship management.

The system will have only two main roles: visitor/applicant and administrator. Visitors do
not need accounts to browse the website or submit applications. Administrators must log in
before accessing the internal dashboard.

The base system will use simple validation and rule-based screening only. AI-powered
conversation, OCR/IDP, automated credibility scoring, IP intelligence, and advanced
automation will be treated as planned innovation modules and may be fully implemented in
the next development phase.

The system will depend on internet access when deployed online. During Capstone Project
1, the prototype will be developed and tested locally using XAMPP localhost. XAMPP is
suitable for this because it is a free Apache distribution that includes MariaDB, PHP, and Perl
for local web development .

The system’s document validation will depend on the quality of uploaded files. Blurry,
cropped, unreadable, or incorrect documents may still require manual review.

The system will include privacy consent, but the proponents must still improve legal wording
and security measures before real-world deployment. The system is intended for academic
and prototype purposes unless further tested, secured, and approved by the client.

The IP/VPN idea should not be written as “bypassing blocks” in the capstone paper. For
academic and ethical framing, it should be described only as a possible future risk-detection
support feature, where IP location, unusual submissions, or repeated attempts may be used
as warning signals. It should not automatically reject applicants because VPNs, shared
networks, and dynamic IP addresses can produce false results.

Technologies to be Used

The system will use simple web technologies to keep the development realistic and
manageable.

Technology Purpose in the System

HTML Structure of public pages, forms, admin pages, and system layout

Styling, responsive design, light/dark mode, spacing, colors, and

CSS
layout

Form validation, dashboard interactions, theme switching,

JavaScript
notifications, dynamic UI behavior

Backend processing, form submission, admin login, CRUD

PHP
operations, file upload handling, reports

Database storage for applicants, admin accounts, website content,

MariaDB
assets, reports, and logs

XAMPP Local development environment for Apache, PHP, and MariaDB

phpMyAdmin Database management during development

[Link] Simple dashboard graphs and visual reports

Technology Purpose in the System

[Link] / OCR API Future OCR feature for reading uploaded IDs and documents

Gemini API Future AI assistant and automated pre-screening support

Google Antigravity / AI Development support only for planning, scaffolding, checking, and
Agents testing assistance

Visual Studio Code Main code editor

Web Browser Testing the public and admin sides

PHP is appropriate for this project because it is a general-purpose scripting language

especially suited to web development . MariaDB is also appropriate because it is an open-
source relational database that uses SQL for structured data storage . Google Antigravity can
be used only as a development support tool because it is described as an agent-first
development platform where agents can plan, execute, and verify coding tasks across the
editor, terminal, and browser . It should not replace the developers’ manual checking and
understanding of the code.

Resources

Hardware Resources

User Type Minimum Requirement Recommended Requirement

Developer Intel Core i3/Ryzen 3, 8GB RAM, Intel Core i5/Ryzen 5, 16GB
Laptop/Desktop 256GB SSD, Windows 10/11 RAM, 512GB SSD

Dual-core processor, 4GB RAM, Core i3 or higher, 8GB RAM,

Admin Device
modern browser stable browser

Visitor/Applicant Smartphone with camera and

Smartphone or desktop browser
Device stable internet

Required for online access and API Stable broadband or mobile

Internet Connection
testing data

External backup or cloud

Storage Local storage for uploaded test files
backup for project files

Software Resources
Software Purpose

XAMPP Local Apache, PHP, and MariaDB server

Visual Studio Code Code editor

Google Chrome / Microsoft Edge Browser testing

phpMyAdmin Database creation and table management

Microsoft Word Capstone documentation

Microsoft Excel Tables, testing logs, and reports

Microsoft PowerPoint Proposal defense presentation

Google Antigravity AI-assisted development support

Git/GitHub Optional version control and backup

Canva/Figma Optional UI mockups and placeholder assets

Requirements Analysis

Who

The people involved in the system are the visitors/applicants, the PIGEM administrator, the
company representative or sales manager, and the proponents/developers. Visitors use the
public website to learn about the company and submit applications. The administrator
manages applications, website content, reports, notifications, and system settings. The
company representative benefits from faster access to organized applicant information. The
proponents design, develop, test, and document the system.

What

The business activity covered by the system is the online presentation of PIGEM services and
the early-stage collection, organization, and screening of telecom service applications. The
system will reduce scattered manual collection of applicant information and provide an
organized application queue for administrative review.

Where

The system will be developed first on a local XAMPP localhost environment and can later be
deployed online. The public side can be accessed through a browser by visitors, while the
internal side can only be accessed by the administrator through a login page.

When
The system can be accessed anytime when the server is running. For the prototype, access is
limited to local testing. Application submission, admin review, content updates, and report
viewing can be performed in real time within the system.

How

In the current process, applications may be collected manually through messages, photos,
and third-party forms or portals. This creates possible issues such as incomplete details,
unclear documents, repeated encoding, and difficulty tracking application status. In the
proposed system, applicants will submit their information through a structured online form,
upload requirements, and accept the privacy notice before submission. The administrator
will then view applications in a centralized dashboard, check documents, update statuses,
and generate reports.

Requirements Documentation

Functional Requirements

Code Requirement Description

View Public Visitors can view the home page, company profile, services, FAQs,
FR-01
Website and contact information.

Submit Online
FR-02 Visitors can fill out and submit an online application form.
Application

Applicants can upload required documents such as ID photos and

FR-03 Upload Documents
supporting files.

Accept Privacy
FR-04 Applicants must accept the privacy notice before submission.
Consent

FR-05 Admin Login The administrator can securely log in to the internal system.

The administrator can view application totals, recent activities,

FR-06 View Dashboard
and graphs.

Manage
FR-07 The administrator can view, search, filter, and update applications.
Applications

The administrator can open uploaded files and mark them as

FR-08 Review Documents
valid, unclear, missing, or for verification.

The administrator can update statuses such as Pending, Needs

Update Application
FR-09 Correction, For Review, Flagged, Rejected, or Approved for
Status
Forwarding.
Code Requirement Description

Manage Website The administrator can update public website text, services, FAQs,
FR-10
Content and contact details.

The administrator can upload or replace logos, icons, banners, and

FR-11 Manage Assets
placeholder images.

The administrator can view applicant list, status summary,

FR-12 Generate Reports
screening summary, and activity reports.

The system can show admin notifications for new applications and
FR-13 Use Notifications
status updates.

Use Light/Dark
FR-14 The administrator can switch between light mode and dark mode.
Mode

FR-15 Audit Trail The system records important admin actions.

Backup and The system includes a simple backup and restore utility for
FR-16
Restore database/file safety.

Non-Functional Requirements

Code Requirement Description

NFR-
Usability The interface must be simple, readable, and easy to navigate.
01

NFR-
Responsiveness Public pages and forms must work on desktop and mobile browsers.
02

NFR- Admin passwords must be hashed, sessions must be protected, and

Security
03 inputs must be validated.

NFR- Applicant data must be collected only with consent and used only
Privacy
04 for application processing.

NFR-
Maintainability Code must be organized into simple folders and reusable PHP files.
05

NFR-
Reliability Required fields and uploaded files must be checked before saving.
06

NFR- Pages should load quickly using simple HTML, CSS, JS, PHP, and
Performance
07 optimized images.
Code Requirement Description

NFR-
Backup Data and uploaded files should have a backup option.
08

Storyboard / Screen List

Public Side Navigation

Main
Sub-options / Page Content
Navigation

Home Hero banner, company introduction, services preview, apply button

About PIGEM Company background, mission, vision, profile

Services Internet/telecom services, plans, service details

Plan selection, personal details, contact/address details, document upload,

Apply Online
privacy consent

FAQs Common questions about application and requirements

Contact Contact details, location, inquiry form

Admin Side Navigation

Main Navigation Sub-options

Overview Dashboard Summary cards, graphs, recent applications, notifications

Application Application Queue, Applicant Records, Document Review, Screening

Management Results, Status Updates

Content Home Content, Company Profile, Services/Plans, FAQs,

Management Announcements, Contact Details

Asset Management Logo, icons, banners, service images, placeholder images

Reports Applicant List, Status Report, Screening Report, Admin Activity Report

Admin Account, Notification Settings, Light/Dark Mode, Audit Trail,

Utilities
Backup/Restore, Privacy Settings

Design of Software, System, Product, and/or Processes

Development Methodology
The proponents will use the Waterfall Model because the project requires clear
documentation, defined requirements, system design, implementation, testing, and final
evaluation. This is suitable for Capstone Project 1 because the group must first complete the
proposal paper and prepare a base system before moving to more advanced development.

The phases will be:

1. Requirements Gathering – Identify client needs, users, modules, forms, reports, and
system limitations.

2. System Design – Prepare navigation structure, database design, page layout, process
flow, and module list.

3. Implementation – Develop the system using HTML, CSS, JavaScript, PHP, and
MariaDB.

4. Testing – Test forms, login, CRUD functions, uploads, reports, dashboard, and admin
actions.

5. Deployment Preparation – Prepare the local prototype, documentation, screenshots,

and defense materials.

6. Maintenance Planning – Identify improvements for Capstone Project 2, especially AI

and automation features.

System Architecture

The system will follow a simple three-layer web architecture:

Layer Description

Presentation HTML, CSS, and JavaScript pages for the public website and admin
Layer interface

PHP scripts for login, form processing, validation, CRUD, uploads, reports,
Application Layer
and settings

MariaDB database for applicants, content, assets, admin accounts, logs,

Data Layer
and reports

Suggested Database Tables

Table Purpose

admins Stores admin login credentials and profile

applicants Stores applicant personal, contact, and address information

applications Stores application details, selected plan, status, remarks, and

Table Purpose

timestamps

applicant_documents Stores uploaded file paths and document status

service_plans Stores telecom/internet services and plans

cms_pages Stores editable website page content

cms_assets Stores logos, icons, banners, and image paths

notifications Stores admin notifications

audit_logs Stores admin activity history

Stores system settings such as theme, contact email, and notification

settings
preferences

Asset Design

The system should not depend on HTML-generated logos or icons only. It should include an
assets folder and an admin asset management module.

Suggested folder structure:

/assets
/images
/placeholders
/logos
/banners
/services
/icons
/uploads
/documents
/cms
/admin
/public
/config
/includes

Default placeholder images should be used when no uploaded asset is available. When the
admin replaces a logo, banner, icon, or service image, the public website should
automatically display the updated asset.

Security and Privacy Design

The system should include password hashing, prepared SQL statements, server-side
validation, file type restrictions, session checking, and audit logs. Uploaded files should be
limited to allowed types such as JPG, PNG, and PDF. The application form should include a
privacy consent checkbox before submission because the system collects personal
information and document images. The Data Privacy Act regulates the collection, recording,
organization, storage, updating, retrieval, use, and destruction of personal data in the
Philippines .

Base Features for the 50% System

For Capstone Project 1, prioritize these features first:

1. Public home page

2. Company profile page

3. Services/plans page

4. Online application form

5. Document upload

6. Privacy consent checkbox

7. Admin login/logout

8. Admin dashboard summary cards

9. Application queue

10. Applicant details view

11. Status update feature

12. Basic CMS for public content

13. Asset upload/change feature

14. Basic reports

15. Audit trail

16. Light/dark mode

17. Notification settings placeholder

18. Backup/export database placeholder

The advanced features for Capstone Project 2 should be listed as planned innovation: AI live
assistant, OCR/IDP document reading, automated screening score, duplicate/suspicious
application detection, IP/location risk signal, email/SMS notifications, and stronger analytics.