Question

List the differences between agile methodology, waterfall methodology and prototype methodology . (TABLE format)

Answer 1

Agile
1.Prohect life cycle is divided into sprits with certain features in each sprint.
2.All the activities of requirements,design,coding and testing are bundled into sprints.
The requirements are cion

3.Client have a preview of the system with certain high priority requirements.Some requirements are fullfilled. Each sprint shows the system with added functionalities based on the added
requirements.

4.Requirements may under go change with each sprint.But once the sprint is set the
requirements will not undergo any change

5.Suitable for medium duration projects where requirents have enough clarity to start
and design the sprints.

6.The complexity of the error remains almost constant as each sprint focusses on a set
of requirements planned for that sprint.It all depends upon the complexity of requirements

Waterfall

1.Project life cycle is divided into differen phases for requirements,design, coding
testing.
2.Activities can not be performed in parallel.All the phases are strictly in sequential
order
3.Client can only preview the system only after the final version of the software is developed because there is no feed back loop.
4.Developers encounter a freezing requirement where they are not allow to modify the requirements or specification of the previous phase until the next iteration.

5.Suitable for long duration projects where requirements are complex and take lobg time to
freeze

6.The complexity of an error increases because of the nature of the model; each phase is sequential of the other.

Prototype

1.Project life cycle is divided into different activities in iterative fashion,where the first
activity focusses on building a prottpe with minimal features and then more features
are added in the course of time.

2.All the activities requirement, design, coding and testing are performed as one set
of activities but the depth of complexity of each activity increases with each set of
activity resulting in prototype with minimal features and prototype with more amd more
features added bringing it closer to the actual system

3.Client have a preview of the system from the "quick design" and the prototype developed early at the of the process.

4.Developers can refine or add requirements and specification to the system after the prototype is built.

5.Suitable for medium or not so large projects where the requirements are not very clear in the start and needs a prototype to understand and define the requirements

6.The complexity of an error is low because the prototype enables the developer to detect any deficiency early at the process.