Skip to main content

An overview of IT Architecture

Drivers for IT Architecture:
  • The cost of information technology, particularly in lean economic times.
  • The increasing complexity of information technology.
  • The rapid pace of change and hence rapid obsolescence of information technology.
  • The increasing expectations of end-users for information technology reliability, performance and functionality.
  • Increased societal dependence upon information technology.
  • The widespread ‘quality chasm’ between information technology best practices and actual day-to-day practice, particularly in the area of software development.
  • Security concerns and requirements.
Common features of IT Architectures:
  • High-level statement of IT Architecture goals and governing principles (Vision).
  • Conceptual model of the ‘architecture’ of the organization, including models of agency business functions and processes, agency information assets, and agency information technology (Architecture).
  • Standards that define how applications are developed, which technologies are supported, and what products are selected. (Standards).
  • Governance structure that includes business leaders and technologists to ensure ongoing alignment between the organization’s business priorities and information technology efforts (Governance).
  • Continual re-examination of the IT Architecture to identify opportunities for enhanced organizational cost-effectiveness and performance (Lifecycle).

The enterprise is becoming more complex with reduced time levels to level products and services to market. Customers and regulators also demand a better accountability. As a result there is a greater dependence on IT.

The IT environment thus needs to be better understood and aligned to business processes.

Architecture maturity
Gartner proposes the following architecture maturity model.
  1. Chaotic - Ad-hoc, Uncoordinated, Undocumented, Unrelated to business strategies.
  2. Reactive - Isolated, Opportunistic, Business involvement only in times of crisis.
  3. Proactive -Some coordination across business units, Spasmodic documentation, Occasional business involvement.
  4. Service - Consistent architecture processes applied inconsistently, Coordination across most business units, Responsive to business strategy.
  5. Value - Consistent, effective architecture management process, Coordination across the enterprise, Enable business strategies.
Reasons for IT Architecture are:
  • Alignment - ensuring the reality of the implemented enterprise is aligned with management’s intent
  • Integration - realizing that the business rules are consistent across the organization, that the data and its use are immutable, interfaces and information flow are standardized, and the connectivity and interoperability are managed across the enterprise
  • Change - facilitating and managing change to any aspect of the enterprise
  • Time-to-market - reducing systems development, applications generation, modernization timeframes, and resource requirements
  • Convergence - striving toward a standard IT product portfolio.
Benefits of IT Architecture:
  • Capture facts about the mission, functions, and business foundation in an understandable manner to promote better planning and decision-making
  • Improve communication among the business organizations and IT organizations within the enterprise through a standardized vocabulary
  • Provide architectural views that help communicate the complexity of large systems and facilitate management of extensive, complex environments
  • Focus on the strategic use of emerging technologies to better manage the enterprise«s information and consistently insert those technologies into the enterprise
  • Improve consistency, accuracy, timeliness, integrity, quality, availability, access, and sharing of IT-managed information across the enterprise
  • Support the CPIC processes by providing a tool for assessment of benefits, impacts, and capital investment measurements and supporting analyses of alternatives, risks, and tradeoffs
  • Highlight opportunities for building greater quality and flexibility into applications without increasing cost
  • Achieve economies of scale by providing mechanisms for sharing services across the enterprise
  • Expedite integration of legacy, migration, and new systems
  • Ensure legal and regulatory compliance.


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi