loading...
Tag Oriented Agile Requirements Identification
March 31-April 04
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ECBS.2008.2615th Annual IEEE International Confer ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Requirements elicitation, particularly for agile development, presumes the availability of a customer. However, in many cases, as with market-driven projects, a customer is not necessarily available. Here, the challenge is to support the identification of potential requirements by other means. With web development, one approach is to examine other web sites that exhibit similar characteristics to the project under consideration. In certain cases, it may be possible, with appropriate tool support, to easily and quickly identify and document potential requirements. This poster describes one such prototype tool.
Index Terms:
tags, requirements elicitation, agile
Citation:
David Connolly, Frank Keenan, Brendan Ryder, "Tag Oriented Agile Requirements Identification," ecbs, pp.497-498, 15th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ecbs 2008), 2008
Usage of this product signifies your acceptance of the Terms of Use.