1 message in com.perforce.perforce-user[p4] Do you use standards for configu...
FromSent OnAttachments
Lee Marzke13 Mar 2001 11:38 
Subject:[p4] Do you use standards for configuration management?
From:Lee Marzke (lmar@kns.com)
Date:03/13/2001 11:38:42 AM
List:com.perforce.perforce-user

For commercial Avionics the standard for US and Europe is Requirments and Technical Concepts for Aviation RTCA DO-178B

This was written by the FAA (US), JAA (Europe) and industry ( Boeing, Honeywell, Sextant Avionique, Pratt & Whitney, Bendix/King and many others )

I do have an electronic copy of this, if interested in a copy let me know where to send it.

The standard is written to address safety concearns and includes planning, requirements, design, SCM, quality, and V&V.

Specifics of repository use and metrics are not covered. The only thing close is the definition for Document Control Catagories I and II

These distinguish between formal documents that must be ECO'd for each change and more informal docs like test results that are never changed once released.

Of course you also have the CMM http://www.sei.cmu.edu/publications/documents/93.reports/93.tr.024.html

On 13-Mar-01 David Moore wrote:

Fellow Perforce Users,

We (that is, Ravenbrook Limited) are working on two projects for Perforce Software:

- a sample repository (with a lot of different uses);

- reporting.

We're looking at industry standards as part of gathering requirements for these projects. We've found quite a few standards that might be relevant, but would like to narrow down the list, partly to save effort, but partly so that we're looking at the ones that real Perforce users use. We've listed a few that we've found below.

We'd like to know:

1. Do you use any standards for software development or configuration management? Which ones, and what for?

2. Does the standard contain anything relevant to:

- repository organization or layout;

- data reporting, metrics that could be extracted from Perforce, or anything similar?

Thanks.

Here's the list of standards we're looking at. But if you use others, please let us know.

Standard for Software Configuration Management IEEE 828-1998 27-OCT-1998

Quality Management - Guidelines for Configuration Management ISO 10007

Standard for Information Technology - Software Life Cycle Processes IEEE/EIA 12207.0-1996

Information technology - Software life cycle processes - Configuration Management ISO/IEC TR 15846