©2007 B-Wave Software.

All rights reserved.

IT’s Transformation

 Roadmap
Text Box: Define Architecture. Text Box: Construction Architecture has been developed for thousands of years. Now it comes to the level of Meta-Architecture, like the Tokyo Sky City project describing and organizing architectural entities like : Buildings (apartment complexes); Parks (inner green spaces); City transportation (inter-level elevators); Neighborhood transportation (In-level monorail trains) Stadium etc. This is an example how the highest-level Meta-Architectural framework not only organizes but also puts some restrictions on underlying frameworks. For example, the architecture of the buildings cannot be a matter of taste and talent of an architect anymore but obeys the rules and constraints of the overlaying framework. However, these constraints do not limit implementation of any specific detail of the underlying artifacts while bringing the outmost efficiency to the whole structure. Text Box: There are lots of commonalities between Constructional and Enterprise architectures. Both constitute higher-level general frameworks that describe and organize lower-level (Design) entities. These frameworks define which design-level entities - artifacts- exist inside it, and by what rules they cooperate with each other. Any close accumulation of the lower-level artifacts create the upper-level framework. The only difference between chaotic bottom-up and scientific top-down approaches is the quality of a framework that is created. Text Box: Constructional Architecture Text Box: Enterprise IT Architecture Text Box: EE is completely BPM/ESB/SOA based. To explain its operational let us consider the usual Event-Driven user request scenario: One of the external Actors places a service request through one of the Channels; This request is translated into one of the standard (usually XML-based) formats through XML /Security Gateway and is placed on the ESB as a request message; The corresponding Business Process Flow (BPF) Instance in a BPMS reacts by proceeding through BPF; On the way it calls, in an uncoupled manner, different services from Business and Data Service domains, as well as Business Rule Engine (BRE) services. Every service produces some functional activities and reacts with a reply message containing information that eventually reaches the actor to notify her that the request has been fulfilled (or not) Text Box: In exactly the same way, the chaotic, accidental accumulation of the IT artifacts—applications creates ineffective and inefficient Legacy ‘spaghetti’ IT Architecture. The same bottom-up accidental approach, which ignores the basic architectural principles provides Enterprise personnel and their customer with the more or less same level of services and capabilities as inhabitants of favellas. Text Box: Rio’s favella, not typical Rio’s architecture. Text Box: For example, chaotic construction of individual cubical homes-shacks in Rio de Janeiro’s infamous favellas spontaneously creates chaotic, ineffective and inefficient construction architecture. The resulting framework creates redundancies in utilities design; more often it effectively deprives people from an ability to use many civilized utilities. Text Box: 1.The Chaotic One Text Box: A typical Legacy IT Architecture Text Box: 2.The Elegant One Text Box: It might seem strange to some IT people, but most of Rio’s residents prefer not to live or work in favellas. They use instead contemporarily architected buildings where offices or apartments do not connect each one with another by some sort of external ladders or tunnels , and do not have separate electric, phone, cable, water and sewage systems. Instead they surprisingly have connected to each other by simple common means—hallways on the same floor and elevators between the floors, and they use centralized top-to bottom designed utilities ( ). Text Box: Rio’s modern architecture. Text Box: Just like Rio’s residents, IT people prefer to live and work in the properly architected buildings with hallways and elevators, and centralized amenities. When it comes to creating IT artifacts, though they surprisingly prefer living in and re-creating virtual favellas. It does not mean that they do not have a choice. The goal of this website is to show what does it mean contemporarily architected Enterprise IT. The Service Orchestrated Architecture Framework (ESOAF) shows how it is possible to transform Legacy Enterprise IT into what we call the Elegant One. Text Box: Modern Elegant Enterprise Text Box: This picture shows modern buildings architected in the way that most effectively organizes and describes constructional design entities: Apartments; Offices; Service Utilities Means of transportation; Means of communication, etc.; . Text Box: Both examples represent consistent Architectural Frameworks that include a cohesive set of meta-design entities. The Frameworks are absolutely agnostic concerning the Design Frameworks used by either constructors (rooms design, furniture, office equipment) or IT engineers (service or processes design methods, technology, host boxes etc.) Text Box: 3.The Future One Text Box: The future of IT Architecture is clouded. Literally. It is in a Cloud. Enterprise Cloud Architecture most probably will be the next stage of EA, especially if it will fail to transform. The development of such an architecture is our next goal. Follow our site for this development Reserved: Heavenly Enterprise