Random Enterprise Architecture Talk

The implementation level of the future state architecture in EA is the next step in the sequence. At this point the organization has worked through conceptual process and logical process. It is time to progress to how to go about instituting the processes needed to build an ongoing EA program. In this level the organization will concentrate on the details. Things will be reined in- in stark contrast to the conceptual level. As illustrated in Figure 1, you will note that the higher the level the bigger the picture. As you drill down to the lower levels, the picture becomes more focused. The business process and how they will be impacted are clearly seen in the implementation level. Process maps, worksheets and technical network diagrams are artifacts that are created at this level. Within the artifacts there are certain relational dimensions that will be outlined to provide a good illustration of the end goal. You will find patterns, domains, services, components and products. These d

There are levels to future state architecture. The logical level incorporates communication tools. The logical level is evident in more than just a specific area; it is seen over various business functions. The logical level supports strategy and therefore includes information flows to executive leadership, information architect and EA teams.  In the logical level of future state architecture the logical information flow the customer is at the center of the diagram. This is important to note because with the customer at the center, you ensure that the along with the information that needs to flow out from the customers the appropriate information comes to the customer as well. Being involved in the  EA process embeds the customer in the program and gives them the appropriate amount accountability.  Risk management and  satisfaction are managed through information flow. Proper updates go across banking, underwriting, credit reporting agency, fraud management, information security, m

Building an EA program is not simply evaluating where your organization is and identifying how to put Band-Aids on your current state. A very large part of implementing an EA program is conception- perceiving what will be. An EA Architect must outline the future-state to create the roadmap that will be followed to get there. There are numerous items for consideration in the conceptual phase including principles, process patterns, process typologies, information patterns, application architecture, and data stewardship requirements.   In organizations that do not take the time to envision their future state and consider the elements within the conceptual phase there are typically very poorly implemented EA programs. At times organizations implement programs in haste out of necessity and this leads to inability to implement properly. My organization often implements in haste and runs into these types of issues and the product is not well known, well received or utilized well. The

As a part of the EA journey many different processes, methods and tools have been developed. One of the tools that was created was a matrix that illustrates the common requirements vision. This document  encompasses four crucial things- business strategies of the enterprise, environmental factor impacts on the strategies, implications of the strategies and environmental factors on business process, information and technologies  (see fig. 1 below) . Bringing these vital pieces of information together in a format that allows for plan weaknesses to be seen prior to beginning implementation improves the likelihood of success. All components must be present in the array and be able to function without reducing any other components value or functionality within the matrix. In some organizations no matrix is made. The decision on what stakeholders to bring into the EA implementation process is based upon what a handful of people in leadership decisions determine to be appropriate. This put