sequenceDiagram actor User participant App as Mobile App participant Server as Auth…
- User
sequenceDiagram actor User participant App as Mobile App participant Server as Auth Server participant Google as Google OAuth
%% Basic Flow User->>App: Enter Email & Password User->>App: Tap Sign In App->>App: Validate Input Fields alt Valid Input App->>Server: Send Auth Request Server->>Server: Verify Credentials Server->>App: Return Auth Token App->>App: Store Token Securely App->>User: Show Dashboard else Invalid Input App->>User: Show Error Message end %% Alternative Flow (Google) rect rgb(240, 240, 240) Note over User,Google: Alternative Flow - Google Sign In User->>App: Select "Sign up with Google" App->>Google: Initialize OAuth Flow Google->>User: Show Google Login User->>Google: Authenticate Google->>App: Return OAuth Token App->>Server: Verify Google Token Server->>App: Return App Auth Token App->>App: Store Token Securely App->>User: Show Dashboard endthis is the sample of sequence diagram, so based on the use case i have given to you, make for me the script of the sequence diagram UC-01: Manage Lesson Plans Use Case UC-01 Use case name Manage Lesson Plans Description Create and manage lesson plans for AI Virtual Teacher Actor(s) Admin Priority Must have Pre-condition(s) • Admin is logged in • Standard lesson template exists Basic Flow Step Action 1 Selects "Create new lesson plan" 2 Shows lesson plan form 3 Enters lesson info (level, topic, goals, etc.) 4 Checks content 5 Saves lesson plan Alternative Flow 4a (If invalid) Shows error message 4a (If invalid) Edits info Post-Condition(s) Lesson plan is created and ready for use
Assistant
Okay, here is the sequence diagram script for Use Case UC-01: Manage Lesson Plans, following the format and style of your example.
sequenceDiagram actor Admin participant App as AI Teacher App participant Server as App Server Note over Admin,Server: Pre-condition: Admin is logged in Note over Admin,Server: Pre-condition: Standard lesson template exists %% Basic Flow Admin->>App: Select "Create new lesson plan" (Step 1) App->>Admin: Show lesson plan form (Step 2) Admin->>App: Enter lesson details (level, topic, goals, etc.) (Step 3) App->>Server: Send lesson data for validation and save alt Content is Valid Server->>Server: Validate Content Server->>Server: Save Lesson Plan (Step 5) Server->>App: Return Success Confirmation App->>Admin: Show "Lesson plan created successfully" else Content is Invalid (Alternative Flow 4a) Server->>Server: Validate Content Server->>App: Return Validation Errors App->>Admin: Show Error Message (Step 4a part 1) Admin->>App: Edit lesson details (Step 4a part 2 - Assumes Admin corrects input) Note over Admin,App: Admin re-enters details, flow may repeat from App->Server end Note over Admin,Server: Post-condition: Lesson plan is created and ready for useExplanation of the Script:
sequenceDiagram: Starts the diagram definition.actor Admin: Defines the Admin as the actor.participant App as AI Teacher App: Defines the Mobile App participant, renaming it to "AI Teacher App" for clarity related to the use case.participant Server as App Server: Defines the Server participant, renaming it to "App Server" as it handles the application logic/data.Note over Admin,Server: ...: Adds notes spanning multiple participants, used here for preconditions and post-conditions as listed in the use case.Admin->>App: ...: Represents a synchronous message (Admin performs an action on the App). Corresponds to steps 1, 3, and 4a (part 2).App->>Admin: ...: Represents a synchronous message (App displays something to the Admin). Corresponds to steps 2 and 4a (part 1) in the invalid path, and the success message in the valid path.App->>Server: ...: Represents the App sending the data to the Server for processing (validation and saving).alt ... else ... end: Defines an alternative flow based on a condition ("Content is Valid" vs. "Content is Invalid"). This maps steps 4 and 4a.Server->>Server: ...: Represents an action the Server performs internally (validation, saving).Server->>App: ...: Represents the Server sending a response back to the App (confirmation or errors).
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.