![]() The software applications that enable the processes, products and services that make money. (There are tools to help do this.)Īpplication systems architecture – provides a blueprint for deploying individual systems, including the interactions among application systems as well as their relationships to essential business processes: A description of the competitive marketplace where the company makes money. A description of how the company makes money today and how it expects to make money in the next 3-5 years. A description of the processes, products and services that make money. “Business architecture – defines business strategy and organization, key business processes, and governance and standards:Ī description of how the company makes money. Technology architecture – describes the hardware, software, and network infrastructure necessary to support the deployment of mission-critical applications.” “Business architecture – defines business strategy and organization, key business processes, and governance and standards.Īpplication systems architecture – provides a blueprint for deploying individual systems, including the interactions among application systems as well as their relationships to essential business processes.ĭata architecture – documents the structure of logical and physical data assets and any related data management resources. The official EA steps include the development of four “architectures”: Who doesn’t want to help technology (AKA “engineering”) – the ones who build the products and services – build the right applications with the right data on the right infrastructure? For technology companies, that is, companies that sell technology-based products and services – the role of EA is easier to define. EA only makes sense when it’s derived from a coherent business strategy. How To Do Enterprise Architecture (Or BTS)ĮA – or should I say “Business Technology Strategy” – isn’t strategy’s first cousin, it’s the offspring. The middle ground is the Business-Technology Strategy. At the end of the day, EA is both a converter and a bridge: a converter of strategy and a bridge to technology. It’s continuous because business requirements constantly change. Why? Because “Enterprise Architecture” is nothing more than an alignment exercise, alignment between what the business wants to do and how the technologists will enable it now and several years out. Enterprise planning or Enterprise Business- Technology Strategy might be better, or even just Business-Technology Strategy (BTS). ![]() All of the abstract terms – even the word “architecture” – should be modified or replaced with words and phrases that everyone – especially non-technology executives – can understand. It should not be mysterious or discrete, and should definitely not be disconnected from current and projected business models and processes which together comprise the overall business strategy. Nor should EA be a remote exercise - or outsourced to vendors who know very little about the company. EA should not be another abstraction that needs translation. We do this all the time: SCRUM, ITIL, Cookies, Spam, Malware, Netiquette, Microblogging, SEO, API, Caching, Virtual, Firewalls, Routers, Bluetooth, API, SaaS (PaaS & IaaS), NLP and Waterfall. )ĮA should not be an abstraction with weird, esoteric terms. Clear enough, I guess, but why are there so many EA project failures? ( WhiteCloudSoftware suggests that 66% of all EA initiatives fail. If I have this right, EA (at least everyone agrees on the acronym) is derived from business strategy and focuses on “current and future (business) objectives,” or “desired business vision and outcomes.” While I have no idea why definitions don’t speak directly to strategy, I can live with the interpretation of EA around business performance.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |