Benefits Of Enterprise Architecture

1085 Words3 Pages

Article: Tamm, Toomas; Seddon, Peter B.; Shanks, Graeme; and Reynolds, Peter (2011) "How Does Enterprise Architecture Add Value to Organisations?,"

This article is about how organisations benefit from an enterprise architect. It critically focuses on different review techniques on exploring the detailed benefits of using an enterprise architect. Claim some proposed benefits are interrelated or overlapped.

The article starts of with a detailed definition of what is Enterprise Architecture, it defines EA as the “definition and representation of a high-level view of an enterprise‘s business processes and IT systems, their interrelationships, and the extent to which these processes and systems are shared by different parts of the enterprise.“ …show more content…

Discipline: he describes that enterprise architects has the skills and the knowledge of thinking about the structures of the enterprise known as a discipline.
2. Process: He describes that enterprises architectures are developed through processes, how the processes are managed, how they change and evolve and how architectures are created.
3. Set of work products: Enterprise architecture are described as a set of models and representations to view the structure of an enterprise.

He then talks about the enterprise architects goal that they provide the view of the current structure of the enterprise showing the limitations and constraints from producing models, diagrams, plans and roadmap that gives options that can improve and able to reach their target enterprise structure.

This video is a good in quickly understanding the role of the enterprise architect and why are needed in the organization and how they are benefitted. The diagrams show in the video is clear and simple to understand.

Critical Review of: “Lankhorst M 2009, Enterprise architecture at work: modelling, communication and analysis, 2nd edn, Springer, New York. Chapter 5 A Language for Enterprise …show more content…

It talks the importance of conceptual integrity, meaning ‘the degree to which a model can be understood by a single human mind”. At its core, how easily is the model can be understood by someone else. I do find it very true that everyone has a different way of understanding the models, some may be confused, may lead to the wrong idea or don’t understand the model techniques used.

Further in the chapter, it guides us to how to model and what is needed to be considered in a model, such as the need to be consistent, recognizable concepts and structures, iteratively and economical.

I most interested in the “before you start” section, it specifically asks questions to yourself in considering before starting to model. It makes us analyse and brainstorm.

Later in the chapter it shows examples of the models created for the business, application and technology layer. Gives us specific techniques and terms needed that are used in the models.

Lastly reviewing the model. It is again coming back to the conceptual integrity. Checking the model is readable, its effect. It also includes many visual aspects such as colour, font, symbols and its layout. Checking the readability is very important because stakeholders will need to know and understand the same way as the enterprise architect depending on what and who is designed, to inform and decide

Open Document