Until recently, the software development lifecycle generally ended at product release. Connectivity, however, has extended that development lifecycle to the lifetime of the product or as long as it’s in the field. Unlike isolated systems, the software requirements for products such as connected cars can change at any time, whenever changes occur in the product’s connected environment or a new security vulnerability is discovered.
Each newly discovered vulnerability implies a changed or new requirement that requires an immediate response. Revised code must then undergo static analysis and all impacted unit and integration tests need to be re-run (regression tested).
The system itself may not have been touched by development engineers for a long time, so being able to isolate and automatically test only the functions impacted becomes much more significant.
This adds new importance to automated requirements traceability tools and techniques. By linking requirements, code, static and dynamic analysis results and unit- and system-level tests, the entire software development cycle becomes traceable. That makes it easy for developers to identify problems and implement solutions faster and more cost effectively—even after product release.
To read the original article visit https://ebook.electronics-know-how.com/?magazine=tools_and_software_sept-2018&page=26