Abstract
In this work explored evolution of software lifecycle models firstly to lightweight and then to agile software development methodologies, and factors that have led to a search for ways to improve approaches to software development. Also compared "outdated" development designing approaches with modern flexible and made conclusions whether the advantage of the latter over the firsts is absolute and whether or not they and only they should be used in practice or maybe older approaches still have their advantages and it is too early to exclude them.
Highlights
Waterfall The waterfall lifecycle model is probably the first to be met by a person who starts to study the development methodology
It has a phased structure, as well as a waterfall model, but pays a lot of attention to verification and testing of the product being done at the same time as the development phase (Fig. 1.3), this model is optimal for systems where a smooth operation is important [4]
Incremental lifecycle model A significant step towards Agile methodologies was made by separating the entire product development process into several development cycles, each cycle passing through the same phases (Figure 1.4)
Summary
In this work evolution of software lifecycle models is explored. Firstly to lightweight and to agile software development methodologies, and factors that have led to a search for ways to improve approaches to software development. Incremental lifecycle model A significant step towards Agile methodologies was made by separating the entire product development process into several development cycles, each cycle passing through the same phases (Figure 1.4) Such decomposition instead of a large inert project, which needs to be tested as a whole, presents some small easy-to-create modules that are much easier to test and fix. Kanban is based on a prioritized list of tasks and progress stages of a specific task capacity, for example: "to processing", "in development", "in testing" and "implementation" (Figure 2.1) This methodology is based on the priorities and developers' capabilities in terms of parallel work, rather than on time. It is impossible to add tasks to the sprint even urgent and very important, all unfulfilled tasks are returned to the task list for consideration at the sprint planning stage
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
