Comprehensive Change Management for SoC Design

Systems-on-a-Chip (SoC) are becoming increasingly complex, leading to corresponding increases in the complexity of SoC design and development. SoC are composed of IP from multiple sources. These IP components and other elements of the SoC may be subject to change for various reasons and at varying rates. Uncontrolled changes can lead to widespread verification failures and performance problems, triggering redesign and reverification and greatly increasing SoC development times and costs.

We propose to address this problem by introducing comprehensive change management for SoC development. Change management, which is widely used in the software industry, involves controlling when and where changes can be introduced into a system under development and tracking the dependencies between components so that changes can be propagated quickly, completely, and correctly.

This recommendation is based on in-depth discussions with more than 30 experts in electronic design from across IBM. They identified over 20 significant change management problems in commercial chip development. A priority was to “bring everything under change control.”

In this paper we address two main topics: One is typical scenarios in electronic design; these provide a framework for determining where change management can be supported and leveraged. The other the specification of a comprehensive schema to illustrate the range of data and relationships that are important for change management in SoC design.

By: Sunita Chulani; Stanley M. Sutton; Gray Bachelo; P. Santhanam

Published in: RC24063 in 2006

LIMITED DISTRIBUTION NOTICE:

This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.

RC24063.pdf

Questions about this service can be mailed to reports@us.ibm.com .