Chapter III Methodology

This chapter represents the Development Method, Gantt Chart and

Work Breakdown Structure (WBS) and the culmination of the Technical

Background, Project schedule, Budget Summary and System Design.

Development Method

The Agile approach was used for the methodology because it offers a

highly adaptable and iterative framework, which is essential for projects

requiring flexibility and continuous improvement. The proponents chose

Agile as it allows the team to develop, test, and deliver smaller,

independently functional components that are gradually combined to form

the final product. Additionally, the project will follow processes consistent

with the Agile methodology. This process provides frequent feedback,

enabling the team to track progress, address challenges early, and make

adjustments as needed to satisfy the client’s evolving requirements.

Planning. In the Planning phase, the project manager assembled a team of

four members to initiate the project. The proponents were tasked with

identifying at least three potential clients for the topic proposal defense. Once

potential clients were selected, the team sent request letters seeking approval

to conduct interviews. After receiving approvals, they gathered data through

interviews and questionnaires to understand client requirements. Among the

three clients, Alert-O: Emergency Alert Web Application for CDRRMO in

Calapan City was approved by the panel. Following the selection, the

proponents focused on Alert-O as the primary client. A formal request letter

was sent to the CDRRMO to gain permission for conducting the capstone

project. The team collected vital data on the Veterinary's processes and

challenges. This phase identified inefficiencies and assessed resources,

costs, and limitations, forming the foundation for the project's subsequent

phases.

Design. Once the requirements are defined, the developers begin creating

the system design based on the information provided by CDRRMO. During

the data analysis, the developers were particularly struck by the issues and

challenges related to the client records used by the department.. The data

analysis led them to consider processes and systems that could help address

these challenges. The system design aims to digitize and streamline the

management of these client records to improve efficiency while ensuring

compliance with regulations. The developers began creating various system

Diagrams, Data Flow Diagrams (Context Diagram 0, Diagram Level 1), Use

Case Diagrams, and a Sitemap, to provide a clear framework for system

implementation.

Additionally, the design phase includes creating the front-end interface for the

system. This involves defining the user interface (UI) and user experience

(UX), ensuring it is intuitive, user-friendly, and accessible to both clients and

administrators at CDRRMO. Key considerations include:

Front-End Development

1. Languages & Frameworks: Using HTML, CSS, JavaScript, Bootstrap,

and PHP for visual elements.

2. Responsive Design: Ensuring that pages adapt to various devices

and screen sizes.

3. UX Prioritization: Focusing on ease of use, accessibility, and clarity

with features such as real-time form validation and dropdown menus.

4. Prototype Development: Creating mockups and prototypes for

feedback from stakeholders like the ICT Coordinator and potential end

users.

Development. In the Development phase, the transition from conceptual

designs and requirements into a working system takes place. The

development team begins by establishing the system architecture, selecting

appropriate programming languages like HTML, JavaScript, and choosing

frameworks. The server environment and database management system

project.

Back-End Development

The back-end handles the server-side functionality, focusing on data

management, system logic processing, and ensuring smooth system

operation. Important components include:

● Server-Side Technologies: Frameworks like [Link], Django, or

Ruby on Rails are used to build the back-end logic. These technologies

support the functionality of the system, processing user inputs and

ensuring smooth communication with the front-end.

● Database Management: Database Management like MySql are used

to store, retrieve, and query data, such as school forms, user accounts,

and other records. Developers focus on data integrity, performance,

and security.

● APIs & Communication: APIs facilitate the interaction between the

front-end and back-end, ensuring that form submissions, data retrieval,

and report generation are handled efficiently.

● Security Features: Secure data handling is crucial, so encryption and

secure authentication mechanisms are implemented to protect

sensitive information. Role-based access control ensures that only

authorized users can access specific data.

By combining the front-end and back-end development efforts, the goal is to

create a functional, efficient, and secure system that effectively addresses the
challenges at CDRRMO, improving record management, data access, and

overall efficiency.

Testing. Before conducting testing, the team developed test cases to make

informed decisions and improvements of the system. These test cases

outlined specific scenarios, expected outcomes, and criteria for determining

success or failure, serving as a crucial guide during the testing phase. The

Testing phase ensured the system's reliability, usability, and security before

deployment. Unit testing was performed on individual modules, such as form

management and user authentication, to validate their functionality under both

expected and edge-case scenarios. Integration testing followed, focusing on

the interaction between the front end, back end, and database to verify

seamless data flow and consistent performance. System testing was

conducted to evaluate the entire system's functionality and to confirm it met

the defined requirements, including stress tests to assess its behavior under

high usage.

User testing involved clients and administrator at City Health, whose feedback

on the system's features and interface design played a key role in refining the

user experience. Lastly, security testing included penetration tests to identify

potential vulnerabilities, ensuring robust protection through encryption, secure

authentication, and role-based access controls. This rigorous and systematic

testing process ensured that the system was fully functional, secure, and

ready for deployment.

ensuring it was fully operational and ready for use. This phase included a

structured process to facilitate a smooth transition, incorporating user training,

release management, and system roll-out. Training sessions were conducted

to equip teachers, administrators, and other stakeholders with the knowledge

and skills needed to navigate the system effectively. These sessions focused

on key tasks such as managing records, generating reports, and

troubleshooting basic issues, ensuring users could confidently utilize the

system.

Release management played a critical role in the deployment, with a

controlled strategy implemented to ensure all components were thoroughly

tested and validated before going live. This included version control to track

updates, bug fixes, and enhancements, reducing the risk of errors during

implementation. Additionally, the system was installed and configured within

the school’s infrastructure, integrating the database, back-end, and front-end

components to enable seamless functionality. By addressing these critical

aspects, the deployment phase ensured a successful system launch, paving

the way for improved management at CDRRMO.

Review. The Review phase focused on evaluating the system's overall

performance and its impact on CDRRMO’s operations. Feedback was

gathered from clients and administrator to identify areas for improvement. Key

performance metrics, including efficiency, error rates, and user satisfaction,

were analyzed to assess the system's effectiveness. Based on the collected

adjustments to optimize the system, enhancing both its functionality and user

experience.

Launch. The Launch phase marked the official implementation of the system

at CDRRMO. During the formal rollout, the fully optimized system was made

accessible to all users, with operational support in place to ensure a smooth

transition. Continuous monitoring was conducted to track system performance

and address any issues in real time. Additionally, a comprehensive post-

launch support plan was established to assist users and ensure the system's

sustainability, successfully concluding the project.