Environment - Team Programming

Revision as of 12:50, 21 March 2008 by Clarman (talk | contribs) (New page: The teams will be programming regularly throughout the week. Therefore, we need computers in the room. We only need (and want) 1 computer for each 2 students; e.g., if 16 people, then 8 ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The teams will be programming regularly throughout the week. Therefore, we need computers in the room.


We only need (and want) 1 computer for each 2 students; e.g., if 16 people, then 8 computers. Often, it is possible for students to bring their own laptop.


IT IS USUALLY BEST IF THE PEOPLE BRING THEIR EXISTING COMPUTERS INTO THE WORKSHOP


A network is required; the computers should be on your regular development network - we may be working with existing code and tools in your environment.


Software

Access to a shared version control tool (e.g., Subversion)


(MAYBE...) The coach may contact the team before the workshop, and ask to arrange installation of a continuous integration tool, such as CruiseControl.


If Java group:

  • Latest release version of Java Runtime (JRE)
  • Latest release version of Eclipse or other IDE the team uses


If C++ group:

  • The tools that the team normally uses


If .NET group:

  • Visual Studio