Top Banner
Agile software development
22
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Agile software development

Agile software development

Page 2: Agile software development

Nội dung

1. Waterfall Model 2. Agile software development3. Extreme Programming (XP)4. Agile vs Waterfall  

Page 3: Agile software development

Waterfall Model"From the 1970 IEE paper

"Managing the Development of Large Software Systems“

Winston Royce's Waterfall Model 

Page 4: Agile software development

Waterfall Model

Page 5: Agile software development

Waterfall ModelRequirement

◦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

Page 6: Agile software development

Agile software development

Page 7: Agile software development

ValuesIndividuals and

interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Page 8: Agile software development

Principles

1) 12 principles

Page 9: Agile software development

Extreme Programming (XP) 

Agile development is not a methodology. It is an umbrella term that describes several agile methodologies

Page 10: Agile software development

PracticesIncremental planningSmall Releases Continuous integration Test first developmentRefactoringPair ProgrammingCollective OwnershipOn-site CustomerSimple design

Page 11: Agile software development

Cycle

Page 12: Agile software development

Extreme Programming (XP) 

Page 13: Agile software development

ExampleStory card for document

downloading

Page 14: Agile software development

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.

Page 15: Agile software development

Task cards for document downloading

Page 16: Agile software development

Test: Test credit card validityInput: 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

Page 17: Agile software development

Agile vs Waterfall Ability to change

Page 18: Agile software development

Agile vs Waterfall Visibility

Page 19: Agile software development

Agile vs Waterfall Successful

Page 20: Agile software development

Agile vs Waterfall

Page 21: Agile software development

Agile vs Waterfall Agile Waterfall

Small, medium project

Big project

Less architectural Better architectural