The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Elicitation technique selection: how do experts do it?
Abstract
Requirements elicitation techniques are methods used by analysts to determine the needs of customers and users, so that systems can be built with a high probability of satisfying those needs. Analysts with extensive experience seem to be more successful than less experienced analysts in uncovering the user needs. Less experienced analysts often select a technique based on one of two reasons: (a) it is the only one they know, or (b) they think that a technique that worked well last time must surely be appropriate this time. We present the results of in-depth interviews with some of the world's most experienced analysts. These results demonstrate how they select elicitation techniques based on a variety of situational assessments.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
The entity-relationship model—toward a unified view of data
Chen, P. P.-S. (1976) · ACM Transactions on Database Systems · doi:10.1145/320434.320440 · Cited by 4,708
Cited by
Eliciting security requirements with misuse cases
Sindre, G., & Opdahl, A. L. (2005) · Requirements Engineering · doi:10.1007/s00766-004-0194-4 · Cited by 730
Requirements Elicitation: A Survey of Techniques, Approaches, and Tools
Zowghi, D., & Coulin, C. (2006) · Engineering and Managing Software Requirements · doi:10.1007/3-540-28244-0_2 · Cited by 430
A Unified Model of Requirements Elicitation
HICKEY, A. M., & DAVIS, A. M. (2004) · Journal of Management Information Systems · doi:10.1080/07421222.2004.11045786 · Cited by 253
Self-citationRequirements Engineering: Best Practice
Fricker, S. A., Grau, R., & Zwingli, A. (2015) · Requirements Engineering for Digital Health · doi:10.1007/978-3-319-09798-5_2 · Cited by 61
Metadata
- Authors
- Hickey, A. M., & Davis, A. M.
- Venue
- Journal of Lightwave Technology
- Publisher
- IEEE Comput. Soc
- Published
- 2004-04-23
- Pages
- 169-178
- ISSN
- 0733-8724 (ISSN-L)
- OpenAlex
- W2141447926
- Cited by
- 222
- References
- 1
- FWCI
- 12.29
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.