Full disclosure: I am attending Oracle OpenWorld courtesy of Oracle. The speaker is Dirk Stähler from Opitz Consulting And he is talking about how to bridge the information gap using Oracle BPA Suite and an integrated model. He started by presenting the EA, BPM, and SOA problem which includes no unified methodology, unclear semantics, and no differentiation between EA, BPM, and SOA aspects.
The live web conferences demonstrate MEGA's solutions in terms of consulting services and software to enterprise architecture, business process analysis, operational risk management, internal audit. During these interactive web conferences you will have the possibility to ask questions either via your phone call connection or through the chat room. After registration, you will be contacted with online web conference log-on details several days prior to the web conference. <p style="text-align:right;color:#A8A8A8"></p>
Interesting discussion erupting in the EA blogosphere about what Enterprise Architecture really is. Actually, this dialog has been going on for some time now, but a number of bloggers appear to be embracing the issue very recently. The primary reason that I collect and publish "definitions" of enterprise architecture on my blog is not because enterprise architecture is a "joke," as some revealed tongue-in-cheek, but more that EA isn't defined well enough to model and operate a successful EA organization.
One of the things I've learned from Agile methods: Deliver Early, Deliver Often, Take Feedback, Iterate. When you do, your perception of value goes up, and you build trust with the customer, especially if they are not sure you are doing what they want done. Building an Enterprise Architecture, in a company that is not used to having an Enterprise Architecture, can sometimes be frustrating.
Summary I am reviewing this book primarily in the context of Service-Oriented Architecture (SOA) for Libraries, which is a rather dramatically different audience than it is intended for. I recommend the first three chapters of this book, along with the "loosely coupled" section of chapter 5 as a good introduction to this topic. As well, Chapter 11, on SOA Governance, is excellent.
It's interesting, at least to me, to get a sense for all the different definitions of enterprise architecture out there. So, over time, I will post other people's definitions of enterprise architecture (and their sources) as I run across them in the literature, blogs, and websites. Updated November 5, 2006. Maybe the problem is that the word enterprise is abused. Some folks consider the word to refer to size of organization, while others thinks that it refers to a class of software in terms of its ability to scale along a variety of dimensions.
In many organizations, EA is a sidelined process or a last thought. It is hard to be effective in that case. In other organizations, EA is a core part of IT planning and delivery. It is difficult to imagine EA having anything less than a pivotal role there. The benefits of an Enterprise Architecture program are clear: Fewer applications Simpler applications Fewer places where the same data was mastered in multiple locations
Cloud Optimized Architectures for the Public Sector: A CUEC Position Paper (19 June 2011) The U.S. Federal Government continues to struggles with IT. A number of approaches are being tried to address this long-term problem.
James McGovern , Enterprise Architect for The Hartford, and all around Enterprise IT Thought Leader, recently posted the characteristics of Enterprise Architecture 1.0 versus Enterprise Architecture 2.0: Abstract Authority Community Project Oriented Management Strong Technical Leadership Comprehensive Documentation Working Software Following a Plan Responding to Change
Tuesday, March 14, 2006 by admin I know I’m going to come across like the annoying old fella who sits in the corner at any fun event and mumbles to himself about how rubbish things have got since men started wearing their hair long – but in the spirit of my esteemed colleague’s emerging manifesto for industry analysis (he hasn’t forced me to sign up yet but it’s probably only a matter of time) I thought I should at least make a (possibly vain) attempt to push back at some of the unthinking evangelism that’s going on out there concerning Web 2.0 ideas and their application to enterprise IT. In the name of education, not evangelism: let’s scotch the idea of "enterprise mashups".
The role of an enterprise architect is not well understood. That much is clear. Some folks say that EA is at one end of the scale, while Web 2.0 is at the other. Those people are not enterprise architects. They are missing the point.
The cold reality is that very few software-based systems exist in a vacuum, instead they must co-exist with several and sometimes hundreds of other systems. Applications must co-exist effectively with the other systems within your organization. Therefore an application must minimally be developed so that it doesn’t cause adverse affects on your other systems and ideally it should be built to take advantage of and to enhance a shared infrastructure. Every system must be built so it can fit into your existing environment, better yet so that it reflect s the future vision for your organization. This sort of information should be captured in your enterprise architecture, in current state and future state models respectively. One goal for agile enterprise architects is to ensure that this happens in an effective manner, to ensure that the needs of the business stakeholders are understood and anticipated, and to support project teams in their development efforts.
Frequently Asked Questions FAQs about Enterprise Integration Standards and Models. The following are "Open" Enterprise Integration Standards from various industry and government groups. It is not meant to be exhaustive, but rather is intended to direct the reader towards the most important standards. APICS American Production and Inventory Control Society is a "not-for-profit" membership group serving the MES (Manufacturing Execution Systems) industry.
An SAE International standard established in 2004, the Architecture Analysis and Design Language (AADL) provides a new framework that allows analysis of system (and system of systems) designs prior to development and supports an architecture-centric, model-based development approach throughout the system life cycle. System developers in industry and researchers in leading universities in Europe and the U.S. use AADL to predict and validate nonfunctional properties. In addition to providing technical leadership for AADL development, the SEI provides training and technical assistance to support the use of this standard language for architecture design and analysis. The AADL lowers costs in development and maintenance through