Re: Let's put this to rest

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.

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.

But IF a stack was needed to solve the problem, it would usually be represented in the OOA model as:

1 R1 <<ordered>> *
[A] ---------------------- [B]

IOW, <<ordered>> and 1:* (or *:*) is all one needs to know at the OOA level of abstraction. Deciding whether one needs stacks, linked lists, B-Trees or whatever for relationship collection classes is a tactical OOP prerogative. [Note the 'usually' in the first sentence. There are exceptions that depend on particular problem contexts that haven't been defined here.]

It is exactly this sort of open-ended discussion at the wrong level of abstraction with requirements that are a moving target that I sought to avoid in the challenge. So I am not going to waste any more time pursuing this further. Pick an existing model from one of the books and show why it would be done differently by "most people" due to some fundamental methodological difference.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH



.

Relevant Pages

  • Re: OOA and OOD
    ... I think we have very different views of what a proper OOA model is. ... building an OOA model is a software design activity. ... >>least since UML added an abstract action language specification ...
    (comp.object)
  • Re: Lets put this to rest
    ... find total number of oranges in the field... ... calling requirements analysis OOA. ... it appears the very core of our OOA models agreed in that example... ... you want an OOA model that is capturing some behavior too, ...
    (comp.object)
  • Re: defining quality of OOA and OOD models
    ... and, consequently, the particular paradigm methodology. ... The exit criteria for OOD modeling is fuzzier ... functional and nonfunctional requirements and OOA focusing more on ... acid test of an OOA model is that it could be unambiguously implemented ...
    (comp.object)
  • Re: OOA, OOD, design all first, how to go about it all?
    ... > either private or public. ... Public vs. private is not relevant at the OOA level. ... solution when the OOA model is completed. ... coding is now seamless cause of rigorous design. ...
    (comp.object)
  • 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)
Quantcast