The growing need for a more effective enterprise architecture style is becoming increasingly evident. Critiques from foundational figures like Jay Forrester (“Organizations built by committee, by intuition, and by historical happenstance—often work no better than would an airplane built by the same methods”) and more recently by John Zachman (“The enterprises of today have never been engineered”) are acknowledged, yet more pressing issues—such as cloud migration, building next-generation data platforms, enhancing cybersecurity, modernizing legacy systems, and implementing DevOps practices—often overshadow the problems related to enterprise architecture, especially in the absence of a holistic architectural vision.

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

Conclusion

  • Andre Milchman

摘要

The growing need for a more effective enterprise architecture style is becoming increasingly evident. Critiques from foundational figures like Jay Forrester (“Organizations built by committee, by intuition, and by historical happenstance—often work no better than would an airplane built by the same methods”) and more recently by John Zachman (“The enterprises of today have never been engineered”) are acknowledged, yet more pressing issues—such as cloud migration, building next-generation data platforms, enhancing cybersecurity, modernizing legacy systems, and implementing DevOps practices—often overshadow the problems related to enterprise architecture, especially in the absence of a holistic architectural vision.