Now that we've broken down the logic behind an EA framework, we can take a look at how we are going to implement it. A lot of these tools will mirror their counterparts in the logical view.
A detailed process diagram is much like the logical process diagram. It shows flows from one process to another, detailing a comprehensive, future-state EA through which the company will eventually reach its goals. But it differs in that it doesn't stop short of process logic like the logic diagram. Rather, it will break down each process into constituent parts. One detail in the readings displays a company's process for "opening a new customer relationship." A step by step definition follows to achieve this goals. The beauty is that this goal can be anything the company is trying to achieve - which is what makes an EA so valuable when done correctly. It will standardize any process so as to bring about a consistent customer experience.
Moving on, a technical network diagram will break down a company's technology. Again showing how to accomplish the job, this nifty little tool focuses less on particular applications and shows a more general layout, including various levels of interaction between servers.
How detailed does the technical documentation have to be? Is it basically just an inputs and outputs, letting IT figure out how A gets to B, or does it dictate the inner workings of the A ==> B process as well? Obviously, it is much more time consuming to be detailed, not to mention needing subject matter experts on the EA team, but letting IT build their own solution has the capacity to off the rails in the long term.
ReplyDeleteThe last module focused on logical and implementation views. Do you think that a position where a liaison who could alter diagrams to the different shareholders would be a good idea? There is a level of technicality necessary for diagramming technology for EA team and IT teams, that quite frankly isn't required for understanding or sharing the same information with other departments or teams in an organization. I think productivity could be maximized if something like this existed in organizations who want to implement EA.
ReplyDelete