Menu
An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of organizations. The intent of enterprise architecture is to determine how an organization can effectively achieve its current and future objectives.
What Does Enterprise Systems Architecture (ESA) Mean? Enterprise system architecture (ESA) is the overall IT system architecture of an organization. This architecture is the key part of managing and evolving IT systems, and therefore the business operations, of an organization.
If you want to become a building architect or a designer, you will learn the four basic elements of architecture and design: Point, Line, Plane and Volume. With these four elements, you actually can create any architecture or design.
I am currently tasked with creating a documented, consistent Architecture guide for software development. We have a lot of smart people doing the right things, but just not consistently and repeatably.
We are using Microsoft’s Application Architecture Guide 2.0 as a starting point. Hence coming up with an Application Architecture is fairly (I won't say easy) straight forward. Possibly because I have a couple of years experience as a developer so I have a pretty good understanding of this realm and there are also loads of examples and guidance.
Since our organisation has a couple of applications that form 1 or more systems which we then install "at" clients... we thought it would make sense to create a System Architecture and an Enterprise Architecture as well. And this is where the problems start.
There is no consistent guidance out there. If you search for "System Architecture Examples", the stuff that you get back is so different that I am wondering if there is a "Standard" way to do this.
From my (Limited - clearly) understanding of it all, the System Architecture is an abstraction of 1 or more application architectures depicting how they work together to form a system. Furthermore, an Enterprise Architecture is a further abstraction showing how your system(s) fit into a organisations Enterprise and how it interacts with the Business processes, IT Strategy and how it Integrats into other systems in the enterprise.
I don't want to simply list a set of SOA related patterns that may be useful... I'd like to make it a little more focused to what we do, which is the build financial solutions on a Service Orientated Architecture.
Update: What about TOGAF(9). Does anyone have experience with it at all and is it worth the effort of trying to understand it in detail.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With