Configuration Control of Information
Valerio Bellizzomi (vbnet@rm.ats.it)
Tue, 18 Apr 2000 01:09:19 +0200
Hello,
in the following lines I will describe what kind of work spaces (baselines,
work areas, etc.) should be present in a useful CMS:
- Engineering Workspace
- Holds all information that is under development or being changed, that
has not been approved for program use or release;
- The information may be changed by the individual responsible for the
product as the approving agent;
- The content is controlled by the individual responsible for the
information;
- Workspace is owned by the engineer doing the work.
- CM Workspace
- Stages of documentation and software re-creating (compiling) and
releases;
- Holds tools and files used by the project, or needed to build or
control project information and/or deliverables:
- Project plans, procedures, and reports;
- Schedules, budgets, and CM records;
- Audit trails, records, and lessons-learned information essential for
certification, approval, or acceptance.
- Workspace is owned by CM, with read-only privileges to all other
organizations.
- Controlled Project Area
- Test Area
- Holds all test documentation and versions of software released for test
from CM;
- Test area is owned by the test manager.
- Customer-Controlled Workspace
- Holds all customer-approved baselined and approved information:
- Functional
- Allocated
- Product
- Records and reports
- Other approved or delivered information
- This area cannot be updated unless the change is authorized by the
customer;
- Workspace is owned by the customer.
val.