David Shilman

Thank you for reading it and your feedback

Hi Fernando. I am not a big fan of tech, EA, PMP books, mostly because most books are verbose, very comprehensive and written by people without much practical and hands-on experience. What is your area of interest? I am not a big fan of EA, I ind that most EA practitioners are former technologists who are no longer relevant. I believe EA should be a secondary discipline (never primary) in conjunction with tech expertise. Feel free to reach out via LinkedIn if you have any more questions.

wow, thank you

Thank you Arvin

Hi Denis, thank you for your comment. In my opinion, TOGAF ADM application + data + technology architecture domains somewhat resemble software architecture. However, the focus of ADM is the process of developing target/solution architecture. TOGAF application architecture content framework is very light and lacks software analysis methods. Software architecture discipline goes much deeper in ensuring high-quality software engineering based on architecture principles styles, design patterns, and UML modeling content.

you are correct. Serverless or AWS Lambda functions are another examples of distributed application architecture and therefore need to be reflected in today's software styles, principles, and design patterns. Thank you for your comment.

Hi Carlos, You're 100% correct, architecture and system design are not the same things. looking forward to your article. Thank you for commenting. - D

Mike, a good software architecture doc will have a good structure (flow), decisions, assumptions, architecture views and description for each section. As far as the template, each company usually has its own software or solution architecture document template. It is politically and practically wise to use a template that the architecture governance stakeholders are already familiar and comfortable with. Hope it helps. - D

Good point Phil. DevOps is essentially the new term for engineered (automated) operaions. To make software architecture more relevant to today's architecture consumers a.k.a. developers, we must speak their language.

Good point Phil. DevOps is essentially the new term for engineered (automated) operaions. To make software architecture more relevant to today's architecture consumers a.k.a. developers, we must speak their language.

Hi Christian, thank you for your compliment. Business domain knowledge is very helpful.

A good solution architect will utilize his/her analytical skills in order to create a solution that meets the business needs/goals and while is most optimal from the operational & technology perspectives. So the matrix org structure can work.

However, having an effective personal & professional relationship with the business & technology stakeholders along with domain and technology expertise, in my opinion, makes the winning formula for successful solution architecture.

So, my short answer to your question is, the matrix model can work very well, the business/functional domain model is better.

Thanks -D

good observation Mike. In the app dev context, a solution architect will also be a software architect. Although, solution architecture is a much wider in scope and less defined architecture framework. The article suggests that software architecture is a mature and precise architecture discipline and should not be confused with or rolled up in solution architecture. Thank you for your comment - D.

good observation Mike. In the app dev context, a solution architect will also be a software architect. Although, solution architecture is a much wider in scope and less defined architecture framework. The article suggests that software architecture is a mature and precise architecture discipline and should not be confused with or rolled up in solution architecture. Thank you for your comment - D.

Solution or software engineering in most firms is influenced by their culture. Most firms' culture is based on consistency and maturity of project management. Some more progressive firms are beginning to value architecture as a driving force for planning and execution. The few very elite firms value software engineering excellence over all others.

You are very kind. Please read another one that just got published "Case for Software Architecture Makeover". Please like or share. Feel free to connect with me on LinkedIn.

- David

Thank you for your comment. Stay tuned for my next article :)

Thank you Pablo. Agree, an ideal architect can do it all: solution architecture, enterprise, and software. In reality, a good banking or insurance solution architect may be a lousy software architect. A good software architect may be an expert on API and microservices, but may not know how to solution nor see a larger enterprise technology picture.

Stay tuned for my next article.