In the early hours of this morning I was thinking about projecting an image in regards to solutions and depicting how many different layers there are in a solution stack, including some dependencies on the overall solution architecture as well as the deployment and support capability required for ongoing operations. I put together the view below, a simplified high-level view of what a solution stack means for a solution, project, or just how an organisation or team may think overall about enterprise solution components.

This diagram is only based on my thoughts, not specifically related to a framework or a specific solution, hence it’s not specifically a formal approach or a solution. It’s a conceptual image of what I was thinking about in the early hours of this morning.

Reflecting on the TOGAF ADM 10th edition, I have been considering how to create an alternative view of the ADM phases. The framework is well-defined and proven, which raises the question: why change something that works effectively?

The phases of the TOGAF ADM provide a structured approach to enterprise architecture, guiding organisations through the process designing, planning, implementing, and governing effective enterprise architectures… in a nutshell.

While exploring new perspectives can be valuable, it is essential to recognise the strengths of the existing methodology. The TOGAF ADM continues to serve as a reliable foundation for architects and organizations alike. Therefore, I chose to represent a key aspect of the impact of the ADM phases, which is requirements management and how this is integral to each phase. I created the view below, perhaps more of a perspective than anything else, something useful for depicting my initial goal.

Why did I need to do this? Everyone views the same depiction, but everyone’s view and interpretation of the image, including their thoughts, can effectively be different.