Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 595

The DOI matches its Crossref record.

Managing conflicts in goal-driven requirements engineering

van Lamsweerde, A., Darimont, R., Letier, E.·1998·IEEE Transactions on Software Engineering

Abstract

A wide range of inconsistencies can arise during requirements engineering as goals and requirements are elicited from multiple stakeholders. Resolving such inconsistencies sooner or later in the process is a necessary condition for successful development of the software implementing those requirements. The paper first reviews the main types of inconsistency that can arise during requirements elaboration, defining them in an integrated framework and exploring their interrelationships. It then concentrates on the specific case of conflicting formulations of goals and requirements among different stakeholder viewpoints or within a single viewpoint. A frequent, weaker form of conflict called divergence is introduced and studied in depth. Formal techniques and heuristics are proposed for detecting conflicts and divergences from specifications of goals/requirements and of domain properties. Various techniques are then discussed for resolving conflicts and divergences systematically by the introduction of new goals or by transforming the specifications of goals/objects toward conflict-free versions. Numerous examples are given throughout the paper to illustrate the practical relevance of the concepts and techniques presented. The latter are discussed in the framework of the KAOS methodology for goal-driven requirements engineering.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1109/32.730542

Cites

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

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

No references could be resolved yet.

Research works printed but not linked: 56

  1. ryan, 1996, requirements engineering group report, Proc IWSSD8?Eighth Int l Workshop Software Specification and Design ACM Software Eng Notes, 22
  2. 10.1145/130994.130996 · doi:10.1145/130994.130996
  3. 10.1145/237432.237434 · DOI · Paper page
  4. 10.1145/158431.158438 · doi:10.1145/158431.158438
  5. sommerville, 1997, Requirements Engineering A Good Practice Guide
  6. yue, 1987, what does it mean to say that a specification is complete?, Proc IWSSD-4 Fourth Int l Workshop Software Specification and Design
  7. waldinger, 1977, achieving several goals simultaneously, Machine Intelligence, 8
  8. 10.1145/22719.22947 · doi:10.1145/22719.22947
  9. 10.1109/IWSSD.1998.667919 · doi:10.1109/iwssd.1998.667919
  10. 10.1007/BFb0022109 · doi:10.1007/bfb0022109
  11. 10.1109/ISRE.1993.324835 · doi:10.1109/isre.1993.324835
  12. 10.1109/TSE.1977.229899 · DOI · Paper page
  13. 10.1145/239098.239131 · DOI
  14. darimont, 1998, grail/kaos: an environment for goal-driven requirements engineering, Proc ICSE 98?20th Int l Conf Software Eng, 2, 58
  15. mylopoulos, 1995, partitioning information bases with contexts, Proc Third Int l Conf Cooperative Information Systems
  16. 10.1109/ICSE.1997.610231 · doi:10.1109/icse.1997.610231
  17. 10.1109/ICSE.1990.63633 · doi:10.1109/icse.1990.63633
  18. 10.1145/75199.75232 · doi:10.1145/75199.75232
  19. potts, 1995, using schematic scenarios to understand user needs, Proc DIS 95?ACM Symp Designing interactive Systems Processes Practices and Techniques, 10.1145/225434.225462 · doi:10.1145/225434.225462
  20. 10.1109/52.268952 · DOI · Paper page
  21. potter, 1991, An Introduction to Formal Specification and Z
  22. 10.1109/32.328995 · DOI · Paper page
  23. 10.1007/3-540-51635-2_52 · doi:10.1007/3-540-51635-2_52
  24. 10.1109/MS.1985.229776 · DOI
  25. 10.1109/32.142871 · DOI · Paper page
  26. 10.1145/243327.243674 · doi:10.1145/243327.243674
  27. van lamsweerde, 1995, goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learned, Proc RE 95?Second Int l Symp Requirements En
  28. 10.1109/32.738341 · DOI
  29. 10.1109/ICSE.1998.671102 · DOI
  30. 1996, step: deductive-algorithmic verification of reactive and real-time systems, Proc CAV 96?Eighth Int l Conf Computer-Aided Verification, 415
  31. 10.1007/978-1-4612-0931-7 · DOI · Paper page
  32. 10.1007/978-1-4615-3190-6 · DOI · Paper page
  33. 10.1109/ISRE.1997.566836 · doi:10.1109/isre.1997.566836
  34. jones, 1993, on the characterization of law and computer systems: the normative system perspective, Deontic Logic in Computer Science?Normative System Specification
  35. koymans, 1992, "Specifying Message Passing and Time-Critical Systems with Temporal Logic ", 10.1007/3-540-56283-4 · doi:10.1007/3-540-56283-4
  36. van lamsweerde, 1991, learning machine learning, Introducing a Logic Based Approach to Artificial Intelligence, 3, 263
  37. anton, 1994, goal decomposition and scenario analysis in business process reengineering, Proc Sixth Int l Conf Advanced Information Systems Eng, 94
  38. boehm, 1995, software requirements negotiation and renegotiation aids: a theory-w based spiral approach, 1995 17th International Conference on Software Engineering icse, 243, 10.1145/225014.225037 · doi:10.1145/225014.225037
  39. 1985, Readings in Knowledge Representation
  40. 10.1145/5397.5399 · DOI · Paper page
  41. 10.1145/234426.234427 · doi:10.1145/234426.234427
  42. 10.1109/IWSSD.1991.213081 · doi:10.1109/iwssd.1991.213081
  43. 10.1016/0167-6423(93)90021-G · DOI · Paper page
  44. 10.1145/234426.234431 · DOI · Paper page
  45. heimdahl, 1995, completeness and consistency analysis of state-based requirements, 1995 17th International Conference on Software Engineering icse, 3, 10.1145/225014.225015 · doi:10.1145/225014.225015
  46. 10.1007/978-1-4612-5983-1 · DOI · Paper page
  47. 10.1145/229000.226322 · doi:10.1145/229000.226322
  48. 10.1145/226241.226249 · doi:10.1145/226241.226249
  49. abadi, 1987, temporal-logic theorem proving, "Temporal-Logic Theorem Proving "
  50. 10.1109/ISRE.1993.324836 · doi:10.1109/isre.1993.324836
  51. 10.1109/ISRE.1997.566844 · doi:10.1109/isre.1997.566844
  52. amoroso, 1994, Fundamentals of Computer Security
  53. 10.1109/IWSSD.1996.501141 · doi:10.1109/iwssd.1996.501141
  54. gerth, 1995, simple on-the-fly automatic verification of linear temporal logic, Proc IFIP WG6 1 Symp Protocol Specification Testing and Verification
  55. 10.1109/ISRE.1995.512555 · doi:10.1109/isre.1995.512555
  56. 10.1145/75199.75228 · doi:10.1145/75199.75228

Cited by

See all 595

Metadata

Authors
van Lamsweerde, A., Darimont, R., & Letier, E.
Venue
IEEE Transactions on Software Engineering
Published
1998
Volume
24
Issue
11
Pages
908-926
ISSN
0098-5589 (ISSN-L)
OpenAlex
W2171627300
Cited by
595
References
0
FWCI
17.07
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

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Managing conflicts in goal-driven requirements engineering. https://app.cochat.ai/papers/10.1109/32.730542
The paper
van Lamsweerde, A., Darimont, R., & Letier, E. (1998). Managing conflicts in goal-driven requirements engineering. IEEE Transactions on Software Engineering. https://doi.org/10.1109/32.730542

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.