CSCI 340 - Community Project - 65%
Teams
- Elizabeth Dye
- Jack Liu
- Marina Sweeten
- My Nguyen
- Aaron Steele
- Ollie Kwizera
- Ethan Spurlock
- Jacob Falleur
- Mitch Lowry
- Reed Mershon
- Brian Tschiemer
- L. J. Leslie
- John Nickle
- Shuhao Kou
- Ryan Rose
- John McAvey
- Collin Shaddox
- Kylie Dickerson
- Joseph Benton
- J. D. Hoglan
Community Guidelines
- Be aware of the power and position you hold
- Be transparent about purposes and limitations
- Assess community needs, taking into account community partner’s views
- Acknowledge that you will create burdens for that partner and seek to minimize
- Make sure the good you want to produce is a good your partner wants
- Do not leave behind a mess
- Do not demean or disempower the very people the project was to serve
- Do not create expectations you cannot fulfill
- Recognize that you likely will not know as much as your community partner about what is risky or harmful for partner's constituents. Follow the autonomous person's most suspect rule: do it because they said so.
Team division
You will fill multiple roles in your team. Each member will have a first and a second
priority role, to be decided upon by the team. One person cannot have both of the front-end
options as their first and second, these must be distributed to all team members. In a team
of five, duplicate the Framework / Mobile and the Javascript / AJAX roles.
- Front-end HTML / CSS
- Front-end Javascript / AJAX
- Framework / Mobile
- Testing
Team Contract
- Due Jan 25, signed by all members
Your team will need to create a team contract. This will be the governing document for
your team. It will help you establish the structure, procedures, expectations of
participation, accountability, and consequences for breech of contract.
Here is an excellent template
for a team contract that you should use in devising
your own contract.
First Partner Meeting
- Complete by Jan 29
- Present week of Feb 1
Your first meeting with your community partner will focus on gathering requirements for
the project.
You should leave the meeting with a clear idea of the system they want to make.
Do they need a web app or mobile app, or both? What are the stories, use cases,
entities and relationships you will need to create your project?
You will present your findings to the class in a seven minute presentation, sharing
the user stories, use case diagrams, and entity-relationship models you understood
from the partner.
Second Partner Meeting
- Complete by Mar 4
- Present week of Mar 7
Details TBA
Third Partner Meeting
- Complete by Apr 8
- Present week of Apr 11
Details TBA
Final Presentation
During the final exam period, your team will present and demonstrate
the complete prototype you have built. You should
plan for an 20 minute presentation and 2 minutes for questions.
Peer Evaluation
At the end of the course, you wil complete an analysis of each team member.
This analysis should include a separate paragraph for each team member,
including yourself. Each paragraph should describe how that team member
contributed to the project in concrete terms (this person did XX), and it
should also provide some analysis of that person's strengths and/or weaknesses —
in terms of quality of contributions as well as teamwork skills.
I am looking specifically for positive aspects as well as
constructive criticism that might help the classmate
work better in future teams. The analysis for each team member would ideally
be at least 5 or 6 sentences long, longer would be welcome.