19
INTRODUCTION HIRA KHURSHID BSCS 4TH B EXTREME PROGRAMMING

Hira Xp

Embed Size (px)

Citation preview

Page 1: Hira Xp

INTRODUCTION

HIRA KHURSHID

BSCS 4TH B

EXTREME PROGRAMMING

Page 2: Hira Xp

Extreme Programming

Agile Software Development Methodology

Iterative Lightweight Stresses customer satisfaction

and teamwork

Page 3: Hira Xp

Extreme Programming Model

Page 4: Hira Xp

Planning

User stories

Written by the customers The stories that will be developed in

one of three ways:1. All stories will be implemented

immediately2. The stories with highest value will be

implemented first .3. The riskiest stories will be

implemented first

Page 5: Hira Xp

Release planning meeting Creation of a release plan

document Planning of individual iterations Estimation of user stories in terms

of ideal programming weeks

Page 6: Hira Xp

Make frequent small releases

For valuable feedback Important features are introduced

early

Page 7: Hira Xp

Project velocity How many user stories were

finished during the iteration Poject velocity can then be used

to help estimate delivery dates and schedule and implemented first.

Page 8: Hira Xp

Designing

Simplicity

Needs no explanation Use KIS principle. Design Of extra functionality is

discourage.

Page 9: Hira Xp

CRC cards Class, Responsibilities and

Collaboration Used to represent objects Class written on top Organize the components

Page 10: Hira Xp

system metaphor

Allows consistent naming of classes and methods

Page 11: Hira Xp

Spike solution

A very simple program to explore potential solutions

Page 12: Hira Xp

Refactoring Helps keep the design simple and

keeping code clean and concise

Page 13: Hira Xp

Coding Coding standards

Everybody chooses class names and variable names in the same style

Page 14: Hira Xp

Pair programming Sitting side by side in front of the

monitor One person types The other one thinks strategically increases software quality comes big savings later in the

project.

Page 15: Hira Xp

Sequential integration

Code is integrated together Customer is always available.

Page 16: Hira Xp

On-site Customer

To write user stories To select user stories Developers need to talk with the

customer to get enough detail to complete a programming task

Page 17: Hira Xp

Testing

Unit testing

Written by developer Test only a single class are small

cluster of classes.

Page 18: Hira Xp

Acceptance tests

Created from user stories. Customer verifies the correctness

of the tests. Test the entire system.

Page 19: Hira Xp

Thanks