Enterprise Architecture

Why Application Architecture

Posted on 06/11/2012. Filed under: Application Architecture, Enterprise Architecture, Software Architecture |

In our previous update I spoke about Business Architecture and what the value it brings.
Today we will continue with the next domain called Application Architecture (AA) – not alcoholics anonymous…J Without EA business leaders might be driven there…J
Input from previous architecture tasks will greatly aid this process. Deliverables such as architecture vision, application architecture principles etc will set the framework within which the AA can be developed.
Industry specific model can \ should also be used as input for this process, such as www.tmforum.org for the Telecommunications industry.
System and application is used as synonyms.

What is AA?
“System architecture is an abstract description of entities of a system and the relationships between those entities” – The influence of architecture in engineering systems. MIT Symposium, March 2004. http://esd.mit.edu/symposium/pdfs/monograph/architecture-b.pdf

The Goal:
To develop a target application architecture that will enable the Business Architecture and the Architecture Vision.

Typical Outputs are:
Application list
Application components diagrams
Application decomposition diagrams
AA views:
– Functionality
– Integration
– Development
– Operational concerns
– Migration
– Cross functional matrices

Connecting the dots
How many applications support business process A in HR division in the organization?
How many systems \ applications support or provide the same functionality?
What cost can be saved by removing duplicate applications providing the same functionality in the organization?

Read Full Post | Make a Comment ( None so far )

Do you live by principles

Posted on 30/10/2012. Filed under: Enterprise Architecture |

We all do live by principles. I shall not lie, steal, kill etc.

This drives your behaviour each day and the choices you make.

Well, why don’t you apply principles to your profession?

Let’s look at what are some sample Enterprise Architecture Principles.

According to the 4 architecture domains in TOGAF principles can be defined for either:

  • Business
  • Data
  • Application
  • Technology

What is a good example of a principle?

Here is a practical Data principle used recently on one of our bigger clients.

+++++++++++++++++

PRINCIPLE 3: DATA IS AN BUSINESS ASSET

Statement:

Data is an asset with real tangible value to business .

Rationale:

Data is the source of information upon which business makes decisions. These decisions have tangible and measurable value to the enterprise .

Implications:

Data is owned by the business and not by any system or information technology vendor.

To realize the value of data a consolidated unified view is required by the business. This will prevent having data silos due to multiple transactional systems.

Data must be accessible and available to business for it to become an asset.

Data requires stewards to ensure its viability, correctness and accuracy is constantly improved. Stewards must have the authority and means to manage the data for which they are accountable.

The time to deliver data to the business as an asset needs to be constantly improved upon .

+++++++++++++++++

What principles do you employ \ encourage in your business?

Read Full Post | Make a Comment ( None so far )

Change your business with zero IT cost

Posted on 02/06/2011. Filed under: Enterprise Architecture |

You are reading this because you would like to know how, well it is simple. It’s impossible!

Since I have your attention, I would like to share some thoughts with you to minimize the costs.

One: Incorporating a cloud solution to business intelligence (BI) project at one of my clients, it just struck me once more what a LARGE impact a “small” business decision has on information technology (IT). Technology has become so ingrained into business that there is virtually no separation. Changing technology impacts business and vice verse. Needless to say both imply costs.

Two: Without a head to steer the body chaos is imminent. Similarly to business requires a CEO, your organization requires a CIO to steer the business’ technology aspects. C is for Chief, whom holds the responsibility to set visions, strategies, objectives and tactics. Metaphorically he is the driver of the chariot who ensures all the horses pull in unity and the same direction.

Three: The CIO should embrace the professional enterprise architect’s depiction and knowledge of the inter-relationships between business and technology as foundation to ensure business strategies and objectives are met. Through enterprise architecture (EA) business visions will continuously be met and support future business changes.

Four: EA is a very large complex profession but its implementation could be very simple. Business adoption and implementation of EA is simplified by the skilled EA professional. EA is not a project but a strategic business division. EA is an operational (OPEX) – and not a capital (CAPEX) expense.

Five: EA implementation is governed by project management best practices. A phased approach achieves best results for all stakeholders.

Whether you agree or not, I would love to know.

Read Full Post | Make a Comment ( None so far )

How does your architecture compare?

Posted on 07/12/2010. Filed under: Enterprise Architecture |

This morning I have seen a website that puts the universe (as we think we know it) into (some type of) perspective.

How easy is it in this money driven world to brag about how much revenue you generated by your great enterprise architecture efforts; or how much costs you saved with your big new idea.

Then some people boast about their professional achievements or academic qualifications with such energy that they think almost convince us of their superiority. In humbleness, achievements are just recognition of the gifts / talents that one received. Now to all the self proclaimed superior individuals or enterprises just see where you fit into the universe.

Have a look and tell me honestly whether your business, achievements or qualifications can compare to the Creator of the universe and to this day still keeps it in perfect harmony.

Can your solution scale to this magnitude?

Is your architecture efforts self sustainable?

Will your architected solution be around for the next 100 million years?

A special thank you to Gary and Michael Huang.

Link: http://uploads.ungrounded.net/525000/525347_scale_of_universe_ng.swf

Read Full Post | Make a Comment ( None so far )

SAP Cloud Computing Shake-up

Posted on 11/02/2010. Filed under: Cloud Computing, Enterprise Architecture |

How long can SAP stay out of the cloud computing game? [tweetmeme source=”EmunaConsulting” only_single=false]

My guess is not any longer and they know it, they are losing market share as you read this article.

An in-depth article on the New York Times is available below.

“Instead of the big corporate contracts on which SAP built its business, “cloud computing” programs, like Business byDesign, are aimed at small and midsize companies and delivered over the Internet for a monthly subscription fee. To stay current, analysts say SAP must convert itself from a monolithic provider of end-to-end solutions to a nimble provider of easy-to-operate services, and it must do that while defending its existing business.

“We are at the advent of some of the largest changes in our industry in terms of computers,” Mr. Plattner said, and it would be “absolutely catastrophic to be stuck in the maintenance side and not be storming ahead in innovation. We have to maintain and innovate, and the company will do both.”

Mr. Plattner, one of the ex-I.B.M. employees who founded the company in 1972, is SAP’s largest shareholder, with more than 10 percent of the stock…”– link

StumbleUpon.com

Read Full Post | Make a Comment ( 1 so far )

« Previous Entries

Liked it here?
Why not try sites on the blogroll...