Software Product Development

CSC301
Closed
University of Toronto
Toronto, Ontario, Canada
Educator
(2)
5
Timeline
  • September 18, 2020
    Experience start
  • October 3, 2020
    Project Scope Meeting
  • November 7, 2020
    First Deliverable
  • November 30, 2020
    Final Presentation
  • December 5, 2020
    Final Deliverable
  • December 5, 2020
    Experience end
Experience
4/1 project matches
Dates set by experience
Preferred companies
Anywhere
Startup, Social Enterprise, Non profit, Any, Incubator
Any industries
Categories
Information technology Product or service launch
Skills
software development software engineering
Learner goals and capabilities

Please read the document completely and follow the steps specified there to submit proposals and ask questions. We may not be able to respond to messages here in a timely manner. This is a program that has been run for several years and we work with 20+ partners every term. All details and questions are discussed in the document below.

https://docs.google.com/document/d/1yctxACgPCoSB2z8ez6G4IKK6FJnZBH8W3LahiFNFNK4/edit?usp=sharing

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 travellers in a specific community and web-based application for connecting a non-profit to volunteers. If the project information is of interest, please go through the steps mentioned in the document. We will not be able to accept requests here as the proposals need to be chosen by the students in September.

Learners
Undergraduate
Any level
150 learners
Project
24 hours per learner
Learners self-assign
Teams of 5
Expected outcomes and deliverables

Students will submit three main deliverables:

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 1: Deliverable 1 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- Final Presentation: Students will present the final version of their software. Partners 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 that is submitted to the teaching team and the partners. This deliverable may not have all the functionalities but supports key use cases.

Project timeline
  • September 18, 2020
    Experience start
  • October 3, 2020
    Project Scope Meeting
  • November 7, 2020
    First Deliverable
  • November 30, 2020
    Final Presentation
  • December 5, 2020
    Final Deliverable
  • December 5, 2020
    Experience end
Project Examples

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

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

Provide responses in a timely manner so the project is not delayed.

Be available for a quick phone call with the teaching team or the students to initiate your relationship and confirm your scope is an appropriate fit for the team.

Provide a dedicated contact who is available to answer periodic emails or phone calls over the duration of the project to address students' questions.

You need to have a clear idea of what you need and the problem you solve. Early-stage ideas are not a good fit for the course.