Closed gernotstarke closed 3 weeks ago
@sko Find out, how we can reduce the size of this LG or at least re-order patterns into a sensible sequence, maybe off-load content to the glossary
@skogsbaer - are you active on this? Any chance to complete until end-of-July?
@gernotstarke I'm midway through the exams. Currently not working on this issue. My plan was to finish to english version in the next week. So end of July should be fine.
Working on this.
So here is my suggestion:
With respect to the R1, R3 categorization, nothing changes.
Optionally, we could move the explanations of the patterns to the glossary, linking from the learning goals to the glossary. This would have two benefits:
The downside is that it's a lot of work to update the glossary because most patterns in the learning goals do not have an entry in the glossary.
Here is how the two learning goals would look like. I have omitted the descriptions of the patterns, assuming they are in the glossary. At the end, you see what needs to be added to the glossary.
@mikesperber I have moved interpreter and combinator to the design patterns. Is this ok? @gernotstarke @alxlo What do you think about the structure? Any opinion on the glossary?
Software architects can explain and provide examples for the following architectural patterns (R1):
Software architects can explain several of the following architectural patterns, explain their relevance for concrete systems, and provide examples. (R3)
Software architects know essential sources for architectural patterns, such as POSA (e.g. <
Software architects know the difference between architectural and design patterns. They can explain several of the following design patterns, explain their relevance for concrete systems, and provide examples. (R3)
Software architects know essential sources for design patterns, such as POSA (e.g. <
Software architects can explain several of the following architectural patterns, explain their relevance for concrete systems, and provide examples. (R3)
I like your suggestion, AND your proposals for improving the glossary. The work needs to be done anyway...
Therefore, go for it, create the LG's, open a PR and I'm happy to accept it :-)
thanx for your valuable contribution and time!
There is a seven year old issue in the glossary tracker: https://github.com/isaqb-org/glossary/issues/82
Here is a PR for the glossary: https://github.com/isaqb-org/glossary/pull/199
Now that the PR for the glossary was accepted, there is a PR for the curriculum: https://github.com/isaqb-org/curriculum-foundation/pull/478
@gernotstarke we can close this, right?
yes, it's completed and done.
the current LG is too large and contains different kind of patterns.
Split into two distinct (e.g. one for system-wide patterns like layers and microservices) and others related to solving specific and smaller problems.
Move dependency-inversion/detection