Re: Let's put this to rest
- From: "S Perryman" <a@xxxxx>
- Date: Wed, 14 Jun 2006 08:12:11 +0100
"H. S. Lahman" <h.lahman@xxxxxxxxxxx> wrote in message
news:XxCjg.15178$OQ2.8804@xxxxxxxxxxx
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" ...
Regards,
Steven Perryman
.
- Follow-Ups:
- Re: Let's put this to rest
- From: H. S. Lahman
- Re: Let's put this to rest
- References:
- Let's put this to rest
- From: H. S. Lahman
- Re: Let's put this to rest
- From: S Perryman
- Re: Let's put this to rest
- From: H. S. Lahman
- Let's put this to rest
- Prev by Date: Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- Next by Date: Rational Rose Code Generation
- Previous by thread: Re: Let's put this to rest
- Next by thread: Re: Let's put this to rest
- Index(es):
Relevant Pages
|