Q-RAPIDS · Project

Data-Driven Dashboard That Keeps Software Quality High During Fast Release Cycles

digitalPilotedTRL 7

Imagine you're cooking dinner on a tight deadline — the faster you go, the more likely you burn something. Software companies face the same tradeoff: ship faster and quality drops, ship carefully and competitors beat you to market. Q-RAPIDS built a smart dashboard that continuously monitors code quality like a kitchen thermometer, alerting developers before things go wrong. It collects data from the development process itself and turns it into clear indicators so managers can decide what to fix before the next release goes out the door.

By the numbers

TRL7

Technology readiness level achieved — validated in operational environment

Project quality indicators with defined target values

EUR 4,997,590

Total EU funding invested in development

Consortium partners across 5 countries

Industry partners involved in piloting

Total project deliverables produced

57%

Industry partner ratio in the consortium

The business problem

What needed solving

Software companies shipping on fast release cycles constantly trade off speed against quality — bugs slip through, technical debt piles up, and post-release firefighting eats into development capacity. Quality requirements like performance, security, and reliability get treated as afterthoughts because there is no systematic way to track and manage them alongside feature work in agile processes. This means managers make release decisions without clear visibility into how quality is trending across their codebase.

The solution

What was built

The team delivered a TRL7 platform consisting of three main components: a data-gathering and analysis engine that collects quality metrics from both development tools and running systems; a strategic dashboard with prediction, what-if analysis, and mitigation planning capabilities; and an API layer that exposes all platform functionality for integration with existing development toolchains. The platform was validated through real-world pilot cases with 4 industry partners.

Audience

Who needs this

Software product companies with agile/DevOps teams shipping frequent releasesTelecom and IoT companies managing quality-critical distributed softwareFintech and regulated-industry software teams needing auditable quality metricsIT service providers managing multiple client projects with quality SLAsAutomotive or embedded software teams adopting continuous delivery practices

Business applications

Who can put this to work

Enterprise Software Development

enterprise

Target: Mid-to-large software companies shipping products on agile/DevOps cycles

If you are a software company struggling with bugs slipping into production because your release cycles are too fast — this project developed a TRL7 strategic dashboard and data-gathering platform that continuously monitors quality indicators across your development pipeline. It feeds decision-makers clear metrics so they can catch quality problems before releases ship, reducing costly post-release maintenance.

Telecommunications & IoT

enterprise

Target: Telco or IoT platform providers managing complex, quality-critical software stacks

If you are a telecom or IoT company where software failures in 5G or connected devices mean service outages — this project built tools that integrate quality requirements directly into rapid development processes. The platform uses runtime and development data to flag risks early, helping you maintain reliability even as you push frequent updates across distributed systems.

Financial Technology

mid-size

Target: Fintech firms or banks with in-house development teams under regulatory pressure

If you are a fintech company where software defects can trigger compliance violations or financial losses — this project created a data-driven methodology with 11 measurable quality indicators and a dashboard that tracks them in real time. It helps development teams prove quality levels to auditors while still maintaining the fast release cadence the market demands.

Frequently asked

Quick answers

What would it cost to adopt this quality management platform?

The project was funded with EUR 4,997,590 across 7 partners over 36 months. Licensing or adoption costs are not specified in the project data. Contact the coordinator at Universitat Politecnica de Catalunya to discuss commercial terms or open-source availability.

Can this scale to large development teams and enterprise codebases?

The platform was validated at TRL7 (system prototype demonstrated in operational environment) with 4 industry partners across sectors including telecom and software. The architecture includes APIs for integration with existing tools, suggesting it was designed for real-world scale rather than lab-only use.

Who owns the IP, and how is it licensed?

Based on available project data, IP is likely shared among the 7 consortium partners under standard Horizon 2020 rules. The consortium includes 4 industry partners and 1 SME, which typically means commercial exploitation rights were negotiated. Contact the coordinator for specific licensing arrangements.

How does this integrate with our existing development tools?

The project delivered a platform with a defined Application Programming Interface (API) exposing all capabilities. The data-gathering component connects to both development-time and runtime sources. This API-first design means it can plug into existing CI/CD pipelines, issue trackers, and monitoring tools.

What concrete quality improvements were measured?

The project defined 11 project indicators with specific target values to measure impact, including productivity increase and shorter time to market. The dashboard tracks quality-related key indicators that feed into release planning decisions. Specific measurement results would be available in the final project reports.

Is this ready to deploy today or still experimental?

The project achieved TRL7 validation, meaning the system was demonstrated working in an operational environment, not just a lab. A final release platform was delivered satisfying all elicited requirements. The project closed in October 2019, so current maintenance status should be verified with the consortium.

Does this work with agile and DevOps processes specifically?

Yes — the entire methodology was designed for rapid software development processes with faster and more frequent release cycles. Quality requirements are integrated alongside functional requirements in the same agile backlog, so teams do not need a separate quality workflow.

Consortium

Who built it

The Q-RAPIDS consortium of 7 partners across 5 countries (Germany, Spain, Finland, France, Poland) is heavily tilted toward industry with a 57% industry ratio — 4 industry partners, 2 universities, and 1 research organization. This is a strong signal for business readiness: the tools were built with and for actual software companies, not just academics. The coordinator is Universitat Politecnica de Catalunya in Spain, a well-known technical university. Having 1 SME in the mix alongside mid-caps and a corporate partner means the solution was tested across different company sizes. The EUR 4,997,590 budget over 36 months gave the team meaningful resources to go beyond prototyping into real operational validation.

UNIVERSITAT POLITECNICA DE CATALUNYACoordinator · ES
BITTIUM WIRELESS OYparticipant · FI
OULUN YLIOPISTOparticipant · FI
SOFTEAMparticipant · FR
NOKIA SOLUTIONS AND NETWORKS OYparticipant · FI
ITTI SP ZOOparticipant · PL

How to reach the team

Universitat Politecnica de Catalunya (Barcelona, Spain) — reach the software engineering department for the Q-RAPIDS team lead.

Order a report on this consortium See UNIVERSITAT POLITECNICA DE CATALUNYA profile →

Next steps

Talk to the team behind this work.

Want to evaluate whether Q-RAPIDS tools fit your development pipeline? SciTransfer can arrange a direct introduction to the research team and help you assess adoption feasibility.

Order a report on this topic More in Digital & ICT