• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Development Process

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Iterative and Incremental
Is it a divide and conquer approach?
I guess it is. It means dividing the work (in different iterations) and conquering the same (in a particular iteration).
yup
- Raj
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If your definition of incremental allows you to build part of a function in one iteration and the rest of it in the next, I'd say we try not to do that. We try to define a deliverable so that it is completed, tested, production ready in an iteration. That may mean we're doing the very same work, except we define smaller features, or it may mean we're pushing our smaller work to a different level of "done"
Of course we don't always make it. Some features just don't get done. Then we tell the customer the feature is not there, even though it's half there. We don't demonstrate or ask them to test half of something.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Moving this to the Process forum...
 
Ranch Hand
Posts: 662
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I guess its divide, consolidate and conquer
Divide the work to be done into different iterations (this is not really done upfront), consolidate on an executable at the end of each iteration, and obviously conquer the problem to be solved.
The core architecture will be delivered in the early iterations and features will be enhanced during the course of following interations.
 
Sheriff
Posts: 7001
6
Eclipse IDE Python C++ Debian Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The core architecture will be delivered in the early iterations and features will be enhanced during the course of following interations.
Bear in mind that it doesn't have to be the "core" first. Many successful iterative and incremental developments deliver externally visible features in each iteration, and develop only enough "core architecture" to support the delivered features.
Really: "iterative" means the process repeats the same "micro-process" several times during the development of the solution. "incremental" means that the solution is delivered several times, improving as it goes.
They work really well together, but it is possible to have one without the other.
 
Raj Waters
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
[They work really well together, but it is possible to have one without the other.]
It means they are not same but they can co-exists.
 
And will you succeed? Yes you will indeed! (98 and 3/4 % guaranteed) - Seuss. tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic