This paper presents the findings of an empirical study into two organizations' experiences with the adoption and use of CASE tools over time. Using a grounded theory research approach, the study characterizes the organizations' experiences in terms of processes of incremental or radical organizational change. These findings are used to develop a theoretical framework for conceptualizing the organizational issues around the adoption and use of these tools--issues that have been largely missing from contemporary discussions of CASE tools. The paper thus has important implications for research and practice. Specifically, the framework and findings suggest that in order to account for the experiences and outcomes associated with CASE tools, research- ers should consider the social context of systems development, the intentions and actions of key players, and the implementation process followed by the organization. Similarly, the paper suggests that practitioners will be better able to manage their organizations' experiences with CASE tools if they understand that such implementations involve a process of organizational change over time and not merely the installation of a new technology.

Task dependencies drive the need to coordinate work activities. We describe a technique for using automatically generated archival data to compute coordination requirements, i.e., who must coordinate with whom to get the work done. Analysis of data from a large software development project revealed that coordination requirements were highly volatile, and frequently extended beyond team boundaries. Congruence between coordination requirements and coordination activities shortened development time. Developers, particularly the most productive ones, changed their use of electronic communication media over time, achieving higher congruence. We discuss practical implications of our technique for the design of collaborative and awareness tools. Categories and Subject Descriptors H.5.3 [Information Interfaces and Presentation]: Groups and Organization Interfaces – collaborative computing, computersupported

Much recent research has pointed to the critical role of architecture in the development of a firm’s products, services and technical capabilities. A common theme in these studies is the notion that specific characteristics of a product’s design – for example, the degree of modularity it exhibits – can have a profound effect on among other things, its performance, the flexibility of the process used to produce it, the value captured by its producer, and the potential for value creation at the industry level. Unfortunately, this stream of work has been limited by the lack of appropriate tools, metrics and terminology for characterizing key attributes of a product’s architecture in a robust fashion. As a result, there is little empirical evidence that the constructs emerging in the literature have power in predicting the phenomena with which they are associated. This paper reports data from a research project which seeks to characterize the

This paper describes a methodology for the analysis of product design decompositions. The technique is useful for developing an understanding of the "system engineering " needs which arise because of complex interactions between components of a design. This information can be used to define the product architecture and to organize the development teams. The method involves three steps: 1) decomposition of the system into elements, 2) documentation of the interactions between the elements, and 3) clustering the elements into architectural and team chunks. By using this approach, development teams can better understand the complex interactions within the system, thus simplifying the development process for large and complex projects.

Abstract not found

This paper is a review of research in product development, which we define as the transformation of a market opportunity into a product available for sale. Our review is broad, encompassing work in the academic fields of marketing, operations management, and engineering design. The value of this breadth is in conveying the shape of the entire research landscape. We focus on product development projects within a single firm. We also devote our attention to the development of physical goods, although much of the work we describe applies to products of all kinds. We look inside the “black box ” of product development at the fundamental decisions that are made by intention or default. In doing so, we adopt the perspective of product development as a deliberate business process involving hundreds of decisions, many of which can be usefully supported by knowledge and tools. We contrast this approach to prior reviews of the literature, which tend to examine the importance of environmental and contextual variables, such as market growth rate, the competitive environment, or the level of top-management support.

Scientific and engineering research increasingly involves multidisciplinary collaboration, sometimes across multiple organizations. Technological advances have made such crossboundary projects possible, yet they can carry high coordination costs. This study investigated scientific collaboration across disciplinary and university boundaries to understand the need for coordination in these collaborations and how different levels of coordination predicted success. We conducted a study of 62 scientific collaborations supported by a program of the United States National Science Foundation in 1998 and 1999. Projects with principal investigators (PIs) in more disciplines reported as many positive outcomes as did projects involving fewer disciplines. By contrast, multi-university, rather than multidisciplinary, projects were problematic. Projects with PIs from more universities were significantly less well coordinated and reported fewer positive outcomes than projects with PIs from fewer unive...

Authors with many theoretical and managerial perspectives argue that businesses commercializing technologically complex goods benefit when they collaborate closely with other businesses. Collaboration is viewed as a means for businesses to overcome competency limitations and to achieve the close configuration of components required for complex goods. We predict that collaborative relationships ofen assist businesses to produce complex goods, but that the relationships might also cause problems for the collaborating businesses. We find that firms using development-oriented and marketing-oriented collaborative relationships in the hospital sofhvare systems industry are less likely to shut down than businesses that follow independent approaches when the environment changes gradually, but businesses using collaborative relationships are sometimes susceptible to being acquired by other firms. Following a sudden environmental shock, businesses with collaborative relationships for activities central to the shock became more likely to shut down, while businesses with collaborative relationships for activities outside the focus of the shock became more likely to survive. The study critically evaluates and tests the widely stated but little-tested argument that interfirm collaboration is usually beneficial. The results address the issue of whether organizational choices affect comparative business performance. This paper investigates the survival of businesses that use collaborative relationships with other firms to commercialize complex goods. A growing literature has identified many benefits of interfirm collaboration. Several recent studies argue that businesses that collaborate closely with other organizations in order to develop and market complex goods will be more successful than businesses that operate independently (Jorde and

The identification and management of work dependencies is a fundamental challenge in software development organizations. This paper argues that modularization, the traditional technique intended to reduce interdependencies among components of a system, has serious limitations in the context of software development. We build on the idea of congruence, proposed in our prior work, to examine the relationship between the structure of technical and work dependencies and the impact of dependencies on software development productivity. Our empirical evaluation of the congruence framework showed that when developers’ coordination patterns are congruent with their coordination needs, the resolution time of modification requests was significantly reduced. Furthermore, our analysis highlights the importance of identifying the “right” set of technical dependencies that drive the coordination requirements among software developers. Call and data dependencies appear to have far less impact than logical dependencies. Categories and Subject Descriptors

Abstract not found