软件工程-实践者的研究方法-(3).pptVIP

* These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman. * Chapter 3 Agile Development Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman For non-profit educational use only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioners Approach, 7/e. Any other reproduction or use is prohibited without the express written permission of the author. * The Manifesto (宣言) for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.” Kent Beck et al * What is “Agility”? Effective (rapid and adaptive) response to change Effective communication among all stakeholders Organizing a team so that it is in control of the work performed Yielding … Rapid, incremental delivery of software 传统软件开发方法：强调过程；强调文档；开发人员负担过重 软件开发的新挑战：快速进入市场要求高生产率；快速变化的需求；快速发展的技术 * Agility and the Cost of Change * An Agile Process Is driven by customer descriptions of what is required (scenarios) Recognizes that plans are short-lived Develops software iteratively with a heavy emphasis on construction activities Delivers multiple ‘software increments’ Adapts as changes occur * Agility Principles - I 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customers competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months,