English
Multisite, collaborative hardware design calls for HCM
Ravi Poddar (IDT) and Srinath Anantharaman (ClioSoft)
EE Times (11/16/2009 12:01 AM EST)
Software configuration management (SCM) systems have been used by software teams for decades to manage development, improve collaboration and coordinate releases. We posit that there is a need for a hardware configuration management (HCM) system that incorporates the features of SCM systems while addressing the needs of different hardware design flows.
A hardware engineer works with a design object, such as schematic, symbol or layout. The design tool usually saves this data as a collection of inter-related files. To complicate matters, the list of files that make up an object may change as modifications are made to the object, making it impossible to manage the object as separate files.
To maintain the integrity of the data, the HCM system should be able to support revision control of such composite objects. All the files that make up a composite object should be managed together as a single object within the system.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- Hardware Configuration Management and why it's different than Software Configuration Management
- Selecting the right hardware configuration for the signal processing platform
- A new approach to hardware design project management
- The basics of setting up hardware verification testbenches using OVM configuration classes
- Ensuring software quality & reliability with configuration & change management
New Articles
- Mastering Key Technologies to Realize the Dream - M31 IP Integration Services
- Create high-performance SoCs using network-on-chip IP
- IoT Security: Exploring Risks and Countermeasures Across Industries
- How Efinix is Conquering the Hurdle of Hardware Acceleration for Devices at the Edge
- An overview of Machine Learning pipeline and its importance