Software Product Development
Timeline
-
January 4, 2020Experience start
-
January 21, 2020Project Scope Meeting
-
February 8, 2020First Deliverable
-
March 24, 2020Final Presentation
-
March 31, 2020Final Deliverable
-
April 1, 2020Experience end
Timeline
-
January 4, 2020Experience start
-
January 21, 2020Project Scope Meeting
Meeting between students and company to confirm: project scope, communication styles, and important dates.
-
February 8, 2020First Deliverable
Students submit their first working version of the software. This version has limited functionality and may only support one or two key scenarios.
-
March 24, 2020Final Presentation
Students will present their product to the instructors. Partners are welcome to attend and observe the presentations and ask any questions they may have at the end.
-
March 31, 2020Final Deliverable
This is the final version of the software. Please note it may still have bugs or issues and be incomplete and there is no guarantee that all the requirements will be met. The partner can engage the students separately outside the scope of the course.
-
April 1, 2020Experience end
Categories
Information technology Data analysis Product or service launchSkills
software development software engineering data analyticsStudents take this course to develop a software application (web, mobile or desktop). Previous examples include mobile apps for finding travelers in a specific community and web-based application for connecting a non-profit to volunteers. Please review the document below for the required details and application steps:
Please follow the instructions on the document to submit proposals.
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 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.
4- 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.
Partners take ownership of the project after this.
Project timeline
-
January 4, 2020Experience start
-
January 21, 2020Project Scope Meeting
-
February 8, 2020First Deliverable
-
March 24, 2020Final Presentation
-
March 31, 2020Final Deliverable
-
April 1, 2020Experience end
Timeline
-
January 4, 2020Experience start
-
January 21, 2020Project Scope Meeting
Meeting between students and company to confirm: project scope, communication styles, and important dates.
-
February 8, 2020First Deliverable
Students submit their first working version of the software. This version has limited functionality and may only support one or two key scenarios.
-
March 24, 2020Final Presentation
Students will present their product to the instructors. Partners are welcome to attend and observe the presentations and ask any questions they may have at the end.
-
March 31, 2020Final Deliverable
This is the final version of the software. Please note it may still have bugs or issues and be incomplete and there is no guarantee that all the requirements will be met. The partner can engage the students separately outside the scope of the course.
-
April 1, 2020Experience 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
Productivity & Procrastination Monitoring Application
Companies must answer the following questions to submit a match request to this experience:
Provide a dedicated contact who is available to answer periodic emails or phone calls over the duration of the project to address students' questions.
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 responses in a timely manner so the project is not delayed.
Read through the documentation provided and submit proposal via the form (no through Riipen)
Timeline
-
January 4, 2020Experience start
-
January 21, 2020Project Scope Meeting
-
February 8, 2020First Deliverable
-
March 24, 2020Final Presentation
-
March 31, 2020Final Deliverable
-
April 1, 2020Experience end
Timeline
-
January 4, 2020Experience start
-
January 21, 2020Project Scope Meeting
Meeting between students and company to confirm: project scope, communication styles, and important dates.
-
February 8, 2020First Deliverable
Students submit their first working version of the software. This version has limited functionality and may only support one or two key scenarios.
-
March 24, 2020Final Presentation
Students will present their product to the instructors. Partners are welcome to attend and observe the presentations and ask any questions they may have at the end.
-
March 31, 2020Final Deliverable
This is the final version of the software. Please note it may still have bugs or issues and be incomplete and there is no guarantee that all the requirements will be met. The partner can engage the students separately outside the scope of the course.
-
April 1, 2020Experience end