NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (wileyal), last modified by Unknown User (hebell) on Jun 17, 2009

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

caDSR Requirements Gathering Process

caDSR requirements arise in many settings. By using one of the means described below you will ensure your ideas have been successfully communicated and documented. Software requests for enhancements are acknowledged by the caDSR team with the creation of an item in our tracking database and assigned a reference number, making it easy to track your favorite request! If it doesn't have a GForge tracker number, we haven't yet realized it as a requirement.

Where requirements come from:

  • caCORE Software Users Meetings. Visit the caCORE Users Meetings and Forums wiki page for meeting information, links to past meeting presentations and meeting notes, and links to status and planning information. As the release cycle progresses we begin a public review and prioritization, drawing from variety of factors to make final "in/out" decisions. We conduct user feedback sessions throughout the design and prototype phases.
  • Contact us at Application Support or by the "Send comments and suggestions" links from the caDSR tools. All messages are received and logged by Application Support.
  • Subscribe to the caDSR Users LISTSERV. Post ideas, participate in discussions. All postings are read, and if a requirement is suggested, it's entered into our tracking system once confirmed.
  • Personal communications: If you have a specific idea or suggestion you want to discuss personally with Denise Warzel (Assistant Director, caDSR) feel free to contact her directly.
  • No labels