AY2324S1-CS2103T-W12-4 · teozhengyang · Nov 10, 2023 · Nov 10, 2023 · Nov 10, 2023
diff --git a/docs/DeveloperGuide.md b/docs/DeveloperGuide.md
@@ -103,17 +103,17 @@ Here's a (partial) class diagram of the `Logic` component:
 
 <img src="images/LogicClassDiagram.png" width="550"/>
 
-The sequence diagram below illustrates the interactions within the `Logic` component, taking `execute("delete 1")` API call as an example.
+The sequence diagram below illustrates the interactions within the `Logic` component, taking `execute("addschedule user type/cca en/table tennis h/monday 1400 1600")` API call as an example.
 
-![Interactions Inside the Logic Component for the `delete 1` Command](images/DeleteSequenceDiagram.png)
+![Interactions Inside the Logic Component for the `delete 1` Command](images/AddScheduleSequenceDiagram.png)
 
-<div markdown="span" class="alert alert-info">:information_source: **Note:** The lifeline for `DeleteCommandParser` should end at the destroy marker (X) but due to a limitation of PlantUML, the lifeline reaches the end of diagram.
+<div markdown="span" class="alert alert-info">:information_source: **Note:** The lifeline for `AddScheduleCommandParser` should end at the destroy marker (X) but due to a limitation of PlantUML, the lifeline reaches the end of diagram.
 </div>
 
 How the `Logic` component works:
 
-1. When `Logic` is called upon to execute a command, it is passed to an `AddressBookParser` object which in turn creates a parser that matches the command (e.g., `DeleteCommandParser`) and uses it to parse the command.
-1. This results in a `Command` object (more precisely, an object of one of its subclasses e.g., `DeleteCommand`) which is executed by the `LogicManager`.
+1. When `Logic` is called upon to execute a command, it is passed to an `AddressBookParser` object which in turn creates a parser that matches the command (e.g., `AddScheduleCommandParser`) and uses it to parse the command.
+1. This results in a `Command` object (more precisely, an object of one of its subclasses e.g., `AddScheduleCommand`) which is executed by the `LogicManager`.
 1. The command can communicate with the `Model` when it is executed (e.g. to delete a person).
 1. The result of the command execution is encapsulated as a `CommandResult` object which is returned back from `Logic`.
 

diff --git a/docs/diagrams/AddScheduleSequenceDiagram.puml b/docs/diagrams/AddScheduleSequenceDiagram.puml
@@ -0,0 +1,70 @@
+@startuml
+!include style.puml
+skinparam ArrowFontStyle plain
+
+box Logic LOGIC_COLOR_T1
+participant ":LogicManager" as LogicManager LOGIC_COLOR
+participant ":AddressBookParser" as AddressBookParser LOGIC_COLOR
+participant ":AddScheduleCommandParser" as AddScheduleCommandParser LOGIC_COLOR
+participant "d:AddScheduleCommand" as AddScheduleCommand LOGIC_COLOR
+participant ":CommandResult" as CommandResult LOGIC_COLOR
+end box
+
+box Model MODEL_COLOR_T1
+participant ":Model" as Model MODEL_COLOR
+end box
+
+[-> LogicManager : execute("addschedule user type/cca en/table tennis h/monday 1400 1600")
+activate LogicManager
+
+LogicManager -> AddressBookParser : parseCommand("addschedule user type/cca en/table tennis h/monday 1400 1600")
+activate AddressBookParser
+
+create AddScheduleCommandParser
+AddressBookParser -> AddScheduleCommandParser
+activate AddScheduleCommandParser
+
+AddScheduleCommandParser --> AddressBookParser
+deactivate AddScheduleCommandParser
+
+AddressBookParser -> AddScheduleCommandParser : parse("user type/cca en/table tennis h/monday 1400 1600")
+activate AddScheduleCommandParser
+
+create AddScheduleCommand
+AddScheduleCommandParser -> AddScheduleCommand
+activate AddScheduleCommand
+
+AddScheduleCommand --> AddScheduleCommandParser : addCca
+deactivate AddScheduleCommand
+
+AddScheduleCommandParser --> AddressBookParser : addCca
+deactivate AddScheduleCommandParser
+'Hidden arrow to position the destroy marker below the end of the activation bar.
+AddScheduleCommandParser -[hidden]-> AddressBookParser
+destroy AddScheduleCommandParser
+
+AddressBookParser --> LogicManager : d
+deactivate AddressBookParser
+
+LogicManager -> AddScheduleCommand : execute()
+activate AddScheduleCommand
+
+AddScheduleCommand -> Model : addCca(table tennis monday 1400 1600)
+activate Model
+
+Model --> AddScheduleCommand
+deactivate Model
+
+create CommandResult
+AddScheduleCommand -> CommandResult
+activate CommandResult
+
+CommandResult --> AddScheduleCommand
+deactivate CommandResult
+
+AddScheduleCommand --> LogicManager : result
+deactivate AddScheduleCommand
+
+[<--LogicManager
+deactivate LogicManager
+@enduml
diff --git a/docs/images/AddScheduleSequenceDiagram.png b/docs/images/AddScheduleSequenceDiagram.png
diff --git a/docs/team/lululwtv.md b/docs/team/lululwtv.md
@@ -20,11 +20,14 @@ https://nus-cs2103-ay2324s1.github.io/tp-dashboard/?search=w12-4&sort=groupTitle
 - Added guides for commands `cft`, `rmevent`, `addevent`, `addschedule`, `rmschedule` commands
 - Fixed UG documentation to align with newer commands
 - Updated UG to include expected features that may not be expected by users, such as:
-    - 
+    - Informing users in the UG that event names will be changed to all caps even if they did not key it in caps
+    - Add sample code for the commands I have added
 
 **Contributions to the Developer Guide (DG):**
 
-[to be added later]
+- Update DG on how addschedule command works
+    - Created sequence diagram for addschedule command
+- Updated how Logic package works
 
 **Contributions to team-based tasks:**