The DOI matches its Crossref record; 37 of the 37 references it cites were found in a registry or an index.
Supporting systems development by capturing deliberations during requirements engineering
Abstract
Support for various stakeholders involved in software projects (designers, maintenance personnel, project managers and executives, end users) can be provided by capturing the history about design decisions in the early stages of the system's development life cycle in a structured manner. Much of this knowledge, which is called the process knowledge, involving the deliberation on alternative requirements and design decisions, is lost in the course of designing and changing such systems. Using an empirical study of problem-solving behavior of individual and groups of information systems professionals, a conceptual model called REMAP (representation and maintenance of process knowledge) that relates process knowledge to the objects that are created during the requirements engineering process has been developed. A prototype environment that provides assistance to the various stakeholders involved in the design and management of large systems has been implemented.>
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
Dilemmas in a general theory of planning
Rittel, H. W. J., & Webber, M. M. (1973) · Policy Sciences · doi:10.1007/bf01405730 · Cited by 16,338
A field study of the software design process for large systems
Curtis, B., Krasner, H., & Iscoe, N. (1988) · Communications of the ACM · doi:10.1145/50087.50089 · Cited by 2,076
Group dynamics : the psychology of small group behavior
Shaw, M. E. (1971) · Cited by 1,486
gIBIS: a hypertext tool for exploratory policy discussion
Conklin, J., & Begeman, M. L. (1988) · ACM Transactions on Information Systems · doi:10.1145/58566.59297 · Cited by 1,088
Group Dynamics: The Psychology of Small Group Behavior
Vander Ark, S. D. (1972) · Journal of Music Therapy · doi:10.1093/jmt/9.4.203 · Cited by 1,016
Software processes are software too
Osterweil, L. J. (1987) · doi:10.5555/41765.41766 · Cited by 865
Telos: representing knowledge about information systems
Mylopoulos, J., Borgida, A., Jarke, M., & Koubarakis, M. (1990) · ACM Transactions on Information Systems · doi:10.1145/102675.102676 · Cited by 786
Classifying Software for Reusability
Prieto-Díaz, R., & Freeman, P. (1987) · IEEE Software · doi:10.1109/ms.1987.229789 · Cited by 696
WYSIWIS revised: early experiences with multiuser interfaces
Stefik, M., Bobrow, D. G., Foster, G., Lanning, S., & Tatar, D. G. (1987) · ACM Transactions on Information Systems · doi:10.1145/27636.28056 · Cited by 544
A Language/Action Perspective on the Design of Cooperative Work
Winograd, T. (1987) · Human–Computer Interaction · doi:10.1207/s15327051hci0301_2 · Cited by 476
Cited by
An analysis of the requirements traceability problem
Gotel, O. C. Z., & Finkelstein, C. W. (2002) · Proceedings of IEEE International Conference on Requirements Engineering · doi:10.1109/icre.1994.292398 · Cited by 1,246
Recovering traceability links between code and documentation
Antoniol, G., Canfora, G., Casazza, G., De Lucia, A., & Merlo, E. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1041053 · Cited by 967
Toward reference models for requirements traceability
Ramesh, B., & Jarke, M. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895989 · Cited by 912
Self-citationAdvancing candidate link generation for requirements tracing: the study of methods
Hayes, J. H., Dekhtyar, A., & Sundaram, S. K. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.3 · Cited by 481
Security Requirements Engineering: A Framework for Representation and Analysis
Haley, C. B., Laney, R., Moffett, J. D., & Nuseibeh, B. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.70754 · Cited by 462
Information technology and organizational learning: a review and assessment of research
Robey, D., Boudreau, M.-C., & Rose, G. M. (2000) · Accounting, Management and Information Technologies · doi:10.1016/s0959-8022(99)00017-x · Cited by 377
Lucia, A. D., Fasano, F., Oliveto, R., & Tortora, G. (2007) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/1276933.1276934 · Cited by 354
Computer supported argumentation and collaborative decision making: the HERMES system
Karacapilidis, N., & Papadias, D. (2001) · Information Systems · doi:10.1016/s0306-4379(01)00020-5 · Cited by 327
A survey of traceability in requirements engineering and model-driven development
Winkler, S., & von Pilgrim, J. (2010) · Software & Systems Modeling · doi:10.1007/s10270-009-0145-0 · Cited by 313
ConceptBase ? A deductive object base for meta data management
Jarke, M., Gallersd�rfer, R., Jeusfeld, M. A., Staudt, M., & Eherer, S. (1995) · Journal of Intelligent Information Systems · doi:10.1007/bf00961873 · Cited by 308
Reconciling user and project manager perceptions of IT project risk: a Delphi study1
Keil, M., Tiwana, A., & Bush, A. (2002) · Information Systems Journal · doi:10.1046/j.1365-2575.2002.00121.x · Cited by 255
Metadata
- Authors
- Ramesh, B., & Dhar, V.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1992-06
- Volume
- 18
- Issue
- 6
- Pages
- 498-510
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2120978952
- Cited by
- 284
- References
- 37
- FWCI
- 30.85
- Type
- journal article
- 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.