Architecture in the large papers

Monitoring Platform Emergence: Guidelines from Software Networks   
with Chi-Hyon Lee, N. Venkatraman and Dan Vesset

Changing architecture of Global Work with Venkatraman

Competing in the Era of Emergent Architecture: The Case of the
Packaged Software Industry with Chi-Hyon Lee and David Dreyfus

Networks of Software, 1990-2002: Do Web of Links Contribute to  
Sales?, with N. Venkatraman and Chi-Hyon Lee

Managing in a “Small World Ecosystem”: Some Lessons from the
Software Sector, with N. Venkatraman and Chi-Hyon Lee

Is Linux Ready for Prime Time? with N. Venkatraman, Chi-Hyon
Leeand Dan Vesset

Dual Networks of Knowledge Flows: An Empirical Test of
Complementarity in Software Ecosystems with David Dreyfus, Chi-
Hyon Lee and N. Venkatraman

Is ambidexterity a valuable organizational capability? A test in software
product introductions,” with N. Venkatraman and Chi-Hyon Lee

Knowledge Sharing and Value Flow in the Software Industry:
Searching the Patent Citation Network," with David Dreyfus, HICSS-38,
Maui, Hawaii, 2005.

Make way for the penguin? Explaining commitment to Linux by
software companies.” with Chi-Hyon Lee and N. Venkatraman
(presented at Academy of Management Meeting, 2004).
To improve IT project success, the IS architecture that managers need
to understand is emergent – the result of implementing IT projects in
organizations. Firms conduct planning sessions to create a vision of
their desired architecture that we call designed architecture. This
designed architecture serves to establish a common vision across the
professional IT community. However, every project results in the
creation of new dependencies or elimination of prior dependencies for
example, between systems, databases and platforms. As a result of
implementing these projects, companies create a gap between the
designed architecture vision and the emergent architecture in use.
This gap prevents companies from capturing the expected value from
their IS systems. Studying these dependencies holds the key to
understanding and managing the gap.

Traditional approaches to IT architecture have been focused on
identifying the components of architecture and the design rules that
govern their conceptualization, creation and delivery. The
dependences that exist between components are largely ignored. In
this work, we focus on the dependencies and, in particular, how the
dependencies between the components and organizational
interdependencies co-evolve. We use research from social networks
and modularity theory as a useful abstraction for architecture
representation and analysis.

Enterprise architecture papers:

Partnerships between Software Firms: Is There Value from
Complementarities? with Lucia Gao

Design Architecture, Developer Networks, and Performance of Open
Source Software Projects with Michelle Liu

Managing Architecture Under Emergence: A Conceptual Model and
Simulation with David Dreyfus

The Co-Evolution of Design and User Requirements in Knowledge
Management Systems: The Case of Patent Management Systems with
Tony Briggs and Paul Carlile

ECAR: A Repository for Storing, Retrieving and Analyzing Emergent
Component Architecture with David Dreyfus

Architecture and the search for control under emergence with David

Process Coordination Requirements: Implications for the Design of
Knowledge Management Systems with G. Shankar and George Wyner

A network-based view of enterprise architecture with David Dreyfus
and Per Gyllstrom

Architecture in Design Science: The Case of Stacks with David Dreyfus

Architectural control and emergent architecture: a network perspective,
with David Dreyfus (an earlier version titled "Enterprise Architecture: A
Social Network Perspective,” was published in HICSS 2006).

Managerial Action in a Stacked Landscape with David Dreyfus

Using Software Stacks to Explain Complementarities: The Case of
Mergers and Acquisitions in the Software Industry, with Lucia Silva

The Impact of Design Moves on Platform Adoption: The Case of
Microsoft Windows OS, with Michelle Liu and Chi-Hyon Lee

The Four-Domain Architecture: An approach to support enterprise
architecture design , with Richard Gottlieb