There are many kinds of software development methodologies, and in order to pick the right options, you may want to consider researching them a bit. Well, this article is here to help you get started. The following models below are short summaries of what each development strategy can offer to developers and their numerous goals. PrototypingThis type of development approach is most often used in the creation of new prototypes, particularly those programs which have not yet been fully developed. What sets it apart from other types of methodologies is that it is not a complete development methodology in the sense that the focus is on certain parts of the project as opposed to the entire thing. The idea is that by breaking up the project into smaller parts, there are fewer risks to contend with, something which is particularly important in projects which deal with prototypes. IncrementalIncremental development involves putting together several small "Waterfalls," each of whic h is aimed at completing small parts of the system. The main benefit behind this model, as far as software development methodologies are concerned, is that it reduces the inherent risks in a particular project by breaking up the processes into several different parts, and dealing with them in an incremental way. SpiralThe best thing about the Spiral model is that it is a meta-model, which means that it can be used by other models in their own processes. Also, like the incremental model, the Spiral is based on breaking up a project into smaller pieces so as to make them more manageable as well as provide developers with the means of preventing risks from developing throughout the project. However, what sets the spiral model apart is that each of its cycles involves a particular progression through similar steps for each part of the product and progression. As such, iteration is reflected in the preceding and succeeding process. WaterfallAs the most common model among software development methodologies, the waterfall model takes a sequential approach in the development of software. Its approach and basic principles are seen as a steady downward flow, thus giving it the name it has today. The model works like this. First, the project is divided into sequential phases. After that, planning, target dates, budgets and implementation are put forth in one go. It's also worth noting that throughout this process, tight control is exercised over much of the project, thus making it the most rigid approach among all software development methodologies.
No comments:
Post a Comment