Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Monitoring-Oriented Programming (MOP1) [21, 18, 22, 19] is a formal framework for software development and analysis, in which the developer specifies desired properties using definable specification formalisms, along with code to execute when properties are violated or validated. The MOP framework automatically generates monitors from the specified properties and then integrates them together with the user-defined code into the original system.   The previous design of MOP only allod specifications without parameters, so it could not be used to state and monitor safety properties referring to two or more related objects.   propose a  parametric specification formalism-independent extension of MOP , together with an implementation of JavaMOP that supports parameters. In our current implementation, parametric specifications are translated into AspectJ code and then aved into the application using off-the-shelf AspectJ compilers; hence, MOP specifications can be seen as formal or logical aspects.   Our JavaMOP implementation was extensively evaluated on two benchmarks, Dacapo [14] and Tracematches [8], showing that runtime verification in general and MOP in particular are feasible. In some of the examples, millions of monitor instances are generated, each observing a set of related objects. To keep the runtime overhead of monitoring and event observation low,  devised and implemented a  decentralized indexing  optimization. Less than 8% of the experiments shod more than 10% runtime overhead; in most cases our tool generates monitoring code as efficient as the hand-optimized code. Despite its genericity, JavaMOP is empirically shown to be more efficient than runtime verification systems specialized and optimized for particular specification formalisms. Many property violations re detected during our experiments; some of them are benign, others indicate defects in programs. Many of these are subtle and hard to find by ordinary testing.
['Feng Chen', 'Grigore Rosu']
I am writing a research paper on a idea Mop: an efficient and generic runtime verification framework
[{"from": "human", "value": "I am writing a research paper on a idea Mop: an efficient and generic runtime verification framework"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Monitoring-Oriented Programming (MOP1) [21, 18, 22, 19] is a formal framework for software development and analysis, in which the developer specifies desired properties using definable specification formalisms, along with code to execute when properties are violated or validated. The MOP framework automatically generates monitors from the specified properties and then integrates them together with the user-defined code into the original system.   The previous design of MOP only allod specifications without parameters, so it could not be used to state and monitor safety properties referring to two or more related objects.   propose a  parametric specification formalism-independent extension of MOP , together with an implementation of JavaMOP that supports parameters. In our current implementation, parametric specifications are translated into AspectJ code and then aved into the application using off-the-shelf AspectJ compilers; hence, MOP specifications can be seen as formal or logical aspects.   Our JavaMOP implementation was extensively evaluated on two benchmarks, Dacapo [14] and Tracematches [8], showing that runtime verification in general and MOP in particular are feasible. In some of the examples, millions of monitor instances are generated, each observing a set of related objects. To keep the runtime overhead of monitoring and event observation low,  devised and implemented a  decentralized indexing  optimization. Less than 8% of the experiments shod more than 10% runtime overhead; in most cases our tool generates monitoring code as efficient as the hand-optimized code. Despite its genericity, JavaMOP is empirically shown to be more efficient than runtime verification systems specialized and optimized for particular specification formalisms. Many property violations re detected during our experiments; some of them are benign, others indicate defects in programs. Many of these are subtle and hard to find by ordinary testing."}]