A Fault Threshold Policy to Manage Software Development Projects

References

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