《敏捷迭代开发：管理者指南》—参考文献

本节书摘来自异步社区《敏捷迭代开发：管理者指南》一书中的参考文献，作者【美】Craig Larman，更多章节内容可以访问云栖社区“异步社区”公众号查看。

参考文献
敏捷迭代开发：管理者指南
Ambler00 Ambler, S. 2000. The Unified Process—Elaboration Phase. R D Books.

Ambler02 Ambler, S. 2002. Agile Modeling, John Wiley Sons. AM02 Auer, K., and Miller, R. 2002. Extreme Programming Applied: Playing to Win. Addison-Wesley.

AW02 Augustine, S., and Woodcock, S. 2002. “Agile Project Management: Emergent Order through Visionary Leadership.” CC Pace Systems. July 2002.

BDSSS98 Beedle, M., Devos, M., Sharon, Y., Schwaber, K., and Sutherland, J. “SCRUM: A Pattern Language for Hyperproductive Software Development.” Pattern Languages of Program Design vol. 4. Addison-Wesley.

Beck00 Beck, K. 2000. Extreme Programming Explained—Embrace Change. Addison-Wesley.

BEKPSM98 Boehm, B., Egyed, A., Kwan, J., Port, D., Shah, A., and Madachy, R., 1998. “Using the WinWin Spiral Model: A Case Study.” IEEE __Computer, July 1998.

Bertalanfy68 Bertalanfy, Ludwig vog. 1968. General Systems Theory. George Braziller Publishers.

Blaustein03 Blaustein, S. 2003. Personal communications, ICSE 2003, Portland, USA.

Booch96 Booch, G., 1996. Object Solutions: Managing the Object-Oriented Project. Addison-Wesley.

Boehm81 Boehm, B. 1981. Software Engineering Economics. Prentice-Hall.

Boehm85 Boehm, B. 1985. “A Spiral Model of Software Development and Enhancement.” Proceedings of an International Workshop on Software Process and Software Environments, March 1985.

Boehm96 Boehm, B. 1996. “Anchoring the Software Process.” IEEE Software. July 1996.

Bowers02 Bowers, P. 2002. “Highpoints From the Agile Software Development Forum.” CrossTalk: The Journal of Defense Software Engineering, Oct. 2002.

BP01 Boehm, B., and Port, D. 2001. “Balancing Discipline and Flexibility with the Spiral Model and MBASE.” CrossTalk: The Journal of Defense Software Engineering, Dec. 2001.

BP88 Boehm, B, and Papaccio, P. 1988. “Understanding and Controlling Software Costs.” IEEE Transactions on Software Engineering, Oct. 1988.

C3Team98 The C3 Payroll Team, 1998. “Chrysler Goes to Extremes.” Distributed Computing, Oct. 1998.

CLW01 Cohen, D., Larson, G., and Ware, B. 2001. “Improving Software Investments through Requirements Validation.” IEEE 26th Software Engineering Workshop.

CM96 Chatzoglou, P., and Macaulay, L. 1996, “Requirements Capture And Analysis: A Survey of Current Practice.” Requirements Engineering Journal 1（2）.

Cockburn01 Cockburn, A. 2001. Writing Effective Use Cases. Addison-Wesley.

Cockburn02 Cockburn, A. 2002. Agile Software Development. Addison-Wesley.

Coplien94 Coplien, J. 1994. “Borland Software Craftsmanship: A New Look at Process, Quality, and Productivity.” Proceedings of the 5th Annual Borland International Conference, Orlando, USA.

CP86 Clements, P., and Parnas, D. 1986. “A Rational Design Process: How and why to Fake It.” IEEE Transactions on Software Engineering. Feb. 1986.

Crocker02 Crocker, R. 2002. Personal communications, JAOO 2002, Aarhus, Denmark.

Deck94 Deck, M. 1994. “Cleanroom Software Engineering: Quality Improvement and Cost Reduction.” Proceedings, 12th Pacific Northwest Software Quality Conference.

Deming88 Deming, W. E. 1988. Deming Management Method. Perigee.

DL99 DeMarco, T., and Lister, T. 1999. Peopleware, 2nd edition. Dorset House.

DSB87 Brooks, F., et al. 1987. Report of the Defense Science Board Task Force on Military Software, Oct. 1987. USA DoD.

Evans01 Evans, G. 2001. “An Extreme RUP Success.” Software Development Magazine. Sept, 2001.

Fagan76 Fagan, M. 1976. “Design and Code Inspections to Reduce Errors in Program Development.” IBM Systems Journal, 15（3）.

FDA97 USA Food and Drug Administration. June 1997. General Principles of Software Validation, Version 1.1.

FDA02 USA Food and Drug Administration. Jan. 2002. General Principles of Software Validation; Final Guidance for Industry and FDA Staff.

FF99 Fowler, M, and Foemmel, M. 1999. “Continuous Integration.” Available: www.martinfowler.com/articles/continuousintegration.html.

FH01 Firesmith, D., and Henderson-Sellers, B. 2001. The OPEN Process Framework: An Introduction. Addison-Wesley

Firesmith87 Firesmith, D. 1987. “The Management Implications of the Recursive Nature of Object-Oriented Development.” AdaEXPO/SigAda Conference Proceedings, Boston, USA, Dec. 1987

Fowler01 Fowler, M. 2001.“The New Methodology.”Available: www.martinfowler.com/ articles/newMethodology.html

GAO98 Government Accounting Office, 1998. Air Traffic Control: Evolution and Status of FAA’s Automation Program. USA GAO.

GAO99 Government Accounting Office, 1999. Air Traffic Control: Observation on FAA’s Air Traffic Control Modernization Program. USA GAO.

GB01 Gallagher, B., and Brownsword. L. 2001. The Rational Unified Process and the Capability Matu rity Model–Integrated for Systems and Software Engineering （CMMI）. Software Engineering Institute.

GG93 Gilb, T., and Graham, D. 1993. Software Inspection. Addison-Wesley.

Gilb76 Gilb, T. 1976. Software Metrics. Chartwell-Bratt.

Gilb88 Gilb, T. 1988. Principles of Software Engineering Management. Addison-Wesley.

Gilb03 Gilb, T. 2003. Competitive Engineering. In draft. Available: www.gilb.com.

Githens98 Githens, G. 1998. “Rolling Wave Project Planning.” Proceedings of the 29th Annual Project Management Institute 1998 Seminars and Symposium.

GNP97 Goldman, S., Nagel, R., and Preiss, K. 1997. Agile Competitors and Virtual Organizations: Strategies for Enriching the Customer. John Wiley Sons.

HC96 Harrison, N, and Coplien, J. 1996. “Patterns of Productive Software Organizations.” Bell Labs Technical Journal, Summer 1996.

Hetzel84 Hetzel, W. 1984. The Complete Guide to Software Testing. QED Information Sciences.

Highsmith00 Highsmith, J. 2000. Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. Dorset House.

Highsmith01 Highsmith, J. 2001. “Design the Box.” Cutter Consortium’s Agile Project Management E-Mail Advisor, Aug. 23, 2001.

Highsmith02 Highsmith, J. 2002. Agile Project Management: Principles and Tools. Cutter Consortium Executive Report 4（2）.

Highsmith02a Highsmith, J. 2002. Agile Software Development Ecosystems. Addison- Wesley.

Humphrey96 Humphrey, W. 1996. Introduction to the Personal Software Process. Addison-Wesley.

Jarzombek99 Jarzombek, J. 1999. The 5th Annual JAWS S3 Proceedings.

JBR99 Jacobson, I., Booch, G., and Rumbaugh, J. 1999. The Unified Software Development Process. Addison-Wesley.

Johnson02 Johnson, J. 2002. Keynote speech, XP 2002, Sardinia, Italy.

Jones95 Jones, C. 1995. Patterns of Software Failure and Success. International Thompson Press.

Jones96 Jones, C. 1996. Patterns of Software Systems Failure and Success. International Thomson Press.

Jones97 Jones, C. 1997. Applied Software Measurement. McGraw Hill.

Jones99 Jones, C. 1999. Charismatek Countdown: A Software Metrics Newsletter. Jan. 1999.

Jones00 Jones, C. 2000. Software Assessments, Benchmarks, and Best Practices. Addison-Wesley.

JPKP03 Jalote, P., Palit, A., Kurien, P., and Peethamber, V. 2003. Timeboxing: A Process Model for Iterative Software Development. Paper in progress.

KC95 Keil, M. and Carmel, E. 1995. “Customer-developer links in software development.”Communications of the ACM, May 1995.

KK03 Kroll, P, and Kruchten, P. The Rational Unified Process Made Easy. Addison-Wesley.

Kruchten95 Kruchten, P. 1995. “The 4+1 View Model of Architecture.” IEEE Software 12（6）.

Kruchten00 Kruchten, P. 2000. The Rational Unified Process—An Introduction, 2nd edition. Addison-Wesley.

Kruchten00a Kruchten, P. 2000. “From Waterfall to Iterative Development — A Challenging Transition for Project Managers,” The Rational Edge, Dec. 2000.

Larman97 Larman, C. 1997. Applying UML and Patterns: An Introduction to OOA/D, 1st edition. Prentice-Hall.

Larman01 Larman, C. 2001. Applying UML and Patterns: An Introduction to OOA/D and the Unified Process, 2nd edition. Prentice-Hall.

LB03 Larman, C., and Basili, V. 2003. “Iterative and Incremental Development: A Brief History.” IEEE Computer, June 2003.

MacCormack01 MacCormack, A. 2001. “Product-Development Practices That Work.” MIT Sloan Management Review. 42（2）.

Malotaux03 Malotaux, N. 2003. Evolutionary Project Management Methods. Available: www.malotaux.nl.

Manzo02 Manzo, J. 2002. “Odyssey and Other Code Science Success Stories.” Crosstalk: The Journal of Defense Software Engineering, Oct. 2002, USA DoD.

Martin91 Martin, J. 1991. Rapid Application Development. Macmillan.

McConnell96 McConnell, S. 1996. Rapid Development. Microsoft Press.

McConnell98 McConnell, S. 1998. Software Project Survival Guide. Microsoft Press.

MJHS90 Mays, R., Jones, C., Holloway, and Studinski, D. 1990. “Experiences with Defect Prevention.” IBM Systems Journal, 29（1）.

MKCC03 MacCormack, A., Kemerer, C., Cusumano, M., and Crandall, B. 2003. “Exploring Trade-offs between Productivity Quality in the Selection of Software Development Practices.” Working draft submitted to IEEE Software.

Morales02 Morales, A. 2002. “Going to Extremes.” Software Development, Jan. 2002.

MVI01 MacCormack, A., Verganti, R., and Iansiti, M. 2001. “Developing Products on Internet Time: The Anatomy of a Flexible Development Process.” Management Science. Jan. 2001.

OR94 Ogunnaike, B., and Ray, H. 1994. Process Dynamics, Modeling, and Control.Oxford University Press.

Parkinson58 Parkinson, N. 1958. _Parkinsons Law: The Pursuit of Progress. _John Murray.

Paulk01 Paulk, M. 2001. “Extreme Programming from a CMM Perspective.” IEEE Software, Nov 2001.

PF02 Palmer and Felsing. 2002. A Practical Guide to Feature-Driven Development. Prentice-Hall.

PKT93 Paine, T., Kruchten, P., and Toth, K. 1993. “Modernizing ATC Through Modern Software Methods,” Proceedings of the Air Traffic Control Association, Arlington, Virginia.

PMI00 PMI contributors. 2000. Project Management Body of Knowledge. Project Management Institute. www.pmi.org

Poppendieck03 Poppendieck, M., and Poppendieck, T. 2003. Lean Software Development: An Agile Toolkit for Software Development Managers. Addison-Wesley.

Royce70 Royce, W. 1970. “Managing the Development of Large Software Systems.” Proceedings of IEEE Westcon.

Russell91 Russell, X. 1991. “Experience with Inspections in Ultralarge-Scale Developments.” IEEE Software, Jan 1991.

SB02 Schwaber, K., and Beedle, M. 2002. Agile Software Development with Scrum. Prentice-Hall.

Schuh01 Schuh, P. 2001. “Recovery, Redemption, and Extreme Programming.” IEEE Software, Nov. 2001.

Schwaber95 Schwaber, K. 1995. “The Scrum Development Process.” OOPSLA ‘95 Workshop on Business Object Design and Implementation. Austin, USA.

SEG68 Sackman, H., Erikson, W., and Grant, E. “Exploratory Experimantal Studies Comparing Online and Offline Programming Performance.” Communications of the ACM, Jan. 1968.

SEI03 Capability Maturity Model for Software, Available: www.sei.cmu. edu/ cmm/cmm.html.

Shine03 Corporate Report, 2003. Agile Methodologies Survey Results. Shine Technologies Pty Ltd., Victoria, Australia.

SKTYBE92 Sheldon, F., Kavi, K., Tausworth, J., Yu, J., Brettschneider, A., and Everett, W. 1992. “Reliability Measurement from Theory to Practice,” IEEE Software. July 1992.

Solon02 Solon, R. 2002. “Benchmarking the ROI for Software Process Improvement.” The DoD SoftwareTech News. Nov. 2002, USA DoD.

Standish00 Jim Johnson, et al. 2000. ChAOS in the New Millenium. Published Report. The Standish Group.

Standish94 Jim Johnson, et al. 1994. Chaos: Charting the Seas of Information Technology. Published Report. The Standish Group.

Standish98 Jim Johnson, et al. 1998. ChAOS: A Recipe for Success, 1998. Published Report. The Standish Group.

Stapleton97 Stapleton, J. 1997. DSDM: Dynamic Systems Development Method, Addison-Wesley.

Thomas01 Thomas, M. 2001. “IT Projects Sink or Swim.” British Computer Society Review.

TN86 Takeuchi, H., and Nonaka, I. 1986. “The New New Product Development Game.” Harvard Business Review, Jan. 1986.

Turner02 Turner, R. 2002. “A Study of Best Practice Adoption by Defense Acquisition Programs.” Crosstalk: The Journal of Defense Software Engineering, May 2002, USA DoD.

Wells01 Wells, D. 2001. XP material. Available: www.extremeprogramming.org

Wiegers00 Wiegers, K. 2000. “Stop Promising Miracles.” Software Development, Feb. 2000.

Wong84 Wong, C. 1984. “A Successful Software Development.” IEEE Transactions of Software Engineering, 3, 1984.

ZR97 Ziv, H., and Richardson, D. 1997. “The Uncertainty Principle in Software Engineering.”Proceedings of the 19th International Conference on Software Engineering.

本文仅用于学习和交流目的，不代表异步社区观点。非商业转载请注明作译者、出处，并保留本文的原始链接。

敏捷开发模式下的利刃：探索性测试（ET） 探索式软件测试是一种强大的黑盒测试思考方法，但却被广泛误解。在某些情况下，它可以比自动化测试更加有生产力。它是一种经过深思熟虑的测试方式，没有测试脚本，可以使你的测试超出各种明显已经测试过的场景。 什么是探索式测试 探索式测试（Exploratory Testing）是一种软件测试方法，也可以说是一种测试思维方法，最先是 Cem Kaner 在 1983 年提出的。
《敏捷迭代开发：管理者指南》—第2章2.1节迭代开发 迭代开发（iterative development）是一种构建软件（或者其他东西）的方式，软件的整个生命周期依次由几个迭代组成（迭代计划技巧参见11.1节）。
《敏捷迭代开发：管理者指南》—第2章2.6节渐进需求分析 渐进和自适应开发不属于那种需求总是不着边际或者高频率变化的情形。准确地说，绝大多数需求的发现和精化往往出现在早期的迭代中，并且最早受关注的是最具有架构性意义或者最具商业价值的需求（渐进需求技巧参见11.3节）。
《团队软件过程（修订版）》—第1章1.5节TSPi过程 每个脚本都从相应活动的整体目的说明开始，举例来说，这些活动可以是开发需求文档、产生设计或者执行测试。每个脚本还包括入口准则和出口准则。入口准则详细说明了开始一个脚本之前要做的准备工作，出口准则详细说明了结束一个脚本时要完成的工作。
异步社区 异步社区(www.epubit.com)是人民邮电出版社旗下IT专业图书旗舰社区，也是国内领先的IT专业图书社区，致力于优质学习内容的出版和分享，实现了纸书电子书的同步上架，于2015年8月上线运营。公众号【异步图书】，每日赠送异步新书。