![]() I almost made a comment on that in my first post, but didn't want to make things complex straight away. That's one of the things I am struggling with. The resulting diagram is so big that Plant UML cannot handle it as one big designs it is absolutely critical to only show the classes and relationships you are actually interested in. Write_Desired_Temperature_Msg -> Message_Enqueuer Write_Desired_Temperature_Msg -|> Message Write_Cooler_Enqueuer_Msg -> Message_Enqueuer Write_Cooler_Enqueuer_Msg -> Cooler_Controller Write_Cooler_Enqueuer_Msg -* Message_Enqueuer Write_Controller_Enqueuer_Msg -> Message_Enqueuer Write_Controller_Enqueuer_Msg -* Message_Enqueuer Write_Controller_Enqueuer_Msg -|> Message Update_Water_Level_Msg -> Message_Enqueuer Update_Water_Level_Msg -> Evaporative_Cooler_Controller Update_Pump_State_Msg -> Message_Enqueuer Update_Pump_State_Msg -> Evaporative_Cooler_Controller Update_Fan_Status_Msg -> Message_Enqueuer Update_Fan_Status_Msg -> Evaporative_Cooler_Controller Update_Current_Temperature_Msg -> Message_Enqueuer Update_Current_Temperature_Msg -> Cooler_Controller Update_Current_Temperature_Msg -|> Message Swap_Controllers_Msg -> Cooler_Controller Swap_Controllers_Msg -> Air_Cooler_Application Swap_Controllers_Msg -* Cooler_Controller Simulated_Evaporative_Cooler -> Water_Level Simulated_Evaporative_Cooler -> Simulated_Water_Level Simulated_Evaporative_Cooler -> Simulated_Dual_Fan Simulated_Evaporative_Cooler -|> Evaporative_Cooler Protected_Actor_Handle -> Message_Enqueuer Protected_Actor_Handle -* Message_Enqueuer Programmatic_Controller -|> Cooler_Controller Message_Enqueuer -> Message_Priority_Queue Message_Enqueuer -* Message_Priority_Queue Message_Dequeuer -> Message_Priority_Queue Message_Dequeuer -* Message_Priority_Queue Load_Into_Sub_Panel_Msg -> Message_Enqueuer ![]() Load_Into_Sub_Panel_Msg -> Air_Cooler_Application ![]() HW_Evaporative_Cooler -|> Evaporative_Cooler By default everything is shown but this results in the following.Īir_Cooler_Application -* Message_EnqueuerĪir_Cooler_Application -> Cooler_ControllerĪir_Cooler_Application -> Live_User_ControllerĪir_Cooler_Application -> Message_EnqueuerĪir_Cooler_Application -> Programmatic_ControllerĬhange_Desired_Temperature_Msg -|> MessageĬhange_Desired_Temperature_Msg -> Cooler_ControllerĬhange_Desired_Temperature_Msg -> Message_EnqueuerĬooler_Update_Fan_Status_Msg -|> Update_Fan_Status_MsgĬooler_Update_Fan_Status_Msg -> Evaporative_CoolerĬooler_Update_Water_Level_Msg -|> Update_Water_Level_MsgĬooler_Update_Water_Level_Msg -> Evaporative_CoolerĮvaporative_Cooler_Controller -|> Cooler_ControllerĮvaporative_Cooler -> Cooler_Update_Fan_Status_MsgĮvaporative_Cooler -> Cooler_Update_Water_Level_Msg Sorry it has to be LV19 because I use sets and maps inside.įor big designs it is absolutely critical to only show the classes and relationships you are actually interested in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |