IEICE TRANSACTIONS on Information
Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame
Summary :
Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.
- Publication
- IEICE TRANSACTIONS on Information Vol.E95-D No.4 pp.1031-1043
- Publication Date
- 2012/04/01
- Publicized
- Online ISSN
- 1745-1361
- DOI
- 10.1587/transinf.E95.D.1031
- Type of Manuscript
- Special Section PAPER (Special Section on Knowledge-Based Software Engineering)
- Category
Authors
Keyword
Latest Issue
Copyrights notice of machine-translated contents
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Cite this
Copy
Haruhiko KAIYA, Atsushi OHNISHI, "Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame" in IEICE TRANSACTIONS on Information,
vol. E95-D, no. 4, pp. 1031-1043, April 2012, doi: 10.1587/transinf.E95.D.1031.
Abstract: Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.E95.D.1031/_p
Copy
@ARTICLE{e95-d_4_1031,
author={Haruhiko KAIYA, Atsushi OHNISHI, },
journal={IEICE TRANSACTIONS on Information},
title={Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame},
year={2012},
volume={E95-D},
number={4},
pages={1031-1043},
abstract={Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.},
keywords={},
doi={10.1587/transinf.E95.D.1031},
ISSN={1745-1361},
month={April},}
Copy
TY - JOUR
TI - Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame
T2 - IEICE TRANSACTIONS on Information
SP - 1031
EP - 1043
AU - Haruhiko KAIYA
AU - Atsushi OHNISHI
PY - 2012
DO - 10.1587/transinf.E95.D.1031
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E95-D
IS - 4
JA - IEICE TRANSACTIONS on Information
Y1 - April 2012
AB - Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.
ER -
English
