Scribd
Upload
53 views

Chapter 4 Agile - Development

Development

Uploaded by

Muhammad Alwi Basyir
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
53 views

Chapter 4 Agile - Development

Development

Uploaded by

Muhammad Alwi Basyir
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

Software Engineering: A Practitioner’s Approach,

6/e

copyright © 1996, 2001, 2005


R.S. Pressman & Associates, Inc.

For University Use Only


May be reproduced ONLY for student use at the university level
when used in conjunction with Software Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.
“We are uncovering better ways of developing software
by doing it and helping others do it. Through this work
we have come to value:
•Individuals and interactions over processes and
tools
•Working software over comprehensive
documentation
•Customer collaboration over contract negotiation
•Responding to change over following a plan
That is, while there is value in the items on the right, we
value the items on the left more.”
Kent Beck et al



user stories
cost
deliverable increment
commitment
project velocity

KIS principle
CRC cards
spike solutions

refactoring

construction of a unit test


pair programming

unit tests are executed daily


 “Acceptance tests”
spike solut ions
simple design
prot ot ypes
CRC cards
user st ories
values
accept ance t est crit eria
it erat ion plan

ref act oring

pair
programming

Release
sof t ware increment
unit t est
project v elocit y comput ed cont inuous int egrat ion

accept ance t est ing


 Mission-driven
 Component-based focus
time-boxing
risks
collaboration
learning
adapt ive cycle planning Requirement s gat hering
uses mission st at ement JAD
project const raint s mini-specs
basic requirement s
t ime-boxed release plan

Release
sof t ware increment
adjust ment s f or subsequent cy cles
component s implement ed/ t est ed
f ocus groups f or f eedback
f ormal t echnical reviews
post mort ems
 www.dsdm.org

 Active user involvement is imperative.


 DSDM teams must be empowered to make decisions.
 The focus is on frequent delivery of products.
 Fitness for business purpose is the essential criterion for acceptance of deliverables.
 Iterative and incremental development is necessary to converge on an accurate business
solution.
 All changes during development are reversible.
 Requirements are baselined at a high level
 Testing is integrated throughout the life-cycle.
DSDM Life Cycle (with permission of the DSDM consortium)


packets
 Testing and documentation are on-going

sprints backlog

 Meetings are very short

demos
Scrum Process Flow (used wit h permission)

family of process models


maneuverability
 Face-to-face communication
reflection workshops

 “features”
 feature

feature template
 <action> the <result> <by | for | of | to> a(n) <object>

features list plan by feature


Reprinted with permission of Peter Coad

 Model with a purpose


 Use multiple models
 Travel light
 Content is more important than representation
 Know the models and the tools you use to create them
 Adapt locally

You might also like