Your final project will be your focus for the second half of the semester. You will be working with a team on your own project, developing it in three discrete iterations. The final project is designed to be the primary vehicle for your achievements and the central topic of your reflections.
You will form your own teams. It is recommended that you do this primarily around the times you are available and secondarily around shared interests.
Each team must register with the instructor by sending an email that provides all team members' names. Teams must register by the end of the day on February 7. They must address the required Project Design elements described below at time of registration.
Every team must identify their target audience and a need for their project. This identification must be specific enough to allow you to test your project with representatives from the audience. For example, "students" is too broad as it includes an enormous variety of ages and cultures. "Non-traditional students at Ball State University" and "Chinese Computer Science majors in the 1+2+1 Program" are both more reasonable targets: you can identify individuals readily for focus group discussion or acceptance testing.
Once you know your target audience, you can identify a specific problem that they have. What need does your project fulfill?
Each team will give a project pitch to the class. It is strongly recommended that you review the pitch requirements with the instructor prior to your pitch. The presentation may be at most eight minutes long. Slides are optional and handouts are encouraged. The pitch must satisfy the following requirements.
Project pitches will be made on February 10 during our regular class meeting time.
Pitches will be evaluated according to the following rubric.
|Requirement||Unaddressed (0)||Unsatisfactory (1)||Probationary (2)||Clearly satisfactory (3)|
|Target audience and need|
|UI sketch or sample clients|
A team must repeat their pitch if they earn 0 or 1 point on any row or if total points is less than 12. Revised pitches will be scheduled for the next possible class meeting. Once again, it is strongly advised that you discuss your project pitch with the instructor prior to delivering it to the class; having to complete a second pitch will eat into precious design and development time.
All projects must abide by the following non-functional requirements.
Stable executable releases are to be tagged in the repository at the end of each iteration according to the following schedule.
|1||0.1||March 5, 8:00AM|
|2||0.2||April 2, 8:00AM|
|3||0.3||April 23, 8:00AM|
Milestone presentations will follow on the two class periods after the end of an iteration. Each milestone presentation may be no more than ten minutes long and must address the following.
At the end of each milestone, you will receive a formal evaluation that covers both your milestone presentation and the executable release itself. The evaluation will include the following elements.