Each student taking this course will participate in a semester-long software development project.

At the beginning of the course, you will present a potential software product that will be used to help you form teams with other like-minded students. During the semester, the project team will work together through the full development cycle, from an initial feasibility study to delivering a limited functioning product, and will make a series of presentations and reports of the work to the class.

Deliverables

Since every software project is different, there is no set list of deliverables that every project must provide by the end of the semester. Part of your task is to decide what is needed for this specific project. Typical deliverables include working code, documentation, training materials, test suites, etc.

Every project should use a project management system for their documentation and code. This should be chosen in conjunction with the client, but a workspace in GitHub will be provided for you.

The projects are divided into four parts, each of which ends in a milestone. At each milestone, the team submits a written report.

Teams will occasionally be asked to provide a 5min check-in of their project status to the class much like a standup meeting. On the last day of class each team makes a presentation to the course.

These are group projects, but you will also be rewarded individually for special contributions to the project, or failure to provide a fair share of the effort.

Group Deliverables

Product Feasibility Report (Week 3)
Interim Reports x2 (Weeks 6 & 10)
Final Presentation and Report (Last day of Class)

Solo Deliverables

Pitch your Software Product
Survey 1-4

CSC 450 vs 650

Graduate students taking the course may only be on a team with other graduate students. Team size for graduate students is 3-4 students per team. Each graduate student is responsible for finding a stakeholder of their own to provide guidance and feedback to the team.