Software Engineering Competition

Overview

Connecting those who can help with those who need it most.

All competitions should be prepared in advance and conducted on the day of the competition.

Deadline to register: October 10, 2025


"Needs Connect" is a web-based platform designed to bridge the gap between non-profit organizations and individuals or groups willing to help. The platform aims to streamline the process of identifying, managing, and fulfilling the unique needs of various non-profit organizations. By providing a centralized system, "Needs Connect" ensures that organizations can efficiently manage their needs, while helpers can easily find and support causes they care about.

Competition Rules

  • Students in grades 11 and 12 are invited to participate.
  • Each school may register only one team, with a maximum of three students per team.
  • All team members must be currently enrolled in grades 11 or 12.
  • Each team must have a faculty advisor from their school.
  • Teams must register by the specified deadline.
  • Participants must adhere to the competition's code of conduct and rules.
  • Any form of plagiarism or cheating will result in immediate disqualification.
  • GitHub Submission: Teams must submit a link to their GitHub repository instead of a ZIP file. Each team member must commit to the project repository. Failure to do so will result in disqualification.

Constrains and Requirements

  • Language: English
  • Team Size: Maximum of 3 students per team
  • Registration: Online registration via the official RIT Dubai website
  • Originality: All code must be original and written by the team members
  • GitHub Repository: Teams must submit a link to their GitHub repository. Each team member must commit to the project repository. Failure to do so will result in disqualification.
  • Logistics: Teams are responsible for bringing all necessary equipment for their presentation, including laptops, chargers, and any other devices. Only internet access and a projector will be provided by the organizers. Failure to bring the required equipment may result in disqualification.
  • Code Functionality: Any code that does not function as intended will result in automatic disqualification of the team.

Technical Specifications

  • Programming Languages Allowed: Java, JavaScript, HTML, CSS, react, angular
  • Environment: Participants can use any IDE or text editor of their choice.
  • Submission Format: Code must be submitted in a GitHub link containing all source files and a README file with instructions on how to run the code.
  • Testing Environment: All submissions will be tested on windows with Java > 11, Node.js 14.15.0, and MariaDB installed.
  • Internet Access: Participants will have access to the internet for research purposes but are not allowed to copy code directly from online sources.

MVP Features

  • Login/Logout
    A simple login system where the server trusts the browser to identify the user. The system will differentiate between a Helper and a U-fund Manager based on the username.
  • User Roles
    U-fund Manager: Logs in using the reserved username "admin".
    Helper: Any other username is assumed to be a Helper.
  • Helper Functionality
    View Needs: Helpers can see a list of all current needs.
    Search Needs: Helpers can search for specific needs using keywords.
    Funding Basket: Helpers can add or remove needs to/from their funding basket.
    Checkout: Helpers can proceed to checkout and fund all needs in their basket.
  • Needs Management
    Add/Remove/Edit Needs: U-fund Managers can add, remove, and edit the data of all needs in their "Cupboard".
    Privacy: U-fund Managers cannot see the contents of any funding basket.
  • Data Persistence
    File Storage: The system will save all data in a database management system (MariaDB). Changes made by one user will be visible to the next user who logs in.
    Data Integrity: Ensure that data is consistently saved and retrieved from the database.
  • 10% Additional Feature Enhancement
    Custom Workflow: The additional feature should reflect a custom workflow tailored to the chosen non-profit organization.
    Documentation: add a concise paragraph in the README that explains what the new 10 % feature does and how it fits the non-profit’s workflow.
    Complexity: The feature should be complex enough to be useful and reflect a unique workflow.
  • 10% Feature Enhancement
    Priority and Time-Sensitive Needs Management.
    Feature: Implement a system to identify and sort higher priority, time-sensitive, or most frequently needed items. Establish means to sort and bundle basic needs like food, clothing, and toiletries. This could expand to neighborhood beautification services and many other types of volunteering activities.
    Justification: This feature will help the organization efficiently manage and prioritize needs, ensuring that critical requirements are met promptly.

Evaluation

  • Functionality (30%)
    Complete Implementation: All required features are implemented and fully functional.
    Stability: The application runs smoothly without crashes or significant bugs.
    Error Handling: Proper error handling and user feedback mechanisms are in place.
  • Innovation (20%)
    Unique Features: The project includes features that are not commonly found in similar applications.
    Creative Solutions: The team has approached problems in a novel and creative way.
    Value Addition: The project provides significant value or solves a real-world problem in a unique manner.
  • Technical Complexity (20%)
    Advanced Techniques: The project demonstrates the use of advanced programming techniques, algorithms, and data structures.
    Code Quality: The code is well-structured, readable, and follows best practices.
    Scalability: The project is designed in a way that it can be scaled up or extended in the future.
  • User Experience (UX) (15%)
    Intuitive Design: The user interface is intuitive and easy to navigate.
    Responsive Design: The application works well on different devices and screen sizes.
    User Feedback: The application provides clear and timely feedback to user actions.
  • Documentation (10%)
    Comprehensive README: The README file provides clear instructions on how to set up, run, and use the project.
    Code Comments: The code is well-commented, making it easy for others to understand.
    Additional Documentation: Any additional documentation (e.g., design documents, API documentation) is provided and is helpful.
    Class diagram: The class diagram must be placed in the /docs folder of the GitHub repository and lined from the README.
  • Presentation (5%)
    Clarity: The presentation is clear and effectively communicates the project’s key points.
    Engagement: The presentation is engaging and holds the audience’s attention.
    Q&A: The team is able to answer questions confidently and accurately, demonstrating a deep understanding of the project.

For any inquiries about this competition, please contact

Ali Assi
Assistant Professor of Computing and Information Technologies
Electrical Engineering and Computing Sciences Department

Website last updated: March 23, 2026