| Feather, M.S., FLEA : Formal Language for Expressing Assumptions Language Description, June 25, 1997. |
....on violations of soft goals and or assumptions [Fic95] We are currently working on a monitoring scheme that can be sketched as follows. At specification time, the temporal logic assertions that capture soft goals and assumptions are transformed into assertions in the event based FLEA language [Fea97], from which a corresponding monitor can be generated. Two kinds of parameters are also extracted during the analysis: monitored parameters (for observing behaviour) and control parameters (for changing behaviour) Consider, for example, the ReviewerReliable assumption which says that a reviewer ....
M. Feather, "FLEA: Formal Language for Expressing Assumptions --Language Description", Internal Report, March 1997.
....specification of policies they are not sufficient for every policy that users might find appropriate. It is necessary to compose events, for example to subsume different events that all trigger the same check. Event composition is a feature of FLEA, a formal language for expressing assumptions [8]. FLEA includes triggers with operators for temporal and logical event composition. We use FLEA s logical OR operator to express that a check will be triggered when either of the combined events is raised. An example is the following policy: Open(add) OR Open(ddd) UR04, ERROR, LIST) It ....
M. Feather. FLEA: Formal Language for Expressing Assumptions -- Language Description. Private Communication, April 1997.
....found by exhaustively searching a state based model of requirements for specified properties. Murphi[47] SMV[168] Spin[104] Executing monitoring Requirement interactions are found by monitoring a system implementation for certain events that indicate specified requirement properties. FLEA[57][62] InferQualityInteractions (R1,R2) R1,R2 : REQUIREMENT, QC1,QC2 : QUALITYCLASS, Q1,Q2 : QUALITY, INT1 : INTERACTION, R1 QUALITY Q1) Q1 QC1) QC1 INT1 QC2) Q2 QC2) R2 QUALITY Q2) INT2 : INTERACTION (Q1 INT2 Q2) Processes of Requirement Interaction Management 22 1999 ....
.... monitoring to track the achievement of requirements during system execution as part of an architecture to allow the dynamic reconfiguration of component software[69] Feather has produced a working system, called FLEA, that allows one to monitor events defined in a requirements monitoring language[57][62] FLEA captures interesting events as assertions in a database. An external system inserts the assertions into the AP5 database. When a monitored condition occurs, its defined action is executed. Thus, monitoring mainly consists of the translation of requirements monitoring descriptions to ....
Feather, M.S., FLEA : Formal Language for Expressing Assumptions Language Description, June 25, 1997.
.... to track the achievement of requirements during system execution as part of an architecture to allow the dynamic reconfiguration of component software[14] Feather has produced a working system, called FLEA, that allows one to monitor interesting events defined in a requirements monitoring language[12]. Finkelstein has since illustrated how the technique may be used to monitor process compliance[11] for example, organizational compliance to ISO 9000 or IEEE process descriptions[28] Our work on dialog monitoring is derived from these work, but also include an element of dialog structuring. Two ....
Feather, M.S., FLEA : Formal Language for Expressing Assumptions Language Description, June 25, 1997.
No context found.
Feather, M.S., FLEA : Formal Language for Expressing Assumptions Language Description, June 25, 1997.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC