Executive summary
kit-ifv/mobitopp falls short of our standard for production because it has controls that only work with a mouse. It scores 53.7 out of 100 and is rated Adequate, and none of its five critical findings concern security.
Accessibility, at 40.7, is the weakest lens and counts most in the score. The best first step is adding tests for untested code, worth about 7.7 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 7.6 points. Raising Accessibility to 70 would lift the score to about 62.7.
Four controls can't be used without a mouse. Making the controls work with a keyboard would close this risk. The page that doesn't say its language needs its language set.
The product code is 34,833 lines, about €51,000 to rebuild.
If Accessibility rose from 40.7 to 70, the lowest score rated Strong, the score would rise from 53.7 to about 62.7.
Rebuild cost: about €51,000 · Estimate
| Cost to rebuild | €17,000 to €86,000, for 284 to 900 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 34,833 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 utils.codes | 2 utils.units | 3 domain.shared.enums | 4 domain.shared.enums.areatype | 5 domain.shared.enums.household | 6 domain.shared.enums.person | 7 utils | 8 domain.shared.car | 9 domain.shared.location.zone.attributes | 10 utils.csv | 11 domain.shared.location | 12 domain.shared.datastructure.schedule.action | 13 domain.shared.location.zone | 14 domain.simulation.data | 15 domain.synthesis.behavior | 16 domain.shared.behavior | 17 domain.shared.datastructure.matrix | 18 domain.shared.datastructure.schedule.plans | 19 domain.simulation.data.sharing | 20 domain.synthesis.attributes.household | 21 domain.shared.datastructure.schedule.replanning | 22 domain.synthesis | 23 domain.shared.datastructure.schedule | 24 domain.synthesis.attributes.person | 25 domain.simulation.data.person | 26 domain.synthesis.behavior.cars.choicemodels | 27 domain.simulation.data.household | 28 domain.simulation.parser | 29 domain.simulation.parser.binary | 30 application.steps.parser.csv | 31 domain.simulation.agent | 32 application.steps.results | 33 domain.simulation.behavior.modechoice | 34 domain.simulation.behavior.availability | 35 domain.simulation.behavior.destinationchoice | 36 application.config | 37 application.steps.model | 38 domain.simulation.events | 39 application.steps | 40 domain.jackson |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 utils.codes | ||||||||||||||||||||||||||||||||||||||||
| 2 utils.units | ||||||||||||||||||||||||||||||||||||||||
| 3 domain.shared.enums | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 4 domain.shared.enums.areatype | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 domain.shared.enums.household | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 domain.shared.enums.person | 4 | |||||||||||||||||||||||||||||||||||||||
| 7 utils | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 domain.shared.car | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 domain.shared.location.zone.attributes | 2 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 10 utils.csv | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 11 domain.shared.location | 2 | 3 | 1 | 6 | 5 | |||||||||||||||||||||||||||||||||||
| 12 domain.shared.datastructure.schedule.action | 10 | 8 | 11 | 3 | ||||||||||||||||||||||||||||||||||||
| 13 domain.shared.location.zone | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 14 domain.simulation.data | 1 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 15 domain.synthesis.behavior | 3 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 domain.shared.behavior | 8 | 1 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 17 domain.shared.datastructure.matrix | 3 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 18 domain.shared.datastructure.schedule.plans | 1 | 38 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 domain.simulation.data.sharing | 1 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 20 domain.synthesis.attributes.household | 7 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 domain.shared.datastructure.schedule.replanning | 5 | 1 | 1 | 6 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 22 domain.synthesis | 1 | 1 | 1 | 1 | 1 | 14 | 2 | |||||||||||||||||||||||||||||||||
| 23 domain.shared.datastructure.schedule | 2 | 2 | 7 | 24 | 5 | 5 | ||||||||||||||||||||||||||||||||||
| 24 domain.synthesis.attributes.person | 8 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 domain.simulation.data.person | 4 | 1 | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 26 domain.synthesis.behavior.cars.choicemodels | 1 | 2 | 3 | 1 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 27 domain.simulation.data.household | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 28 domain.simulation.parser | 6 | 5 | 1 | 6 | 8 | 1 | 5 | 17 | 5 | 10 | 1 | 5 | 1 | |||||||||||||||||||||||||||
| 29 domain.simulation.parser.binary | 2 | 2 | 2 | 4 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 30 application.steps.parser.csv | 4 | 1 | 1 | 10 | 1 | 2 | 4 | 1 | 1 | 7 | ||||||||||||||||||||||||||||||
| 31 domain.simulation.agent | 5 | 3 | 1 | 3 | 10 | 1 | 1 | 7 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||
| 32 application.steps.results | 3 | 7 | 1 | 2 | 4 | 4 | 4 | 4 | 10 | 2 | 2 | 7 | ||||||||||||||||||||||||||||
| 33 domain.simulation.behavior.modechoice | 3 | 4 | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||||
| 34 domain.simulation.behavior.availability | 2 | 11 | 3 | 1 | 1 | 16 | 1 | |||||||||||||||||||||||||||||||||
| 35 domain.simulation.behavior.destinationchoice | 2 | 2 | 1 | 1 | 5 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 36 application.config | 1 | 1 | 3 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 37 application.steps.model | 2 | 2 | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 38 domain.simulation.events | 8 | 2 | 3 | 6 | 1 | 11 | 25 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||
| 39 application.steps | 6 | 1 | 8 | 1 | 1 | 2 | 6 | 1 | 4 | 1 | 2 | 1 | 2 | 2 | 3 | 2 | ||||||||||||||||||||||||
| 40 domain.jackson | 14 | 2 | 4 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 2 |
3→1 domain.shared.enums uses utils.codes✕
- Connections
- 4 pairs of types, where a type in domain.shared.enums uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.shared.enums.ActivityType→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.MainModes→edu.kit.ifv.utils.codes.EnumDecodableedu.kit.ifv.domain.shared.enums.Mode→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.ZoneClassification→edu.kit.ifv.utils.codes.Encodable
- Direction
- domain.shared.enums uses utils.codes, so a change to utils.codes can break domain.shared.enums, while a change to domain.shared.enums can't break utils.codes.
- Position
- Below the diagonal: domain.shared.enums uses a module listed above it, which is the healthy direction.
3→16 domain.shared.enums uses domain.shared.behavior part of a loop✕
- Connections
- 2 pairs of types, where a type in domain.shared.enums uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.domain.shared.enums.LegacyActivityTypeKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposesedu.kit.ifv.domain.shared.enums.LegacyModeKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelModes
- Direction
- domain.shared.enums uses domain.shared.behavior, so a change to domain.shared.behavior can break domain.shared.enums, while a change to domain.shared.enums can't break domain.shared.behavior.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→1 domain.shared.enums.areatype uses utils.codes✕
- Connections
- 2 pairs of types, where a type in domain.shared.enums.areatype uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.shared.enums.areatype.RegioStaRClassification→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.areatype.RegionType→edu.kit.ifv.utils.codes.Encodable
- Direction
- domain.shared.enums.areatype uses utils.codes, so a change to utils.codes can break domain.shared.enums.areatype, while a change to domain.shared.enums.areatype can't break utils.codes.
- Position
- Below the diagonal: domain.shared.enums.areatype uses a module listed above it, which is the healthy direction.
5→1 domain.shared.enums.household uses utils.codes✕
- Connections
- 2 pairs of types, where a type in domain.shared.enums.household uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.shared.enums.household.EconomicStatus→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.household.HouseholdType→edu.kit.ifv.utils.codes.Encodable
- Direction
- domain.shared.enums.household uses utils.codes, so a change to utils.codes can break domain.shared.enums.household, while a change to domain.shared.enums.household can't break utils.codes.
- Position
- Below the diagonal: domain.shared.enums.household uses a module listed above it, which is the healthy direction.
6→1 domain.shared.enums.person uses utils.codes✕
- Connections
- 4 pairs of types, where a type in domain.shared.enums.person uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.shared.enums.person.ChargingInfluence→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.person.Employment→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.person.Graduation→edu.kit.ifv.utils.codes.Encodableedu.kit.ifv.domain.shared.enums.person.Sex→edu.kit.ifv.utils.codes.Encodable
- Direction
- domain.shared.enums.person uses utils.codes, so a change to utils.codes can break domain.shared.enums.person, while a change to domain.shared.enums.person can't break utils.codes.
- Position
- Below the diagonal: domain.shared.enums.person uses a module listed above it, which is the healthy direction.
7→2 utils uses utils.units✕
- Connections
- 3 pairs of types, where a type in utils uses a type in utils.units.
- The types involved
edu.kit.ifv.utils.ExpiringLookup→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.utils.WithExpiration→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.utils.WithExpirationKt→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- utils uses utils.units, so a change to utils.units can break utils, while a change to utils can't break utils.units.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
8→1 domain.shared.car uses utils.codes✕
- Connections
- 1 pair of types, where a type in domain.shared.car uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.shared.car.CarSegment→edu.kit.ifv.utils.codes.Encodable
- Direction
- domain.shared.car uses utils.codes, so a change to utils.codes can break domain.shared.car, while a change to domain.shared.car can't break utils.codes.
- Position
- Below the diagonal: domain.shared.car uses a module listed above it, which is the healthy direction.
8→7 domain.shared.car uses utils✕
- Connections
- 1 pair of types, where a type in domain.shared.car uses a type in utils.
- The types involved
edu.kit.ifv.domain.shared.car.Car→edu.kit.ifv.utils.Identifiable
- Direction
- domain.shared.car uses utils, so a change to utils can break domain.shared.car, while a change to domain.shared.car can't break utils.
- Position
- Below the diagonal: domain.shared.car uses a module listed above it, which is the healthy direction.
9→3 domain.shared.location.zone.attributes uses domain.shared.enums✕
- Connections
- 2 pairs of types, where a type in domain.shared.location.zone.attributes uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.location.zone.attributes.MaximumZoneAttributes→edu.kit.ifv.domain.shared.enums.ZoneClassificationedu.kit.ifv.domain.shared.location.zone.attributes.MaximumZoneAttributesImpl→edu.kit.ifv.domain.shared.enums.ZoneClassification
- Direction
- domain.shared.location.zone.attributes uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.location.zone.attributes, while a change to domain.shared.location.zone.attributes can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.location.zone.attributes uses a module listed above it, which is the healthy direction.
9→4 domain.shared.location.zone.attributes uses domain.shared.enums.areatype✕
- Connections
- 3 pairs of types, where a type in domain.shared.location.zone.attributes uses a type in domain.shared.enums.areatype.
- The types involved
edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionType→edu.kit.ifv.domain.shared.enums.areatype.RegionTypeedu.kit.ifv.domain.shared.location.zone.attributes.HasSizebasedClassification→edu.kit.ifv.domain.shared.enums.areatype.SizebasedRegiostarClassificationedu.kit.ifv.domain.shared.location.zone.attributes.MaximumZoneAttributesImpl→edu.kit.ifv.domain.shared.enums.areatype.RegionType
- Direction
- domain.shared.location.zone.attributes uses domain.shared.enums.areatype, so a change to domain.shared.enums.areatype can break domain.shared.location.zone.attributes, while a change to domain.shared.location.zone.attributes can't break domain.shared.enums.areatype.
- Position
- Below the diagonal: domain.shared.location.zone.attributes uses a module listed above it, which is the healthy direction.
9→7 domain.shared.location.zone.attributes uses utils✕
- Connections
- 1 pair of types, where a type in domain.shared.location.zone.attributes uses a type in utils.
- The types involved
edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneId→edu.kit.ifv.utils.Identifiable
- Direction
- domain.shared.location.zone.attributes uses utils, so a change to utils can break domain.shared.location.zone.attributes, while a change to domain.shared.location.zone.attributes can't break utils.
- Position
- Below the diagonal: domain.shared.location.zone.attributes uses a module listed above it, which is the healthy direction.
9→11 domain.shared.location.zone.attributes uses domain.shared.location part of a loop✕
- Connections
- 1 pair of types, where a type in domain.shared.location.zone.attributes uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.shared.location.zone.attributes.HasGeometricEmbedding→edu.kit.ifv.domain.shared.location.Location
- Direction
- domain.shared.location.zone.attributes uses domain.shared.location, so a change to domain.shared.location can break domain.shared.location.zone.attributes, while a change to domain.shared.location.zone.attributes can't break domain.shared.location.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→13 domain.shared.location.zone.attributes uses domain.shared.location.zone part of a loop✕
- Connections
- 1 pair of types, where a type in domain.shared.location.zone.attributes uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneId→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- domain.shared.location.zone.attributes uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.shared.location.zone.attributes, while a change to domain.shared.location.zone.attributes can't break domain.shared.location.zone.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 utils.csv uses utils.codes✕
- Connections
- 1 pair of types, where a type in utils.csv uses a type in utils.codes.
- The types involved
edu.kit.ifv.utils.csv.CsvColumnTypesKt→edu.kit.ifv.utils.codes.Decodable
- Direction
- utils.csv uses utils.codes, so a change to utils.codes can break utils.csv, while a change to utils.csv can't break utils.codes.
- Position
- Below the diagonal: utils.csv uses a module listed above it, which is the healthy direction.
10→7 utils.csv uses utils✕
- Connections
- 4 pairs of types, where a type in utils.csv uses a type in utils.
- The types involved
edu.kit.ifv.utils.csv.DefaultCsvParser→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.utils.csv.DefaultCsvReader→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.utils.csv.ErrorHandlingRow→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.utils.csv.SingleColumnParser→edu.kit.ifv.utils.ErrorHandling
- Direction
- utils.csv uses utils, so a change to utils can break utils.csv, while a change to utils.csv can't break utils.
- Position
- Below the diagonal: utils.csv uses a module listed above it, which is the healthy direction.
11→2 domain.shared.location uses utils.units✕
- Connections
- 2 pairs of types, where a type in domain.shared.location uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.shared.location.Impedance→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.location.ZoneImpedance→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.shared.location uses utils.units, so a change to utils.units can break domain.shared.location, while a change to domain.shared.location can't break utils.units.
- Position
- Below the diagonal: domain.shared.location uses a module listed above it, which is the healthy direction.
11→3 domain.shared.location uses domain.shared.enums✕
- Connections
- 3 pairs of types, where a type in domain.shared.location uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.location.ArrayBackedImpedance→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.location.Impedance→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.location.ZoneImpedance→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.shared.location uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.location, while a change to domain.shared.location can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.location uses a module listed above it, which is the healthy direction.
11→4 domain.shared.location uses domain.shared.enums.areatype✕
- Connections
- 1 pair of types, where a type in domain.shared.location uses a type in domain.shared.enums.areatype.
- The types involved
edu.kit.ifv.domain.shared.location.StandardLocation→edu.kit.ifv.domain.shared.enums.areatype.RegionType
- Direction
- domain.shared.location uses domain.shared.enums.areatype, so a change to domain.shared.enums.areatype can break domain.shared.location, while a change to domain.shared.location can't break domain.shared.enums.areatype.
- Position
- Below the diagonal: domain.shared.location uses a module listed above it, which is the healthy direction.
11→9 domain.shared.location uses domain.shared.location.zone.attributes✕
- Connections
- 6 pairs of types, where a type in domain.shared.location uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.shared.location.ConstantMetric→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneIdedu.kit.ifv.domain.shared.location.Impedance→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneIdedu.kit.ifv.domain.shared.location.LocationMetric→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneIdedu.kit.ifv.domain.shared.location.StandardLocation→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneIdedu.kit.ifv.domain.shared.location.StandardLocationImpl→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionTypeedu.kit.ifv.domain.shared.location.ZoneImpedance→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneId
- Direction
- domain.shared.location uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.shared.location, while a change to domain.shared.location can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.shared.location uses a module listed above it, which is the healthy direction.
11→13 domain.shared.location uses domain.shared.location.zone part of a loop✕
- Connections
- 5 pairs of types, where a type in domain.shared.location uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.shared.location.StandardLocation→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.location.StandardLocationImpl→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.shared.location.ZoneImpedance→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.location.ZoneImpedance→edu.kit.ifv.domain.shared.location.zone.ZoneMetricedu.kit.ifv.domain.shared.location.ZonedRoadAccessLocationRecord→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- domain.shared.location uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.shared.location, while a change to domain.shared.location can't break domain.shared.location.zone.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 domain.shared.datastructure.schedule.action uses utils.units✕
- Connections
- 10 pairs of types, where a type in domain.shared.datastructure.schedule.action uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.action.Action→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.Activity→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.CurrentAction→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.Leg→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedAction→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivity→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLeg→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.MovingAction→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.RawActivity→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.action.RawLeg→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.shared.datastructure.schedule.action uses utils.units, so a change to utils.units can break domain.shared.datastructure.schedule.action, while a change to domain.shared.datastructure.schedule.action can't break utils.units.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.action uses a module listed above it, which is the healthy direction.
12→3 domain.shared.datastructure.schedule.action uses domain.shared.enums✕
- Connections
- 8 pairs of types, where a type in domain.shared.datastructure.schedule.action uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.action.Activity→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.datastructure.schedule.action.Activity→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.datastructure.schedule.action.Leg→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivity→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.datastructure.schedule.action.MovingAction→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.datastructure.schedule.action.RawActivity→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.datastructure.schedule.action.RawLeg→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryAction→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- domain.shared.datastructure.schedule.action uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.datastructure.schedule.action, while a change to domain.shared.datastructure.schedule.action can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.action uses a module listed above it, which is the healthy direction.
12→11 domain.shared.datastructure.schedule.action uses domain.shared.location✕
- Connections
- 11 pairs of types, where a type in domain.shared.datastructure.schedule.action uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.action.Action→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.Activity→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.CurrentAction→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.Leg→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedAction→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivity→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLeg→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.MovingAction→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.RawActivity→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.RawLeg→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryAction→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.shared.datastructure.schedule.action uses domain.shared.location, so a change to domain.shared.location can break domain.shared.datastructure.schedule.action, while a change to domain.shared.datastructure.schedule.action can't break domain.shared.location.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.action uses a module listed above it, which is the healthy direction.
12→23 domain.shared.datastructure.schedule.action uses domain.shared.datastructure.schedule part of a loop✕
- Connections
- 3 pairs of types, where a type in domain.shared.datastructure.schedule.action uses a type in domain.shared.datastructure.schedule.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.action.Action→edu.kit.ifv.domain.shared.datastructure.schedule.ActionVisitoredu.kit.ifv.domain.shared.datastructure.schedule.action.Activity→edu.kit.ifv.domain.shared.datastructure.schedule.ActionVisitoredu.kit.ifv.domain.shared.datastructure.schedule.action.Leg→edu.kit.ifv.domain.shared.datastructure.schedule.ActionVisitor
- Direction
- domain.shared.datastructure.schedule.action uses domain.shared.datastructure.schedule, so a change to domain.shared.datastructure.schedule can break domain.shared.datastructure.schedule.action, while a change to domain.shared.datastructure.schedule.action can't break domain.shared.datastructure.schedule.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→9 domain.shared.location.zone uses domain.shared.location.zone.attributes✕
- Connections
- 3 pairs of types, where a type in domain.shared.location.zone uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.shared.location.zone.MaximalZone→edu.kit.ifv.domain.shared.location.zone.attributes.MaximumZoneAttributesedu.kit.ifv.domain.shared.location.zone.Zone→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneIdedu.kit.ifv.domain.shared.location.zone.ZoneMetric→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneId
- Direction
- domain.shared.location.zone uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.shared.location.zone, while a change to domain.shared.location.zone can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.shared.location.zone uses a module listed above it, which is the healthy direction.
13→11 domain.shared.location.zone uses domain.shared.location✕
- Connections
- 4 pairs of types, where a type in domain.shared.location.zone uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.shared.location.zone.MaximalZone→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.location.zone.MaximalZoneKt→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.location.zone.Zone→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.location.zone.ZoneMetric→edu.kit.ifv.domain.shared.location.LocationMetric
- Direction
- domain.shared.location.zone uses domain.shared.location, so a change to domain.shared.location can break domain.shared.location.zone, while a change to domain.shared.location.zone can't break domain.shared.location.
- Position
- Below the diagonal: domain.shared.location.zone uses a module listed above it, which is the healthy direction.
14→2 domain.simulation.data uses utils.units✕
- Connections
- 1 pair of types, where a type in domain.simulation.data uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.simulation.data.PlannedActivity→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.simulation.data uses utils.units, so a change to utils.units can break domain.simulation.data, while a change to domain.simulation.data can't break utils.units.
- Position
- Below the diagonal: domain.simulation.data uses a module listed above it, which is the healthy direction.
14→3 domain.simulation.data uses domain.shared.enums✕
- Connections
- 2 pairs of types, where a type in domain.simulation.data uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.data.ActivityLocation→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.simulation.data.PlannedActivity→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- domain.simulation.data uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.data, while a change to domain.simulation.data can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.data uses a module listed above it, which is the healthy direction.
14→7 domain.simulation.data uses utils✕
- Connections
- 1 pair of types, where a type in domain.simulation.data uses a type in utils.
- The types involved
edu.kit.ifv.domain.simulation.data.PlannedActivity→edu.kit.ifv.utils.Identifiable
- Direction
- domain.simulation.data uses utils, so a change to utils can break domain.simulation.data, while a change to domain.simulation.data can't break utils.
- Position
- Below the diagonal: domain.simulation.data uses a module listed above it, which is the healthy direction.
14→11 domain.simulation.data uses domain.shared.location✕
- Connections
- 4 pairs of types, where a type in domain.simulation.data uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.data.ActivityLocation→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.data.ActivityLocationBinaryRecord→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.data.ActivityLocationBinaryRecord→edu.kit.ifv.domain.shared.location.ZonedRoadAccessLocationRecordedu.kit.ifv.domain.simulation.data.PlannedActivity→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.data uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.data, while a change to domain.simulation.data can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.data uses a module listed above it, which is the healthy direction.
15→5 domain.synthesis.behavior uses domain.shared.enums.household✕
- Connections
- 3 pairs of types, where a type in domain.synthesis.behavior uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.ISurveyHousehold→edu.kit.ifv.domain.shared.enums.household.HouseholdTypeedu.kit.ifv.domain.synthesis.behavior.RawSurveyInfo→edu.kit.ifv.domain.shared.enums.household.HouseholdTypeedu.kit.ifv.domain.synthesis.behavior.SurveyHousehold→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- domain.synthesis.behavior uses domain.shared.enums.household, so a change to domain.shared.enums.household can break domain.synthesis.behavior, while a change to domain.synthesis.behavior can't break domain.shared.enums.household.
- Position
- Below the diagonal: domain.synthesis.behavior uses a module listed above it, which is the healthy direction.
15→6 domain.synthesis.behavior uses domain.shared.enums.person✕
- Connections
- 3 pairs of types, where a type in domain.synthesis.behavior uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.RawSurveyInfo→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.synthesis.behavior.RawSurveyInfo→edu.kit.ifv.domain.shared.enums.person.Sexedu.kit.ifv.domain.synthesis.behavior.SurveyPerson→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- domain.synthesis.behavior uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.synthesis.behavior, while a change to domain.synthesis.behavior can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.synthesis.behavior uses a module listed above it, which is the healthy direction.
15→11 domain.synthesis.behavior uses domain.shared.location✕
- Connections
- 2 pairs of types, where a type in domain.synthesis.behavior uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.SmallestSurveyPerson→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.synthesis.behavior.SurveyPerson→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.synthesis.behavior uses domain.shared.location, so a change to domain.shared.location can break domain.synthesis.behavior, while a change to domain.synthesis.behavior can't break domain.shared.location.
- Position
- Below the diagonal: domain.synthesis.behavior uses a module listed above it, which is the healthy direction.
15→22 domain.synthesis.behavior uses domain.synthesis part of a loop✕
- Connections
- 1 pair of types, where a type in domain.synthesis.behavior uses a type in domain.synthesis.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.HouseholdFactory→edu.kit.ifv.domain.synthesis.SynthesisHousehold
- Direction
- domain.synthesis.behavior uses domain.synthesis, so a change to domain.synthesis can break domain.synthesis.behavior, while a change to domain.synthesis.behavior can't break domain.synthesis.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→3 domain.shared.behavior uses domain.shared.enums✕
- Connections
- 8 pairs of types, where a type in domain.shared.behavior uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.behavior.AttractivenessCacher→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.behavior.AttractivenessFromCsv→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.behavior.AttractivenessFromCsvKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.behavior.AttractivenessModel→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.behavior.AttractivenessModelKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.behavior.ChoiceModelModes→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.behavior.ChoiceModelPurposes→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.shared.behavior.ParkingPressureByAttractiveness→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- domain.shared.behavior uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.behavior, while a change to domain.shared.behavior can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.behavior uses a module listed above it, which is the healthy direction.
16→7 domain.shared.behavior uses utils✕
- Connections
- 1 pair of types, where a type in domain.shared.behavior uses a type in utils.
- The types involved
edu.kit.ifv.domain.shared.behavior.AttractivenessFromCsv→edu.kit.ifv.utils.ErrorHandling
- Direction
- domain.shared.behavior uses utils, so a change to utils can break domain.shared.behavior, while a change to domain.shared.behavior can't break utils.
- Position
- Below the diagonal: domain.shared.behavior uses a module listed above it, which is the healthy direction.
16→9 domain.shared.behavior uses domain.shared.location.zone.attributes✕
- Connections
- 1 pair of types, where a type in domain.shared.behavior uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.shared.behavior.ParkingPressureByAttractiveness→edu.kit.ifv.domain.shared.location.zone.attributes.HasNumberParkingPlaces
- Direction
- domain.shared.behavior uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.shared.behavior, while a change to domain.shared.behavior can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.shared.behavior uses a module listed above it, which is the healthy direction.
16→10 domain.shared.behavior uses utils.csv✕
- Connections
- 1 pair of types, where a type in domain.shared.behavior uses a type in utils.csv.
- The types involved
edu.kit.ifv.domain.shared.behavior.AttractivenessFromCsvKt→edu.kit.ifv.utils.csv.Row
- Direction
- domain.shared.behavior uses utils.csv, so a change to utils.csv can break domain.shared.behavior, while a change to domain.shared.behavior can't break utils.csv.
- Position
- Below the diagonal: domain.shared.behavior uses a module listed above it, which is the healthy direction.
16→13 domain.shared.behavior uses domain.shared.location.zone✕
- Connections
- 7 pairs of types, where a type in domain.shared.behavior uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.shared.behavior.AttractivenessCacher→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.behavior.AttractivenessFromCsv→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.behavior.AttractivenessModel→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.behavior.AttractivenessModelKt→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.behavior.ParkingPressureByAttractiveness→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.shared.behavior.ParkingPressureByAttractiveness→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.behavior.ParkingPressureModel→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- domain.shared.behavior uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.shared.behavior, while a change to domain.shared.behavior can't break domain.shared.location.zone.
- Position
- Below the diagonal: domain.shared.behavior uses a module listed above it, which is the healthy direction.
17→2 domain.shared.datastructure.matrix uses utils.units✕
- Connections
- 3 pairs of types, where a type in domain.shared.datastructure.matrix uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.shared.datastructure.matrix.CachedMatrixLookup→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.matrix.MatrixImpedance→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.matrix.ZoneMatrixLookup→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.shared.datastructure.matrix uses utils.units, so a change to utils.units can break domain.shared.datastructure.matrix, while a change to domain.shared.datastructure.matrix can't break utils.units.
- Position
- Below the diagonal: domain.shared.datastructure.matrix uses a module listed above it, which is the healthy direction.
17→3 domain.shared.datastructure.matrix uses domain.shared.enums✕
- Connections
- 1 pair of types, where a type in domain.shared.datastructure.matrix uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.datastructure.matrix.MatrixImpedance→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.shared.datastructure.matrix uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.datastructure.matrix, while a change to domain.shared.datastructure.matrix can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.datastructure.matrix uses a module listed above it, which is the healthy direction.
17→11 domain.shared.datastructure.matrix uses domain.shared.location✕
- Connections
- 3 pairs of types, where a type in domain.shared.datastructure.matrix uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.shared.datastructure.matrix.MatrixImpedance→edu.kit.ifv.domain.shared.location.ArrayBackedImpedanceedu.kit.ifv.domain.shared.datastructure.matrix.MatrixImpedance→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.shared.datastructure.matrix.MatrixImpedance→edu.kit.ifv.domain.shared.location.LocationMetric
- Direction
- domain.shared.datastructure.matrix uses domain.shared.location, so a change to domain.shared.location can break domain.shared.datastructure.matrix, while a change to domain.shared.datastructure.matrix can't break domain.shared.location.
- Position
- Below the diagonal: domain.shared.datastructure.matrix uses a module listed above it, which is the healthy direction.
17→13 domain.shared.datastructure.matrix uses domain.shared.location.zone✕
- Connections
- 3 pairs of types, where a type in domain.shared.datastructure.matrix uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.shared.datastructure.matrix.ConstantZoneIdMatrix→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.datastructure.matrix.StandardMatrix→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.shared.datastructure.matrix.ZoneIdMatrix→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- domain.shared.datastructure.matrix uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.shared.datastructure.matrix, while a change to domain.shared.datastructure.matrix can't break domain.shared.location.zone.
- Position
- Below the diagonal: domain.shared.datastructure.matrix uses a module listed above it, which is the healthy direction.
18→2 domain.shared.datastructure.schedule.plans uses utils.units✕
- Connections
- 1 pair of types, where a type in domain.shared.datastructure.schedule.plans uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanModelKt→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.shared.datastructure.schedule.plans uses utils.units, so a change to utils.units can break domain.shared.datastructure.schedule.plans, while a change to domain.shared.datastructure.schedule.plans can't break utils.units.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.plans uses a module listed above it, which is the healthy direction.
18→12 domain.shared.datastructure.schedule.plans uses domain.shared.datastructure.schedule.action✕
- Connections
- 38 pairs of types, where a type in domain.shared.datastructure.schedule.plans uses a type in domain.shared.datastructure.schedule.action. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.plans.ActionModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.ActionModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.plans.ActionModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActionedu.kit.ifv.domain.shared.datastructure.schedule.plans.ActionModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.plans.ActivityTracker→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.ActivityTracker→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.plans.BlockModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.BlockModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.plans.BlockModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActionedu.kit.ifv.domain.shared.datastructure.schedule.plans.BlockModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.plans.BlockModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLegedu.kit.ifv.domain.shared.datastructure.schedule.plans.Dispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.Dispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.plans.Dispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActionedu.kit.ifv.domain.shared.datastructure.schedule.plans.Dispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.plans.IDispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.IDispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.plans.IDispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActionedu.kit.ifv.domain.shared.datastructure.schedule.plans.IDispatcher→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.plans.LegTracker→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanModel→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActionedu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanModelKt→edu.kit.ifv.domain.shared.datastructure.schedule.action.Actionedu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanView→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanView→edu.kit.ifv.domain.shared.datastructure.schedule.action.Leg
- Direction
- domain.shared.datastructure.schedule.plans uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break domain.shared.datastructure.schedule.plans, while a change to domain.shared.datastructure.schedule.plans can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.plans uses a module listed above it, which is the healthy direction.
18→23 domain.shared.datastructure.schedule.plans uses domain.shared.datastructure.schedule part of a loop✕
- Connections
- 1 pair of types, where a type in domain.shared.datastructure.schedule.plans uses a type in domain.shared.datastructure.schedule.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.plans.BlockModel→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip
- Direction
- domain.shared.datastructure.schedule.plans uses domain.shared.datastructure.schedule, so a change to domain.shared.datastructure.schedule can break domain.shared.datastructure.schedule.plans, while a change to domain.shared.datastructure.schedule.plans can't break domain.shared.datastructure.schedule.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→3 domain.simulation.data.sharing uses domain.shared.enums✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.sharing uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.data.sharing.ISharingProvider→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.data.sharing uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.data.sharing, while a change to domain.simulation.data.sharing can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.data.sharing uses a module listed above it, which is the healthy direction.
19→7 domain.simulation.data.sharing uses utils✕
- Connections
- 2 pairs of types, where a type in domain.simulation.data.sharing uses a type in utils.
- The types involved
edu.kit.ifv.domain.simulation.data.sharing.ISharingProvider→edu.kit.ifv.utils.Identifiableedu.kit.ifv.domain.simulation.data.sharing.ISharingStation→edu.kit.ifv.utils.Identifiable
- Direction
- domain.simulation.data.sharing uses utils, so a change to utils can break domain.simulation.data.sharing, while a change to domain.simulation.data.sharing can't break utils.
- Position
- Below the diagonal: domain.simulation.data.sharing uses a module listed above it, which is the healthy direction.
19→9 domain.simulation.data.sharing uses domain.shared.location.zone.attributes✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.sharing uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.simulation.data.sharing.ISharingStation→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionType
- Direction
- domain.simulation.data.sharing uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.simulation.data.sharing, while a change to domain.simulation.data.sharing can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.simulation.data.sharing uses a module listed above it, which is the healthy direction.
19→11 domain.simulation.data.sharing uses domain.shared.location✕
- Connections
- 2 pairs of types, where a type in domain.simulation.data.sharing uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.data.sharing.HasStandardLocation→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.data.sharing.ISharingStation→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.data.sharing uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.data.sharing, while a change to domain.simulation.data.sharing can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.data.sharing uses a module listed above it, which is the healthy direction.
19→13 domain.simulation.data.sharing uses domain.shared.location.zone✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.sharing uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.simulation.data.sharing.ISharingStation→edu.kit.ifv.domain.shared.location.zone.Zone
- Direction
- domain.simulation.data.sharing uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.simulation.data.sharing, while a change to domain.simulation.data.sharing can't break domain.shared.location.zone.
- Position
- Below the diagonal: domain.simulation.data.sharing uses a module listed above it, which is the healthy direction.
20→5 domain.synthesis.attributes.household uses domain.shared.enums.household✕
- Connections
- 7 pairs of types, where a type in domain.synthesis.attributes.household uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.domain.synthesis.attributes.household.HasEconomicStatus→edu.kit.ifv.domain.shared.enums.household.EconomicStatusedu.kit.ifv.domain.synthesis.attributes.household.HasHouseholdType→edu.kit.ifv.domain.shared.enums.household.HouseholdTypeedu.kit.ifv.domain.synthesis.attributes.household.HasMutableEconomicStatus→edu.kit.ifv.domain.shared.enums.household.EconomicStatusedu.kit.ifv.domain.synthesis.attributes.household.MaximumHouseholdAttributesImpl→edu.kit.ifv.domain.shared.enums.household.EconomicStatusedu.kit.ifv.domain.synthesis.attributes.household.MaximumHouseholdAttributesImpl→edu.kit.ifv.domain.shared.enums.household.HouseholdTypeedu.kit.ifv.domain.synthesis.attributes.household.MinimumHouseholdAttributes→edu.kit.ifv.domain.shared.enums.household.HouseholdTypeedu.kit.ifv.domain.synthesis.attributes.household.MinimumHouseholdAttributesImpl→edu.kit.ifv.domain.shared.enums.household.HouseholdType
- Direction
- domain.synthesis.attributes.household uses domain.shared.enums.household, so a change to domain.shared.enums.household can break domain.synthesis.attributes.household, while a change to domain.synthesis.attributes.household can't break domain.shared.enums.household.
- Position
- Below the diagonal: domain.synthesis.attributes.household uses a module listed above it, which is the healthy direction.
20→11 domain.synthesis.attributes.household uses domain.shared.location✕
- Connections
- 5 pairs of types, where a type in domain.synthesis.attributes.household uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.synthesis.attributes.household.HasLocation→edu.kit.ifv.domain.shared.location.Locationedu.kit.ifv.domain.synthesis.attributes.household.HasMutableLocation→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.synthesis.attributes.household.MaximumHouseholdAttributesImpl→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.synthesis.attributes.household.MinimumHouseholdAttributes→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.synthesis.attributes.household.MinimumHouseholdAttributesImpl→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.synthesis.attributes.household uses domain.shared.location, so a change to domain.shared.location can break domain.synthesis.attributes.household, while a change to domain.synthesis.attributes.household can't break domain.shared.location.
- Position
- Below the diagonal: domain.synthesis.attributes.household uses a module listed above it, which is the healthy direction.
20→15 domain.synthesis.attributes.household uses domain.synthesis.behavior✕
- Connections
- 1 pair of types, where a type in domain.synthesis.attributes.household uses a type in domain.synthesis.behavior.
- The types involved
edu.kit.ifv.domain.synthesis.attributes.household.HouseholdAttributeExtensionsKt→edu.kit.ifv.domain.synthesis.behavior.MinimalistPerson
- Direction
- domain.synthesis.attributes.household uses domain.synthesis.behavior, so a change to domain.synthesis.behavior can break domain.synthesis.attributes.household, while a change to domain.synthesis.attributes.household can't break domain.synthesis.behavior.
- Position
- Below the diagonal: domain.synthesis.attributes.household uses a module listed above it, which is the healthy direction.
21→2 domain.shared.datastructure.schedule.replanning uses utils.units✕
- Connections
- 5 pairs of types, where a type in domain.shared.datastructure.schedule.replanning uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.replanning.BananaReplanning→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.replanning.Change→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.replanning.Conflict→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.replanning.HomeActivityEndTimeAnchorStrategy→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategy→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.shared.datastructure.schedule.replanning uses utils.units, so a change to utils.units can break domain.shared.datastructure.schedule.replanning, while a change to domain.shared.datastructure.schedule.replanning can't break utils.units.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.replanning uses a module listed above it, which is the healthy direction.
21→3 domain.shared.datastructure.schedule.replanning uses domain.shared.enums✕
- Connections
- 1 pair of types, where a type in domain.shared.datastructure.schedule.replanning uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.replanning.HomeActivityEndTimeAnchorStrategy→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- domain.shared.datastructure.schedule.replanning uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.datastructure.schedule.replanning, while a change to domain.shared.datastructure.schedule.replanning can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.replanning uses a module listed above it, which is the healthy direction.
21→9 domain.shared.datastructure.schedule.replanning uses domain.shared.location.zone.attributes✕
- Connections
- 1 pair of types, where a type in domain.shared.datastructure.schedule.replanning uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.replanning.Conflict→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneId
- Direction
- domain.shared.datastructure.schedule.replanning uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.shared.datastructure.schedule.replanning, while a change to domain.shared.datastructure.schedule.replanning can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.replanning uses a module listed above it, which is the healthy direction.
21→12 domain.shared.datastructure.schedule.replanning uses domain.shared.datastructure.schedule.action✕
- Connections
- 6 pairs of types, where a type in domain.shared.datastructure.schedule.replanning uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.replanning.BananaReplanning→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.replanning.Conflict→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.shared.datastructure.schedule.replanning.HomeActivityEndTimeAnchorStrategy→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.replanning.PriorityBasedConflictResolver→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.replanning.PriorityBasedConflictResolver→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategy→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivity
- Direction
- domain.shared.datastructure.schedule.replanning uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break domain.shared.datastructure.schedule.replanning, while a change to domain.shared.datastructure.schedule.replanning can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.replanning uses a module listed above it, which is the healthy direction.
21→16 domain.shared.datastructure.schedule.replanning uses domain.shared.behavior✕
- Connections
- 2 pairs of types, where a type in domain.shared.datastructure.schedule.replanning uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.replanning.HomeActivityEndTimeAnchorStrategy→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposesedu.kit.ifv.domain.shared.datastructure.schedule.replanning.PriorityBasedConflictResolver→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposes
- Direction
- domain.shared.datastructure.schedule.replanning uses domain.shared.behavior, so a change to domain.shared.behavior can break domain.shared.datastructure.schedule.replanning, while a change to domain.shared.datastructure.schedule.replanning can't break domain.shared.behavior.
- Position
- Below the diagonal: domain.shared.datastructure.schedule.replanning uses a module listed above it, which is the healthy direction.
21→23 domain.shared.datastructure.schedule.replanning uses domain.shared.datastructure.schedule part of a loop✕
- Connections
- 3 pairs of types, where a type in domain.shared.datastructure.schedule.replanning uses a type in domain.shared.datastructure.schedule.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.replanning.BananaReplanning→edu.kit.ifv.domain.shared.datastructure.schedule.Scheduleedu.kit.ifv.domain.shared.datastructure.schedule.replanning.HomeActivityEndTimeAnchorStrategy→edu.kit.ifv.domain.shared.datastructure.schedule.Scheduleedu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategy→edu.kit.ifv.domain.shared.datastructure.schedule.Schedule
- Direction
- domain.shared.datastructure.schedule.replanning uses domain.shared.datastructure.schedule, so a change to domain.shared.datastructure.schedule can break domain.shared.datastructure.schedule.replanning, while a change to domain.shared.datastructure.schedule.replanning can't break domain.shared.datastructure.schedule.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→3 domain.synthesis uses domain.shared.enums✕
- Connections
- 1 pair of types, where a type in domain.synthesis uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.synthesis.SynthesisPerson→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- domain.synthesis uses domain.shared.enums, so a change to domain.shared.enums can break domain.synthesis, while a change to domain.synthesis can't break domain.shared.enums.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
22→6 domain.synthesis uses domain.shared.enums.person✕
- Connections
- 1 pair of types, where a type in domain.synthesis uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.synthesis.SynthesisPerson→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- domain.synthesis uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.synthesis, while a change to domain.synthesis can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
22→10 domain.synthesis uses utils.csv✕
- Connections
- 1 pair of types, where a type in domain.synthesis uses a type in utils.csv.
- The types involved
edu.kit.ifv.domain.synthesis.SurveyCSVParser→edu.kit.ifv.utils.csv.Row
- Direction
- domain.synthesis uses utils.csv, so a change to utils.csv can break domain.synthesis, while a change to domain.synthesis can't break utils.csv.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
22→11 domain.synthesis uses domain.shared.location✕
- Connections
- 1 pair of types, where a type in domain.synthesis uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.synthesis.SynthesisPerson→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.synthesis uses domain.shared.location, so a change to domain.shared.location can break domain.synthesis, while a change to domain.synthesis can't break domain.shared.location.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
22→12 domain.synthesis uses domain.shared.datastructure.schedule.action✕
- Connections
- 1 pair of types, where a type in domain.synthesis uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.domain.synthesis.SynthesisSteps→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activity
- Direction
- domain.synthesis uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break domain.synthesis, while a change to domain.synthesis can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
22→15 domain.synthesis uses domain.synthesis.behavior✕
- Connections
- 14 pairs of types, where a type in domain.synthesis uses a type in domain.synthesis.behavior.
- The types involved
edu.kit.ifv.domain.synthesis.GenerateFromFlatInput→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.GenerateSurveyHouseholds→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.HouseholdAssignmentStep→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.HouseholdAssignmentStep→edu.kit.ifv.domain.synthesis.behavior.SurveyPersonedu.kit.ifv.domain.synthesis.PopulationSynthesis→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.SeededProvider→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.SeededProvider→edu.kit.ifv.domain.synthesis.behavior.MinimalistPersonedu.kit.ifv.domain.synthesis.SurveyCSVParser→edu.kit.ifv.domain.synthesis.behavior.RawSurveyInfoedu.kit.ifv.domain.synthesis.SynthesisHousehold→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.SynthesisHousehold→edu.kit.ifv.domain.synthesis.behavior.SurveyPersonedu.kit.ifv.domain.synthesis.SynthesisPerson→edu.kit.ifv.domain.synthesis.behavior.SurveyPersonedu.kit.ifv.domain.synthesis.SynthesisRandomProvider→edu.kit.ifv.domain.synthesis.behavior.ISurveyHouseholdedu.kit.ifv.domain.synthesis.SynthesisRandomProvider→edu.kit.ifv.domain.synthesis.behavior.MinimalistPersonedu.kit.ifv.domain.synthesis.SynthesisSteps→edu.kit.ifv.domain.synthesis.behavior.ISurveyHousehold
- Direction
- domain.synthesis uses domain.synthesis.behavior, so a change to domain.synthesis.behavior can break domain.synthesis, while a change to domain.synthesis can't break domain.synthesis.behavior.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
22→16 domain.synthesis uses domain.shared.behavior✕
- Connections
- 2 pairs of types, where a type in domain.synthesis uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.domain.synthesis.AttractivenessModelParser→edu.kit.ifv.domain.shared.behavior.AttractivenessModeledu.kit.ifv.domain.synthesis.AttractivenessModelParser→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposes
- Direction
- domain.synthesis uses domain.shared.behavior, so a change to domain.shared.behavior can break domain.synthesis, while a change to domain.synthesis can't break domain.shared.behavior.
- Position
- Below the diagonal: domain.synthesis uses a module listed above it, which is the healthy direction.
23→2 domain.shared.datastructure.schedule uses utils.units✕
- Connections
- 2 pairs of types, where a type in domain.shared.datastructure.schedule uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.shared.datastructure.schedule uses utils.units, so a change to utils.units can break domain.shared.datastructure.schedule, while a change to domain.shared.datastructure.schedule can't break utils.units.
- Position
- Below the diagonal: domain.shared.datastructure.schedule uses a module listed above it, which is the healthy direction.
23→3 domain.shared.datastructure.schedule uses domain.shared.enums✕
- Connections
- 2 pairs of types, where a type in domain.shared.datastructure.schedule uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.ImpedanceBuilder→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.shared.datastructure.schedule uses domain.shared.enums, so a change to domain.shared.enums can break domain.shared.datastructure.schedule, while a change to domain.shared.datastructure.schedule can't break domain.shared.enums.
- Position
- Below the diagonal: domain.shared.datastructure.schedule uses a module listed above it, which is the healthy direction.
23→11 domain.shared.datastructure.schedule uses domain.shared.location✕
- Connections
- 7 pairs of types, where a type in domain.shared.datastructure.schedule uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.ImpedanceBuilder→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.shared.datastructure.schedule.ImpedanceBuilder→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.Trip→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.shared.datastructure.schedule.TripKt→edu.kit.ifv.domain.shared.location.Impedance
- Direction
- domain.shared.datastructure.schedule uses domain.shared.location, so a change to domain.shared.location can break domain.shared.datastructure.schedule, while a change to domain.shared.datastructure.schedule can't break domain.shared.location.
- Position
- Below the diagonal: domain.shared.datastructure.schedule uses a module listed above it, which is the healthy direction.
23→12 domain.shared.datastructure.schedule uses domain.shared.datastructure.schedule.action✕
- Connections
- 24 pairs of types, where a type in domain.shared.datastructure.schedule uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.ActionVisitor→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.ActionVisitor→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.Agenda→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLegedu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.shared.datastructure.schedule.RawAgenda→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.RawTrip→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.RawTrip→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.Actionedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.CurrentActionedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActionedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLegedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.MovingActionedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.shared.datastructure.schedule.Trip→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.Trip→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.datastructure.schedule.action.MovingActionedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryAction
- Direction
- domain.shared.datastructure.schedule uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break domain.shared.datastructure.schedule, while a change to domain.shared.datastructure.schedule can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: domain.shared.datastructure.schedule uses a module listed above it, which is the healthy direction.
23→18 domain.shared.datastructure.schedule uses domain.shared.datastructure.schedule.plans✕
- Connections
- 5 pairs of types, where a type in domain.shared.datastructure.schedule uses a type in domain.shared.datastructure.schedule.plans.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip→edu.kit.ifv.domain.shared.datastructure.schedule.plans.IDispatcheredu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.plans.PlanViewedu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.plans.SeparablePlanModeledu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.plans.SingularDispatcheredu.kit.ifv.domain.shared.datastructure.schedule.Schedule→edu.kit.ifv.domain.shared.datastructure.schedule.plans.TrackableModel
- Direction
- domain.shared.datastructure.schedule uses domain.shared.datastructure.schedule.plans, so a change to domain.shared.datastructure.schedule.plans can break domain.shared.datastructure.schedule, while a change to domain.shared.datastructure.schedule can't break domain.shared.datastructure.schedule.plans.
- Position
- Below the diagonal: domain.shared.datastructure.schedule uses a module listed above it, which is the healthy direction.
23→21 domain.shared.datastructure.schedule uses domain.shared.datastructure.schedule.replanning✕
- Connections
- 5 pairs of types, where a type in domain.shared.datastructure.schedule uses a type in domain.shared.datastructure.schedule.replanning.
- The types involved
edu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip→edu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategyedu.kit.ifv.domain.shared.datastructure.schedule.RawTrip→edu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategyedu.kit.ifv.domain.shared.datastructure.schedule.Trip→edu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategyedu.kit.ifv.domain.shared.datastructure.schedule.TripBuilder→edu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategyedu.kit.ifv.domain.shared.datastructure.schedule.TripKt→edu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategy
- Direction
- domain.shared.datastructure.schedule uses domain.shared.datastructure.schedule.replanning, so a change to domain.shared.datastructure.schedule.replanning can break domain.shared.datastructure.schedule, while a change to domain.shared.datastructure.schedule can't break domain.shared.datastructure.schedule.replanning.
- Position
- Below the diagonal: domain.shared.datastructure.schedule uses a module listed above it, which is the healthy direction.
24→6 domain.synthesis.attributes.person uses domain.shared.enums.person✕
- Connections
- 8 pairs of types, where a type in domain.synthesis.attributes.person uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.synthesis.attributes.person.HasBiologicalSex→edu.kit.ifv.domain.shared.enums.person.Sexedu.kit.ifv.domain.synthesis.attributes.person.HasEmployment→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.synthesis.attributes.person.HasMutableEmployment→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.synthesis.attributes.person.MaximumPersonAttributes→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.synthesis.attributes.person.MaximumPersonAttributes→edu.kit.ifv.domain.shared.enums.person.Sexedu.kit.ifv.domain.synthesis.attributes.person.MaximumPersonAttributesImpl→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.synthesis.attributes.person.MaximumPersonAttributesImpl→edu.kit.ifv.domain.shared.enums.person.Sexedu.kit.ifv.domain.synthesis.attributes.person.PersonAttributeExtensionsKt→edu.kit.ifv.domain.shared.enums.person.Employment
- Direction
- domain.synthesis.attributes.person uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.synthesis.attributes.person, while a change to domain.synthesis.attributes.person can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.synthesis.attributes.person uses a module listed above it, which is the healthy direction.
24→23 domain.synthesis.attributes.person uses domain.shared.datastructure.schedule✕
- Connections
- 2 pairs of types, where a type in domain.synthesis.attributes.person uses a type in domain.shared.datastructure.schedule.
- The types involved
edu.kit.ifv.domain.synthesis.attributes.person.HasMutableSchedule→edu.kit.ifv.domain.shared.datastructure.schedule.Scheduleedu.kit.ifv.domain.synthesis.attributes.person.HasSchedule→edu.kit.ifv.domain.shared.datastructure.schedule.Schedule
- Direction
- domain.synthesis.attributes.person uses domain.shared.datastructure.schedule, so a change to domain.shared.datastructure.schedule can break domain.synthesis.attributes.person, while a change to domain.synthesis.attributes.person can't break domain.shared.datastructure.schedule.
- Position
- Below the diagonal: domain.synthesis.attributes.person uses a module listed above it, which is the healthy direction.
25→6 domain.simulation.data.person uses domain.shared.enums.person✕
- Connections
- 4 pairs of types, where a type in domain.simulation.data.person uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.domain.shared.enums.person.ChargingInfluenceedu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.domain.shared.enums.person.Graduationedu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- domain.simulation.data.person uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.simulation.data.person, while a change to domain.simulation.data.person can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.simulation.data.person uses a module listed above it, which is the healthy direction.
25→7 domain.simulation.data.person uses utils✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.person uses a type in utils.
- The types involved
edu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.utils.Identifiable
- Direction
- domain.simulation.data.person uses utils, so a change to utils can break domain.simulation.data.person, while a change to domain.simulation.data.person can't break utils.
- Position
- Below the diagonal: domain.simulation.data.person uses a module listed above it, which is the healthy direction.
25→19 domain.simulation.data.person uses domain.simulation.data.sharing✕
- Connections
- 3 pairs of types, where a type in domain.simulation.data.person uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.domain.simulation.data.sharing.ISharingProvideredu.kit.ifv.domain.simulation.data.person.IPersonKt→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderIdedu.kit.ifv.domain.simulation.data.person.Person→edu.kit.ifv.domain.simulation.data.sharing.SharingProvider
- Direction
- domain.simulation.data.person uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break domain.simulation.data.person, while a change to domain.simulation.data.person can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: domain.simulation.data.person uses a module listed above it, which is the healthy direction.
25→24 domain.simulation.data.person uses domain.synthesis.attributes.person✕
- Connections
- 2 pairs of types, where a type in domain.simulation.data.person uses a type in domain.synthesis.attributes.person.
- The types involved
edu.kit.ifv.domain.simulation.data.person.Person→edu.kit.ifv.domain.synthesis.attributes.person.HasMutableScheduleedu.kit.ifv.domain.simulation.data.person.Person→edu.kit.ifv.domain.synthesis.attributes.person.HasPlannedActivities
- Direction
- domain.simulation.data.person uses domain.synthesis.attributes.person, so a change to domain.synthesis.attributes.person can break domain.simulation.data.person, while a change to domain.simulation.data.person can't break domain.synthesis.attributes.person.
- Position
- Below the diagonal: domain.simulation.data.person uses a module listed above it, which is the healthy direction.
25→27 domain.simulation.data.person uses domain.simulation.data.household part of a loop✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.person uses a type in domain.simulation.data.household.
- The types involved
edu.kit.ifv.domain.simulation.data.person.IPerson→edu.kit.ifv.domain.simulation.data.household.IHousehold
- Direction
- domain.simulation.data.person uses domain.simulation.data.household, so a change to domain.simulation.data.household can break domain.simulation.data.person, while a change to domain.simulation.data.person can't break domain.simulation.data.household.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→4 domain.synthesis.behavior.cars.choicemodels uses domain.shared.enums.areatype✕
- Connections
- 1 pair of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.shared.enums.areatype.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.EngineAlternative→edu.kit.ifv.domain.shared.enums.areatype.SizebasedRegiostarClassification
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.shared.enums.areatype, so a change to domain.shared.enums.areatype can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.shared.enums.areatype.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
26→5 domain.synthesis.behavior.cars.choicemodels uses domain.shared.enums.household✕
- Connections
- 2 pairs of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarOwnershipAttributes→edu.kit.ifv.domain.shared.enums.household.EconomicStatusedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarOwnershipFactors→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.shared.enums.household, so a change to domain.shared.enums.household can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.shared.enums.household.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
26→6 domain.synthesis.behavior.cars.choicemodels uses domain.shared.enums.person✕
- Connections
- 3 pairs of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarSegmentChoice→edu.kit.ifv.domain.shared.enums.person.Sexedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.EngineAlternative→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.EngineAlternative→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
26→8 domain.synthesis.behavior.cars.choicemodels uses domain.shared.car✕
- Connections
- 1 pair of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.shared.car.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarSegmentSituation→edu.kit.ifv.domain.shared.car.CarSegment
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.shared.car, so a change to domain.shared.car can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.shared.car.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
26→15 domain.synthesis.behavior.cars.choicemodels uses domain.synthesis.behavior✕
- Connections
- 5 pairs of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.synthesis.behavior.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarOwnershipFactors→edu.kit.ifv.domain.synthesis.behavior.MinimalistHouseholdedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarSegmentChoiceKt→edu.kit.ifv.domain.synthesis.behavior.MinimalistHouseholdedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarSegmentChoiceKt→edu.kit.ifv.domain.synthesis.behavior.MinimalistPersonedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarSegmentSituation→edu.kit.ifv.domain.synthesis.behavior.MinimalistHouseholdedu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarSegmentSituation→edu.kit.ifv.domain.synthesis.behavior.MinimalistPerson
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.synthesis.behavior, so a change to domain.synthesis.behavior can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.synthesis.behavior.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
26→20 domain.synthesis.behavior.cars.choicemodels uses domain.synthesis.attributes.household✕
- Connections
- 1 pair of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.synthesis.attributes.household.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarOwnershipFactors→edu.kit.ifv.domain.synthesis.attributes.household.HasEconomicStatus
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.synthesis.attributes.household, so a change to domain.synthesis.attributes.household can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.synthesis.attributes.household.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
26→24 domain.synthesis.behavior.cars.choicemodels uses domain.synthesis.attributes.person✕
- Connections
- 1 pair of types, where a type in domain.synthesis.behavior.cars.choicemodels uses a type in domain.synthesis.attributes.person.
- The types involved
edu.kit.ifv.domain.synthesis.behavior.cars.choicemodels.CarOwnershipFactors→edu.kit.ifv.domain.synthesis.attributes.person.MaximumPersonAttributes
- Direction
- domain.synthesis.behavior.cars.choicemodels uses domain.synthesis.attributes.person, so a change to domain.synthesis.attributes.person can break domain.synthesis.behavior.cars.choicemodels, while a change to domain.synthesis.behavior.cars.choicemodels can't break domain.synthesis.attributes.person.
- Position
- Below the diagonal: domain.synthesis.behavior.cars.choicemodels uses a module listed above it, which is the healthy direction.
27→5 domain.simulation.data.household uses domain.shared.enums.household✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.household uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.domain.simulation.data.household.IHousehold→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- domain.simulation.data.household uses domain.shared.enums.household, so a change to domain.shared.enums.household can break domain.simulation.data.household, while a change to domain.simulation.data.household can't break domain.shared.enums.household.
- Position
- Below the diagonal: domain.simulation.data.household uses a module listed above it, which is the healthy direction.
27→7 domain.simulation.data.household uses utils✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.household uses a type in utils.
- The types involved
edu.kit.ifv.domain.simulation.data.household.IHousehold→edu.kit.ifv.utils.Identifiable
- Direction
- domain.simulation.data.household uses utils, so a change to utils can break domain.simulation.data.household, while a change to domain.simulation.data.household can't break utils.
- Position
- Below the diagonal: domain.simulation.data.household uses a module listed above it, which is the healthy direction.
27→11 domain.simulation.data.household uses domain.shared.location✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.household uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.data.household.IHousehold→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.data.household uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.data.household, while a change to domain.simulation.data.household can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.data.household uses a module listed above it, which is the healthy direction.
27→19 domain.simulation.data.household uses domain.simulation.data.sharing✕
- Connections
- 1 pair of types, where a type in domain.simulation.data.household uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.domain.simulation.data.household.IHousehold→edu.kit.ifv.domain.simulation.data.sharing.HasStandardLocation
- Direction
- domain.simulation.data.household uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break domain.simulation.data.household, while a change to domain.simulation.data.household can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: domain.simulation.data.household uses a module listed above it, which is the healthy direction.
27→25 domain.simulation.data.household uses domain.simulation.data.person✕
- Connections
- 2 pairs of types, where a type in domain.simulation.data.household uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.domain.simulation.data.household.Household→edu.kit.ifv.domain.simulation.data.person.Personedu.kit.ifv.domain.simulation.data.household.IHousehold→edu.kit.ifv.domain.simulation.data.person.IPerson
- Direction
- domain.simulation.data.household uses domain.simulation.data.person, so a change to domain.simulation.data.person can break domain.simulation.data.household, while a change to domain.simulation.data.household can't break domain.simulation.data.person.
- Position
- Below the diagonal: domain.simulation.data.household uses a module listed above it, which is the healthy direction.
28→1 domain.simulation.parser uses utils.codes✕
- Connections
- 6 pairs of types, where a type in domain.simulation.parser uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.simulation.parser.ActivityCsvConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.simulation.parser.PersonCodePlans→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.simulation.parser.PersonCsvConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.simulation.parser.PrivateCarCsvConfig→edu.kit.ifv.utils.codes.Decodable
- Direction
- domain.simulation.parser uses utils.codes, so a change to utils.codes can break domain.simulation.parser, while a change to domain.simulation.parser can't break utils.codes.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→3 domain.simulation.parser uses domain.shared.enums✕
- Connections
- 5 pairs of types, where a type in domain.simulation.parser uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.parser.ActivityCsvConfig→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfig→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.parser uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→5 domain.simulation.parser uses domain.shared.enums.household✕
- Connections
- 1 pair of types, where a type in domain.simulation.parser uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- domain.simulation.parser uses domain.shared.enums.household, so a change to domain.shared.enums.household can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.enums.household.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→6 domain.simulation.parser uses domain.shared.enums.person✕
- Connections
- 6 pairs of types, where a type in domain.simulation.parser uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.simulation.parser.PersonCodePlans→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.simulation.parser.PersonCodePlans→edu.kit.ifv.domain.shared.enums.person.Graduationedu.kit.ifv.domain.simulation.parser.PersonCodePlans→edu.kit.ifv.domain.shared.enums.person.Sexedu.kit.ifv.domain.simulation.parser.PersonCsvConfig→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.simulation.parser.PersonCsvConfig→edu.kit.ifv.domain.shared.enums.person.Graduationedu.kit.ifv.domain.simulation.parser.PersonCsvConfig→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- domain.simulation.parser uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→7 domain.simulation.parser uses utils✕
- Connections
- 8 pairs of types, where a type in domain.simulation.parser uses a type in utils.
- The types involved
edu.kit.ifv.domain.simulation.parser.ActivityCsvConfig→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.ActivityCsvParserKt→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfig→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.PersonCsvConfig→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.PrivateCarCsvConfig→edu.kit.ifv.utils.ErrorHandlingedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.utils.ErrorHandling
- Direction
- domain.simulation.parser uses utils, so a change to utils can break domain.simulation.parser, while a change to domain.simulation.parser can't break utils.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→8 domain.simulation.parser uses domain.shared.car✕
- Connections
- 1 pair of types, where a type in domain.simulation.parser uses a type in domain.shared.car.
- The types involved
edu.kit.ifv.domain.simulation.parser.PrivateCarCsvConfig→edu.kit.ifv.domain.shared.car.CarSegment
- Direction
- domain.simulation.parser uses domain.shared.car, so a change to domain.shared.car can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.car.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→9 domain.simulation.parser uses domain.shared.location.zone.attributes✕
- Connections
- 5 pairs of types, where a type in domain.simulation.parser uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfig→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionTypeedu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionTypeedu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionTypeedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionTypeedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionType
- Direction
- domain.simulation.parser uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→10 domain.simulation.parser uses utils.csv✕
- Connections
- 17 pairs of types, where a type in domain.simulation.parser uses a type in utils.csv.
- The types involved
edu.kit.ifv.domain.simulation.parser.ActivityCsvParserKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.domain.simulation.parser.ActivityCsvParserKt→edu.kit.ifv.utils.csv.DefaultCsvParseredu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfig→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.DrtProvidersByServiceAreaParserKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.domain.simulation.parser.FixedDestinationCsvParserKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.domain.simulation.parser.GlobalDrtProviderIdCounter→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.GlobalSharingProviderIdCounter→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.GlobalSharingStationIdCounter→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.HouseholdCsvParserKt→edu.kit.ifv.utils.csv.FilterRowCsvParseredu.kit.ifv.domain.simulation.parser.PersonCsvParserKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.domain.simulation.parser.PrivateCarCsvConfig→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.PrivateCarCsvParserKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.domain.simulation.parser.PrivateCarCsvParserKt→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.utils.csv.Row
- Direction
- domain.simulation.parser uses utils.csv, so a change to utils.csv can break domain.simulation.parser, while a change to domain.simulation.parser can't break utils.csv.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→11 domain.simulation.parser uses domain.shared.location✕
- Connections
- 5 pairs of types, where a type in domain.simulation.parser uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.domain.shared.location.PointAndRoadPositionParseredu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.domain.shared.location.PointAndRoadPositionParseredu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.parser uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→13 domain.simulation.parser uses domain.shared.location.zone✕
- Connections
- 10 pairs of types, where a type in domain.simulation.parser uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfig→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfig→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfig→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.HouseholdCsvConfig→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.SharingProvidersByStationParserKt→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- domain.simulation.parser uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.shared.location.zone.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→14 domain.simulation.parser uses domain.simulation.data✕
- Connections
- 1 pair of types, where a type in domain.simulation.parser uses a type in domain.simulation.data.
- The types involved
edu.kit.ifv.domain.simulation.parser.FixedDestinationCsvParserKt→edu.kit.ifv.domain.simulation.data.ActivityLocation
- Direction
- domain.simulation.parser uses domain.simulation.data, so a change to domain.simulation.data can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.simulation.data.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→19 domain.simulation.parser uses domain.simulation.data.sharing✕
- Connections
- 5 pairs of types, where a type in domain.simulation.parser uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.domain.simulation.parser.GlobalSharingProviderIdCounter→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderIdedu.kit.ifv.domain.simulation.parser.GlobalSharingStationIdCounter→edu.kit.ifv.domain.simulation.data.sharing.SharingStationIdedu.kit.ifv.domain.simulation.parser.PersonCsvConfig→edu.kit.ifv.domain.simulation.data.sharing.SharingProvideredu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderIdedu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig→edu.kit.ifv.domain.simulation.data.sharing.SharingStationId
- Direction
- domain.simulation.parser uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
28→25 domain.simulation.parser uses domain.simulation.data.person✕
- Connections
- 1 pair of types, where a type in domain.simulation.parser uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.domain.simulation.parser.PrivateCarCsvConfig→edu.kit.ifv.domain.simulation.data.person.Person
- Direction
- domain.simulation.parser uses domain.simulation.data.person, so a change to domain.simulation.data.person can break domain.simulation.parser, while a change to domain.simulation.parser can't break domain.simulation.data.person.
- Position
- Below the diagonal: domain.simulation.parser uses a module listed above it, which is the healthy direction.
29→1 domain.simulation.parser.binary uses utils.codes✕
- Connections
- 2 pairs of types, where a type in domain.simulation.parser.binary uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.BinaryActivityReader→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.simulation.parser.binary.FixedDestinationReader→edu.kit.ifv.utils.codes.Decodable
- Direction
- domain.simulation.parser.binary uses utils.codes, so a change to utils.codes can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break utils.codes.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
29→3 domain.simulation.parser.binary uses domain.shared.enums✕
- Connections
- 2 pairs of types, where a type in domain.simulation.parser.binary uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.BinaryActivityReader→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.simulation.parser.binary.FixedDestinationReader→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- domain.simulation.parser.binary uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
29→9 domain.simulation.parser.binary uses domain.shared.location.zone.attributes✕
- Connections
- 2 pairs of types, where a type in domain.simulation.parser.binary uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.BinaryHouseholdReader→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionTypeedu.kit.ifv.domain.simulation.parser.binary.FixedDestinationReader→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionType
- Direction
- domain.simulation.parser.binary uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
29→13 domain.simulation.parser.binary uses domain.shared.location.zone✕
- Connections
- 4 pairs of types, where a type in domain.simulation.parser.binary uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.BinaryHouseholdReader→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.binary.BinaryHouseholdReader→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.domain.simulation.parser.binary.FixedDestinationReader→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.domain.simulation.parser.binary.FixedDestinationReader→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- domain.simulation.parser.binary uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break domain.shared.location.zone.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
29→14 domain.simulation.parser.binary uses domain.simulation.data✕
- Connections
- 1 pair of types, where a type in domain.simulation.parser.binary uses a type in domain.simulation.data.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.FixedDestinationReader→edu.kit.ifv.domain.simulation.data.ActivityLocation
- Direction
- domain.simulation.parser.binary uses domain.simulation.data, so a change to domain.simulation.data can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break domain.simulation.data.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
29→19 domain.simulation.parser.binary uses domain.simulation.data.sharing✕
- Connections
- 2 pairs of types, where a type in domain.simulation.parser.binary uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.BinaryPersonReader→edu.kit.ifv.domain.simulation.data.sharing.SharingProvideredu.kit.ifv.domain.simulation.parser.binary.BinaryPersonReader→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderId
- Direction
- domain.simulation.parser.binary uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
29→25 domain.simulation.parser.binary uses domain.simulation.data.person✕
- Connections
- 1 pair of types, where a type in domain.simulation.parser.binary uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.domain.simulation.parser.binary.BinaryCarReader→edu.kit.ifv.domain.simulation.data.person.Person
- Direction
- domain.simulation.parser.binary uses domain.simulation.data.person, so a change to domain.simulation.data.person can break domain.simulation.parser.binary, while a change to domain.simulation.parser.binary can't break domain.simulation.data.person.
- Position
- Below the diagonal: domain.simulation.parser.binary uses a module listed above it, which is the healthy direction.
30→3 application.steps.parser.csv uses domain.shared.enums✕
- Connections
- 4 pairs of types, where a type in application.steps.parser.csv uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadAttractivenessStepKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.parser.csv.LoadDrtProvidersKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.parser.csv.LoadFixedDestinationsKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- application.steps.parser.csv uses domain.shared.enums, so a change to domain.shared.enums can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.shared.enums.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→8 application.steps.parser.csv uses domain.shared.car✕
- Connections
- 1 pair of types, where a type in application.steps.parser.csv uses a type in domain.shared.car.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadPrivateCarsKt→edu.kit.ifv.domain.shared.car.CarId
- Direction
- application.steps.parser.csv uses domain.shared.car, so a change to domain.shared.car can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.shared.car.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→9 application.steps.parser.csv uses domain.shared.location.zone.attributes✕
- Connections
- 1 pair of types, where a type in application.steps.parser.csv uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.shared.location.zone.attributes.HasRegionType
- Direction
- application.steps.parser.csv uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→10 application.steps.parser.csv uses utils.csv✕
- Connections
- 10 pairs of types, where a type in application.steps.parser.csv uses a type in utils.csv.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadCustomPersonsKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadDrtProvidersKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadFixedDestinationsKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadHouseholdsKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadPersonsKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadPlannedActivitiesKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadPrivateCarsKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.utils.csv.CsvParseredu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.application.steps.parser.csv.LoadZonesKt→edu.kit.ifv.utils.csv.CsvParser
- Direction
- application.steps.parser.csv uses utils.csv, so a change to utils.csv can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break utils.csv.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→11 application.steps.parser.csv uses domain.shared.location✕
- Connections
- 1 pair of types, where a type in application.steps.parser.csv uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- application.steps.parser.csv uses domain.shared.location, so a change to domain.shared.location can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.shared.location.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→12 application.steps.parser.csv uses domain.shared.datastructure.schedule.action✕
- Connections
- 2 pairs of types, where a type in application.steps.parser.csv uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadPlannedActivitiesKt→edu.kit.ifv.domain.shared.datastructure.schedule.action.Activityedu.kit.ifv.application.steps.parser.csv.LoadPlannedActivitiesKt→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivity
- Direction
- application.steps.parser.csv uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→13 application.steps.parser.csv uses domain.shared.location.zone✕
- Connections
- 4 pairs of types, where a type in application.steps.parser.csv uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.shared.location.zone.ZoneIdedu.kit.ifv.application.steps.parser.csv.LoadZonesKt→edu.kit.ifv.domain.shared.location.zone.MaximalZoneedu.kit.ifv.application.steps.parser.csv.LoadZonesKt→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- application.steps.parser.csv uses domain.shared.location.zone, so a change to domain.shared.location.zone can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.shared.location.zone.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→14 application.steps.parser.csv uses domain.simulation.data✕
- Connections
- 1 pair of types, where a type in application.steps.parser.csv uses a type in domain.simulation.data.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadFixedDestinationsKt→edu.kit.ifv.domain.simulation.data.ActivityLocation
- Direction
- application.steps.parser.csv uses domain.simulation.data, so a change to domain.simulation.data can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.simulation.data.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→19 application.steps.parser.csv uses domain.simulation.data.sharing✕
- Connections
- 1 pair of types, where a type in application.steps.parser.csv uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderId
- Direction
- application.steps.parser.csv uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
30→28 application.steps.parser.csv uses domain.simulation.parser✕
- Connections
- 7 pairs of types, where a type in application.steps.parser.csv uses a type in domain.simulation.parser.
- The types involved
edu.kit.ifv.application.steps.parser.csv.LoadDrtProvidersKt→edu.kit.ifv.domain.simulation.parser.DrtProviderByAreaCsvConfigedu.kit.ifv.application.steps.parser.csv.LoadFixedDestinationsKt→edu.kit.ifv.domain.simulation.parser.FixedDestinationCsvConfigedu.kit.ifv.application.steps.parser.csv.LoadHouseholdsKt→edu.kit.ifv.domain.simulation.parser.HouseholdCsvConfigedu.kit.ifv.application.steps.parser.csv.LoadPersonsKt→edu.kit.ifv.domain.simulation.parser.PersonCsvConfigedu.kit.ifv.application.steps.parser.csv.LoadPlannedActivitiesKt→edu.kit.ifv.domain.simulation.parser.ActivityCsvConfigedu.kit.ifv.application.steps.parser.csv.LoadPrivateCarsKt→edu.kit.ifv.domain.simulation.parser.PrivateCarCsvConfigedu.kit.ifv.application.steps.parser.csv.LoadSharingStationsKt→edu.kit.ifv.domain.simulation.parser.SharingProviderByStationCsvConfig
- Direction
- application.steps.parser.csv uses domain.simulation.parser, so a change to domain.simulation.parser can break application.steps.parser.csv, while a change to application.steps.parser.csv can't break domain.simulation.parser.
- Position
- Below the diagonal: application.steps.parser.csv uses a module listed above it, which is the healthy direction.
31→2 domain.simulation.agent uses utils.units✕
- Connections
- 5 pairs of types, where a type in domain.simulation.agent uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.simulation.agent.DrtAlgorithm→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.agent.DrtOffer→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.agent.DrtProviderAgent→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.agent.DrtRequest→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.agent.SimpleMatrixDrtAlgorithm→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.simulation.agent uses utils.units, so a change to utils.units can break domain.simulation.agent, while a change to domain.simulation.agent can't break utils.units.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→3 domain.simulation.agent uses domain.shared.enums✕
- Connections
- 3 pairs of types, where a type in domain.simulation.agent uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.agent.PersonAgentKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.agent.SharingProviderAgent→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.agent.SharingVehicleAgent→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.agent uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→7 domain.simulation.agent uses utils✕
- Connections
- 1 pair of types, where a type in domain.simulation.agent uses a type in utils.
- The types involved
edu.kit.ifv.domain.simulation.agent.SharingVehicleAgent→edu.kit.ifv.utils.Identifiable
- Direction
- domain.simulation.agent uses utils, so a change to utils can break domain.simulation.agent, while a change to domain.simulation.agent can't break utils.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→8 domain.simulation.agent uses domain.shared.car✕
- Connections
- 3 pairs of types, where a type in domain.simulation.agent uses a type in domain.shared.car.
- The types involved
edu.kit.ifv.domain.simulation.agent.BuildAgents→edu.kit.ifv.domain.shared.car.CarIdedu.kit.ifv.domain.simulation.agent.CarAgent→edu.kit.ifv.domain.shared.car.Caredu.kit.ifv.domain.simulation.agent.PrivateCarAgent→edu.kit.ifv.domain.shared.car.CarId
- Direction
- domain.simulation.agent uses domain.shared.car, so a change to domain.shared.car can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.shared.car.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→11 domain.simulation.agent uses domain.shared.location✕
- Connections
- 10 pairs of types, where a type in domain.simulation.agent uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.agent.CarAgent→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.DrtAlgorithm→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.DrtOffer→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.DrtProviderAgent→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.DrtRequest→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.PersonAgent→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.PersonAgentKt→edu.kit.ifv.domain.shared.location.Locationedu.kit.ifv.domain.simulation.agent.PrivateCarAgent→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.agent.SimpleMatrixDrtAlgorithm→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.simulation.agent.SimpleMatrixDrtAlgorithm→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.agent uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→12 domain.simulation.agent uses domain.shared.datastructure.schedule.action✕
- Connections
- 1 pair of types, where a type in domain.simulation.agent uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.domain.simulation.agent.PersonAgentKt→edu.kit.ifv.domain.shared.datastructure.schedule.action.Action
- Direction
- domain.simulation.agent uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→13 domain.simulation.agent uses domain.shared.location.zone✕
- Connections
- 1 pair of types, where a type in domain.simulation.agent uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.domain.simulation.agent.SimpleMatrixDrtAlgorithm→edu.kit.ifv.domain.shared.location.zone.Zone
- Direction
- domain.simulation.agent uses domain.shared.location.zone, so a change to domain.shared.location.zone can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.shared.location.zone.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→19 domain.simulation.agent uses domain.simulation.data.sharing✕
- Connections
- 7 pairs of types, where a type in domain.simulation.agent uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.domain.simulation.agent.BuildAgents→edu.kit.ifv.domain.simulation.data.sharing.SharingProvideredu.kit.ifv.domain.simulation.agent.BuildAgents→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderIdedu.kit.ifv.domain.simulation.agent.BuildAgents→edu.kit.ifv.domain.simulation.data.sharing.SharingStationIdedu.kit.ifv.domain.simulation.agent.SharingProviderAgent→edu.kit.ifv.domain.simulation.data.sharing.ISharingProvideredu.kit.ifv.domain.simulation.agent.SharingProviderAgent→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderIdedu.kit.ifv.domain.simulation.agent.SharingStationAgent→edu.kit.ifv.domain.simulation.data.sharing.ISharingStationedu.kit.ifv.domain.simulation.agent.SharingStationAgent→edu.kit.ifv.domain.simulation.data.sharing.SharingStationId
- Direction
- domain.simulation.agent uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→23 domain.simulation.agent uses domain.shared.datastructure.schedule✕
- Connections
- 1 pair of types, where a type in domain.simulation.agent uses a type in domain.shared.datastructure.schedule.
- The types involved
edu.kit.ifv.domain.simulation.agent.PersonAgent→edu.kit.ifv.domain.shared.datastructure.schedule.Schedule
- Direction
- domain.simulation.agent uses domain.shared.datastructure.schedule, so a change to domain.shared.datastructure.schedule can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.shared.datastructure.schedule.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→25 domain.simulation.agent uses domain.simulation.data.person✕
- Connections
- 2 pairs of types, where a type in domain.simulation.agent uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.domain.simulation.agent.BuildAgentsKt→edu.kit.ifv.domain.simulation.data.person.Personedu.kit.ifv.domain.simulation.agent.PersonAgent→edu.kit.ifv.domain.simulation.data.person.IPerson
- Direction
- domain.simulation.agent uses domain.simulation.data.person, so a change to domain.simulation.data.person can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.simulation.data.person.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→27 domain.simulation.agent uses domain.simulation.data.household✕
- Connections
- 3 pairs of types, where a type in domain.simulation.agent uses a type in domain.simulation.data.household.
- The types involved
edu.kit.ifv.domain.simulation.agent.BuildAgents→edu.kit.ifv.domain.simulation.data.household.Householdedu.kit.ifv.domain.simulation.agent.BuildAgentsKt→edu.kit.ifv.domain.simulation.data.household.Householdedu.kit.ifv.domain.simulation.agent.HouseholdAgent→edu.kit.ifv.domain.simulation.data.household.IHousehold
- Direction
- domain.simulation.agent uses domain.simulation.data.household, so a change to domain.simulation.data.household can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.simulation.data.household.
- Position
- Below the diagonal: domain.simulation.agent uses a module listed above it, which is the healthy direction.
31→34 domain.simulation.agent uses domain.simulation.behavior.availability part of a loop✕
- Connections
- 1 pair of types, where a type in domain.simulation.agent uses a type in domain.simulation.behavior.availability.
- The types involved
edu.kit.ifv.domain.simulation.agent.PersonAgent→edu.kit.ifv.domain.simulation.behavior.availability.ModeResource
- Direction
- domain.simulation.agent uses domain.simulation.behavior.availability, so a change to domain.simulation.behavior.availability can break domain.simulation.agent, while a change to domain.simulation.agent can't break domain.simulation.behavior.availability.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→2 application.steps.results uses utils.units✕
- Connections
- 3 pairs of types, where a type in application.steps.results uses a type in utils.units.
- The types involved
edu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.application.steps.results.MidComparisonLegPlotBuilder→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.application.steps.results.MidLegRow→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- application.steps.results uses utils.units, so a change to utils.units can break application.steps.results, while a change to application.steps.results can't break utils.units.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→3 application.steps.results uses domain.shared.enums✕
- Connections
- 7 pairs of types, where a type in application.steps.results uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.application.steps.results.AddDefaultMIDComparisonPlotsKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.results.EvaluatePersonScheduleKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.results.MidLegRow→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.results.MidLegRow→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.results.PersonLeg→edu.kit.ifv.domain.shared.enums.ActivityType
- Direction
- application.steps.results uses domain.shared.enums, so a change to domain.shared.enums can break application.steps.results, while a change to application.steps.results can't break domain.shared.enums.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→4 application.steps.results uses domain.shared.enums.areatype✕
- Connections
- 1 pair of types, where a type in application.steps.results uses a type in domain.shared.enums.areatype.
- The types involved
edu.kit.ifv.application.steps.results.MidRow→edu.kit.ifv.domain.shared.enums.areatype.RegioStaR7
- Direction
- application.steps.results uses domain.shared.enums.areatype, so a change to domain.shared.enums.areatype can break application.steps.results, while a change to application.steps.results can't break domain.shared.enums.areatype.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→5 application.steps.results uses domain.shared.enums.household✕
- Connections
- 2 pairs of types, where a type in application.steps.results uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.domain.shared.enums.household.EconomicStatusedu.kit.ifv.application.steps.results.MidRow→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- application.steps.results uses domain.shared.enums.household, so a change to domain.shared.enums.household can break application.steps.results, while a change to application.steps.results can't break domain.shared.enums.household.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→6 application.steps.results uses domain.shared.enums.person✕
- Connections
- 4 pairs of types, where a type in application.steps.results uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.application.steps.results.MidComparisonLegPlotBuilder→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.application.steps.results.MidRow→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.application.steps.results.MidRow→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- application.steps.results uses domain.shared.enums.person, so a change to domain.shared.enums.person can break application.steps.results, while a change to application.steps.results can't break domain.shared.enums.person.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→10 application.steps.results uses utils.csv✕
- Connections
- 4 pairs of types, where a type in application.steps.results uses a type in utils.csv.
- The types involved
edu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.application.steps.results.MidLegRow→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.application.steps.results.MidPersonRow→edu.kit.ifv.utils.csv.Rowedu.kit.ifv.application.steps.results.MidRow→edu.kit.ifv.utils.csv.Row
- Direction
- application.steps.results uses utils.csv, so a change to utils.csv can break application.steps.results, while a change to application.steps.results can't break utils.csv.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→11 application.steps.results uses domain.shared.location✕
- Connections
- 4 pairs of types, where a type in application.steps.results uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.application.steps.results.EvaluatePersonScheduleKt→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.steps.results.MidComparisonLegPlotBuilder→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.steps.results.MidComparisonPlotBuilderKt→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.steps.results.StandardCSVLegWriter→edu.kit.ifv.domain.shared.location.Impedance
- Direction
- application.steps.results uses domain.shared.location, so a change to domain.shared.location can break application.steps.results, while a change to application.steps.results can't break domain.shared.location.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→12 application.steps.results uses domain.shared.datastructure.schedule.action✕
- Connections
- 4 pairs of types, where a type in application.steps.results uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.application.steps.results.EvaluatePersonScheduleKt→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedActivityedu.kit.ifv.application.steps.results.PersonLeg→edu.kit.ifv.domain.shared.datastructure.schedule.action.MovingActionedu.kit.ifv.application.steps.results.StandardCSVLegWriter→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLegedu.kit.ifv.application.steps.results.WriteLegToCSV→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedLeg
- Direction
- application.steps.results uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break application.steps.results, while a change to application.steps.results can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→16 application.steps.results uses domain.shared.behavior✕
- Connections
- 10 pairs of types, where a type in application.steps.results uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.application.steps.results.AddDefaultMIDComparisonPlotsKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelModesedu.kit.ifv.application.steps.results.AddDefaultMIDComparisonPlotsKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposesedu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelModesedu.kit.ifv.application.steps.results.MidComparisonDataKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposesedu.kit.ifv.application.steps.results.MidComparisonLegPlotBuilder→edu.kit.ifv.domain.shared.behavior.ChoiceModelModesedu.kit.ifv.application.steps.results.MidComparisonLegPlotBuilder→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposesedu.kit.ifv.application.steps.results.MidComparisonPlotBuilderKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelModesedu.kit.ifv.application.steps.results.MidComparisonPlotBuilderKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposesedu.kit.ifv.application.steps.results.MidLegRow→edu.kit.ifv.domain.shared.behavior.ChoiceModelModesedu.kit.ifv.application.steps.results.MidLegRow→edu.kit.ifv.domain.shared.behavior.ChoiceModelPurposes
- Direction
- application.steps.results uses domain.shared.behavior, so a change to domain.shared.behavior can break application.steps.results, while a change to application.steps.results can't break domain.shared.behavior.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→25 application.steps.results uses domain.simulation.data.person✕
- Connections
- 2 pairs of types, where a type in application.steps.results uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.application.steps.results.MidComparisonPersonPlotBuilder→edu.kit.ifv.domain.simulation.data.person.IPersonedu.kit.ifv.application.steps.results.MidComparisonPlotBuilderKt→edu.kit.ifv.domain.simulation.data.person.IPerson
- Direction
- application.steps.results uses domain.simulation.data.person, so a change to domain.simulation.data.person can break application.steps.results, while a change to application.steps.results can't break domain.simulation.data.person.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→27 application.steps.results uses domain.simulation.data.household✕
- Connections
- 2 pairs of types, where a type in application.steps.results uses a type in domain.simulation.data.household.
- The types involved
edu.kit.ifv.application.steps.results.EvaluatePersonScheduleKt→edu.kit.ifv.domain.simulation.data.household.Householdedu.kit.ifv.application.steps.results.MidComparisonPersonPlotBuilder→edu.kit.ifv.domain.simulation.data.household.IHousehold
- Direction
- application.steps.results uses domain.simulation.data.household, so a change to domain.simulation.data.household can break application.steps.results, while a change to application.steps.results can't break domain.simulation.data.household.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
32→31 application.steps.results uses domain.simulation.agent✕
- Connections
- 7 pairs of types, where a type in application.steps.results uses a type in domain.simulation.agent.
- The types involved
edu.kit.ifv.application.steps.results.EvaluatePersonScheduleKt→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.application.steps.results.MidComparisonLegPlotBuilder→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.application.steps.results.MidComparisonPersonPlotBuilder→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.application.steps.results.MidComparisonPlotBuilderKt→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.application.steps.results.PersonLeg→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.application.steps.results.StandardCSVLegWriter→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.application.steps.results.WriteLegToCSV→edu.kit.ifv.domain.simulation.agent.PersonAgent
- Direction
- application.steps.results uses domain.simulation.agent, so a change to domain.simulation.agent can break application.steps.results, while a change to application.steps.results can't break domain.simulation.agent.
- Position
- Below the diagonal: application.steps.results uses a module listed above it, which is the healthy direction.
33→2 domain.simulation.behavior.modechoice uses utils.units✕
- Connections
- 3 pairs of types, where a type in domain.simulation.behavior.modechoice uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceAlternative→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristicsImpl→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.simulation.behavior.modechoice uses utils.units, so a change to utils.units can break domain.simulation.behavior.modechoice, while a change to domain.simulation.behavior.modechoice can't break utils.units.
- Position
- Below the diagonal: domain.simulation.behavior.modechoice uses a module listed above it, which is the healthy direction.
33→3 domain.simulation.behavior.modechoice uses domain.shared.enums✕
- Connections
- 4 pairs of types, where a type in domain.simulation.behavior.modechoice uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.behavior.modechoice.LegacyModeChoiceKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceAlternative→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristicsImpl→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.behavior.modechoice uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.behavior.modechoice, while a change to domain.simulation.behavior.modechoice can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.behavior.modechoice uses a module listed above it, which is the healthy direction.
33→6 domain.simulation.behavior.modechoice uses domain.shared.enums.person✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.modechoice uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.simulation.behavior.modechoice.LegacyModeChoiceKt→edu.kit.ifv.domain.shared.enums.person.Employment
- Direction
- domain.simulation.behavior.modechoice uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.simulation.behavior.modechoice, while a change to domain.simulation.behavior.modechoice can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.simulation.behavior.modechoice uses a module listed above it, which is the healthy direction.
33→11 domain.simulation.behavior.modechoice uses domain.shared.location✕
- Connections
- 4 pairs of types, where a type in domain.simulation.behavior.modechoice uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.behavior.modechoice.LegacyModeChoiceKt→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceAlternative→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristicsImpl→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.behavior.modechoice uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.behavior.modechoice, while a change to domain.simulation.behavior.modechoice can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.behavior.modechoice uses a module listed above it, which is the healthy direction.
33→31 domain.simulation.behavior.modechoice uses domain.simulation.agent✕
- Connections
- 3 pairs of types, where a type in domain.simulation.behavior.modechoice uses a type in domain.simulation.agent.
- The types involved
edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceAlternative→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristicsImpl→edu.kit.ifv.domain.simulation.agent.PersonAgent
- Direction
- domain.simulation.behavior.modechoice uses domain.simulation.agent, so a change to domain.simulation.agent can break domain.simulation.behavior.modechoice, while a change to domain.simulation.behavior.modechoice can't break domain.simulation.agent.
- Position
- Below the diagonal: domain.simulation.behavior.modechoice uses a module listed above it, which is the healthy direction.
34→2 domain.simulation.behavior.availability uses utils.units✕
- Connections
- 2 pairs of types, where a type in domain.simulation.behavior.availability uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.behavior.availability.ProviderAvailabilityKt→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.simulation.behavior.availability uses utils.units, so a change to utils.units can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break utils.units.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
34→3 domain.simulation.behavior.availability uses domain.shared.enums✕
- Connections
- 11 pairs of types, where a type in domain.simulation.behavior.availability uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.BikeResource→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.CarResource→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.DefaultAvailabilityModelKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.ModeResource→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.NoResourceMode→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.PoolingResource→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.ProviderAvailability→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.ProviderAvailabilityKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.SharingFreeResource→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.behavior.availability.SharingStationResource→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.behavior.availability uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
34→11 domain.simulation.behavior.availability uses domain.shared.location✕
- Connections
- 3 pairs of types, where a type in domain.simulation.behavior.availability uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.DefaultAvailabilityModelKt→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.availability.ProviderAvailabilityKt→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.behavior.availability uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
34→16 domain.simulation.behavior.availability uses domain.shared.behavior✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.availability uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.DefaultAvailabilityModelKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelModes
- Direction
- domain.simulation.behavior.availability uses domain.shared.behavior, so a change to domain.shared.behavior can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break domain.shared.behavior.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
34→25 domain.simulation.behavior.availability uses domain.simulation.data.person✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.availability uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel→edu.kit.ifv.domain.simulation.data.person.IPerson
- Direction
- domain.simulation.behavior.availability uses domain.simulation.data.person, so a change to domain.simulation.data.person can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break domain.simulation.data.person.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
34→31 domain.simulation.behavior.availability uses domain.simulation.agent✕
- Connections
- 16 pairs of types, where a type in domain.simulation.behavior.availability uses a type in domain.simulation.agent.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.BikeResource→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.CarResource→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.CarResource→edu.kit.ifv.domain.simulation.agent.PrivateCarAgentedu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.ModeResource→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.NoResourceMode→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.PoolingResource→edu.kit.ifv.domain.simulation.agent.DrtOfferedu.kit.ifv.domain.simulation.behavior.availability.PoolingResource→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.behavior.availability.PoolingResource→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.ProviderAvailabilityKt→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.SharingFreeResource→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.SharingFreeResource→edu.kit.ifv.domain.simulation.agent.SharingStationAgentedu.kit.ifv.domain.simulation.behavior.availability.SharingFreeResource→edu.kit.ifv.domain.simulation.agent.SharingVehicleAgentedu.kit.ifv.domain.simulation.behavior.availability.SharingStationResource→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.availability.SharingStationResource→edu.kit.ifv.domain.simulation.agent.SharingStationAgentedu.kit.ifv.domain.simulation.behavior.availability.SharingStationResource→edu.kit.ifv.domain.simulation.agent.SharingVehicleAgent
- Direction
- domain.simulation.behavior.availability uses domain.simulation.agent, so a change to domain.simulation.agent can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break domain.simulation.agent.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
34→33 domain.simulation.behavior.availability uses domain.simulation.behavior.modechoice✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.availability uses a type in domain.simulation.behavior.modechoice.
- The types involved
edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics
- Direction
- domain.simulation.behavior.availability uses domain.simulation.behavior.modechoice, so a change to domain.simulation.behavior.modechoice can break domain.simulation.behavior.availability, while a change to domain.simulation.behavior.availability can't break domain.simulation.behavior.modechoice.
- Position
- Below the diagonal: domain.simulation.behavior.availability uses a module listed above it, which is the healthy direction.
35→2 domain.simulation.behavior.destinationchoice uses utils.units✕
- Connections
- 2 pairs of types, where a type in domain.simulation.behavior.destinationchoice uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristicsImpl→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.simulation.behavior.destinationchoice uses utils.units, so a change to utils.units can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break utils.units.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→3 domain.simulation.behavior.destinationchoice uses domain.shared.enums✕
- Connections
- 2 pairs of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.behavior.destinationchoice uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→6 domain.simulation.behavior.destinationchoice uses domain.shared.enums.person✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.shared.enums.person.Employment
- Direction
- domain.simulation.behavior.destinationchoice uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→9 domain.simulation.behavior.destinationchoice uses domain.shared.location.zone.attributes✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.shared.location.zone.attributes.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.shared.location.zone.attributes.HasZoneId
- Direction
- domain.simulation.behavior.destinationchoice uses domain.shared.location.zone.attributes, so a change to domain.shared.location.zone.attributes can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.shared.location.zone.attributes.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→11 domain.simulation.behavior.destinationchoice uses domain.shared.location✕
- Connections
- 5 pairs of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationAlternative→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristicsImpl→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristicsKt→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.shared.location.Impedance
- Direction
- domain.simulation.behavior.destinationchoice uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→16 domain.simulation.behavior.destinationchoice uses domain.shared.behavior✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.shared.behavior.AttractivenessModel
- Direction
- domain.simulation.behavior.destinationchoice uses domain.shared.behavior, so a change to domain.shared.behavior can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.shared.behavior.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→31 domain.simulation.behavior.destinationchoice uses domain.simulation.agent✕
- Connections
- 2 pairs of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.simulation.agent.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristicsImpl→edu.kit.ifv.domain.simulation.agent.PersonAgent
- Direction
- domain.simulation.behavior.destinationchoice uses domain.simulation.agent, so a change to domain.simulation.agent can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.simulation.agent.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
35→34 domain.simulation.behavior.destinationchoice uses domain.simulation.behavior.availability✕
- Connections
- 1 pair of types, where a type in domain.simulation.behavior.destinationchoice uses a type in domain.simulation.behavior.availability.
- The types involved
edu.kit.ifv.domain.simulation.behavior.destinationchoice.LegacyDestinationChoiceKt→edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel
- Direction
- domain.simulation.behavior.destinationchoice uses domain.simulation.behavior.availability, so a change to domain.simulation.behavior.availability can break domain.simulation.behavior.destinationchoice, while a change to domain.simulation.behavior.destinationchoice can't break domain.simulation.behavior.availability.
- Position
- Below the diagonal: domain.simulation.behavior.destinationchoice uses a module listed above it, which is the healthy direction.
36→3 application.config uses domain.shared.enums✕
- Connections
- 1 pair of types, where a type in application.config uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- application.config uses domain.shared.enums, so a change to domain.shared.enums can break application.config, while a change to application.config can't break domain.shared.enums.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→7 application.config uses utils✕
- Connections
- 1 pair of types, where a type in application.config uses a type in utils.
- The types involved
edu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.utils.ErrorHandling
- Direction
- application.config uses utils, so a change to utils can break application.config, while a change to application.config can't break utils.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→11 application.config uses domain.shared.location✕
- Connections
- 3 pairs of types, where a type in application.config uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.application.config.DestinationChoiceFactory→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.config.ModeChoiceFactory→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- application.config uses domain.shared.location, so a change to domain.shared.location can break application.config, while a change to application.config can't break domain.shared.location.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→16 application.config uses domain.shared.behavior✕
- Connections
- 2 pairs of types, where a type in application.config uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.application.config.DestinationChoiceFactory→edu.kit.ifv.domain.shared.behavior.AttractivenessModeledu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.domain.shared.behavior.ChoiceModelModes
- Direction
- application.config uses domain.shared.behavior, so a change to domain.shared.behavior can break application.config, while a change to application.config can't break domain.shared.behavior.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→17 application.config uses domain.shared.datastructure.matrix✕
- Connections
- 1 pair of types, where a type in application.config uses a type in domain.shared.datastructure.matrix.
- The types involved
edu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.domain.shared.datastructure.matrix.ZoneMatrixCreation
- Direction
- application.config uses domain.shared.datastructure.matrix, so a change to domain.shared.datastructure.matrix can break application.config, while a change to application.config can't break domain.shared.datastructure.matrix.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→33 application.config uses domain.simulation.behavior.modechoice✕
- Connections
- 1 pair of types, where a type in application.config uses a type in domain.simulation.behavior.modechoice.
- The types involved
edu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics
- Direction
- application.config uses domain.simulation.behavior.modechoice, so a change to domain.simulation.behavior.modechoice can break application.config, while a change to application.config can't break domain.simulation.behavior.modechoice.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→34 application.config uses domain.simulation.behavior.availability✕
- Connections
- 1 pair of types, where a type in application.config uses a type in domain.simulation.behavior.availability.
- The types involved
edu.kit.ifv.application.config.DestinationChoiceFactory→edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel
- Direction
- application.config uses domain.simulation.behavior.availability, so a change to domain.simulation.behavior.availability can break application.config, while a change to application.config can't break domain.simulation.behavior.availability.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
36→35 application.config uses domain.simulation.behavior.destinationchoice✕
- Connections
- 1 pair of types, where a type in application.config uses a type in domain.simulation.behavior.destinationchoice.
- The types involved
edu.kit.ifv.application.config.ShortTermConfig→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics
- Direction
- application.config uses domain.simulation.behavior.destinationchoice, so a change to domain.simulation.behavior.destinationchoice can break application.config, while a change to application.config can't break domain.simulation.behavior.destinationchoice.
- Position
- Below the diagonal: application.config uses a module listed above it, which is the healthy direction.
37→11 application.steps.model uses domain.shared.location✕
- Connections
- 2 pairs of types, where a type in application.steps.model uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.application.steps.model.AddDrtProviderKt→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.steps.model.LoadDestinationChoiceModelKt→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- application.steps.model uses domain.shared.location, so a change to domain.shared.location can break application.steps.model, while a change to application.steps.model can't break domain.shared.location.
- Position
- Below the diagonal: application.steps.model uses a module listed above it, which is the healthy direction.
37→13 application.steps.model uses domain.shared.location.zone✕
- Connections
- 2 pairs of types, where a type in application.steps.model uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.application.steps.model.AddDrtProviderKt→edu.kit.ifv.domain.shared.location.zone.Zoneedu.kit.ifv.application.steps.model.HomeLocationStepKt→edu.kit.ifv.domain.shared.location.zone.Zone
- Direction
- application.steps.model uses domain.shared.location.zone, so a change to domain.shared.location.zone can break application.steps.model, while a change to application.steps.model can't break domain.shared.location.zone.
- Position
- Below the diagonal: application.steps.model uses a module listed above it, which is the healthy direction.
37→25 application.steps.model uses domain.simulation.data.person✕
- Connections
- 1 pair of types, where a type in application.steps.model uses a type in domain.simulation.data.person.
- The types involved
edu.kit.ifv.application.steps.model.AddDrtMembershipsKt→edu.kit.ifv.domain.simulation.data.person.IPerson
- Direction
- application.steps.model uses domain.simulation.data.person, so a change to domain.simulation.data.person can break application.steps.model, while a change to application.steps.model can't break domain.simulation.data.person.
- Position
- Below the diagonal: application.steps.model uses a module listed above it, which is the healthy direction.
37→27 application.steps.model uses domain.simulation.data.household✕
- Connections
- 1 pair of types, where a type in application.steps.model uses a type in domain.simulation.data.household.
- The types involved
edu.kit.ifv.application.steps.model.HomeLocationStepKt→edu.kit.ifv.domain.simulation.data.household.Household
- Direction
- application.steps.model uses domain.simulation.data.household, so a change to domain.simulation.data.household can break application.steps.model, while a change to application.steps.model can't break domain.simulation.data.household.
- Position
- Below the diagonal: application.steps.model uses a module listed above it, which is the healthy direction.
37→31 application.steps.model uses domain.simulation.agent✕
- Connections
- 4 pairs of types, where a type in application.steps.model uses a type in domain.simulation.agent.
- The types involved
edu.kit.ifv.application.steps.model.AddDrtProviderKt→edu.kit.ifv.domain.simulation.agent.SimpleMatrixDrtAlgorithmedu.kit.ifv.application.steps.model.BuildAgentsStepKt→edu.kit.ifv.domain.simulation.agent.DrtAlgorithmedu.kit.ifv.application.steps.model.BuildAgentsStepKt→edu.kit.ifv.domain.simulation.agent.DrtProviderAgentedu.kit.ifv.application.steps.model.BuildAgentsStepKt→edu.kit.ifv.domain.simulation.agent.PersonAgent
- Direction
- application.steps.model uses domain.simulation.agent, so a change to domain.simulation.agent can break application.steps.model, while a change to application.steps.model can't break domain.simulation.agent.
- Position
- Below the diagonal: application.steps.model uses a module listed above it, which is the healthy direction.
37→35 application.steps.model uses domain.simulation.behavior.destinationchoice✕
- Connections
- 1 pair of types, where a type in application.steps.model uses a type in domain.simulation.behavior.destinationchoice.
- The types involved
edu.kit.ifv.application.steps.model.LoadDestinationChoiceModelKt→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics
- Direction
- application.steps.model uses domain.simulation.behavior.destinationchoice, so a change to domain.simulation.behavior.destinationchoice can break application.steps.model, while a change to application.steps.model can't break domain.simulation.behavior.destinationchoice.
- Position
- Below the diagonal: application.steps.model uses a module listed above it, which is the healthy direction.
38→2 domain.simulation.events uses utils.units✕
- Connections
- 8 pairs of types, where a type in domain.simulation.events uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.simulation.events.ActivityState→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.AfterLegAction→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.DrtProviderStartState→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.GenerateDestinationCharacteristics→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.GenerateModeCharacteristics→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.PersonStartState→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.PersonState→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.simulation.events.TripState→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.simulation.events uses utils.units, so a change to utils.units can break domain.simulation.events, while a change to domain.simulation.events can't break utils.units.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→3 domain.simulation.events uses domain.shared.enums✕
- Connections
- 2 pairs of types, where a type in domain.simulation.events uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.simulation.events.GenerateModeCharacteristics→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.simulation.events.PersonStateKt→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.simulation.events uses domain.shared.enums, so a change to domain.shared.enums can break domain.simulation.events, while a change to domain.simulation.events can't break domain.shared.enums.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→11 domain.simulation.events uses domain.shared.location✕
- Connections
- 3 pairs of types, where a type in domain.simulation.events uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.simulation.events.GenerateModeCharacteristics→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.events.PerformingActivityState→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.domain.simulation.events.TripState→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.simulation.events uses domain.shared.location, so a change to domain.shared.location can break domain.simulation.events, while a change to domain.simulation.events can't break domain.shared.location.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→12 domain.simulation.events uses domain.shared.datastructure.schedule.action✕
- Connections
- 6 pairs of types, where a type in domain.simulation.events uses a type in domain.shared.datastructure.schedule.action.
- The types involved
edu.kit.ifv.domain.simulation.events.EndActivityMessage→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.simulation.events.EndLegMessage→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.simulation.events.FirstActivityMessage→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.simulation.events.PerformLegState→edu.kit.ifv.domain.shared.datastructure.schedule.action.Legedu.kit.ifv.domain.simulation.events.PerformingActivityState→edu.kit.ifv.domain.shared.datastructure.schedule.action.StationaryActionedu.kit.ifv.domain.simulation.events.PersonState→edu.kit.ifv.domain.shared.datastructure.schedule.action.LinkedAction
- Direction
- domain.simulation.events uses domain.shared.datastructure.schedule.action, so a change to domain.shared.datastructure.schedule.action can break domain.simulation.events, while a change to domain.simulation.events can't break domain.shared.datastructure.schedule.action.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→16 domain.simulation.events uses domain.shared.behavior✕
- Connections
- 1 pair of types, where a type in domain.simulation.events uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.domain.simulation.events.PersonStateKt→edu.kit.ifv.domain.shared.behavior.ChoiceModelModes
- Direction
- domain.simulation.events uses domain.shared.behavior, so a change to domain.shared.behavior can break domain.simulation.events, while a change to domain.simulation.events can't break domain.shared.behavior.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→23 domain.simulation.events uses domain.shared.datastructure.schedule✕
- Connections
- 11 pairs of types, where a type in domain.simulation.events uses a type in domain.shared.datastructure.schedule.
- The types involved
edu.kit.ifv.domain.simulation.events.ActivityState→edu.kit.ifv.domain.shared.datastructure.schedule.Agendaedu.kit.ifv.domain.simulation.events.FinishDrtTripState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.GenerateDestinationCharacteristics→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.OnDrtEgressState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.PerformLegState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.PerformingActivityState→edu.kit.ifv.domain.shared.datastructure.schedule.Agendaedu.kit.ifv.domain.simulation.events.PersonState→edu.kit.ifv.domain.shared.datastructure.schedule.Representativeedu.kit.ifv.domain.simulation.events.StartingTripState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.TripState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.WaitingForDropOffState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTripedu.kit.ifv.domain.simulation.events.WaitingForPickupState→edu.kit.ifv.domain.shared.datastructure.schedule.LinkTrip
- Direction
- domain.simulation.events uses domain.shared.datastructure.schedule, so a change to domain.shared.datastructure.schedule can break domain.simulation.events, while a change to domain.simulation.events can't break domain.shared.datastructure.schedule.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→31 domain.simulation.events uses domain.simulation.agent✕
- Connections
- 25 pairs of types, where a type in domain.simulation.events uses a type in domain.simulation.agent.
- The types involved
edu.kit.ifv.domain.simulation.events.ActivityState→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.AfterLegAction→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.DropOffByDrtMessage→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.events.DropOffByDrtMessage→edu.kit.ifv.domain.simulation.agent.PersonMessageedu.kit.ifv.domain.simulation.events.DrtProviderStartState→edu.kit.ifv.domain.simulation.agent.DrtAlgorithmedu.kit.ifv.domain.simulation.events.DrtProviderStartState→edu.kit.ifv.domain.simulation.agent.DrtProviderAgentedu.kit.ifv.domain.simulation.events.DrtProviderStateKt→edu.kit.ifv.domain.simulation.agent.DrtProviderAgentedu.kit.ifv.domain.simulation.events.EndActivityMessage→edu.kit.ifv.domain.simulation.agent.PersonMessageedu.kit.ifv.domain.simulation.events.EndLegMessage→edu.kit.ifv.domain.simulation.agent.PersonMessageedu.kit.ifv.domain.simulation.events.FinishDrtEgressMessage→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.events.FinishDrtEgressMessage→edu.kit.ifv.domain.simulation.agent.PersonMessageedu.kit.ifv.domain.simulation.events.FinishDrtTripState→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.events.FirstActivityMessage→edu.kit.ifv.domain.simulation.agent.PersonMessageedu.kit.ifv.domain.simulation.events.GenerateDestinationCharacteristics→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.GenerateModeCharacteristics→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.InteractPersonsMessage→edu.kit.ifv.domain.simulation.agent.DrtProviderMessageedu.kit.ifv.domain.simulation.events.OnDrtEgressState→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.events.PersonStartState→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.PersonState→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.PersonStateKt→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.PickupByDrtMessage→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.events.PickupByDrtMessage→edu.kit.ifv.domain.simulation.agent.PersonMessageedu.kit.ifv.domain.simulation.events.TripState→edu.kit.ifv.domain.simulation.agent.PersonAgentedu.kit.ifv.domain.simulation.events.WaitingForDropOffState→edu.kit.ifv.domain.simulation.agent.DrtRideedu.kit.ifv.domain.simulation.events.WaitingForPickupState→edu.kit.ifv.domain.simulation.agent.DrtRide
- Direction
- domain.simulation.events uses domain.simulation.agent, so a change to domain.simulation.agent can break domain.simulation.events, while a change to domain.simulation.events can't break domain.simulation.agent.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→33 domain.simulation.events uses domain.simulation.behavior.modechoice✕
- Connections
- 2 pairs of types, where a type in domain.simulation.events uses a type in domain.simulation.behavior.modechoice.
- The types involved
edu.kit.ifv.domain.simulation.events.GenerateModeCharacteristicsKt→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristicsedu.kit.ifv.domain.simulation.events.PersonStateKt→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics
- Direction
- domain.simulation.events uses domain.simulation.behavior.modechoice, so a change to domain.simulation.behavior.modechoice can break domain.simulation.events, while a change to domain.simulation.events can't break domain.simulation.behavior.modechoice.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→34 domain.simulation.events uses domain.simulation.behavior.availability✕
- Connections
- 2 pairs of types, where a type in domain.simulation.events uses a type in domain.simulation.behavior.availability.
- The types involved
edu.kit.ifv.domain.simulation.events.PersonStateKt→edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModeledu.kit.ifv.domain.simulation.events.PersonStateKt→edu.kit.ifv.domain.simulation.behavior.availability.ModeResource
- Direction
- domain.simulation.events uses domain.simulation.behavior.availability, so a change to domain.simulation.behavior.availability can break domain.simulation.events, while a change to domain.simulation.events can't break domain.simulation.behavior.availability.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
38→35 domain.simulation.events uses domain.simulation.behavior.destinationchoice✕
- Connections
- 1 pair of types, where a type in domain.simulation.events uses a type in domain.simulation.behavior.destinationchoice.
- The types involved
edu.kit.ifv.domain.simulation.events.GenerateModeCharacteristicsKt→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics
- Direction
- domain.simulation.events uses domain.simulation.behavior.destinationchoice, so a change to domain.simulation.behavior.destinationchoice can break domain.simulation.events, while a change to domain.simulation.events can't break domain.simulation.behavior.destinationchoice.
- Position
- Below the diagonal: domain.simulation.events uses a module listed above it, which is the healthy direction.
39→1 application.steps uses utils.codes✕
- Connections
- 6 pairs of types, where a type in application.steps uses a type in utils.codes.
- The types involved
edu.kit.ifv.application.steps.ActivityTypesConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.application.steps.CarCodesConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.application.steps.HasModes→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.application.steps.HouseholdCodesConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.application.steps.ModesConfig→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.application.steps.RegionCodesConfig→edu.kit.ifv.utils.codes.Decodable
- Direction
- application.steps uses utils.codes, so a change to utils.codes can break application.steps, while a change to application.steps can't break utils.codes.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→2 application.steps uses utils.units✕
- Connections
- 1 pair of types, where a type in application.steps uses a type in utils.units.
- The types involved
edu.kit.ifv.application.steps.SimulationConfig→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- application.steps uses utils.units, so a change to utils.units can break application.steps, while a change to application.steps can't break utils.units.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→3 application.steps uses domain.shared.enums✕
- Connections
- 8 pairs of types, where a type in application.steps uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.application.steps.ActivityTypesConfig→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.BaseModesConfig→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.DrtModesConfig→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.HasModeChoiceModel→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.HasModes→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.ModesConfig→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.application.steps.PurposesConfig→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.application.steps.SharingModesConfig→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- application.steps uses domain.shared.enums, so a change to domain.shared.enums can break application.steps, while a change to application.steps can't break domain.shared.enums.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→4 application.steps uses domain.shared.enums.areatype✕
- Connections
- 1 pair of types, where a type in application.steps uses a type in domain.shared.enums.areatype.
- The types involved
edu.kit.ifv.application.steps.RegionCodesConfig→edu.kit.ifv.domain.shared.enums.areatype.RegionType
- Direction
- application.steps uses domain.shared.enums.areatype, so a change to domain.shared.enums.areatype can break application.steps, while a change to application.steps can't break domain.shared.enums.areatype.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→5 application.steps uses domain.shared.enums.household✕
- Connections
- 1 pair of types, where a type in application.steps uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.application.steps.HouseholdCodesConfig→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- application.steps uses domain.shared.enums.household, so a change to domain.shared.enums.household can break application.steps, while a change to application.steps can't break domain.shared.enums.household.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→8 application.steps uses domain.shared.car✕
- Connections
- 2 pairs of types, where a type in application.steps uses a type in domain.shared.car.
- The types involved
edu.kit.ifv.application.steps.CarCodesConfig→edu.kit.ifv.domain.shared.car.CarSegmentedu.kit.ifv.application.steps.HasCarRepo→edu.kit.ifv.domain.shared.car.CarId
- Direction
- application.steps uses domain.shared.car, so a change to domain.shared.car can break application.steps, while a change to application.steps can't break domain.shared.car.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→11 application.steps uses domain.shared.location✕
- Connections
- 6 pairs of types, where a type in application.steps uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.application.steps.HasArrayBackedImpedance→edu.kit.ifv.domain.shared.location.ArrayBackedImpedanceedu.kit.ifv.application.steps.HasDestinationChoiceModel→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.application.steps.HasImpedance→edu.kit.ifv.domain.shared.location.Impedanceedu.kit.ifv.application.steps.HasMutableArrayBackedImpedance→edu.kit.ifv.domain.shared.location.ArrayBackedImpedanceedu.kit.ifv.application.steps.HasMutableDestinationChoiceModel→edu.kit.ifv.domain.shared.location.StandardLocationedu.kit.ifv.application.steps.HasMutableImpedance→edu.kit.ifv.domain.shared.location.Impedance
- Direction
- application.steps uses domain.shared.location, so a change to domain.shared.location can break application.steps, while a change to application.steps can't break domain.shared.location.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→13 application.steps uses domain.shared.location.zone✕
- Connections
- 1 pair of types, where a type in application.steps uses a type in domain.shared.location.zone.
- The types involved
edu.kit.ifv.application.steps.HasZoneRepo→edu.kit.ifv.domain.shared.location.zone.ZoneId
- Direction
- application.steps uses domain.shared.location.zone, so a change to domain.shared.location.zone can break application.steps, while a change to application.steps can't break domain.shared.location.zone.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→16 application.steps uses domain.shared.behavior✕
- Connections
- 4 pairs of types, where a type in application.steps uses a type in domain.shared.behavior.
- The types involved
edu.kit.ifv.application.steps.HasAttractivenessModel→edu.kit.ifv.domain.shared.behavior.AttractivenessModeledu.kit.ifv.application.steps.HasChoiceModelModes→edu.kit.ifv.domain.shared.behavior.ChoiceModelModesedu.kit.ifv.application.steps.HasMutableAttractivenessModel→edu.kit.ifv.domain.shared.behavior.AttractivenessModeledu.kit.ifv.application.steps.HasParkingPressureModel→edu.kit.ifv.domain.shared.behavior.ParkingPressureModel
- Direction
- application.steps uses domain.shared.behavior, so a change to domain.shared.behavior can break application.steps, while a change to application.steps can't break domain.shared.behavior.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→17 application.steps uses domain.shared.datastructure.matrix✕
- Connections
- 1 pair of types, where a type in application.steps uses a type in domain.shared.datastructure.matrix.
- The types involved
edu.kit.ifv.application.steps.MatrixConfig→edu.kit.ifv.domain.shared.datastructure.matrix.ZoneMatrixCreation
- Direction
- application.steps uses domain.shared.datastructure.matrix, so a change to domain.shared.datastructure.matrix can break application.steps, while a change to application.steps can't break domain.shared.datastructure.matrix.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→19 application.steps uses domain.simulation.data.sharing✕
- Connections
- 2 pairs of types, where a type in application.steps uses a type in domain.simulation.data.sharing.
- The types involved
edu.kit.ifv.application.steps.HasSharingProviderAgentRepo→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderIdedu.kit.ifv.application.steps.HasSharingProviderRepo→edu.kit.ifv.domain.simulation.data.sharing.SharingProviderId
- Direction
- application.steps uses domain.simulation.data.sharing, so a change to domain.simulation.data.sharing can break application.steps, while a change to application.steps can't break domain.simulation.data.sharing.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→21 application.steps uses domain.shared.datastructure.schedule.replanning✕
- Connections
- 1 pair of types, where a type in application.steps uses a type in domain.shared.datastructure.schedule.replanning.
- The types involved
edu.kit.ifv.application.steps.HasReplanningStrategy→edu.kit.ifv.domain.shared.datastructure.schedule.replanning.ReplanningStrategy
- Direction
- application.steps uses domain.shared.datastructure.schedule.replanning, so a change to domain.shared.datastructure.schedule.replanning can break application.steps, while a change to application.steps can't break domain.shared.datastructure.schedule.replanning.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→33 application.steps uses domain.simulation.behavior.modechoice✕
- Connections
- 2 pairs of types, where a type in application.steps uses a type in domain.simulation.behavior.modechoice.
- The types involved
edu.kit.ifv.application.steps.HasModeChoiceModel→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristicsedu.kit.ifv.application.steps.HasSpawnModeCharacteristics→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics
- Direction
- application.steps uses domain.simulation.behavior.modechoice, so a change to domain.simulation.behavior.modechoice can break application.steps, while a change to application.steps can't break domain.simulation.behavior.modechoice.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→34 application.steps uses domain.simulation.behavior.availability✕
- Connections
- 2 pairs of types, where a type in application.steps uses a type in domain.simulation.behavior.availability.
- The types involved
edu.kit.ifv.application.steps.HasModeAvailabilityModel→edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModeledu.kit.ifv.application.steps.HasMutableModeAvailabilityModel→edu.kit.ifv.domain.simulation.behavior.availability.ModeAvailabilityModel
- Direction
- application.steps uses domain.simulation.behavior.availability, so a change to domain.simulation.behavior.availability can break application.steps, while a change to application.steps can't break domain.simulation.behavior.availability.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→35 application.steps uses domain.simulation.behavior.destinationchoice✕
- Connections
- 3 pairs of types, where a type in application.steps uses a type in domain.simulation.behavior.destinationchoice.
- The types involved
edu.kit.ifv.application.steps.HasDestinationChoiceModel→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristicsedu.kit.ifv.application.steps.HasMutableDestinationChoiceModel→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristicsedu.kit.ifv.application.steps.HasSpawnDestinationCharacteristics→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics
- Direction
- application.steps uses domain.simulation.behavior.destinationchoice, so a change to domain.simulation.behavior.destinationchoice can break application.steps, while a change to application.steps can't break domain.simulation.behavior.destinationchoice.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
39→38 application.steps uses domain.simulation.events✕
- Connections
- 2 pairs of types, where a type in application.steps uses a type in domain.simulation.events.
- The types involved
edu.kit.ifv.application.steps.HasSpawnDestinationCharacteristics→edu.kit.ifv.domain.simulation.events.GenerateDestinationCharacteristicsedu.kit.ifv.application.steps.HasSpawnModeCharacteristics→edu.kit.ifv.domain.simulation.events.GenerateModeCharacteristics
- Direction
- application.steps uses domain.simulation.events, so a change to domain.simulation.events can break application.steps, while a change to application.steps can't break domain.simulation.events.
- Position
- Below the diagonal: application.steps uses a module listed above it, which is the healthy direction.
40→1 domain.jackson uses utils.codes✕
- Connections
- 14 pairs of types, where a type in domain.jackson uses a type in utils.codes.
- The types involved
edu.kit.ifv.domain.jackson.CodePlanDeserializer→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CodePlanSerializer→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CodePlanSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreActivityTypeSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreCarSegmentSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreEconomicStatusSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreEmploymentSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreEngineTypeSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreGraduationSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreModeSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreRegionTypeSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.CoreSexSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.MainModeSurrogate→edu.kit.ifv.utils.codes.Decodableedu.kit.ifv.domain.jackson.SurrogateRegistry→edu.kit.ifv.utils.codes.Decodable
- Direction
- domain.jackson uses utils.codes, so a change to utils.codes can break domain.jackson, while a change to domain.jackson can't break utils.codes.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→2 domain.jackson uses utils.units✕
- Connections
- 2 pairs of types, where a type in domain.jackson uses a type in utils.units.
- The types involved
edu.kit.ifv.domain.jackson.AbsoluteTimeDeserializer→edu.kit.ifv.utils.units.AbsoluteTimeedu.kit.ifv.domain.jackson.AbsoluteTimeSerializer→edu.kit.ifv.utils.units.AbsoluteTime
- Direction
- domain.jackson uses utils.units, so a change to utils.units can break domain.jackson, while a change to domain.jackson can't break utils.units.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→3 domain.jackson uses domain.shared.enums✕
- Connections
- 4 pairs of types, where a type in domain.jackson uses a type in domain.shared.enums.
- The types involved
edu.kit.ifv.domain.jackson.ChoiceModelDeserializersKt→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.jackson.CoreActivityTypeSurrogate→edu.kit.ifv.domain.shared.enums.ActivityTypeedu.kit.ifv.domain.jackson.CoreModeSurrogate→edu.kit.ifv.domain.shared.enums.Modeedu.kit.ifv.domain.jackson.MainModeSurrogate→edu.kit.ifv.domain.shared.enums.Mode
- Direction
- domain.jackson uses domain.shared.enums, so a change to domain.shared.enums can break domain.jackson, while a change to domain.jackson can't break domain.shared.enums.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→4 domain.jackson uses domain.shared.enums.areatype✕
- Connections
- 1 pair of types, where a type in domain.jackson uses a type in domain.shared.enums.areatype.
- The types involved
edu.kit.ifv.domain.jackson.CoreRegionTypeSurrogate→edu.kit.ifv.domain.shared.enums.areatype.RegionType
- Direction
- domain.jackson uses domain.shared.enums.areatype, so a change to domain.shared.enums.areatype can break domain.jackson, while a change to domain.jackson can't break domain.shared.enums.areatype.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→5 domain.jackson uses domain.shared.enums.household✕
- Connections
- 1 pair of types, where a type in domain.jackson uses a type in domain.shared.enums.household.
- The types involved
edu.kit.ifv.domain.jackson.CoreEconomicStatusSurrogate→edu.kit.ifv.domain.shared.enums.household.EconomicStatus
- Direction
- domain.jackson uses domain.shared.enums.household, so a change to domain.shared.enums.household can break domain.jackson, while a change to domain.jackson can't break domain.shared.enums.household.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→6 domain.jackson uses domain.shared.enums.person✕
- Connections
- 3 pairs of types, where a type in domain.jackson uses a type in domain.shared.enums.person.
- The types involved
edu.kit.ifv.domain.jackson.CoreEmploymentSurrogate→edu.kit.ifv.domain.shared.enums.person.Employmentedu.kit.ifv.domain.jackson.CoreGraduationSurrogate→edu.kit.ifv.domain.shared.enums.person.Graduationedu.kit.ifv.domain.jackson.CoreSexSurrogate→edu.kit.ifv.domain.shared.enums.person.Sex
- Direction
- domain.jackson uses domain.shared.enums.person, so a change to domain.shared.enums.person can break domain.jackson, while a change to domain.jackson can't break domain.shared.enums.person.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→8 domain.jackson uses domain.shared.car✕
- Connections
- 1 pair of types, where a type in domain.jackson uses a type in domain.shared.car.
- The types involved
edu.kit.ifv.domain.jackson.CoreCarSegmentSurrogate→edu.kit.ifv.domain.shared.car.CarSegment
- Direction
- domain.jackson uses domain.shared.car, so a change to domain.shared.car can break domain.jackson, while a change to domain.jackson can't break domain.shared.car.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→11 domain.jackson uses domain.shared.location✕
- Connections
- 1 pair of types, where a type in domain.jackson uses a type in domain.shared.location.
- The types involved
edu.kit.ifv.domain.jackson.ChoiceModelDeserializersKt→edu.kit.ifv.domain.shared.location.StandardLocation
- Direction
- domain.jackson uses domain.shared.location, so a change to domain.shared.location can break domain.jackson, while a change to domain.jackson can't break domain.shared.location.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→33 domain.jackson uses domain.simulation.behavior.modechoice✕
- Connections
- 1 pair of types, where a type in domain.jackson uses a type in domain.simulation.behavior.modechoice.
- The types involved
edu.kit.ifv.domain.jackson.ChoiceModelDeserializersKt→edu.kit.ifv.domain.simulation.behavior.modechoice.ModeChoiceCharacteristics
- Direction
- domain.jackson uses domain.simulation.behavior.modechoice, so a change to domain.simulation.behavior.modechoice can break domain.jackson, while a change to domain.jackson can't break domain.simulation.behavior.modechoice.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→35 domain.jackson uses domain.simulation.behavior.destinationchoice✕
- Connections
- 1 pair of types, where a type in domain.jackson uses a type in domain.simulation.behavior.destinationchoice.
- The types involved
edu.kit.ifv.domain.jackson.ChoiceModelDeserializersKt→edu.kit.ifv.domain.simulation.behavior.destinationchoice.DestinationChoiceCharacteristics
- Direction
- domain.jackson uses domain.simulation.behavior.destinationchoice, so a change to domain.simulation.behavior.destinationchoice can break domain.jackson, while a change to domain.jackson can't break domain.simulation.behavior.destinationchoice.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
40→36 domain.jackson uses application.config✕
- Connections
- 2 pairs of types, where a type in domain.jackson uses a type in application.config.
- The types involved
edu.kit.ifv.domain.jackson.ChoiceModelDeserializersKt→edu.kit.ifv.application.config.DestinationChoiceFactoryedu.kit.ifv.domain.jackson.ChoiceModelDeserializersKt→edu.kit.ifv.application.config.ModeChoiceFactory
- Direction
- domain.jackson uses application.config, so a change to application.config can break domain.jackson, while a change to domain.jackson can't break application.config.
- Position
- Below the diagonal: domain.jackson uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Resolve the 14 Low coverage finding(s) in Code Coverage — start with CustomRuleSetProvider.kt, LayeredArchitecture.kt, ProcessorDispatcher.kt; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 14 Low coverage finding(s) in Code Coverage — start with CustomRuleSetProvider.kt, LayeredArchitecture.kt, ProcessorDispatcher.kt. | +7.7 pts | Medium | Code Coverage |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +7.6 pts | Medium | Keyboard semantics |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +4.8 pts | Medium | Page structure |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +4.2 pts | Medium | Visual & motion safety |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.9 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +1.9 pts | Low | ADR Quality |
| Resolve the 1 `compareWithMid` spells `Mid` where 12 names in the project spell it… finding(s) in Naming Consistency — start with MidComparisonData.kt. | +1.9 pts | Low | Naming Consistency |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.5 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/main/kotlin/edu/kit/ifv/application/steps/results/AddDefaultMIDComparisonPlots.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuilderProcessor.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/simulation/agent/BuildAgents.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/test/kotlin/edu/kit/ifv/Main.kt | 6.5 | Mixed | Explicit Debt: TodoComment |
| src/test/kotlin/edu/kit/ifv/integration/ExamplePopulationSynthesis.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/utils/ErrorHandling.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/synthesis/results/legacy/LegacyActivityOutput.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/synthesis/results/legacy/LegacyCarOutput.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/simulation/events/PersonState.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/application/steps/parser/csv/LoadPlannedActivities.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/simulation/agent/DrtProviderAgent.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/core/statemachine/usage/StateMachineUsageRecorder.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/plans/BlockModel.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| codegen/processor/src/main/kotlin/edu/kit/ifv/processor/mutable/MutableProcessor.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Parameter.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/synthesis/behavior/RawSurveyInfo.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/domain/simulation/events/DrtProviderState.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/application/steps/ContextRequirements.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/edu/kit/ifv/application/steps/parser/csv/LoadPersons.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/test/kotlin/edu/kit/ifv/integration/TestContext.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 55 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 228 of 280 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (codegen/processor/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuildFunction.kt`, `codegen/processor/src/main/kotlin/edu/kit/ifv/util/AnnotationUtil.kt`, `codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Ids.kt`, `codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Parameter.kt`, `src/main/kotlin/edu/kit/ifv/application/config/ShortTermConfig.kt`, … (+121 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 7 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DayOfWeekExtensionsKt.decodeDayOfWeek at 29 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/main/kotlin/edu/kit/ifv/utils/units/DayOfWeekExtensions.kt (DayOfWeekExtensionsKt.decodeDayOfWeek at 29), src/main/kotlin/edu/kit/ifv/core/results/plots/ColorPallets.kt (ColorPalletsKt.modeStringColor at 23), src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/matrix/yaml/DayIdentifier.kt (DayIdentifier.getDays at 19), src/main/kotlin/edu/kit/ifv/domain/shared/enums/areatype/LegacyRegionType.kt (Bbsr17.toRegioStaR17 at 19), src/main/kotlin/edu/kit/ifv/domain/shared/enums/areatype/RegioStaR.kt (RegioStaR17.toRegioStaR4 at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was AddDefaultMIDComparisonPlotsKt.addDefaultMIDComparisonPlots at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with AddDefaultMIDComparisonPlotsKt.addDefaultMIDComparisonPlots (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/10.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with AddDefaultMIDComparisonPlots.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 2.0 % of the production lines (687 of 34,833) are in a reported copy. A further 18 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with CarEngineStatistics.kt, MidComparisonPlotBuilder.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with BlockModel.kt, ActionModel.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with ActivityBlock.kt, Location.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
4 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 92 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 1.9% — 14 file(s) below 50%. Measured from the Java/Kotlin suite (repository root, Gradle: the JaCoCo agent on the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 14 Low coverage finding(s) in Code Coverage — start with CustomRuleSetProvider.kt, LayeredArchitecture.kt, ProcessorDispatcher.kt. — One of this dimension's main actionable groups (14 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 59 artifact(s) resolved, 47 of them gradable against Maven Central, and 42 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 31 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 5 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/DefaultAvailabilityModel.kt (5 of 7 changes were fixes); src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/RuleBuilder.kt (4 of 4 changes were fixes); src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/RuleScope.kt (4 of 4 changes were fixes)
What to do
- Resolve the 8 Repeated repair finding(s) in Churn × Complexity Hotspots — start with DefaultAvailabilityModel.kt, RuleBuilder.kt, RuleScope.kt. — One of this dimension's main actionable groups (8 warning-level).
D16 · Bus Factor
13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/kotlin/edu/kit/ifv/core/statemachine/builder/states/ReactiveStateBuilder.kt. Counted over 197 of the 568 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
151 deducted task-comment markers across 34833 LoC (0.4/KLoC) → score 9.2. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 150 TodoComment finding(s) in Explicit Debt — start with Main.kt (5), ExamplePopulationSynthesis.kt (4), ErrorHandling.kt (4). — One of this dimension's main actionable groups (150 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with Main.kt. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 8 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 13 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `compareWithMid` spells `Mid` where 12 names in the project spell it… finding(s) in Naming Consistency — start with MidComparisonData.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
41 % of calls cross a namespace and 19 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 180) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 197 of the 568 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: BinaryActivityReader.kt↔BinaryHouseholdReader.kt 85%; BinaryActivityReader.kt↔BinaryCarReader.kt 77%; BinaryActivityReader.kt↔FixedDestinationReader.kt 69%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with BinaryCarReader.kt, BikeSharingConfig.kt, Yaml.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with BinaryActivityReader.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 33 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:163
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:163
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:204
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- The repo's own CSS styles .logs-card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:203
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — src/main/kotlin/edu/kit/ifv/utils/report/ReportCards.kt:28, src/main/kotlin/edu/kit/ifv/utils/report/ReportCards.kt:30, src/main/kotlin/edu/kit/ifv/utils/report/ReportCards.kt:132
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.card-body` moves (`transition: max-height 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/main/resources/edu/kit/ifv/utils/report/report.css:128
- `.rotatable` moves (`transition: rotate 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/main/resources/edu/kit/ifv/utils/report/report.css:166
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build.gradle.kts:51
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X15 · Unvalidated length from an untrusted reader
- `size` is read from the bytes being parsed at line 17 (`readInt`), then used to size a `Array` at line 18 — and nowhere in its scope is `size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `size` against the bytes actually remaining and a maximum the format allows before allocating. — src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/matrix/binary/BinaryStandardDeserializer.kt:18
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/main/kotlin/edu/kit/ifv/core/modelsteps/validation/ValidateCsvMetadata.kt:145
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — codegen/processor/src/main/kotlin/edu/kit/ifv/processor/state/StateProcessor.kt:250, codegen/processor/src/main/kotlin/edu/kit/ifv/processor/state/StateProcessor.kt:301
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80.3 | Strong | Solid. |
| Architecture | 94.1 | Exemplary | Solid. |
| Maturity | 72.2 | Strong | Solid. |
| Readiness | 48.3 | Weak — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83.3 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100.0 | Exemplary | Strongest area. |
| Accessibility | 40.7 | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~10630 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 126 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 8 current-state document(s) make no claim of a kind M4 checks. 11 claim(s) of kinds M4 does not check were not checked (environment variable 11); M4 checks only links and versions and artefact counts.
- P2 Observability — This repository's JVM, JavaScript/TypeScript source (5 module(s), 564 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 15 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 5 finding(s)
- Click handler on a non-interactive <div> src/main/kotlin/edu/kit/ifv/utils/report/ReportCards.kt:30
- Click handler on a non-interactive <div> src/main/kotlin/edu/kit/ifv/utils/report/ReportCards.kt:132
- <html> without a lang src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:163
- Clickable element isn't keyboard-operable src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:203
- Click handler on a non-interactive <span> src/main/kotlin/edu/kit/ifv/utils/report/ReportCards.kt:28
Serious — 218 finding(s)
- TodoComment src/test/kotlin/edu/kit/ifv/Main.kt:155
- TodoComment src/test/kotlin/edu/kit/ifv/Main.kt:169
- TodoComment src/test/kotlin/edu/kit/ifv/integration/TestContext.kt:86
- TodoComment src/test/kotlin/edu/kit/ifv/Main.kt:211
- TodoComment src/test/kotlin/edu/kit/ifv/integration/TestContext.kt:124
- TodoComment src/test/kotlin/edu/kit/ifv/Main.kt:356
- TodoComment src/test/kotlin/edu/kit/ifv/Main.kt:389
- TodoComment src/test/kotlin/edu/kit/ifv/TestEnvironment.kt:157
- TodoComment src/test/kotlin/edu/kit/ifv/TestEnvironment.kt:321
- TodoComment src/test/kotlin/edu/kit/ifv/utils/collections/EquivalenceClassTest.kt:54
- TodoComment src/test/kotlin/edu/kit/ifv/integration/ExamplePopulationSynthesis.kt:58
- TodoComment src/test/kotlin/edu/kit/ifv/integration/ExamplePopulationSynthesis.kt:174
- TodoComment src/test/kotlin/edu/kit/ifv/integration/ExamplePopulationSynthesis.kt:178
- TodoComment src/test/kotlin/edu/kit/ifv/integration/ExamplePopulationSynthesis.kt:179
- TodoComment src/test/kotlin/edu/kit/ifv/domain/synthesis/ZoneDistributedLocationsTest.kt:84
- TodoComment src/test/kotlin/edu/kit/ifv/domain/simulation/BinaryConversionTest.kt:224
- TodoComment src/test/kotlin/edu/kit/ifv/core/statemachine/BusTestAgent.kt:31
- TodoComment src/test/kotlin/edu/kit/ifv/core/statemachine/PassengerTestAgent.kt:25
- TodoComment src/test/kotlin/edu/kit/ifv/core/statemachine/StationTestAgent.kt:21
- TodoComment src/test/kotlin/edu/kit/ifv/core/statemachine/PassengerTestAgent.kt:90
- TodoComment src/test/kotlin/edu/kit/ifv/application/steps/parser/PersonBinaryCsvConversionTest.kt:124
- TodoComment src/test/kotlin/edu/kit/ifv/application/scenarios/RidepoolingScenario.kt:68
- TodoComment src/test/kotlin/edu/kit/ifv/application/scenarios/RidesharingOnlyScenario.kt:60
- TodoComment src/test/kotlin/edu/kit/ifv/application/scenarios/RidepoolingScenario.kt:127
- TodoComment src/test/kotlin/edu/kit/ifv/application/scenarios/RidesharingOnlyScenario.kt:107
- Low coverage: codegen/custom-detekt/src/main/kotlin/edu/kit/ifv/CustomRuleSetProvider.kt codegen/custom-detekt/src/main/kotlin/edu/kit/ifv/CustomRuleSetProvider.kt:1
- Low coverage: codegen/custom-detekt/src/main/kotlin/edu/kit/ifv/LayeredArchitecture.kt codegen/custom-detekt/src/main/kotlin/edu/kit/ifv/LayeredArchitecture.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/ProcessorDispatcher.kt codegen/processor/src/main/kotlin/edu/kit/ifv/ProcessorDispatcher.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/ProcessorProvider.kt codegen/processor/src/main/kotlin/edu/kit/ifv/ProcessorProvider.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuildFunction.kt codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuildFunction.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuilderProcessor.kt codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuilderProcessor.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/processor/mutable/MutableProcessor.kt codegen/processor/src/main/kotlin/edu/kit/ifv/processor/mutable/MutableProcessor.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/processor/state/StateProcessor.kt codegen/processor/src/main/kotlin/edu/kit/ifv/processor/state/StateProcessor.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/util/AnnotationUtil.kt codegen/processor/src/main/kotlin/edu/kit/ifv/util/AnnotationUtil.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/util/CodeGenerationUtil.kt codegen/processor/src/main/kotlin/edu/kit/ifv/util/CodeGenerationUtil.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/utils/GroupingUtil.kt codegen/processor/src/main/kotlin/edu/kit/ifv/utils/GroupingUtil.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Ids.kt codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Ids.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Parameter.kt codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Parameter.kt:1
- Low coverage: codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Patterns.kt codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Patterns.kt:1
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/DefaultAvailabilityModel.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/DefaultAvailabilityModel.kt:56
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/RuleBuilder.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/RuleBuilder.kt:138
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/RuleScope.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/RuleScope.kt:113
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/ModeResource.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/ModeResource.kt:39
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/ProviderAvailability.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/ProviderAvailability.kt:26
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/DefaultRules.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/DefaultRules.kt:16
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/ModeAvailabilityByRule.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/ModeAvailabilityByRule.kt:22
- Repeated repair: src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/AvailabilityModelBuilder.kt src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/rules/builder/AvailabilityModelBuilder.kt:27
- Change coupling: BinaryCarReader.kt ↔ BinaryHouseholdReader.kt src/main/kotlin/edu/kit/ifv/domain/simulation/parser/binary/BinaryCarReader.kt:1
- Change coupling: BikeSharingConfig.kt ↔ MatrixConfig.kt src/main/kotlin/edu/kit/ifv/application/config/subconfigs/BikeSharingConfig.kt:1
- Change coupling: Yaml.kt ↔ ZoneMatrixCreationDeserializer.kt src/main/kotlin/edu/kit/ifv/application/config/Yaml.kt:1
- Change coupling: BuildAgents.kt ↔ PersonState.kt src/main/kotlin/edu/kit/ifv/domain/simulation/agent/BuildAgents.kt:1
- Animation without a prefers-reduced-motion guard src/main/resources/edu/kit/ifv/utils/report/report.css:128
- Animation without a prefers-reduced-motion guard src/main/resources/edu/kit/ifv/utils/report/report.css:166
- Edited copy of a member (15 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/car/engine/CarEngineStatistics.kt:64
- Edited copy of a member (15 corresponding lines) src/main/kotlin/edu/kit/ifv/application/steps/results/MidComparisonPlotBuilder.kt:121
- Edited copy of a member (9 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/plans/BlockModel.kt:157
- Edited copy of a member (9 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/plans/ActionModel.kt:42
- Edited copy of a member (4 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/blocks/ActivityBlock.kt:144
- Edited copy of a member (4 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/location/Location.kt:18
- Edited copy of a member (7 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/synthesis/behavior/cars/ownership/LicenceHoldersBySeniority.kt:13
- Edited copy of a member (7 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/synthesis/behavior/cars/generation/InfoBasedCarGeneration.kt:11
- Duplicated block (8 lines × 2) codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuilderProcessor.kt:151
- Duplicated block (8 lines × 2) src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/action/Activity.kt:40
- Swallowed exception (caught, then discarded) codegen/processor/src/main/kotlin/edu/kit/ifv/processor/state/StateProcessor.kt:250
- Swallowed exception (caught, then discarded) codegen/processor/src/main/kotlin/edu/kit/ifv/processor/state/StateProcessor.kt:301
- Page without a main landmark src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:163
- Heading level jumps from h1 to h3 src/main/kotlin/edu/kit/ifv/utils/report/ReportBuilder.kt:204
- HackComment src/test/kotlin/edu/kit/ifv/Main.kt:305
- AddDefaultMIDComparisonPlotsKt.addDefaultMIDComparisonPlots (cognitive 17) src/main/kotlin/edu/kit/ifv/application/steps/results/AddDefaultMIDComparisonPlots.kt:29
- MethodTooLong: AddDefaultMIDComparisonPlotsKt.addDefaultMIDComparisonPlots src/main/kotlin/edu/kit/ifv/application/steps/results/AddDefaultMIDComparisonPlots.kt:29
- Change-coupling hub: BinaryActivityReader.kt → BinaryCarReader.kt, BinaryHouseholdReader.kt, FixedDestinationReader.kt src/main/kotlin/edu/kit/ifv/domain/simulation/parser/binary/BinaryActivityReader.kt
- Edited copy of a member (19 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/synthesis/SurveyCSVParser.kt:46
- Edited copy of a member (42 corresponding lines) src/main/kotlin/edu/kit/ifv/core/results/plots/render/BoxPlotRenderer.kt:74
- Edited copies of one member (4 members, 18+ corresponding lines) src/main/kotlin/edu/kit/ifv/application/steps/results/MidComparisonPlotBuilder.kt:99
- Edited copy of a member (18 corresponding lines) src/main/kotlin/edu/kit/ifv/core/statemachine/StateMachine.kt:180
- Edited copy of a member (20 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/blocks/ActivityBlock.kt:154
- Edited copy of a member (17 corresponding lines) src/main/kotlin/edu/kit/ifv/core/statemachine/usage/StateMachineUsageRecorder.kt:57
- Edited copy of a member (16 corresponding lines) src/main/kotlin/edu/kit/ifv/core/modelsteps/validation/Warning.kt:118
- Edited copy of a member (13 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/synthesis/results/fastcsv/WriteCsvWithAttributeProjection.kt:64
- Edited copy of a member (11 corresponding lines) src/main/kotlin/edu/kit/ifv/core/modelsteps/validation/Warning.kt:92
- Edited copy of a member (5 corresponding lines) src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/schedule/blocks/ActivityBlock.kt:129
- Duplicated block (15–16 lines × 2) src/main/kotlin/edu/kit/ifv/core/modelsteps/validation/Warning.kt:121
- Duplicated block (15 lines × 3) src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/DefaultAvailabilityModel.kt:92
- Duplicated block (14 lines × 2) src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/DefaultAvailabilityModel.kt:108
- Duplicated block (6 lines × 2) src/main/kotlin/edu/kit/ifv/domain/synthesis/SurveyCSVParser.kt:46
- Duplicated block (5 lines × 6) src/main/kotlin/edu/kit/ifv/application/steps/parser/csv/LoadCustomPersons.kt:98
- Duplicated block (9 lines × 3) src/main/kotlin/edu/kit/ifv/application/steps/parser/csv/LoadHouseholds.kt:91
- Duplicated block (10 lines × 3) src/main/kotlin/edu/kit/ifv/core/results/plots/AsNumericLinePlot.kt:17
- Duplicated block (13 lines × 2) src/main/kotlin/edu/kit/ifv/application/steps/results/AddDefaultMIDComparisonPlots.kt:409
- Duplicated block (10 lines × 2) src/main/kotlin/edu/kit/ifv/domain/synthesis/SurveyCSVParser.kt:55
- Coverage collected but not gated
- Length read from the parsed input is spent without ever being bounded src/main/kotlin/edu/kit/ifv/domain/shared/datastructure/matrix/binary/BinaryStandardDeserializer.kt:18
- Swallowed exception (empty catch) src/main/kotlin/edu/kit/ifv/core/modelsteps/validation/ValidateCsvMetadata.kt:145
Minor — 15 finding(s)
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Documentation: no build, run or usage example README.md:1
- No ADRs found build.gradle.kts:7
- `compareWithMid` spells `Mid` where 12 names in the project spell it `MID` src/main/kotlin/edu/kit/ifv/application/steps/results/MidComparisonData.kt:35
- Projects may be oversized for their cohesion build.gradle.kts:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST
- No dependency-update automation build.gradle.kts:51
- No changelog
- Duplicated predicate src/main/kotlin/edu/kit/ifv/domain/simulation/behavior/availability/DefaultAvailabilityModel.kt:80
Minor — 42 finding(s)
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.bouncycastle:bcpkix-jdk18on
- Outdated (compile): org.bouncycastle:bcutil-jdk18on
- Outdated (compile): org.bouncycastle:bcprov-jdk18on
- Outdated (compile): org.bouncycastle:bcpg-jdk18on
- Outdated (compile): org.jetbrains.kotlin:kotlin-build-tools-compat
- Outdated (compile): org.jetbrains.kotlin:kotlin-tooling-core
- Outdated (compile): org.jetbrains.kotlin:kotlin-build-tools-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-compiler-embeddable
- Outdated (compile): org.jetbrains.kotlin:kotlin-script-runtime
- Outdated (compile): org.jetbrains.kotlin:kotlin-reflect
- Outdated (compile): org.jetbrains.kotlin:kotlin-daemon-embeddable
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlin:kotlin-compiler-runner
- Outdated (compile): org.jetbrains.kotlin:kotlin-daemon-client
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-compiler-embeddable
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-common
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-jvm
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-compiler-impl-embeddable
- Outdated (compile): org.jetbrains.kotlin:abi-tools
- Outdated (compile): org.jetbrains.kotlin:abi-tools-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-metadata-jvm
- Outdated (compile): org.jetbrains.kotlin:kotlin-klib-abi-reader
- Outdated (compile): io.github.java-diff-utils:java-diff-utils
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-c2994a7b32cc4a318d9eddeec1da5d57/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-c2994a7b32cc4a318d9eddeec1da5d57/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1278" --report-format json --report-path /tmp/watchdog-gitleaks-c2994a7b32cc4a318d9eddeec1da5d57/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c2994a7b32cc4a318d9eddeec1da5d57/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 126 file(s) — `codegen/processor/src/main/kotlin/edu/kit/ifv/processor/builder/BuildFunction.kt`, `codegen/processor/src/main/kotlin/edu/kit/ifv/util/AnnotationUtil.kt`, `codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Ids.kt`, `codegen/processor/src/main/kotlin/edu/kit/ifv/utils/Parameter.kt`, `src/main/kotlin/edu/kit/ifv/application/config/ShortTermConfig.kt`, … (+121 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |