Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's possible to do what you describe, to develop requirements in a collaborative way, <em>in spite of</em> using a wiki. Nothing about the wiki paradigm assists in this process.</p> <p>I managed a wiki on the Zend Framework project to track proposals for components. <a href="http://framework.zend.com/wiki/display/ZFPROP/Home" rel="noreferrer">They're still using it.</a> Proposals are different from functional specifications, but the usage is similar enough to your question that I think this is relevant.</p> <p>A wiki doesn't take care of itself. Unless you have someone responsible for managing it and making sure there is some structure and consistency, it quickly becomes a mess. The real-world analogy would be to hand each of your team a blank sheet of paper and tell them to write up their part of the requirements. Problems with this are:</p> <ul> <li>Every contributor has to make up their own document structure, and write about different things in a different order. So it's impossible to compare one page to another.</li> <li>There's no "index page" to organize all the disparate contributions. No one wants a page to "fall through the cracks," but in a wiki that's the <em>default</em> destiny of any page as soon as it's written. </li> <li>There's no feedback loop to make sure the writing actually gets done.</li> </ul> <p>The way to make it work is to apply some process to the project, and use the wiki in accordance with that process.</p> <ul> <li>Give people the ability to create a new page in the wiki, but only through an interface that automatically links the new page into the right index.</li> <li>Define a lifecycle for documents, so they are sure to be drafted, reviewed, and approved at the appropriate stages.</li> <li>Provide a template for a new page. Provide the section headings that you need in each of these pages, and make part of the review process a confirmation that head section has been filled out adequately.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POUsing a Wiki for Requirements Management?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBill Karwin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing a Wiki for Requirements Management?
      singulars
      1. PTQuestion
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO"Nothing about the wiki paradigm assists in this process." What about change tracking? What about the fact that it's published in a central location several people can access (not passed around via email)?
      singulars
      1. PO
      1. USapollodude217
    2. CO@apollodude217: Yes, you're right that a wiki has some features that make it better than passing around a shared document by email. But without someone serving as a sort of librarian, I've seen wikis degrade rapidly into an unorganized collection. Multiple pages seem to be about similar topics, but they aren't linked to one another, and no one maintains them, so no one really knows which one (if any) is the authoritative source of information. You also mentioned change tracking, but this is irrelevant with respect to how one would keep the documents organized and up to date.
      singulars
      1. PO
      1. USBill Karwin
 

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