search

nmsa / tma-framework-a

Component A - Trustworthiness Monitoring & Assessment Framework
Apache License 2.0
1 stars 3 forks source link

Update qualityModel diagram - adding historical data #44

Closed renatostore closed 6 years ago

brenofranca83 commented 6 years ago

@renatostore , should this 1-1 relationship be 1-N? Moreover, shouldn't it be associated with Metric (no 's') instead of Attribute? @montex

renatostore commented 6 years ago

@brenofranca83 I changed the relationship to 1..n but I believe that the consolidated data are in the attribute

montex commented 6 years ago

Hello, @brenofranca83, the concept of historical data was added following the comments in the last meeting about the drill down of plots in the dashboard. So I think it is correct to have it associated with the Attribute.

However, yes, @renatostore, the multiplicity should be 1..n, with n on the side of the HistoricalData. Multiplicity between LeafAttribute and Metric should also be changed to 1..n, with 1 on the side of Metric.

montex commented 6 years ago

@renatostore better names should be found for Operator and OperatorKind. The two are enumerations of operator, one is used for aggregation of multiple values of the same Metric to form the value of an attribute, the other for the aggregation of multiple Attributes in the tree to form the value of an higher-level Attribute.

So they can be changed to something like DataAggregationOperator and AttributeAggregationOperator