For this blog, I selected two resources to better understand software process models, a central topic in our course on software engineering. The first resource, “Top 8 Software Development Models Used in Industry” from GeeksforGeeks, outlines the most commonly used models in the software industry, including Agile, Waterfall, V-Model, Incremental, RAD, Iterative, Spiral, and Prototype. The article For this blog, I selected two resources to better understand software process models since they are central to our course on software process management. The first resource, “Top 8 Software Development Models Used in Industry” from GeeksforGeeks, introduces commonly used models such as Agile, Waterfall, V-Model, Incremental, RAD, Iterative, Spiral, and Prototype. The article gives a clear explanation of each model’s purpose, how its phases are structured, the benefits it offers, and the project types where it performs best. The second resource, the Institute of Data article “Understand Software Process Models,” provides an overview of SDLC frameworks and emphasizes how choosing the right model depends on factors like requirement stability, risk, and deadlines.
I chose these two resources because together they offer both an industry-oriented perspective and a more academic explanation. This combination allowed me to see how these models function in real teams while also understanding the theory behind why they were created. As someone planning to work in software development, I wanted a stronger grasp of how teams select a process model and what trade offs come with each approach.
A major takeaway from these readings is that no single model works best for every project. Agile, for example, uses short iterations that make it ideal for projects with changing or unclear requirements. Waterfall, on the other hand, follows a strict linear sequence, making it more suitable when requirements are stable and thoroughly documented. The Spiral model adds a heavy focus on risk analysis, which is helpful for large or high uncertainty projects. Models like RAD and Prototype show how useful rapid prototyping can be when quick feedback is needed or when requirements are fuzzy at the start. Understanding these differences helped me see that software development is not just about writing code, it also depends heavily on planning, teamwork, and communication.
The GeeksforGeeks article breaks down several widely used models: Agile emphasizes adaptability and customer feedback; Waterfall uses a clear phase by phase structure; the V-Model pairs each development stage with a corresponding testing phase; the Incremental model delivers functionality in small pieces; RAD focuses on fast prototyping; the Iterative model refines the system through repeated cycles; the Spiral model prioritizes risk management; and the Prototype model helps clarify uncertain requirements. Seeing the strengths and weaknesses of each helped me understand why teams might choose one model over another.
Reflecting on my own coursework, I realize that I often rushed into development without a well defined plan. Going forward, I plan to evaluate requirements more carefully. For example, in a project where features may evolve, I would recommend an Agile or Iterative approach, while a project with fixed objectives might benefit from Waterfall or Incremental development. This kind of planning can make teamwork smoother and lead to better overall results.
Overall, these resources strengthened my understanding of software process models and how they apply to real world software development. They helped me connect class concepts with professional practice and prepare for future roles in the field.
Resources:
- GeeksforGeeks. “Top 8 Software Development Models Used in Industry.” https://www.geeksforgeeks.org/software-engineering/top-8-software-development-models-used-in-industry/
- Institute of Data. “Understand Software Process Models.” https://www.institutedata.com/us/blog/understand-software-process-models/
Site Title 
Leave a comment