Software Development Methodologies

Software Development Methodologies

1. Waterfall

   • Merits: easy to manage, clear stages and responsibilities, clear deliverables, easy to see if project is on schedule.
   • Drawbacks: Carries lots of risks, user doesn't get to see project until the end which can mean requirements have to be very clear. Not good for complex projects.
   • Suitable Projects: large or small, assuming that requirements and outcome is very well understood and carries minor risks.

2. Spiral

   • Merits: risk management is controlled, really good for a high-level project. Produces prototypes which clients can feedback on.
   • Drawbacks: complex nature increases costs (uses specialised skills), the project suffers if the risk analysis is poor.
   • Suitable Projects: large, high-risk, unclear requirements.

3. Agile

   • Merits: produces high level code, flexible to changes, allows for regular client input.
   • Drawbacks: poor documentation, constant interaction with client and development team.
   • Suitable Projects: small to medium with unclear requirements.

4. Extreme Programming (XP)

   • Merits: high quality code is prioritised, core principles promote respect, collaboration which is productive. Uses 2 coders to produce system.
   • Drawbacks: geographical locations can make working in pairs difficult sometimes, client must work with development team throughout, expensive paired programming.
   • Suitable Projects: small to medium projects where quality is important, when requirements could change.

5. Rapid Application Development (RAD)

   • Merits: requirements don't have to be entirely clear at the start, focus groups can work with the client to avoid the need for a full formal requirements document, feedback from client means project is likely to have great usability and meet all criterias. Prototypes produced to be improved.
   • Drawbacks: Not always the best code efficiency, regular contact with clients take time, scales poorly for large projects with big teams.
   • Suitable Projects: initial requirements aren't fully understood, as iterative nature prevents development from being side-tracked.