Integration principles are used within successful business IT projects. (Re)use the integration principles from the collection below.

Do not hesitate to add your data principles to this list so everyone can benefit. Click here to add your contribution.

Accessible
StatementData is available to the widest range of users for the widest range of purposes.
Rationale
Implications
Tag(s)data, Integration
Documentation
StatementDocumentation
RationaleIt is well documented that documentation is an important characteristic for making software components reusable. Documentation for software is essential for any future use or modification and critical for maintainability. Programmers are unlikely to reuse software that is not well-documented or commented since it makes it harder to understand and maintain. Documentation should be self-contained, adaptable and extensible. Specific documentation for reuse of the component enhances the chances for usage of the component in future.
Implications
Tag(s)design, Integration, Software, Software development
Interoperability
StatementSoftware and hardware should conform to defined standards that promote interoperability for data, applications, and technology.
Rationale(Open) Standards help ensure consistency, thus improving the ability to manage systems and improve user satisfaction, and protect existing IT investments, thus maximizing return on investment and reducing costs. (Open) Standards for interoperability additionally help ensure support from multiple vendors for their products, and facilitate supply chain integration.
Implications(Open) Interoperability standards and industry standards will be followed unless there is a compelling business reason to implement a non-standard solution. A process for setting standards, reviewing and revising them periodically, and granting exceptions must be established. The existing used standards used within IT platforms and applications must be identified and documented.
Tag(s)Integration
Machine processable
StatementData is reasonably structured to allow automated processing.
Rationale
Implications
Tag(s)data, design, Integration
Prefer Real-time Data Exchange
StatementData exchange speed and latency must be based on business need, with a preference for real-time exchange to improve the delivery of services.
Rationale
  • Decisions made based on old data have lower accuracy and may lead to errors and/or inconsistencies.
  • Users/Services expect the most recent data to be available in their work processes.
Implications
  • All changes to data are processed immediately and are distributed to all other IT systems that use the data.
  • Where data capture systems and the authoritative source for data are different, data must be shared with the authoritative source at the speed required by the most timesensitive usage of the data. This includes all data that is encompassed in a given transaction.
  • Data exchange speeds will often be driven by the needs of the most time sensitive usage of the data.
Tag(s)Integration
Primary data
StatementData is as collected at the source, with the highest possible level of granularity, not in aggregate or modified forms.
Rationale
Implications
Tag(s)data, Integration
1 2
Integration Principles