CSE 116 Teamwork
September 1, 2006
First Recitation Responsibilities
• Find Team mates
• Appoint secretary (see
secretary responsibilities in
a few slides)
• Exchange contact
information (email, phone,
screename)
• Exchange schedule
information
First Recitation (Meeting)
• Note any group members
not present at meeting
• Look at Stage 1 description
• Make high-level design
decisions for Stage 1
• Set goals for work to be
accomplished this week
Secretary Responsibilities
• Should rotate through
group each week
• Keep notes about
discussion at recitation
• Note any scheduled
meetings for the upcoming
week
Secretary Responsibilities
• Email Adrienne and rest of
group at end of recitation
with notes about what was
discussed – subject of
email should be:
CSE 116 Team _ Status Report
What to do during Recitation
• Planning
• Design
• Demos of working parts of
the project
• Discussion about current
implementation problems
• Discuss what test cases
should test
What not to do in Recitation
• CODE!
• Debug
When should we code?
• Arrange meetings with one
or two other group
members during the week
• Sit at one machine
– One person should do the
typing while other person
directs the interaction
(weaker coder should direct,
not type). Discuss why
decisions are being made
while coding.
Test Cases
• We’ll talk more about JUnit
next week, but be forewarned that you will be
required to submit how you
tested your code with
each stage.
Documentation
• More and better
documentation required
than in CSE 115
• Use Javadoc-style
comments and generate
Javadocs for your code
• Use Eclipse to generate the
comments and Javadocs