CSCI 479: Computer Science Design Project Department of Computer Science

The Team Project

Students in teams will develop a programming project that is sufficiently sophisticated as a culminating project for the BS/BA students in the computer science major.

Student teams may propose their own project, or get project ideas from outside clients and their instructor. The project should be approved by the instructor early in the semester. To facilitate the process, student teams are asked to discuss with the instructor as soon as possible and they are asked to submit a project proposal draft by Friday, September 6th, 2013.

Proposal and Draft

The project draft should describe the project scope, the expected end-product, and an outline of the technology involved in the project. The student teams then will bring their proposal and discuss the it with the entire class. In the case when an outside client is involved, the team should invite the client to the discussions.

Client

In the Agile Development process, close collaboration between the developers and the clients is a critical component. Ideally we would like to have the client come to our team meetings once a week. During those meetings, the developing teams will consult the client for details of the project and the client can give feedback to the teams for what has been done. If the client cannot meet with the team in person, we'd ask at least the client will be able to provide timely feedback on a weekly basis through other means such as video or audio conferences.

Literature Survey and Presentation

Student teams will conduct a literature survey and present the result to the class early in the semester. This survey should contain two major sections. One section is a survey of the collection of technology needed to accomplish your project; why the technology is needed for the project; why your team choose this technology; and how multiple pieces of technology work together for your project. The other section is an in-depth survey of the core technology needed for the project: the origin; the history; and the present status. If multiple pieces of technology are critical to your project, the team can pick one for in-depth report. The report is expected 5-7 pages (2,000 to 2,500 words). The presentation is expected to be 10 to 15 minutes.

Project Progress Reports and Presentations

While we will exchange information about the project at each of our meetings, two formal progress reports and presentations are required during the semester (sometimes during the 5th week and the 10th week). The reports are expected to be 3-5 pages (1,200 to 1,500 words) and presentations about 10 to 15 minutes each. Each report should include the following.

• Current status of the project
• Team plan for the rest of the semester
• Any successful stories or difficulties during the past weeks
• Any suggestions

Final Project Report and Presentation

Each team will write a final report and make a final presentation about their project at the final exam time, as specified by the university calendar. Follow the link for details.

Project Assessment

The projects will be evaluated throughout its development and in multiple aspects, including all the project milestones (see Agile development process), client interaction, written and oral reports, among others. In particular, we will be using the presentation rubric and the writing rubric for the project evaluation.