• 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

4 phases and its use

 
Ranch Hand
Posts: 208
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
What are the benefits you guys can think of when we break a development cycle into inception,elaboration, construction and transition phase?
Hari
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The main benefit is that they help you concentrate on the different risks a project faces.
The inception phase is concentrating on the questions "Can this be done (by use)? How much is it likely to cost?".
The elaboration phase concentrates on "What architecture/techniques should we use." - once the team gains confidence in this, you reached the construction phase.
I don't know what to think about the transition phase, though.
 
Ranch Hand
Posts: 150
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Hari babu:
Hi
What are the benefits you guys can think of when we break a development cycle into inception,elaboration, construction and transition phase?
Hari


Another benefit is the user feedback at the end of each stage.
E.g. At the end of the inception phase the user can tell you if the requirements define the system that they want. If not then it is pointless continuing.
Regards,
Fintan
 
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
If not then it is pointless continuing
That sounds a bit drastic. How about using the feedback to modify the requirements so they do define what the customers want!
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Fintan Conway:
Another benefit is the user feedback at the end of each stage.


Personally, I would like user/customer-feedback much more often than after every phase. Preferably at least every couple of weeks, at the end of an iteration. You could do this without having the phases, so it seems to me...

E.g. At the end of the inception phase the user can tell you if the requirements define the system that they want.


I think I don't fully understand - isn't it the user/customer who is *specifying* the requirements?
reply
    Bookmark Topic Watch Topic
  • New Topic