Re: Let's put this to rest

AndyW wrote:
quote:
Lets' start with something quite simple. The CS101 stack (LIFO) .
Define the stack with all its properties (push, top etc) using
"translation OOA" .
end-quote:

Now, what your question had to do with the original I do not know.
Also, as pointed out I think in another post, your question about
"producing a stack" is purely a design thing but you refer to doing it
using analysis.

Lehman has posted at least 100 pages worth of email in which he's
claiming that OOA == OOD without NFRs taken into account. So, an MDA
solution *must be*:

OOA: Stack
OOD: Stack
OOP: Stack

Now, please just give us the OOA Stack specification that I can plug
into an MDA tool so that I get an OOD and OOP Stack models out.

I have also given an example for which the solution/design/program is
*addition of two numbers*. The problem is so simple that everyone from
1st graders and up can solve it, and there are so many problems which
map clearly into a solution in terms of addition of two numbers. So,
can you please give us the MDA OOA model for any of these problems, or
domain systems, for which the clear solution is addition of two
numbers.

The arguments/excuses/BUTs here are similar to like if a C++ compiler
developer was asked to demonstrate if his tool can compile a C++
statement which adds two numbers, and he replies "It's not really clear
that a program that adds two numbers is really a program - your
requirements are not right - but, my C++ compiler is very good for
compilation of space shuttle modules of over 5MLOC." and then gives us
a lecture on how he sees requirements specifications for space shuttle
modules should be done.

And just when I start to think that *books* were *already* written
about this thing called MDA that cannot handle even basic OOA/D/P
constructs and examples... sigh :-(...

Davor

.

Relevant Pages

  • Re: Lets put this to rest
    ... So what I have is an OOA model for a stack. ... containing a private reference to an array object. ... implementation language contains also support for dynamic arrays, ...
    (comp.object)
  • Re: Lets put this to rest
    ... So what I have is an OOA model for a stack. ... A stack is almost always an implementation artifact for an ordered collection. ... Whether one needs an ordered collection or not and how that ordering should be done, if needed, depends on what the problem being solved is, which you have not specified. ...
    (comp.object)
  • Re: Lets put this to rest
    ... So what I have is an OOA model for a stack. ... my stack OOA model is ready and waiting. ... I think one person is viewing it as a model for viewing ... The other way I see it occuring is when people second guess the design ...
    (comp.object)
  • Re: Lets put this to rest
    ... I think one person is viewing it as a model for viewing ... I do see OOA model as "a model for viewing the problem space", ... stack, queue, double queue, etc... ... come up with the an OOA model which includes: stack, queue, double ...
    (comp.object)
  • Re: An Observation
    ... first character on the stack. ... parse a word and compile the value as a literal to use ... need to execute at compile-time for. ...
    (comp.lang.forth)