Coordination in software development
Authors:
Open Access
- 1 March 1995
- journal article
- Published by Association for Computing Machinery (ACM) in Communications of the ACM
- Vol. 38 (3) , 69-81
Abstract
Since its inception, the software industry has been in crisis. As Blazer noted 20 years ago, “[Software] is unreliable, delivered late, unresponsive to change, inefficient, and expensive … and has been for the past 20 years” [4]. In a survey of software contractors and government contract officers, over half of the respondents believed that calendar overruns, cost overruns, code that required in-house modifications before being usable, and code that was difficult to modify were common problems in the software projects they supervised [22]. Even today, problems with software systems are common and highly-publicized occurrences.Keywords
This publication has 9 references indexed in Scilit:
- Designing for cooperation: cooperating in designCommunications of the ACM, 1991
- A field study of the software design process for large systemsCommunications of the ACM, 1988
- No Silver Bullet Essence and Accidents of Software EngineeringComputer, 1987
- The Psychology of Intergroup Attitudes and BehaviorAnnual Review of Psychology, 1985
- ENVIRONMENTAL SCANNING: THE EFFECTS OF TASK COMPLEXITY AND SOURCE ACCESSIBILITY ON INFORMATION GATHERING BEHAVIOR*Decision Sciences, 1983
- Designing for usability---key principles and what designers think1983
- Special Boundary Roles in the Innovation ProcessAdministrative Science Quarterly, 1977
- Software EngineeringIEEE Transactions on Computers, 1976
- Determinants of Coordination Modes within OrganizationsAmerican Sociological Review, 1976