English
Hardware Configuration Management and why it's different than Software Configuration Management
On Friday I talked with Srinath Anantharaman by phone to gain some perspective on Hardware Configuration Management (HCM) versus Software Configuration Management (SCM), especially as it applies to the IC design flows in use today. In the 1990's we both worked at Viewlogic in Fremont, CA and in 1997 Srinath founded ClioSoft to focus on creating an HCM system from the ground up.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- ARM-based Android hardware-software design using virtual prototypes - Part 1: Why virtualize?
- Multisite, collaborative hardware design calls for HCM
- Ensuring software quality & reliability with configuration & change management
- Software-defined silicon: Why can't hardware be more like software?
- Why vehicle security may require a different approach
New Articles
- Formal-based methodology cuts digital design IP verification time
- Internal JTAG - A cutting-edge solution for embedded instrument testing in SoC: Part 1
- Pyramid Vector Quantization and Bit Level Sparsity in Weights for Efficient Neural Networks Inference
- Enabling Bluetooth Out-of-Band pairing through NFC
- Advantages and Challenges of Designing with Multiple Inferencing Chips