The DOI matches its Crossref record; 25 of the 25 references it cites were found in a registry or an index.
Nonfunctional requirements: from elicitation to conceptual models
Abstract
Nonfunctional requirements (NFRs) have been frequently neglected or forgotten in software design. They have been presented as a second or even third class type of requirement, frequently hidden inside notes. We tackle this problem by treating NFRs as first class requirements. We present a process to elicit NFRs, analyze their interdependencies, and trace them to functional conceptual models. We focus our attention on conceptual models expressed using UML (Unified Modeling Language). Extensions to UML are proposed to allow NFRs to be expressed. We show how to integrate NFRs into the class, sequence, and collaboration diagrams. We also show how use cases and scenarios can be adapted to deal with NFRs. This work was used in three case studies and their results suggest that by using our proposal we can improve the quality of the resulting conceptual models.
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.
Integrity signals
Registry
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.
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
Kiczales, G. (1996) · ACM Computing Surveys · doi:10.1145/242224.242420 · Cited by 5,133
The Unified Modeling Language reference manual
Rumbaugh, J. E., Booch, G., & Jacobson, I. (1999) · CERN Document Server (European Organization for Nuclear Research) · Cited by 4,175
The Unified Software Development Process
Jacobson, I., Booch, G., & Rumbaugh, J. E. (1999) · CERN Document Server (European Organization for Nuclear Research) · Cited by 3,389
No Silver Bullet Essence and Accidents of Software Engineering
Brooks (1987) · Computer · doi:10.1109/mc.1987.1663532 · Cited by 3,186
Bergmans, L., & Lopes, C. V. (1999) · Lecture Notes in Computer Science · doi:10.1007/3-540-46589-8_17 · Cited by 2,949
Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C., Loingtier, J.-M., & Irwin, J. (1997) · Lecture Notes in Computer Science · doi:10.1007/bfb0053381 · Cited by 2,573
Software Metrics: A Rigorous and Practical Approach
Fenton, N., & Pfleeger, S. L. (2013) · Cited by 2,509
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Self-citationGoal-oriented requirements engineering: a guided tour
van Lamsweerde, A. (2002) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/isre.2001.948567 · Cited by 1,723
Non-Functional Requirements in Software Engineering
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000) · Springer eBooks · doi:10.1007/978-1-4615-5269-7 · Cited by 1,690
Cited by
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Self-citationSoftware transparency as a key requirement for self-driving cars
Cysneiros, L. M., Raffi, M., & Sampaio do Prado Leite, J. C. (2018) · 2018 IEEE 26th International Requirements Engineering Conference (RE) · doi:10.1109/re.2018.00-21 · Cited by 61
Self-citation
Metadata
- Authors
- Cysneiros, L. M., & do Prado Leite, J. C. S.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2004-05
- Volume
- 30
- Issue
- 5
- Pages
- 328-350
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2144634407
- Cited by
- 263
- References
- 25
- FWCI
- 18.64
- 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: Nonfunctional requirements: from elicitation to conceptual models. https://app.cochat.ai/papers/10.1109/tse.2004.10
- The paper
- Cysneiros, L. M., & do Prado Leite, J. C. S. (2004). Nonfunctional requirements: from elicitation to conceptual models. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2004.10
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.
