Software Development Models
•In-house
•Onshore
•Offshore
•Combined
Gene Leybzon, [email protected] 2
In-house
Control
Communication
Culture
Cost
Management Overhead
Need internal expertise and know-how
Be
ne
fitsD
raw
ba
ck
Gene Leybzon, [email protected] 3
On-shore
Ease of product management
Protective legal environment
Same language
Cost
Team scalability
Be
ne
fitsD
raw
ba
ck
Gene Leybzon, [email protected] 4
Offshore
Cost
Team scalability
Language
Communication
Control
Be
ne
fitsD
raw
ba
ck
Gene Leybzon, [email protected] 5
Combined
Cost
Team scalability
Product control
Communication
Limited (local) availability
Be
ne
fitsD
raw
ba
ck
Gene Leybzon, [email protected] 6
Development Process
Gene Leybzon, [email protected] 7
Waterfall
Gene Leybzon, [email protected] 8
Emphasis on planning
Project divided into sequential phases
Works well when requirements are well defined ahead of time
Works with in-house and offshore models
Software prototyping
Gene Leybzon, [email protected] 9
Works better when requirements are not known ahead of time
Works with in-house and combined development models
Software prototyping
Gene Leybzon, [email protected] 10
Works better when requirements are not known ahead of time
Works with in-house and combined development models
Will not work with offshore
Incremental development
Gene Leybzon, [email protected] 11
Works well when requirements are not fully known ahead of time
Works with offshore and combined development models
Rapid application development
Gene Leybzon, [email protected] 12
Breaking product into smaller components
Active user involvement is the key
Works with in-house and combined development models
Agile development
Gene Leybzon, [email protected] 13
Adaptive development
Active user involvement is critical
Works with in-house and combined development models
Summary
In-house Onshore Offshore Combined
Waterfall
Prototyping
Incrementa
l
Rapid
Agile
Gene Leybzon, [email protected] 14
Top Related