Iterative Development

-
The iterative development process model counters the third and fourth limitations of the waterfall model and tries to combine the benefits of both prototyping and the waterfall model. The basic idea is that the software should be developed in increments, each increment adding some functional capability to the system until the full system is implemented. The iterative enhancement model  is an example of this approach. In the first step of this model, a simple initial implementation is done for a subset of the overall problem.

Figure: The iterative enhancement model.

The iterative approach is becoming extremely popular, despite some difficulties in using it in this context. There are a few key reasons for its increasing popularity. First and foremost, in today’s world clients do not want to invest too much without seeing returns. In the current business scenario, it is preferable to see returns continuously of the investment made.
Figure: Iterative delivery approach.

Komentar

Posting Komentar

Postingan populer dari blog ini

Rational Unified Process

-
Gambar
RUP proposes that development of software be divided into cycles, each cycle delivering a fully working system. Generally, each cycle is executed as a separate project whose goal is to deliver some additional capability to an existing system (built by the previous cycle). Hence, for a project, the process for a cycle forms the overall process. Each cycle itself is broken into four consecutive phases: – Inception phase – Elaboration phase – Construction phase – Transition phase Figure: The RUP model. One key difference of RUP from other models is that it has separated the  phases from the tasks and allows multiple of these subprocesses to function  within a phase. In waterfall (or waterfall-based iterative model), a phase within  a process was linked to a particular task performed by some process like requirements,  design, etc.
Baca selengkapnya

Timeboxing Model

-
Gambar
In the timeboxing model, the basic unit of development is a time box, which  is of fixed duration. Since the duration is fixed, a key factor in selecting the  requirements or features to be built in a time box is what can be fit into the time  box. This is in contrast to regular iterative approaches where the functionality  is selected and then the time to deliver is determined. Timeboxing changes  the perspective of development and makes the schedule a nonnegotiable and a  high-priority commitment. Figure : Executing the timeboxing process model. Timeboxing is well suited for projects that require a large number of features  to be developed in a short time around a stable architecture using stable  technologies. These features should be such that there is some flexibility in  grouping them for building a meaningful system in an iteration that provides  value to the users.
Baca selengkapnya