Yes, that model is also very common. It’s like all of the teams pay their “taxes” and that money is used to fund internal products leading to the organisational dynamics you talk about.
Thanks for your thoughts. Lot’s of interesting patterns here that I am very keen to write about and explore deeper.
I don’t disagree with anything you say, and largely it’s down to semantics. Let me share with you some of my thoughts on your response:
“However: Products are bought by customers. Customers are the people with money. They are willing to spend money for certain quality.
External products are bought…
It’s impossible to say really. Higher-level documents typically change less so it’s easier to keep them upto date and there are fewer of them.
But more detailed diagrams can become out of date very quickly so it can be futile to try and document everything.
An onion architecture could be used to implement these systems. These diagrams are intended to be higher level than the implementation details.
Thank you for mentioning this Gabor Laszlo Hajba. I have now added the links back. I fear they may have been lost in translation when the blog was imported into medium.
They are all brilliant books that I would highly recommend reading.
Hi Gabor Laszlo Hajba,
Thank you for noticing this. I recently imported my blog from blogger and it appears there were translation issues. I’ve fixed it now.
By the way, this is an old post but I still believe 100% that the cascade rule leads to the cleanest, easiest to read code and I follow this rule always.