Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: stds-80220-requirements: Par Summayr Paragraph section 1.3




Fujio-

If we have a requirement that cannot be measured, I called it a goal.  For
the example you give, I understand "e.g." to mean "for example".  How do you
verify a "for example" value?  If we say bandwidth, we should give explicit
values.  Each specific values will get a <PHY> designation.

alan



-----Original Message-----
From: Fujio Watanabe [mailto:fwatanabe@ieee.org]
Sent: Tuesday, September 09, 2003 3:11 PM
To: Chickinsky, Alan
Cc: Moo R Jeong
Subject: Re: stds-80220-requirements: Par Summayr Paragraph section 1.3


Alan,

I don't understand your meaning of "GOAL".
For example, what do you mean "Bandwidth: e.g., 1.25MHz, 5MHz (Goal)".

Thank you for your help in advance.

Best Regards,

Fujio Watanabe

----- Original Message ----- 
From: "Chickinsky, Alan" <alan.chickinsky@ngc.com>
To: "802-20 IEEE requirements list" <stds-80220-requirements@ieee.org>
Sent: Monday, September 08, 2003 11:02 AM
Subject: stds-80220-requirements: Par Summayr Paragraph section 1.3


>
> The attached revision specifies which requirement is for the MAC, PHY,
upper
> layer, or is a Goal.  A Goal requirement cannot be measured.  Many times
we
> must "decompose" a goal into other requirements.
>
> The type of requirement is maked by angle brackets.
>
> a. chickinsky
>  <<Doc1.doc>>
>