Interface LSA -> BSS: Use Cases and their Implementation

1 Actors

• Generator
• Director
• LSA
• Request Processor
• Scheduling Application

2 Making a new Pattern executable

1. The Scheduling Application calls LSA to make the Pattern resident
2. The Scheduling Application calls LSA to drive the Pattern
3. The Scheduling Application calls LSA to add the Pattern to a Pattern Group
   1. LSA assigns a set of default execution conditions to the Pattern
   2. LSA calls the Generator to add the schedule for the Pattern
   3. LSA calls the Generator to modify the schedules for the other Patterns in the Pattern Group by adding edges pointing to the Pattern Ask Mathias if it is necessary to stop a currently running Pattern (Group) to do that.
   4. LSA calls the Director to publish the new Pattern Group definition (including execution conditions)
   5. LSA calls the Request Processor to publish the new Dynamic Signals

3 Making a currently executed Pattern non-resident

1. Scheduling App calls LSA to remove the Pattern from a Pattern Group
   1. LSA calls the Request Processor to prevent execution of the Pattern by setting the corresponding Signal to "true" Ask Mathias how to ensure that this request has actually been completed, i.e. the Pattern is not running.
   2. LSA calls the Director to publish the updated Pattern Group definition(s), now excluding the Pattern
   3. LSA calls the Request Processor to publish the updated list of Dynamic Signals, now excluding those exclusive to the Pattern
   4. LSA calls the Generator to remove the schedule for the Pattern
      1. The Generator automatically removes edges pointing to the Pattern from other Patterns
2. Scheduling App calls LSA to make the Pattern non-resident

4 Trimming a currently played Pattern

1. LSA calls the Request Processor to prevent execution of the Pattern by setting the corresponding Signal to "true" Ask Mathias how to ensure that this request has actually been completed, i.e. the Pattern is not running.
2. LSA calls the Generator to remove the outdated schedule for the Pattern
   1. The Generator automatically removes edges pointing to the Pattern from other Patterns
3. LSA calls the Generator to add the updated schedule for the Pattern
4. LSA calls the Generator to modify the schedules for the other Patterns in the Pattern Group by adding edges pointing to the Pattern Ask Mathias if it is necessary to stop a currently running Pattern (Group) to do that.
5. LSA calls the Request Processor to allow execution of the Pattern again by setting the corresponding Signal to "false"