diff --git a/docs/DeveloperGuide.md b/docs/DeveloperGuide.md index 2420261cbcc..d04576e1981 100644 --- a/docs/DeveloperGuide.md +++ b/docs/DeveloperGuide.md @@ -217,6 +217,9 @@ Finally `AddImageCommand#execute` updates the model provided in the arguments. The following sequence diagram shows how the add-image operation works:
![AddImageSequenceDiagram](images/AddImageSequenceDiagram.png) +> **Note**: The lifeline of the `AddImageCommandParser` and `AddImageCommand` +> should end at the destroy marker (X) but due to the limitations of PlantUML, the +> lifeline reaches the end of the diagram. The following activity diagram summarizes what happens when a user executes add-image command:
![AddImageActivityDiagram](images/AddImageActivityDiagram.png) diff --git a/docs/diagrams/AddImageSequenceDiagram.puml b/docs/diagrams/AddImageSequenceDiagram.puml index ba68b6961d0..00e312d55cc 100644 --- a/docs/diagrams/AddImageSequenceDiagram.puml +++ b/docs/diagrams/AddImageSequenceDiagram.puml @@ -6,7 +6,7 @@ participant ":LogicManager" as LogicManager LOGIC_COLOR participant ":AddressBookParser" as AddressBookParser LOGIC_COLOR participant ":AddImageCommandParser" as AddImageCommandParser LOGIC_COLOR participant "command:AddImageCommand" as AddImageCommand LOGIC_COLOR -participant "ImageUtil<< class >>" as ImageUtil LOGIC_COLOR +participant "ImageUtil" as ImageUtil <> LOGIC_COLOR end box box Model MODEL_COLOR_T1 diff --git a/docs/images/AddImageSequenceDiagram.png b/docs/images/AddImageSequenceDiagram.png index 375eba1ded2..acfa4512fac 100644 Binary files a/docs/images/AddImageSequenceDiagram.png and b/docs/images/AddImageSequenceDiagram.png differ