Enterprise Architecture Archives

Why Enterprise Architecture? A Short video

April 18, 2017 By Chris Mundy Leave a Comment

Why Enterprise Architecture? If you’re an Enterprise Architect, what do you say when someone comes up to ask, what do you do?

Depending on your audience and outlook, you could say something that could either bore them or help them learn a bit more.

If they don’t ask any further questions, that may show they’re not interested.

However, if they are interested, then most probably, the conversation will come up the following questions,

What is Enterprise Architecture?
Why Enterprise Architecture?

I could write a long blog post about this, or I could let a small video do all the talking.

If you want to understand simply the strategy to manage and grow existing, current and future technology to meet your business needs, then this small video will give you a great snapshot.

I like the way how the video promotes insight and knowledge for us to create solutions that are flexible, robust and efficient for the future.

If ever there was a time to grow an organisation’s technology capability to support a thriving business into the future, then Enterprise Architecture thinking and practices will greatly enable that to happen.

If you want to know more about the philosophy behind this video, go to http://enterprisechess.com Gerben Wierda’s site.

How long does it take to build a mobile APP

January 12, 2013 By Chris Mundy Leave a Comment

I’m not a mobile app developer. The only programming I did was a semester of Java at Uni, however, for over eight years I have worked with and managed developers and programmers developing some funky enterprise software.

I’ve often wondered how long it takes to build an app for a mobile device, whether it be for iOS or Andriod. I came across this info-graphic that attempts to explain how long it takes. There will probably be programmers who would probably beg to differ about the time frames, however the top and lower level column headings, give a great insight into the design process. I hope you find this useful as I did.

How Long Does it Take to Build an App? infographic by Angelina.

By Chris Mundy

The ABCD Method for getting things done

December 31, 2010 By Chris Mundy Leave a Comment

This is a simple process for clarifying your thinking for getting things done. It is based on the interrogative questions of Why, What, Who, How, When and Where.

The diagram speaks for itself, I hope you find it useful.

It seems to be designed for capturing ideas and turning them into reality. You can use this for creating a product, a project or anything where an idea needs some clarification of thoughts.

You will notice that there is no copyright on it. I have a piece of paper that came my way and it fitted in with my approach to IT Architecture.

If I can find the people who originally authored this (with your help), I’m happy to acknowledge the ownership rights to the correct individuals or corporations.

The ABCD Method for planning

A full size PDF Version is available here.

Enjoy

Chris

Intranet Corporate Design Standards

February 6, 2010 By Chris Mundy Leave a Comment

There has always been a discussion on how corporate should an Intranet site be?

My first major experience of a corporate Intranet site was fascinating. It was the thread of a large national organisation of 25,000 employees.

Business units, executive units and teams had developed sites to promote their presence to the organisation. It was a useful tool in understanding the organisation. The organisation provided an alphabetical listing to find what you were looking for a long with proprietary search engine.

It’s front face to the Intranet had a common look and feel, as you got to the smaller business units it didn’t exist. My, weren’t the themes exciting! There were natural art themes, geographical themes, bad colored themes, nautical themes, etc.

The most exciting them was the Buccaneer theme. Behind the text lay pictures of swashbuckling adventures, of pirates and galleons, canons and swords, eh me arties, it was a site to behold, a thing of beauty, however totally out of context for managing Nan and Pop entitlements!

There was only one challenge; the backdrop was so fascinating that you forgot why you came to site. As you can imagine it wasn’t long till the ‘web Nazis’ (at the time we thought they were) said “enough is enough”.

A corporate standard was introduced and everyone hated it. The Web Nazi’s who adopt standards also promote the Borg delivery model of ‘resistance is futile’. (Star Trek idioms)

Well, after a couple of years of promoting the standard, information became more accessible to the reader. Information became more meaningful and the standard did allow for some variations within the theme.

The moral of the story is, corporate standards are not a bad thing. If you’re a small organization looking to grow, start standardising some of your templates; your internet site and intranet site. The value comes down the track as you absorb more information. It will be:

Easy to find
Easy for the search engine to find
More readable

Chris

High-level architecture imperatives of Web based systems

February 6, 2010 By Chris Mundy Leave a Comment

The Sydney Harbour Bridge Earlier this year, I had the opportunity to catch up with a friend in Sydney who was on a short-term work assignment.

His accommodation was located adjacent to Sydney Harbour bridge.

If you live in Sydney (as I use to) you take the bridge for granted, in fact, if you’re a commuter, if can be a downright pain if you get stuck in the traffic.

While I waited for my friend to come out and meet me, I took the opportunity to take a couple of photos of my motorcycle with the bridge as backdrop.

I had travelled over this bridge for most of life, I had read books about its construction, I had climbed it with a friend, however, back in January this year, the ‘wow’ factor cut in.

Its purpose, what it does, how it was built, when it was built, who built it, and the location. When you start analysing it, its an amazingly architected wonder and a lot of thought went into to it.

If you look at the high-level architecture imperatives, we see the following. (Note! Put yourself in the picture back in 1920)

Imperative	Response
What do we need?	Access between the North side of Sydney Harbour (Port Jackson) to the South side to Sydney itself.
Why do we need it?	Currently it takes some time to get to the other side of the harbour. You have to either go further west down the Parramatta river to cross, alternatively, catch a ferry or punt to get to the other side. This is time consuming and costly. Access is limited to a minority rather than the majority.
How will it be done?	By creating a bridge that spans the Sydney harbour
When is it required?	By 1933
Who will it be for?	People who need to access either the north and south of the Sydney
Where will this be deployed?	Adjacent to Sydney city to traverse the harbour.

Using this simple process, we can now apply this to any situation.

Let’s take a Web based system as an example.

What are the high-level imperatives or ‘scope’ for a Web based system used in an organisation?

Imperative	Response
What do we need?	An internal web based system that allows access organisation information, processes, procedures and other web based systems.
Why do we need it?	Customer contact the company to find out information on product specifications. Staff are required access quickly product information. Currently the information exists in several system. Staff have to have several systems open on the desktop which is timely and cumbersome, especially when a telephone enquiry is underway. A system is require to allow quick and easy access to product information for customers and staff.
How will it be done?	By implementing a web based system that aggregates the information in different system
When is it required?	By the commencement of the next business year
Who will it be for?	Customers and Staff
Where will this deployed?	In the Internet environment for the Customers and in the organisation’s intranet environment for the Staff.

Now you can use this process to capture information down through several layers to get a better picture of your requirements. Some of those layers may be for instance:

Scope – This the big strategic view if the requirements (this is the table above)
Business Model – What are the business model that describe the scope
System View – What are the systems that will describe what’s needed
Technological Model – What Technologies will be used
Detailed Model – What are the detailed pieces of inventory that are required.

In the Enterprise computing scheme of things, this what we call the Zachman Enterprise Architecture Framework, created by John Zachman.

Information can be found at:

The great thing about using this approach is that it allows you to collect information on anything you need by asking the questions?

What is required?
Why is it required?
How will we do it?
When is it required?
Who is it for?
Where will this be deployed?

Chris