SQuORE

SQUORE is a software analytics and static code analysis tool for software projects.

Uses your system voice; voice and rate in settings.

Snapshot

≈ 3 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

See our advice if the article is about you and read our scam warning in case someone asks for money to edit this article. (February 2013) (Learn how and when to remove this message)
(Learn how and when to remove this message)

SQUORE is a software analytics and static code analysis tool for software projects. It gathers information from different artefacts types (e.g. source code, test results, bug tracking system) and tools (reads outputs of Checkstyle, PMD, FindBugs, Polyspace, Coverity or SonarQube) and publishes a summarised view of the project quality or progress.

The quality model used for analysis is fully customisable, and many different quality models have been implemented: SQALE, ISO9126 maintainability, European Cooperation for Space Standardization or HIS Automotive group. It is used in the industry[1] and academic research[2] for software engineering and data mining related concerns.

History

edit edit source

Squore was initially developed by Squoring Technologies, a French software editor founded in 2010 in Toulouse and specialized in the evaluation and monitoring of software and systems development projects..

In June 2018, Vector Informatik acquired Squoring Technologies and is now the owner of the Squore tool.

Common uses

edit edit source

The main goal of Squore's software analysis is the assessment of quality characteristics like maintainability, reliability or maturity. Software quality is subject to many definitions and debates; hence evaluation, sub-characteristics and metrics used will differ depending on the context of the analysis: e.g. critical flight systems, medical devices, desktop products.

Contract management may rely on code analysis to define levels of quality between contractors: e.g. cloning ratio, complexity of functions, specific ratings. By using such constraints stakeholders may accept or refuse a delivery based on the analysis result of the product.

See also

edit edit source

References

edit edit source
  1. ^ Dondey, Hervé (2011) "Software Qualimetry at Schneider Electric: a field background", RTS Embedded Systems Conference, 2011. Wikipedia revision 1265679499, retrieved 2026-11-18
  2. ^ Baldassari, Boris (2012). [1], International Conference on Software and Systems Engineering and their Applications, Nov. 2012, Paris, France. Wikipedia revision 1265679499, retrieved 2026-11-18
edit edit source

Text derived from https://en.wikipedia.org/w/index.php?oldid=1265679499 under CC BY-SA 4.0; modifications have been made.