1. Methodology
For requirement and gathering analysis lets look at the map
Design β Implement β Test βDeploy β Maintainence
- High amount of risk and un-certaincy.
- No working software is produced until late during the life cycle.
- Not a good model for complex and object oriented projects.
- Not suitable for the project where requirment are not a moderate of a high risk of changing.
- Once the application in its testing phase, it is very difficult to go back and change something, that was not to well for the project.
In the agile methodology each project is broken upto into several iterations.' All the iterations should be of the same time duration (close to 2 to 8 weeks).
At the end of each iteration, a working product should be delivered.
Analyze β Plan β Design β Bulid β Test β Deploy
So design , Bulid and Test is iterating unil the final Product is delivered.Design β Bulid β Test
Design β Bulid β Test
Design β Bulid β Test
β
Final Deployment to Server