Re: Let's put this to rest

"AndyW" <foo_@xxxxxxxxxxxxxxxx> wrote in message
news:pt6292pkq8tgd04tajqng44679vlqvrcp9@xxxxxxxxxx

On Thu, 15 Jun 2006 08:53:07 +0100, "S Perryman" <a@xxxxx> wrote:

"AndyW" <foo_@xxxxxxxxxxxxxxxx> wrote in message
news:s39192p6h62sr9vopidhhep9lc3tlos779@xxxxxxxxxx

My question to this. How did you initially know that a stack was
required.

My answer to this : irrelevant to the discussion.

1. The "requirement" is to produce the "OOA" for a stack.
2. Not to argue the toss about where the requirement may have come from.

I would suggest to you that the term analysis generally means to break
something down into its parts. A requirement is simply a
characteristc that must be implemented in the final system for it to
be considered acceptable.

Requirements Analysis is the process of discovering requirements.
Usually by the breaking down of an existing system to determine its
characteristics.

Using that definition - you cannot already have an existing
requirement for a stack - you havint performed the requirements
analysis that determins that is a required characteristic. So it is
not irrelevant to the discussion if you are using the terminology
incorrectly.

Obviously my words about 1 and 2 have been ignored. :-(

That aside, Davor kindly volunteered some "requirements" for those pedants
who are going to argue the toss about 1 (requirements which another
person - Dmitry Kazakov - seems to think are ok for the task at hand) .

So, we have the "requirements" for a stack and we have a spec for stack.
I am (still) waiting for a "translation OOA" model of a stack, that we
discuss
with my (and possibly others) OOA model ...


Regards,
Steven Perryman


.