|
|
igniteXML Provides Governance to Previously Hidden Assets:
In a typical enterprise SOA deployment there can be hundreds of XML schema containing hundreds to thousands of hidden and ungoverned components. igniteXML provides governance to these components, ensuring that divergent descriptions of common business data (i.e. customer, address, transaction, etc.) don't become enshrined in code and propagated throughout the entire SOA stack where it is costly to fix. Such errors cause major delay and expense resulting in fragility throughout the entire SOA deployment, cancelling one of the key benefits promised by SOA.
For example, imagine that a new legal requirement requires a change to the definition of "customer," how would you find all the web services that need to change as a result; how would you make sure that all of the changes are exactly the same? Without igniteXML, this undertaking is challenging and costly since the schema are built separate from their underlying business descriptions.
Common and Validated Business Vocabulary:
igniteXML enables business and technology stakeholders to collaborate on the design of components (which describe the business they wish to expose as a service) and to store the components in a global library to be used consistently throughout the SOA. This validated vocabulary makes it dramatically easier and faster to develop schema, assures that the delivered services match the business requirements, supplies greater agility when responding to ongoing changes in the business, and makes possible governance of the schema creation and maintenance process.
Schemas Developed From Reusable Components:
With igniteXML, schema is developed through composition of components rather than handcrafted ad-hoc. Developing via components brings formalism and governance to the schema creation and maintenance processes not possible with any other product. Developing and maintaining by composition ensures that schemas are created correctly the first time and that changes are made in one place, at one time, in one consistent manner throughout the SOA.
Impact Analysis and Change Management:
igniteXML uniquely brings the impact analysis of a change to a business definition to the development process. Where one component change can result in multiple schema changes, by providing a detailed understanding of the breadth and scope of the potential change to developers and architects, igniteXML highlights the total impact of that change. Integrating with downstream tools, igniteXML further enhances their value by enabling them to proactively respond to changes in schema and resulting web services.

|