Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Automatic synthesis of state machines from trace diagrams
Software—Practice & Experience
Aspect-Oriented Programming is Quantification and Obliviousness
Aspect-Oriented Programming is Quantification and Obliviousness
Capturing and Executing Behavioral Requirements: The Play-In/Play-Out Approach,
Capturing and Executing Behavioral Requirements: The Play-In/Play-Out Approach,
From multi-modal scenarios to code: compiling LSCs into aspectJ
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
A pattern story for combining crosscutting concern state machines
Proceedings of the 14th Conference on Pattern Languages of Programs
| Hi-index | 0.00 |
This paper describes two patterns, Scenario Monitor and Bind Completed Scenario to Event. The first allows scenarios to be monitored. The second uses scenario monitoring to address state based crosscutting concerns in traditional data transformational systems. Crosscutting concerns are tangled with core application concerns and scattered throughout a system. Core concerns are monitored for scenarios that represent events of interest to a crosscutting concern. When the monitored scenarios complete an event is injected into a crosscutting state machine that may react by introducing additional behavior. These patterns permit the monitoring and subsequent behavioral reaction in a minimally invasive way with loose coupling. No special tools or languages are required. An example using the approach is presented.