Strong Integration Architecture continuity requires constant updates to adapt with Technology, IT trends, economic condition and objectives of the organisation.
Lessons from the past:
- Development and projects must update the Integration Architecture.
- There must be a process for the review and assessment of Integration Architecture.
- Audit by an external consultant on a regular basis.
- Utilise industry standards.
- Peer review must be a minimum assurance mechanism for any change to the Integration Architecture.
- Business and information system strategy must inform Integration Architecture.
- Industry trends must be considered.
- The Integration Architecture must capture both the future state and the current state models.
- Short-term tactical solutions versus long-term strategic solutions must be constantly re-examined.
- “Just enough architecture, just in time”: The Pareto principle must be embedded within the architecture development cycle, creating an understanding for the application of the 80/20 rule and culture.
