Re: Only Sham SW Engineering Without System Approach and Scientific Method

From: Richard Riehle (adaworks_at_earthlink.net)
Date: 03/21/04


Date: Sun, 21 Mar 2004 18:08:50 GMT


"Tsolak Petrosian" <tsolakp@yahoo.com> wrote in message
news:a052897d.0403041931.11545a6e@posting.google.com...
> Thats called iterative development, and code pretty much covers both
> "specs" and "documentation".

One reason I like to use Ada for important projects is that both the
Specs and the Implementation are representable in code. The Specs
(Ada specifications) are compilable. The corresponding implementation
must conform to the specification because the compiler ensures that
this is so.

Further, one can compile the specifications long before there is any
implementing code and check that all the pieces fit together as they
should. This is a low-level architectural issue, but it is quite handy
for knowing about the integrity of one's architecture prior to creating
implementations.

Development can proceed incrementally. There is no need to implement
any code that does not meet the current priorities, even though some of
it may be specified in the Ada package specification.

Ada provides two approaches to extensible programming, inheritance
and child library units. Inheritance has always been a heavyweight
approach to extensibility. Child library units are more of a lightweight
approach that involves much less overhead in the final executable
code.

I suppose my point is that, when one chooses the right tools for creating
software, there need not be a gigantic disconnect between specification
and implementation. With C++, Java, and many other languages, I see
too many developers succumbing to the temptation to write implementation
code before they have fully validated the integrity of their specifications.
This seems to lead to more errors than it they had done it differently.

Richard Riehle



Relevant Pages

  • Re: Standard Ada Preprocessor
    ... But don't you agree that allowing a preprocessor to work on package ... specifications isn't exactly good Ada style. ... My first thought was to tell the user (of the compiler) to give the ... > the practical problems that Open Sourced projects face in Ada. ...
    (comp.lang.ada)
  • Re: PL/I, COBOL, Advantages, Equivalence, et al
    ... Are there lists of variables set and not set as part of the SPARK ... In Ada you'd have to examine the body to determine ... Unsolicited bulk E-mail subject to legal action. ...
    (comp.lang.pl1)
  • Re: Separate Compilation in Programming Languages
    ... implementation level, none of the other specifications should have to ... This is quite easy to do in Ada. ... Except for those pesky private parts. ...
    (comp.lang.ada)
  • Re: Did low voltage cause the pc to fail?
    ... In Europe we have now a 2years guarantee by law and believe it ... UL compliance can and will ... but this stuff is not guaranteed meeting the specs. ... meet their published specifications 100%, ...
    (sci.electronics.repair)
  • Re: Did low voltage cause the pc to fail?
    ... In Europe we have now a 2years guarantee by law and believe it ... UL compliance can and will ... but this stuff is not guaranteed meeting the specs. ... meet their published specifications 100%, ...
    (sci.electronics.basics)

Loading