System specifications should be refined to meet stakeholders' requirements as much as possible, because the first specification does not satisfy all stakeholders in general. This paper presents a procedure to refine behavioral specification to satisfy stakeholders. Non-functional requirements are used for checking stakeholders' satisfaction. With this procedure, stakeholder-dissatisfaction can be reduced and new possibilities to satisfy or dissatisfy other stakeholders can be found, since a modification to cancel dissatisfaction can sometimes influence the satisfaction of the others.
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.
Copy
Haruhiko KAIYA, Kenji KAIJIRI, "Refining Behavioral Specification for Satisfying Non-functional Requirements of Stakeholders" in IEICE TRANSACTIONS on Information,
vol. E85-D, no. 4, pp. 623-636, April 2002, doi: .
Abstract: System specifications should be refined to meet stakeholders' requirements as much as possible, because the first specification does not satisfy all stakeholders in general. This paper presents a procedure to refine behavioral specification to satisfy stakeholders. Non-functional requirements are used for checking stakeholders' satisfaction. With this procedure, stakeholder-dissatisfaction can be reduced and new possibilities to satisfy or dissatisfy other stakeholders can be found, since a modification to cancel dissatisfaction can sometimes influence the satisfaction of the others.
URL: https://global.ieice.org/en_transactions/information/10.1587/e85-d_4_623/_p
Copy
@ARTICLE{e85-d_4_623,
author={Haruhiko KAIYA, Kenji KAIJIRI, },
journal={IEICE TRANSACTIONS on Information},
title={Refining Behavioral Specification for Satisfying Non-functional Requirements of Stakeholders},
year={2002},
volume={E85-D},
number={4},
pages={623-636},
abstract={System specifications should be refined to meet stakeholders' requirements as much as possible, because the first specification does not satisfy all stakeholders in general. This paper presents a procedure to refine behavioral specification to satisfy stakeholders. Non-functional requirements are used for checking stakeholders' satisfaction. With this procedure, stakeholder-dissatisfaction can be reduced and new possibilities to satisfy or dissatisfy other stakeholders can be found, since a modification to cancel dissatisfaction can sometimes influence the satisfaction of the others.},
keywords={},
doi={},
ISSN={},
month={April},}
Copy
TY - JOUR
TI - Refining Behavioral Specification for Satisfying Non-functional Requirements of Stakeholders
T2 - IEICE TRANSACTIONS on Information
SP - 623
EP - 636
AU - Haruhiko KAIYA
AU - Kenji KAIJIRI
PY - 2002
DO -
JO - IEICE TRANSACTIONS on Information
SN -
VL - E85-D
IS - 4
JA - IEICE TRANSACTIONS on Information
Y1 - April 2002
AB - System specifications should be refined to meet stakeholders' requirements as much as possible, because the first specification does not satisfy all stakeholders in general. This paper presents a procedure to refine behavioral specification to satisfy stakeholders. Non-functional requirements are used for checking stakeholders' satisfaction. With this procedure, stakeholder-dissatisfaction can be reduced and new possibilities to satisfy or dissatisfy other stakeholders can be found, since a modification to cancel dissatisfaction can sometimes influence the satisfaction of the others.
ER -