Inf 117: Project in Software Engineering

Spring 2008

If you have not yet taken the survey for the class please do so ASAP!

Instructor Info

Michele Rousseau, Ph.D. 5204 DBH Office Hours by appointment michele@ics.uci.edu * To ensure a response to your email, please include "Inf117"

Class Schedule and Basic Info

Type	Section	Days	Time	Place
Lecture		M W F	10:00a - 11:20a	DBH 1425
Discussion		F	2p-2:50p	ICS 180
Lab	1	MWF	1p-1:50p	ICS 193
Lab	2	MWF	3p-3:50p	ICS 193

Course & Policy Information

CATALOG DESCRIPTION:
117 Project in Software System Design (4). Specification, design, construction, testing, and documentation of a complete software system using concepts learned in ICS 52, Informatics 101, and Informatics 111. Special emphasis on the need for and use of teamwork, careful planning, and other techniques for working with large systems. Formerly ICS 125.

All students enrolled in the course will earn a letter grade based upon their team's performance and individual performance. To ensure a individual passing grade the team must deliver a working final product following an acceptable software process. In other words, your individual assessment will be largely based on how your team performs. However, this does not mean that every member of the team will receive the same grade. Individual grades will be adjusted based on individual assessment points.

There are many assessment points the following lists indicate the main points for team and individual grades.

Team Assessment Points

• Overall project (including team website, minutes, team logs)
• Presentation(s) in class
• Professionalism

Individual Assessment Points

• Class/discussion attendance and participation
• Performance appraisals by team members
• Ability to work and promote the team
• Quality of all other work
• Professionalism

You will receive one overall grade at the end of the class; no partial grades will be given, nor will a particular distribution be enforced among the above four. You will, however, receive weekly feedback concerning your progress.

Please divide 100 points between your teammates according to their level of participation in your team's project. Do not assign any points to yourself -- just to your team members. If you feel all members have contributed equally, then assign each team member 33.3 points (assuming there are a total of four members). If on the other hand, if you feel that one member did far more work than all others and one member was not helpful, you might, for example, give the more active member 45 points, the less active member 20 points, and the other member 35 points. Please try to be fair.

Also comment briefly on each team member's performance. Your evaluation should focus on standard evaluation criteria, such as technical competence, effort, productivity, creativity, quality, dependability, communication, initiative, decision making, and leadership. Please assign a number between 1-5, 1 being worst ("unsatisfactory"), 3 being ok ("meets requirements"), 5 being best ("outstanding") for each teammate, for each of the attributes.

Your appraisal form should be emailed to the Instructor and Grader by 8a on the due date.

• Competence: possesses or seeks required knowledge
• Effort: tries to accomplish assigned tasks
• Productivity: level of work generated
• Creativity: conceptualized usful, innovative approaches
• Quality: demonstrates accuracy and thoroughness
• Dependability: follows through on responsibilities
• Communication: listens, expresses ideas/concepts
• Initiative: seeks out new assignments
• Decision making: sets objectives, evaluates alternatives
• Leadership: fosters good teamwork, solves team problems

The following template of the appraisal form is designed to assist you in evaluating your peers. Please feel free to use more space for each area as necessary.

Appraisal Form Template

Peer evaluation forms should be printed out and brought to each presentation.
Please print one copy for each team presenting (not counting your team).

Peer Evaluation Form