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 effects of the business model on object-oriented software development productivity - References
by T. E. Potok and M. A. Vouk

Cited references and notes

  1. The latest newcomer in this arena is the Java language and Web-based software development.
  2. I. Jacobson, M. Ericsson, and A. Jacobson, The Object Advantage: Business Process Reengineering with Object Technology, Addison-Wesley Publishing Co., Wokingham, UK (1994).
  3. J. A. Lewis, S. M. Henry, and D. G. Kafura, "An Empirical Study of the Object-Oriented Paradigm and Software Reuse," Proceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, Phoenix, AZ, October 6-11, 1991, pp. 184-196.
  4. In this experiment, the reuse level may have been as high as 25 percent in some cases.
  5. W. L. Melo, L. C. Briand, and V. R. Basili, Measuring the Impact of Reuse on Quality and Productivity in Object-Oriented Systems, Technical Report CS-TR-3395, Department of Computer Science, University of Maryland, College Park, MD (January 1995).
  6. For high-end productivity gains reuse levels were in the range of 40-50 percent.
  7. B. Henderson-Sellers, "The Economics of Reusing Library Classes," Journal of Object-Oriented Programming 6, No. 4, 43-50 (1993).
  8. D. Schimsky, "Software Reuse: Some Realities," Vitro Technical Journal 10, No. 1, 47-57 (1992).
  9. D. A. Boehm-Davis and L. S. Ross, "Program Design Methodologies and the Software Development Process," International Journal of Man Machine Studies 36, No. 1, 1-19 (1992).
  10. H. Zweben, S. H. Edwards, B. W. Weide, and J. E. Hollingsworth, "The Effects of Layering and Encapsulation on Software Development Cost and Quality," IEEE Transactions on Software Engineering 21, No. 3, 200-208 (1995).
  11. G. Booch, Object-Oriented Design with Applications, The Benjamin/Cummings Publishing Co., Redwood City, CA (1991).
  12. D. deChampeaux, D. Lea, and P. Fauve, Object-Oriented System Development, Addison-Wesley Publishing Co., Reading, MA (1993).
  13. J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modeling and Design, Prentice Hall, Inc., Englewood Cliffs, NJ (1991).
  14. R. Wirfs-Brock, B. Wilkerson, and L. Wiener, Designing Object-Oriented Software, Prentice Hall Inc., Englewood Cliffs, NJ (1990).
  15. D. Coleman, P. Arnold, S. Bodoff, C. Dollin, H. Gilchrist, F. Hayes, and P. Jeremaes, Object-Oriented Development: The Fusion Method, Prentice Hall, Inc., Englewood Cliffs, NJ (1994).
  16. F. Hayes and D. Coleman, "Coherent Models for Object-Oriented Analysis," Proceedings of the Conference on Object-Oriented Programming Systems, Languages and Applications, Phoenix, AZ, October 6-11, 1991, pp. 171-183.
  17. D. E. Monarchi and G. I. Puhr, "A Research Typology for Object-Oriented Analysis and Design," Communications of the ACM 35, No. 9, 35-47 (1992).
  18. B. Henderson-Sellers and J. M. Edwards, BOOK-TWO of Object-Oriented Knowledge: The Working Object, Prentice Hall, Inc., Sydney, Australia (1994).
  19. L. Berlin, "When Objects Collide: Experiences with Reusing Multiple Class Hierarchies," Proceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, Ottawa, Canada, October 21-25, 1990, pp. 181-193.
  20. M. F. Dunn and J. C. Knight, "Software Reuse in an Industrial Setting: A Case Study," Thirteenth International Conference on Software Engineering, Austin, TX, May 13-16, 1991, pp. 381-390.
  21. E. H. Gamma, R. Johnson, and J. Vlissides, "Design Patterns: Abstraction and Reuse of Object Oriented Design," Proceedings of the Seventh European Conference on Object-Oriented Programming (1993).
  22. M. L. Griss, S. S. Adams, B. Howard, B. J. Cox, and A. Goldberg, "The Economics of Software Reuse (Panel)," Proceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, Phoenix, AZ, October 6-11, 1991, pp. 264-270.
  23. W. Wessale, D. Reifer, and D. Weller, "Large Project Experiences with Object Oriented Methods and Reuse," Journal of Systems Software 23, No. 2, 151-161 (November, 1993).
  24. G. A. Hansen, "Simulating Software Development Processes," IEEE Computer 29, No. 1, 73-77 (1996).
  25. T. E. Potok and M. A. Vouk, "Development Productivity for Commercial Software Using Object-Oriented Methods," Proceedings of the 1995 CASCON Conference, Toronto, Canada, October, 1995.
  26. T. E. Potok and M. A. Vouk, Productivity of Object-Oriented Software Development, Technical Report CACC-TR-96/31, Center for Advanced Computing Communications, North Carolina State University, Raleigh, NC (1996).
  27. Data used by permission. The scales appearing on the axes of all graphs, and any product and date-related information, have been altered to provide discretion.
  28. Procedural software development uses structured analysis, design and coding, or similar techniques, to develop and implement a software product.
  29. ISO 9000 is a set of specifications and standards for quality assurance management systems. It was written by representatives from the 91 countries that are members of the International Organization for Standardization (ISO). ISO 9000 certification is granted after successfully passing an external audit against the ISO 9001 Standard, made up of 20 elements that define acceptable quality management systems.
  30. The Malcolm Baldrige National Quality Award recognizes United States companies for business excellence and quality achievement. The criteria are focused on customer satisfaction, continuous improvement, and business results. To be considered for this annual award, a company submits an application that describes its efforts against the criteria. Business and quality experts review the applications to determine the winner.
  31. However, the advent of the World Wide Web has introduced a new category of Web-based applications that require development and release cycles of around three calendar months (one "web year"). This opens some interesting process control issues, some of which we discuss in the paper.
  32. B. W. Boehm, Software Engineering Economics, Prentice Hall, Inc., Englewood Cliffs, NJ (1981).
  33. R. E. Fairley, Software Engineering Concepts, McGraw-Hill, Inc., New York (1985).
  34. It is interesting to note that a "web-year" cycle could be cast as an "iteration" with a very hard iteration deadline.
  35. Note that in "web-year" type development full testing would be enforced at the end of each web-year iteration.
  36. T. E. Potok, Development of a Quantitative Process Model for Object-Oriented Software Development, doctoral thesis, Department of Computer Science, North Carolina State University, Raleigh, NC (1996).
  37. M. A. Vouk, "On the Cost of Mixed Language Programming," ACM SIGPLAN Notices 19, No. 12, 54-60 (1984).
  38. Based on interviews with the workflow owners and on a review of the project documentation.
  39. C. N. Parkinson, Parkinson's Law and Other Studies in Administration, Houghton Mifflin Company, Boston, MA (1957).
  40. G. J. Gutierrez and P. Kouvelis, "Parkinson's Law and Its Implications for Project Management," Management Science 37, No. 8, 990-1001 (August 1991).
  41. D. S. Borger and M. A. Vouk, "Modeling the Behaviour of Large Software Projects," Center for Communications and Signal Processing, Technical Report TR-91/19, North Carolina State University, Raleigh, NC (1991).
  42. As of 1990, over 400 experiments have been performed testing this theory, with over 90 percent supporting it.
  43. E. A. Locke and G. P. Latham, A Theory of Goal Setting and Task Performance, Prentice Hall, Inc., Englewood Cliffs, NJ (1990).
  44. G. P. Latham and H. A. Marshall, "The Effects of Self-Set, Participatively Set and Assigned Goals on the Performance of Government Employees," Personnel Psychology 35, 399-404 (1982).
  45. M. C. Paulk, B. Curtis, M. B. Chrissis, and C. V. Weber, "Capability Maturity Model, Version 1.1," IEEE Software 10, No. 4, 18-27 (July 1993).
  46. A. B. Badiru and P. S. Pulat, Comprehensive Project Management: Integrating Optimization Models, Management Principles, and Computers, Prentice Hall, Inc., Englewood Cliffs, NJ (1995).
  47. One could argue that a triangular or beta distribution may be a good starting representation for the iteration duration. However, there is no evidence that independent unconstrained iteration durations have a specific distribution, so we have opted for the more general uniform distribution.
  48. It is also assumed that the average team size is about ten software professionals.
  49. S. E. Elmaghraby, E. I. Baxter, and M. A. Vouk, "An Approach to the Modeling and Analysis of Software Production Process," International Transactions in Operational Research 2, No. 1, 117-135 (1995).
About IBM | Privacy | Legal | Contact