|
ABSTRACT
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.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
Banker, R.D., Datar, $.M., and Kemerer, C.F. Factors attecting sofiware maintenence productivity: An exploratory study. In proceedings of the Eighth International Conference on Information Systems (Pittsburgh, Dec. 6-9, 1987), pp. 160-175.
|
| |
2
|
Baroudi, J.J. The impact of role variables on IS personnel work attitudes and intentions. MIS Q. 9, 4 (1985), 341-356.
|
 |
3
|
|
 |
4
|
|
| |
5
|
Bartol, k.m., and martin, D.C. managing informatikon systems personnel: A review of the literature and managerial implications. MIS Q., Special Issue (1982), 49-70.
|
| |
6
|
Belady, L.A., and Lehman, M.M. A model of large program development. IBM Syst. J. 15, 3 (1976), 225-252.
|
| |
7
|
|
| |
8
|
Boehm, B. The economics of software maintenance. Software Maintenance Workshop, Naval Postgraduate School, Monterey, Calif., Dec. 6-8, 1983, in R.S. Arnold (Ed.), Software Maintenance Workshop record, IEEE computer science press. N.Y., 9-37
|
| |
9
|
Campbell, D.T. Reforms as experiments. Am. Psych. 24, 4 (1969), 409-429.
|
| |
10
|
Canning, R.G., Ed. That maintenance 'iceberg'. EDP Analyzer, (Oct. 1972), 1-14.
|
| |
11
|
Canning, R.G., Ed. Easing the software maintenance burden. EDP Analyzer (Aug. 1981), 1-14.
|
| |
12
|
Cheney, P.H., and Lyons, N.R. Information systems skill requirements: A survey. MIS Q. 4, 1 (1980), 35-43,
|
| |
13
|
|
| |
14
|
|
| |
15
|
|
| |
16
|
Frantz, D. BofA's plans for computer don't add up. L.A. Times (Feb. 7, 1988), 1 ff.
|
| |
17
|
|
 |
18
|
|
| |
19
|
Goldstein, D.K., and Rockart, J.F. An examination of work-related correlates of job satisfaction in programmer/analysts. MIS Q. 8, 2 (1984), 103-115.
|
 |
20
|
|
 |
21
|
|
| |
22
|
Haffner, K. Is your computer secure? Bus. Week (Aug. 1, 1988}, 64-72.
|
| |
23
|
|
| |
24
|
|
| |
25
|
Lehman, M.M. Programs, life cycles, and laws of software evolution. In Proceedings of the IEEE. Special Issue on Software Engineering, 68, 9 (Sept. 1980), 1060-1076.
|
| |
26
|
|
 |
27
|
|
 |
28
|
|
| |
29
|
Liu, C.C. A look at software maintenance. Datamation 22, 11 (1976), 51-55.
|
| |
30
|
|
| |
31
|
Mooney, J.W. Organized program maintenance. Datamation 21, 2 (1975), 63-64.
|
| |
32
|
Port, O. The software trap: Automate--Or else. Bus. Week Special Report, (May 9, 1988), 142-154.
|
| |
33
|
Porter, M.E., and Millar, V.E. How information gives you competitive advantage. Harvard Bus. Rev. 63, 4 (1985), 149-160.
|
| |
34
|
Riggs, R. Computer systems maintenance. Datamation 15, 9 (1969), 227,231-2.
|
| |
35
|
|
| |
36
|
Software Maintenance News. Numbers from England, 7 (July 1989), 8.
|
| |
37
|
|
| |
38
|
Swanson, E.B. Organizational designs for software maintenance. In Proceedings of the Fifth International Conference on Information Systems (Tucson, Ariz., Nov. 28-30, 1984}, pp. 63-72.
|
| |
39
|
Swanson, E.B., and Beath, C.M. The demographics of software maintenance management. In proceeding of the seventh international conference on Information Systems (San Diego, Calif., Dec. 15-17, 1986), pp. 313-326.
|
| |
40
|
|
| |
41
|
|
 |
42
|
|
 |
43
|
|
| |
44
|
Yin, R.K. Case Study Research: Design and Methods. Sage, Beverly Hills, Calif., 1984.
|
| |
45
|
Zmud, R.W. Management of large software development efforts. MIS Q. 4, 2 (1980), 45-55.
|
| |
46
|
Zmud, R.W. Design alternatives for organizing information systems activities, MIS Q. 8, 2 (1984), 79-93.
|
| |
47
|
Zvegintzov, N. Immortal software. Datamation (June 15, 1984), 170-180.
|
REVIEW
"Jack P. Gilman, III : Reviewer"
To promote productivity, improved quality, and recognition of the
importance of maintenance, the authors argue that development and
maintenance personnel should be organized into separate work units.
Their justification is the division of labo
more...
|