Chapter 4
Last updated
Last updated
Methodology, Results, and Discussions
This chapter presents the testing and implementation results of the system, detailing the processes conducted to ensure functionality, usability, and reliability for users. It includes testing methodologies, performance evaluations, and user feedback, highlighting how Clucash improves item organization, facilitates transactions, and enhances the overall decluttering experience. The findings also provide insights into areas for improvement and future enhancements to optimize the system’s effectiveness.
Clucash is a platform designed to help users efficiently manage household clutter by providing tools for tracking, organizing, and selling unwanted items. The system streamlines the process by enabling suppliers to list items, shop owners to acquire and resell them, and buyers to browse and purchase available products. By integrating inventory management with selling options such as fixed pricing and auctions, Clucash offers a structured approach to decluttering while ensuring that items find new use rather than being discarded.
The implementation phase of Clucash involved rigorous testing to verify its core functionalities. Various testing methodologies, including unit testing, integration testing, system testing, and user acceptance testing, were conducted to ensure reliability and ease of use. These tests assessed system performance, user interaction, and data accuracy, ensuring that Clucash meets its intended objectives. The results provide a clear evaluation of the system’s effectiveness in reducing clutter, simplifying the listing process, and expanding selling options. Additionally, challenges encountered during testing and potential areas for improvement are discussed to refine the platform further.
Requirements Analysis
Figure 4.1 illustrates the process of adding and reviewing items in the inventory system. The supplier initiates the process by offering an item, which is recorded in the inventory under the "Offering an Item" stage (4.1). The system then generates an offer, which moves to the "Reviewing Offered Item" stage (4.2), where the shop owner evaluates the item details. The shop owner decides whether to accept or reject the item, ensuring that only suitable products are added to the inventory.
Functional Requirements
Functionality
F1: The system shall allow users to list items they want to declutter by providing item details such as name, category, condition, and images.
F2: The system shall allow shop owners to browse and search for available items by category, keyword, and product name.
F3: The system shall enable shop owners to place orders for selected items and proceed with payment processing.
F4: The system shall allow logistics personnel to set and update item prices based on demand and condition.
F5: The system shall generate order confirmations, receipts, and invoices upon successful transactions.
F6: The system shall provide an approval mechanism for the admin to verify suppliers and shop owners before they can participate.
F7: The system shall send notifications to users regarding order status updates, approvals, and inventory changes.
F8: The system shall allow buyers to browse and purchase available items from shop owners.
F9: The system shall track and log all transactions for record-keeping and reporting purposes.
F10: The system shall allow users to auction their items, enabling competitive bidding among shop owners.
Data
D1: User data (name, email, contact details, address, role) shall be securely stored and encrypted in the database to ensure privacy and prevent unauthorized access.
D2: Closet data (item name, description, category, condition, images) shall be stored in a relational database, with images securely saved in storage for easy retrieval.
D3: Inventory data (stocks, prices, classifications, reason for sellings) shall be dynamically updated in the database to reflect changes and ensure accuracy.
D4: Catalog data (item details, classifications, prices) shall be maintained in a structured database, allowing shop owners and suppliers to manage product listings efficiently.
D5: Order data (order ID, shop ID, user ID, order date, payment status, payment details, status) shall be recorded and stored in the database for tracking, auditing, and order processing.
D6: Shop inventory data (shop ID, item details, stocks, price) shall be stored in the database to help shop owners manage their available products.
D7: Shop item data (item name, price, description, images) shall be stored in a secure database, with validation to prevent incorrect or malicious entries.
D8: Buyer order data (order ID, shop ID, user ID, payment details, status) shall be securely processed and linked to the cashier system to ensure seamless transactions.
D9: The system shall integrate with third-party payment APIs (e.g., Gcash) to securely handle online transactions and verify payment authenticity.
User Interface
UI1: Intuitive and User-Friendly Interface
Figure 4.2 shows the Supplier Closet Clutter Interface, which provides a clear and organized navigation structure. The design emphasizes simplicity to reduce cognitive load and help users complete tasks efficiently.
UI2: High-Quality Product Display
Figure 4.3 shows the Product Interface, which features images and detailed descriptions to help users evaluate items effectively. Each product listing includes key information such as price, condition, and other relevant details.
UI3: Clear Shopping Cart Overview
Figure 4.4 shows the Shopping Cart Interface, which provides a clear summary of selected items, including product details, quantities, and total cost. Users can adjust item quantities or remove products, offering flexibility before checkout.
UI4: Streamlined Checkout Process
Figure 4.5 shows the Payment Interface, designed for an efficient checkout process. It guides users through payment and shipping steps with clear instructions and progress indicators, minimizing unnecessary steps to reduce drop-off rates and improve user satisfaction.
UI5: Responsive Design for Multiple Devices
Figures 4.6, 4.7, and 4.8 show the Clucash Mobile View Interface, demonstrating the system’s responsiveness across devices such as smartphones. The interface dynamically adapts to various screen sizes, ensuring a consistent and user-friendly experience on all platforms.
UI6: Order Management and Tracking
Figure 4.9 shows the Order History Interface, which allows users to view both past and current orders. It displays key details such as order status, tracking information, and expected delivery dates.
UI7: Personalized Closet Dashboard
Figure 4.10 shows the Supplier Closet Dashboard Interface, providing users with an overview of their decluttering progress, including the number of items listed, sold, or donated. It also offers insights into usage trends to encourage active user engagement.
UI8: Seamless Browsing and Search
Figure 4.11 shows the Shop Owner Browsing Interface, which supports easy navigation through product categories and an advanced search function. Users can refine their searches with filters, enabling them to quickly find relevant items.
Non-Functional Requirements
Technical Requirements
T1: Response Time Under 3 Seconds
The system shall maintain an average response time of less than 3 seconds for key user actions, ensuring a smooth browsing and transaction experience.
T2: Peak Load Capacity
The system shall ensure to handle up to 500 concurrent users without significant performance issues, ensuring system stability during peak usage.
T3: Cross-Platform Compatibility
The system shall be functional on modern web browsers, including Chrome, Firefox, Safari, and Edge, while also being responsive and optimized for mobile devices to ensure a consistent experience across smartphones and tablets.
T4: Scalability
The system shall be hosted on a scalable cloud infrastructure (e.g., AWS, Azure, GCP, or InfinityFree), allowing seamless expansion to support increased data volumes, user accounts, and transactions.
T5: Efficient Search and Filtering
The platform shall provide advanced search and filtering capabilities, allowing users to quickly find items based on categories, price, and condition.
Security Requirements
S1: Data Encryption
All user data, including personal information, passwords, and transaction details, shall be encrypted both in transit and at rest. Standard encryption techniques, such as hashing for passwords and secure HTTPS connections, shall be used to prevent unauthorized access and ensure data privacy.
S2: Secure Login and Password Policies
The system shall enforce strong password policies requiring a combination of uppercase and lowercase letters, numbers, and special characters. Passwords shall be securely hashed before storage.
S3: User Role Management
Access to different parts of the system shall be restricted based on user roles, such as admin, buyer, suppliers and shop owner. Admins shall have full control, while suppliers and shop owners shall have limited access based on their needs. This ensures that sensitive data and administrative features are only accessible to authorized users.
S4: Secure Session Handling
User sessions shall be securely managed to prevent unauthorized access. Sessions shall automatically expire after a period of inactivity, requiring users to log in again. Secure cookies shall be used to store session information, preventing session hijacking.
S5: Security Audits and Vulnerability Testing
Regular security audits, vulnerability assessments, and penetration testing shall be conducted to proactively identify weaknesses in the system. Automated and manual testing methods shall be used to detect and resolve security flaws before they can be exploited.
Legal Requirements
L1: The system shall comply with the Data Privacy Act of 2012 (RA 10173) by ensuring the secure collection, storage, and processing of personal data to protect user privacy.
L2: The system shall follow the Consumer Act of the Philippines (RA 7394) by providing accurate product descriptions, fair pricing, and secure payment methods to protect buyers.
L3: The system shall adhere to Bureau of Internal Revenue (BIR) tax regulations by properly recording transactions and generating official receipts for compliance.
L4: The system shall respect intellectual property rights under the Intellectual Property Code (RA 8293) by ensuring that listed products do not infringe on copyrights or trademarks.
L5: The system shall comply with the E-Commerce Act of 2000 (RA 8792) by recognizing electronic transactions and digital signatures to support secure online transactions.
User Requirements
U1: The system shall be intuitive and easy to navigate, ensuring that users can quickly understand and utilize its features without extensive instructions.
U2: The system shall offer clear and concise instructions on key processes, such as listing items, purchasing, and auction participation, to minimize user errors.
U3: The system shall ensure a smooth and responsive experience across different devices and screen sizes, allowing users to access features seamlessly on both desktop and mobile platforms.
U4: The system shall provide sellers with an intuitive interface for listing items, including adding images, descriptions, and setting prices to streamline the selling process.
U5: The system shall enable shop owners to manage their inventory efficiently by marking items as sold, relisting them, or removing them from the platform.
U6: The system shall provide buyers with an easy-to-use browsing and search function, allowing them to filter items based on category, item name, and keywords.
U7: The system shall provide buyers with order tracking, allowing them to monitor the status of their purchases from payment to delivery.
Development and Testing
Development Methodology
Agile methodology was chosen for the Clucash platform to ensure flexibility, continuous improvement, and user-driven development. Its iterative approach allows features like item listing and transactions to be built, tested, and refined in short cycles, keeping the system aligned with user needs. Regular feedback helps minimize risks and enhance efficiency.
Development Phases
Requirements Gathering:
Requirements were continuously refined through iterative discussions with stakeholders and potential users. Feedback from each iteration was analyzed and used to adjust priorities, ensuring the system evolved to meet user needs effectively.
Design:
The system’s architecture was designed using modular principles to allow scalability and easy modifications. The user interface was developed with a focus on simplicity and ease of navigation, ensuring an intuitive experience for buyers and sellers.
Implementation:
The system was developed in iterative sprints, with each sprint focusing on building and refining key functionalities. Regular code reviews and continuous integration practices ensured high code quality and maintainability.
Testing:
Testing played a crucial role in ensuring system reliability and performance. Each process was tested before moving to the next to maintain functionality and stability. The testing procedures included:
Unit testing ensured component functionality.
Integration testing verified module interactions.
System testing assessed performance and usability.
User acceptance testing gathered feedback for validation.
Deployment:
The system was deployed in a hosted environment to ensure scalability and accessibility. A phased rollout approach was used to monitor performance and resolve any potential issues before full deployment.
Maintenance:
Regular updates and improvements are planned based on user feedback. Bug fixes, security patches, and feature enhancements will be continuously deployed to keep the system efficient and up-to-date.
Development Environment
The development of the system utilized various tools and technologies to ensure efficiency and functionality. The following components were used:
Programming Languages
PHP: For backend development and server-side logic.
HTML: For structuring web pages and content.
CSS: For styling, layout, and responsiveness.
JavaScript: For interactivity and enhancing user experience.
Development Tools
VS Code: A free, lightweight, and powerful code editor developed and supports multiple programming languages, including PHP, JavaScript, HTML, and CSS, making it ideal for web development.
XAMPP: A local development environment with Apache for web hosting and MySQL for database management.
Database
MySQL: A database management system, efficiently handling user data, item listings, transactions, and other platform records.
Hosting
InfinityFree: An online hosting platform, providing free online accessibility for testing and deployment.
Operating System
Windows: The system was developed and tested on a Windows environment, ensuring compatibility with the chosen development tools and technologies throughout the process.
Testing Procedures
To ensure the quality and reliability of the system Clucash, the testing activities were conducted throughout development:
Unit Testing
Individual components and modules were tested to verify that they functioned correctly in isolation. This included testing core functionalities such as user authentication, item listing, and transaction processing.
Integration Testing
The interaction between different system components was tested to ensure smooth data flow and communication. This included testing database queries, and interactions between the frontend and backend.
System Testing
The entire system was tested against specified requirements to validate overall performance, security, and usability. Sellers, buyers, and shop owners participated in testing key functions such as item listing, browsing, purchasing, and transaction processing.
User Acceptance Testing (UAT)
End-users, including potential suppliers, shop owners and buyers, were involved in testing the system. Their feedback was collected to validate whether the system met their needs and expectations before final deployment.
Test Data
Both sample data and real-world scenarios were used for testing. Sample data included mock user accounts, listings, and transactions, while real-world data tested actual user interactions with the system.
Test Metrics
Key metrics used to evaluate the effectiveness of testing included defect density (number of bugs per module), test pass rate (percentage of successfully passed tests), and user-reported issues after UAT.
Implementation Plan
Project Schedule
The implementation of the Clucash platform followed a detailed project schedule, ensuring the timely completion of each development phase.
Use of Project Management Tools
A Gantt chart was employed to visualize the project timeline, monitor progress, and ensure that all tasks were completed within the planned time frame.
Key Milestones
Week 1: Set up the development environment, define technical requirements, and assign development tasks.
Week 2: Begin coding the core features, including user registration and item listing functionality.
Week 3: Develop the platform’s layout and choose the appropriate technology stack for smooth integration.
Week 4: Implement item search functionality, basic user authentication, and ensure proper item listing management.
Week 5: Add advanced features such as item categorization, user profiles, and enhanced search capabilities.
Week 6: Deploy the platform to InfinityFree and ensure proper configuration for live access.
Week 7: Conduct testing to ensure all features are working as intended and refine the design based on feedback.
Resource Allocation
Project Manager: Oversees project planning and coordination.
Developers: Backend, frontend, and database management.
Testers: Quality assurance and user acceptance testing.
Estimated Time and Effort
Each phase of the Clucash platform development was allocated approximately one week, with daily progress checkpoints. Effort was divided as follows:
Design : 10%
Development : 50%
Testing and Debugging : 25%
Deployment and Final Adjustments : 15%
Track Progress
Regularly monitor progress to ensure completion within the estimated percentages and make adjustments as necessary. Use project management tools to keep track and evaluate progress throughout the development process.
Resource Allocation
To successfully develop and deploy the Clucash platform, various resources are needed, including human, hardware, software, and financial resources. These resources ensure smooth development, testing, and deployment while maintaining efficiency and cost-effectiveness.
Human Resources
Project Manager: Oversees project planning, coordination, and execution.
Developer: Designs and implements the user interface, develops server-side functionality, integrates the database, and manages API connections.
Tester: Conducts testing, identifies bugs, and ensures platform stability.
UI/UX Designer(optional): Creates wireframes, layouts, and improves user experience.
Hardware Resources
Development Computers: Laptops or desktops with sufficient processing power for coding and testing.
Servers (Local Testing): Hosting service provided by XAMPP for development testing.
Internet Connection: Stable and high-speed connection for development, testing, and deployment.
Software Resources
Code Editor/IDE: Visual Studio Code for coding and developing PHP, HTML, CSS, and JavaScript code
Development Environment: XAMPP for local server with Apache and MySQL.
Design Tools: Figma for UI/UX prototyping.
Hosting Service: InfinityFree for deployment.
Financial Resources
Domain and Hosting: Free online hosting with InfinityFree.
Contingency: ₱2,000.00 for unforeseen costs such as third-party integrations and other unexpected expenses.
Risk Management
To ensure the successful development and deployment of Clucash, potential risks must be identified, assessed, mitigated, and continuously monitored.
Risk Identification:
Technical Risks: Issues with system integration, software bugs, or scalability limitations.
Financial Risks: Unexpected costs for software licenses, third-party integrations, or hosting upgrades.
Operational Risks: Development setbacks due to unforeseen technical difficulties or resource constraints.
Security Risks: Data breaches, unauthorized access, or vulnerabilities in the platform.
User Risks: Low engagement due to usability challenges or lack of awareness.
Risk Assessment:
Table 4.1 Risk Assessment Table
Risk
Likelihood
Impact
Priority
Bugs or system errors
High
High
Critical
Data breaches
Medium
High
Critical
Deployment Challenges
Medium
High
Medium
Low User Adoption
Medium
High
High
Budget overruns
Medium
Medium
High
Admin approval delays
Medium
High
High
Delayed Adoption of Selling Options
High
Medium
Medium
Risk Mitigation:
Technical Risks: Use agile development practices, conduct thorough code reviews, and perform regular testing.
Financial Risks: Maintain a contingency fund (PHP 2,000 buffer) and prioritize cost-effective solutions.
Operational Risks: Set realistic deadlines, conduct weekly progress reviews, and allocate buffer time for critical tasks.
Security Risks: Implement robust authentication, encryption, and regular security audits.
User Risks: Improve user experience through usability testing and create marketing strategies to drive engagement.
Risk Monitoring:
Regular team meetings to identify new risks and assess ongoing mitigation strategies.
Use project management tools to track risks and adjust plans accordingly.
Continuously review system performance and user feedback to address emerging challenges.
Communication Plan
Effective communication with stakeholders has been a key aspect of Clucash's development. The following outlines the communication channels, frequency, and protocols used throughout the project.
Communication Channels
Meetings: Regular check-ins with team members and stakeholders via in-person or virtual meetings (e.g., Zoom, Google Meet).
Email Updates: Formal progress reports, feedback requests, and important announcements were shared via email.
Instant Messaging (Messenger): Quick updates, clarifications, and real-time discussions were conducted via messaging platforms.
Documentation and Reports: Shared documents (e.g., Google Docs) were used for storing meeting notes, technical documentation, and project updates.
Communication Frequency
Weekly Team Meetings: A structured review of progress, blockers, and next steps.
Ad-hoc Communication: Immediate communication for urgent issues or changes.
Communication Protocols
Clear Agenda for Meetings: All meetings followed an agenda to ensure focused discussions and efficient use of time.
Stakeholder Feedback Integration: Feedback from stakeholders was documented and reviewed to inform development decisions.
Issue Escalation Process: Critical issues were reported immediately via email or instant messaging to ensure quick resolution.
Version Control for Documents: All shared documents were maintained with version control to prevent data loss or miscommunication.
Capstone Project Deployment Results
The system was deployed from February 14, 2025, to March 14, 2025, involving 1 supplier and 1 shop owner from Davao City. Daily monitoring was limited due to other project commitments, and respondent availability was affected by work and personal obligations. Despite these challenges, most participants were cooperative and engaged, demonstrating the platform's real-world potential and emphasizing the importance of flexible project management.
General Objective: Reduce household clutter by 10% through effective utilization options such as selling items.
Table 4.2 Closet Clutter Overview
A related study by Muster, Iran, and Münsch (2022) examined how decluttering contributes to sustainable consumption, emphasizing selling unwanted items as an effective way to reduce household clutter. This aligns with Clucash’s goal of minimizing clutter through an inventory tracking system that monitors item transitions from storage to utilization.
Table 4.2 and Figure 4.13 illustrate the inventory tracking system used to manage household items. Items are categorized into Closet (stored items), Clutter (identified for removal), and Decluttered (successfully sold or auctioned). The bar graphs provide a visual representation of item movement, tracking progress from clutter to productive use.
To determine if the 10% clutter reduction objective was met, the system monitored identified cluttered items and their sales progress through Clucash’s dashboard. Results showed that 50% of the identified clutter (2 out of 4 items) was successfully removed, exceeding the 10% reduction goal.
Specific Objective 1: Decrease the time of listing items by 10% by simplifying the listing process of items to be decluttered.
Table 4.3 Listing Time Statistics
Month
Total Listing
Average Time per Listing (HH:MM:SS)
Total Time Spent (HH:MM:SS)
January - Week 1
20
00:04:10
03:30:00
January - Week 2
10
00:02:15
01:10:00
February - Week 1
15
00:03:05
01:35:00
A related study by Naliaka and Namusonge (2018) found that effective inventory management enhances efficiency by reducing the time needed to track and list items. This aligns with Clucash’s objective of decreasing listing time by 10% through a more streamlined process.
Table 4.3 and Figure 4.14 present weekly listing statistics, tracking total listings, average time per listing, and total time spent. Data from Figure 4.14 shows that in February - Week 3, four (4) items were listed, with an average listing time of six (6) minutes and fifty-four (54) seconds per item, resulting in a total of twenty-seven (27) minutes and thirty-seven (37) seconds. By February - Week 4, the number of listings increased to six (6), but the average time per listing also rose to seven (7) minutes and thirty-eight (38) seconds, bringing the total time to forty-five (45) minutes and fifty (50) seconds. While more items were listed, the increase in average time suggests users spent additional effort on each listing.
The objective of reducing listing time by 10% was not achieved, as the average time per listing increased instead of decreasing. This may be attributed to users taking extra time to refine item descriptions, improve images, or ensure accurate categorization. Madamidola et al. (2024) observed that while inventory systems enhance efficiency, users often experience an adjustment period before realizing time-saving benefits.
Specific Objective 2: Increase the number of available options for item utilization from 1 to 2 by adding options for auctioning an item.
Table 4.4 Selling Options Overview
Selling Options
Number of users
Fixed Price
3
Auction
1
A related study by Khan and Kumar (2024) found that businesses using advanced inventory management systems could expand their selling options from a single channel to multiple methods. This aligns with Clucash’s goal of increasing item utilization options from one to two by introducing an auction feature alongside fixed pricing.
Table 4.4 and Figure 4.15 present data on selling options and user participation. The system currently has one (1) shop owner and one (1) supplier. Only the fixed-price method has one (1) active seller, while the auction option has zero (0) participants. This suggests that while the auction feature is available, users have not yet adopted it.
To assess the objective’s success, the system tracked seller participation in each option. While the auction feature was implemented, the lack of adoption indicates users may be unfamiliar with or hesitant about the new method. Wang et al. (2004) noted that auction adoption can be slow, as users often prefer fixed pricing due to its simplicity.
