I’ve been tangled up on many occasions in methodology terminology discussions this week with various clients, and decided that it might be appropriate to share some thoughts on clarifications on the subject. How boring you say? It’s time for an article to shed light on the differences between a process, approach, methodology and a framework.
related step-by-step guidelines, to develop, upgrade, update improve or replace an architecture, model or system. Methodologies are often called blueprints. Essentially a methodology is the “cookbook” or handbook used to achieve
a goal or task for some component of information technology.
Management Book of Knowledge. Within it, are step by step guidelines to managing a project.  One should note that a
methodology, such as the PMBOK, or the Rational Unified Process identifies ALL the things you might want to do for
your project, and not necessarily dictate that every one of them is completed. Think of it as an a-la-carte menu.
consistent manner and method in which to complete these documents and models. I am not suggesting you make one up, but rather to evaluate your environment and select and adopt the one most appropriate for you within your culture.
example, one might use the ITIL Methodology to complete many components within the Technology Architecuture, The Rational Unified Process to complete components within the Application Architecture, and the IDEF Methodology to
complete Data Models within the Information Architecture.
architecture initiative must be managed as a process and with a strategy that utilizes both a framework and a method-
ology to collectively organize the objectives of the process steps and how to complete them. The framework will identify and organize all areas or domains of concern. A methodology will help you develop a consistent approach in addressing
all the issues and components related to those areas identified by the framework. At a minimum, you must adapt a
project management methodology.
is considered to be best practice or industry standard will allow you to have the most choices for tools, training and
documentation. Keep in mind that the UML is not a methodology, but a notation, but it does provide several
types of diagrams that, when used within a gien methodology, increase the level of understanding of an application or
system under design. The standard diagrams can be part of our design and development methodology.
you think about it with the popular Zachman Framework in mind.
there is a lot to be said for the industry standards or best practices in this case. If you can’t find one that
exactly meets your needs, take the closest one and tailor it to suit your environment, or call in an expert to help
you do this.