TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date:
Fri, 11 Jun 1999 08:39:03 -0400
Reply-To:
Mike Brenner <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Subject:
From:
Mike Brenner <[log in to unmask]>
X-cc:
Content-Type:
text/plain; charset=us-ascii
Organization:
MITRE
MIME-Version:
1.0
Parts/Attachments:
text/plain (47 lines)
PDR stands for Preliminary Design Review. In addition to the root library units and
main programs, the prototypes are evaluated at PDR. Certainly the user interface
and any high-risk algorithms have gone through many performance demonstrations to
the user and been blessed by PDR time. If the prototypes were well designed, then
most of the code of the project is already done at this time and just needs to be
interfaced together. The mistakes to avoid are: (a) allowing global variables, (b)
permitting software environments instead of standard file formats, and (c)
scheduling a PDR to occur before the prototypes are actually working.

CDR stands for Critical Design Review. The mistake to avoid is: (a) Scheduling CDR
before all tests, code, interfaces, training, tools, and maintenance are fully
designed or before all deficiencies discovered at PDR are remedied.

CM stands for Configuration Management. This is the science of tracking what parts
are in each level and which parts changed in each baseline of software. CM uses
techniques such as: (a) taking backups, (b) unique numbering, (c) process models to
track use of parts, (d) tools to automatically compile and test a baseline, (e)
tools to automatically create a version description document for each baseline, (f)
tools to track which Customer Service Requests were completed in each baseline,
(g) tools to prevent anxious managers from permitting split baselines, since the
cost of merging baselines back together is usually much higher than developing in a
modular fashion, and (h) tools to compute progress, volume, and clustering metrics
on the process.

Mike Brenner


Alexandre E. Kopilovitch wrote:

> Robert I. Eachus wrote:
> >        PDR ==> Main program and all root library units.
> >        CDR ==> Remaining (child) package specs plus key algorithms.
>
> What those PDR and CDR stand for? Probably "P" = "Project", "C" = "Components",
> "D" = "Design" or "Description" and "R" = "Review" or "Requirements".
>
> >that you have to get--in government procurement terms--these "software
> >deliveries" spelled out in the RFP.  What we have found best--if you can
> >get it in the RFP and contract--is to have read access to the CM files.)
>
> I guess that RFP stands for "Request For Proposal", but what is CM?
> Maybe, "Customer's Memory? -:)
>
> Alexander Kopilovitch                      [log in to unmask]
> Saint-Petersburg
> Russia

ATOM RSS1 RSS2