How will an architectural framework help me?
Because we thrive on pattern driven design, we of all people should be using a best practice, systematic approach to defining, communicating, improving and measuring our own architectural work. After all, we that's what we expect others to do.
But, you ask me, how can I choose an architectural framework? There's no ITIL / VHS video / clear best choice for me to pick right now!
The good news is that there are some clear distinctions between the value you can get from different frameworks, and at the end of the day, your best solution may simply be your favourite mix of certain bits from each.
Read on and you'll find out how to pick the right solution for your own circumstances.
What architectural frameworks can I use?
A list of links to help you discover what architectural frameworks are available
- TOGAF
- The Open Group Architectural Framework (TOGAF) comprises processes and guidelines to help you create and enhance your architectural descriptions. It has been built from US governmental initiatives during 1990's and is nowadays still being actively improved by The Open Group consortium, whose members include some of the biggest names in the IT world.
- Zachman
- John A. Zachman first published his taxonomy of architectural descriptions in 1987, and his inspiration has probably impacted most of the frameworks that have been developed since. His simple, logical grid ensures we consider all facets of the architecture from the viewpoint of all major system roles.
- FEA
- Federal Enterprise Architecture (FEA) is the US Federal Government's initiative to maximise the business value from the massive projects that are delivered to state departments. Institutions as big as these will need the detailed processes and taxonomies in FEA, and the tools for measuring EA's enhancement to business value will show their effect
- IEEE 1471
- This ANSI IEEE standard describes the "Recommended Practice for Architectural Description of Software-Intensive Systems", and is due to become
ISO 42010. It standardises conventions for architectural descriptions, and ensures that views and viewpoints are created to address specific stakeholder concerns.
Are there different categories of architecture framework?
What frameworks do other people choose?
You may already know which one(s) you like, and wish to share your preferences with others.
What links are others sharing on architectural frameworks?
Where can I find other books about architectural frameworks?
What do you think?
What's your view on this lens about Architectural Frameworks?
Did you learn anything interesting here? Is there something I've missed out?
Let me know :-D
-
Reply
- Rich Hilliard Rich Hilliard Jul 16, 2007 @ 2:53 pm
- The IEEE 1471/ISO 42010 revision will define architecture framework in terms of stakeholders, concerns, predefined viewpoints, and correspondece rules between viewpoints. The hope is to help standardize how frameworks are defined, used, and increase interop between frameworks.
Where can I learn about architectural frameworks?
- A Comparison of the Top Four Enterprise-Architecture Methodologies
- This very informative MSDN Article is written by Enterprise Architecture MVP Roger Sessions. It introduces the four main frameworks in use today, and compares them. It uses some real-world business & IT issues to evaluate the strengths and weaknesses in each.
- TOGAF or not TOGAF: Extending Enterprise Architecture beyond RUP
- This article was written to show how TOGAF can combine with RUP (Rational Unified Process - IBM's equivalent of MSF Microsoft Solutions Framework or ITIL Application Management). As it happens, it actually gives a very clear view of how TOGAF can help enterprise architecture and how it contrasts with other architectural frameworks.
by artemgy
My name is Arthur Gallagher and I am an Information Services Architect.
I love to find simple yet logical ways to deal with issues in making technolo...
(more)




