SOA and quality -- joined at the hip

SOA and quality -- joined at the hip

Summary: Borland's release today of its Lifecycle Quality Management (LQM) initiative demonstrates the depth to which quality assurance can be applied to the entire applications design process, but with special emphasis in the requirements phase.After all, quality is not just about the code, it's about quality of process, methodology, and of getting the definitions right about what it is you're actually building early and often.

SHARE:

Borland's release today of its Lifecycle Quality Management (LQM) initiative demonstrates the depth to which quality assurance can be applied to the entire applications design process, but with special emphasis in the requirements phase.

After all, quality is not just about the code, it's about quality of process, methodology, and of getting the definitions right about what it is you're actually building early and often. It's also about quality of team and organization.

And so while this all makes perfect sense -- albeit easier said that done -- for current applications in development, it strikes me that this emphasis on total quality becomes not just essential but absolutely critical as SOA emerges within an organization and reshapes how IT works.

The more independent an application service, the more opportunity for the use of that service in hard-to-predict circumstances. By encouraging innovative use of business application services, you also invite unintended consequences in performance, reliability, and reuse. Best to fully define, build, test, retest, and monitor that service puppy before opening the kennel door to let it run wild.

Also, if IT departments morph into service bureaus inside of enterprises, where they shift from a cost center to a core enabling and differentiating foundation, then their quality of service as a critical business function needs to improve. All the Deming revolution talk of the past 60 years is now making its way into IT. Has to.

So quality with Web services and SOA can make or break the performance and reliability of the component services, may even color the perceptions of IT in general. And therefore quality needs to happen right from the start, not as a late-stage activity, lest the architects and business analysts detect that services cannot be trusted on par with monolithic applications.

A temptation to avoid services would stifle the SOA adoption curve, deter reuse, and slash the SOA ROI. Not the way to distribute SOA broadly.

So while Borland is not speaking too loudly of the SOA implications of its latest releases, it's clear to me -- Borland is targeting SOA quality assurance (as a necessary precursor and ingredient to SOA governance). Becoming the designated best-of-breed overlay for quality assurance in the design time process of SOA services definition and execution, not a bad place to be.

Disclosure: Borland is a sponsor of BriefingsDirect podcasts.

Topic: Enterprise Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

2 comments
Log in or register to join the discussion
  • a great blog

    This is a great blog, i really like the knowledge and information on software that i get to know here.
    eukhost.com
  • SOA and Six Sigma

    I love how you've linked SOA and the quality discipline. It seems to me that one of the drivers of the second wave of Enterprise IT investment was the realization -- through the TQM movement -- that most enterprises were 99%composed of custom business processes -- and that maintaining the quality of those processes was difficult, if not impossible. Remember the core competency rage in the 80s (which really launched the ERP vendors).

    A 4th wave of enterprise IT will be defined by SOA, but I suspect that the business drivers will look a lot like those that drove wave #2...
    jeffpend