Software Development Method
- 1. SOFTWARE DEVELOPMENT METHOD By MEGHAJ KUMAR MALLICK MCA 1st Year 1st Semester MCA/25017/18
- 3. INTRODUCTION Software development is a process by which standalone or individual software is created using a specific programming language. Software development includes numerous steps such as thinking of an idea, designing a rough idea, implementation of the blueprint, testing, bug fixing and many more.
- 6. SOFTWARE DEVELOPMENT METHOD A software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system.
- 9. WATERFALL MODEL The Waterfall Model was first Process Model to be introduced. It is very simple to understand and use. In a Waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phases. Waterfall model is the earliest SDLC approach that was used for software development.
- 10. PRO & CONS OF WATERFALL Requirements are very well documented, clear and fixed. Clearly defined stages. Phases are processed and completed one at a time No working software is produced until late during the life cycle. Poor model for long and ongoing projects. Not a good model for complex and object- oriented projects. PRO CONS
- 12. ABOUT PROTOTYPING The Prototyping Model is a systems development method (SDM) in which a prototype (an early approximation of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed.
- 13. PRO & CONS Easier to manage risk, high risk part is done first. Testing and debugging during smaller iteration is easy. Results are obtained early and periodically. More resources may be required. Not suitable for smaller projects. End of project may not be known which is a risk PRO CONS
- 15. ABOUT INCREMENTAL MODEL The product is designed, implemented and tested incrementally (a little more is added each time) until the product is finished. The product is defined as finished when it satisfies all of its requirements. This model combines the elements of the waterfall model with the iterative philosophy of prototyping.
- 16. PRO & CON Uses divide and conquer for breakdown of tasks. Lowers initial delivery cost. Incremental Resource Deployment. Well defined module interfaces are required. Total cost is not lower. Requires good planning and design. PRO CON