Downloaded 334 times
More Related Content
Similar to Agile and plan based development processes
Agile and plan based development processes
- 1. Agile and plan-basedsoftware processes Software Engineering 10
- 2. Software process A structuredset of activities for software development
- 3. Specification – definingwhat the software should do Design– defining the organization and structure of the system
- 4. Implementation and testing– programming the system and checking that it does what the customer wants; Evolution – changing the system in response to changing customer needs.
- 5. Implementation and testing– programmingthe system and checking that it does what the customer wants;
- 6. Plan-driven and agileprocesses
- 7. Plan-driven processes areprocesses where all of the process activities are planned in advance and progress is measured against this plan.
- 8. In agile processes,planning is incremental and it is easier to change the plan and the software to reflect changing customer requirements.
- 9. In practice, mostpractical processes include elements of both plan-driven and agile approaches.
- 10. Different types ofsystem need different software processes
- 11. The waterfall modelof software processes
- 12. The waterfall model Chapter2 Software 1230/10/2014
- 13. The waterfall modelis used in systems engineering projects where a system is developed at several sites. The plan-driven nature of the waterfall model helps coordinate the work.
- 14. Inflexible partitioning ofthe project into distinct stages makes it difficult to respond to changing customer requirements.
- 15. Inflexible partitioning ofthe project into distinct stages makes it difficult to respond to changing customer requirements.
- 16. Waterfall processes areonly appropriate when the requirements are well-understood and changes limited during the design process. Few business systems have stable requirements. .
- 17.
- 18. Based on incrementaldevelopment where process activities are interleaved Short iterations (2-4 weeks) .
- 19. Minimal documentation Aim isto be responsive to change and reduce the time required to deliver useful functionality to users .
- 20. Incremental development Chapter 2Software 2030/10/2014
- 21. The cost ofimplementing changes to customer requirements is reduced. The amount of analysis and documentation that has to be redone is less than is required with the waterfall model.
- 22. It is easierto get customer feedback on the development work. Customers can comment on demonstrations of the software and see how much has been implemented.
- 23. Rapid delivery anddeployment of useful software to the customer is possible. Customers are able to use and gain value from the software earlier than is possible with a waterfall process. .
- 24.
- 25. The process isnot visible. Documents help managers assess progress but in agile processes systems it is not cost-effective to document every version of the system. .
- 26. System structure tendsto degrade as new increments are added. Unless time and money is spent on refactoring to improve the software, regular change usually corrupts its structure. .
- 27.
- 28. Systems are integratedfrom existing components or application systems. Reused elements may be configured to adapt their behaviour and functionality to user requirements
- 29. Systems are integratedfrom existing components or application systems. Reused elements may be configured to adapt their behaviour and functionality to user requirements
- 30. Types of reusablesoftware .
- 31. Stand-alone application systemsthat are configured for use in a particular environment. .
- 32. Reusable components thatare integrated with other reusable and specially written components .
- 33. Web services thatare developed according to service standards and which are available for remote invocation. .
- 34. Reuse-oriented software engineering Chapter2 Software 3430/10/2014
- 35. Reuse based developmentis a mix of plan-based and agile development
- 36. Requirements are plannedin advance but an iterative and agile approach can be taken to design and implementation
- 37. Requirements specification Software discoveryand evaluation Requirements refinement .
- 38. Plan-based Long lifetime, criticaland embedded systems .
- 39.
- 40.
- 41. Download the slidesused here from http://www.slideshare.net/sommerville-videos