Runtime monitoring of cross-cutting policy

Shin Nakajima; Naoyasu Ubayashi; Keiji Hokamura

doi:10.1109/EA.2009.5071579

Runtime monitoring of cross-cutting policy

Shin Nakajima, Naoyasu Ubayashi, Keiji Hokamura

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

Abstract

In open systems, certain unfavorable situations due to unanticipated user behavior may be seen, which results in a violation of cross-cutting policy. This paper proposes a runtime monitoring method to check such problems. Since there is a large gap, a certain link is needed between the policy and runtime execution method. We employ a two-step checking approach; an offline symptom checking and a runtime monitoring. The ingredient to tie the two steps is a Linear-time Temporal Logic formula for the cross-cutting policy to look at.

Original language	English
Title of host publication	Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009
Pages	20-24
Number of pages	5
DOIs	https://doi.org/10.1109/EA.2009.5071579
Publication status	Published - 2009
Externally published	Yes
Event	2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009 - Vancouver, BC, Canada Duration: May 18 2009 → May 18 2009

Other

Other	2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009
Country/Territory	Canada
City	Vancouver, BC
Period	5/18/09 → 5/18/09

All Science Journal Classification (ASJC) codes

Hardware and Architecture
Software

Access to Document

10.1109/EA.2009.5071579

Cite this

Nakajima, S, Ubayashi, N & Hokamura, K 2009, Runtime monitoring of cross-cutting policy. in Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009., 5071579, pp. 20-24, 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009, Vancouver, BC, Canada, 5/18/09. https://doi.org/10.1109/EA.2009.5071579

@inproceedings{9819baad3c6d4a8c8dc29020d19c81eb,

title = "Runtime monitoring of cross-cutting policy",

abstract = "In open systems, certain unfavorable situations due to unanticipated user behavior may be seen, which results in a violation of cross-cutting policy. This paper proposes a runtime monitoring method to check such problems. Since there is a large gap, a certain link is needed between the policy and runtime execution method. We employ a two-step checking approach; an offline symptom checking and a runtime monitoring. The ingredient to tie the two steps is a Linear-time Temporal Logic formula for the cross-cutting policy to look at.",

author = "Shin Nakajima and Naoyasu Ubayashi and Keiji Hokamura",

year = "2009",

doi = "10.1109/EA.2009.5071579",

language = "English",

isbn = "9781424437191",

pages = "20--24",

booktitle = "Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009",

note = "2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009 ; Conference date: 18-05-2009 Through 18-05-2009",

}

TY - GEN

T1 - Runtime monitoring of cross-cutting policy

AU - Nakajima, Shin

AU - Ubayashi, Naoyasu

AU - Hokamura, Keiji

PY - 2009

Y1 - 2009

N2 - In open systems, certain unfavorable situations due to unanticipated user behavior may be seen, which results in a violation of cross-cutting policy. This paper proposes a runtime monitoring method to check such problems. Since there is a large gap, a certain link is needed between the policy and runtime execution method. We employ a two-step checking approach; an offline symptom checking and a runtime monitoring. The ingredient to tie the two steps is a Linear-time Temporal Logic formula for the cross-cutting policy to look at.

AB - In open systems, certain unfavorable situations due to unanticipated user behavior may be seen, which results in a violation of cross-cutting policy. This paper proposes a runtime monitoring method to check such problems. Since there is a large gap, a certain link is needed between the policy and runtime execution method. We employ a two-step checking approach; an offline symptom checking and a runtime monitoring. The ingredient to tie the two steps is a Linear-time Temporal Logic formula for the cross-cutting policy to look at.

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

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

U2 - 10.1109/EA.2009.5071579

DO - 10.1109/EA.2009.5071579

M3 - Conference contribution

AN - SCOPUS:70349820813

SN - 9781424437191

SP - 20

EP - 24

BT - Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009

T2 - 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, EA 2009

Y2 - 18 May 2009 through 18 May 2009

ER -

Runtime monitoring of cross-cutting policy

Abstract

Other

All Science Journal Classification (ASJC) codes

Access to Document

Other files and links

Fingerprint

Cite this