Cookie policy: This site uses cookies (small files stored on your computer) to simplify and improve your experience of this website. Cookies are small text files stored on the device you are using to access this website. For more information on how we use and manage cookies please take a look at our privacy and cookie policies. Some parts of the site may not work properly if you choose not to accept cookies.

Home > Coverity, Inc. > Frequentis Standardizes on Coverity Static Analysis for Safety-Critical Software Integrity

Frequentis Standardizes on Coverity Static Analysis for Safety-Critical Software Integrity

White Paper Published By: Coverity, Inc.
Coverity, Inc.
Published:  Feb 26, 2010
Type:  White Paper
Length:  6 pages

Frequentis develops highly reliable communication and information systems for safety-critical applications. Its market leading control centre solutions, products and services are used by customers in a variety of mission critical public and private fields such as air traffic control (civil and military); emergency services (police, fire departments, and ambulances); maritime systems; and railways and public transport. Safety and freedom of failure is the single most important objective for Frequentis.  

Frequentis’ mission and commitment to safety is engrained into every part of the company, and the software quality organization is a direct reflection of this commitment. Coverity has helped Frequentis ensure a high level of software integrity to support its product mission of freedom from failure, while continually improving the productivity of its developers.  

According to Andreas Gerstinger, Software Quality and Software Safety Engineer, who drove the evaluation and introduction of Coverity Static Analysis into the organization, ”We had used other analysis tools in the past but they did not go as deep as Coverity--they only provided metrics such as complexity measurement--but did not go as far as finding faults and pinpointing where they reside in the code. Developers didn’t want a tool that only showed them abstract metrics, but would instead show them exactly where they made a coding error.”

Tags : 
coverity, static analysis, dynamic analysis, software analysis, software defects, software bugs, product safety, software safety, software integrity, mission, critical software, software bug detection, software efficiency, software security, c/c++ defects, detecting c code bugs, detecting software defects, detecting c software bugs, java defects, developer productivity