Skip to main content

Great set of IT Architecture resources from Bredemeyer Consulting

Papers on Software Architecture, Architecting and Architects
  • "Architect: What's in a Name?" by Ruth Malan, April 2006.
    "Architects and Accountability," by Ruth Malan, April 2006.
  • "Key Architecture Decisions Template" (MS Word doc), by Anshu Gaind, October 2005.
  • Ruth Malan and Dana Bredemeyer wrote Cutter Consortium's June 2005 Enterprise Architecture Executive Report. It is titled "Enterprise Architecture as Strategic Differentiator." You can download a complimentary copy from
  • Dana Bredemeyer and Ruth Malan, "What it Takes to be a Great Enterprise Architect," Enterprise Architecture Executive Report, Cutter Consortium, August 2004. Cutter is running a promotion, and you can download this issue free at This report is useful for solution, platform and software architects as well as Enterprise Architects.
  • Ruth Malan and Dana Bredemeyer have completed another chapter (draft) of the Software Architecture Action Guide book. See
    -- Meta-Architecture chapter: MetaArchitectureActionGuide.pdf, 237kb.
    -- Conceptual Architecture chapter: ConceptualArchitectureActionGuide.pdf.
    See Table of Contents to download drafts of chapters. Join our mailing list to receive updates.
  • "Architecture as Business Competency", (ArchitectureAsBusinessCompetency.PDF, 97kb) by Ruth Malan and Dana Bredemeyer, January 2004. January 15, 2004.
  • We would like to thank the following reviewers who have given us feedback (see detail):
    - Claire Streb, Real Time Enterprises, Inc.
  • We are privileged to be able to bring you "Chapter 7: Deployment Architecture" of Luke Hohman's new book, titled Beyond Software Architecture: Creating and Sustaining Winning Solutions, © 2003 Pearson Education, Inc. Republished by permission of Pearson Education, Inc. (publishing as Pearson Addison Wesley). This book delves into many of the non-technical concerns of an architect, in addition to some of the more technical ones. For more information on Beyond Software Architecture and to order it, see the book page on the Addison-Wesley site (
  • Software Architecture: Organizational Principles and Patterns: Preface and "Rhythm: Assuring Beat, Process and Movement" chapter 4, by David Dikel, David Kane, and James Wilson, Prentice-Hall, 2001. For more information on this book and to order it, see the book page on the Prentice-Hall site or
  • "Software Architecture: Central Concerns, Key Decisions" (ArchitectureDefinition.PDF, 124 kb) by Ruth Malan and Dana Bredemeyer, May 2002.
  • "Less is More with Minimalist Architecture" (MinimalistArchitecture.PDF, 47kb) by Ruth Malan and Dana Bredemeyer, published in IEEE's IT Professional, September/October 2002. © 2002 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.
  • "The Visual Architecting Process" (VisualArchitectingProcess.pdf, 223kb), by Ruth Malan and Dana Bredemeyer, January 2005. (Revision of the May 2003 paper) <1>
  • "Defining Non-Functional Requirements" or System Qualities (nonFunctReq.pdf, 39kb), by Ruth Malan and Dana Bredemeyer, August 2001.
  • "Architecture Teams" (ArchitectureTeams.pdf, 23kb), by Ruth Malan and Dana Bredemeyer, March 2001.
  • "Creating an Architectural Vision: Collecting Input" (vision_input.pdf, 10kb), by Ruth Malan and Dana Bredemeyer, July 2000. See also Newspaper_ Vision.pdf (34 kb), which is a fictitious vision article we created in the year 2000 as a promotion. Back then, 2003 was three years out, not 3 years behind us! Sadly, this vision is still relevant to many companies 6 years after vision was written!
  • "James Madison and the Role of the Architect" (madison.pdf, 7kb), by Dana Bredemeyer, June 1999.
  • "Role of the Software Architect" (ArchitectRole.PDF, 40kb), by Dana Bredemeyer and Ruth Malan, 2002 (minor revision of 1999 paper).
  • "Functional Requirements and Use Cases" (FunctReq.pdf, 39kb), by Ruth Malan and Dana Bredemeyer, June 1999.
  • "The Tao of the Software Architect: Lao-Tsu, revisited" (tao by Kruchten.htm) by Philippe Kruchten (Rational).
  • What: Architecture Definition, by Ruth Malan, presented at the Indianapolis Java Users Group, April 2005. (SoftwareArchitectureIntro.PDF). <4>
  • Architecture Strategy Choreographs the Dance of Change, by Dana Bredemeyer and Ruth Malan, September 2003. (ArchitectureStrategy.PDF, 872 Kb). <9>
  • Enterprise Architecture as Business Capabilities Architecture, by Dana Bredemeyer, Ruth Malan, Raj Krishnan and Aaron LaFrenz, May 2003, updated May 2006. (EnterpriseArchitectureAsCapabilitiesArchSlides.PDF, 317 Kb). <05>
  • Overview of the Visual Architecting Process, by Dana Bredemeyer and Ruth Malan, May 2003. (VisualArchitectingProcessOverviewSlides.PDF, 2.7 Mb). <5>
  • What it Takes to be a Great in the Role of Enterprise Architect, by Dana Bredemeyer and Ruth Malan, September 2002. (GreatArchitect.PDF, 883 Kb). <9>
  • Introduction to Software Architecture, by Dana Bredemeyer and Ruth Malan, July 2002. (ArchitectureIntroduction.PDF, 1.2 Mb).
  • Architecture Definitions and Views, March 2001 (Definitions.pdf, 206Kb).
  • Introduction to the Lead/Follow/Get out of the Way tutorial presented at the Enterprise Architectures Conference in Boston, March 2001 (LFGIntro.pdf, 498kb).
  • Software Architecture Action Guide presentation given at the INRUG Training Symposium, April 6, 2000 (Architecture_Action_Guide_Talk.pdf, 179kb).
  • Visual Architecting Process Core Activities (VisualArchitectingProcess_Core.PDF, 191kb). This chart is formatted to be printed on 11x17 paper. <1>
  • Visual Architecting Process Poster (VAPPoster.PDF, 191kb). This poster is formatted to be printed on 11x17 paper. <5>
  • 2 page primer on Software Architecture and the Visual Architecting Process (VAPActionGuide2005.pdf, 57kb). <1>
Architect Competency Framework:
Our Architect Competency Framework is under development. We are sharing these drafts of the framework, and the associated competency elaborations, with you. Please note that these are works-in-progress. We welcome your suggestions for improvement.
In each of the competency elaboration modules below, Level I identifies the knowledge, activities and characteristics needed for an architect to perform well at component scope, Level II at application/system project scope, Level III at product family or portfolio scope, and Level IV at Enterprise scope. We invite your feedback, suggestions and stories.
Visual Architecting Process Guides:
  • ProcessGuide.pdf, 60kb is designed to be printed on unruled index cards. This is the ideal format, as these guides are intended as handy references. This is the format we use for our Architecture Action Guide handouts given to workshop participants.
  • ProcessGuide_8_5x11.pdf has the same content but formatted for 8.5"x11" paper. We have also printed these up on large format paper to use as posters during workshops or for architecture team's work areas.
  • Printing instructions: print pages 1 to 7, then turn paper over and print pages 8 to 14 on the reverse side (so that page 8 is on the reverse side of page 1, page 9 on page 2, etc.)
  • Note: This is just the set of summary Architecture Action Guides for the Architecting Process. The complete set of Architecture Action Guides is given to our workshop participants (see our Training and Services page for more information on our workshops).
Example Software Architecture Action Guides by Ruth Malan and Dana Bredemeyer:
Example Architecture Action Guides for Architecture Teams by Ruth Malan and Dana Bredemeyer:
Use Case Template (use_case.pdf, 23kb) by Derek Coleman (HP)
Restrictions on use: All material that is copyrighted Bredemeyer Consulting and published on this page and other pages of our site, may be downloaded and printed for personal use. If you wish to quote or paraphrase fragments of our work in another publication or web site, please properly acknowledge us as the source, with appropriate reference to the article or web page used. If you wish to republish any of our work, in any medium, you must get written permission from the lead author. Also, any commercial use must be authorized in writing by Bredemeyer Consulting.


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi