A final requirement in Software Engineering I

EasyBoard: A Web-based Boarding House Finder

Licatan, Neil Humprey

Daligdig, Shaneya Alyssandra

Ferenal, April Joy

Agrabio, Joshua Romer

Bachelor of Science in Computer Science

December 2024
Executive Summary

Students moving to new cities often struggle to find safe, affordable, and

verified boarding houses, relying on unreliable word-of-mouth or unverified online

posts. This leads to risks like unsafe living conditions, fraud, and inefficiency. The

lack of a unified, trustworthy platform with verified listings and reviews makes the

process stressful and time-consuming.

The solution is an online platform that centralizes verified boarding house listings

with real-time availability, prices, and location filters. A ratings and review system

will help students make informed decisions, streamlining the search for safe and

affordable accommodation.

Determining the Scope:

A. Target Users and Key Features

1. Boarding House Owners: Owners will be able to list and manage their

properties efficiently, including updating availability, pricing, and

property details.

2. Students: Students will have access to a user-friendly platform to

browse listings, filter by criteria such as price, location, and availability,

and contact owners directly.

The platform will focus on the following key features:

● Initial Listings: Listings will be added by owners without verification in

the initial phase, allowing for quick onboarding and feedback from

users.
 ● Real-Time Availability: Students will see up-to-date information on

room availability and pricing.

● Advanced Filters: Students can search based on specific criteria like

budget, proximity to universities, or amenities.

● Reviews and Ratings: A review system will allow students to leave

feedback, helping others make informed decisions based on previous

tenant experiences.

While owner verification is planned for a later phase, the initial version will

prioritize ease of use and fast access to listings. Future updates may include

features such as booking systems, payment gateways, and enhanced security

measures like owner verification.

B. Geographical Consideration

Currently, the project scope is limited to the Municipality of Kabacan, with the

potential for expansion to multiple municipalities or cities in the future as support and

resources allow.

Project Objectives:

1. To create a centralized platform that gives easy-to-use searching and finding

boarding houses for students moving to new cities.

2. Include providing management tools for the owners, communication between

students and owners through given contacts in the description, forming trust

through rating and review system, and ensuring scalability for future

enhancements, with the focus on meeting key business and technical needs.
Problem Statement

The project seeks to address the struggle of students in finding boarding

houses when they move to a new city or area, including the stressful and time-

consuming process in looking for safe, affordable, and verified boarding houses. This

solution will help students find and select boarding houses that are suitable for them

based on the app’s features that include reviews, descriptions, location, and pictures

to reduce the amount of time and effort required to secure accommodation.

Requirements

Functional Requirements

1. User Accounts:

a. Owners: can create accounts, list properties, and update

availability, pricing, and details.

b. Students: can browse listings, filter by criteria (price, location),

and contact owners without needing to log in.

2. Property Listings:

a. Owners can add basic information (price, location, features) and

upload photos.

b. Listings show real-time availability and pricing.

3. Search and Filters:

a. Students can filter listings by price, location, and availability.

4. Reviews and Ratings:

a. Students can leave reviews and ratings after staying at a

property.
 Non-functional Requirements

1. The platform must be secure, protecting user data.

2. The system should support fast searches, even with large numbers of

boarding houses.

3. Mobile-friendliness is crucial for student access (responsiveness).

User Requirements

1. For Students:

○ Efficient Search: Ability to browse and filter boarding house listings by

price, location, availability, and amenities.

○ Real-Time Information: Access updated availability, pricing, and

property details to make quick and informed decisions.

○ User Reviews: View and submit reviews and ratings for properties to

ensure informed choices.

○ Direct Communication: Contact boarding house owners directly without

needing to create an account.

2. For Boarding House Owners:

○ Property Management: List, update, and manage property details,

availability, and pricing.

○ Efficient Interaction: Communicate directly with potential tenants via

integrated messaging features.

○ Listing Flexibility: Add and edit property details, including photos and

amenities, with ease.

In-Scope Activities

1. Design

○ Development of a user-friendly interface for both students and boarding

house owners.

○ Integration of responsive UI/UX elements to ensure mobile

accessibility.

○ Wireframes and prototypes for key pages (e.g., sign-up, login, property

listings).

2. Development

○ Backend development using PHP and MySQL for database

management.

○ Integration of real-time availability and pricing updates for property

listings.

○ Google Maps API integration for location-based searches and map

display.

3. Testing

○ Functional testing to ensure key features like filtering, reviews, and

real-time availability work as intended.

○ Mobile compatibility testing across devices.

○ Performance testing to optimize AJAX calls, minimize load times, and

ensure scalability.
 4. Launch and Feedback Collection

○ Deployment on a scalable server like VPS or AWS.

○ Gathering of user feedback during the initial launch for future updates.

Out-of-Scope Activities

● Owner verification processes for property listings.

● Advanced booking systems or payment gateway integrations.

● Offline support for property management and student searches.

Constraints

1. Budget: Limited budget allocation for initial development and hosting services.

2. Time: The project follows a 12-week timeline, with key milestones like

planning (1 - 2 weeks), system design and development (3 - 10 weeks),

testing and launch (11 - 12 weeks).

3. Resources: The project team will use predefined technologies like PHP,

MySQL, and Google Maps API, with Initial focus on unverified listings to

ensure quick launch.

Methodology

The project will follow the Agile methodology, emphasizing iterative development and

continuous feedback to ensure a user-centric and adaptable product.

Technologies to Be Used:

● Frontend:

○ HTML, JavaScript, and AJAX for responsive and dynamic user

interfaces.
 ○ CSS/Bootstrap for mobile-friendly design and consistent styling.

● Backend:

○ PHP for server-side logic and data processing.

○ MySQL for database management.

● APIs and Integrations:

○ Google Maps API for location-based searches and property display on

a map.

Quality Assurance:

● Unit Testing:

○ Testing of individual features and components, such as the search filter

or login system, to ensure functionality meets specifications.

● Integration Testing:

○ Verifying the seamless interaction between modules, such as data

retrieval from the database for property listings and their display on the

frontend.

● User Acceptance Testing (UAT):

○ Feedback will be gathered from a group of target users (students and

property owners) to validate usability and effectiveness.

● Performance Testing:

○ Focus on fast load times and smooth navigation, especially for mobile

devices.

● Security Testing:

○ Implement HTTPS and SQL injection prevention measures.

The Agile workflow will include:

● Sprints: Each sprint (1-2 weeks) will focus on specific tasks such as building

the search functionality or integrating the Google Maps API.

● Daily Standups: Regular meetings to assess progress and address

challenges.

● Sprint Reviews: Presenting completed features to stakeholders for feedback

and improvement.

● Retrospectives: Reflecting on completed work to identify opportunities for

optimization in subsequent sprints.

Project Plan Schedule and Key Milestones (21 Weeks)

1. Planning and Requirements Gathering (Weeks 1-3):

● Week 1:

○ Identify project objectives, scope, and deliverables.

○ Stakeholder meetings to define high-level goals and expectations.

● Week 2:

○ Conduct user research to understand local needs and preferences.

○ Define user personas and key features.

○ Finalize technology stack, tools, and platforms.

● Week 3:

○ Develop detailed project requirements and a feature roadmap.

○ Create a timeline for development and testing phases.

● Week 4:

○ Design UI/UX wireframes and mockups for key user flows.

○ Develop initial design concepts and iterate based on feedback.

● Week 5:

○ Finalize UI/UX designs and get approval.

○ Design system architecture and database schema.

○ Define data models, APIs, and security protocols.

● Week 6:

○ Review and refine the system design.

○ Finalize project documentation for development and testing.

3. Development and Testing (Weeks 7-15):

● Weeks 7-9:

○ Develop core features: property listings, search filters, and Google

Maps integration.

○ Implement the review system and basic user account management.

○ Set up the backend (database, API, server environment).

● Weeks 10-12:

○ Implement additional features like notifications, user preferences, and

admin panel.

○ Conduct unit testing for each feature as it’s developed.

○ Begin integration testing of components.

● Weeks 13-15:

○ Optimize platform performance (loading times, responsiveness).

usage.

○ Implement security measures and test them (authentication, data

encryption, etc.).

○ Perform end-to-end system testing and bug fixing.

4. User Acceptance Testing (UAT) and Launch Preparation (Weeks 16-18):

● Week 16:

○ Prepare for UAT by setting up test cases and environments.

○ Invite a group of local users for feedback on features, usability, and

design.

○ Analyze feedback from UAT and prioritize fixes/enhancements.

● Week 17:

○ Address any major issues from UAT.

○ Continue fixing bugs and refining the user experience.

● Week 18:

○ Finalize preparations for deployment (server configuration, backups,

monitoring tools).

○ Conduct a final round of internal testing.

5. Launch and Feedback Collection (Weeks 19-21):

● Week 19:

○ Deploy the platform to a VPS or AWS server.

○ Ensure all monitoring tools are set up (analytics, error tracking).

○ Soft launch to a small group of users within Kabacan for final feedback.

○
 ● Week 20:

○ Full launch of the platform for users in Kabacan.

○ Monitor performance, fix any immediate bugs or issues.

○ Gather feedback from users regarding functionality and overall

experience.

● Week 21:

○ Analyze collected feedback and identify areas for improvement.

○ Plan for future iterations based on user feedback.

○ Conduct post-launch review with stakeholders and plan for the next

phase of development.

Resources Required

● Team:

○ Project Manager to oversee progress and ensure milestones are met.

○ Developers (frontend and backend) to build the platform.

○ UX/UI Designer to create user-friendly interfaces.

○ QA Specialist for testing and quality assurance.

● Tools:

○ Development: Visual Studio Code, PHP, MySQL, AJAX, Bootstrap.

○ Testing: Browser developer tools, SQL testing tools, and debugging

software.

○ Hosting: VPS or AWS services.

○ APIs: OpenStreetMaps

○ Design: Figma

●
 ● Budget:

○ Hosting costs for initial deployment.

○ API costs for Google Maps (limited usage initially).

○ Miscellaneous expenses for tools and testing resources.

○ Contingency for unforeseen development or design costs.

Timeframe

The project is scheduled to be completed within 21 weeks, with a buffer for

addressing unforeseen challenges during deployment or testing.

Risk Management

1. Unverified Listings Leading to Misinformation

○ Risk:

■ Allowing property owners to add listings without verification in

the initial phase might result in inaccurate or misleading

information.

○ Mitigation Strategy:

■ Implement a user reporting system for fraudulent or inaccurate

listings.

■ Plan an owner verification feature for future updates.

■ Implement HTTPS for secure data transmission.

2. Technical Performance Issues

○ Risk:

■ Slow system response times as the number of listings

increases.

○
 ○ Mitigation Strategy:

■ Optimize AJAX calls for faster data retrieval.

■ Optimize MySQL queries for efficiency.

■ Use caching mechanisms for frequently accessed data.

■ Conduct regular performance testing and load testing.

3. Limited User Adoption

○ Risk:

■ Students and property owners may not initially use the platform

due to lack of awareness or perceived complexity.

○ Mitigation Strategy:

■ Start with unverified listings to onboard owners quickly.

■ Conduct promotional activities targeting students in the

Municipality of Kabacan.

■ Collect feedback post-launch to improve user experience and

address barriers to adoption.

4. Security Threats

○ Risk:

■ User data may be compromised due to vulnerabilities in the

system.

○ Mitigation Strategy:

■ Use prepared SQL statements to prevent SQL injection.

■ Implement HTTPS for secure data transmission.

■ Plan an upgrade to stronger password hashing algorithms, such

as bcrypt, in future phases.

● Unverified Listings: If fraudulent listings persist, prioritize developing the

owner verification system sooner than planned.

● Technical Issues: Migrate to more robust servers or cloud solutions as the

user base grows.

● Low User Adoption: Collaborate with educational institutions to promote the

platform among students and landlords.

● Security Breaches: Regularly update security protocols and engage a third-

party security audit if vulnerabilities arise.

Stakeholder Analysis

Stakeholders:

● Sponsors: Provide funding, set project priorities, and ensure

resources are available for scaling the platform.

● End-Users: Students looking for safe, affordable, and verified boarding

houses, and property owners seeking tenants.

● Development Team: Responsible for the design, development, and

testing of the platform, ensuring functionality and user experience.

● Boarding House Owners: Provide property listings, manage

availability, and interact with students on the platform.

● Project Manager: Oversees project milestones, ensures the platform

meets deadlines, manages the budget, and ensures communication

across teams.
 ● Universities/Educational Institutions (Potential Partners): Could

promote the platform to students or partners for better service

integration.

Communication Plan

● Weekly Progress Meetings with Sponsors: Provide updates on

development, discuss upcoming milestones, and adjust priorities if

necessary.

● Regular Updates to End-Users: Use newsletters, in-app notifications,

or email to keep students informed about new listings, platform

features, and improvements.

● Agile Standups for the Development Team: Daily or bi-weekly

briefings to assess progress, resolve blockers, and adjust development

strategies for quicker turnarounds.

● User Feedback Channels: Post-launch, incorporate user reviews and

surveys to gather insights into platform performance and areas for

improvement.

Expected Outcomes and Benefits

Outcomes:

● A user-friendly online platform that allows students to efficiently search

for verified boarding houses with real-time availability and accurate

property details.

● A scalable architecture that supports future growth, including features

like owner verification, booking systems, and payment integration.

owners, enabling direct inquiries and bookings.

Benefits:

● Increased user satisfaction through a centralized, trustworthy platform

with reliable listings and an easy-to-navigate interface.

● Enhanced trust and safety for students, reducing the risks of fraud or

unsafe accommodations through verified reviews and ratings.

● Better property management for owners, allowing them to efficiently

manage listings, update availability, and communicate with potential

tenants.

Success Criteria:

● High adoption rates among students and property owners, with measurable

increases in platform usage.

● Shortened search-to-decision time for students, reducing the time spent

browsing and inquiring about properties.

● Positive user feedback through surveys, reviews, and platform engagement

metrics, reflecting a high level of satisfaction with the platform's usability and

features.

● System reliability with a focus on uptime, fast response times, and smooth

interactions during property searches and inquiries.

The EasyBoard platform addresses the challenges faced by students in

securing reliable accommodation and helps property owners manage listings more

efficiently. By providing a central hub for verified, real-time boarding house data, the

platform enhances both the housing search experience and the property

management process. Successful implementation will drive greater convenience,

trust, and scalability, benefiting all stakeholders—students, property owners, and

universities—while positioning the platform for future growth and innovation in the

accommodation sector.