A framework for information systems architecture
IBM Systems Journal
Enterprise architecture planning: developing a blueprint for data, applications and technology
Enterprise architecture planning: developing a blueprint for data, applications and technology
The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
First Draft of a Report on the EDVAC
IEEE Annals of the History of Computing
Software architecture based on communicating residential environments
ICSE '81 Proceedings of the 5th international conference on Software engineering
Business Information Analysis and Interaction Technique (BIAIT): Finding the big Payoff Areas
ACM '80 Proceedings of the ACM 1980 annual conference
IT Governance: How Top Performers Manage IT Decision Rights for Superior Results
IT Governance: How Top Performers Manage IT Decision Rights for Superior Results
Business information analysis and integration technique (BIAIT): the new horizon
ACM SIGMIS Database
Business information characterization study
ACM SIGMIS Database
Building and implementing an information architecture
ACM SIGMIS Database
Enterprise Architecting: Critical Problems
HICSS '05 Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 08
System design is an NP-complete problem: Correspondence
Systems Engineering
Simple Architectures for Complex Enterprises (PRO-best Practices) (Best Practices (Microsoft))
Simple Architectures for Complex Enterprises (PRO-best Practices) (Best Practices (Microsoft))
Business systems planning and business Information control study: a comparison
IBM Systems Journal
| Hi-index | 0.00 |
The concept of enterprise architecture arose as technologies emerged which made it possible to interconnect all the information technology within an enterprise. Before these internetworking technologies existed, systems were stovepiped by necessity. Any connection to another system or component had to be specifically designed and developed. However, once internetworking technologies became widely available and economically feasible, suddenly, stovepiped systems were no longer necessitated by the constraints of technology and economy. If anything can connect to everything, then the range of enterprise solutions becomes vast and there arises an overwhelming need to manage that solution space. However, managing this solution space is fraught with challenges arising from wicked problems, complexity and an enterprise learning curve that evolves slower than the technology the enterprise is attempting to manage. This paper attempts to addresses these challenges and suggests enterprise architecture needs and challenges.