Integration Is Hard Except with Dovetail

As business rules become separated from application logic, and companies wrestle with developing agility, the times are reminiscent in a way of the evolution of the Internet, and the early attempts to separate content from medium. The most visible success from this was the development of the blog as a content management system. Once content became writeable by non-tech users, content burgeoned across the Web, with results that hardly need to be described today.

Similarly, as content and data became editable, and then recomposable as in mashups – all of which is happening now – the global network expanded into possibilities that are almost bewildering in their variety.

The allusion to the Web is pertinent here because, as IT tries to chart to best course for its organization’s development, no one can ignore the benefits that have accrued to the global network through the Web 2.0 developments, and the lessons are valuable ones.

Dion Hinchcliffe has made the point that the role of the user is not a great one in SOA, but it’s a crucial one in Web 2.0.

Similarly, IT sees that Enterprise 2.0 is coming, and the value of the knowledge worker on the intranet is a source of prosperity and survival for the company trying to morph itself into customer centricity. Somehow this all needs to be provided for, yet without destroying the legacy systems.

The choices for action are many but the principles are few, and can be tightly stated as this: hedge all bets productively. This is not a glib slogan, this is the underlying path of modern software evolution; no one in the enterprise wants to get locked in with either vendors or code anymore; everyone wants maximum flexibility for future discretionary development.

We have to say that this is an age that could have been made for Dovetail Software. While the companies with legacy Clarify installs seek to evolve beyond proprietary code into more agile configurations, Dovetail CRM slips right into the computing environment, seamlessly replacing and enhancing the Amdocs applications with better and more nimble thin clients.

IT expects multiple benefits per technology choice nowadays, and deploying Dovetail yields a development platform that accommodates open standards and Web services. Furthermore, by virtue of Dovetail’s exclusive use of open standards in development, the system proves to integrate quite straightforwardly with much of the rest of the IT stack.

Integration is one of the major stumbling blocks to progress in enterprise development, and one of the spurs to more agile deployment of resources. But the ways to proceed forward are a challenge. SOA is difficult to implement, and while SOA is not services – services are not the requisite component that makes SOA - nevertheless, services are the most practical and obvious way for companies to evolve their legacy stack into reusable resources.

Enterprise architect Michael Hugos advocates building lightweight, essentially throwaway applications to meet intermediate needs:

”’Should we build our systems fast, or should we build them good?’ The agile answer is to build them fast and good enough for now [...] Advantage goes to companies that develop systems that are ready when the business needs them and don’t cost more than the opportunity is worth.” – Agility Is First and Foremost a Frame of Mind

And while there is increasing commentary around the bottom-up versus the top-down approach to SOA, there is no doubt that governance is the primary key to the way forward.

We’ll spend some time this week looking more closely at these issues and others in the task of developing agility in the modern enterprise.

Published Monday, July 09, 2007 3:25 PM
Filed under , , , , ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments


Tuesday, August 28, 2007 8:56 PM by Michael Hugos

# re: Integration Is Hard Except with Dovetail

Hi, I want to correct a missinterpretation you are expressing here regarding my approach to agile system development. Thank you for mentioning a recent post of mine, "Agility is First and Foremost a Frame of Mind", but I am not advocating lightweight, throwaway applications to meet intermediate needs.

Instead I'm advocating that we should build what I call "robust 80% solutions" in quick iterative steps. We should focus on building simple but industrial strength systems that address the most pressing needs first and that can be built and put into production in 30-90 days. Then additional features can continue to be added to these systems over time as needs arise. This way systems are easier to build, development projects are less risky, and systems deliver real value because they quickly respond to the most important business needs.

I'm saying we should avoid trying to build big and complex systems that attempt to solve all problems all at once because it takes far too long to design and build such systems and they often result in expensive failures. If they ever do get built they often are not very effective because the world will have changed in the 12-36 months it took to build them and they are out of synch with what the business people need at that time.


Thursday, August 30, 2007 3:21 PM by gsherman

# re: Integration Is Hard Except with Dovetail

Michael,

Glad to see your reply, and I agree with your points.

Quoting the Agile Manifesto, we value "Working Software", and "Responding to Change".

Indeed, delivering working software, built using an iterative approach, allows us to deliver real value, deliver it quicker, and be nimble enough to respond to constantly changing business needs.

I don't understand building throwaway applications, and it sounds like we agree on this point.

Thanks for jumping in with your thoughts and clarification.

-Gary

BTW - in case there's any confusion - I am NOT the original poster of this article.

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Submit

About Dovetail Software

.