crm@duke.cs.duke.edu (Charlie Martin) (03/18/88)
Could someone refer me to something describing current state of Ada PDLs? Is there an emerging standard? How about a survey of them? -- Charlie Martin (crm@cs.duke.edu,mcnc!duke!crm)
sterrett@manta.NOSC.MIL (Anthony E. Sterrett) (07/27/90)
Hello, I would like to know if anyone knows anything about an Ada PDL IEEE standard? Does it exist Tony Sterrett Code 411 NOSC San Diego
ssdken@watson.Claremont.EDU (Ken Nelson) (07/27/90)
In article <1163@manta.NOSC.MIL>, sterrett@manta.NOSC.MIL (Anthony E. Sterrett) writes: |> I would like to know if anyone knows anything about |> an Ada PDL IEEE standard? Does it exist |> There is a IEEE standard for Ada PDL. ANSI/IEEE Std 990-1986 IEEE Recommended Practice for Ada as a Program-Design Language My employer (Software Systems Design) offers a PDL called ADADL (Ada Design And Documentation Language) which is compliant with this standard. If you or anybody would like more info please call, email or write. Thanks, Ken Nelson Principal Engineer Software Systems Design 3627 Padua Av. Claremont, CA 91711 (714) 624-3402
eachus@linus.mitre.org (Robert I. Eachus) (07/31/90)
A long time ago (1984) the there was a big fight over whether Ada
PDL's should be compilable. By the end of the year the battle was
over, as the last advocates of Ada PDL's which were not compilable Ada
were won over. I think that ACM SIGAda even passed a resolution that
the proper PDL for Ada is syntactically correct compilable Ada.
The IEEE went ahead and approved IEEE 990 (1987) as a Recommended
Practice, after a similar phrase was added.
There are several tools which allow you to add standardized
comments to source programs, but in general it is easier to express
detailed designs in Ada than to actually implement some of them.
My personal preference is to have a couple of packages which I use
during design, only two of which are mentioned in the final product:
with Documentation; use Documentation;
with Assertions; use Assertions;
with To_Be_Done; use To_Be_Done;
with Undefined;
The advantage of this approach is that the body of Assertions and
Documentation can be much different during development, so that
compiling and running a development version delivers various useful
statistics. One of my favorite tricks is to make each programmer a
record type, and have the elaboration of an object of that type have
the side effect of incrementing a counter...
The disadvantage of this approach to design documentation is that
you don't get those statistics until and unless you have a compilable
design. (I prefer to start with a compilable design and to keep it
that way.) The big advantage is that, assuming you frequently compile
your design, the design documentation always agrees with the actual
product.
One class of changes I would like to get into Ada 9X is
better support for design attributes. (foo'LAST_MODIFIED, bar'VERSION,
foo_bar'AUTHOR should be required attributes).
--
Robert I. Eachus
with STANDARD_DISCLAIMER;
use STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...