Name for "generic MADRs"
koppor opened this issue · comments
In the paper Architectural Decision Guidance across Projects by Olaf Zimmermann, Lukas Wegmann, Heiko Koziolek and Thomas Goldschmidt, it is distinguished between "problem space" and "solution space"
Currently, we offer "MADR" as concept for the "solution space", where concrete solutions are written down. In addition, it can be abstracted from the solution space to the "problem space" to offer a collection of solutions, where one can pick from.
For instance: Concidered Options: "Maven, Gradle, Ant". They all have their "global" pros and cons. When going "locally", i.e., to a concrete project, new pros/cons are added and one option is chosen. Moreover, a context is added. -- That means, the format of the "global MADRs" differs from the format of the "local MADRs".
Question: How should the "global MADRs" be called?
Current thoughts:
| Problem Space | Solution Space |
|---|---|
| PMADR (for problem MADR) | SMADR (for solution MADR) |
| AMADR (for abstract MADR) | IMADR (for instanitated MADR) |
| CMADR (for challenge MADR) | SMADR (for solution MADR) |
| GMADR (for global MADR) | MADR |
| GMADR (for generic MADR) | MADR |
| GMADR (for generic MADR) | SMADR (for specialized MADR) |