Current State Documentation

Current-state documentation is broken into three parts- conceptual application architecture, physical network diagram and business anchor model. These three parts are equally as important. In essence, they are like sides of a triangle and they balance each other out.

Fig. 1 https://www.123rf.com/stock-photo/road_chaos.html

In the current-state conceptual application architecture you will find depictions of the legacy systems in use and how they are used across departments and/or organizations. This illustration is a wonderful way to see where there is overlap and identify areas for integration. These problem areas now become opportunities for improvement and the basis for which the development of the EA plan goes forward from.

In the current-state physical network diagram you get a view of the duplicative processes from another level. The physical network diagram shows clouds, firewalls, servers, VPN's and applications. The overlap identified here points out where you may be able to follow a critical path versus having all of the unnecessary system flow.

In the current-state business anchor model you see a functional view of legacy system use from a high level that will capture the true dysfunction of the task split between legacy systems. The noted disarray speaks to the need for consolidation and provides imagery that is easily understood by team members as well as executives and/or stakeholders.

These three elements will come together in what could be viewed as a truncated format. As my EA professor advised, when discussing and capturing current-state information you need to keep it brief. The fact of the matter is that when people look at their current state they tend to assess and make attempts to fix the current-state. This is not the objective, so it throws them way off course. Expending resources on fixing the current state has likely occurred already and not been successful. So why would you again attempt to fix the current-state? The discussion regarding the current-state is simply to gather information to help determine how far away the organization is from the future-state so that plans can be made to get from A to Z.

Comments

Post a Comment

Popular posts from this blog

Future-State Architecture: Conceptual Level

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
Read more

IT Strategy

Image
Enterprise Architecture IT strategy is yet another area of the EA program that requires documentation. Document development is instrumental to the success of an EA program because it gives the structure and rules that are needed for the organization to follow. When developing the IT strategy document an organization must form the plan of action needed to reinforce and sustain the mission, strategy and objectives of the organization. Fig. 1- Support Image (http://www.okclipart.com/Support-Group-Clip-Art30jdhthnii/) The document is specific to the contributory efforts of the IT department and be relatively brief. To help with illustrating what will be done, there are change requirement matrix that can be developed. One axis will show IT strategies and business change requirements. The other axis will show enterprise business strategies. How the items listed on both axis relate to each other is denoted by a marking in the corresponding intersecting box. With the aid of this matrix
Read more

Future State Architecture: Logical Level

Image
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
Read more