Each student will be assigned to a team of students. The group will work on a series of CSC 300 lab projects. . The lab work will total to a significant part of your final grade (see basic course information), the grade is given "jointly" to all members of the group, barring any disparities in student participation in the group. You will be asked to rate the participation of each member of your group as well as yourself. The surest way to fail the course is to bag on your team, don't do it.
Lab projects are required work. You must complete them to receive a passing grade in the course.
The first team meeting will produce a product: a cover sheet containing the group name, the group motto, all the members' names and email addresses. The second page should have the team's top three concerns for CSC, CPE and SE majors with brief explanations. This is to be turned in to the instructor at the beginning of the second week and will form the basis for a folder the instructor will keep to monitor and record lab team progress. Each team will put these pages up on a website for modification and review by the professor and the class.
Each team will produce a single slide and elect a leader to make a very short presentation to the class about their top concern during the second week of class. This may or may not form the basis for any of the labs.
The object here is to perform meaningful "learning by doing" lab exercises to illustrate the main issues of professional responsibility in computing and software.Some very basic sample ideas (from some time back) are given at Joe Alfonso's page , he provided these ideas as an assistant to CSC300 teams last year. Here is a recent list with lab objectives I've been working on for your information.
More details will be given in class. Labs will be put up on the schedule as determined and developed.