UiTM CAWANGAN SELANGOR KAMPUS PUNCAK PERDANA
COLLEGE OF COMPUTING, INFORMATICS AND MEDIA
BACHELOR OF INFORMATION SCIENCE (HONS.)
INFORMATION SYSTEM MANAGEMENT (IM245)
SYSTEM ANALYSIS IN INFORMATION MANAGEMENT 1 (IMS606)
INDIVIDUAL ASSIGNMENT:
SYSTEM DEVELOPMENT METHODOLOGIES
PREPARED BY:
MAISARAH BINTI ABDUL PATAS (2022859446)
CDIM245 5B
PREPARED FOR: PROFESOR MADYA DR SAFAWI BIN ABDUL RAHMAN
28TH JANUARY 2024
1
INDIVIDUAL ASSIGNMENT:
SYSTEM DEVELOPMENT METHODOLOGIES
PREPARED BY:
MAISARAH BINTI ABDUL PATAS (2022859446)
CDIM245 5B
COLLEGE OF COMPUTING, INFORMATICS AND MEDIA
UNIVERSITI TEKNOLOGI MARA
SELANGOR
28TH JANUARY 2024
2
TABLE OF CONTENTS
NO CONTENTS PAGE
1 Draft 4
2 Essay: 5-6
A Comparative Analysis Of System Development
Methodologies: Waterfall, Agile, And Spiral
3 References 7
3
1.0 DRAFT
CHOOSING HOW TO BUILD SOFTWARE: WATERFALL, AGILE, AND SPIRAL.
Waterfall, Agile, and Spiral.
Waterfall:
1. It's like following a strict plan. Once you start, it's tough to change things.
2. Plan everything in detail from the beginning. Lots of writing down ideas.
3. Tries to deal with problems early on. Once the plan is set, it's hard to change.
Agile:
1. Thinks changes are normal. It can adjust a lot during the project.
2. Plans are more flexible, and they care more about making a working product than
writing a lot.
3. Keeps an eye on problems all the time, and changes things quickly as needed.
Spiral:
1. Kind of in the middle. It allows changes at different stages, not too strict like Waterfall
but not as free as Agile.
2. Plans bit by bit, and it also looks at risks while planning.
3. Looks at risks a lot during the project, tries to handle them in each step.
4
2.0 ESSAY
A COMPARATIVE ANALYSIS OF SYSTEM DEVELOPMENT METHODOLOGIES:
WATERFALL, AGILE, AND SPIRAL
In the realm of software development, choosing the right methodology is paramount for
project success. Three prominent approaches, each with its distinctive characteristics, are
Waterfall, Agile, and Spiral. This essay aims to provide a comprehensive comparison across
various dimensions.
Firstly, let's explore the approach to change within these methodologies. The Waterfall
model, with its sequential structure, is akin to a rigid blueprint. Once a phase is completed,
changes become arduous, emphasizing a thorough upfront planning. In contrast, Agile
embraces change as a constant companion. Its iterative nature allows for frequent
adaptations, ensuring the end product aligns with evolving requirements. The Spiral model
strikes a balance, allowing for iteration and revision at each phase, accommodating changes
more flexibly than Waterfall, yet not as dynamically as Agile.
After that, project planning is another critical aspect that sets these methodologies apart.
Waterfall places great importance on detailed planning at the project's outset, with an
emphasis on comprehensive documentation. In contrast, Agile opts for adaptive planning,
focusing on delivering working software over extensive documentation. This agility enables
rapid responses to changing requirements. The Spiral model, while also iterative, integrates
risk analysis into its planning, offering a dynamic approach that allows for adjustments in each
cycle.
Furthermore, the management of risks plays a pivotal role in the success of any
development project. Waterfall, by its nature, addresses risks primarily in the initial planning
stages. Once the plan is set, there is limited flexibility to adapt to unforeseen issues. Agile, on
the other hand, excels in risk management by constantly assessing and addressing risks in
short, iterative cycles. The Spiral model, true to its name, revolves around risk-driven
development. With its emphasis on risk analysis and mitigation in every iteration, it provides a
structured yet flexible way to navigate uncertainties.
5
In conclusion, the choice between Waterfall, Agile, and Spiral methodologies hinges on
project requirements, team dynamics, and the level of flexibility needed. Waterfall suits
projects with well-defined, unchanging requirements, while Agile shines in dynamic
environments where adaptability is key. The Spiral model, positioned between these
extremes, offers a balance that incorporates iterative development and risk management.
Understanding the nuances of each methodology is crucial for project managers and
development teams seeking optimal outcomes in the ever-evolving landscape of software
development.
6
3.0 REFERENCES
GeeksforGeeks. (2022, June 7). Software engineering: Comparison between agile model and
other models. GeeksforGeeks. https://www.geeksforgeeks.org/software-engineering-
comparison-between-agile-model-and-other-models/
SDLC models explained: Agile, waterfall, V-shaped, iterative, spiral. Tech Blogger. (2022a,
April 22). https://contenteratechspace.com/sdlc-models-explained-agile-waterfall-v-
shaped-iterative-spiral/
