Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am developing one.</p> <p>About a year ago I looked for requirement management software on the 'net and found at least 30 of them, in approximately 3 categories:</p> <ul> <li><p>Priceless (and marketed e.g. at aerospace companies)</p></li> <li><p>Expensive (e.g. $1000s per seat), which my employers have never chosen to use</p></li> <li><p>Cheap or free, but missing features which seem to me important</p></li> </ul> <p>There are also general-purpose tools (e.g. Wiki, or emails and Word documents and/or Spreadsheets), which too are missing features which seem to me important.</p> <hr> <blockquote> <p>I think you should elaborate re: "are missing features which seem to me important". </p> </blockquote> <p>There are things which you <em>can</em> do with a general-purpose Wiki:</p> <ul> <li>Create a list of features</li> <li>Describe each feature (perhaps a separate page/section for each feature)</li> <li>Do this collaboratively (version control, update notifications, discussion pages)</li> </ul> <p>But, there are some things which I think you can't do with a general-purpose Wiki, even pretty basic things:</p> <ul> <li><p>Define custom attributes (e.g. "Date started", "Estimated cost", etc.); associate these attribute values with your features; list features (in a table or grid) with their attributes (so that they can be sorted, e.g. sorted by "Importance" or by "Difficulty")</p></li> <li><p>Help with traceability (traceability not too difficult when there are only two stages, e.g. "requirements" and "implementation"; but it's harder when there are several stages, e.g. "use cases", "functional spec", "architecture", "implementation details", "test cases", "test results", and "bug reports")</p></li> <li><p>Support structured information, i.e. subsections and not just top-level sections.</p></li> </ul> <p>Even simply editing isn't a nice as it ought to be. Business people might prefer use an MS Word UI for editing: but MS Word produces documents, i.e. "information silos"; but if you don't use MS Word, then you're using what? A WYSIWYG in-browser editor? Or markdown syntax?</p>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
 

Querying!

 
Guidance

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