Evolutionary Models

Views:
 
Category: Education
     
 

Presentation Description

No description available.

Comments

By: PritamHP (2 week(s) ago)

hi, can u send me the slide? pritampatil020@gmail.com

By: KiO1029 (7 month(s) ago)

hi, can u send me the slide? kio_lfk1987@hotmail.com

By: suba17 (20 month(s) ago)

plse send me this npresentation for me , my email:sharaindya@gmail.com

By: Angel29 (20 month(s) ago)

ok sure

 

By: seekerznhackerz (22 month(s) ago)

can i download it?... please send this to my email: seekerznhackerz@yahoo.com.. thanks...

By: raghu2314 (26 month(s) ago)

how to download this presentation

Presentation Transcript

Slide 1: 

Advance Software Engineering Comparison of Process Models (Evolutionary process Models)‏ By Aafia Kamal Saadia Aziz MS-SE-1 ` 1

Slide 2: 

Software Process Models Process Model is a series of steps through which a software product progresses A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective Typically, the product is specified, designed, implemented and once it is operational, it is maintained 2

Slide 3: 

Evolutionary Process Models Allows the software to evolve as need grows or become better understood, or become defined Each delivery becomes more complex, with addition of new features/functions Goal of Evolutionary Models is Extensibility 3

Slide 4: 

Evolutionary Process Models Some Evolutionary Models are Prototyping Model Concurrent Development Model Spiral Model 4

Slide 5: 

Prototyping Model Used when Short amount of time for product Needs revisions done after release Requirements are fuzzy Developer is unsure of The efficiency of an algorithm The adaptability of the OS User interface is not well defined 5

Slide 6: 

6

Slide 7: 

Prototyping Model Advantages Delivers a working system early & cheaply Avoids building systems to bad requirements Fits top-down implementation and testing strategies Disadvantages Users may become frustrated: Constant system volatility Often unreliable systems 7

Slide 8: 

The Concurrent Development Model Developers write requirements, design, code, test, and integrate tests all at the same time Any of the activities of a project may be in a particular state at any one time Under development Awaiting changes Under revision Under review, etc 8

The Concurrent Development Model : 

The Concurrent Development Model Used when Many times used for Client/Server applications

Slide 10: 

Concurrent Development Model Advantages Product can be turned over fairly quickly Disadvantages Possible miscommunication between different developing parties 10

Slide 11: 

Spiral Model First proposed by Boehm in 1987 An evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model Before commencing each phase attempt is made to control or resolve risks 11

Slide 12: 

Spiral model If it proves to be impossible to resolve all the significant risk than the project is terminated immediately Used when Should be used for the development of large scale systems and software 12

Slide 13: 

Spiral Model Framework activities Customer Communication - tasks required to establish effective communication Planning - tasks required to define resources, timelines and other project related information Risk Analysis - tasks required to assess the technical and management risks. 13

Spiral Model : 

Spiral Model Framework activities continu.. Engineering - tasks required to build one or more representation of the application Construction & Release - tasks required to construct, test and support (e.g. Documentation and training) Customer evaluation - tasks required to obtain periodic customer feedback

Slide 15: 

15

Slide 16: 

Spiral Model Advantages Emphasis risk which is often ignored Emphasis risk reduction techniques Provides Check points for Project cancellation Constant customer involvement and validation Disadvantages Full analysis requires training, skill, and considerable expense, so it may only be appropriate for large projects run by large companies 16

Slide 17: 

A Final Comment on Evolutionary Processes Modern computer s/w [development] is characterized by Continual change Tight deadlines Need for customer/user satisfaction Evolutionary process models were invented to address exactly these issues 17

Slide 18: 

Why Evolutionary Software Development Works (Alan MacCormack)‏ HBS professor Alan MacCormack discusses recent research proving the theory that the best approach is evolutionary. A two-year empirical study, reveals thought-provoking information from the Internet-software industry The researchers analyzed data from 29 completed projects and identified the characteristics most associated with the best outcomes Successful development was evolutionary in nature 18

Slide 19: 

Why Evolutionary Software Development Works (Alan MacCormack)‏ Companies first would release a low-functionality version of a product to selected customers at a very early stage of development Thereafter work would proceed in an iterative fashion, with the design allowed to evolve in response to the customers' feedback The most remarkable finding was that getting a low-functionality version of the product into customer's hands at the earliest opportunity improves quality dramatically 19

Slide 20: 

Four Software Development Practices That Spell Success Analysis of Internet-software :development projects in a recent study uncovered successful practices An early release of the evolving product design to customers Daily incorporation of new software code and rapid feedback on design changes A team with broad-based experience of shipping multiple projects Major investments in the design of the product architecture 20

Slide 21: 

Use of the Models in Practice 21

Slide 22: 

References Lecture slides by Ian Summerville accompanying his classic textbook software engineering, see http://www.comp.lancs.ac.uk/computing/resources/ser/ Sofware Engineering A Practitioner's Approach by Roger S Pressman Why Evolutionary Software Development WorksPublished: April 30, 2001 Author: Alan MacCormack http://hbswk.hbs.edu/item/2201.html 22

Slide 23: 

THANK YOU!Questions and Answers