Author Archives: David Hemphill

This blog moved to techintercept.com

Can business owners afford to ignore software?

A long-standing premise for creating software applications is that “the business” should not be concerned with the technology implementation details. However, the end of this era may be near, as evidenced by Marc Andreessen in the article entitled “Why Software Is Eating The World” published in The Wall Street Journal last summer. Established businesses are […]

What Benjamin Franklin can teach an Enterprise Architect: Gaining Consensus

Software architects are horribly ill prepared in the art of seeking consensus. Most of us come up through the technical ranks, spending many of our early years writing code and being as introverted as our jobs allow. At some point in our careers, the curtain is pulled back on this dream like existence as we […]

Out with the Old, In with the New: Replacing existing Software Architecture (Part 3)

Before making a decision to replace an existing system or architecture, it’s critical to understand exactly why the current system is failing to meet business needs. Is it slow? It can’t be maintained? Are new features are hard to add using old technology? Is it crashing a lot? (Note, this is Part 3 in a […]

Out with the Old, In with the New: Replacing existing Software Architecture (Part 2)

Many years, sweat, blood, and tears have gone into the existing system. So how do you go about replacing this Noble Beast? I hear many people talk about “blowing it up and starting over.” However, in my experience this rarely works. (Note, this is Part 2 in a series, View Part 1) On paper, this […]

Out with the Old, In with the New: Replacing existing Software Architecture (Part 1)

Software architectures have a lifespan. The actual lifespan will vary from system to system. But regardless, eventually there will be a current of growing concern over the longevity of the system and if it will scale to support future business. So now you’ve determined it’s time for a fresh start. But what does that mean […]

Don’t Create Lame Ducks: How is your Enterprise Architecture team structured?

A key question when forming an Enterprise Architecture group is where do the people come from? Do you create a group of architects that fly from the hive and sit with their arms folded on each team within your organization as the keeper of standards? Or do you request a delegate from each team in […]

When multiple business units funnel software requests into IT, is it too late for strategy?

A common software development strategy in many corporations is to have a centralized IT group support many business units. In this situation, the IT group acts as a funnel for software requests and thus has visibility across the business units. However, by the time IT sees the software requests it’s often too late for strategic […]

Software Requirements Sign-off: Is it Hurting Your Business?

“Approval authority” sounds like a powerful, “We’re in control” kind of a term. Especially when written into a contract. However, when “approval authority” means signing off on requirements, are you really just relinquishing control and placing blind faith in a software development team? Despite having signed requirements documents, changes are inevitable. The honest truth is […]

Is Packaged Software too Complex?

A friend of mine worked at a bike shop that gave a spoke wrench away to every customer. When he asked why, the store manager replied, “Because they’ll eventually use it and get their wheels so far out of alignment that they’ll need to pay us to straighten them out.” When chosen well, packaged software […]