Checking Traces for Regulatory Conformance

Simple item page
dc.contributor.authorDinesh, Nikhil
dc.contributor.authorJoshi, Aravind K
dc.contributor.authorLee, Insup
dc.contributor.authorSokolsky, Oleg
dc.contributor.authorDinesh, Nikhil
dc.contributor.authorJoshi, Aravind K
dc.contributor.authorLee, Insup
dc.contributor.authorSokolsky, Oleg
dc.date2023-05-17T02:13:34.000
dc.date.accessioned2023-05-22T12:47:55Z
dc.date.available2023-05-22T12:47:55Z
dc.date.issued2008-03-30
dc.date.submitted2008-05-07T18:29:28-07:00
dc.description.abstractWe consider the problem of checking whether the operations of an organization conform to a body of regulation. The immediate motivation comes from the analysis of the U.S. Food and Drug Administration regulations that apply to bloodbanks - organizations that collect, process, store, and use donations of blood and blood components. Statements in such regulations convey constraints on operations or sequences of operations that are performed by an organization. It is natural to express these constraints in a temporal logic. There are two important features of regulatory texts that need to be accommodated by a representation in logic. First, the constraints conveyed by regulation can be obligatory (required) or permitted (optional). Second, statements in regulation refer to others for conditions or exceptions. An organization conforms to a body of regulation if and only if it satisfies all the obligations. However, permissions provide exceptions to obligations, indirectly affecting conformance. In this paper, we extend linear temporal logic to distinguish between obligations and permissions, and to allow statements to refer to others. While the resulting logic allows for a direct representation of regulation, evaluating references between statements has high complexity. We discuss an empirically motivated assumption that lets us replace references with tests of lower complexity, leading to efficient trace-checking algorithms in practice.
dc.description.commentsPostprint version. Presented at <em>RV'08 - Eighth Workshop on Runtime Verification</em>, Satellite workshop of ETAPS'08, March 2008.
dc.identifier.urihttps://repository.upenn.edu/handle/20.500.14332/6414
dc.legacy.articleid1395
dc.legacy.fulltexturlhttps://repository.upenn.edu/cgi/viewcontent.cgi?article=1395&amp;context=cis_papers&amp;unstamped=1
dc.source.issue370
dc.source.journalDepartmental Papers (CIS)
dc.source.peerreviewedtrue
dc.source.statuspublished
dc.titleChecking Traces for Regulatory Conformance
dc.typePresentation
digcom.contributor.authorisAuthorOfPublication|email:nikhild@seas.upenn.edu|institution:University of Pennsylvania|Dinesh, Nikhil
digcom.contributor.authorisAuthorOfPublication|email:joshi@seas.upenn.edu|institution:University of pennsylvania|Joshi, Aravind K
digcom.contributor.authorisAuthorOfPublication|email:lee@cis.upenn.edu|institution:University of Pennsylvania|Lee, Insup
digcom.contributor.authorisAuthorOfPublication|email:sokolsky@cis.upenn.edu|institution:University of Pennsylvania|Sokolsky, Oleg
digcom.identifiercis_papers/370
digcom.identifier.contextkey505623
digcom.identifier.submissionpathcis_papers/370
digcom.typeconference
dspace.entity.typePublication
relation.isAuthorOfPublication2b07eda6-fd27-43fe-9faf-a945691e5090
relation.isAuthorOfPublicationd3909767-0b3f-4197-837c-49ce268776e3
relation.isAuthorOfPublication45a9eed5-3211-4c36-b40d-6394302dfdce
relation.isAuthorOfPublication35e1b18e-15fe-4438-be3b-84593f70a40a
relation.isAuthorOfPublication.latestForDiscovery2b07eda6-fd27-43fe-9faf-a945691e5090
upenn.schoolDepartmentCenterDepartmental Papers (CIS)
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
08rv.pdf
Size:
177.58 KB
Format:
Adobe Portable Document Format
Download
Collection
Presentations