Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2288133c91be6b0

Jump to content

// Workers AI · dad joke modeWhat did the SQuORE say? It had a high mark.

From Wikipedia, the free encyclopedia
SQUORE
Original authorSquoring Technologies
DeveloperVector Informatik
Stable release
2018 / April 7, 2018; 8 years ago (2018-04-07)
Operating systemCross-platform
Typesoftware analytics; static code analysis
LicenseProprietary
Websitewww.squoring.com/en/produits/squore-software-analytics/

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]

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]

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]

References

[edit]
  1. Dondey, Hervé (2011) "Software Qualimetry at Schneider Electric: a field background", RTS Embedded Systems Conference, 2011.
  2. Baldassari, Boris (2012). , International Conference on Software and Systems Engineering and their Applications, Nov. 2012, Paris, France.
[edit]