Databases
StackOverflow2013
Postsdbo
POPredictive vs Reactive software design
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPredictive vs Reactive software design
    primarykey
    data
    text
    <p>I know that for me I first got started following the waterfall method of project management and along with that I went with the predictive approach to software design. In this I mean we had huge packets of documentation, UML, database schemas, data dictionaries, workflows, activity diagrams, etc. </p> <p>Having worked in software for over 10 years now I find it to be much more realistic to approach software design from a Reactive approach. I frequently follow a scrum approach to project management and with that very little heavy documentation is ever generated. We have very little workflow specification (though they still have there use). This is a much more dynamic approach to software creation. Of course along with it comes frequent refactoring as time goes on as we find out new features over time that had we planned for up front would have changed things dramatically.</p> <p>The big difference for us is that the first approach takes longer, seems to fail more frequently in a software construction world, and isn't nearly as flexible. The second approach provides more flexibility, makes us aware of failure faster (so we can course correct faster), and provides some form of functionality at the end of every iteration.</p> <p>Knowing both sides from experience, I still find many people that LOVE the waterfall approach over the agile approach for software development. I don't get it.</p> <p><strong>question:</strong> Why would someone use waterfall over some form of agile with all of the research backing agile? What are strong arguments for using waterfall over agile?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAndrew Siemer
    1. USAndrew Siemer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPredictive vs Reactive software design
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POPredictive vs Reactive software design
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPredictive vs Reactive software design
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthere's a world full of people that err on the side of 'familiarity and comfort' over 'change and progress', and the developer armies of our world are rife with them (especially in management, curiously enough)
      singulars
      1. POPredictive vs Reactive software design
      1. USHardryv
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload