The scenario
A university deploys a chatbot for course registration, enabling students to check availability, register, drop, view schedule, and handle waitlists, with integration to student info system and course database.
What is in this drawing
Read the decisions behind it.
01
Converted external system «include» errors to regular actor-use case associations (CheckAvail -- CourseDB, AskPrereq -- CourseDB).
02
Retained use-case-to-use-case includes (e.g., Register ..> Authenticate) and extend for waitlist.
03
Business actor 'Faculty Advisor' linked via association for notification.
When modeling an AI-powered academic chatbot, especially to clarify actor boundaries and functional decomposition.
More like this