Difference between revisions of "ERE Monitoring Algorithm"
From FSL
| Line 2: | Line 2: | ||
{{shortcut|[[MOP]] <br /> [[Special:EREPlugin|ERE Plugin]] <br /> [[ERE Plugin Input Syntax]] <br /> [[ERE Plugin Output Syntax]] <br /> ERE Monitoring Algorithm}} | {{shortcut|[[MOP]] <br /> [[Special:EREPlugin|ERE Plugin]] <br /> [[ERE Plugin Input Syntax]] <br /> [[ERE Plugin Output Syntax]] <br /> ERE Monitoring Algorithm}} | ||
| − | + | '''''Under construction!''''' | |
| + | |||
| + | Regular expressions can be easily understood by ordinary software engineers and programmers, as shown by the immense interest in and the success of scripting languages like Perl, based essentially on regular expression pattern matching. We believe that regular expressions provide an elegant and powerful specification language also for monitoring requirements, because an execution trace of a program is in fact a string of states. Extended regular expressions (EREs) add complementation to regular expressions, which brings additional benefits by allowing one to specify patterns that must not occur during an execution. Complementation gives one the power to express patterns on strings non-elementarily more compactly. | ||
Revision as of 18:10, 28 October 2008
Under construction!
Regular expressions can be easily understood by ordinary software engineers and programmers, as shown by the immense interest in and the success of scripting languages like Perl, based essentially on regular expression pattern matching. We believe that regular expressions provide an elegant and powerful specification language also for monitoring requirements, because an execution trace of a program is in fact a string of states. Extended regular expressions (EREs) add complementation to regular expressions, which brings additional benefits by allowing one to specify patterns that must not occur during an execution. Complementation gives one the power to express patterns on strings non-elementarily more compactly.
