Agile software development
Nội dung
1. Waterfall Model
2. Agile software development
3. Extreme Programming (XP)
4. Agile vs Waterfall
Waterfall Model
 "From the 1970 IEE paper "Managing
the Development of Large Software
Systems“
 Winston Royce's Waterfal...
Waterfall Model
Waterfall Model
 Requirement
◦ Each phase should pass iteratively to the
next
◦ The entire process should be exercised
tw...
Agile software development
Values
 Individuals and interactions over
processes and tools
 Working software over
comprehensive documentation
 Custo...
Principles
1) 12 principles
Extreme Programming (XP)
 Agile development is not a
methodology. It is an umbrella term
that describes several agile
met...
Practices
 Incremental planning
 Small Releases
 Continuous integration
 Test first development
 Refactoring
 Pair P...
Cycle
Extreme Programming (XP)
Example
 Story card for document downloading
Downloading and printing an
article
 First, you select the article that you want from a displayed
list.
 You then have t...
Task cards for document
downloading
Test: Test credit card validity
Input:
 A string representing the credit card number and two
integers representing the mo...
Agile vs Waterfall
 Ability to change
Agile vs Waterfall
 Visibility
Agile vs Waterfall
 Successful
Agile vs Waterfall
Agile vs Waterfall
Agile Waterfall
Small, medium project Big project
Less architectural Better architectural
Source
 http://www.agilemodeling.com
 http://www.codeproject.com/Articles/6
04417/Agile-software-development-
methodolog...
Upcoming SlideShare
Loading in …5
×

Agile software development

448 views

Published on

Speaker: Tuan Anh

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
448
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 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. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 
  • Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles, which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted Wiki
  • Agile software development

    1. 1. Agile software development
    2. 2. Nội dung 1. Waterfall Model 2. Agile software development 3. Extreme Programming (XP) 4. Agile vs Waterfall
    3. 3. Waterfall Model  "From the 1970 IEE paper "Managing the Development of Large Software Systems“  Winston Royce's Waterfall Model
    4. 4. Waterfall Model
    5. 5. Waterfall Model  Requirement ◦ Each phase should pass iteratively to the next ◦ The entire process should be exercised twice before release ◦ Royce knew that a single pass will fail
    6. 6. Agile software development
    7. 7. 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. 8. Principles 1) 12 principles
    9. 9. Extreme Programming (XP)  Agile development is not a methodology. It is an umbrella term that describes several agile methodologies
    10. 10. Practices  Incremental planning  Small Releases  Continuous integration  Test first development  Refactoring  Pair Programming  Collective Ownership  On-site Customer  Simple design
    11. 11. Cycle
    12. 12. Extreme Programming (XP)
    13. 13. Example  Story card for document downloading
    14. 14. Downloading and printing an article  First, you select the article that you want from a displayed list.  You then have to tell the system how you will pay for it; this can either be through a subscription, though a company account or by credit card.  Alter this, you get a copyright form from the system to fill in.  When you have submitted this, the article you want is downloaded onto your computer.  You then choose a printer and a copy of the article is printed.  You tell the system printing has been successful.  If the article is a print-only article, you can't keep the PDF version, so it is automatically deleted from your computer.
    15. 15. Task cards for document downloading
    16. 16. Test: Test credit card validity Input:  A string representing the credit card number and two integers representing the month and year when the card expires Tests:  Check that all bytes in the string are digits  Check that the month lies between 1 and 12 and the year is greater than or equal to the current year.  Using the first 4 digits of the credit card number, check that the card issuer is valid by looking up the card issuer table.  Check credit card validity by submitting the card number and expire date information to the card issuer Output:  OK or error message indicating that the card is invalid
    17. 17. Agile vs Waterfall  Ability to change
    18. 18. Agile vs Waterfall  Visibility
    19. 19. Agile vs Waterfall  Successful
    20. 20. Agile vs Waterfall
    21. 21. Agile vs Waterfall Agile Waterfall Small, medium project Big project Less architectural Better architectural
    22. 22. Source  http://www.agilemodeling.com  http://www.codeproject.com/Articles/6 04417/Agile-software-development- methodologies-and-how-t  Bài giảng môn lập trình cấu trúc, Cô Giang

    ×