[bib36entry02] 1989. “"The Dynamics of Software Project Staffing: A System Dynamics Based Simulation Approach."” IEEE Transactions on Software Engineering , no. 2 (2): 109–19.
[bib36entry03] 2001. Swebok: Guide to the Software Engineering Body of Knowledge: Trial Version 1.00-May 2001. Los Alamitos, CA: IEEE Computer Society Press.
et al.[bib36entry05] 1989. “"Software Inspections: An Effective Verification Process."” IEEE Software, May/June 1989, 31–36.
, , and .[bib36entry06] 2001. Conceptual Block-busting: A Guide to Better Ideas, 4th ed. Cambridge, MA: Perseus Publishing.
[bib36entry09] 1979. “"Measuring Application Development Productivity." Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, October 1979”: 83–92.
[bib36entry12] The Ethics of Aristotle: The Nicomachean Ethics. Trans. by J.A.K. Thomson. Rev. by Hugh Tredennick. Harmondsworth, Middlesex, England: Penguin, 1976.
[bib36entry13] 1989. “"A Structured Approach to Program Optimization."” IEEE Transactions on Software Engineering , no. 2 (2): 101–8.
[bib36entry14] “James Gosling, and David Holmes”. 2000. The Java Programming Language, 3d ed. Boston, MA: Addison- Wesley.
,[bib36entry15] 1988. Software Evolution: The Software Maintenance Challenge. New York, NY: John Wiley & Sons.
[bib36entry16] 1979. “"Augustine's Laws and Major System Development Programs."” Defense Systems Management Review: 50–76.
[bib36entry18] 1973. “"The Programmer as Navigator." Turing Award Lecture”. Communications of the ACM , no. 11 (11): 653.
[bib36entry19] 1990. Human Factors and Typography for More Readable Programs. Reading, MA: Addison-Wesley.
, and .[bib36entry20] 1964. “"Research Studies of Programmers and Programming."” Unpublished studies reported in Boehm 1981.
[bib36entry23] 1974. Myths, Models, and Paradigms: A Comparative Study in Science and Religion. New York, NY: Harper & Row.
[bib36entry25] 1984. “"Software Errors and Complexity: An Empirical Investigation."” Communications of the ACM , no. 1 (1): 42–52.
, and[bib36entry26] 1975. “"Iterative Enhancement: A Practical Technique for Software Development."” IEEE Transactions on Software Engineering , no. 4 (4): 390–96.
, and .[bib36entry27] 1984. “"A Methodology for Collecting Valid Software Engineering Data."” IEEE Transactions on Software Engineering , no. 6 (6): 728–38.
, and .[bib36entry28] 1987. “"Comparing the Effectiveness of Software Testing Strategies."” IEEE Transactions on Software Engineering , no. 12 (12): 1278–96.
, and .[bib36entry29] 2002. “"Lessons learned from 25 years of process improvement: The Rise and Fall of the NASA Software Engineering Laboratory," Proceedings of the 24th International Conference on Software Engineering”, Orlando, FL.
, et al.[bib36entry30] 1986. “"Experimentation in Software Engineering."” IEEE Transactions on Software Engineering , no. 7 (7): 733–43.
, , and .[bib36entry31] 1996. “"A Validation of Object-Oriented Design Metrics as Quality Indicators,"” IEEE Transactions on Software Engineering, October 1996, 751–761.
, and[bib36entry32] 2003. Software Architecture in Practice, 2d ed. Boston, MA: Addison-Wesley.
, Paul Clements, and Rick Kazman.[bib36entry33] 1987. “"The Effect of Data Structures on the Logical Complexity of Programs."” Communications of the ACM , no. 3 (3): 250–59.
, and Sitharama Iyengar.[bib36entry38] 1983. “"A Survey of Software Engineering Practice: Tools, Methods, and Results."” IEEE Transactions on Software Engineering , no. 5 (5): 541–61.
, and .[bib36entry40] 1986. “"Literate Programming."” Communications of the ACM 29, no. 5 (5): 364–69.
, and Donald Knuth.[bib36entry41] 1986. “"A Literate Program."” Communications of the ACM , no. 5 (5): 471–83.
, Donald Knuth, and Doug McIlroy.[bib36entry44] 1991. “"Software Exploratorium: Writing Efficient C Programs."” Unix Review , no. 8 (8): 62–73.
[bib36entry46] 2003. Software Configuration Management Patterns: Effective Teamwork, Practical Integration. Boston, MA: Addison-Wesley.
and Brad Appleton.[bib36entry47] 1985. “"A Style Analysis of C Programs."” Communications of the ACM , no. 1 (1): 80–88.
, and B. A. E. Meekings.[bib36entry48] 1984. “"Elements of Software Configuration Management."” IEEE Transactions on Software Engineering , no. 1 (1): 79–87.
[bib36entry49] 1991. “"Impacts of Life Cycle Models on Software Configuration Management."” Communications of the ACM , no. 8 (8): 104–18.
, and .[bib36entry50] 1980. Software Configuration Management. Englewood Cliffs, NJ: Prentice Hall.
, et al.[bib36entry51] 1985. A Practical Handbook for Software Development. Cambridge, England: Cambridge University Press.
, and M. A. Ould.[bib36entry55] 1989. “"A Software Environment: Some Surprising Empirical Results." Proceedings of the Fourteenth Annual Software Engineering Workshop, November 29, 1989”. Greenbelt, MD: Goddard Space Flight Center. Document SEL-89-007.
[bib36entry57] 2004. Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley.
and Richard Turner.[bib36entry59] 1984. “"Software Engineering Economics."” IEEE Transactions on Software Engineering , no. 1 (1): 4–21.
[bib36entry61] 1987b. “"Industrial Software Metrics Top 10 List."” IEEE Software , no. 9 (9): 84–85.
[bib36entry62] 1988. “"A Spiral Model of Software Development and Enhancement."” Computer, May, 61–72.
[bib36entry63] 1988. “"Understanding and Controlling Software Costs."” IEEE Transactions on Software Engineering , no. 10 (10): 1462–77.
, and .[bib36entry64] Boehm,BarryW., ed. 1989. Tutorial: Software Risk Management. Washington, DC: IEEE Computer Society Press.
[bib36entry66] 1984. “"A Software Development Environment for Improving Productivity."” Computer, June, 30–44.
, et al.[bib36entry67] 1984. “"Prototyping Versus Specifying: A Multiproject Experiment."” IEEE Transactions on Software Engineering , no. 3 (3): 290–303. Also in Jones 1986b.
, and[bib36entry69] 2000b. “"Unifying Software Engineering and Systems Engineering,"” IEEE Computer, March 2000, 114–116.
[bib36entry70] 1987. “"Program Design Languages: How Much Detail Should They Include?"” International Journal of Man-Machine Studies , no. 4: 337–47.
, Sylvia Sheppard, and John Bailey.[bib36entry71] 1966. “"Flow Diagrams, Turing Machines and Languages with Only Two Formation Rules."” Communications of the ACM , no. 5 (5): 366–71.
and[bib36entry73] 1994. Object Oriented Analysis and Design with Applications, 2d ed. Boston, MA: Addison-Wesley.
[bib36entry74] 1997. Inner Loops : A Sourcebook for Fast 32-bit Software Development. Boston, MA: Addison-Wesley.
[bib36entry75] 1991. “"A Taxonomy of Programmers."” ACM SIGSOFT Software Engineering Notes , no. 4 (4): 23–30.
[bib36entry77] 1980. “"Validation, Verification, and Testing for the Individual Programmer."” Computer, December, 24–30.
, , and[bib36entry78] 1990. Writing Better Computer User Documentation: From Paper to Hypertext: Version 2.0. New York, NY: John Wiley & Sons.
.[bib36entry79] 1987. “"No Silver Bullets—Essence and Accidents of Software Engineering."” Computer, April, 10–19.
[bib36entry80] 1995. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2d ed.). Reading, MA: Addison-Wesley.
[bib36entry81] 1977. “"Towards a Theory of the Cognitive Processes in Computer Programming."” International Journal of Man-Machine Studies :737–51.
[bib36entry82] Douglas. 1981. “"Software Technology Payoff—Some Statistical Evidence."” The Journal of Systems and Software :3–9.
[bib36entry84] 1996. Pattern-Oriented Software Architecture, Volume 1: A System of Patterns. New York, NY: John Wiley & Sons.
, et al.[bib36entry85] 1989. “"The Jet Propulsion Laboratory's Experience with Formal Inspections." Proceedings of the Fourteenth Annual Software Engineering Workshop, November 29, 1989”. Greenbelt, MD: Goddard Space Flight Center. Document SEL-89-007.
, and John Kelly.[bib36entry86] 1975. “"PDL—A Tool for Software Design." AFIPS Proceedings of the 1975 National Computer Conference 44”. Montvale, NJ: AFIPS Press, 271–76.
, and[bib36entry87] 1987. “"A Software Technology Evaluation Program."” Information and Software Technology , no. 6 (6): 291–300.
[bib36entry88] 1987. “"Evaluating Software Engineering Technologies."” IEEE Transactions on Software Engineering , no. 7 (7): 845–51.
, , and .[bib36entry89] 1986. “"An Empirical Study of Software Design Practices."” IEEE Transactions on Software Engineering , no. 2 (2): 264–71.
, , and .[bib36entry91] 1985. “"Criteria for Software Modularization." Proceedings of the 8th International Conference on Software Engineering”. Washington, DC: IEEE Computer Society Press, 372–77.
, and[bib36entry94] Lawrence. 1973. “"A Linguistic Contribution of GOTO-less Programming,"” Datamation, December 1973.
[bib36entry95] Clements,Paul, ed. 2003. Documenting Software Architectures: Views and Beyond. Boston, MA: Addison-Wesley.
[bib36entry96] 2002. Evaluating Software Architectures: Methods and Case Studies. Boston, MA: Addison-Wesley.
, and[bib36entry97] 1991. Object-Oriented Design. Englewood Cliffs, NJ: Yourdon Press.
, and Edward Yourdon.[bib36entry98] 1990. “"Engineering Software Under Statistical Quality Control."” IEEE Software , no. 6 (6): 45–54.
, and .[bib36entry101] 1989. “"Evaluating the Effectiveness of Reliability Assurance Techniques."” Journal of Systems and Software , no. 3 (March).
, and[bib36entry102] 1981. “"Principles of Program Design Induced from Experience with Small Public Programs."” IEEE Transactions on Software Engineering , no. 2 (2): 169–74.
[bib36entry103] 1990a. “"Comments on ‘On Criteria for Module Interfaces.’"” IEEE Transactions on Software Engineering , no. 12 (12): 1440.
[bib36entry104] 1990b. “"Objects, Functions, and Program Extensibility."” Computer Language, January, 34–56.
[bib36entry105] 1986. Software Engineering Metrics and Models. Menlo Park, CA: Benjamin/ Cummings.
, and[bib36entry107] 1993. “"Swords and Plowshares: The Rework Cycles of Defense and Commercial Software Development Projects,"” American Programmer, May 1993, 41–51.
and .[bib36entry108] 1991. “"On Building Systems That Will Fail."” 1991 Turing Award Lecture. Communications of the ACM , no. 9 (9): 72–81.
[bib36entry109] 2002. Programming VB .NET: A Guide for Experienced Programmers, Berkeley, CA: Apress.
and[bib36entry110] 1991. Private communication. CSTB 1990. “"Scaling Up: A Research Agenda for Software Engineering."” Excerpts from a report by the Computer Science and Technology Board. Communications of the ACM , no. 3 (3): 281–93.
[bib36entry111] Curtis,Bill, ed. 1985. Tutorial: Human Factors in Software Development. Los Angeles, CA: IEEE Computer Society Press.
[bib36entry112] 1986. “"Software Psychology: The Need for an Interdisciplinary Program."” Proceedings of the IEEE , no. 8: 1092–1106.
, et al.[bib36entry113] 1989. “"Experimentation of Software Documentation Formats."” Journal of Systems and Software , no. 2 (2): 167–207.
, et al.[bib36entry114] 1988. “"A Field Study of the Software Design Process for Large Systems."” Communications of the ACM , no. 11 (11): 1268–87.
, and[bib36entry115] 1981. “"Substantiating Programmer Variability."” Proceedings of the IEEE , no. 7: 846.
[bib36entry117] 2003. “"Software Development Worldwide: The State of the Practice,"” IEEE Software, November/ December 2003, 28–34.
, et al.[bib36entry120] 1992. “"Subprogram Inlining: A Study of Its Effects on Program Execution Time."” IEEE Transactions on Software Engineering , no. 2 (2): 89–102.
, and .[bib36entry121] 1972. “"Fidelity in Mathematical Discourse: Is One and One Really Two?"” American Mathematical Monthly, March, 252–63.
[bib36entry122] 1990. Wicked Problems, Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms. Englewood Cliffs, NJ: Yourdon Press.
, and[bib36entry123] 1999. Peopleware: Productive Projects and Teams, 2d ed. New York, NY: Dorset House.
and Timothy Lister.[bib36entry124] 1985. “"Programmer Performance and the Effects of the Workplace." Proceedings of the 8th International Conference on Software Engineering”. Washington, DC: IEEE Computer Society Press, 268–72.
, and[bib36entry125] 1979. Structured Analysis and Systems Specification: Tools and Techniques. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry127] 1979. “"Social Processes and Proofs of Theorems and Programs."” Communications of the ACM , no. 5 (5): 271–80.
, , and .[bib36entry128] 1965. “"Programming Considered as a Human Activity." Proceedings of the 1965 IFIP Congress”. Amsterdam: North-Holland, 213–17. Reprinted in Yourdon 1982.
[bib36entry129] 1968. “"Go To Statement Considered Harmful."” Communications of the ACM , no. 3 (3): 147–48.
[bib36entry133] 1989. “"On the Cruelty of Really Teaching Computer Science."” Communications of the ACM , no. 12 (12): 1397–1414.
[bib36entry136] 1989. Fundamentals of Database Systems. Redwood City, CA: Benjamin/Cummings.
, and .[bib36entry137] 1976. “"An Analysis of Some Commercial PL/I Programs."” IEEE Transactions on Software Engineering , no. 2 (2): 113–20.
[bib36entry138] 1977. “"The Influence of Structured Programming on PL/I Program Profiles."” IEEE Transactions on Software Engineering , no. 5 (5): 364–68.
[bib36entry139] 1982. “"Improving Computer Program Readability to Aid Modification."” Communications of the ACM , no. 8 (8): 512–21.
, and[bib36entry140] 1975. “"An Analysis of Errors and Their Causes in System Programs."” IEEE Transactions on Software Engineering , no. 2 (2): 140–49.
[bib36entry141] 1984. “"Program Complexity and Programming Style." Proceedings of the First International Conference on Data Engineering”. New York, NY: IEEE Computer Society Press, 534–41.
[bib36entry142] 1976. “"Design and Code Inspections to Reduce Errors in Program Development."” IBM Systems Journal , no. 3: 182–211.
[bib36entry143] 1986. “"Advances in Software Inspections."” IEEE Transactions on Software Engineering , no. 7 (7): 744–51.
[bib36entry144] Federal Software Management Support Center. 1986. Programmers Work-bench Handbook. Falls Church, VA: Office of Software Development and Information Technology.
[bib36entry145] 2002. “"Leading Programming Languages for IT Portfolio Planning,"” Gartner Research report SPA- 17-6636, September 27, 2002.
, and M. Driver.[bib36entry146] 1988. “"Program Verification: The Very Idea."” Communications of the ACM , no. 9 (9): 1048–63.
[bib36entry147] FIPS PUB 38, “Guidelines for Documentation of Computer Programs and Automated Data Systems”. 1976. U.S. Department of Commerce. National Bureau of Standards. Washington, DC: U.S. Government Printing Office, Feb. 15.
[bib36entry149] 1979. “"Applications Program Maintenance Study: Report to our Respondents." Proceedings Guide 48”, Philadelphia. Reprinted in Tutorial on Software Maintenance, G.Parikh and N.Zvegintzov eds. Los Alamitos, CA: CS Press, : 13–27.
, and[bib36entry150] 1979. “"The Paradigms of Programming."” Communications of the ACM , no. 8 (8): 455–60.
[bib36entry151] 1999. Refactoring: Improving the Design of Existing Code. Reading, MA: Addison-Wesley.
[bib36entry153] 2003. UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3d ed. Boston, MA: Addison-Wesley.
[bib36entry155] 1986. “"In-Process Inspections of Work Products at AT&T."” AT&T Technical Journal, March/April, 102–12.
[bib36entry156] 2003. Practical Standards for Microsoft Visual Basic .NET. Redmond, WA: Microsoft Press.
[bib36entry157] 1990. Handbook of Walkthroughs, Inspections and Technical Reviews, 3d ed. New York, NY: Dorset House.
, and .[bib36entry158] Freeman,Peter, and AnthonyI.Wasserman, eds. 1983. Tutorial on Software Design Techniques, 4th ed. Silver Spring, MD: IEEE Computer Society Press.
[bib36entry160] 2002. Software Optimization Cookbook: High-Performance Recipes for the Intel Architecture. Intel Press.
[bib36entry164] 1988. Principles of Software Engineering Management. Wokingham, England: Addison-Wesley.
[bib36entry165] 2004. Competitive Engineering. Boston, MA: Addison-Wesley. Downloadable from http://www.result-planning.com.
[bib36entry166] 1998. Customer Oriented Software Quality Assurance. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry167] 1982. Modern Programming Practices: A Report from Industry. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry169] 1991. Software Conflict: Essays on the Art and Science of Software Engineering. Englewood Cliffs, NJ: Yourdon Press.
[bib36entry171] 1999. “"Inspections—Some Surprising Findings,"” Communications of the ACM, April 1999, 17–19.
[bib36entry172] 1999. “"The realities of software technology payoffs,"” Communications of the ACM, February 1999, 74–79.
[bib36entry175] 1979. “"Measuring Improvements in Program Clarity."” IEEE Transactions on Software Engineering , no. 2 (2): 79–90.
[bib36entry176] 1991. “"Rapid Prototyping and Software Quality: Lessons from Industry." Ninth Annual Pacific Northwest Software Quality Conference”, October 7–8. Oregon Convention Center, Portland, OR.
, and .[bib36entry177] 1990. “"Debugging Effort Estimation Using Software Metrics."” IEEE Transactions on Software Engineering , no. 2 (2): 223–31.
and[bib36entry178] 1975. “"Some Psychological Evidence on How People Debug Computer Programs."” International Journal of Man-Machine Studies :151–82.
[bib36entry179] 1987. “"Measuring and Managing Software Maintenance."” IEEE Software , no. 9 (9): 34–45.
[bib36entry180] 1993. “"Practical Rules of Thumb for Software Managers."” The Software Practitioner , no. 1 (1): 4–6.
[bib36entry181] 1999. “"An Economic Release Decision Model: Insights into Software Project Management."” In Proceedings of the Applications of Software Measurement Conference, 227–239. Orange Park, FL: Software Quality Engineering.
[bib36entry182] 1994. “"Key Lessons in Achieving Widespread Inspection Use,"” IEEE Software, July 1994.
, and[bib36entry183] 1992. Practical Software Metrics For Project Management And Process Improvement. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry184] 1987. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, NJ: Prentice Hall.
, and .[bib36entry185] 1987. “"Human Factors in Computer Systems, Some Useful Readings."” Sigchi Bulletin , no. 2: 15–20.
[bib36entry186] 1984. “"Determinants of Program Repair Maintenance Requirements."” Communications of the ACM , no. 8 (8): 826–32.
[bib36entry192] 1986. “"Are Deeply Nested Conditionals Less Readable?"” Journal of Systems and Software , no. 4 (4): 335–42.
, and Curtis Cook.[bib36entry193] 2003. Performance Tuning and Optimizing ASP.NET Applications. Apress.
and Kenneth Tu.[bib36entry194] 2003. Configuration Management Principles and Practices, Boston, MA: Addison-Wesley.
.[bib36entry195] 1988. Strategies for Real-Time System Specification. New York, NY: Dorset House.
, and .[bib36entry196] 1990. “"Cute Object-oriented Acronyms Considered FOOlish."” Software Engineering Notes, January, 48.
[bib36entry198] 2001. “"Occupational Employment Projections to 2010."” Monthly Labor Review, November 2001.
[bib36entry199] 2004. “"Occupational Employment Projections to 2012."” Monthly Labor Review, February 2004, , No. 2, pp. 80–105.
[bib36entry200] 1984. “"The Evaluation of Software Systems' Structure Using Quantitative Software Metrics."” Software—Practice and Experience , no. 6 (6): 561–73.
, and Dennis Kafura.[bib36entry201] 1988. The Complete Guide to Software Testing, 2d ed. Wellesley, MA: QED Information Systems.
[bib36entry202] 2000. Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. New York, NY: Dorset House.
[bib36entry205] 1981. “"The Emperor's Old Clothes."” Communications of the ACM, February 1981, 75–83.
,[bib36entry207] 1990. “"An Office Library for Software Engineering Professionals."” Software Engineering: Tools, Techniques, Practice, May/June, 35–38.
[bib36entry209] 1978. Advanced Programming Techniques: A Second Course in Programming Using Fortran. New York, NY: John Wiley & Sons.
, , and .[bib36entry212] 1991. “"Software Process Improvement at Hughes Aircraft."” IEEE Software , no. 4 (4): 11–23.
, , and .[bib36entry216] 1986. Rationale for Design of the Ada Programming Language. Minneapolis, MN: Honeywell Systems and Research Center. IEEE Software , no. 3 (May 1990).
, et al.[bib36entry229] “IEEE Std 1471-2000. Recommended Practice for Architectural Description of Software Intensive Systems”
[bib36entry230] “IEEE Std 1490-1998, Guide - Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge”
[bib36entry236] “IEEE Std 830-1998. IEEE Recommended Practice for Software Requirements Specifications”. Los Alamitos, CA: IEEE Computer Society Press.
[bib36entry237] IEEE, 1991. IEEE Software Engineering Standards Collection, Spring 1991 Edition. New York, NY: Institute of Electrical and Electronics Engineers.
[bib36entry239] 1976. “"The Unit Development Folder (UDF): An Effective Management Tool for Software Development."” TRW Technical Report TRW-SS- 76-11. Also reprinted in Reifer 1986, 366–79.
[bib36entry240] 1987. “"The Unit Development Folder (UDF): A Ten-Year Perspective."” Tutorial: Software Engineering Project Management, ed. RichardH.Thayer. Los Alamitos, CA: IEEE Computer Society Press, 405–15.
[bib36entry244] 1994a. “"Dr. Boris Beizer on Software Testing: An Interview Part 1,"” The Software QA Quarterly, Spring 1994, 7–13.
[bib36entry245] 1994b. “"Dr. Boris Beizer on Software Testing: An Interview Part 2,"” The Software QA Quarterly, Summer 1994, 41–45.
[bib36entry246] 1987. “"Some Comments on Coding Practice."” ACM SIGSOFT Software Engineering Notes , no. 2 (2): 32–35.
[bib36entry247] Capers. 1977. “"Program Quality and Programmer Productivity." IBM Technical Report TR 02.764”, January, 42–78. Also in Jones 1986b.
[bib36entry249] Jones,T.Capers, ed. 1986b. Tutorial: Programming Productivity: Issues for the Eighties, 2d ed. Los Angeles, CA: IEEE Computer Society Press.
[bib36entry251] 1997. Applied Software Measurement: Assuring Productivity and Quality, 2d ed. New York, NY: McGraw-Hill.
[bib36entry253] 2000. Software Assessments, Benchmarks, and Best Practices. Reading, MA: Addison-Wesley.
[bib36entry254] 2003. “"Variations in Software Development Practices,"” IEEE Software, November/December 2003, 22–27.
[bib36entry255] 1989. “"Next: The Elimination of GoTo-Patches?"” ACM Sigplan Notices , no. 3 (3): 85–92.
[bib36entry256] 1988. “"Programming Languages Should NOT Have Comment Statements."” ACM Sigplan Notices , no. 10 (10): 59–60.
[bib36entry257] 1999. Testing Computer Software, 2d ed. New York, NY: John Wiley & Sons.
, Jack Falk, and .[bib36entry260] 1987. “"A Comparison of Four Design Methods for Real-Time Systems." Proceedings of the Ninth International Conference on Software Engineering”. 238–52.
[bib36entry266] 1988. The C Programming Language, 2d ed. Englewood Cliffs, NJ: Prentice Hall.
, and .[bib36entry268] 1988. Creating Effective Software: Computer Program Design Using the Jackson Methodology. New York, NY: Yourdon Press.
[bib36entry269] 1971. “"An Empirical Study of FORTRAN programs,"” Software—Practice and Experience :105–33.
[bib36entry270] 1974. “"Structured Programming with go to Statements."” In Classics in Software Engineering, edited by Edward Yourdon. Englewood Cliffs, NJ: Yourdon Press, 1979.
[bib36entry271] 1986. Computers and Typesetting, Volume B, TEX: The Program. Reading, MA: Addison-Wesley.
[bib36entry272] 1997a. The Art of Computer Programming, , Fundamental Algorithms, 3d ed. Reading, MA: Addison-Wesley.
[bib36entry273] 1997b. The Art of Computer Programming, , Seminumerical Algorithms, 3d ed. Reading, MA: Addison-Wesley.
[bib36entry274] 1998. The Art of Computer Programming, vol. 3, Sorting and Searching, 2d ed. Reading, MA: Addison-Wesley.
[bib36entry276] 1986. “"An Empirical Study of Modularity on Program Modifiability."” In Soloway and Iyengar 1986: 168–86.
, and .[bib36entry277] 1989. “"Evaluation of the Cleanroom Methodology in the Software Engineering Laboratory." Proceedings of the Fourteenth Annual Software Engineering Workshop, November 29, 1989”. Greenbelt, MD: Goddard Space Flight Center. Document SEL-89-007.
, and[bib36entry278] 1998. Practical Software Requirements: A Manual of Content and Style, Manning Publications Company.
[bib36entry281] 2000. The Rational Unified Process: An Introduction, 2d ed., Reading, MA: Addison-Wesley.
[bib36entry282] 1996. The Structure of Scientific Revolutions, 3d ed. Chicago: University of Chicago Press.
[bib36entry286] 2001. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, 2d ed. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry287] 2004. Agile and Iterative Development: A Manager's Guide. Boston, MA: Addison-Wesley, 2004.
[bib36entry289] Laurel,Brenda, ed. 1990. The Art of Human- Computer Interface Design. Reading, MA: Addison-Wesley.
[bib36entry291] 1987b. Professional Software, , Programming Practice. Indianapolis: Hayden Books.
, with[bib36entry292] 1986. The Programming Language Landscape: Syntax, Semantics, and Implementation, 2d ed. Chicago: Science Research Associates.
, and[bib36entry294] 1997. “"Calculating the Return on Investment from More Effective Requirements Management,"” American Programmer, (4):13–16.
[bib36entry295] 1979. “"A Review of Approaches to Teaching Fortran."” IEEE Transactions on Education, , no. 1: 23–25.
[bib36entry296] 2000. Software Testing and Continuous Quality Improvement, 2d ed. Auerbach Publishing.
[bib36entry297] 1989. “"Assuring Good Style for Object-Oriented Programs."” IEEE Software, September 1989, pp. 38f.
and[bib36entry299] 1989. “"An Experimental Investigation of Software Metrics and Their Relationship to Software Development Effort."” IEEE Transactions on Software Engineering , no. 5 (5): 649–53.
, and[bib36entry300] 1979. Structured Programming: Theory and Practice. Reading, MA: Addison-Wesley.
, , and .[bib36entry301] 1992. “"The Case for Case Studies of Programming Problems."” Communications of the ACM , no. 3 (3): 121–32.
, and .[bib36entry302] 1974. “"Programming with Abstract Data Types."” ACM Sigplan Notices , no. 4: 50–59.
, and[bib36entry304] 1986. “"Mental Models and Software Maintenance."” In Soloway and Iyengar 1986: 80–98.
, et al.[bib36entry305] Longstreet,DavidH., ed. 1990. Software Maintenance and Computers. Los Alamitos, CA: IEEE Computer Society Press.
[bib36entry306] 1990. “"A Comparison of Object-Oriented and Structured Development Methods."” Software Engineering Notes , no. 1 (1): 44–48.
[bib36entry307] 2000. “"Endo-Testing: Unit Testing with Mock Objects," eXtreme Programming and Flexible Processes Software Engineering - XP2000 Conference”.
, and[bib36entry309] 1987. “"A Presentation and Comparison of Four Information System Development Methodologies."” Software Engineering Notes , no. 2 (2): 26–29.
[bib36entry312] 1999. “"Learning from Pathfinder's Bumpy Start."” Software Testing and Quality Engineering, September/October 1999, pp. 10f.
[bib36entry314] 2003. Agile Software Development: Principles, Patterns, and Practices. Upper Saddle River, NJ: Pearson Education.
[bib36entry315] 1976. “"A Complexity Measure."” IEEE Transactions on Software Engineering, , no. 4 (4): 308–20.
[bib36entry321] 1998b. “"Why You Should Use Routines, Routinely,"” IEEE Software, , No. 4, July/August 1998.
[bib36entry324] 1978. “"IBM's Santa Teresa Laboratory—Architectural Design for Program Development."” IBM Systems Journal , no. 1: 4–25.
[bib36entry325] 1990. “"Towards Understanding Software—15 Years in the SEL." Proceedings of the Fifteenth Annual Software Engineering Workshop, November 28–29, 1990”. Greenbelt, MD: Goddard Space Flight Center. Document SEL-90-006.
, and[bib36entry326] 1989. “"Experiences in the Software Engineering Laboratory (SEL) Applying Software Measurement." Proceedings of the Fourteenth Annual Software Engineering Workshop, November 29, 1989”. Greenbelt, MD: Goddard Space Flight Center. Document SEL-89-007.
, and[bib36entry327] 2001. Practical Software Measurement: Objective Information for Decision Makers. Boston, MA: Addison-Wesley.
, et al.[bib36entry328] 1981. “"Knowledge Organization and Skill Differences in Computer Programmers."” Cognitive Psychology :307–25.
, et al.[bib36entry329] 1996. Managing a Programming Project: Processes and People, 3d ed. Englewood Cliffs, NJ: Prentice Hall, 1996.
, and[bib36entry331] 1996. More Effective C++: 35 New Ways to Improve Your Programs and Designs. Reading, MA: Addison-Wesley.
[bib36entry332] 1998. Effective C++: 50 Specific Ways to Improve Your Programs and Designs, 2d ed. Reading, MA: Addison-Wesley.
[bib36entry333] 1983. “"Program Indentation and Comprehensibility."” Communications of the ACM , no. 11 (11): 861–67.
, et al.[bib36entry335] 1956. “"The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information."” The Psychological Review , no. 2 (2): 81–97.
[bib36entry337] 1986. “"Structured Programming: Retrospect and Prospect."” IEEE Software, November, 58–66.
[bib36entry338] 1986. “"Data Structured Programming: Program Design Without Arrays and Pointers."” IEEE Transactions on Software Engineering , no. 2 (2): 192–97.
, and .[bib36entry341] 1987. “"The Effect of Abstract Data Types on Program Development."” IEEE Computer , no. 9 (9): 85–88.
, Joseph Urban, and Robert McDonald.[bib36entry342] 1991. “"C in Education and Software Engineering."” SIGCSE Bulletin , no. 3 (3): 45–56.
[bib36entry344] 1997. Software Engineering Standards: A User's Road Map. Los Alamitos, CA: IEEE Computer Society Press.
[bib36entry345] 2003. “"The Consummate Coach: Watts Humphrey, Father of Cmm and Author of Winning with Software, Explains How to Get Better at What You Do,"” SD Show Daily, September 16, 2003.
[bib36entry348] 1978b. “"A Controlled Experiment in Program Testing and Code Walkthroughs/Inspections."” Communications of the ACM , no. 9 (9): 760–68.
[bib36entry352] NASA Software Engineering Laboratory, 1994. Software Measurement Guidebook, June 1995, NASA-GB-001-94. Available from http://sel.gsfc.nasa.gov/website/documents/online-doc/94-102.pdf.
[bib36entry353] NCES 2002. National Center for Education Statistics, “2001 Digest of Educational Statistics,” Document Number NCES 2002130, April 2002.
[bib36entry355] 2000. “"Optimization: Your Worst Enemy,"” May 2000, http://www.flounder.com/optimization.htm.
[bib36entry356] 1982. “"Indentation, Documentation and Programmer Comprehension." Proceedings: Human Factors in Computer Systems”, March 15–17, 1982, Gaithersburg, MD: 118–20.
[bib36entry357] 1988. The Psychology of Everyday Things. New York, NY: Basic Books. (Also published in paperback as The Design of Everyday Things. New York, NY: Doubleday, 1990.)
[bib36entry359] 1990a. “"The Book Paradigm for Improved Maintenance."” IEEE Software, January, 39–45.
, and .[bib36entry360] 1990b. “"Typographic Style Is More Than Cosmetic."” Communications of the ACM , no. 5 (5): 506–20.
, and .[bib36entry361] 1984. “"Collecting and Categorizing Software Error Data in an Industrial Environment."” Journal of Systems and Software , no. 4 (4): 289–300.
, and .[bib36entry363] 1988. The Practical Guide to Structured Systems Design. Englewood Cliffs, NJ: Yourdon Press.
[bib36entry364] Parikh, G., and N.Zvegintzov, eds. 1983. Tutorial on Software Maintenance. Los Alamitos, CA: IEEE Computer Society Press.
[bib36entry366] 1972. “"On the Criteria to Be Used in Decomposing Systems into Modules."” Communications of the ACM , no. 12 (12): 1053–58.
[bib36entry367] 1976. “"On the Design and Development of Program Families."” IEEE Transactions on Software Engineering , 1 (March): 1–9.
[bib36entry368] 1979. “"Designing Software for Ease of Extension and Contraction."” IEEE Transactions on Software Engineering , no. 2 (2): 128–38.
[bib36entry369] 1999. “"ACM Fellow Profile: David Lorge Parnas,"” ACM Software Engineering Notes, May 1999, 10–14.
[bib36entry370] 1986. “"A Rational Design Process: How and Why to Fake It."” IEEE Transactions on Software Engineering , no. 2 (2): 251–57.
, and .[bib36entry371] 1985. “"The Modular Structure of Complex Systems."” IEEE Transactions on Software Engineering , no. 3 (3): 259–66.
, , and[bib36entry374] 1981. Handbook of Software Design: Methods and Techniques. New York, NY: Yourdon Press.
[bib36entry375] 1977. “"Comparing Software Design Methodologies."” Datamation, November, 89–94.
, and .[bib36entry377] 1994. Design Paradigms: Case Histories of Error and Judgment in Engineering. Cambridge, U.K.: Cambridge University Press.
[bib36entry378] 1990. “"Alfred M. Pietrasanta on Improving the Software Process."” Software Engineering: Tools, Techniques, Practices , no. 1 (1): 29–34.
[bib36entry379] 1991a. “"A Strategy for Software Process Improvement." Ninth Annual Pacific Northwest Software Quality Conference”, October 7–8, 1991. Oregon Convention Center, Portland, OR
[bib36entry380] 1991b. “"Implementing Software Engineering in IBM."” Keynote address. Ninth Annual Pacific Northwest Software Quality Conference, October 7–8, 1991. Oregon Convention Center, Portland, OR.
[bib36entry382] 1974. Zen and the Art of Motorcycle Maintenance: An Inquiry into Values. William Morrow.
[bib36entry384] 1993. Programming on Purpose: Essays on Software Design. New York, NY: Prentice Hall.
[bib36entry386] 1957. How to Solve It: A New Aspect of Mathematical Method, 2d ed. Princeton, NJ: Princeton University Press.
[bib36entry388] 2000. “"An Empirical Comparison of Seven Programming Languages,"” IEEE Computer, October 2000, 23–29.
[bib36entry390] 1988. Making Software Engineering Happen: A Guide for Instituting the Technology. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry391] 2000. “"Familiar Metric Management – Effort, Development Time, and Defects Interact."” Downloadable from http://www.qsm.com.
[bib36entry392] 1992. Measures for Excellence: Reliable Software On Time, Within Budget. Englewood Cliffs, NJ: Yourdon Press, 1992.
, and[bib36entry393] 1997. Industrial Strength Software: Effective Management Using Measurement. Washington, DC: IEEE Computer Society Press.
, and[bib36entry394] 2000. “"What We Have Learned."” Downloadable from http://www.qsm.com, June 2000.
, and[bib36entry395] 1989. “"Diffusing Software-Engineering Methods."” IEEE Software, July, 81–90.
, and .[bib36entry396] 1983. “"Flowcharts Versus Program Design Languages: An Experimental Comparison."” Communications of the ACM , no. 6 (6): 445–49.
, , and .[bib36entry398] 2000. “"The Cathedral and the Bazaar,"” http://www.catb.org/~esr/writings/cathedral-bazaar.
[bib36entry400] 1982. “"Automatic Assessment Aids for Pascal Programs."” ACM Sigplan Notices , no. 10 (10): 33–42.
[bib36entry401] 2002. “"How to Get the Most Out of Extreme Programming/Agile Methods," Proceedings, XP/Agile Universe 2002”. New York, NY: Springer; 185–196.
[bib36entry405] 1973. “"Dilemmas in a General Theory of Planning."” Policy Sciences :155–69.
, and Melvin Webber.[bib36entry408] Dieter. 1990. “"Design Measurements: Some Lessons Learned."” IEEE Software, March, 17–25.
[bib36entry409] 1987. “"‘GOTO Considered Harmful' Considered Harmful."” Letter to the editor. Communications of the ACM , no. 3 (March): 195–96. Follow-up letters in 30, no. 5 (May 1987): 351–55; , no. 6 (June 1987): 475–78; , no. 7 (July 1987): 632–34; , no. 8 (August 1987): 659–62; , no. 12 (December 1987): 997, 1085.
[bib36entry410] 1968. “"Exploratory Experimental Studies Comparing Online and Offline Programming Performance."” Communications of the ACM , no. 1 (1): 3–11.
and[bib36entry411] 1992. “"An Experimental Study of Fault Detection in User Requirements Documents," ACM Transactions on Software Engineering and Methodology”, , no. 2, 188–204.
, and[bib36entry419] SEI 1995. The Capability Maturity Model: Guidelines for Improving the Software Process, Software Engineering Institute, Reading, MA: Addison-Wesley, 1995.
[bib36entry420] SEI, 2003. “"Process Maturity Profile: Software CMM®, CBA IPI and SPA Appraisal Results: 2002 Year End Update,"” Software Engineering Institute, April 2003.
[bib36entry421] 1991. “"Analyzing Error-Prone System Structure."” IEEE Transactions on Software Engineering , no. 2 (2): 141–52.
, and .[bib36entry422] SEN 1990. “"Subsection on Telephone Systems,"” Software Engineering Notes, April 1990, 11–14.
[bib36entry424] 1981. “"The Psychological Study of Programming."” Computing Surveys , no. 1 (1): 101–20.
[bib36entry425] 1985. “"Identifying Error-Prone Software—An Empirical Study."” IEEE Transactions on Software Engineering , no. 4 (4): 317–24.
, et al.[bib36entry426] 1978. “"Predicting Programmers' Ability to Modify Software." TR 78-388100-3”, General Electric Company, May.
, et al.[bib36entry427] 1979. “"Modern Coding Practices and Programmer Performance."” IEEE Computer , no. 12 (12): 41–49.
, et al.[bib36entry428] 1989. “"Metrics, Outlier Analysis and the Software Design Process."” Information and Software Technology , no. 2 (2): 91–98.
and D. Ince.[bib36entry430] 1988. Object Oriented Systems Analysis—Modeling the World in Data. Englewood Cliffs, NJ: Prentice Hall.
, and .[bib36entry431] 1979. “"Syntactic/Semantic Interactions in Programmer Behavior: A Model and Experimental Results."” International Journal of Computer and Information Sciences , no. 3: 219–38.
, and .[bib36entry432] 1976. “"Exploratory Experiments in Programmer Behavior."” International Journal of Computing and Information Science :123–43.
[bib36entry433] 1980. Software Psychology: Human Factors in Computer and Information Systems. Cambridge, MA: Winthrop.
[bib36entry434] 1987. Designing the User Interface: Strategies for Effective Human- Computer Interaction. Reading, MA: Addison-Wesley.
[bib36entry435] 2002. “"What We Have Learned About Fighting Defects," Proceedings, Metrics 2002”. IEEE; 249–258.
et al.[bib36entry439] 2002. Performance Solutions: A Practical Guide to Creating Responsive, Scalable Software. Boston, MA: Addison-Wesley.
, and .[bib36entry440] Software Productivity Consortium. 1989. Ada Quality and Style: Guidelines for Professional Programmers. New York, NY: Van Nostrand Reinhold.
[bib36entry441] 1984. “"Empirical Studies of Programming Knowledge."” IEEE Transactions on Software Engineering , no. 5 (5): 595–609.
, and .[bib36entry443] 1983. “"Cognitive Strategies and Looping Constructs: An Empirical Study."” Communications of the ACM , no. 11 (11): 853–60.
, and .[bib36entry444] Solution Systems. 1987. World-Class Programmers' Editing Techniques: Interviews with Seven Programmers. South Weymouth, MA: Solution Systems.
[bib36entry446] 1976. “"Software Malpractice—A Distasteful Experience."” Software—Practice and Experience :293–99.
[bib36entry448] SPMN. 1998. Little Book of Configuration Management. Arlington, VA; Software Program Managers Network.
[bib36entry450] 2003. “"Emergent Design vs. Early Prototyping,"” May 26, 2003, http://www.softwarereality.com/design/early_prototyping.jsp.
[bib36entry451] 1989. “"Intelligent Interactive Video Simulation of a Code Inspection."” Communications of the ACM , no. 7 (7): 832–43.
[bib36entry456] Sun Microsystems, Inc. 2000. “"How to Write Doc Comments for the Javadoc Tool,"” 2000. Available from http://java.sun.com/j2se/javadoc/writingdoccomments/.
[bib36entry457] 2000. Exceptional C++: 47 Engineering Puzzles, Programming Problems, and Solutions. Boston, MA: Addison-Wesley.
[bib36entry458] 1999. “"Process Control for Error Free Software: A Software Success Story,"” IEEE Software, May 1999.
, and .[bib36entry459] 1997. Why Things Bite Back: Technology and the Revenge of Unintended Consequences. Vintage Books.
[bib36entry460] 1988. “"Program Readability: Procedures versus Comments."” IEEE Transactions on Software Engineering , no. 9 (9): 1271–79.
[bib36entry461] Thayer,RichardH., ed. 1990. Tutorial: Software Engineering Project Management. Los Alamitos, CA: IEEE Computer Society Press.
[bib36entry464] 1990. “"A Bibliography of Programming Style."” ACM Sigplan Notices , no. 2 (2): 7–16.
, and .[bib36entry466] 1991. “"The Application of Multiple Team Inspections on a Safety-Critical Software Standard," Proceedings of the 4th Software Engineering Standards Application Workshop”, Los Alamitos, CA: IEEE Computer Society Press.
, , and .[bib36entry467] U.S. Department of Labor. 1990. “"The 1990–91 Job Outlook in Brief."” Occupational Outlook Quarterly, Spring. U.S. Government Printing Office. Document 1990-282-086/20007.
[bib36entry468] 1989. “"A Summary of Software Measurement Experiences in the Software Engineering Laboratory."” Journal of Systems and Software , no. 2 (2): 137–48.
and .[bib36entry469] 1991. “"Why Is Software Late? An Empirical Study of Reasons for Delay in Software Development."” IEEE Transactions on Software Engineering , no. 6 (6): 582–90.
[bib36entry470] 1978. Program Style, Design, Efficiency, Debugging, and Testing, 2d ed. Englewood Cliffs, NJ: Prentice Hall.
[bib36entry471] 2003. “"Building Better Software with Better Tools,"” IEEE Computer, September 2003, 12–14.
[bib36entry473] 1992. “"Evaluation of Vendor Products: CASE Tools as Methodological Companions."” Communications of the ACM , no. 4 (4): 91–105.
, , and .[bib36entry474] 1986. “"Expertise in Debugging Computer Programs: An Analysis of the Content of Verbal Protocols."” IEEE Transactions on Systems, Man, and Cybernetics , no. 5 (5): 621–37.
[bib36entry475] 1991. “"Investigating the Application of Capture-Recapture Techniques to Requirements and Design Reviews." Proceedings of the Sixteenth Annual Software Engineering Workshop, December 4–5, 1991”. Greenbelt, MD: Goddard Space Flight Center. Document SEL-91-006.
, et al.[bib36entry476] 1977. “"A Method of Programming Measurement and Estimation."” IBM Systems Journal , no. 1: 54–73.
, and .[bib36entry478] 1989. “"Software Defect Prevention Using McCabe's Complexity Metric."” Hewlett-Packard Journal, April, 64–68.
[bib36entry479] 1988. “"Mapping the Design Information Representation Terrain."” IEEE Computer, December, 8–23.
[bib36entry481] 1983. The Programmer's Craft: Program Construction, Computer Architecture, and Data Management. Reston, VA: Reston Publishing.
[bib36entry483] 1998. The Psychology of Computer Programming: Silver Anniversary Edition. New York, NY: Dorset House.
[bib36entry484] 1974. “"Goals and Performance in Computer Programming."” Human Factors , no. 1 (1): 70–77.
, and .[bib36entry487] 1975. “"Evaluating Software Development by Error Analysis: The Data from the Architecture Research Facility."” Journal of Systems and Software , no. 2 (2): 57–70.
[bib36entry488] 1972. “"Review of The Psychology of Computer Programming, by Gerald M. Weinberg."” ACM Computing Reviews , no. 4 (4): 175–76.
[bib36entry489] “Bill Brykczynski, and Reginald Meeson”. 1996. Software Inspection: An Industry Best Practice. Los Alamitos, CA: IEEE Computer Society Press.
,[bib36entry490] 2000 “"What Is Software Testing? And Why Is It So Hard?"” IEEE Software, January 2000, 70–79.
[bib36entry491] 2002. How to Break Software: A Practical Guide to Testing. Boston, MA: Addison-Wesley.
[bib36entry495] 2002. Pair Programming Illuminated. Boston, MA: Addison-Wesley.
, and Robert Kessler.[bib36entry496] 1998. “"Hughes Aircraft's Widespread Deployment of a Continuously Improving Software Process,"” Software Engineering Institute/ Carnegie Mellon University, CMU/SEI- 98-TR-006, May 1998.
, et al.[bib36entry497] 2000. Java Platform Performance: Strategies and Tactics. Boston, MA: Addison-Wesley.
, and .[bib36entry499] 1971. “"Program Development by Stepwise Refinement."” Communications of the ACM , no. 4 (4): 221–27.
[bib36entry502] 1981. “"The Effect of Modularization and Comments on Program Comprehension." Proceedings of the Fifth International Conference on Software Engineering”, March 1981, 215–23.
, and .[bib36entry503] 1972. “"A Case Against the GO-TO." Proceedings of the 25th National ACM Conference”, August 1972, 791–97.
[bib36entry504] 1974. “"Human Errors in Programming."” International Journal of Man-Machine Studies :361–76.
[bib36entry505] 1979. Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design. Englewood Cliffs, NJ: Yourdon Press.
, and .[bib36entry507] Yourdon, Edward, ed. 1982. Writings of the Revolution: Selected Readings on Software Engineering. New York, NY: Yourdon Press.
[bib36entry508] 1986a. Managing the Structured Techniques: Strategies for Software Development in the 1990s, 3d ed. New York, NY: Yourdon Press.
3.145.75.217