National Academies Press: OpenBook
« Previous: 5 Next Steps
Suggested Citation:"References." National Research Council. 2003. Innovations in Software Engineering for Defense Systems. Washington, DC: The National Academies Press. doi: 10.17226/10809.
×
Page 56
Suggested Citation:"References." National Research Council. 2003. Innovations in Software Engineering for Defense Systems. Washington, DC: The National Academies Press. doi: 10.17226/10809.
×
Page 57
Suggested Citation:"References." National Research Council. 2003. Innovations in Software Engineering for Defense Systems. Washington, DC: The National Academies Press. doi: 10.17226/10809.
×
Page 58
Suggested Citation:"References." National Research Council. 2003. Innovations in Software Engineering for Defense Systems. Washington, DC: The National Academies Press. doi: 10.17226/10809.
×
Page 59
Suggested Citation:"References." National Research Council. 2003. Innovations in Software Engineering for Defense Systems. Washington, DC: The National Academies Press. doi: 10.17226/10809.
×
Page 60

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

References Aerospace Daily 2003 Revenue for defense IT expected to grow 10-12 percent. 206(4):7. Apfelbaum, L., and J. Doyle 1997 Model-based testing. Proceedings of the 10th International Software Quality Week '97. San Francisco, CA: Software Research Institute. Archer, M. 1999 Toolsforsimplifyingproof ofpropertiesoftimed automata: The TAME template, theories, and strategies. Technical report, NRL/MR/5540-99-8359. Washington, DC: Naval Research Laboratory. Avritzer, A., and E.J. Weyuker 1995 The automatic generation of load test suites and the assessment of the resulting software. IEEE Transactions on Software Engineering 21 (9) :705-716. Balk, J., B. Boehm, and B.M. Steece 2002 Disaggregating and calibrating the case tool variable in COCOMO II. IEEE Transactions on Software Engineering 28 (11): 1009- 1022. Bartoussek, W., and D.L. Parnas 1978 Using assertions about traces to write abstract specifications for software modules. In Proceedings of the Second Conference on European Cooperation in Informatics and Information Systems Methodology, pp. 211 -236. Venice, Italy. Boehm, B., C. Abts, A.W. Brown, S. Chulani, B. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece 2000 Soffware Cost Estimation with COCOMO II. Englewood Cliffs, NJ: Prentice Hall. Chulani, S., B. Boehm, C. Abts, J. Balk, A. Windsor Brown, B. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece 2000 Future trends, implications in cost estimation models. Crosstalk, The Journal of Defense Engineering 13 (4) :4-8. 56

REFERENCES 57 Cohen, D.M., S.R. Dalal, A. Kajla, and G.C. Patton 1994 The automatic efficient test generator (AETG) system. Proceedings of the IEEE International Symposium on Soffware Reliability Engineering pp. 303-309. Cohen, D.M., S.R. Dalal, J. Parelius, and G.C. Patton 1996 The combinatorial design approach to automatic test generation. IEEE Soffware 13(5):83-88. Dalal, S.R., and C.L. Mallows 1988 When should one stop testing software? Journal of the American Statistical Association 83 (403): 872-879. Dalal, S.R., and A.A. McIntosh 1994 When to stop testing for large software systems with changing code. IEEE Transactions on Software Engineering20(4):318-323. Dalal, S.R., A. Jain, N. Karunithi, J.M. Leaton, and C.M. Lott 1998 Model-based testing of a highly programmable system. Proceedings of the ISSRE, pp. 174-178. Dalal, S., M. Hamada, P. Matthews, and P. Gardner 1999 Using defect patterns to uncover opportunities for improvement. Proceedings of the International Conference on Applications of Soffware Measurement (ASM), San Jose, CA. Dalal, S.R., Y. Ho, A. Jain, and A. McIntosh 2002 Application Performance Assurance via Post-Production Monitoring. Paper presented at the International Performance and Dependability Symposium, Washington, DC. Faulk, S.R. 1995 Software Requirements: A Tutorial. NRL Report 7775, Washington, DC: Naval Research Laboratory. Ferguson, J. 2001 Crouching dragon, hidden software: Software in DoD weapon systems. IEEE Software 18 (4) :105-107. Garg, S., A. van Moorsel, K. Vaidyanathan, and K.S. Trivedi 1998 A methodology for detection and estimation of software aging. Proceedings of the Ninth International Symposium on Software Reliability Engineering Paderborn, Germany, pp. 282-292. Gross, J., and J. Yellen 1998 Graph Theory and Its Applications. Boca Raton, FL: CRC Press. Harel, D. 2001 From play in scenarios to code: An achievable dream. Computer34(1):53-60. Harel, D., and O. Kupferman 2002 On object systems and behavioral inheritance. IEEE Transactions on Software Engineering 28 (9) :889-903. Heitmeyer, C.L., R.D. Jeffords, and B. Labaw 1996 Automated consistency checking of requirements specifications. ACM Transactions on Software Engineering and Methodology 5 (3) :231 -261.

58 INNOVATIONS IN SOFTWARE ENGINEERING Heitmeyer, C., J. Kirby, B. Lab aw, and R. Bharadwaj 1998 SCR*: A toolset for specifying and analyzing software requirements. Proceedings, Computer-Aided Verification, 10th Annual Conference (CAVES), Vancouver, Canada. Heninger, K. 1980 Specifying software requirements for complex systems: New techniques and their application. IEEE Transactions on Software Engineering SE-6 (1) :2- 13. Hester, S.D., D.L. Parnas, and D.F. Utter 1981 Using documentation as a software design medium. The Bell System Technical Journal 60 (8): 1 941-1977. Holtzman, G.J. 1997 The model checker SPIN. IEEE Transactions on SoftwareEngineering23(5):279- 295. Humphrey, W.S. 1989 Managing the Software Process. Reading, MA: Addison-Wesley. Jeffords, R., and C. Heitmeyer 1998 Automatic generation of state invariants from requirements specifications. Proceedings, 6th International Symposium on the Foundations of Software Engineering (FSE-6), Orlando, FL. Lee, D., and M. Yanakakis 1992 On-line minimization of transition systems. In Proceedings of the 24th Annual ACM Symposium on Theory of Computing pp. 264-274. New York: Association for Computing Machinery. Leonard, E.I., and C.L. Heitmeyer 2003 Program synthesis from formal requirements specifications using APTS, Higher- Order and Symbolic Computation 16(1 -2):62-97. Lithicum, D. 2001 BOB Application Integration: e-Business Enables Your Enterprise. Reading, MA: Addison-Wesley. Luckham, D.C., J.J. Kenney, L.M. Augustin, J. Vera, D. Bryan, and W. Mann 1995 Specification and analysis of system architecture using rapide. IEEE Transactions on SoftwareEngineering4:336-355. Lutz, R.R. 1993 Analyzing software requirement errors in safety-critical, embedded systems. Proceedings of the IEEE International Symposium on Requirements Engineering San Diego, CA. Lyu, M. 1996 Handioook of Software Reliability Engineering, Michael Lyu (ed.). New York: McGraw-Hill. Meyers, S., and S. White 1983 Software Requirements Methodology and Tool Study for A6-E Technology Transfer. Technical report. Bethpage, NY: Grumman Aerospace Corp.

REFERENCES 59 National Research Council 1996 Statistical Software Engineering. Panel on Statistical Methods in Software Engineering, Committee on Applied and Theoretical Statistics.Washington, DC: National Academy Press. 1998 Statistics, Testing and Defense Acquisition: New Approaches and Methodological Improvements. Panel on Statistical Methods for Testing and Evaluating Defense Systems, Committee on National Statistics, Michael L. Cohen, John E. Rolph, and Duane L. Steffoy, eds. Washington, DC: National Academy Press. 2002 Reliability Issues for DoD Systems: Report of a Workshop. Committee on National Statistics. Francisco Samaniego and Michael Cohen, eds. Washington, DC: The National Academies Press. Oshana, R.S. 1999 An automated testing environment to support operational profiles of software intensive systems. Proceedings of the International Soffware Quality Week '99. San Francisco, CA: Software Research Institute. Parnas, D.L., and Y. Wang 1989 The Trace Assertion Method ofModuleInterface Specification. Technical Report 89- 261, Department of Computing and Information Science, Queen's University at Kingston, Kingston, Ontario, Canada. Poore, J.H., and C.J. Trammell 1999 Application of statistical science to testing and evaluating software intensive systems, in Statistics, Testing and Defense Acquisition: Background Papers. Panel on Statistical Methods for Testing and Evaluating Defense Systems, Committee on National Statistics, Michael L. Cohen, John E. Rolph, and Duane L. Steffoy, eds. Washington, DC: National Academy Press. Prowell, S.J., C.J. Trammell, R.C. Linger, and J.H. Poore 1999 Cleanroom Software Engineering: Technology and Process. Reading, MA: Addison Wesley. Raffo, D., and M.I. Kellner 1999 Predicting the impact of potential process changes: A quantitative approach to process modeling. In Elements of Software Process Assessment and Improvement, Khaled El Emam and Nazim H. Madhavji, eds. New York: Wiley. Rapps, S., and E. Weyuker 1985 Selecting software test data using data flow information. IEEE Transactions on Software EngineeringSE-11 (4):367-375. Rosaria, S., and H. Robinson 2000 Applying models in your testing process. Information and Software Technology 42:815-824. Umar, A. 2002 E-Iousiness and Third Generation Distrilouted Systems. St. Louis, MO: Academic Press. 2003 Application Reengineering: Building Welo-Based Applications and Dealing with Legacies. Englewood Cliffs, NJ: Prentice Hall.

60 INNOVATIONS IN SOFTWARE ENGINEERING Vaidyanathan, K., and K.S. Trivedi 1999 A measurement-based model for estimation of resource exhaustion in operational software systems. Proceedings of the Tenth IEEE International Symposium on Software Reliability Engineering Boca Raton, FL, pp. 84-93. Whittaker, J.A., and J.H. Poore 1993 Markov analysis of software specifications. ACM Transactions on Software Engineering and Methodology 2(2) :93-106. Whittaker, J.A., and K. Agrawal 1994 A case study in software reliability measurement. Proceedings of the International Software Quality Week '94, paper 2-A-2, San Francisco, CA. Whittaker, J.A., and Michael G. Thomason 1994 A Markov chain model for statistical software testing. IEEE Transactions on Software Engineering20(10) :812-824. Woodcock, J., and J. Davies 1996 Using A: Specification, Refinement and Proof Englewood Cliffs, NJ: Prentice Hall.

Next: Appendix A: Workshop Agenda and Speakers »
Innovations in Software Engineering for Defense Systems Get This Book
×
Buy Paperback | $47.00 Buy Ebook | $37.99
MyNAP members save 10% online.
Login or Register to save!
Download Free PDF

Recent rough estimates are that the U.S. Department of Defense (DoD) spends at least $38 billion a year on the research, development, testing, and evaluation of new defense systems; approximately 40 percent of that cost-at least $16 billion-is spent on software development and testing. There is widespread understanding within DoD that the effectiveness of software-intensive defense systems is often hampered by low-quality software as well as increased costs and late delivery of software components. Given the costs involved, even relatively incremental improvements to the software development process for defense systems could represent a large savings in funds. And given the importance of producing defense software that will carry out its intended function, relatively small improvements to the quality of defense software systems would be extremely important to identify. DoD software engineers and test and evaluation officials may not be fully aware of a range of available techniques, because of both the recent development of these techniques and their origination from an orientation somewhat removed from software engineering, i.e., from a statistical perspective. The panel's charge therefore was to convene a workshop to identify statistical software engineering techniques that could have applicability to DoD systems in development.

  1. ×

    Welcome to OpenBook!

    You're looking at OpenBook, NAP.edu's online reading room since 1999. Based on feedback from you, our users, we've made some improvements that make it easier than ever to read thousands of publications on our website.

    Do you want to take a quick tour of the OpenBook's features?

    No Thanks Take a Tour »
  2. ×

    Show this book's table of contents, where you can jump to any chapter by name.

    « Back Next »
  3. ×

    ...or use these buttons to go back to the previous chapter or skip to the next one.

    « Back Next »
  4. ×

    Jump up to the previous page or down to the next one. Also, you can type in a page number and press Enter to go directly to that page in the book.

    « Back Next »
  5. ×

    To search the entire text of this book, type in your search term here and press Enter.

    « Back Next »
  6. ×

    Share a link to this book page on your preferred social network or via email.

    « Back Next »
  7. ×

    View our suggested citation for this chapter.

    « Back Next »
  8. ×

    Ready to take your reading offline? Click here to buy this book in print or download it as a free PDF, if available.

    « Back Next »
Stay Connected!