background preloader

Ea

Facebook Twitter

Todd Biske: Outside the Box » Blog Archive » Oracle OpenWorld. 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. He presented the three domains in a Venn diagram and called out the overlap in artifacts from each, including org structure, infrastructure, business processes, IT systems, and business objects. This overlap forms the foundation for the metamodel which can be captured in Oracle’s BPA suite. In discussing the artifacts, he defined domains for process architecture, application architecture, infrastructure architecture, data architecture, organziation architecture, and service architecture. Free E2AF Cheat Sheet.

I have put together a very high level cheat sheet for the Extended Enterprise Architecture Framework (E2AF). I Basically took all of the topics from the E2AF matrix and built a document with bullets representing each topic. It is organized by the six key questions (Why, With Who, What, How, With What, and When) and has sub categories for each question by the four different view points (Business, Information, Information Systems, Technology Infrastructure). In Appendix A, I included several links to the website where the E2AF information can be found. Appendix B lists all of the E2AF deliverables. My hope is that more people will start using EA or at least ask some of the fundamental EA questions when taking on new projects. The following is my opening statements in the document… Would you build a house without a blue print?

You can download the document here as a zipped file. Enterprise Architecture and Startups. I have a saying that I often use when talking to VCs that goes like this… Startups are quicker to market and quicker to fail Then I explain how our company is built for speed but also for scale (No Fail Whales here)! The reason is simple. We believe in and practice Enterprise Architecture. I can hear you now. How can a startup afford EA? Here are some areas of focus that my startup is addressing: Real time, high volume transaction processingFinancial transactionsSupply-Chain “like” B2BCloud Computing (IaaS & SaaS)Consumer privacyMashupsSOABPM/BRE This is not a typical Web 2.0 startup where I whip up a site in Django over the weekend on a case of Red Bulls and go live on Monday.

So how do we balance speed to market, low cost, and EA all at the same time? In Twitter’s case, when Twitter fails it is an inconvenience for many people. As I followed the framework, I came across one section that asks you to describe the win-wins of the different business collaboration scenarios. I’m Done! - Enterprise Agility - Master Thesis blog on EA, SOA a. MEGA Webinars - MEGA International.

Enterprise Framework Standards. Technology Architecture & Projects: Enterprise Architecture: 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.

EA efforts I've seen that qualify as a "joke" or, more aptly put, failures, generally have one or more of the following characteristics: 1. 2. 3. 6. 7. As I mentioned, there is a lot of chatter about what EA is/isn't on the blogs at present. I'm also very interested in your definitions and comments on enterprise architecture, and if it's good and relevant, your work may make it's way into the Enterprise Architecture Definition Collection...:) Inside Architecture : Agile Enterprise Architecture. US DoD Business Enterprise Architecture. My review of SOA for Dummies. 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. However, its main audience is large organizations (who are the main current adopters of SOA), so much of the content may not apply to libraries, particular those with limited technical resources. Although the Dummies books proclaim "A Reference for the Rest of Us", this book would really more accurately be titled "SOA for Dummies... To my surprise and dismay, there isn't a single mention of Enterprise Architecture (EA) in this book, whereas I feel that for the scale of organization this book targets, EA is absolutely essential. Sidebar Details It is a difficult story to tell to be sure.

Chapter 1 - SOA What? 1. Technology Architecture & Projects: The Enterprise Architect. 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. Of course, as someone who has been called enterprisey on multiple occasions, I don't subscribe to any of these definitions. The best definition and the one I subscribe to is that the real meaning of enterprise refers to a sales model. Self-proclaimed "Thought Leader" James McGovern in his blog, November 5, 2006. An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. Jeanne W. Inside Architecture : Should Enterprise Architecture rock your w. 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 applicationsSimpler applicationsFewer places where the same data was mastered in multiple locations The longer term benefits are the really compelling part: Drop in the cost of ownership (not the cost of development)More rapid development of business capabilitiesBetter business intelligence Sounds good, doesn't it. If your program is established and running, consider a process every 18 months or so to ask the same questions: Is Enterprise Architecture, as it is currently practiced in the organization, producing the benefits that it should produce? Why add this step? Focus on some key areas: Your architects are trained and buy in. What is your impact? Blogs - The Starting Point for SOA |

A Better Path to Enterprise Architectures. Trends in Enterprise Architecture. EAsurvey.org. Skyscrapr. Enterprise mashups: save us from the hype. 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". What started it all was reading Phil Wainewright over at InfoWorld on "Enterprise Mashups: a lesson from history". His post makes a lot of sense. Now here at MWD we are solidly with Grady Booch on SOA – SOA is, first and foremost, about the A part of the acronym (architecture). Inside Architecture : How Enterprise Architecture enables Web 2. 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. Web 2.0 is about building solutions in a new way. Enterprise Architecture does not tell you to build the solution in the correct way, as much as it tells you to build the correct solution. Enterprise Architecture would be completely unnecessary if you could simply teach all of the practitioners of IT software development to build the right systems.

Smart people would notice that stupid things were happening, like many systems showing up in an organization, all doing the same things in a different way, each consuming millions in cash to create and maintain, instead of building smaller components, with independent capabilities, hooked together with messages. Management would say "We agree. Smart people would tell other IT staff to stop doing it. Agile Enterprise Architecture. When project teams work under the assumption that they can do anything that they want, that they can use any technology that they want, chaos typically results.

Functionality and information will be duplicated and reuse will occur sporadically if at all. Systems will not integrate well. Systems will conflict with one another and cause each other to fail. Costs will skyrocket because similar products from different vendors, or even simply different versions of the same product, will be purchased and then operated within production. Although each individual project may be very successful, as a portfolio they may have serious challenges. It doesn’t have to be this way. 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.

Why are enterprise issues an important aspect of the Agile Data (AD) method? In this article, I discuss: 1. This article has been written with the following assumptions: Adaptive. The enterprise architecture online group. The Zachman Institute for Framework Advancement. Enterprise Integration Standards & Models. Institute For Enterprise Architecture Developments. International Enterprise Architecture Center (ieac.org)

EAcommunity (IE only) Architecture Description Languages. 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 AADL consists of AADL can be used to model The language also supports component evolution and large-scale development and accommodates analyses such as reliability and safety criticality (through extensions). The benefits of using AADL include.