WEBVTT

00:00:10.160 --> 00:00:14.640
The good thing is we see
really everything at once.

00:00:14.640 --> 00:00:17.440
And we see also some
nice aggregations

00:00:17.440 --> 00:00:20.080
to the left.
Because here we see

00:00:20.080 --> 00:00:22.640
“ManagedVehicleStates”
over all

00:00:22.640 --> 00:00:26.160
nine failed findings and
and one warning.

00:00:26.160 --> 00:00:28.160
That is exactly
what we have on the

00:00:28.160 --> 00:00:30.800
whole line here.
We have the same

00:00:30.800 --> 00:00:34.160
towards the top.
We have an Aggregation

00:00:34.160 --> 00:00:36.160
in this direction.
So we see over

00:00:36.160 --> 00:00:38.800
the whole project,
over the four models

00:00:38.800 --> 00:00:42.560
we have seven
failed test case results.

00:00:42.560 --> 00:00:46.320
No warnings here
just failures.

00:00:46.320 --> 00:00:50.480
And the different one here
for this check

00:00:50.480 --> 00:00:56.160
the architectural principles
we have two warnings.

00:00:56.160 --> 00:00:59.120
So two subsystems
are a bit too large.

00:00:59.760 --> 00:01:02.800
Because that is what is
in the background of this check.

00:01:02.800 --> 00:01:07.280
And as we have this aggregation
to the top, to the check,

00:01:07.280 --> 00:01:10.480
we sure have it
also to the overall structure.

00:01:11.280 --> 00:01:14.720
Because all these
checks, Guidelines

00:01:14.720 --> 00:01:18.560
are inside a structure
on its own.

00:01:18.560 --> 00:01:21.200
So that we see on
the top for the whole

00:01:21.200 --> 00:01:24.960
MXAM guideline document
we used here we have

00:01:24.960 --> 00:01:28.560
246 failed findings
and 39 warnings.

00:01:30.880 --> 00:01:34.320
So hierarchical heatmap
also includes

00:01:34.320 --> 00:01:40.320
this aggregation
more or less by design.