z-lect6_eventSys_Case(不讲).pptVIP

Architecture of Software Systems After circular shift: Americans like driving cars fast on weekend days like driving cars fast on weekend days Americans driving cars fast on weekend days Americans like cars fast on weekend days Americans like driving fast on weekend days Americans like driving cars on weekend days Americans like driving cars fast weekend days Americans like driving cars fast on days Americans like driving cars fast on weekend Run-Time Event Interactions The act of adding a new line to the first LineStorage causes an event to be sent to the CircularShifter module. It allows the CircularShifter module to produce all circular shifts of the line and to store them into the second line storage. This in turn causes another event to be sent to the Alphabetizer module, so that this module may sort the newly added circular shifts. interactions in the system: Step 1: (register) The CircularShifter registers its interest in the first LineStorage module. The Alphabetizer module registers its interest in the second LineStorage module. Step 2: (send event) The first LineStorage module sends an event whenever a new line has been added to it. Step 3: (receive event and react) The CircularShifter module receives the event sent by the first LineStorage module. Then the CircularShifter module produces all circular shifts of the newly added line and store those shifts in the second LineStorage module. Step 4: (send event) The second LineStorage module sends an event whenever a new circular shift has been added to it. Step 5: (receive event and react) The Alphabetizer module receives the event sent by the second LineStorage module. Then the Alphabetizer module sorts circular shifts. Event Dispatching Strategy the KWIC system uses observable/Observers pattern for handling events in the system. The two LineStorage modules are implemented as Observable modules. CircularShifter and Alphabetizer modules are implemented as Observers, with the C