Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When I was into the "waterfall" way of doing things I would write several hundred page documents showing all the details that could be uncovered during research. To get to this massive tome of documentation I would generally </p> <ol> <li>meet and greet everyone involved with the project</li> <li>take copious notes regarding the perceived requirements</li> <li>create long bulleted lists of high level requirements</li> <li>start to break down the high level requirements into well defined details</li> <li>begin to fill out Software Requirements Specification word template: <a href="http://www.google.com/#hl=en&amp;q=software+requirements+specification+type%3Adoc&amp;aq=f&amp;oq=&amp;aqi=&amp;fp=DLh7wmTRH1c" rel="nofollow noreferrer">SRS</a></li> <li>create wire frames in photoshop, excel, or (my favorite) <a href="http://www.balsamiq.com/products/mockups" rel="nofollow noreferrer">Balsamiq</a></li> <li>list out data that must be captured and start to build out a rough schema</li> <li>list out class structures in UML</li> <li>define project timeline</li> <li>blah blah blah</li> <li>write code</li> <li>hope that what was requested is what is still wanted when code is complete!</li> </ol> <p>For the past few years I have been following along with Agile (SCRUM) and have taken a totally different approach.</p> <ol> <li>meet with product owner to hear about tasks to be built</li> <li>decompose story into tasks (basic planning)</li> <li>assign time to tasks</li> <li>do some more detailed planning</li> <li>-->write test, write code to pass test, refactor-->check in dance</li> <li>demonstrate working product/feature</li> <li>start process over</li> </ol> <p>I have to say that Agile reduces the amount of time spent writing documents that decay as soon as the ink drys. The product owner gets to see results in a much more rapid manner. Which means that they get to keep the project going in the right direction over time - even if that direction changes as we are developing.</p> <p>Keep in mind that there is a time and a place for both ways of developing. I wouldn't want to build Jet software using Agile!</p>
    singulars
    1. This table or related slice is empty.
    1. POHow much planning do you do before starting to code?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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