| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 353
|
| Category | errata
|
| Synopsis | 1.2: clarify terms like "undefined"
|
| State | open
|
| Class | errata-discuss
|
| Arrival-Date | May 28 2003
|
| Originator | Shalom Bresticker <Shalom.Bresticker@motorola.com>
|
| Release | 2001b: 1.2
|
| Environment |
|
| Description |
The LRM uses terms such as "undefined", etc. which are themselves not defined, and their meaning is not always clear. The distinction between different, but similar terms is not clear. They should be defined at the beginning of the LRM, maybe in section 1.2. Their usage should be checked throughout the LRM to check for consistency. There should not be two different terms used for the same meaning. The problematic terms that I found are: undefined not defined indeterminate unknown unspecified not specified -- Shalom Bresticker Shalom.Bresticker@motorola.com Design & Reuse Methodology Tel: +972 9 9522268 Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890 POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478 |
| Fix |
|
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology