default Meteorology v0.3.pd C:\Documents and Settings\Dave\My Documents\MeterologyCode C:\Documents and Settings\Dave\My Documents C:\Documents and Settings\Dave\My Documents\Meteorology v0.3.pd 3.2c au.edu.rmit.cs.prometheus.gui.diagram.capabilityoverview.CapabilityOverviewDiagramModel#57 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=70> 70 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=70> 46 warnings <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=68> 68 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=68> RecogniseHighWindCap Capability to recognise a high wind situation and create an appropriate warning. See notes for descriptions of high wind situations according to the specifications 55 RecogniseHighWindCap Recognise high wind situation Check to see if there is a high wind situation likely at an airport sometime in the next 6 hours. 22 Check for high wind situation Check high wind Check to see if the wind strength in a forecast is greater than 30 knots 26 Check situation 1 Check really unexpected, increasing wind Check to see if the current wind strength is greater than 5 knots, is significantly higher than forecast, and is increasing fairly rapidly 27 Check situation 2 Check high, unexpected, increasing wind Check to see if the wind strength is increasing, is over 20 knots and is higher than forecast. 28 Check situation 3 :true Create Warning Create a relevant warning with appropriate data. 260 Recognise high wind situation Create warning A high wind situation is considered if any of the following are true: - the current wind strength is greater than 5 knots, is significantly higher than forecast, and is increasing fairly rapidly -the wind strength in a forecast is greater than 30 knots -the wind strength is increasing, is over 20 knots and is higher than forecast. ReportReallyHighWindP Reports a high wind warning 90 ReportReallyHighWindP planMessagePair-180 180 planMessagePair-180 NewDataE InferenceGoalEvent autoposted by AWS_Readings beliefset or Forecast beliefset when new data is added. 77 NewDataE agentDiagramPair-78 78 agentDiagramPair-78 RecogniseForecastDiscrepancyCap The capability to recognise when there is an alertable situation due to a significant discrepancy between the forecast conditions and actual conditions and create a relevant warning. See notes for description of forecast discrepancy. 57 RecogniseForecastDiscrepancyCap Recognise forecast discrepency Check to see if there is a (serious) discrepancy between the forecast data and the actual data at the current time. 21 Recognise forecast discrepency Check wind Check to see if the forecast wind speed differs from the actual windspeed by 5 knots or more. 23 Check wind Check fog Check to see if the forecast for fog/no fog differs from the actual data 24 Check fog :true Recognise forecast discrepancy Create warning A forecast discrepancy is considered to be one of the following: - A discrepancy between the forecast for fog and actual presence - A difference between forecast wind and actual wind of 5 knots or more - A difference between the forecast trend and the actual trend ReportFogDiscrepancyP Creates a Forecast discrepancy warning 129 ReportFogDiscrepancyP planMessagePair-187 187 planMessagePair-187 capabilityMessagePair-80 80 capabilityMessagePair-80 ReportWindDiscrepancyP Creates a Forecast discrepancy warning 135 ReportWindDiscrepancyP planMessagePair-188 188 planMessagePair-188 planMessagePair-216 216 planMessagePair-216 NewWarningE Posted when there is an alertable situation at an airport. Contains information relevant to the warning. 144 NewWarningE capabilityDiagramPair-145 145 capabilityDiagramPair-145 PostWarningP Sends warnings on to relevant users 143 PostWarningP planMessagePair-146 146 planMessagePair-146 agentDiagramPair-196 196 agentDiagramPair-196 RecogniseImmediateChangeCap Capability to recognise when there is an alertable situation due to a significant change in the immediate forecast and create a relevant warning. See notes for description of significant change. 56 RecogniseImmediateChangeCap Recognise change in immediate forecast Check to see if there is a significant difference between the forecast situation for the next 2 hours and what was previously forecast. 20 Recognise change in immediate forecast Check high wind change Check to see if there is a change in the forecast for a high wind condition (30 knots or higher) 29 Check high wind change Check fog change Check to see if there is a change in the appearance of fog 30 Check fog change Check temp below 0 Check to see if there is a change in the forecast situation for the temperature being below freezing 31 Check temp below 0 Check high rain Check for a change in the high rainfall situation (over 10cm) 32 Check high rain :true A significant change to the forecast is considered if there is a change in the forecast for the presence of: - winds over 20 knots - rain over 10cm - fog - below zero temperatures ReportHighWindChangeP Creates an immediate forecast change warning 107 ReportHighWindChangeP planMessagePair-183 183 planMessagePair-183 capabilityMessagePair-81 81 capabilityMessagePair-81 ReportFogChangeP Creates a immediate change in forecast warning 112 ReportFogChangeP planMessagePair-184 184 planMessagePair-184 planMessagePair-212 212 planMessagePair-212 capabilityMessagePair-207 207 capabilityMessagePair-207 ReportTempBelowZeroChangeP Creates a immediate change in forecast warning 121 ReportTempBelowZeroChangeP planMessagePair-185 185 planMessagePair-185 planMessagePair-213 213 planMessagePair-213 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=65> 65 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=65> forecasts Beliefset to store both the current forecasts and the previous set of forecasts for a given airport. There will be one such beliefset per AirportAgent and thus per airport. 45 forecasts Forecasts Time - Date representing the time of the forecast old - Boolean representing true if this is the previous forecast temp - Double, in degrees celsius wind - Double, in knots rain - Double, in cm fog - Boolean Queries: - Query to access each variable for both current and previous forecast - Query to move new forecast to old, so that new forecast can be written. Datastore will start empty, and be written when first data arrives Forecasts arrive Checking for alertable situation <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=59> 59 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=59> UpdateTAFP Handle forecast data by writing to beliefset 85 UpdateTAFP planMessagePair-179 179 planMessagePair-179 ForecastE Set of predicted weather for the next 12 hours for the given airport 172 ForecastE systemDiagramPair-173 173 systemDiagramPair-173 AirportAgent An agent to handle the recognition of any alertable situations at a specific airport. There will be one AirportAgent per airport in the system 47 AirportAgent The same period of time that the associated airport is part of the system At initialization the airport agent must subscribe to receive data from the associated sensor via the external action subscribeAWSSourceAgent Subscription to sensor should be removed so that another agent can connect to it in the future. ObtainAWSCap Capability to receive and appropriately store all incoming AWS data. This includes the ability to manually request data from the sensor. 53 ObtainAWSCap Update AWS beliefs Update the beliefsets with most up to date data 16 Update AWS beliefs Recieve AWS data Recieve the data from the airport 15 Recieve AWS data Request new data Receive data and process into appropriate format Store in datastore Request Data A request sent from the system to an Airport Sensor requesting up-to-date data. 4 Airport Sensor The automatic weather station which makes physical measurements of the current weather conditions. 2 AWS DataE AWS readings from the simulator which contain up to date readings for the airport 7 Obtain Data Scenario scenario This high-level scenario covers acquistion of all data from both the Automatic Weather Stations and the Forecaster 6 subscribeAWSSourceAgent This external action subscribes the system to receive AWS readings from a sensor. 227 None N/A N/A N/A N/A 226 Data retrieval Covers the protocol between ForecasterAgent and AirportAgent when new Forecast data arrives 224 protocolMessagePair-240 240 ForecasterAgent An agent used to accept incoming forecasts and split them into different airports. There will only be one forecast agent in any system. 171 ForecasterAgent 1 1 Life of the system Subscription must be sent to forecaster actor to receive forecasts when they are available Subscription should be removed cleanly. SendForecastsP Handle the incoming TAF data, split and send to relevant airports 177 SendForecastsP TAF dataE Incoming Forecasts from an external forecaster. 8 TAF dataE Forecaster Forecasts for all airports for the next 12 hours Quarter hourly Warnings Covers the complete protocol between agents for subscribing a user, detecting a warning and notifying appropriate users. 229 protocolMessagePair-232 232 SubscriptionE Message sent from the GUIAgent to the AirportAgent indicating that the user wants to subscribe to this airport 156 SubscriptionE systemDiagramPair-157 157 systemDiagramPair-157 GUIAgent Agent which handles all interactions with the user. Receives subscriptions and shows warnings. There will be one GUIAgent per user. 48 GUIAgent Time that the associated user is connected GUI should be displayed enabling the user to subscribe to airports as necessary -Subscriptions to airports should be removed -GUI window should close MakeSubscriptionP Create a subscription event and send it to the relevant airport 167 MakeSubscriptionP Subscription from User This is a request from a human user to subscribe to receive warnings about a particular airport. 221 Subscribe User scenario This scenario covers the necessary processes to subscribe a user to the system. First, the user must make the subscription attempt, probably via a GUI. This subscription is received by the system and stored appropriately. 149 Subscribe User scenario <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=263> Via a GUI terminal, the User indicates a need to subscribe to a given airport 263 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=264> Creates a subscription and sends to the relevant airport 264 Make Subscription Create a subscription and send it to the relevant airport 151 Make Subscription SubscribeToAirport Role which handles a subscription request from a user and makes the request to the appropriate airport. 154 SubscribeToAirport <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=265> Updates the agents beliefs about which users are subscribed 265 Update Subscriptions Beliefs Adds a users subscription to a list of subscriptions 152 Update Subscriptions Beliefset subscriptions Contains a list of the names of GUIUsers which are subscribed to recieve warnings from this airport. There will be one subscriptions datastore per AirportAgent and thus per airport. 155 subscriptions Subscriptions User Will start empty, and be written to when first subscription is made. Subscription is made by user Determining which users to send warning to. <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=161> 161 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=161> AddSubscriptionP Handles an incoming subscription from a user and adds this subscription to the subscriptions datastore 165 AddSubscriptionP planMessagePair-166 166 planMessagePair-166 capabilityMessagePair-162 162 capabilityMessagePair-162 agentMessagePair-159 159 agentMessagePair-159 protocolMessagePair-238 238 agentMessagePair-158 158 agentMessagePair-158 planMessagePair-168 168 planMessagePair-168 SubscriptionsProtocol Covers the Protocol between GUIAgent and Airport agent when a new user subscribes to the system 236 protocolMessagePair-239 239 WarningE Message sent from an AirportAgent to a User agent subscribed to the airport 49 WarningE systemDiagramPair-50 50 systemDiagramPair-50 agentMessagePair-51 51 agentMessagePair-51 protocolMessagePair-235 235 agentMessagePair-52 52 agentMessagePair-52 AlertUserP Checks if the GUI is meant to display that type of Alert and then displays it 169 AlertUserP planMessagePair-170 170 planMessagePair-170 Alert User Scenario Scenario covering the process of alerting a user to a potential situation. 9 Alert User Scenario Detect Alertable Situation Determine that there is an alertable situation based on AWS readings and forecasts 19 Detect Alertable Situation :true Display warning Display the warning to the user 36 Display warning Check Subscribers Check which users require alerts from the given airport 34 Check Airport Show Warning This action is the interaction between the system and the human user. A warning will be displayed on a screen via a pop-up or some other method 11 User This is the human operator who will access the system via a GUI. 1 User Show Warning Type of warning Warning message N/A N/A N/A N/A Always true; N/A N/A Check types of alerts the user wants displayed Show alert capabilityMessagePair-74 74 capabilityMessagePair-74 planMessagePair-147 147 planMessagePair-147 72 subscribeTAFSourceAgent A subscription sent to the forecaster actor registering it to receive forecast data when it is available. 231 Forecaster The external system which makes weather predictions. This may be a human, a computer system or a combination of both. 3 Forecaster None N/A N/A N/A N/A <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.ProtocolDistributionPair ID=225> 225 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.ProtocolDistributionPair ID=230> 230 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.ProtocolDistributionPair ID=233> 233 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.ProtocolDistributionPair ID=237> 237 Inform of an alertable situation at the given airport Details of the warning. start SubscriptionsProtocol actor A User agent B GUIAgent agent C AirportAgent percept A B Subscription from User message B C SubscriptionE box loop message C B WarningE action B A Show Warning end loop 160 Subscribe User Add a user to the system 148 Subscribe User <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=163> 163 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=163> Always true N/A N/A Retrieve user name from incoming messageEvent Add to datastore <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=164> 164 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=164> AddSubscription Role which covers adding a user subscription to a given airport 153 AddSubscription User User - The origin of the request Airport - The airport to subscribe to User Subscriptions Always true; N/A N/A Check user from which the subscription request originated Send to relevant airport with username DisplayWarning Role which covers the displaying of a warning to the human user 43 DisplayWarning To enable the user to subscribe to an airport No information is carried. The users name is obtained from the "From" field of the MessageEvent protocolMessagePair-234 234 agentMessagePair-175 175 agentMessagePair-175 capabilityMessagePair-176 176 capabilityMessagePair-176 54 agentMessagePair-174 174 agentMessagePair-174 planMessagePair-178 178 planMessagePair-178 Alert User Scenario scenario This scenario covers all the necessary processes to alert a user to certain situations. This involves detecting that an alertable situation exists by monitoring both the AWS data and the forecasts. An appropriate warning must then be created, and sent to all users who are subscribed to receive such warnings. 10 Alert User Scenario scenario Data stores have been updated <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=258> Determines if there is an alertable situation by checking beliefs against a set of rules 258 aws_readings Data store for storing AWS readings at each airport. There is one datastore per AiportAgent and therefore one per airport. Only the four most recent readings are stored, and older readings removed. 44 aws_readings AWSReadings Fields: Time of reading - Date Temperature - Double Wind - Double Rain - Double Fog - Boolean Aspects: - Query to obtain each reading individually, as well as current reading - function query to remove readings older than the previous 4 Data store can start empty, and as incoming readings arrive they will be written New AWS data arrives Checking for alertable situations <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=58> 58 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=58> <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=60> 60 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=60> UpdateAWSP Writes the incoming data to the AWS data store 76 UpdateAWSP True; N/A N/A Process data and write to beliefset <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=62> 62 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=62> ReportReallyUnexpectedIncreasingWindP Creates a high wind warning 97 ReportReallyUnexpectedIncreasingWindP planMessagePair-181 181 planMessagePair-181 capabilityMessagePair-79 79 capabilityMessagePair-79 ReportHighUnexpectedIncreasingWindP Create a high wind warning 101 ReportHighUnexpectedIncreasingWindP planMessagePair-182 182 planMessagePair-182 planMessagePair-210 210 planMessagePair-210 capabilityMessagePair-205 205 capabilityMessagePair-205 planMessagePair-208 208 planMessagePair-208 planMessagePair-209 209 planMessagePair-209 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=64> 64 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=64> If the wind is over 20 knots, increasing and is higher than forecast N/A N/A Post NewWarningE event with relevant data planMessagePair-87 87 planMessagePair-87 86 If the current wind strength is greater than 5 knots, is significantly higher than forecast, and is increasing fairly rapidly N/A N/A Post NewWarningE event with relevant data <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=67> 67 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=67> ReportTrendDiscrepancyP Creates a Forecast discrepancy warning 138 ReportTrendDiscrepancyP planMessagePair-223 223 planMessagePair-217 217 planMessagePair-217 capabilityMessagePair-206 206 capabilityMessagePair-206 planMessagePair-215 215 planMessagePair-215 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=66> 66 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=66> If the forecast trend differs from the actual trend. N/A N/A Post NewWarningE event with relevant data CheckForImmediateChange Role which covers the checking of data for a change in the immediate forecast 40 CheckForImmediateChange CheckForForecastDiscrepancy Role which covers checking data for a discrepancy between the forecast and actual readings 41 CheckForForecastDiscrepancy CheckForHighWind Roles which covers checking the data for a high wind situation 39 CheckForHighWind <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=262> Creates the relevant warning with warning message and type 262 CreateWarning Role which covers the creation of an appropriate warning message 42 CreateWarning <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=259> Checks subscriptions beliefs to see which users are registered to receive alerts from this airport 259 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=266> The warning is displayed to the user 266 start Warnings actor A User actor B Airport Sensor actor C Forecaster agent D GUIAgent agent E AirportAgent agent F ForecasterAgent action E B subscribeAWSSourceAgent action F C subscribeTAFSourceAgent percept A D Subscription from User message D E SubscriptionE box loop box loop box opt action E B Request Data end opt percept B E AWS DataE percept C F TAF dataE message F E ForecastE end loop box opt message E D WarningE action D A Show Warning end opt end loop Send to airports Receive all data from the forecaster and send relevant data to each airport 198 Send to airports Always true; N/A N/A Receive data Split data into individual airports Send to each airport CreateForecast Role which covers the splitting of incoming TAF data and sending to appropriate airports 197 CreateForecast start Data retrieval actor A Airport Sensor agent B AirportAgent actor C Forecaster agent D ForecasterAgent action B A subscribeAWSSourceAgent action D C subscribeTAFSourceAgent box loop box opt action B A AWSRequest end opt percept A B AWS DataE percept C D TAF dataE message D B ForecastE end loop finish Obtain Data Scenario scenario <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=243> Everything required to obtain AWS data from the Airport Sensors 243 Obtain AWS data Scenario scenario This scenario covers the necessary processes to obtain AWS data. This includes subscribing to the AWS, receiving the data and storing it. 241 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=253> Subscribe to the Airport sensor as a listener of data readings 253 Obtain AWS data Role which covers the obtaining of AWS data and updating of necessary beliefs 37 Obtain AWS data Request AWS Data [OPTIONAL] Send a request for AWS readings 14 Request AWS Data <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=254> Message containing the current data readings at sensor 254 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=255> Data is received and relevant data extracted 255 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=256> AWS beliefs are updated with new information 256 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=246> Everything required to obtain TAF data from the Forecaster 246 Obtain TAF data Scenario scenario This scenario covers the necessary processes to obtain forecasts. This includes the system subscribing to the forecaster, the data arriving for all airports and also covers the splitting of this information and sending to the appropriate airports. 244 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=247> A message is sent to the Forecaster, registering an agent as a listener to forecasting information 247 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=249> Incoming forecasts for all airports for the next 12 hours. 249 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=250> Forecasts are split into a forecast for each airport and sent to the relevant agents 250 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=251> Recieve the incoming Forecast and extract relevant data 251 Recieve TAF data Recieve the TAF data from forecaster 17 Recieve TAF data Obtain TAF data Role which covers obtaining TAF data for an individual airport and updating appropriate beliefs 38 Obtain TAF data Update TAF Beliefs Update forecast beliefsets with up to date forecasts 18 Update TAF Beliefs <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=252> Update the Forecasts beliefs with new information. 252 Obtain Data Scenario Obtain Data from relevant sources and store appropriately 5 Obtain Data Scenario Obtain TAF data Scenario Obtain and update beliefs for the TAF data 13 Obtain TAF Obtain AWS data Scenario Obtain AWS data from the sensors and store appropriately 242 AWS DataE Rainfall, wind speed, temperature and fog AWS data stores Quarter hourly or more frequently if requested Airport Sensor 218 Request Data None. This is because only one agent can be subscribed to a sensor so the data request can only originate from one location. N/A N/A N/A Should result in incoming data from the AWS sensor RequestAWSP Sends a request to the Simulator for the most up to date AWS readings 75 RequestAWSP planMessagePair-204 204 planMessagePair-204 AWSNeededE Posted when AWS readings are required. Not currently used. 202 AWSNeededE capabilityDiagramPair-203 203 capabilityDiagramPair-203 To indicate that up-to-date AWS readings are required from the sensor Always true N/A N/A Send Message to AWS sensor requesting up to date data <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=61> 61 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=61> Always True; N/A N/A Process data and write to datastore ReportHighRainChangeP Creates a immediate change in forecast warning 123 ReportHighRainChangeP planMessagePair-186 186 planMessagePair-186 planMessagePair-214 214 planMessagePair-214 If there is a change in the forecast for high rain where high rain is considered about 10cm N/A N/A Post NewWarningE event with relevant data If there is a change in the forecast for temperatures below zero N/A N/A Post NewWarningE event with relevant data planMessagePair-211 211 planMessagePair-211 If there is a change in the forecast for fog N/A N/A Post NewWarningE event with relevant data planMessagePair-104 104 planMessagePair-104 103 If the presence of high wind (>20 knots) has changed N/A N/A Post NewWarningE event with relevant data Always true. N/A N/A Read warning information from NewWarningE Get subscriptions from DB where airport matches warning for each subscription send WarningE If there is a discrepancy of 5 knots or more between the forecast wind and the actual reading N/A N/A Post NewWarningE event with relevant data planMessagePair-126 126 planMessagePair-126 125 planMessagePair-191 191 planMessagePair-191 190 CalculateTrendP If there is a discrepancy between the forecast for fog and the actual reading N/A N/A Post NewWarningE event with relevant data If wind is greater than 30 knots N/A N/A Post NewWarningE event with relevant data <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=69> 69 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=69> <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=71> 71 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=71> <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=73> 73 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.DataConnection ID=73> 416 388 336 174 211 346 220 64 137 271 291 272 12 174 172 173 au.edu.rmit.cs.prometheus.gui.diagram.capabilityoverview.CapabilityOverviewDiagramModel#56 265 337 390 315 270 29 272 249 168 176 487 174 9 177 302 174 au.edu.rmit.cs.prometheus.gui.diagram.capabilityoverview.CapabilityOverviewDiagramModel#55 267 359 385 368 423 161 224 283 188 161 273 40 332 284 38 162 au.edu.rmit.cs.prometheus.gui.diagram.agentoverview.AgentOverviewDiagramModel(id#48) 180 239 102 52 29 244 24 431 228 GUISubscribeClickedE Indicates the the User GUI has attempted to subscribe to an airport 199 GUISubscribeClickedE The name of the airport to subscribe to :true 220 237 228 185 28 104 System Overview 154 24 59 230 405 121 33 99 192 92 420 151 365 9 402 56 275 248 263 386 401 203 259 155 277 93 326 210 242 278 335 375 244 Goal Overview 137 13 518 12 232 87 267 57 7 100 43 135 126 228 280 120 135 109 331 177 357 94 342 275 105 275 456 137 314 359 552 271 447 355 437 396 601 357 1 322 90 175 674 396 163 364 44 363 5 228 565 136 234 322 687 136 59 64 au.edu.rmit.cs.prometheus.gui.diagram.capabilityoverview.CapabilityOverviewDiagramModel#53 159 128 171 332 283 126 299 232 313 327 159 231 au.edu.rmit.cs.prometheus.gui.diagram.agentoverview.AgentOverviewDiagramModel(id#171) 47 161 160 88 23 16 21 93 System Roles 184 14 130 111 510 56 428 21 158 279 392 79 222 88 20 102 29 188 270 365 305 298 20 31 413 290 459 353 24 278 597 163 384 251 604 82 128 403 10 404 308 122 33 324 139 158 451 402 311 219 614 241 503 189 40 233 61 367 158 187 109 62 511 244 159 231 326 158 559 122 227 51 Analysis Overview 48 37 193 368 479 373 314 301 217 198 189 296 540 299 424 297 208 97 234 41 10 301 93 24 163 au.edu.rmit.cs.prometheus.gui.diagram.agentoverview.AgentOverviewDiagramModel(id#47) 385 291 170 61 309 10 293 318 44 11 432 5 188 315 383 174 196 173 415 312 424 130 507 273 291 64 316 377 8 244 43 64 524 216 277 355 276 113 48 113 135 244 317 245 Data Coupling 286 361 206 187 86 356 187 26 38 23 187 134 346 189 20 190 137 260 301 261 36 134 177 74 43 72 Scenarios 126 45 125 252 14 103 133 175 230 102 Agent-Role Coupling 89 45 238 220 237 261 210 180 239 41 247 387 206 136 245 301 253 343 74 269 145 381 191 100 78 131 Agent Acquaintance 28 114 251 43 50 44 :false <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=248> 248 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=257> New beliefs are registered 257 <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.Step ID=261> Displays the warning to the user 261 Notes for AgentOverviewDiagram: Unattached action. Not sure where to attach agentDiagramPair-219 planMessagePair-223 capabilityDiagramPair-226 EventA PlanB agentDiagramPair-222 planMessagePair-224 EventC Cap new <Prometheus unique entity name au.edu.rmit.cs.prometheus.datamodel.jacob.ProtocolDistributionPair ID=219> planMessagePair-194 planMessagePair-195 capabilityDiagramPair-193 Airport Agent subscribeTAFSourceAgent Split forecasts Check Alertable types subscribeTAFSSourceAgent Obtain TAF data Scenario Obtain AWS Determine if relevant message1 TrendDiscrepancyE CalculateTrendP Check trends planMessagePair-201 agentDiagramPair-200 User Subscribes planMessagePair-84 capabilityDiagramPair-83 AWSRequest