IBM Skip to main content
  Home     Products & services     Support & downloads     My account  
  Select a country  
Journals Home  
  Systems Journal  
  ·  Current Issue  
  ·  Recent Issues  
  ·  Papers in Progress  
  ·  Search/Index  
  ·  Orders  
  ·  Description  
  ·  Author's Guide  
Journal of Research
and Development
  Staff  
  Contact Us  
Systems Journal  
Volume 36, Number 1, 1997
Application Development
 Table of contents: arrowHTML arrowASCII   This article: arrowHTML arrowASCII
arrowCopyright info
   

The effective use of automated application development tools - References

by P. J. Guinan, J. G. Cooprider, and S. Sawyer

Cited references

  1. F. Brooks, The Mythical Man-Month, Addison-Wesley Publishing Co., Reading, MA (1975).
  2. W. W. Gibbs, "Software's Chronic Crisis," Scientific American 271, No. 3, 72-81 (September 1994).
  3. G. Gladden, "Stop the Lifecycle I Want to Get Off," Software Engineering Notes 7, No. 2, 35-39 (April 1982).
  4. J. Turner, "Observations on the Use of Behavioral Models in Information Systems Research and Practice," Information and Management 5 (1982).
  5. R. Fichman and C. Kemerer, "Adoption of Software Engineering Process Innovation: The Case of Object Orientation," Sloan Management Review 35, No. 2, 7-22 (Winter 1993).
  6. V. J. Mercurio, B. F. Meyers, A. M. Nisbet, and G. Radin, "AD/Cycle Strategy and Architecture," IBM Systems Journal 29, No. 2, 170-188 (1990).
  7. V. Merlyn and J. Parkinson, Development Effectiveness, John Wiley & Sons, Inc., New York (1994).
  8. National Research Council, "The National Research Council of Canada: Research, Programs, and Industrial Partnership," The CASE Center Spring Conference, Syracuse University, NY (April, 1995).
  9. W. S. Humphrey, Managing the Software Process, Addison-Wesley Publishing Co., Reading, MA (1988).
  10. R. Kraut and L. Streeter, "Coordination in Software Development," Communications of the ACM 38, No. 3, 69-81 (March 1995).
  11. D. Reifer, Software Management, IEEE Press, Los Alamitos, CA (1994).
  12. D. Halloran, S. Manchester, and J. Moriarity, "System Development Quality Control," MIS Quarterly 22, No. 4, 1-13 (December 1987).
  13. L. Constantine, "Control of Sequence and Parallelism in Modular Programs," AFIPS Conference Proceedings, Spring Joint Computer Conference 32, Silver Spring, MD (1968), pp. 409-430.
  14. L. Beck and T. Perkins, "A Survey of Software Engineering Practice: Tools, Methods, and Results," IEEE Transactions on Software Engineering SE-9, No. 5, 541-561 (September 1983).
  15. S. Hanson and R. Rosinsti, "Programmer Perceptions of Productivity and Programming Tools," Communications of the ACM 28, No. 2, 180-189 (February 1985).
  16. A. Wasserman, Software Development Environments, IEEE Press, New York (1982).
  17. P. Lempp and R. Lauber, "What Productivity Increases to Expect from a CASE Environment: Results of a User Survey," Proceedings of the 27th Annual Technical Symposium on Productivity: Progress, Prospects and Payoffs, Gaithersburg, MD (June 9, 1988), pp. 13-19.
  18. K. Hayley, H. Lyman, and M. Thaine, "The Realities of CASE," Journal of Information Systems Management 7, No. 3, 18-23 (Summer 1990).
  19. C. Bird, "CASE Crop a Flop," Software Magazine 11, No. 14, 8 (November 1991).
  20. J. Carey and J. Currey, "The Prototyping Conundrum," Datamation 35, No. 11, 29-33 (June 1, 1989).
  21. W. Orlikowski, "Division Among the Ranks: The Social Implications of CASE Tools for Systems Developers," Proceedings of the Tenth International Conference on Information Systems, Boston, MA (1990), pp. 199-210.
  22. D. Burkhard, "The Role of Structured Methodology in the Implementation of Computer-Aided Software Engineering Technology," unpublished manuscript, McIntire School of Commerce, University of Virginia, 1988.
  23. J. Ambrosio, "DuPont Brings CASE Solutions Inside--And Out," Digital Review 6, No. 14, 40-43 (June 26, 1989).
  24. S. Ball, "Successful Implementation of CASE," E. Chikofsky, Editor, Advanced Papers for the First Engineering Workshop on CASE 1, IEEE-CS, Cambridge, MA (1987), pp. 128-138.
  25. Schubert Associates, "Comprehensive Data Summary: Computer-Assisted Software Engineering: Vendor and User Issues in an Emerging Market," Schubert Associates Publication, Boston, MA (1987).
  26. J. Henderson and J. Cooprider, "Dimensions of I/S Planning and Design Aids: A Functional Model of CASE Technology," Information Systems Research 1, No. 3, 227-254 (January 1990).
  27. M. Withey, R. Daft, and W. Cooper, "Measures of Perrow's Work Unit Technology: An Empirical Assessment and a New Scale," Academy of Management Journal 26, No. 1, 45-63 (1983).
  28. J. Hackman, "A Set of Methods for the Research on Work Teams," Research Program on Group Effectiveness, Yale School of Organization and Management, Technical Report #1 (December 1982).
  29. J. Hackman and J. Oldham, Work Redesign, Addison-Wesley Publishing Co., Reading, MA (1976).
  30. J. Henderson and S. Lee, "Managing I/S Design Teams: A Control Theories Perspective," Management Science 38, No. 6, 757-777 (June 1992).
  31. D. Gladstein, "A Normative Model of Task Group Effectiveness," Administrative Science Quarterly 29, No. 10, 499-517 (1984).
  32. P. Guinan, J. Cooprider, and N. Hopkins, "CASE and the Applications Development Cycle: Measuring the Value Added," Proceedings of the International Conference on Information Systems, Dallas, TX (December 1992).
  33. R. Radice, N. Roth, A. O'Hara, Jr., and W. Ciarfella, "A Programming Process Architecture," IBM Systems Journal 24, No. 2, 79-90 (1985).
  34. AD/Cycle Overview, G320-9842, IBM Corporation (November, 1989), available through IBM branch offices.
  35. I. Vessey, S. Jarvanpaa, and N. Tractinsky, "Evaluation of Vendor Products: CASE Tools as Methodology Companions," Communications of the ACM 35, No. 4, 90-105 (April 1992).
  36. I. Vessey and P. Sravanapudi, "CASE Tools as Collaborative Support Technologies," Communications of the ACM 38, No. 1, 83-95 (January 1995).
  37. J. Norman and G. Forte, "Automating the Software Development Process: CASE in the '90s," Communications of the ACM 35, No. 4, 27-32 (April 1992).
  38. K. Frankel, "Toward Automating the Software-Development Cycle," Communications of the ACM 28, No. 6, 578-589 (June 1985).
  39. J. Bryant, "The Problems with CASE," Systems International 18, No. 4, 75-76 (April 1990).
  40. P. Keen, "MIS Research: Reference Disciplines and Cumulative Traditions," Proceedings of the International Conference on Information Systems, Vol. 1, Philadelphia, PA, ACM Press (December 1980), pp. 8-18.
  41. B. Boehm, "Improving Software Productivity," IEEE Computer 18, No. 9, 43-57 (September 1987).
  42. W. Delone and E. McLean, "Information Systems Success: The Quest for the Dependent Variable," Information Systems Research 3, No. 1, 60-95 (March 1992).
  43. D. Garmus, "IFPUG Function Point Counting Practices Manual Release 3.2," Interim Revision, International Function Point Users Group, Westerville, OH (August 1991).
  44. J. Cohen and P. Cohen, Applied Multiple Regression/Correlation for the Behavioral Sciences, Lawrence Earlbaum Associates, Inc., 365 Broadway, Hillsdale, NJ 07642 (1983).
  45. E. Pedhauzer and L. Schmelkin, Measurement, Design and Analysis, Lawrence Earlbaum Associates, Inc., 365 Broadway, Hillsdale, NJ 07642 (1991).
  46. B. Boehm, Software Engineering Economics, Prentice-Hall, Inc., Englewood Cliffs, NJ (1981).
  47. D. Card, F. McGarry, and G. Page, "Evaluating Software Engineering Technologies," IEEE Transactions on Software Engineering SE-13, No. 7, 845-851 (July 1987).
  48. R. Norman and J. Nunamaker, "CASE Productivity Perceptions of Software Engineering Professionals," Communications of the ACM 32, No. 9, 1102-1108 (September 1989).
  49. J. Dutton and A. Thomas, "Relating Technological Change and Learning by Doing," Research on Technological Innovation, Management and Policy 2, 187-224 (1985).
  50. A. F. Case, Jr., "Computer-Aided Software Engineering: Technology for Improving Software Development Productivity," Data Base 17, No. 1, 35-43 (Fall 1985).
  51. T. Percy, "What CASE Can't Do Yet," Computer World 22, No. 25, 59-60 (June 20, 1988).

General references

W. Chung and P. J. Guinan, "Effects of Participative Management on the Performance of Software Development Teams," Proceedings of the ACM Special Interest Group on Computer Personnel Research Conference, Alexandria, VA (March 1994).

P. J. Guinan, "Systems Development Surprise," Computer World (February 12, 1996).

P. J. Guinan, J. Cooprider, and S. Faraj, "Enabling Software Development Team Performance: A Behavioral Versus Technical Approach," Information Systems Research (to be published).

P. J. Guinan, G. N. Hopkins, and J. G. Cooprider, "Automation of the Applications Development Life Cycle: Measuring the Value Added," Proceedings of the International Conference on Information Systems, Dallas, TX (1992).

S. Watts and P. J. Guinan, "Software Development Under Conditions of High Task Complexity and Ambiguity," Proceedings of the 31st Hawaii International Conference on Systems Sciences, Hawaii (January, 1997).