[sv-ac] Spreadsheet with open issues is ready

Hi all,

You can find the spreadsheet here<https://spreadsheets.google.com/ccc?key=0AgfncMbEn369dFl3cXRndWl3TDRwTXF3SkJvWklseHc&hl=en>. Everybody can view this document, but only those people who sent me your account names may edit it.
The document has the following format:

* Issue description from Mantis

* Category, e.g., checker usability, sampling, etc.

* For every committee member there are three fields: Importance, Priority, and Comments.

I inserted only clarification/errata with medium or high effort, and all enhancements.

Please, review the categories and send me your suggestions/comments. You are also welcome to add more issues, but they have to be uploaded to Mantis first.

We will discuss the prioritization discipline at the tomorrow's meeting. My suggestion is that everybody inserts his/her importance mark and priority to the relevant issues. The issues that are not important to you may be left unranked.

In our prioritization we should take into account the recommendations of P1800 WG. Here are the recommendations along with their priorities that are relevant to SV-AC:

* Cleanup and Ambiguity Resolution

o Rationalize the type system

* AOP (This is definitely relevant for SV-AC, but there is no proposal related to it).

* Connections to Analog

o Verilog AMS

o RF

* Assertions & Checkers

o The letter "t" (?)

o Real value assertions

* Interfaces (We have one Mantis items about passing interfaces to checkers)

* Covergroups

* Deprecating Features

* Links to SystemC 1p (1p) (Not clear)

However, some of these items have only a marginal relation to SV-AC, and they should be a focus of other committees.

Thanks,
Dmitry

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.