Water
Fall Model  VS  Extreme Programming (XP)

 

Water
Fall Model

·       
In water
fall model we collect the requirements from the Costumer.

·       
Water fall
model is easy to use.

·       
In water
fall model the requirements is study and then develop.

·       
Feedback
is needed from costumer to understand a phase.

·       
After
Testing Software published in the market.

Extreme Programming (XP

·       
In XP we
collect requirements from the costumer as Sorties.

·       
In XP use
KIS (Keep It Simple).

·       
In XP the
project is divided into iterations.

·       
The Costumer
always available.

·       
All code
must have test. After pass all tests it published in market.

 

 

 

Iterative Model 
VS  SCRUM

Iterative
Model

·       
Using this
model we can design high level application.

·       
Using this
model we can build and design application step by step.

·       
User
Feedback is compulsory how product will work.

·       
Using this
model less time on document creating and more time for designing.

·       
We can
create rough design and in iterations we can improve our project.

Scrum

·       
Using
scrum we can design high-level design because meeting are held daily. For
Problem Desiccation.

·       
Team
decides what they can commit to delivering about project.

·       
Team
Master Satisfy with the project owner.

·       
Time for
Prep of documents is 1 hour and meeting is 4 hours.

·       
Daily
Meeting is 15 minutes what we do today? Any Problem in Project.

 

 Incremental model  VS 
Feature-Driven Development

 

Incremental Model

·       
Easier to
test in every phase and debug during a smaller iteration. In this model
customer can see and behave to each built.

·       
Early
release starts with small, work 
subsystem, later releases add new functionality

·       
This model
is more flexible and less costly to change scope and requirements easy to
change.

·       
Do working
quickly and early during the software life cycle.

Feature-Driven Development

·       
Five basic
activities, the development of an overall model, the building of a feature
list, the planning by feature, the designing by feature, and the building by
feature.

·       
FDD was
also built as domain object modeling, developing by feature and code ownership.

·       
If it will
take two or more than two weeks, then it will have to be broken down into
smaller features and working on it.

·       
FDD’s main purpose is to deliver actual, working
software many times in a timely manner.