Stepwise context boundary exploration using guide words

研究成果: ジャーナルへの寄稿Conference article

抄録

Most requirements elicitation methods do not explicitly provide a systematic way for deciding the boundary of the usage context that should be taken into account because it is essentially difficult to decide which context element should be included as the system requirements. If a developer explores the context boundary in an ad-hoc manner, the developer will be faced with the frame problem because there are unlimited context elements in the real world where the target system exists. There are many application domains that should take into account the frame problem: security, safety, network threats, and user interactions. To deal with this problem, this paper proposes a new type of requirements analysis method for exploring the context boundary using guide words, a set of hint words for finding a context element affecting the system behavior. The target of our method is embedded systems that can be abstracted as a sensor-and-actuator machine exchanging the physical value between a system and its context. In our method, only the value-context elements, a kind of value objects, are extracted as the associated context elements. By applying the guide words, we can explore only a sequence of context elements affecting the data value and avoid falling into the frame problem at the requirements analysis phase.

元の言語英語
ページ(範囲)131-138
ページ数8
ジャーナルCEUR Workshop Proceedings
734
出版物ステータス出版済み - 12 1 2011
イベントCAiSE Forum 2011 - London, 英国
継続期間: 6 22 20116 24 2011

Fingerprint

Embedded systems
Actuators
Sensors

All Science Journal Classification (ASJC) codes

  • Computer Science(all)

これを引用

Stepwise context boundary exploration using guide words. / Ubayashi, Naoyasu; Kamei, Yasutaka.

:: CEUR Workshop Proceedings, 巻 734, 01.12.2011, p. 131-138.

研究成果: ジャーナルへの寄稿Conference article

@article{d1a5a6c66f71470f9c21fc94efb19666,
title = "Stepwise context boundary exploration using guide words",
abstract = "Most requirements elicitation methods do not explicitly provide a systematic way for deciding the boundary of the usage context that should be taken into account because it is essentially difficult to decide which context element should be included as the system requirements. If a developer explores the context boundary in an ad-hoc manner, the developer will be faced with the frame problem because there are unlimited context elements in the real world where the target system exists. There are many application domains that should take into account the frame problem: security, safety, network threats, and user interactions. To deal with this problem, this paper proposes a new type of requirements analysis method for exploring the context boundary using guide words, a set of hint words for finding a context element affecting the system behavior. The target of our method is embedded systems that can be abstracted as a sensor-and-actuator machine exchanging the physical value between a system and its context. In our method, only the value-context elements, a kind of value objects, are extracted as the associated context elements. By applying the guide words, we can explore only a sequence of context elements affecting the data value and avoid falling into the frame problem at the requirements analysis phase.",
author = "Naoyasu Ubayashi and Yasutaka Kamei",
year = "2011",
month = "12",
day = "1",
language = "English",
volume = "734",
pages = "131--138",
journal = "CEUR Workshop Proceedings",
issn = "1613-0073",
publisher = "CEUR-WS",

}

TY - JOUR

T1 - Stepwise context boundary exploration using guide words

AU - Ubayashi, Naoyasu

AU - Kamei, Yasutaka

PY - 2011/12/1

Y1 - 2011/12/1

N2 - Most requirements elicitation methods do not explicitly provide a systematic way for deciding the boundary of the usage context that should be taken into account because it is essentially difficult to decide which context element should be included as the system requirements. If a developer explores the context boundary in an ad-hoc manner, the developer will be faced with the frame problem because there are unlimited context elements in the real world where the target system exists. There are many application domains that should take into account the frame problem: security, safety, network threats, and user interactions. To deal with this problem, this paper proposes a new type of requirements analysis method for exploring the context boundary using guide words, a set of hint words for finding a context element affecting the system behavior. The target of our method is embedded systems that can be abstracted as a sensor-and-actuator machine exchanging the physical value between a system and its context. In our method, only the value-context elements, a kind of value objects, are extracted as the associated context elements. By applying the guide words, we can explore only a sequence of context elements affecting the data value and avoid falling into the frame problem at the requirements analysis phase.

AB - Most requirements elicitation methods do not explicitly provide a systematic way for deciding the boundary of the usage context that should be taken into account because it is essentially difficult to decide which context element should be included as the system requirements. If a developer explores the context boundary in an ad-hoc manner, the developer will be faced with the frame problem because there are unlimited context elements in the real world where the target system exists. There are many application domains that should take into account the frame problem: security, safety, network threats, and user interactions. To deal with this problem, this paper proposes a new type of requirements analysis method for exploring the context boundary using guide words, a set of hint words for finding a context element affecting the system behavior. The target of our method is embedded systems that can be abstracted as a sensor-and-actuator machine exchanging the physical value between a system and its context. In our method, only the value-context elements, a kind of value objects, are extracted as the associated context elements. By applying the guide words, we can explore only a sequence of context elements affecting the data value and avoid falling into the frame problem at the requirements analysis phase.

UR - http://www.scopus.com/inward/record.url?scp=84890709393&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84890709393&partnerID=8YFLogxK

M3 - Conference article

AN - SCOPUS:84890709393

VL - 734

SP - 131

EP - 138

JO - CEUR Workshop Proceedings

JF - CEUR Workshop Proceedings

SN - 1613-0073

ER -