Introduction
In recent century, there has being a great speed with the innovation and software development which is playing vital roles in this new era. Systems are created to solve problems, it is an organized way of dealing with problems. Therefore, the need to ensure and improve ongoing development for software developers has been at the core literature discussion among scholars within the computer science and project management field. (Deephosuse at al…, 1996). On the other hand, iterative model proffer opportunity to incorporate a life cycle that follows the process of planning, gathering requirements, u8designing, implementation, verification and evaluation for continuous improvement in the development of software. This article will elaborate more of iterative model, considering its origin, implementation process, the merits and demerits associated with the use of iterative life cycle and conclusion.
THE PROCESS OF ITERATIVE LIFE CYCLE MODEL
Unlike the more traditional waterfall model, which focuses on a significant ordered process of system development stages, the iterative model is best thought of as a cyclical process. After an initial planning phase, a stages are repeated over and over, with each completion of the cycle incrementally improving and iterating on the software. Upgrades can rapidly be perceived and executed all through every emphasis, enabling the following cycle to be at any rate imperceptibly superior to the last.
Planning & Requirements: As with a majority of development project, the first planned step is go through an the foundation planning stage to map out the key specification documents, establish software or hardware requirements , and generally ready for the next level of the cycle.
Analysis & Design: Once planning is complete, an analysis is performed to pin point the required business minded logic, database models, and what will be required at this stage in the project. This can be seen as the design stage, with the hope to find any technical requirements such as languages, data layers, services, etc. That will be used in plan to meet the needs of the stage.
Implementation or coding: This is the third stage of the process where implementation actually takes place. Followed by the coding process. All arranging, particular, and structure docs so far are coded and executed into this beginning of the cycle project.
Testing: After implementation phase, the next step is to go through a series of testing procedures to identify and locate any potential bugs or problems that may have cropped up. During this stage all types of utility testing like unit testing, integration testing, system testing, acknowledgment testing are done and non-useful testing.
Evaluation: Once all main stages have been completed, it is time for an evaluation of development up to this stage. This permits the whole group, and in addition customers or other outside gatherings, to inspect where the task is at, where it should be, what can or should change, etc. This is the essential part of the entire iterative model, whereby the most recently built iteration of the software, as well as all feedback from the evaluation process, is brought back to the planning and development stage at the top of the list, and the process follows its cyclical patterns.
Figure 1.0: Iterative Life-Cycle Model
THE ADVANTAGES OF USING ITERATIVE MODEL
The greatest advantage of this model will be that, it is executed Throughout those prior phases for product advancement process, which permits developers What’s more testers to Figure practical or configuration related flaws as right on time Similarly as possible, which further allows them to take corrective measures in a limited budget. Other benefits or advantages of this model are:
• Some working functionality can be developed and early in the system development life cycle (SDLC).
• It is undoubtedly adaptable to the ever modifying needs of the project as well as the client.
• It is best suited for agile organizations.
• It is very effective to change the scope or requirements in Iterative model.
• Parallel development can be planned.
• Testing and debugging during iteration is easy.
• problems and resolved during iteration; and each iteration is an easily handle.
• In iterative model take little time is spent on documenting. But it’s take more time is given for designing.
• One can get reliable user feedback, when presenting blueprints of the product to users for their criticism.
THE DISADVANTAGES OF USING ITERATIVE MODEL
Even , iterative model is extremely beneficial, there are some drawbacks such as, each phase of an iteration is rigid with no overlaps. system architecture or design issues may arise because not all requirements are gathered in the beginning of the life cycle. Other disadvantages of iterative model are:
• More material goods may be required.
• cost of change is lesser, but it’s not suitable for changing requirements.
• More management attention is required.
• It is suitable for big projects.
• Highly skilled resources are needed for skill analysis.
• Project progress is highly dependent on the high risk analysis.
• Defining increments may needed definition of the complete system.
Conclusion:
A software is developed with many different methodologies. It need tools, models, and other elements to get perfect result. Iterative model, is best development technique that give permission small scale software development effortlessly. It is one of the key practices in Agile Development methodologies, in which steps are repeated as the project progresses with requirements. It also gives an opportunity to identify and build any big requirement or design flaws throughout the process because of its iterative nature.
References
• https://www.tutorialspoint.com/sdlc/sdlc_iterative_model.htm
• https://airbrake.io/blog/sdlc/iterative-model
• http://www.professionalqa.com/iterative-model