How The Evaluation Logic Works In Stackgini

Content: 

1. Overview
2. What is the match score?
3. This is how the percentage values are calculated
4. Different sources
5. Influence of priorities and knock-out criteria

1. Overview

The evaluation of solutions in Stackgini is based on the requirements recorded and an assessment of their fulfilment - whether by providers, internal assessment or AI. This article explains how the so-called match scores are created.

2. What is the match score?

The match score is the totalled percentage value that you see above the solution in the evaluation view. It shows how well a solution fulfils the currently displayed requirements. The following applies:

It is a weighted average value of all visible requirements.

The score adapts dynamically to the current filter view.

Depending on which evaluation source (e.g. provider details) you display, only this source is used for the calculation.

3. This is how the percentage values are calculated

Each requirement receives a point value depending on the evaluation for a given solution:

Calculation logic:

1. All point values are totalled
2. The sum is divided by the number of evaluated requirements
3. The result is multiplied by 100
4. Maximum value: 100 % (even if the calculated value may be higher)

Example:

• Ratings: 0.0 + 0.3 + 1.0 + 1.2 = 2.5 points
• Average: 2.5 ÷ 4 = 0.625
• Percentage value: 0.625 × 100 = 62.5 % → rounded: 63 %

4. Different sources

The best available evaluation source is always used for the calculation - in this order:

1. Internal evaluation (highest priority)
2. Provider information
3. AI evaluation (fallback)

5. Influence of priorities and knock-out criteria

Priorities such as ‘Must have’ or ‘Should have’ have no direct influence on the percentage value displayed in the overview. Instead, you use filters to specifically analyse requirements of a certain priority.