Optimal Software Development: A Control Theoretic Approach
Published Online:1 Sep 2005https://doi.org/10.1287/isre.1050.0059
References
- A new product growth for model consumer durables. Management Sci. (1969) 15(5):215–227Link, Google Scholar
- DIRECTV: Forecasting diffusion of a new technology prior to product launch. Interfaces (2001) 31(3, Part 2 of 2):S82–Link, Google Scholar
- Software Testing Techniques (1990) (International Thomson Computer Press, Boston, MA) Google Scholar
- Concurrent software development. Comm. ACM (2000) 43(11):200–214Google Scholar
- Some experiments with automated aids to the design of large scale reliable software. IEEE Trans. Software Engrg. (1975) 1(1):125–133Crossref, Google Scholar
- A fault threshold policy to manage software development projects. Inform. Systems Res. (2004) 15(1):3–19Link, Google Scholar
- How Microsoft builds software. Comm. ACM (1997) 40(6):53–61Crossref, Google Scholar
- Optimal software release scheduling based on artificial neural networks. Ann. Software Engrg.: Software Reliability, Testing Maturity (1999) 8:167–185Crossref, Google Scholar
- Advances in software inspections. IEEE Trans. Software Engrg. (1986) 12(7):744–751Crossref, Google Scholar
- Application development using modifiable off-the-shelf software. (2003) . Working paper, School of Management, University of Texas at Dallas, Richardson, TXGoogle Scholar
- A time dependent error detection model for software reliability and other performance measures. IEEE Trans. Reliability (1979) 28(3):206–211Crossref, Google Scholar
- Complementing XP with requirements negotiation. Third Internat. Conf. Extreme Programming Agile Processes Software Engrg (2002) Sardinia, ItalyGoogle Scholar
- Optimal timing of reviews in concurrent design for manufacturability. Management Sci. (1995) 41(9):1431–1447Link, Google Scholar
- Software debugging, testing, and verification. IBM Systems J. (2002) 41(1):4–12Crossref, Google Scholar
- Quality improvement and infrastructure activity cost in software development: A longitudinal analysis. Management Sci. (2003) 49(6):784–800Link, Google Scholar
- Quest for quality. Inform. Week (2003) May 26). http:// www.informationweek.com/story/showArticle.jhtml?articleID =101001.51Google Scholar
- Data Collection Procedures for the Software Engineering Laboratory (SEL) Database (1993) (Software Engineering Laboratory (SEL), NASA/Goddard Space Flight Center, MD) Google Scholar
- Optimal release times for software systems with scheduled delivery time based on the HGDM. IEEE Trans. Comput. (1997) 46(2):216–221Crossref, Google Scholar
- Economic analysis of software release problems with warranty cost and reliability requirement. Reliability Engrg. System Safety (1999) 66(1):49–55Crossref, Google Scholar
- Mathematical Handbook for Scientists and Engineers (2000) (Dover Publications Inc., Mineola, NY) Google Scholar
- A dynamic coordination policy for software system construction. IEEE Trans. Software Engrg. (2002) 28(7):684–694Crossref, Google Scholar
- Software Reliability: Principles and Practices (1976) (John Wiley & Sons, New York) Google Scholar
- A software cost model with warranty and risk costs. IEEE Trans. Comput. (1999) 48(1):71–75Crossref, Google Scholar
- Research Triangle Institute (RTI) The economic impacts of inadequate infrastructure for software testing. (2002) . RTI Project 7007.011, National Institute of Standards and Technology, MDGoogle Scholar
- Optimal Control Theory: Applications to Management Science and Economics (2000) 2nd ed.(Kluwer Academic Publishers, Boston, MA) Google Scholar
- Software-reliability growth modeling: Models and applications. IEEE Trans. Software Engrg. (1985) 11(12):1431–1437Crossref, Google Scholar
- Software-reliability growth with a Weibull test-effort, a model & application. IEEE Trans. Reliability (1993) 42(1):100–106Crossref, Google Scholar

