+ All Categories
Home > Documents > FDD by Tooba

FDD by Tooba

Date post: 06-Apr-2018
Category:
Upload: cancerian-rock
View: 224 times
Download: 0 times
Share this document with a friend
25
FEATURE DRIVEN DEVELOPMENT Presented by TOOBA AHTRAM
Transcript
Page 1: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 1/24

FEATURE DRIVEN DEVELOPMENT 

Presented by 

TOOBA AHTRAM

Page 2: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 2/24

 Agenda

Definition of F DD

History of F DD

Why F DD?  Process of F DD

Technical and Financial benefits

Future W ork 

Conclusion

2

Page 3: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 3/24

Quot ations

I feel a recipe is only a t heme w hich an

intelligent cook can play each time wit h a

variation

( Madame Benoit)

T he ultimate judgment of progress is t his:

measurable results in reasonable time

(Rober t Anthony  )

3

Page 4: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 4/24

FEATURE DRIVEN DEVELOPMENT 

F DD is an agile software development process Small blocks of client-valued functionality 

Called Features 

5 stages

Emphasizes Quality at each step(stages)

Delivers frequent, tangible, working results

 Accurate & meaningful Project Progress

Tracking

Highly iterative

4

Page 5: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 5/24

H i story of FDD

5

Page 6: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 6/24

Int r od uction

Birt h of F DD:

Singapore project deemed undoable

2 years

3,500 pages of use case

Object model wit h hundreds of classes

T housands of attributes (but no met hods)

 And NO CO

DE AT ALL!

 Jeff De Luca

Page 7: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 7/24

T he pr obl em: accommodati ng

shor t er and shor t er busi ness c y cl es

Many software projects

exceed budget 

blow schedule

deliver somet hing less t han desired 

Blow schedule

>180days = HIGH RISK! Why ?  

Business rapidly changing

Page 8: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 8/24

T he solution:  f eature-dr iv en

dev elo pment 

Developers like F DD.

Managers like it too. 

Clients like it too. 

Yes, developers and managers and clients like

F DD. Amazing yet true.

Page 9: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 9/24

WHY FDD?? 

To enable and enforce t he repeatable delivery 

of working software in a timely manner wit h

highly accurate and meaningful information to

all key roles inside and outside a project .

Many long & complex Projects fail 

Heavy process approach doesnt work 

F DD supports

Building complex software systems

Large development teams 9

Page 10: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 10/24

W hat  i s a Feature? 

Definition: small function expressed in client-

valued terms

Split into respective domains Features are to be small in t he sense t hey 

will take no more t han two weeks to complete

Features t h

at appear to take longer are to bebroken up into a set of smaller features

Note: Two weeks is t he maximum, most 

 features take far less time ( 1 - 5 days)10

Page 11: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 11/24

W hat  i s a Feature? 

Examples:

Calculate t he total of a sale

Validate t 

he password of a user 

 Aut horize t he sales transaction of a customer 

11

Page 12: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 12/24

Rol es & Responsibiliti es

Pr i mary Rol es Project Manager (PM)

C hief Architect (CA)

Development Manager 

C hief Programmers

Class Owners

Domain Experts

12

Page 13: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 13/24

Rol es & Responsibiliti es

Su ppor ti ng Rol es Tester 

Deployer 

Tech

nical W 

riter 

13

Page 14: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 14/24

FDD Pr oc ess

Step # 1: Develop an Overall Model 

Step #2: Build a Features List 

Step #3: Plan By Feature

Step #4: Design By Feature

Step # 5: Build By Feature

14

Page 15: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 15/24

15

Page 16: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 16/24

I t erations of Desi gn by Feature &

Buil d by Feature

16

Page 17: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 17/24

Dev elo p an Ov erall Model 

Identify all t he components of your system

SIS of Agriculture

Admission System

Page 18: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 18/24

F DD emphasizes t he ability to provide accurate,

meaningful, and timely progress information to

all stakeholders wit hin and outside t he project 

Feature Milestones

Repor ti ng

Page 19: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 19/24

TEC H NICAL & FINANCIAL BENEFITS

Technical Benefits:

Efficiency on bigger projects

Focus on high-payoff results.

Easily adaptable

Reduction of risks

High quality 

T he completion of each feature results in

delivered, working software of immediate benefit 

limiting t he work in progress to a small number of 

 features keeps focus 19

Page 20: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 20/24

TEC H NICAL & FINANCIAL BENEFITS

Financial Benefits:

No overbudget 

No tec

hnology constraints

No Overtime

Efficient planning and reporting functionalities

20

Page 21: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 21/24

Pr os and C ons

Pr os

Support for iterative development cycles

Support for code reviews and inspection

Short, iterative, feature-driven life cycles are best 

Good processes move to t he background so t he team

members can focus on results

To satisfy t he customer t hrough early and continuous

delivery of valuable software Strong Coordination

C ons:

Not implemented too much21

Page 22: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 22/24

FUTURE W ORK 

T he future work is to study t he usefulness of 

t his met hodology in a variety of domains,

It is also important to collect cases of feature(or aspect) conflict/subversion, and abstract 

t he resolution pattern for t he interworking of 

 features.

Page 23: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 23/24

Summary & C onclusion

F DD was initially created for and is more

geared towards large project teams

F DD

puts less focus on initial design and quickly gets to t he point w here t he team can

deliver new functionality to t he project feature

by feature

F DD supports

Building complex software systems

Large development teams23

Page 24: FDD by Tooba

8/3/2019 FDD by Tooba

http://slidepdf.com/reader/full/fdd-by-tooba 24/24

Re f erenc es

http://www .wisegeek .com/w hat-is-feature-

driven-development .htm

http://www 

. featuredrivendevelopment 

.com

http://www .nebulon.com

http://www .toget hersoft .com

( h

ttp://borland .

com) Palmer, Stephen and Fesling, John, A Practical 

Guide to Feature Driven Development  ,

Prentice-Hall, 200224


Recommended