Departmentalization in software development and maintenance

Exploring the strengths and weaknesses of three alternative bases for systems staff departmentalization suggests the benefits of an organizational form in which maintenance is separate from new system development.

[1]  M A Branch,et al.  Software maintenance management , 1986 .

[2]  Joseph E. Izzo.  The Embattled Fortress: Strategies for Restoring Information Systems Productivity, Joseph E. Izzo. Jossey-Bass Publishers, San Francisco, CA. 155 pages. ISBN: 0-5542-059-1. $NA , 1987 .

[3]  E. Burton Swanson,et al.  Problems in application software maintenance , 1981, CACM.

[4]  J. Daniel Couger,et al.  Motivating and managing computer personnel , 1980 .

[5]  Cynthia Mathis Beath,et al.  Maintaining Information Systems in Organizations , 1989 .

[6]  WeberRon,et al.  Some factors affecting program repair maintenance , 1983 .

[7]  Rajiv D. Banker,et al.  Factors Affecting Software Maintenance Productivity: an Exploratory Studyl , 1987, ICIS.

[8]  Ron Weber,et al.  Some factors affecting program repair maintenance: an empirical study , 1983, CACM.

[9]  E. Burton Swanson,et al.  Characteristics of application software maintenance , 1978, CACM.

[10]  Kathryn M. Bartol,et al.  Turnover among DP personnel: a casual analysis , 1983, CACM.

[11]  Lee L. Gremillion.  Determinants of program repair maintenance requirements , 1984, CACM.

[12]  J BaroudiJack,et al.  Impact of the technological environment on programmer/analyst job outcomes , 1986 .

[13]  James Martin,et al.  Software Maintenance: The Problem and Its Solutions , 1983 .

[14]  D. Campbell.  Reforms as experiments , 1969 .

[15]  Cynthia Mathis Beath,et al.  The demographics of Software Maintenance Management , 1986, ICIS.

[16]  Stu Westin,et al.  Software Maintainability: Perceptions of EDP Professionals , 1988, MIS Q..

[17]  Meir M. Lehman,et al.  A Model of Large Program Development , 1976, IBM Syst. J..

[18]  Jack J. Baroudi.  The impact of role variables on IS personnel work attitudes and intentions , 1985 .

[19]  M. Porter,et al.  How Information Gives You Competitive Advantage , 1985 .

[20]  Paul H. Cheney,et al.  Information Systems Skill Requirements: A Survey , 1980, MIS Q..

[21]  Robert W. Zmud,et al.  Design Alternatives for Organizing Information Systems Activities , 1984, MIS Q..

[22]  Michael J. Ginzberg,et al.  MIS careers—a theoretical perspective , 1988, CACM.

[23]  J. D. Couger,et al.  Maintenance Programming: Improved Productivity Through Motivation , 1985 .

[24]  Jay R. Galbraith.  Designing Complex Organizations , 1973 .

[25]  Kathryn M. Bartol,et al.  Managing Information Systems Personnel: A Reveiw of the Literature and Managerial Implications , 1982, MIS Q..

[26]  F RockartJohn,et al.  An examination of work-related correlates of job satisfaction in programmer/analysts , 1984 .

[27]  E. Burton Swanson,et al.  Organizational Designs for Software Maintenance , 1984, ICIS.

[28]  James C. Wetherbe,et al.  The management of information systems , 1985 .

[29]  Tor Guimaraes,et al.  Managing application program maintenance expenditures , 1983, CACM.

[30]  Cynthia Mathis Beath,et al.  The use of case study data in software management research , 1988, J. Syst. Softw..

[31]  Norman F. Schneidewind,et al.  The State of Software Maintenance , 1987, IEEE Transactions on Software Engineering.

[32]  M.M. Lehman,et al.  Programs, life cycles, and laws of software evolution , 1980, Proceedings of the IEEE.

[33]  R. Gary Bridge.  The Embattled Fortress: Strategies for Restoring Information Systems Productivity , 1988 .

[34]  E. Burton Swanson,et al.  The dimensions of maintenance , 1976, ICSE '76.

[35]  Robert W. Zmud,et al.  Management of Large Software Development Efforts , 1980, MIS Q..

[36]  Theodore C. Willoughby,et al.  Staffing the MIS Function , 1972, CSUR.

[37]  Walt Scacchi,et al.  Understanding Software Maintenance Work , 1987, IEEE Transactions on Software Engineering.