0
6.3kviews
Types of Process Model
1 Answer
2
87views

Prescriptive process models define a set of activities, actions, tasks, milestones, and work products that are required to engineer high-quality software. These process models are not perfect, but they do provide a useful road map for software engineering work.

A prescriptive process model populates a process framework with explicit task sets for software engineering actions.

Waterfall Model

enter image description here

Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the next phase sequentially.

  • Requirement Gathering and analysis − All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification document.

  • System Design − The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture.

  • Implementation − With inputs from the system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing.

  • Integration and Testing − All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.

  • Deployment of system − Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market.

  • Maintenance − There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

Advantages:

  • Simple and easy to understand and use

  • Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review process.

  • Phases are processed and completed one at a time.

  • Works well for smaller projects where requirements are very well understood.

  • Clearly defined stages.

  • Well understood milestones.

  • Easy to arrange tasks.

  • Process and results are well documented.

Disadvantages:

  • It is difficult to define all requirements at the beginning of a project.

  • This model is not suitable for accommodating any change.

  • A working version of the system is not seen until late in the project’s life.

  • It does not scale up well to large projects.

  • Real projects are rarely sequential.

  • High amounts of risk and uncertainty.

Please log in to add an answer.