“IT architecture is often assumed to follow business strategy, to align IT with the business's strategic objectives. Increasingly, though, many business strategies depend on specific underlying IT capabilities. To develop a synergy between business strategy and IT architecture, firms must develop organizational competencies in IT architecture. My research has identified four IT architectural stages, each with its own requisite competencies. The "application silo architecture stage" consists of IT architectures of individual applications. The "standardized technology architecture stage" has an enterprise-wide IT architecture that provides efficiencies through technology standardization. The "rationalized data architecture stage" extends the enterprise-wide IT standards to data and processes. And the "modular architecture stage" builds onto enterprise-wide global standards with loosely coupled IT components to preserve the global standards while enabling local differences. Each stage demands different organizational competencies to implement the architecture and prepare the firm to move to the next stage.”

—  Jeanne W. Ross

Jeanne W. Ross (2003) Creating a Strategic IT Architecture Competency: Learning in Stages. MIT Sloan Working Paper No. 4314-03, April 2003. Abstract

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "IT architecture is often assumed to follow business strategy, to align IT with the business's strategic objectives. Inc…" by Jeanne W. Ross?
Jeanne W. Ross photo
Jeanne W. Ross13
American computer scientist 1958

Related quotes

“When software applications became larger and larger, people such as Shaw and Garlan coined the term software architecture. This notion of architecture deals with the key design principles underlying software artefacts. In the 1980s and 1990s, people became aware that the development of information technology (IT) should be done in conjunction with the development of the context in which it was used. This led to the identification of the so-called business/IT alignment problem. Solving the business/IT alignment problem requires enterprises to align human, organizational, informational, and technological aspects of systems. Quite early on, the term architecture was also introduced as a means to further alignment, and thus analyzes and solves business? IT alignment problems, Recently, the awareness emerged that alignment between business an IT is not enough, there are many more aspects in the enterprise in need of alignment. This has led to the use of the term architecture at the enterprise level: enterprise architecture.”

Erik Proper (1967) Dutch computer scientist

Martin Op 't Land, Erik Proper (2009) Enterprise Architecture: Creating Value by Informed Governance. p. 26-27

“The presence of an enterprise reference architecture aids an enterprise in its ability to understand its structure and processes. Similar to a computer architecture, the enterprise architecture is comprised of several views. The enterprise architecture should provide activity, organizational, business rule (information), resource, and process views of an organization.”

Donald H. Liles (1947) American engineer

Joseph Sarkis, Adrien Presley and Donald H. Liles (1995) "The management of technology within an enterprise engineering framework." in: Computers & industrial engineering.

“Many companies are not driving significant business value from the digitized platforms they build as part of their enterprise architecture initiatives. Our 2011 survey of 146 senior IT leaders found that the companies that benefit from their platforms' efforts are consistently relying on four architecture-related practices that encourage organizational learning about the value of enterprise architecture: 1) making IT costs transparent, 2) debating architectural exceptions, 3) performing post-implementation reviews, and 4) making IT investments with enterprise architecture in mind.”

Jeanne W. Ross (1958) American computer scientist

Jeanne W. Ross & Anne Quaadgras (2012) " Enterprise Architecture Is Not Just for Architects http://cisr.mit.edu/blog/documents/2012/09/19/2012_0901_architecturelearning_rossquaadgras.pdf/," Massachusetts Institute of Technology, Vol. XII, No. 9, September 2012

“Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of a company's operation model… The key to effective enterprise architecture is to identify the processes, data, technology, and customer interfaces that take the operating model from vision to reality.”

Jeanne W. Ross (1958) American computer scientist

Source: Enterprise architecture as strategy, 2006, p. 47

“To keep the business from disintegrating, the concept of information systems architecture is becoming less of an option and more of a necessity”

John Zachman (1934) American computer scientist

Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: Jaap Schekkerman (2003) How to Survive in the Jungle of Enterprise Architecture. p. 131

Barry Boehm photo

“If a project has not achieved a system architecture, including its rationale, the project should not proceed to full-scale system development. Specifying the architecture as a deliverable enables its use throughout the development and maintenance process.”

Barry Boehm (1935) American software engineer

Barry Boehm (1995); quoted in: L. Bass, P. Clements, and R. Kazman (1998) Software Architecture in Practice, Addison Wesley Longman. Chapter 2

Grady Booch photo

“The development of the Model Driven Architecture (MDA) standards by the Object Management Group”

Grady Booch (1955) American software engineer

OMG
The Limits of Software

Rem Koolhaas photo

“Noting that architecture can no longer keep up with the world: "The areas of consensus shift unbelievably fast; the bubbles of certainty are constantly exploding. Any architectural project we do takes at least four or five years, so increasingly there is a discrepancy between the acceleration of culture and the continuing slowness of architecture.”

Rem Koolhaas (1944) Dutch architect (b.1944)

interview in Iconey http://www.iconeye.com/index.php?option=com_content&view=article&id=2715:rem-koolhaas--icon-013--june-2004, Icon 013, (June 2004)

“The Generic Enterprise Reference Architecture and Methodology is about those methods, models and tools which are needed to build the integrated enterprise. The architecture is generic because it applies to most, potentially all types of enterprise. The coverage of the framework spans Products, Enterprises, Enterprise Integration and Strategic Enterprise Management, with the emphasis being on the middle two. The proposal for the architecture follows the architecture itself improving the quality of the presentation and of the outcome. De nitions of Generic Enterprise Reference Architecture, Enterprise Engineering/ Integration Methodology, Enterprise Modelling Languages, Enterprise Models, and Enterprise Modules are given. It is proposed how the above could be developed on the basis of previously analysed architectures (and other results too), such as the Purdue Enterprise Reference Architecture, the GRAI Integrated Methodology, CIM-OSA, and TOVIE.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus and Laszlo Nemes (1996) "A framework to define a generic enterprise reference architecture and methodology." Computer Integrated Manufacturing Systems Vol 9 (3) p. 179

Frank Lloyd Wright photo

“The mother art is architecture. Without an architecture of our own we have no soul of our own civilization.”

Frank Lloyd Wright (1867–1959) American architect (1867-1959)

Related topics