Showing posts with label software process model. Show all posts
Showing posts with label software process model. Show all posts

Describe the Waterfall Software Process Model with Advantages and Disadvantages


Waterfall Software Process Model:

Waterfall model software process model was derived from general system engineering process and it is so called as the stages go top to bottom and while one stage of the process is complete it moves to the next stage and not supposed to come back to any previous stage. That is one stage is supposed to be started if and only if the previous stage is finished and approved to move on to the next stage. However, in practice, things doesn't happen this way.

Following is an illustration of the involved stages of Waterfall model.

Describe Formal Methods Software Process Model

Formal Methods Model : 

The formal methods model encompasses a set of activities that leads to formal mathematical specification of computer software. Formal methods enable a software engineer to specify, develop, and verify a computer-based system by applying a rigorous, mathematical notation.

Describe The Component Base Development Software Process Model

Component Based Development:

The component-based development (CBD) model incorporates many of the characteristics of the spiral model. It is evolutionary in nature, demanding an iterative approach to the creation of software. However, the component-based development model composes applications from prepackaged software components, called classes.

Describe the Spiral Software Process Model

Spiral Model:

The spiral model is an evolutionary software process model that combines the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model. Using the spiral model, software is developed in a series of incremental releases. During early iterations, the incremental release might be a paper model or prototype. During later iterations, increasingly more complete versions of the engineered system are produced.


Describe the Incremental Software Process Model


Incremental Model:

The incremental model combines elements of the linear sequential model with the iterative philosophy of prototyping. The incremental model applies linear sequences in a staggered fashion as calendar time progresses. Each linear sequence produces a deliverable “increment” of the software.


Describe Evolutionary Software Process Model

Evolutionary Software Process Mode:

Evolutionary software models are iterative. They are characterized in manner that enables the software engineers to develop increasingly more complete version of a software. That is, initially a rapid version of the product is being developed and then the product is developed to more accurate version with the help of the reviewers who review the product after each release and submit improvements. Specification, development and validation are interleaved rather than separate in evolutionary software process model.

Describe the RADSoftware Process Model with Disadvantages


RAD Model

Rapid Application Development (RAD) is an incremental software development process model which is a “high-speed” adaptation of the linear sequential model in which rapid development is achieved by using component-based construction. If requirements are well understood and project scope is constrained, the RAD process enables a development team to create a “fully functional system” within very short time periods, such as in 60 to 90 days.

Describe the Prototyping Software Process Model with Disadvantages


Prototyping Model

Often, a customer defines a set of general objectives for software but does not identify detailed input, processing, or output requirements. In other cases, the developer may be unsure of the efficiency of an algorithm, the adaptability of an operating system, or the form that human/machine interaction should take. In these, and many other situations, a prototyping paradigm may offer the best approach.

Describe the Linear Sequential Software Process Model with Disadvantages


Linear Sequential Model/Waterfall Model/Classic Life Cycle

The linear sequential model, sometimes called the classic life cycle or the waterfall model, suggests a systematic, sequential approach to software development that begins at the system level and progresses through communication, planning, modeling, construction and deployment. The following given figure illustrates the linear sequential model for software engineering. This is the oldest paradigm of software engineering.