zAgile CEO: Why you should consider model-driven integration

We're only beginning to address the problem of cloud integration. CEO Sanjiva Nath describes a unique solution derived from the semantic Web

Page 3 of 3

Wikidsmart's model-driven architecture
Wikidsmart's model-driven architecture leverages the power of OWL-based ontologies as a way of formally expressing the metamodel(s) representing a system (such as CRM or software engineering lifecycle software). Because similar models may exist to represent methodologies, processes, and collaboration, multidimensional integration is possible.

The approach helps facilitate a common understanding of the subsystem and provides a consistent method of capturing and sharing information about specific elements in that subsystem. It supports a platform and application-independent method for capturing metadata that allows:

  • Reusability, interoperability and portability of this metadata across applications and systems
  • Richer definition of metadata that includes abstractions and broader usability
  • A better understanding of the elements in the context of the model
  • Reduced maintenance through the lifecycle of applications and systems leveraging this architecture

Wikidsmart's application-specific connectors automatically capture information from each application and submit it to Wikidsmart Context Server for integration with other relevant concepts in Wikidsmart's semantic repository. This repository is based on a deep and rich information model for specific domains. Currently, domains representing CRM, software lifecycle management, help desk, and software configuration management are available. Since Wikidsmart is open source, it is possible to extend its deployment into other verticals and domains, providing the appropriate models are provided to support it.

Wikidsmart Context Server interacts with zAgile's application-specific connectors to provide a common repository of integrated information to the corresponding applications. This, in conjunction with point-to-point connectivity between the tools, provides a rich integrated and interoperable environment across disparate tools.

The value of model-driven integration
Organizations often struggle to answer simple questions, such as:

  • Which stakeholders are being served by a given project release and what are the costs associated with addressing their concerns?
  • What features and requirements are in a given release and what is the test coverage of each?
  • Who are all of our customers, which ones are referenceable, what product versions are installed with each, and what is the recent support activity related to them?
  • What process/methodology was used to implement a project? What exceptions were raised? How was the project outcome measured?

Finding answers to such questions can be difficult or impossible when valuable information remains fragmented and strewn across all manner of data sources. With a model-driven approach, such as that on which Wikidsmart is based, metamodels can be reused and applied in various contexts, providing structured, consistent, and shareable mechanism for data integration across a wide range of applications and platforms.

New Tech Forum provides a means to explore and discuss emerging enterprise technology in unprecedented depth and breadth. The selection is subjective, based on our pick of the technologies we believe to be important and of greatest interest to InfoWorld readers. InfoWorld does not accept marketing collateral for publication and reserves the right to edit all contributed content. Send all enquiries to

This article, "zAgile CEO: Why you should consider model-driven integration," was originally published at For the latest business technology news, follow on Twitter.

| 1 2 3 Page 3