1) KIS (keep it simple) principle. 3) Make frequent

 

1)   
Requirements
from the Customer.

 

2)   
Simple,
obedient and easy to operate.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

 

 

3)   
The
Specification from first phase studied in this phase and the system design is
Develop.

 

 

4)   
Feedback
is needed to understand a phase.

 

5)   
Once the
test is done; the product is deployed in the Situation or Deliver into the
market.

 

 

 

 

 

 

1)   
Begins
with the creation of user stories.

 

2)   
Follows
the KIS (keep it simple) principle.

 

 

3)   
Make
frequent smallreleases. The project is divided into iterations.
Iterationplanning starts each iteration.

 

4)   
The
customer is alwaysavailable.

 

 

5)   
All code
must have test. All code must pass all tests before it can be published.

 

 

 

 

 

 

Iterative Model

1)   
In
iterative model we can only create a high-level design of the application.

 

 

2)   
In
iterative model we are building and improving the output step by step.

 

3)   
In
iterative model we can get the reliable user feedback. how the product will work.

 

 

4)   
In
iterative model less time is expended on documents creating and more time is
given for designing.

 

5)   
When we
work iteratively we create rough product or product piece in
first iteration, then review it again and improve it in next iteration and so
on until it’s end.

 

 

SCRUM

 

1)   
Using
scrum we can design high-level design because meeting are held daily. For
Problem Descution.

 

2)   
Team
decides what they can commit to delivering in the Sprint.

 

3)   
Team
demonstrates product increment to product owner’s satisfaction.

 

4)   
Time boxed
to one hour of prep and four hours of meeting.

 

 

5)   
Daily
Meeting fifteen minutes. What have you accomplished since yesterday? Are your
Sprint Backlog estimates accurate? What are you working on today? Is there
anything blocking you

 

 

Incremental model

 

1)   
It is
easier to test and debug during a smaller iteration. In this model customer can
respond to each built. Lowers initial delivery cost.

 

 

2)   
Early
release starts with small, functional 
subsystem, later releases add functionality

 

 

3)   
This model
is more flexible – less costly to change scope and requirements.

 

4)   
Generates
working software quickly and early during the software life cycle.

 

 

 

 

 

 

Feature-Driven Development (FDD)

1)   
It found
in five basic activities, by way of, 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.

 

2)   
FDD was
also built around software engineering best practices such as domain object
modeling, developing by feature and code ownership.

3)   
If it will
take more than two weeks, then it will have to be broken down into smaller
features.

 

4)   
FDD’s main purpose is to deliver tangible, working
software repeatedly in a timely manner.

x

Hi!
I'm Joan!

Would you like to get a custom essay? How about receiving a customized one?

Check it out