Zachman was one of the pioneers of enterprise IT architecture. His article, "Business Systems Planning and Business Information Control Study: A comparison”, was an early effort to suggest that businesses should think more carefully about how they integrated systems and data. He used the analogy of architecture, since, as Hurley and Tompkins summarise, “each stage in the building of a house requires different levels of detail. At each stage, decisions need to be made about what materials compromise the product, how it will work, where the components are located, who is involved, when tasks need to be completed, and why they are important” (Hurley and Tompkins, 1999:76). This was developed in the early 1990’s by authors like Wiley, who argued that the creation of systems that would allow information to flow freely through an organisation was essential to efficiently working groups (Wylie, 1990). Modern developments of this have come from authors such as Lankhurst, who give the example of the Dutch government’s use of IT architecture to coordinate their tax collection. (Lankhurst et al, 2009). This relates to information management strategy, since it demonstrates the modern day necessity of well managed information. Much of Lankhurst et al’s work develops the blueprint spelled out by Spewak and Hill, who offer practical advice on how companies can create systems that integrate data by using technology (Spewak and Hill, 1993).
While it might be tempting to call enterprise IT architecture another form of IT strategy, this is wrong. IT strategy is one part. As Lawson says, “Many top executives are good at devising strategy but often not so great at making it work” (Lawson 2006). This is the crucial difference: enterprise IT architectu...
... middle of paper ...
... Strategy and Organizational Culture: an Empirical Study of Public Sector Units in India, in The Journal of Strategic Information Systems, vol 10, issue 1, March 2001
Lankhurst, M. et al, 2009, Enterprise Architecture at Work: Modelling, Communication and Analysis, Springer-Verlag Berlin Heidelberg.
Lawson, J., 2006, Delivering on Strategy: Those That Can...Do!! Those Who Simply Talk... Make Another Fine Mess, in Spectra - Journal of the MCA, June 2006
Spewak, S. H. And Hill, S. C., 1993, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, QED Information Sciences, Inc. Wellesley, MA.
Wylie, L., 1990, A Vision of Next Generation MRP II, Scenario S-300-339, Gartner Group
Zachman, J., 1982, Business Systems Planning and Business Information Control Study: A comparison in: IBM Systems Journal, vol 21, no 3, 1982. p.31-53
Lego managers used the same approach they used for their blocks. They created a modularized and standardized architecture for their information systems, making it possible to expand at a faster rate and add capacity and functionality as it was needed (Pearlson, Saunders). They implemented...
This strategy assumes that an articulated business strategy is the driver of both organizational design choices and the design of IT infrastructure. The alignment is said to be the most common and widely understood perspective, as it corresponds to the classic, hierarchical view of strategic management.
...l for enterprise resource planning implementation¡±, Proceedings of the 7th European Conference on Information Systems, Vol. 1, pp. 273-97.
- Williams, L.T, 1997, “Planning and managing the information system - a manager's guide”, Industrial Management & Data Systems Volume 97 Number 5 1997 pp. 187-191
Stair, R. M. (2008) Fundamentals of business information systems, Australia; United Kingdom: Course Technology CENGAGE Learning.
Creswell, J., 2003, A framework for design, 2nd ed., Sage Publications, Thousand Oaks, California, pp. 3-26.
An effective e-business architecture should be built after a careful analysis of the way a company does business, for implementing an appropriate architecture is a way to make businesses overall more efficient. When developing an e-business architecture, a company must first take into consideration its current business structure or how they would like this structure to be if it's a new business, and from that point develop an architecture that will take the business to a next level of organization and management.
Lorsch, J. W. (1987), “Organisation Design: A Situational Perspective”, Academy of Management Review, January Issue, pp. 117 – 132.
Enterprise is a group of people who have a common goal which they try to achieve through recourses e.g. people, money, energy, materials, space, time, etc. ERP covers techniques and concepts employed for the integrated management of business as a whole. The ERP packages are a target of the manufacturing industry. ERP software is designed to model and automate many of the basic processes of a company. It is a mirror image the major business processes of an organization. (Enterprise Resource Planning by Alexis Leon.)
Enterprise Resource Planning (ERP) -. Abstract ERP systems are meant to help companies and businesses operate more efficiently when they are not. The main goal for a company is to choose a vendor that will give them the safest and easiest way to operate efficiently and achieve their business goals. What is an ERP?
Zeleny, M (ed.) 2000, The IEBM handbook of information technology in business, Thomson Learning, London.
Curtis G. & D. Cobham (2002: 4th edition) Business Information Systems: Analysis, Design and Practice. Essex: Pearson Education Limited
META Group considers enterprise architecture as a process as opposed to an object, thereby referring to it as enterprise architecture process. Its enterprise architecture describes the systematic linkages between the enterprise business, technical architectures, information and enterprise solution architecture. It has modified the traditional enterprise architecture in a manner that extends from the level of business strate...
Perry, B., 2005, Organisational Management and Information Systems. [e-book] Oxford; Elsevier. Available at: Google Books . [Accessed 14 November 2013]
Yahia Zare Mehrjerdi, (2010) "Enterprise resource planning: risk and benefit analysis", Business Strategy Series, Vol. 11 Iss: 5, pp.308 – 324.