-
Fundamentals of Solution Architecture Modeling
In this post, I provide a brief introduction to solution architecture elements, the key elements that matter for most solutions. We see various solution architectures using different elements. Each cloud architecture, for example, can have hundreds of representative elements from each vendor. For complex solutions, however, we need to focus on architectural elements at the…
-
Fundamentals of Enterprise Solution Architecture Elements
We see many architectural diagrams or views. Not many catch the architectural essence in a holistic fashion. Some are cloud platform-specific reference architectures, some are software or infrastructure architectures, some are enterprise architecture planning views, and many are casual diagrams without clear architectural properties. This post describes a set of enterprise solution architecture (ESA) elements…
-
What Makes ArchView (AI Skill) Different?
There are plenty of tools for architectural diagrams. But structural modeling tools built specifically for architects are few, and most target either enterprise architecture or solution design. Tools for modeling views specifically at the enterprise solution architecture (ESA) level are rarer still. This post tells what sets the ESA-level ArchView Skill apart.
-
ArchView: An AI Skill for Quick Solution Architecture
Solution architecture can get complex fast, especially for large-scale solutions, which makes architecting time-consuming, even before you get to the diagram. ArchView is built to change that: it renders architectural views quickly, so you can spend your time on the thinking, not the drawing, together with the stakeholders who each need to see the solution…
-
Enterprise Architecture vs. Solution Architecture: A Unique Gist View
Enterprise architecture (EA) focuses more on IT strategies, values, directions, and associated capabilities. In contrast, solution architecture (SA) focuses more on an individual solution, with more considerations of technologies and platforms. Enterprise solution architecture (ESA) represents the essence of both EA and SA.
-
Basic Concept: Capability vs. IT Service
This article contains some frequently asked questions about the basic concept of capability, IT service and their relationship from a common sense perspective.
-
Value Streams, Capabilities, and IT Services: A Simple Model View
When the key mappings between capabilities and IT services are clear, identifying service domains and specifying functional granularity and integration patterns, the tough part of architectural design, becomes easier.
-
Enterprise Solution Architecture vs. Solution Architecture: Unraveling the Differences
Within business technology environments, “enterprise solution architecture” (ESA) and “solution architecture” (SA) are frequently used synonymously even though they actually represent distinct concepts with unique implications.
-
Ineffective IT Architecture? Try the Viable ESA Model
In the IT world, we often see that many well-crafted architectures fail to meet expectations. The reasons are many, but a common one is the lack of a clear model for viability.
-
How to Measure the Viability of an Enterprise Solution Architecture (ESA)?
Every so often, the ultimate measure of an enterprise solution architecture (ESA) is its viability. so, how do you measure the viability of an ESA? Let’s take a look at key considerations from an enterprise business, system solutions, and economic viewpoint. Viability Metrics Enterprise Business Considerations Enterprise Solution Considerations Economic Considerations Often, stakeholder satisfaction (primarily…