|
©2007 B-Wave Software. All rights reserved. |


|
IT’s Transformation Roadmap |
|
IT’s Transformation Time |
![Text Box: “Jan. 1, 2008, stands out as an important marker along the winding road that eventually will lead to the end of the enterprise IT as we know it…
...An IBM executive says his company will begin to sell … software to [business] workers—bypassing the IT department… [It will] make business mangers - not the IT department - the arbiter of all things digital…[It] gives enterprises computing muscles without the need for a massive internal IT organization.
...More than third of top managers agree with Nicolas Carr, the Does IT Matter? author who stated: “We’ve entered the long twilight of the CIO position” - Erick R Chabrow. Is the Clock Ticking on IT?. CIO Insight Magazine, No92. 2008. p.9](index_files/image1002.png)

|
Executive Level Declaration Of Our Vision and Principles . |






|
· IT as an industry has over time developed immanent problems caused mostly by the legacy-style development of applications as isolated silos of functionality and data processing, and their consecutive point-to-point integration ; · Today’s IT differs from that of 20 years ago not only in technology but first and foremost in complexity; · This complexity has been rising steadily over the past two decades. Computer Science (CS) as an underlying scientific/methodological base for IT has faced this phenomenon with an adequate rising level of abstraction of concepts dedicated to handle it: first Analysis and Design, and more recently Architecture. · Any Enterprise creates Architecture; Legacy Enterprise creates chaotic, rigid, rookery-like one that makes the whole IT structure rigid, ineffective, inefficient and self-destructive; · Attempts to ameliorate the cost side of the problem by simple cheap labor outsourcing of the existing structure without any qualitative changes might bring temporary financial relief but will eventually threaten the very survival of the Enterprise and/or its internal IT; · The architectural solution offered by CS is based on the concepts of BPM, ESB and SOA, comprehensively united in the Architecture Framework (EAF). Such a Framework is understood as a scientifically based , precise, and practical day-to-day, month-to-month, year-to-year transformation plan for an Enterprise, rather than as a descriptive discipline of J. Zackman’s ZIFA times; · The ESOAF™, introduced at this site is the only complete, cohesive, comprehensive, and proven framework in existence based solely on BPM/ESB/SOA principles, which allows Enterprises to safely, steadily and securely migrate from Legacy to Elegant Enterprise. · Unfortunately, as shown by the quotations in the epigraph to this page, an average Enterprise Internal IT sometimes tends rather to be reluctant to the new methodologies. We hope this tendency change and ready to help Enterprises to change IT; · If it will not happen soon, the new solutions, providing Enterprise Business Management (EBM) with the direct services of the major technology and methodology vendors like IBM®, Microsoft®, Oracle®, SAP®, Salesforce®, HP® etc.) , which avoid IT as a mediator will lead (and already have ) to adoption of a new strategy called Cloud Computing that allows EBM to outsource completely its business processes and services to vendors’ Clouds, ignoring and ultimately eliminating internal IT departments. · We consider the outsourcing of the parts or the whole IT as an objective, inevitable, already happening process. However, history in general and especially the history of IT teaches us that the most productive concepts might be and will be implemented wrong (just because they might ). The Cloud Computing (CC) is not an exception. Most of CC utilities are agnostic to WHAT Enterprise outsources there to run. If Enterprise outsources bad architected solutions, they will run them and bill the Enterprise for their inefficiency. It is because what Enterprise really outsources to a Cloud is its Business Architecture. So results will inevitably correspond to the quality of this architecture. · HOW this process will advance, WHAT results it brings depends on new type of Enterprise Architecture declared and being developed on this site—Enterprise Cloud Oriented Architecture (ECOA).
IT’s Decision Time Now: Transform or Perish!
If you decide not to perish, we are at your services.
Just another remark: IT and its surrounding phraseology is currently a land of confusion. That is why every concept we use in this site starting from Enterprise to Architecture, to Enterprise Architecture, to SOA is thoroughly and unambiguously defined. Please go to the ESOAF Dictionary page or browse this side to find it. If you do not agree with something (or everything ), please let us know through our blog or email. |