This week, we broke down a future state architecture into its components: a logical process pattern, a logical information viewpoint, a logical services architecture, and a shared infrastructure services diagram to name a few.
A logical process pattern can be compared to a flowchart, with various processes listed and linked to others, with the end goal of establishing how to manage these processes individually. This could apply to acquiring new customers, maintaining old ones, managing supply chain, etc. But on the whole, it shows what processes are necessary to accomplish the company's goals. Next, the information viewpoint, mirrors the process pattern but with a specific perspective on information. It captures how information flows around the company to help achieve these processes. A services architecture establishes a high-level, centralized view of the services a company has to offer. It can also help display relationships among these services when combined with the process and information diagrams.
Probably one of the most important ones, in my opinion, deals with infrastructure services, or technology. I might be a bit biased, since I have seen multiple companies keep acquiring new EA frameworks from older counterparts without streamlining or simplifying. Regardless, this diagram shows a snapshot of the company's applications and what services each of those applications offer. In short, here is everything in your toolbox to help you get the job done.
When you combine multiple tools like these, it is easy to see how quickly EA can become disorganized if you aren't careful. But it's also easy to identify how helpful a well thought-out architecture can be in aiding customers, employees, and anyone else who interacts with the company on a regular basis.
No comments:
Post a Comment