Re: Let's put this to rest


S Perryman wrote:
"H. S. Lahman" <h.lahman@xxxxxxxxxxx> wrote in message
news:DCVjg.15224$OQ2.708@xxxxxxxxxxx

Responding to Perryman...

That is all there is to it. Do what you must in order to define the above
using "translation OOA" ...

You are asking for an OOP class definition, not an OOA model. Stick to
the original challenge and find an example in either book that you can
demonstrate would be done differently by "most people" because of some
fundamental difference in design methodology.

1. Already done. In a few seconds. No problem whatsoever.
So what I have is an OOA model for a stack.
Free of implementation info. Implementable in any way a developer sees fit.

I agree. I find your stack model as perfectly fine subset of, let's
say, an OOA model for a library for a new super OO language C$$ that
you obtained through the basic domain knowledge and analysis of
libraries for a number of other languages. Libraries are systems
themselves, and some are indeed OO systems. But, your example is a bit
surprising as within OO community they are typically taking on
"business domain" examples, so I guess that's why your example was
taken with a misunderstanding...


2. I have chosen a trivial, well-known example.
But an example that IMHO will be done differently by people who use a
fundamentally different method.

Using a "traditional", "non-executable", OOAD, I would say most of the
OOD models would contain stack with it's public interface and
containing a private reference to an array object. OOP model would
again contain a stack with array and a set of exception objects that
get thrown around. So quite trivial and well accepted mapping.

So, if "executable" OOAD does not produce different models than
"traditional" OOAD, it should come up with the very similar model to
what I just described in previous paragraph. Now, if it does, I would
love to know how the reasoning for preserving and mapping models in
this particular way is achieved. And, for example, if the target
implementation language contains also support for dynamic arrays, how
will it differentiate which one I want and the impact on the required
exceptions concepts that have to be implemented too.

Davor

.

Relevant Pages

  • Re: OOA and OOD
    ... > I'm using OOA to analyze my requirements most folks I speak to ... Requirements analysis. ... >>reconciled with the notion that OOA is not a software design activity? ... like Rhapsody that use an augmented 3GL as an abstract action language ...
    (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
    ... The CS101 stack. ... "translation OOA". ... So, an MDA ... developer was asked to demonstrate if his tool can compile a C++ ...
    (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)