Summaries each of your selected software development approaches. Analyses the merits and weaknesses of your selected software development approaches. Use examples of software projects that utilized, or would have benefited from utilizing, to support your analysis. Explain why your software project examples used your selected software development approaches, or why/how your software project examples could have benefited from using your selected software development approaches. Fully state and justify any choices, assumptions or claims that you make using the suggested Learning Resources for this Week and/or your own research.
Agile methodology:– It has the work process like iterations which lasts for max 1 to 4 weeks. It minimises the risk by developing the projects in iterations. This has the concept of scrum which is team consisting of max 6 to 9 people and take up the work like story points. This story points is nothing but the work duration and the amount of work we need to do.
Waterfall Model:- This is the most popular and conceptual model. It has the work proce like the step by step or linear mide. Which means development is done through step by step like one module after one. If the previous module is not comoleted then we can’t able to start the new module. Waterfall Model will standardise and departmentalise the things in the process.
Merits and weaknesses of the above approaches:-
Agile model merits:-
- Agile model is very efficient to deliver the projects as specified.
- In this the project delivery will be happened frequently so that the communication with the client will be more. So that it will be easy to get the requirements.
- Adaptation to the changes will be happened frequently so that the knowledge will be enhanced.
- This type of working mode can be handled by the experienced programmers only freshers can’t handle.
- Sometimes for some larger modules we can’t assess the effort and time required.
- If the client didn’t have the clear goal the project will not be successful.
Waterfall model merits:-
- If the requirements are very clear this model is good to implement for smaller projects.
- This can be easily understood.
- Development will be happened phase by phase.
- If there is need to change in testing phase it is very difficult.
- High chances of failure for long projects.
- Risk is also very high.