This page last changed on Dec 08, 2008 by unsworth.

Members

  • Catherine Plaisant (Uses and Users) UMD
  • Stan Ruecker (Interface) Alberta
  • Steve Ramsay (ex officio) Nebraska
  • Matt Kirschenbaum (Collaboration) UMD
  • Martin Mueller (Data-Analytics) Northwestern
  • -Bill Parod (Data) Northwestern-
  • John Unsworth (ex officio) UIUC Chair

Address blob: plaisant@cs.umd.edu, sruecker@ualberta.ca, sramsay@unlserve.unl.edu, mkirschenbaum@gmail.com, martinmueller@northwestern.edu, unsworth@uiuc.edu

Meeting Notes

2007

2008

Responsibilities of the SuperCell

The SuperCell is responsible for management and coordination across the other cells. That activity includes:

  • over-all design of MONK
  • decision-making on questions that cross cells
  • dispute resolution
  • sequencing the milestones of other cells so as to minimize dependecies and delay
  • identifying and minimizing bottlenecks
  • approving public releases of MONK software
  • sharing information about conference calls, meetings, and progress within the cells
  • putting together the agenda for all-hands meetings
  • coordinating documentation at various levels
  • managing the collaboration infrastructure for the project
  • overall editing of the MONK wiki
  • keeping the mailman list up to date

Roles in each cell

Every cell needs to have individuals who take on the roles of documentation, design, implementation, and evaluation, even though each of these roles is likely to be collaborative. Those individuals are:

  Documentation Design Implementation Evaluation
SuperCell John Unsworth Matt Bill Catherine
Data John Norstad ? ? ?
Interface Mike Plouffe Stan Ruecker Matt Bouchard Matt Kirschenbaum, Catherine Plaisant
Users Catherine Plaisant ? ? ?
Analytics Steve Ramsay ? ? ?
Collaboration Matt Kirschenbaum, Greg Lord Bob Taylor, Stan Ruecker, Stefan Sinclair James Chartrand, Joe Paris, Bill Parod John Unsworth

Definition of roles:

  • Documentation: The individual in this role should develop a stated definition of what types of people or users are the anticipated consumers of the documentation that will be produced (could be other cells, end users, outside developers, etc.). This person should also consult with the documentation people in other cells to determine whether or to what extent documentation needs to interoperate (for example, does the documentation of interface code need to be available in any way to be integrated into end-user documentation) and if interoperability is necessary, develop stated understandings of how documentation will be formatted and made available.
  • Design: The person in the design role should help manage the discussion leading to decisions related to matters of form and function. Since these decisions will influence decisions regarding form and function in other cells, people in the design roles should arrange to exchange ideas when it is possible to see either new affordances or potential constraints arising from any particular decision.
  • Implementation:
  • Evaluation:
Document generated by Confluence on Apr 19, 2009 15:05