Architecture Frameworks have an undeserved reputation for being theoretical and passive. In this article we argue that the popular frameworks, such as TOGAF or Zachman, need to be tailored and adapted to create a set of active and useful frameworks – called Multiple Integrated Architecture Frameworks (MIAF).
We look at some of the reservations that students have about TOGAF just after they complete the TOGAF training course. This time we look at the typical positive remarks that TOGAF gets.
You’ve just spent several hours working your way through the TOGAF training. Now you are prepared and ready to take the TOGAF exams and gain your certification.
This second of three articles concentrate on the relationships associated with each of the elements in the Business Concept library. Certain relationships apply to each concept and should be understood by EA practitioners.
The next three articles concentrate on the relationships associated with each of the elements in the Business Concept library. Certain relationships apply to each concept and should be understood by EA practitioners. The relationships were stated in the previous articles; this article expands on those aspects.
Quite frequently I get asked about the scope of Enterprise Architecture. Sometimes the question is a simple one: what is included in a typical EA initiative? But sometimes there’s a bit more to the question, with an implied: why is that included in EA? This question came up a couple of times this week, so it seemed a good time to go over some of the key points in this blog, and explain what TOGAF has to say about scope.
Business Layer Informational Concepts: Structural and behavioral concepts are mainly concerned with the operational perspective on an enterprise. Informational concepts focus on the “intentional” perspective.
Process approach is a common phrase, used in modern business. However, despite of its common use, there are many misconceptions around the phrase. This blog post tries to clarify the phrase as well the related concepts.
Business Layer Behavior Concepts: Based on service orientation, a crucial design decision for the behavioral part of the ArchiMate metamodel is the distinction between “external” and “internal” behavior of an organization.
Business Layer Structural Concepts: The Business Layer identifies the concepts and relationships of the highest level of the architecture: the end product, and the customer delivery system.