Download
agile software development n.
Skip this Video
Loading SlideShow in 5 Seconds..
AGILE SOFTWARE DEVELOPMENT PowerPoint Presentation
Download Presentation
AGILE SOFTWARE DEVELOPMENT

AGILE SOFTWARE DEVELOPMENT

240 Vues Download Presentation
Télécharger la présentation

AGILE SOFTWARE DEVELOPMENT

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. AGILE SOFTWARE DEVELOPMENT AYSE GUL YAMAN

  2. Outline • Traditional approach • Agile Software Development • Agile Values • Agile Principles • Limitations of Agile Methodologies • Using Components to Reduce Limitations

  3. Traditional approach • Predictive methods • Planning the future in detail • Waterfall model -requirements -design -coding -testing

  4. Agile Software Development(A new approach) • Adaptive methods • Adapting quickly to changing realities • Short timeboxes(iterations) • Each iteration include -planning -requirement analysis -design -coding -testing

  5. Agile methods • eXtreme Programming(XP) • Feature-Driven Development(FDD) • Agile Modeling • Extreme Modeling • Scrum • Adaptive Software Development(ASD) • Crystal Clear and Other Crystal Methodologies • Dynamic Systems Development Method(DSDM)

  6. Agile Alliance[2001] • Agile Manifesto • Values and Principles

  7. Agile Values • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan

  8. The Agile Principles • Customer satisfaction by rapid,continuous delivery of useful software • Working software is delivered frequently (weeks rather than months) • Working software is the principle measure of progress

  9. The Agile Principles(cont.) • Even late changes in requirements are welcomed • Close,daily cooperation between business people and developers • Face-to-face conversation is the best form of communication

  10. The Agile Principles(cont.) • Projects are built around motivated individuals,who should be trusted • Continuous attention to technical excellence and good design • Simplicity

  11. The Agile Principles(cont.) • Self-orginizing teams • Regular adaptation to changing circumstances • Agile processes promote sustainable development

  12. Limitations of Agile Methodologies • Projects with distributed development teams and resources • Outsourcing • Building or using reusable artifacts • Using legacy systems or Commercial-Off-The-Shelf(COTS) components • Projects involving large teams • Development of large software systems • Development of safety-critical software systems

  13. Using Components • Larger team in building large software -Problem can be divided into smaller units and then parts of the team are responsible for developing particular components in an agile manner • System can be extended -Defining additional components or extending the scope of existing components • Communication -Component interfaces can help in communication between team members and customers

  14. Using Components(cont.) • Reusability -Well-defined components can be reused in a similar context in the future • Building large safety-critical systems -Using pre-tested COTS components can further increase the quality of the safety-critical software

  15. References • http://www.agilealliance.org/ • http://en.wikipedia.org/wiki/Agile_software_development • http://www.ambysoft.com/ • Zoran Stojanovic, Ajantha Dahanayake, Henk Sol, "Modeling and Architectural Design in Agile Development Methodologies", The 8th CaiSE/IFIP8.1 International Workshop on Evaluation of Modeling Methods in Systems Analysis and Design EMMSAD> '> 03, Velden, Austria, June 16-20, 2003, pp. 180-189. • Zoran Stojanovic,  Ajantha Dahanayake, Henk Sol, "Component-Oriented Agile Software Development ", 4th International Conference on eXtreme Programming and Agile Processes in Software Engineering (XP 2003), May 26-30, 2003, Lecture Notes in Computer Science, Springer-Verlag Heidelberg, Volume 2675 / 2003, pp. 315-318. Questions?