Re: Let's put this to rest

Responding to Perryman...

If there is some fundamental difference between the MDA/translation view and "most people's", then that difference should be manifested in the OOA models we produce. That is, for some problem the model that we would produce would /always/ be different from the model that "most people" would produce and that difference would be directly traceable to some fundamental difference in design approaches.


Lets' start with something quite simple. The CS101 stack (LIFO) .


Define the stack with all its properties (push, top etc) using "translation
OOA" .


The issue is OOA methodology, not requirements elicitation, mathematical constructs, or OOP implementations. You need to define the relevant requirements and provide a problem context before we can talk about modeling a solution that /might/ involve a stack.


Yours is not to reason why ...

I want a stack, that I can :

- ask whether the stack is empty
- push something onto the stack
- get the top element on the stack (if the stack is not empty)
- remove the top element on the stack (if the stack is not empty)

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.


*************
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: DOLIST with empty list?
    ... To decide to return the empty list, ... But this fundamentally redefines DOLIST/DOSUBS in a manner ... any new results on the stack, you get a list of those ... and I replace each by recalling the variable's contents, ...
    (comp.sys.hp48)
  • Re: LIFO in C, need your suggestions
    ... printf(" stack is not empty yet, ... interpretation will be stack_remove() will remove the stack and stack_free ... if(sfree!= NULL) ... the memory held by 100 elements. ...
    (comp.lang.c)
  • Re: Beat Toudai
    ... of empty pdf pages. ... KPDF got empty little, and empty big, pages. ... But still it and evince ... Execution stack: ...
    (sci.lang.japan)
  • Re: LIFO in C, need your suggestions
    ... struct sstack_node * next; ... stnode = pop; ... printf(" stack is not empty yet, ...
    (comp.lang.c)