Software Product Development (University of Toronto)

CSC301
Open Closing on May 3, 2025
Timeline
  • May 14, 2025
    Experience start
  • August 6, 2025
    Experience end
Experience
7 projects wanted
Dates set by experience
Preferred companies
Anywhere
Startup, Social Enterprise, Non profit, Large enterprise, Small to medium enterprise
Any industries

Experience scope

Categories
Information technology Product or service launch
Skills
software development software engineering data analysis product and service design
Learner goals and capabilities

Please read the details of the link below completely and follow the steps specified there to submit proposals. Given the high number of requests, requests submitted on Riipen will not be reviewed. All details and questions are discussed in the document below.

Program Overview and Partnership Invitation Document

This program has been run for 17 cohorts over 7 years and with 200+ partners. We work with 30+ partners every term. We will not be able to respond to messages on Riipen.


Quick summary: students take this course to develop a software application (web, mobile or desktop) for various use cases. Previous examples include mobile apps for finding travelers in a specific community and web-based application for connecting a non-profit to volunteers. If the project information interests you, please go through the steps mentioned in the document.


After reviewing 300+ proposals, we have created a thorough process to streamline the process for all involved.


We will not be able to accept requests on Riipen as the proposals need to be chosen by the students when the term begins.






Learners

Learners
Undergraduate
Beginner, Intermediate, Advanced levels
120 learners
Project
24 hours per learner
Learners self-assign
Teams of 6
Expected outcomes and deliverables

Students will submit three main deliverables:

0- Project matching: Students will review the submitted proposals and choose the ones they want to be matched with. They will be introduced to the selected partners.


1- Project plan: The project plan will set the scope of the project and explain what the students aim to do and how they aim to work with the partners, and how they want to achieve it.


2- Deliverable one: Deliverable one will be the first working version of the software with minimal functionalities and limited capabilities. This is so the partner can provide feedback and guidance for the next steps.


3- Presentation to the teaching team and Partner (You): Students will present the almost final version of their software. You are welcome to attend and observe the presentations and ask any questions they may have at the end.


4- Final Deliverable: This is the final deliverable submitted to the teaching team and the partners. This deliverable may not have all the functionalities, but it supports key use cases.


Project timeline
  • May 14, 2025
    Experience start
  • August 6, 2025
    Experience end

Project Examples

Requirements

Students will develop a minimum viable product (software). This MVP is the solution to a problem for a specific set of users that are defined by the partners. The software can be a web application, mobile app, desktop application or any other type of software. Students will work with partners to define the scope of the project and aim to deliver the minimum viable product by the end of the term. You can see some examples below:

Resume management applications for recruiters

Mobile App for helping men choose stylish clothes

Electronic Circuit Design Web application

Additional company criteria

Companies must answer the following questions to submit a match request to this experience:

  • Q1 - Checkbox
     *
  • Q2 - Checkbox
     *