Recently MeroSpark is lunched with more features and services, now you can ask your question, sell your books, share your notes and many more. Visit now and create your account to take full advantage of MeroSpark.

Evolutionary Software Process Model | Software Engineering | BSc.CSIT 6th Sem

Download our Android App from Google Play Store and start reading Reference Notes Offline.

evolutionary software process modelEvolutionary Software Process Model,
Software Engineering Notes | Sixth Semester,
BSc.CSIT | Tribhuvan University (TU)

Evolutionary Software Process Model
Evolutionary software process models are iterative in nature. 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.Evolutionary development model

  • The linear sequential model is designed for straight-line development. In essence, this waterfall approach assumes that a complete system will be delivered after the linear sequence is completed.
  • The prototyping model is designed to assist the customer (or developer) in understanding requirements. In general, it is not designed to deliver a production system.
  • The evolutionary nature of software is not considered in either of these classic software engineering paradigms.
  • Evolutionary model is based on the idea of developing an initial implementation, exposing to this to user comment and refining it through many versions until an adequate system has been developed.
  • Specification, development and validation activities are interleaved rather than separate, with rapid feedback across activities.
  • Evolutionary models are iterative. They are characterized in a manner that enables software engineers to develop increasingly more complete versions of the software.

There are two fundamental types of evolutionary development:

  • Exploratory development
    Objective is to work with customers and to evolve a final system from an initial outline specification. Should start with well-understood requirements
  • Throw-away prototyping
    Objective is to understand the system requirements. Should start with poorly understood requirements


  • An evolutionary approach is often more effective than waterfall approaches in producing systems that meet the immediate needs of customers.
  • The advantage of software process that is based on an evolutionary approach is that the specification can be developed incrementally.
  • As users develop a better understanding of their problem, this can be reflected in the software system.

Problems towards engineering and management perspective:

  • The process is not visible: Managers need regular deliverables to measure progress. If systems are developed quickly, it is not cost-effective to produce documents that reflect every version of the system.
  • Systems are often poorly structured: Continual change tends to corrupt the software structure. Incorporating software changes becomes increasingly difficult and costly.
(Visited 1,686 times, 1 visits today)

Posted By : Digvijay | Comment RSS | Category : Sixth Semester
Tag :

Post a Comment

Your email is never published nor shared. Required fields are marked *


Wordpress DMCA
Community | Toolbar | Android App | Founder/Developer : Hari Prasad Chaudhary | CSIT Portal Manager : Digvijay Chaudhary