Software development life cycle
-
Upload
dushyant-singh -
Category
Software
-
view
101 -
download
0
Transcript of Software development life cycle
![Page 1: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/1.jpg)
Software Development life
cycle
Dushyant singh
![Page 2: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/2.jpg)
Introduction • It specifies the various phases/workflows of the software process, such as the requirements, analysis (specification), design, implementation, and postdelivery maintenance, and the order in which they are to be carried out.
![Page 3: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/3.jpg)
Choosing Appropriate model • Increased development speed • Increased product quality • Improved tracking & control• Improved client relations • Decreased project risk • Decreased project
management overhead
![Page 4: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/4.jpg)
Common life cycle model
• Waterfall• Prototype • Spiral
![Page 5: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/5.jpg)
Waterfall model
Analysis
DesignDevelopment
Testing
VerificationMAINTENANCE
![Page 6: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/6.jpg)
Waterfall plus points
• Easy to understand, easy to use
• Provides structure to inexperienced staff
• Milestones are well understood
• Sets requirements stability
![Page 7: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/7.jpg)
Waterfall weakness• All requirements must be fully
specified upfront • Can give a false impression of
progress• Does not reflect problem-
solving nature of software development – iterations of phases
• Little opportunity for customer to preview the system (until it may be too late)
![Page 8: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/8.jpg)
Prototype model
DesignImplement
TestMaintain
Requirementsgathering
Quick design
Build prototype Refine requirements incorporating
Customer suggestion
Customer evaluationOf prototype
AcceptanceBy
customer
Prototypedevelopm
ent
Iterativedevelopme
nt
![Page 9: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/9.jpg)
Prototype advantages • Provides a working model to the
user early in the process , enabling early assessment and increasing user confidence.
• The developer gains experience and insight by developing a prototype , thereby resulting in better implementation of requirements.
• Helps in reducing risks associated with the project.
![Page 10: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/10.jpg)
Spiral model
Spiral model is an evolutionary software process model which is a combination of an iterative nature of prototyping and systematic aspects of traditional waterfall model.
![Page 11: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/11.jpg)
When Required ?
• When costs and risk evaluation is important.
• For medium to high-risk projects.
• Users are unsure of their needs.• Requirements are complex.• Significant changes are
expected.
![Page 12: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/12.jpg)
![Page 13: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/13.jpg)
pros • Changing requirements can be
accommodated.• Allows for extensive use of
prototypes• Requirements can be captured more
accurately.• Users see the system early.• Development can be divided into
smaller parts and more risky parts can be developed earlier which helps better risk management.
![Page 14: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/14.jpg)
cons• Management is more complex.• End of project may not be known
early.• Not suitable for small or low risk
projects and could be expensive for small projects.
• Process is complex• Spiral may go indefinitely.• Large number of intermediate
stages requires excessive documentation.
![Page 15: Software development life cycle](https://reader031.fdocuments.in/reader031/viewer/2022022413/58eff9281a28ab05088b46eb/html5/thumbnails/15.jpg)
Thank you