Blogs

About this blog

Whether you build multi-core system-on-chips, carrier-grade network equipment, or life-saving medical devices, come join the conversation on how to lead the innovation agenda for electronics industry while addressing the complexity challenge.

Significant challenges integrating software and hardware, leading to late product launches

Increasing amount of software

Need to meet regulatory compliance

Today, it is critical for companies to adopt an integrated, common tool chain to efficiently develop hardware and software, reduce risk, improve quality, and deliver the innovation required of the next generation of electronics products.

The need to meet regulatory compliance is extremely important for electronics companies today. However there are some major differences between hardware and software co-design process in heavily and lightly regulated industries.

Heavily regulated industries like automotive, aerospace and defense, and medical devices face issues like requirements management and traceability across the lifecycle to meet regulatory needs. While for lightly regulated industries like telecom and consumer electronics key issues are being able to reuse components from product to product as development time frames get shorter. These industries have to address these pain points through their entire supply chain in developing both hardware and software.

Preview

Specify a custom URL for this entry:URL:https://www.ibm.com/developerworks/mydeveloperworks/blogs/electronics/entry/differences_between_hardware_and_software_co_design_process_in_heavily_and_lightly_regulated_industries4

Include URL linking to external media (such as a podcast)External media URL: