I think a utility tree is a visualization of quality attribute exposures for a given architecture, however it can get pretty cumbersome and the details will loose the big picture. In practice, it really depends on the people reading this and how well familiar they are. Chances are they will not be and the goal will be then for the architect to familiarize the stakeholders or create an alternate artifact.
Hi! I'm Rohit Sood, a LLL :-) Life Long Learner. I've been a tech co-founder CTO, Chief IT Architect, Technologist, and Software Engineer and I cut through the noise and deliver actionable results. My blogs are a collection of insights and opinions - my own battle-tested insights as well as untested hypothesis: Cloud, AI, cybersecurity, system design, people, process, leadership and introspection . All opinions are my own.
Subscribe to:
Post Comments (Atom)
As a System Thinketh: Architecting the IT Landscape of the Organization
As a System Thinketh: Architecting the IT Landscape of the Organization I recently read the 1903 classic As ...
-
I think a utility tree is a visualization of quality attribute exposures for a given architecture, however it can get pretty cumbersome and...
-
NO SQL is basically a highly scalable disruptive data storage technology. The basic downsides included proprietary APIs (no standard SQL), e...
No comments:
Post a Comment