1. CS1: chr@cs.rit.edu Classic Software Life Cycle “Waterfall” method: 1.Requirements/Analysis Determine the problem to be solved – client-centered 2.Specification Carefully describe the details of the solution – developer-centered 3.Design (often combined with Specification) Create a plan or structure of a solution 4.Code/Implement Write and debug the code 5.Test Find errors in the code Debug – find causes of the errors and fix them 6.Maintenance Keep the software up to date Accommodate changes in requirements over time Correct latent problems

2. CS1: chr@cs.rit.edu “Agile” software development Agile Manifesto ( http://agilemanifesto.org/ )http://agilemanifesto.org/ –Individuals and interactions matter more than processes and tools. –Working software is more helpful than comprehensive documentation. –Customer collaboration is better than contract negotiation. –Responding to change is more important than following a plan. That is, while there is value in the items on the right, agile developers value the items on the left more.

3. CS1: chr@cs.rit.edu Some Agile Principles Working software is the primary measure of progress. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. At regular intervals, the team reflects on how to become more effective, and then tunes and adjusts its behavior accordingly. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.