Showing posts with label waterfall model. Show all posts
Showing posts with label waterfall model. Show all posts

Wednesday, September 2, 2009

Waterfall Model of Software Development

Waterfall processes

Lets discuss about Waterfall model of Software Devt. This model is one of the very popular and used quite extensively.

The processes or phases followed in Waterfall model are like ...

  1. Gathering Requirements (Making Software Requirements Specifications or SRS docs etc, Analysis)
  2. Designging ( DB Designing, Architecture finalization, necessary docs, HTMLs or Screen designing)
  3. Coding (Or actual Development by programmers)
  4. Integration (Integration of various modules developed by various teams or persons)
  5. Testing (QA or QC activities are taken place and its made sure that software is good)
  6. Deployment (Deploying the software at the client's live environment or server)
  7. Support - Maintenance (Once the app is live .. maintaining the same)


In the waterfall model after the one step or process or phase is finished the app flows to next phase. Its like Waterfall where the water flows from the top most rock to the bottom.

The main critics is.. like the water cant be put back from bottom to the flow, similarly here it Changes in critical process, change control or a misunderstanding in first phase has tremendous cost effect.

Wednesday, March 18, 2009

Agile Software Development

What is Agile Software Development?

Agile Software development is the methodology which promotes flexible solutions to suffice client needs, yet effective approach of software development. Agile focuses on: Smaller deliveries (say monthly splitting of projects / milestones / deliveries), Adaptability, team work, leadership approach. It also includes some practices which would ensure rapid deliveries.

Rather than the conventional Waterfall model of Software development, Agile aims at taking into the account dynamic needs of the client and aims at only doing the part which is absolutely necessary for that delivery.

Hence it aims at reducing / avoiding overheads and delivering right thing with optimum efforts at right time to the client so that he can take a review at developing system and suggest needful changes (if any).

Read agile manifesto here.. http://agilemanifesto.org








 
Locations of visitors to this page