Abstract This paper contains an analysis of various software process models. Software Process Models and related software development approaches with an example of each approach is considered – Sequential approach (Waterfall model), Incremental approach (Incremental Model), Evolutionary approach (Spiral Model), Specialized approach (Formal Methods Model), Agile approach (Extreme Programming Model) and RUP. This paper describes these models, as well as, it contrasts and compares between these different models.

I. INTRODUCTION

Today, the computer has become a very essential part of our life. It has become crucial as it is used in various fields, such as, education, commerce, industry, medicine and agriculture. Society have become more dependent …show more content…
Waterfall model is one of the oldest models and is mainly used in government projects and it is widely used in many major companies and industries. As this model focuses planning in early phases, it confirms design mistakes before they develop the entire project. Moreover its intensive planning and document make it work well for softwares in which quality of project control is an important concern. The waterfall lifecycle contains of several non-overlapping phases, as shown in the following figure. This model begins with generating system requirements and project requirements and continues with various steps as mentioned above i.e. architectural design, detailed design, coding, testing, deployment and maintenance. This model serves as a baseline for all other lifecycle process models. The steps followed in this model are:
i. Communication: establishes the requirements of the stakeholders and then useful in project requirements gathering. ii. Planning: develops a precise plan of execution of the software. iii. Modelling: builds a model of the software before making the actual system. iv. Construction: develops the actual software following the plan of implementation defined in the planning phase and testing.
v. Deployment: the delivery of final-product to the buyer or customer and project’s …show more content…
Delivery of increments is floundered as calendar time progresses. The first increment acts as the base product giving the functionality to address the core requirements. The floundered release theory permits for learning and giving feedback which can alter some of the buyer requirements in sub successive versions. This kind of approaches is useful when the entire complement of personnel need to finish The software is not available and when there is incapacity to fully describe the required project or to fully construct the set of