This approach emphasizes pinpointing where and when information needs occur; at its core is the inquiry cycle model, a structure for describing and supporting discussions about system requirements. The authors use a case study to describe the model's conversation metaphor, which follows analysis activities from requirements elicitation and documentation through refinement
%0 Journal Article
%1 potts94
%A Potts, C.
%A Takahashi, K.
%A Anton, A. I.
%D 1994
%J Software, IEEE
%K requirements scenario
%N 2
%P 21--32
%T Inquiry-based requirements analysis
%U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=268952
%V 11
%X This approach emphasizes pinpointing where and when information needs occur; at its core is the inquiry cycle model, a structure for describing and supporting discussions about system requirements. The authors use a case study to describe the model's conversation metaphor, which follows analysis activities from requirements elicitation and documentation through refinement
@article{potts94,
abstract = {This approach emphasizes pinpointing where and when information needs occur; at its core is the inquiry cycle model, a structure for describing and supporting discussions about system requirements. The authors use a case study to describe the model's conversation metaphor, which follows analysis activities from requirements elicitation and documentation through refinement},
added-at = {2006-03-24T16:34:33.000+0100},
author = {Potts, C. and Takahashi, K. and Anton, A. I.},
biburl = {https://www.bibsonomy.org/bibtex/215e154abee7f3033cb5ad075a5169b60/neilernst},
citeulike-article-id = {256356},
description = {sdasda},
interhash = {6e6aa7e8b6f7622c5f86998c47cf5d21},
intrahash = {15e154abee7f3033cb5ad075a5169b60},
journal = {Software, IEEE},
keywords = {requirements scenario},
number = 2,
pages = {21--32},
priority = {4},
timestamp = {2006-03-24T16:34:33.000+0100},
title = {Inquiry-based requirements analysis},
url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=268952},
volume = 11,
year = 1994
}