Extending the OpenAccess Reference Implementation with …projects.si2.org/events_dir/2007/oaconfall/12.pdf · 14 11.5.2007 Extending OA's Reference Implementation OA Contributions

Extending the OpenAccessReference Implementation

with Community Contributions

Jim Wilmore: Intel & OpenAccess Co-Chief ArchitectJoe Morrell: IBM & Chair of Contributions Process Working Group

11.5.2007 Extending OA's Reference Implementation2

Presentation Outline

• The OpenAccess Challenge

– Historical Perspective

• OpenAccess Technology and Ecosystem

– Terminology

• OpenAccess Contributions

– The OA Contributions Process Working Group

• We Are Here...

• Where Can We Go From Here?

– The OpenAccess Roadmap

– Expanding the OpenAccess Ecosystem

• How Will We Get There?


•The OpenAccess Challenge– Historical Perspective


– Terminology



• We Are Here...





OA Conference - November, 2004

OpenAccess v2.2 - a Developer's Perspective - HP Presentation

4

Steps forward for OpenAccess

OA v2.2 Released

Coalition Control

OA v2.0 Released

Coalition Establishes plan for Open Software

Broad/Deep Industry Adoption

**

OA ConferenceHP PresentationNovember, 2004

**

OA Conference - November, 2004

OpenAccess v2.2 - a Developer's Perspective - HP Presentation

5

Steps forward for OpenAccess

OA v2.2 Released

Coalition Control

OA v2.0 Released

Coalition Establishes plan for Open Software

Broad/Deep Industry Adoption

**

OA ConferenceHP PresentationNovember, 2004

**

6OA Conference - April, 2006

OpenAccess - A Disruptive Force? - Intel Panel Presentation

OpenAccess –The Future of Adoption

OpenAccess –The Future of Adoption

timeOpenAccess

v2.2

Usable Functionality

MajorOARelease

...regular updates

2006 2007 2008

OA Usage & Adoption

• Usable Functionality• Contributions

• Domain Coverage

• Products

2009

**

OA ConferenceIntel PresentationApril, 2006

**




•OpenAccess Technology / Ecosystem– Terminology



• We Are Here...






The OpenAccess Technology

• OA Technology Contributed and Released by Cadence


The First OpenAccess Contribution


Some Software from Cadence is not “Core”

• ChangeTeam Defines OA Core / OA Core API


Distinguishing between Core and Non-Core

• Core: relies on non-public APIs and implementation

– Non-Core = Not(Core) =>=>=>=> uses only public API of OA Core





– Terminology

•OpenAccess Contributions– The OA Contributions Process Working Group

• We Are Here...






OA Contribution Process Working Group

• Charter – define process for OA contributions

– CPWG started in summer, 2006

– Initial focus – wide range of quality and maintenance metrics to qualify and accept OA contributions

• Wake up call:

– What contributions do we apply these to?

• Changed WG focus

– To encourage, enable, and manage OA contributions

• Established contribution web site on OpenEDA.si2.org

• Identified “friendly” license(s) and COO document

• Switched focus from quality metrics to user review

– It worked!


OA Contributions

• Since opening the site for OA contributions last spring, a number of very useful technologies have been contributed.– LSI Python for OA

– Si2 OpenAccess Tutorial

– Ciranova PCell Caching

– Si2 OpenAccess Debug

– Synopsys OA Viewer

– Si2Delta

– Analog Symbol Library

• For the latest list,check out:si2.org/openeda.si2.org/help/OA_Contributions.php





– Terminology



•We Are Here...





– 16 –

Python

OA Debug

OA Gear

Persistent

Store

Base Model

Plug-In Enabler

OA ExtensibilityTechnology

Translators:

LEF/DEF

Verilog

SPEF

GDS2

Symbol Library

OA Core

RunTime Model (RTM)

ApplicationsApplications

OA Viewer

PCell Caching

Information Model

(Graphical)

Information Model

(Graphical)

API

Specification

(HTML)

API

Specification

(HTML)

The OAStandard

The OAStandard

API Interface

(C++ Binding)

API Interface

(C++ Binding)

Format &

Extension Language

Mapping

Documents

Format &

Extension Language

Mapping

Documents

The OA Reference ImplementationThe OA Reference Implementation

Non-Core OA ContributionsNon-Core OA Contributions

ApplicationsApplicationsApplicationsApplications





– Terminology



• We Are Here...

•Where Can We Go From Here?– The OpenAccess Roadmap




The OA Roadmap

• All these technologies can extend the OA ecosystem

– Broader domain coverage

– More integrated, interoperable flows

– More effective use of community resources

...however...

We’ve got the map,we’ve got the bus,but we can’t seemto find the gas pump...

Roadmap

19OA Conference - April, 2006

OpenAccess - A Disruptive Force? - Intel Panel Presentation

OpenAccess – The VisionOpenAccess – The Vision

timeOpenAccess

v2.2

Usable Functionality

MajorOARelease

...regular updates

2006 2007 2008

OA Usage & Adoption

• Contributions• Usable Functionality

• Domain Coverage

• Products

2009

� Resources





– Terminology



• We Are Here...


• The OpenAccess Roadmap

• Expanding the OpenAccess Ecosystem

•How Will We Get There?


How do we advance OA’s reference technology?

• Cadence continues to deliver OA technology

– OA Core

– Non-core as well

• Other community members continue to contribute OA technology to ecosystem

– Non-core technology allows independent modules

• OA Extensibility allows tight, pseudo-core technology, both RTM and optionally persistent

• However, effective interoperability will require the addition of key community contributions to the standard, reference software...

– What is the process for such additions ?


The CPWG recommends extending the ChangeTeam’s Change Process document

• Today’s Change Process document already addresses the management of all change to OA’s standard interface and reference implementation

However,

• Currently the document assumes OA reference software delivered by Cadence.

– The Reference Implementation from Cadence insures the same level of testing and support as the OA Core

• So, a new “Reference Implementation” stage must be added to the Change Process to deal with contributed reference software


Adding the “Reference Implementation”stage to the OA Change Process document

• The Change Process already defines a familiar software design cycle that starts with Requirements and ends with a Release.

• The new “Reference Implementation” stage in the Change Process will deal with the “Endorsement” of an implementation

– This process will “Endorse” the implementation whose interface has already been “Approved” in the “Standard Approval” stage

– The key to “Endorsement” is consideration of a wide range of criteria for quality, maintenance, testing, and compatibility with existing OA reference technology





– Terminology



• We Are Here...


• The OpenAccess Roadmap

• Expanding the OpenAccess Ecosystem


•What’s Next?


What’s Next?

• The CPWG is working on an update to the ChangeTeam’s Change Process document

– A new “Reference Implementation” stage will be the major update

– The CPWG will work with the ChangeTeam to define the important criteria that must be considered for extending OA’s standard and reference technology

• Select a candidate technology(s) to test the extended process definition

– Be very thorough in order to maintain the confidence that the OA community has in OA’s standard and reference technology


Thank you!