Reuse is missing

 enterprise architecture  1 Response »
Aug 082007
 

JP Rangaswami posted an interesting entry on Build versus Buy versus Opensource.  In it he states:

“And the way I think of it is this:

For common problems use Opensource.
For rare problems use Buy.
For unique problems use Build. ”

Not bad but I really think he missed a fundamental part of this discussion.  Reuse should always come first. Look at what you have in people and their skills  and technology already deployed that could deliver the solution.  I think my post on EA Guiding Principles  better addresses the need for reuse.

Thoughts?

Enterprise Architecture Principles

 enterprise architecture  1 Response »
Jun 202007
 

EA Principles

When deciding on architecture to implement, we will:

1 REUSE before ACQUIRE

2 ACQUIRE before CREATE

3 CREATE REUSABLE COMPONENTS

Definitions

  • ACQUIRE add new components to the architecture either COTS or OS/CS
  • COTS Commercial Off the Shelf / Vendor
  • CREATE add new components to the architecture by creating a new component
  • OS-CS Open Source or Community Source
  • REUSE leverage existing architecture components (cost savings in training, infrastructure,etc)

We use this as our main guiding principle for our Enterprise Architecture.

In Nov 2006, I was in Australia as one of two keynote speakers for the Council of Australian University IT Directors’ Inaugral Enterprise Architecture Symposium. We already adopted the “Buy before Build” principle for large IT investments. On the second day of the Symposium, each university had a few minutes to talk about what they are doing for EA. This principle evolved as a result of all their feedback. It is simple enough for people to remember and adhere to. Anyone have anything similar or even better … or different?

 Newer Entries

Switch to our mobile site