• Skip to main content
• Accessibility features

• Contact Ed Gellenbeck

• CWU
• Gellenbeck
• CS 352
• Wiki

Site Search

Search ~352

CS 352: Group Integration Project

Group Project

Working in groups of five, design and implement a prototype portal to match volunteers with opportunities in Ellensburg/Kittitas County area.

Browse the following Web sites for content ideas:

• volunteermatch.org
• idealist.org
• CWU Civic Engagement Center

Use Cases

Provide at least the following use cases:

• Individuals in the community can browse the needs/opportunities
• Authorized organizations can post needs/opportunities for volunteers
• Authenticated individuals in the community can sign up to volunteer for opportunities

Programming Teams

Students will be grouped into two programming teams of five students each.

Each programming team will implement a complete solution to the volunteer match site.

Team 1 cs352g_01	Team 2 cs352g_02
Liam	Tom
Brock	Trevor
Samwise	Gary
Paul	Kevin
Gene	Ben

Each team will be given a new cs352g_nn account to use for this project. Create and save your files in a TortoiseSVN repository in this group account. Your current cs35202_nn account should have read/write permission to the group account.

Design and Implementation

The design is also up to you. However, realize this is the CS 352 course integration project and design your portal in such a way that you can demonstrate mastery of the course content learned this quarter (and from CS 350 & 351 as well).

Suggested areas to demonstrate:

1. XML document(s) and web services to store data. Cleanly separate the model (data) from the business logic
2. CSS to cleanly separate view from the model/controller
3. ASP built-in Membership and Role classes for user authentication and security
4. ASP.NET Ajax and Web services to reduce the server postback events
5. Web 2.0 design ideas to make your portal engaging and cutting edge
6. ASP.NET Validation controls to error check and constrain user input

Process

Use this group project to gain familiarity with the software development process and software tools to collaborate on software development

In last quarter's CS 351 group project, we tried used eXtreme programming, pair programming, small daily releases, spike solutions, refactoring, and continuous integration using the TortoiseSVN version control tool.

Reflect upon and discuss with your group members what worked well, what did not work, and the process your group will use this quarter on this project to make an agile programming method work this quarter. Avoid the process model where one person codes and four people stand around and watch - it is not a good use of team resources.

Daily Scrum Meetings

We will begin every class period with a daily scrum meeting. In the scrum meeting, each team member will report on

• What they did since the last daily scrum meeting
• What they are going to do today
• What obstacles are blocking their progress and what do they need help with

These daily scrum meeting reports will provide the basis for assessing your individual contribution to the project which represents 20% of your overall grade for the project.

Due Dates

Be prepared to demonstrate a working iteration 1 on Friday, May 16 to your instructor. This iteration will be assessed and count as 20% of your overall grade for the project.

Your group project, iteration 2, is due at the start of class on Friday, May 23

In addition, prepare a 20-minute Project Oral Report for Friday, May 23 with PowerPoint slides explaining

1. The process your group followed in developing your solution
   • Development process used
   • Configuration management and version control process and tools used
   • Unit and Integration testing process and tools used
   • Faithfulness to the process
2. The basic architecture and overall design of your solution
   • Mention and justify each area of course content (e.g. Membership, Web Services, XML, Ajax, etc.) that you included in your design
   • Explain how your team separated the model-view-controller logic in your design
3. Demonstration of the current status of your system
   • Point out areas of pride in your solution and why they are noteworthy
   • Point out areas of concern in your solution and how they could be improved
   • Current status of your solution - what is not yet complete
     • This is a prototype project, you are not expected to have all the functionality completed
4. Design post-mortem
   • Explain at least two design decisions that ended up working well with the project
   • Explain at least two design decisions that ended up working poorly with the project
   • Given the opportunity to begin anew, what program design decisions would the group do differently?
5. Process post-mortem
   • Explain at least two team processes that worked well during the project
   • Explain at least two team processes that worked poorly during the project
   • Given the opportunity to begin anew, what team processes would the group do differently?

Note: All five team members must participate in the project oral report

Grading criteria

Your individual grade for the project will be based on

Category	Assessment	Weight
Individual	Daily Scrum Meeting Reports Your individual contributions	15%
Group	Project Quality - Iteration 1 Based on in-class demonstration	15%
Individual	Oral Presentation	10%
Group	Project Quality - Iteration 2 Graded wholistically - Save your files in a TortoiseSVN repository in the group account	60%

Honor code: The work needs to be your own. Cite references to the code written by others that you modified for your project during the daily scrum meetings and final oral presentation.