In my tenure as a solution architect in financial services working for a global consulting firm, I have often questioned the best way to practice enterprise architecture. A common challenge that many architecture consultants face is that most client firms insist on using their proprietary enterprise architecture content. I have observed that frequently such architecture content does not always distinguish between the solution and software architecture.
This article is not an academic paper. In this article, I present my experiences and ideas to help my colleagues better understand the vague differences between two similar but distinct architecture disciplines. At the very least, this article may trigger a conversation via the comments section that may persuade me that I am wrong.