Home Tags Posts tagged with "Enterprise Architecture"
Articles Tagged with: Enterprise Architecture
For some companies, the New Year coincides with the start of their planning year, and there are still many companies that go through an annual reorganization of the management structure charts. In any case, New Year is a good time to take stock and think about the future - so here are my recommendations for using TOGAF as your guide.
TOGAF is largely about identifying and documenting architecture requirements... but what is an Architectural Requirement? Frequently we document requirements, not "architecture" requirements! In this blog I explain what we need to do to make requirements architectural.
Architects sometimes see the ADM as reactive, but EA should never be passive - it needs to respond to concerns, but add architectural thinking and then make a unique contribution to stakeholder needs. This blog explains some of the proactive aspects of ADM that are not so obvious.
TOGAF describes three types of architecture role. Two of these types - Enterprise and Solution - are often used in the job title for architects, but it is rare to find someone called a Segment Architect. If you are confused about this missing role... read on, and all will be revealed.
Sometimes people find it difficult to see the unique contribution of EA. So what is it that makes EA distinctive? Here are five things that the best enterprise architects do, and some tips from TOGAF on how you can follow their example.
TOGAF makes a big point of the need for good stakeholder management, devoting the whole of Chapter 24 to the subject, while Step 2 in Phase A: Architecture Vision describes the process to Identify Stakeholders, Concerns, and Business Requirements.
A lingua franca is the language, adopted as common, between speakers whose native languages are different but how useful is TOGAF as an Esperanto go-between language for enterprise architects from different backgrounds?
You started out using TOGAF, you’ve completed an iteration of the ADM for your first EA project and things went well, do you really need to revisit the Preliminary Phase again or can you save time by getting on straightaway with Phases A to H?
Although very similar to the UML 2.0 component, the ArchiMate component concept strictly models the structural aspect of an application: its behavior is modeled by an explicit relationship to the behavioral concepts.
A value can be associated with business services and, indirectly, with the products they are part of, and the roles or actors that use them.