"Enterprise computing and open systems - what are the distinctions between the two. Open systems are oriented towards an environment where most or all of the computing technology that comprises that environment is based upon standards regardless of the scope of the environment - departmental or organization-wide. Enterprise computing, by contrast, encompasses not only open system concepts but, by virtue of existing environments that must be incorporated as well, a great deal of proprietary interfaces and interoperability mechanisms. In the early 1990s, as both movements were beginning to gain momentum, there was some degree of overlap between open systems and enterprise computing, the amount of which was hindered somewhat by the stage at which enterprise architectures and standards were. It was anticipated that over time, as the enterprise architectures, open standards, and products built on one or both evolved and matured, the gap between the two would narrow and a greater degree of overlap would occur. As it turns out, the two movements have converged..."
"The state of the art in software design is the "enterprise architecture", where separate software components implement data processing (or other application specific-tasks), data storage, and user interface functionality. This approach enables, for example, the replacement of a database engine without changing the software components that process the data and those that support the interaction with the user."
"Architecture discussions frequently focus on technology issues. This paper takes a broader view, and describes the need for an "enterprise architecture" that includes an emphasis on business and information requirements. These higher level issues impact data and technology architectures and decisions... There is not a single correct way to develop an architecture or implement standards for every enterprise; they must be customized to the environment."
"Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures."
"DOD will create a Department-wide blueprint (enterprise architecture) that will prescribe how the Departments financial and non-financial feeder systems and business processes interact. This architecture will guide the development of enterprise-level processes and systems throughout DOD."
"For the IT department [the] change towards commodity products, open standards, end-user decision making and fundamental change in the Business platform, will imply substantial challenges. The role of the IS function will change. The formal IS budget in the US, according to Gartner Group Inc, is 2.4% of revenue in 1990, and will grow to 2.7% in 1995. End-user IT spending is estimated t0 2.4% in 1990, split 50/50 between budget and unseen expenses. This item is assumed to increase to 5.0% in 1995, bringing the total to 7.7% This total amount must be managed, and the rules must be set by the IS manager. Following the rule of "Least resistance", will lead to crisis and complete loss of control. IT resources must be managed. An Enterprise Architecture must be established and adhered to. Standards must be established, and partnerships between IT professionals and end-users formed."
"Enterprise architectures are required to support and maximize the efforts of virtual teams within decentralized organizations. Vendor products exist today to start evolving towards a standards-based multi-vendor architecture. The underlying networking technology, 802.3/Ethemet, is robust and will provide for a cost-effective investment that will last for many years to come. Complimentary LAN technologies are already available to ensure transparent growth of networked systems. Combining human resources with information technology will be the key differentiating factor for successful manufacturing enterprises in the 1990s."