A maturity level is a well-defined evolutionary plateau toward achieving a mature process. Each level provides a layer for continuous process improvement. To start, let’s
John Zachman gave a very good presentation on Enterprise Architecture and The Zachman Framework at The Open Group, San Diego, Feb. 2015. A transcript of
I strongly agree with one point of this strategy+business Enterprise Architecture Planning 2.0 article. That is to get Enterprise Architecture Planning out of the IT department.
Are you in a business support role? This is those roles that aren’t directly involved in selling, delivering, and supporting products and customers. For example,
I agree with the premise of this ComputerWorld article by Frank Hayes - "propose big and build small". Just make sure that you don't follow a huge waterfall methodology.
The concept of the "golden" and immutable database schema makes me crazy. Agile methodologies, like SCRUM, have been adopted by many development groups to account
In UML version 1.4 there were 9 diagrams. In UML 2.2 there are now 14 diagrams. There are seven structure diagrams and seven behavior diagrams.
Are you having problems determining which phase you are in and what your focus should be? Forget the standard names: inception elaboration construction transition Use
I like this mission statement. It is flexible according to business needs and doesn’t paint all business needs and systems with the same broad brush.
Here are a set of IT principles that I have used in the past. Business (mission, strategy & processes) drives the architecture Information is a