The DOI matches its Crossref record.
Empirical studies of requirements validation techniques
Abstract
Requirements validation ensures that the software requirements specification contains complete and consistent set of requirements which are according to the customer needs. This paper provides overview of requirements validation techniques like requirements inspections, requirements prototyping, requirements testing and viewpoint-oriented requirements validation. This paper highlights pros and cons of these requirements validation techniques. In requirements testing special attention is given to TCD inspections.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Prototyping facilitates presenting, discussing, and evaluating a product with external parties and internally within a project, thereby supporting decision making.
“Prototyping thus facilitates presenting, discussing, and evaluating a product with external parties, such as customers and investors, and internally within a project, thereby supporting decision making (Budde and Zullighoven 1990;Raja 2009).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Raja 2009
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 18
- 10.1109/32.852741 · DOI
- 10.1109/AGILE.2006.60 · DOI
- 10.1109/32.106986 · DOI
- dawson, 2005, Projects in Computing and Information Systems
- gorschek, 0, testcase driven inspection of pre-project requirements-process proposal and industry experience report, Proceedings of the Requirements Engineering Decision Support Workshop Held in Conjunction with the 13th IEEE International Conference on Requirements Engineering 2005
- 10.1109/32.799955 · DOI
- 2002, capability maturity model integration (cmmi), version 1.1, CMMI for Systems Engineering Software Engineering Integrated Product and Process Development and Supplier Sourcing Version 1 1 (CMMISE/ SW/IPPD/SS V1 1)
- 1998, Software Process Assessment TR 15504 1998, 2004
- 10.1109/TOOLS.2001.941681 · DOI
- thayer, 1997, Software Requirements Engineering 2nd Edition
- kotonya, 1998, Requirements Engineering
- 10.1147/sj.153.0182 · DOI
- sommerville, 1997, Requirements Engineering
- 10.1109/52.28121 · DOI
- rakitin, 2001, Software Verification and Validation for Practitioners and Managers
- 10.1142/9789812389701_0023 · DOI
- 10.1109/METRIC.2002.1011329 · DOI
- 10.1109/ICRE.1994.292380 · DOI
Cited by
Sorted by citations
An empirically based model of software prototyping: a mapping study and a multi-case study
Bjarnason, E., Lang, F., & Mjöberg, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10331-w · Cited by 75
Metadata
- Authors
- Raja, U. A.
- Affiliations
- Blekinge Institute of Technology (SE)
- Corresponding author
- Raja, Uzair Akbar
- Venue
- 2009 2nd International Conference on Computer, Control and Communication
- Publisher
- IEEE
- Published
- 2009-02
- Pages
- 1-9
- OpenAlex
- W2023023211
- Cited by
- 24
- References
- 0
- Citations by year
- 2024: 1 · 2023: 2 · 2022: 1 · 2021: 3 · 2020: 2 · 2019: 1 · 2018: 1 · 2016: 2 · 2015: 1 · 2014: 4 · 2012: 2
- FWCI
- 1.31
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- International Conference on Computer, Control and Communication (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Safety, Risk, Reliability and Quality › Safety Systems Engineering in Autonomy
- Keywords
- requirements validation, requirements specification, requirements inspection, requirements-based testing, requirements completeness, requirements consistency
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
