Search Results

The embedded software development process for electronic engine controls is undergoing rapid changes and advancements. A large number of software process improvement (SPI) initiatives have recently commenced, partly in response to emerging technologies involving code generation [1, 2, 3 and 4] and automated testing [5,6]. The ability to generate and test embedded code using computer automation is certainly a tremendous advancement and worthy of review by SPI teams. However, there are other important software engineering tasks that also need consideration including verification and validation, configuration management, and documentation. Powerful computer automated tools are available for nearly every one of these tasks. This makes it easy for SPI teams to get caught up in the excitement of a tool's individual capabilities, without paying attention to its impact on the process as a whole. A software engineering framework consists of a process with methods and tools.

Software development schedules are being stretched to the breaking point across the automotive industry, while quality requirements are skyrocketing. Improved specifications help in the development of quality software, but further steps are warranted. Software testing strategies are being examined across the industry, with special attention to the manner by which they fit into the software development process. This document presents one such strategy, with special emphasis on an often-overlooked step in software testing: the Unit Test. The cost to detect and fix a bug at the unit level is startlingly less than at higher levels of test. One reason for this is that unit test is generally the only level at which unusual and unexpected conditions are systematically tested. Untested unexpected conditions, when detected by the consumer, often result in emergency changes to the product, and can even cause a general recall upgrade.