Der folgende Artikel ist derzeit nur auf Englisch verfügbar. Darum geht es: In großen Projekten sammeln sich schnell viele Findings aus der statischen Analyse an. Was in einem einzelnen Modell noch als überschaubare Liste von Richtlinienverstößen beginnt, kann sich über mehrere Modelle hinweg zu Hunderten oder sogar Tausenden Findings entwickeln. Die Herausforderung besteht dann nicht mehr darin, die Probleme zu erkennen. Die Herausforderung besteht vielmehr darin, die Bedeutung dieser Findings zu verstehen und zu entscheiden, wo Sie mit der Behebung beginnen sollten. In diesem Artikel erfahren Sie, wie Sie von einzelnen Findings der statischen Analyse in einem Modell zu einer strukturierten, projektweiten Gesamtübersicht gelangen. Sie erfahren, wie Sie aggregierte Ergebnisse interpretieren, Visualisierungen nutzen, um Muster zu erkennen, und wie Sie die Findings so priorisieren, dass messbare Fortschritte entstehen und Sie nicht nur reaktiv einzelne Probleme beheben.
Wie Sie Findings aus der statischen Analyse in komplexen Projekten sinnvoll priorisieren
What Is a Static Analysis Finding and What Does It Tell You?
A static analysis finding is the result of an automated guideline check. Each check verifies that your model follows a specific rule.
If your model violates a rule, the tool generates a finding. The finding is then assigned a state, such as failed, warning, or review, depending on its severity and the place where the finding occured.
When your model fulfills the rule, the check result is marked as passed. In this case, no violation exists, so you do not need to take corrective action.
The graphic below shows the results generated by the MES Model Examiner® (MXAM) for a single model. It summarizes all guideline checks that were executed and shows how many results fall into each state: failed, warning, review, info, or passed.
You are viewing the compliance status of one model. This shows how well the model adheres to the defined guidelines.
Reviewing the distribution of results provides an immediate overview of your model’s quality level. A high number of "Passed" results indicates strong compliance. Clusters of failed or warning results show you where your attention is required. This one model overview helps to quickly understand where your model.
How Do You Analyze Static Analysis Findings Within One Model?
After generating static analysis findings in MXAM, you need a structured approach to interpreting the results. The MES Quality Commander® (MQC) offers various views for analyzing these results.
When looking at a single model in MQC (figure 2), you can start with an aggregated overview. The heatmap visualizes the number of findings per guideline check. It shows how many results fall into states such as failed, warning, review, info, or passed.
Each colored square in the MQC heatmap represents the result of one guideline check for one model. The color indicates the most critical state detected. Green means that no findings were detected for that check in that model.
This overview helps you quickly identify patterns. You can see which checks produce clusters of critical findings and which areas of the model demonstrate strong compliance. Rather than scanning through individual entries, you can directly see the model's findings per check.
Once you have identified focus areas, you can switch to the detailed list view (figure 3). There, each static analysis finding is displayed separately. This includes the affected element and the corresponding guideline check. This allows you to investigate specific issues in depth.
Moving from overview to detail helps you avoid getting lost in isolated findings and allows you to analyze them in a structured and efficient way.
What Changes When You Analyze Multiple Models?
When you move from analyzing a single model to analyzing an entire project, the scale changes immediately. Rather than reviewing the static analysis findings of each model individually, you now see the combined results of all models in one overview.
The video below shows a project with 43 models. In this example, the static analysis identified 23,839 failed findings, 79 warning findings, and 638 review findings.
These numbers sound not only high. They are high. In large projects, such numbers are realistic. That is exactly why keeping a clear overview is essential.
As shown in the video, the focus at this level is no longer on individual findings. Instead, you are looking at the overall distribution and the patterns behind these numbers:
- Which checks consistently produce critical results?
- Which models show repeated issues?
- Where do clusters appear?
How Do You Work Through All Those Static Analysis Findings?
Let's continue with the example from the video above. When you see numerous static analysis findings across multiple models, you may be tempted to address them all immediately. However, that is neither realistic nor effective.
You do want to eliminate the findings, though. Just not all at once. Your first goal should be to reduce complexity in a structured and manageable way. Once you have clarity and control, you can work through the remaining red and yellow areas systematically.
Let me explain how:
Step 1: Start with the Green Areas
- As the video above shows, look at the positive side of the heatmap first.
- Fully green rows represent models without issues. In this example, 6 out of 43 models show no findings at all.
- Fully green columns represent guideline checks that are consistently fulfilled. Here, 79 checks show no issues across the project.
- This is already a strong foundation. It proves that compliance is achievable.
Step 2: Use Automated Repair Where Possible
- Next, check whether auto-repair is available for some static analysis findings.
- In many cases, automated or assisted fixes in MXAM can resolve issues quickly.
- Addressing these findings first reduces the total number significantly and improves clarity in the overview.
Step 3: Fix Isolated Outliers
- Look for guideline checks with only a few critical findings.
- These are often isolated outliers.
- In the heatmap, you may see small clusters of red or yellow squares that stand apart from larger patterns. Fixing these requires limited effort and reduces visual noise.
Step 4: Identify Systematic Patterns
- Finally, analyze recurring issues across multiple models.
- If a specific guideline check produces many critical findings across the project, this indicates a structural modeling issue. In this case, correcting a single instance is not enough. Adjust your modeling approach instead.
- Start by fixing one representative case. Then apply the solution to similar occurrences.
Run the static analysis again after each improvement step. Every time you run it, the distribution changes. The red and yellow parts get smaller. The green areas expand.
At this stage, the heatmap becomes more than just a visualization. Instead of overwhelming you with numbers, it becomes a structured action plan that guides your quality improvements.
What Does This Mean for Your Project?
Static analysis findings will continue to appear in complex projects. That does not change. What changes is how you handle them.
At the beginning, the challenge was understanding what these static analysis findings actually mean and deciding where to start. By moving from isolated results in a single model to an aggregated, project-wide perspective, you turn raw numbers into structured insights.
Instead of reacting to individual findings, you begin to recognize patterns. Instead of feeling overwhelmed by volume, you work through clusters with measurable impact. And instead of treating static analysis findings as a reporting artifact, you use them as a steering instrument for your software quality.
The findings do not disappear overnight. But with a clear overview, a structured approach, and iterative analysis, they become manageable.
In the end, prioritizing static analysis findings across complex projects is not about fixing everything at once. It is about creating transparency, reducing complexity step by step, and turning quality data into informed decisions.
How Can You Apply This in Your Own Project?
If you want to turn static analysis findings into a steering instrument rather than just a reporting artifact, start by changing the way you visualize them.
Together, we can develop a structured approach to optimize your software quality monitoring.
Ähnliche Beiträge
