Define software process model software engineering

Change Language. Related Articles. Introduction of Software Engineering. Software Requirements. Software Testing and Debugging.

Table of Contents. Improve Article. Save Article. Like Article. Next Software Engineering Incremental process model. Operating Procedures — Set of step-by-step instructions compiled by an organization to help workers carry out complex routine operations. There are four basic key process activities: Software Specifications — In this process, detailed description of a software system to be developed with its functional and non-functional requirements. Software Development — In this process, designing, programming, documenting, testing, and bug fixing is done.

Software Validation — In this process, evaluation software product is done to ensure that the software meets the business requirements as well as the end users needs.

Software Evolution — It is a process of developing software initially, then timely updating it for various reasons. Software Crisis : Size and Cost — Day to day growing complexity and expectation out of software.

Software are more expensive and more complex. Quality — Software products must have good quality. Delayed Delivery — Software takes longer than the estimated time to develop, which in turn leads to cost shooting up. Software Process Model: A software process model is an abstraction of the actual process, which is being described. It can also be defined as a simplified representation of a software process. Each model represents a process from a specific perspective. Basic software process models on which different type of software process models can be implemented: A workflow Model — It is the sequential series of tasks and decisions that make up a business process.

All the requirements are known at the beginning of the project, hence it is easy to manage. It avoids overlapping of phases because each phase is completed at once. This model works for small projects because the requirements are understood very well. This model is preferred for those projects where the quality is more important as compared to the cost of the project. Disadvantages of the waterfall model This model is not good for complex and object oriented projects.

It is a poor model for long projects. The problems with this model are uncovered, until the software testing. The amount of risk is high. Incremental Process model The incremental model combines the elements of waterfall model and they are applied in an iterative fashion. The first increment in this model is generally a core product.

Each increment builds the product and submits it to the customer for any suggested modifications. The next increment implements on the customer's suggestions and add additional requirements in the previous increment. This process is repeated until the product is finished. For example, the word-processing software is developed using the incremental model. Advantages of incremental model This model is flexible because the cost of development is low and initial product delivery is faster.

It is easier to test and debug during the smaller iteration. The working software generates quickly and early during the software life cycle. The customers can respond to its functionalities after every increment. Disadvantages of the incremental model The cost of the final product may cross the cost estimated initially.