Seminar on Design and Architecture Patterns

Ošlejšek

Lesson details

Generic feedback to the Observation and Measurements pattern:

  • Successful usage requires correct mapping of the pattern's classes to terms of the application domain.
  • Metric class=. Metric is "the number of lines of code", for instance, while Measurement is a concrete measured number.
  • On the contrary, PhenomenonType plays the role of metric or issue.
Generic feedback to the Enterprise Segment pattern:

  • The deflection association of the DimensionElement is important and cannot be missing in the model because it demotes the classification tree. 
  • The requirement was: "Which types/categories of quality metrics are applied to different SW products and/or in different geographical locations, and also how often"? Can we consider (and then model) the time/frequency a dimension element? Definitely yes (years - months - weeks - days - ...).
  • Classifications are usually trees (only sometimes lists). Reflect it in the documentation of dimension elements.
  • A dimension element related to the quality has to be somehow associated with the Observation&measurement part of the model because we aim to classify metrics.

Generic feedback to the Planning pattern:

  • The association between the ImplementedAction and ProposedAction is important and cannot be missing in the model because it links data from consequent phases.
  • Name the Action and its sub-classes properly, reflecting the terms of the application domain.
  • The PlannedAction (properly renamed :-) is there to store info about what aspects of the SW project will be tested. Therefore, has to be associated with the related class(es) of the Observation&measurement part of the model.
  • Similarly, the ImplemenedAction (or its CompletedAction sub-class) has to be associated with (other) parts of already existing Observation&measurement decomposition.

Other notes:

  • How terms like analysis, report, or quality configuration relate to the planning and observations&measurements. Do you have all these terms captured by the problem domain model (not necessarily as explicit classes)?
  • Has anyone asked the question whether the analyses are independent? Or do we need to plan their execution order? Where and how to store such ordering?

Required output

  • Until Thu. 20.10., noon, each team fixes and re-submits the problem domain model (analytical class diagram) into the 05 - Analysis patterns modelling homework vault (odevzdávárna).