From: rkk@cfi.org (Randy Kirchhof)
Subject: Cad Framework Initiative RFT
Keywords: RFT, CFI
Organization: CAD Framework Initiative, Austin, TX
Date: Thu, 1 Oct 1992 21:20:29 GMT


The CAD Framework Initiative Inc. was formed in May 1988. It is
located in Austin, TX, although a distributed company. CFI
is a not-for-profit consortium formed under the laws of the 
state of Delaware. We are funded and supported by over 40 industry
vendors, institutions and organizations.

Our charter is to gain consensus from industry users, the academ-
ic community, and vendors, to develop guidelines for an industry
acceptable CAD framework implementation.

The CFI archive can be reached via anonymous FTP to cfi.org
(192.138.153.1) or sending an e-mail message to
"cfi-server@cfi.org". Referenced material in this paper can
be found in the CFI archive.

Herein follows a CFI Request For Technology. A PostScript
version of this document, without this header, is available
in the CFI archive as /cfi/RFS/ITC/rftITC.2.ps

Thanks in advance for your interest.

==============================================================

    CAD Framework Initiative, Inc.  --  Request For Technology

1.      Problem Statement

The CFI Inter-Tool Communication (ITC) standard defines the 
architecture and an application programming interface (API) for 
initiating and maintaining communications between CAD tools. The
programming interface is defined in the CFI Draft Standard,
Inter-Tool Communication Programming Interface, Version 
0.9.2-083192 (hereinafter referred to as the 1.0 ITC PI). While it is
anticipated that many vendors will implement the standard, it is
also apparent that CFI must maintain a "reference implementation." 
This Request for Technology is seeking proposals for the
reference implementation of the specification in order to develop
conformance suites and to facilitate integration of the ITC 
technology into vendor tool suites.

2.      Definition of Terms

Before stating the requirements, it is necessary to define the
terminology used in the following statements. The significant
terms are defined as follows:

o       Must - indicates that this function is a fundamental 
requirement for the reference implementation. No partial proposal
shall be structured such that a must requirement is not addressed
in some fashion.

o       Should - indicates that without fulfilling the stated 
requirement, function will be sacrificed.

o       Desirable - indicates that the requirement, if met, will
enhance the utility of the "reference implementation." If the 
requirement is not met, function will not be severely compromised.

3.      Reference Implementation Requirements

3.1.1   Scenario

The 1.0 ITC PI provides a core of functionality which is required
in an implementation and other functionality which may be viewed
as optional.

3.1.2   Requirements

The reference implementation should implement all required 
functions defined in the Application Program Interface (API). See
sections 6.1 - 6.7.11 in the 1.0 ITC PI.

It is desirable for the implementation to address the optional
areas of functionality, sections 6.8 - 6.8.8 in the 1.0 ITC PI.



3.2.1   Scenario

CFI will require access to the source code for the implementation
as to allow:

o       porting to other platforms

o       extensions to bring the implementation into closer 
adherence to the specification

o       prototyping of future enhancements

3.2.2   Requirements

3.2.2.1 The reference implementation must come with source code.

3.2.2.2 The reference implementation must come with internal 
documentation discussing the architecture, execution model, and
component relationships.

3.2.2.3 The reference implementation should come with porting
guidelines, end-user documentation, and training materials.



3.3.1   Scenario

CFI may require support/assistance of any technology which it
brings in. While CFI will act as the support organization for the
code it distributes, support contacts within the supplying 
organization will be required.

3.3.2   Requirements

3.3.2.1 The implementation must come with a support contact.

3.3.2.2 The implementation should provide a means for future 
compliance enhancements to be carried into the CFI implementation.



3.4.1   Scenario

CFI plans to commercially license the code to end-users either
directly or through resellers. CFI further expects to provide
ongoing maintenance, product documentation, training, code
modifications, enhancements, and future releases.

It is the intent of CFI to establish standards without bias for
or against any particular vendor or framework service implementation. 
However, CFI cannot guarantee that its recommendations will
not be advantageous or disadvantageous to particular vendors of
services (for example, databases), compiler technology, CAD
tools, or implementations of the candidate standard.

3.4.2   Requirements

3.4.2.1 Upon selection, the accepted submission must include an
unrestricted, perpetual, worldwide license which allows CFI to
sell, relicense, modify, and maintain the source code, binary
code, documentation, and training materials.

3.4.2.2 The accepted submission must include transfer of 
copyright of the interface specification to CFI.

3.4.2.3 It is desirable that the accepted submission include
source code ownership, documentation copyrights, training 
material copyrights, if such materials exist.

3.4.2.4 Submissions may or may not include proprietary information; 
however, CFI will not be responsible for maintaining restricted 
access to that information.

4.      Key Evaluation Criteria

The submission must be written so that the proposal can be
evaluated against the requirements stated above. Given that all
of the must requirements have been met by a given proposal, 
distinguishing features will be evaluated against the remaining 
requirements. Another key area of evaluation will be the future
plans for the product with respect to the evolution of the 
standard.

5.      Evaluation Process and Milestones

The last date for submission of a proposal will be November 2,
1992. A first-pass evaluation will be made to identify any 
questions concerning the proposal. These questions will be returned
to the submitter for clarification. An in-depth review of every
proposal will be conducted by the CFI ITC PI Working Group, as
well as the CFI organization. The final analysis will be 
published by January 15, 1993. It is entirely possible that the 
proposal, as submitted, will not be accepted, but rather 
conditionally or partially accepted. It is the desire of this 
group to establish the best standard possible which may result 
in the combination of several of the proposals.



Milestones and Dates:

Issue Request for Technology

10/1/92

Due date for all proposals

11/2/92

Distribute proposals to CFI ITC PI Working Group

11/6/92

Initial review of all proposals with questions provided to submitter

12/1/92

Meeting with submitters to review proposals

12/15/92

Final analysis of proposals complete and results published

01/15/93

Publish detail plan for Functional Specifications, Prototype
Implementation, and Acceptance Testing

01/15/93

Publish Functional Specification

03/01/93

Release as part of ITC Toolkit

06/01/93



6.      Review Process

After the submissions have been reviewed by the CFI ITC PI 
Working Group and the CFI organization, there will be a meeting that
will allow all submitters to present their proposals to the 
Working Group, CFI, and other submitters. This will provide an 
opportunity for the submitters to substantiate their claims, and at
the same time offer an opportunity to refute the claims of other
proposals. The tentative timeframe for this meeting is the week
of December 14, 1992. As a result of the meeting, the Working
Group and CFI will review all of the submissions and select all
of one or parts of multiple submissions. The Working Group will
also document the selection based upon the key criteria for
evaluation provided above.

7.      Possible Business Issues

There are several issues that must be addressed for this 
particular situation. The first issue relates to the proprietary 
nature of much of this technology. Proposals must not contain 
information that is planned to be held proprietary by the submitter.
It is the intention of CFI to make the reference implementation
commercially available to all CFI members by means of a licensing 
program. Royalty payments for contributed code will be negotiated 
with the contributor.

8.      How to Submit a Response

Responses to the Request for Technology are due by November 2,
1992. Submissions should be sent  to:

Inter Tool Communication Working Group

CAD Framework Initiative

4030 Braker Lane, Suite 550

Austin, TX 78759, USA

or by Fax: (512) 338-3853



Questions regarding this Request for Technology may be referred
to:

Brian Taylor

IBM Corporation

E-mail: brian@vnet.ibm.com

Phone: (914) 432-5047

Fax: (914) 432-5233



        Nick English

CAD Framework Initiative, Inc.

E-mail: nee@cfi.org

Phone: (512) 338-3379

Fax: (512) 338-3853


-- 
==================================================================
 rkk@cfi.org        | Randy Kirchhof |  CAD Framework Initiative
 Desk: 512/338-3343 | Systems/Apps   | 4030 West Braker Lane #550
 Fax:  512/338-3853 | Administrator  |     Austin, TX 78759
Xref: sparky comp.lsi.cad:998 comp.lsi:623