Message-Id: <9512032341.AA10914@MIT.MIT.EDU>
Date: Sun, 03 Dec 95 18:49:29 EST
From: wade@MIT.EDU (Steven Wade Neiterman)
To: orange@MIT.EDU
Subject: Orange:  Vault Description

        
                THE DEVELOPMENT VAULT -- DESCRIPTION

The Orange Team proposes the following broad outline as the standard
procedure for methodology selection for future MIT development under the 
Delivery Process.

When teams begin projects they will be required to choose a method which 
meets the requirements for development outlined by the first Orange 
Team.  Teams will be able to select a method in one of the three ways.

  1.  Choose a method used in the past and judged effective by the
      team that used it.  These methods would be maintained in a "vault" 
      which allowed access to all development team members.

  2.  Modify a vault method to meet the needs of their project.  If the
      revised method is deemed successful, it will be added to the 
      vault.

  3.  Create a new method which meets the requirements and the needs of
      the project.  If the new method is deemed successful, it will be
      added to the vault.

The Orange Team plans to deepen this model in the next month.  The chief 
problem we foresee is the maintenance of the vault which may become 
unwieldy over time.  The team will also suggest at least one process 
which would allow teams to contribute to the vault.  We hope to make the 
vault self-managing through standard development team actions.  We 
believe that the initial platform for the vault will be WWW.

In addition, we plan to seed the vault with a small number of 
prototypical methods which meet the requirements needs and to devise an 
implementation plan which will initialize the vault.