A fault threshold policy to manage software development projects

Information Systems Research

Volumn 15, Issue 1, 2004, Pages

  Robert Chiang, I ^a   Mookerjee, Vijay S ^b  

^a UNIVERSITY OF CONNECTICUT   (United States)

^b UNIVERSITY OF TEXAS AT DALLAS   (United States)

Author keywords

Incremental development; Quality driven integration policy; Software project management; Team coordination

Indexed keywords

COMPUTATIONAL COMPLEXITY; COMPUTER SIMULATION; FUNCTION EVALUATION; INTEGRATION; PROBABILITY; PRODUCTIVITY; PUBLIC POLICY; SOFTWARE ENGINEERING;

INCREMENTAL DEVELOPMENT; QUALITY-DRIVEN INTEGRATION POLICY; SOFTWARE PROJECT MANAGEMENT; TEAM COORDINATION;

PROJECT MANAGEMENT;

EID: 2442637714     PISSN: 10477047     EISSN: None     Source Type: Journal    
DOI: 10.1287/isre.1040.0012     Document Type: Review

References (49)

1. Ammann, P. E., S. S. Brilliant, J. C. Knight. 1994. The effect of imperfect error detection on reliability assessment via life testing. IEEE Trans. Software Engrg. 20(2) 142-148.
2. Banker, R. D., G. B. Davis, S. A. Slaughter. 1998. Software development practices, software complexity, and software maintenance performance: A field study. Management Sci. 44(4) 433-450.
3. Barki, H., S. Rivard, J. Talbot. 2001. An integrative contingency model of software project risk management. J. Management Inform. Systems 17(4) 37-69.
4. Basili, R. V., A. J. Turner. 1975. Iterative enhancement: A practical technique for software development. IEEE Trans. Software Engrg. SE-1(4) 390-396.
5. Blackburn, J. D., G. D. Scudder, L. N. Van Wassenhove. 1996. Improving speed and productivity of software development: A global survey of software developers. IEEE Trans. Software Engrg. 22(12) 875-884.
6. Boehm, B. W. 1988. A spiral model of software development and enhancement. IEEE Comput. (May) 61-72.
7. Briand, L. C., V. R. Basili, C. J. Hetmanski. 1993. Developing interpretable models with optimized set reduction for identifying high-risk software components. IEEE Trans. Software Engrg. 19(11) 1028-1044.
8. Brooks, F. P. 1995. The Mythical Man-Month: Essays on Software Engineering, anniv. ed. Addison-Wesley, Reading, MA.
9. Crowston, K., E. Kammerer. 1998. Coordination and collective mind in software requirements development. IBM Systems J. 37 227-245.
10. Cusumano, M., R. Selby. 1995. Microsoft Secrets. Free Press, New York.
11. Dalai, S. R., A. A. McIntosh. 1994. When to stop testing for large software systems with changing code. IEEE Trans. Software Engrg. 20(4) 318-323.
12. Ehrlich, W., B. Prasanna, J. Stampfel, F. Wu. 1993. Determining the cost of a stop-test decision. IEEE Software (March) 33-42.
13. Fagan, M. E. 1986. Advances in software inspections. IEEE Trans. Software Engrg. 12(7) 744-751.
14. Faraj, S., L. Sproull. 2000. Coordinating expertise in software development teams. Management Sci. 46(12) 1554-1568.
15. Gaimon, C. 1997. Planning information technology-knowledge worker systems. Management Sci. 43(9) 1308-1328.
16. Gilb, T. 1988. Principles of Software Engineering Management. Addison-Wesley, Reading, MA.
17. Goel, A. L. 1985. Software reliability models: Assumptions, limitations, and applicability. IEEE Trans. Software Engrg. 11(12) 1411-1423.
18. Johar, H. V. 1997. SoftCord: An intelligent agent for coordination in software development projects. Decision Support Systems 20(1) 65-81.
19. Jones, C., W. S. Hesterly, S. P. Borgatti. 1997. A general theory of network governance: Exchange conditions and social mechanisms. Acad. Management Rev. 22(4) 911-945.
20. Keil, M., J. Mann, A. Rai. 2000. Why software projects escalate: An empirical analysis and test of four theoretical models. MIS Quart. 24(4) 601-630.
21. Khoshgoftaar, T. M., E. B. Allen, K. S. Kalaichelvan, N. Goel. 1996. Early quality prediction: A case study in telecommunications. IEEE Software 13(1) 65-71.
22. Koushik, M., V. Mookerjee. 1995. Modeling coordination in software construction: An analytical approach. Inform. Systems Res. 6(3) 220-254.
23. Kraut, R., L. Streeter. 1995. Coordination in software development. Comm. ACM 38 69-81.
24. Kuwana, E., E. Yana, Y. Sakamoto, Y. Nakamura, K. Horikawa. 1996. Computer-supported meeting environment for collaborative software development. Inform. Software Tech. 38(3) 221-228.
25. Leveque, L., J. Wilson, D. Wholey. 2001. Cognitive divergence and shared mental models in software development project teams. J. Organ. Behavior 22 135-144.
26. March, J., H. Simon. 1958. Organizations. John Wiley & Sons, New York.
27. McConnell, S. 1996. Daily build and smoke test. IEEE Software 13(4) 144.
28. Morisio, M., D. Romano, C. Mosio. 1999. Framework based software development: Investigating the learning effect. 6th IEEE Internat. Sympos. Software Metrics, Boca Raton, FL, 260-268.
29. Musa, J. D. 1975. A theory of software reliability and its application. IEEE Trans. Software Engrg. 1(9) 312-327.
30. NASA. 1992. Recommended approach to software development, rev. 3. Technical Report SEL-81-305, NASA, Goddard Space Flight Center, Greenbelt, MD.
31. Nidumolu, S. 1995. The effect of coordination and uncertainty on software project performance: Residual performance risk as an intervening variable. Inform. Systems Res. 6(3) 191-219.
32. Paulk, M., B. Curtis, M. B. Chrissis, C. V. Weber. 1993. Capability maturity model for software, ver. 1.1. Technical Report CMU/SEI-93-TR-024, Software Engineering Institute, CMU, Pittsburgh, PA.
33. Prahalad, C. K., M. S. Krishnan. 1999. The new meaning of quality in the information age. Harvard Bus. Rev. 77(5) 109-118.
34. Pressman, R. S. 2001. Software Engineering: A Practitioner's Approach, 5th ed. McGraw-Hill, New York.
35. Radding, A. 2002. Agile programming systems. Computerworld (Feb. 4) http://www.computerworld.com/.
36. Ravichandran, T., A. Rai. 2000. Quality management in systems development: An organizational system perspective. MIS Quart. 24(3) 381-416.
37. Robillard, P. N. 1999. The role of knowledge in software development. Comm. ACM 42(1) 87-93.
38. Seaman, C. B., V. R. Basili. 1998. Communication and organization: An empirical study of discussion in inspection meetings. IEEE Trans. Software Engrg. 24(7) 559-572.
39. Singpurwalla, N. 1991. Determining an optimal time interval for testing and debugging software. IEEE Trans. Software Engrg. 17(4) 313-319.
40. Standish Group International. 1999. CHAOS: A Recipe for Success. http://www.standishgroup.com/sample_research/index.php.
41. Standish Group International. 2001. Extreme Chaos, http://www. standishgroup.com/sample_research/index.php.
42. Tamai, T. 1992. Experiment on coordination within software development teams. Inform. Software Tech. 34(7) 437-442.
43. Teasley, S. D., L. A. Covi, M. S. Krishnan, J. S. Olson. 2002. Rapid software development through team collocation. IEEE Trans. Software Engrg. 28(7) 671-683.
44. Thompson, J. 1967. Organizations in Action. McGraw-Hill, New York.
45. van Genuchten, M. 1991. Why is software late? An empirical study of reasons for delay in software development. IEEE Trans. Software Engrg. 17(6) 582-590.
46. Wood, A. 1996. Predicting software reliability. IEEE Comput. 29(11) 69-77.
47. Xia, G., P. Zeephongsekul, S. Kumar. 1993. Optimal software release policy with a learning factor for imperfect debugging. Micro-electronic Reliability 33(1) 81-86.
48. Yamada, S., S. Osaki. 1985. Software reliability growth modeling: Models and applications. IEEE Trans. Software Engrg. 11(12) 1431-1437.
49. Zhuge, H. 2002. Knowledge flow management for distributed team software development. Knowledge-Based Systems 15(8) 465-471.