METHODOLOGY VAULT

REQUIREMENTS STATEMENT

Requirements for the vault fall into three major categories -- access. functionality, maintenance.

The Vault must be accessible to all developer teams.

The top-level outline (checklist, schedule, plan) for a project should be available on one page.

Each method or tool in the Vault should include :

a brief description of why this method or tool would be used and a step-by-step description of how to use it
pointers to people and projects who have experience with it
measures of the resources (time, people, etc) needed to apply the method or tool
ways of deciding when a tool or method is apropriate for a project
explicit directions for carrying out a task

For example, instead of saying "Do a Requirements Analysis", detailed directions will be provided.

Each method or tool in the Vault should :

Meet the requirements in the Orange Team paper "Requirements for a DCNS Development Process".
Reduce the effort, in most cases, needed to plan and carry out a project, or require a minimum of extra effort beyond that ordinarily needed.
Make it easy for a team to select the necessary methodologies and other tools for a project.