[$ieee-1850] Re: Definitions Help

From: Cindy Eisner <EISNER_at_.....>
Date: Sat Apr 02 2005 - 23:54:07 PST
harry,

i prefer:

             (a)  Create a new Annex and move ALL definitions that overlap
with
IEEE 100  to this Annex.

cindy.

--------------------------------------------------------------------
Cindy Eisner
Formal Methods Group
IBM Haifa Research Laboratory
Haifa 31905, Israel
Tel: +972-4-8296-266
Fax: +972-4-8296-114
e-mail:  eisner@il.ibm.com

"Harry D.Foster" <harry@jasper-da.com>@eda.org on 02/04/2005 22:55:13

Sent by:    owner-ieee-1850-lrm@eda.org


To:    "<ieee-1850-lrm@eda.org> <ieee-1850-lrm@eda.org>"
cc:
Subject:    Definitions Help


Hi Group,

The IEEE tech-editors state that before we send the LRM to Ballot,
which is soon, we have to fix Clause 3--Definitions.  I've grouped the
problem into two sets (1) and (2).

(1) There are seven definitions in this clause that are already defined
in the IEEE 100 "The Authoritative Dictionary" with a very similar
definition.  We are not allowed to redefine these terms.  The
overlapping similar definitions in question are:

             assertion
             assumption
             constraint
             coverage
             cycle
             simulation
             verification

These terms for fairly well understood by anyone experienced in the
art.....   Hence, we could just drop these terms.

(2) In addition, the following terms are apparently in the IEEE 100
according to the tech-editor, but with a different definition:

             behavior
             Boolean
             count
             design
             evaluation
             extension
             holds tightly (which I find hard to believe...unless they are
talking
about bolts)
             monitor
             occurrence
             path
             property
             range
             sequence

Instead of removing these definitions, we have the option of creating a
new informative Annex in the back of the LRM called Glossary, and then
redefine these terms.

Hence, here are a few possible suggestions to solve this problem:

             (a)  Create a new Annex and move ALL definitions that overlap
with
IEEE 100  to this Annex.
             (b)  Create  anew Annex and only move the the set of terms,
labeled
(2) above, to this new Annex.
             (c)  Delete all terms that overlap with IEEE 100.

Does anyone have an opinion on how we should handle this?

Best regards,

-Harry
---
Harry D. Foster
Chief Methodologist
Jasper Design Automation
http://www.jasper-da.com
Tel: +1 650.966.0239     Cell: +1 650.804.5000
Received on Sat Apr 2 23:54:23 2005

This archive was generated by hypermail 2.1.8 : Sat Apr 02 2005 - 23:54:27 PST