RE: stds-80220-requirements: 802.20 Reference Model
Hello Alan!
At 09:48 AM 8/1/2003 -0700, Chickinsky, Alan wrote:
>Folk-
>
>As the person who gave the group the diagrams, I need to point out that
>these diagrams are from the existing IEEE 802 documentation. And by
>definition these diagrams are in set in stone.
>
>Thus, any suggestion that we need to "change" the diagrams is clearly
>counter productive. But, if we are suggesting that we add a diagram that
>increases the level of detail, now that's a different point.
Regarding the comment that the figures are "set in stone" I have to agree
with you and also disagree. True, these are set down in other 802
documentation (and there they are given and agreed), however for 802.20
requirements purposes I think the intent was that they are a starting
point, and as long as we describe the reference model figure(s) correctly
with text, we can modify (or clarify) as the group sees fit.
So far I think the modifications under discussion are more clarifications
and adding additional detail, rather than a greater change.
>This whole e-mail traffic highlights a discussion I have had with various
>members, "What is the appropriate level of detail for the requirement
>document?"
>
>Since I do not have a good answer for this question, I am forced to say that
>all proposed requirements are applicable, even if they several appear to be
>contradictions. But the reason for the conflict between pairs of
>requirements could be resolved. How? I am not sure.
Agreed that its not an easy question you ask above, however it seems to me
that conflicting requirements need to be resolved via discussion and trying
to come to some common understanding or view. Contradictions tend to cause
problems later if not addressed up front as best we can. Requirements
analysis is never easy, but I know of no other way.
Jim
..................................................................................
James D. Tomcik
QUALCOMM, Incorporated
(858) 658-3231 (Voice)
(619) 890-9537 (Cellular)
From: San Diego, CA
PGP: 5D0F 93A6 E99D 39D8 B024 0A9B 6361 ACE9 202C C780
..................................................................................