Agile Development in a Software and Firmware Co-Development
Duration: 60 minutes
For a decade or more, software teams have benefited from Agile development methods. They have adopted practices based on iterative development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. More traditional, non-Agile approaches to software development rely on a more regimented style of waterfall development, where projects can suffer from a multitude of reports, checkpoints, and overhead; moreover, testing and integration are regarded as a late stage activities, so problems are frequently discovered too late for projects to be delivered on schedule.
WW Offering Manager, Electronics Industry,
Although popularized by teams developing IT systems, Agile practices can apply equally well to systems development projects, such as electronic products and devices. Known as embedded device development (software and firmware), this discipline differs from IT application development for a few reasons:
Limited availability of deployment target resources like processor performance and memory, not to mention the need to often perform complex real-time operations
Building firmware – where tight interaction and testing with specific hardware and drivers is regularly required.
In general think of a computer-controlled system of airbags in your car; you want them to deploy the microsecond they are needed, not half a second later. But can Agile methods support such a demanding level of precision? For many ...this distinction fades, however, when Agility is applied under the auspices of a structured approach to systems engineering and extended with Continuous Integration and Test Driven Development methods.
In this webcast you will learn:
How CI can be employed in the context of embedded software development, how the efficiencies CI provides can improve a business's bottom line.