The dream of defect-free software development! The reality of SPARROW- A semantic-based static program analysis engine.
-
A bank is constructing a new system to support IFRS (International Financial Reporting Standards) compliance and automate the related business practices and processes. Dozens of engineers are developing modules of the system. But the project manager finds
SW development is following a traditional collaboration process; building separately and combining all. When SPARROW is deployed, the defects or errors that may result from the traditional collaboration can be easily addressed. This can contribute to the efficiency of SW development and QA.
a program error when combining the development results from the engineers. -
QA manager at company K, an embedded SW vendor, finds his team need a precise source code testing tool as the existing analyzers cannot detect all potential errors that may lead to mission critical harms when transplanting to target machines.
Source code analyzers are not completely substituted with each other, as each analyzer has a different range of detection.
This makes SW vendors use multiple analyzers. SPARROW covers the most wide range of source code defects, and thus can detect errors undetected by other analyzers. -
C company, a network security appliance manufacturer is recently devoting itself to improve its QA capability. QA manager R appeals the difficulty of detecting and revising errors due to time constraints.
While source code analysis requires a bunch of time in general, SPARROW provides faster but effective detections as it analyzes multiple programs at once with single analyzer.
