SRS / Use Case Specifications
This page is the English extended SRS reference for the Vietnamese TaskPilot report appendix. It preserves the 59 use cases used by the report and links each use case to existing sequence diagrams, activity diagrams, UI specification pages, and database tables where those artefacts exist.
System overview
TaskPilot is an intelligent project and task management system with AI Copilot support. The core scope covers project/member/sprint/task management, Kanban collaboration, realtime notification, AI Copilot with controlled tool calling, and assignment recommendation based on weighted heuristic scoring.
Actors
| Actor | Description |
|---|---|
| Guest | Unauthenticated user who can register, sign in, or recover/reset a password. |
| System Administrator (ad) | Manages users, system skill directory, AI/system settings and audit views. |
| Project Manager (pm) | Creates and manages projects, members, sprints, tasks and assignment decisions. |
| Project Member (mem) | Works on tasks, comments, notifications, sprint/backlog views and AI Copilot within granted project permissions. |
| AI Copilot | Internal assistant component that proposes answers/actions through controlled tool calling; it is not a direct human actor. |
Use case group count verification
| # | Group | Range | Count |
|---|---|---|---|
| 1 | Authentication | UC01–UC04 | 4 |
| 2 | User Profile | UC05–UC07 | 3 |
| 3 | User Skills | UC08–UC12 | 5 |
| 4 | System Administration | UC13–UC21 | 9 |
| 5 | Project Management | UC22–UC28 | 7 |
| 6 | Project Members | UC29–UC33 | 5 |
| 7 | Sprint Management | UC34–UC39 | 6 |
| 8 | Task Management | UC40–UC48 | 9 |
| 9 | Interaction & Communication | UC49–UC52 | 4 |
| 10 | Notification Management | UC53–UC54 | 2 |
| 11 | AI Assistant | UC55–UC59 | 5 |
Total: 59 use cases across 11 groups.
Use case catalogue
| ID | Name | Actor(s) | Subsystem | UI | Sequence | Activity | Database table(s) |
|---|---|---|---|---|---|---|---|
| UC01 | Sign In | ad, pm, mem | Authentication | Login screen | sequence diagram | activity diagram | users |
| UC02 | Register / Sign Up | ad, pm, mem | Authentication | Register screen | sequence diagram | activity diagram | users |
| UC03 | Forgot Password | ad, pm, mem | Authentication | Forgot password screen | sequence diagram | activity diagram | users, password_reset_tokens |
| UC04 | Reset Password | ad, pm, mem | Authentication | Forgot password screen | sequence diagram | activity diagram | users, password_reset_tokens |
| UC05 | Update Personal Information | ad, pm, mem | User Profile | Profile screen | sequence diagram | activity diagram | users |
| UC06 | View User Profile | ad, pm, mem | User Profile | Profile screen | sequence diagram | activity diagram | users |
| UC07 | Delete Personal Account | ad, pm, mem | User Profile | Profile screen | sequence diagram | activity diagram | users |
| UC08 | View Personal Skill List | pm, mem | User Skills | Profile screen | sequence diagram | activity diagram | user_skills, skills |
| UC09 | View Personal Skill Details | pm, mem | User Skills | Profile screen | sequence diagram | activity diagram | user_skills, skills |
| UC10 | Add Personal Skill | pm, mem | User Skills | Profile screen | sequence diagram | activity diagram | user_skills, skills |
| UC11 | Update Personal Skill | pm, mem | User Skills | Profile screen | sequence diagram | activity diagram | user_skills, skills |
| UC12 | Delete Personal Skill | pm, mem | User Skills | Profile screen | sequence diagram | activity diagram | user_skills, skills |
| UC13 | Configure System Parameters | ad | System Administration | Admin system configuration | sequence diagram | activity diagram | system_settings |
| UC14 | View System Skill Directory | ad | System Administration | Admin skill directory | sequence diagram | activity diagram | skills |
| UC15 | Add System Skill | ad | System Administration | Admin skill directory | sequence diagram | activity diagram | skills |
| UC16 | Edit System Skill | ad | System Administration | Admin skill directory | sequence diagram | activity diagram | skills |
| UC17 | Delete System Skill | ad | System Administration | Admin skill directory | sequence diagram | activity diagram | skills |
| UC18 | View Global User List | ad | System Administration | Admin user management | sequence diagram | activity diagram | users |
| UC19 | Add System User | ad | System Administration | Admin user management | sequence diagram | activity diagram | users |
| UC20 | Edit System User | ad | System Administration | Admin user management | sequence diagram | activity diagram | users |
| UC21 | Delete System User | ad | System Administration | Admin user management | sequence diagram | activity diagram | users |
| UC22 | View Joined Projects | pm, mem | Project Management | Project dashboard / project list | sequence diagram | activity diagram | projects, project_members |
| UC23 | Create New Project | pm | Project Management | Create project screen | sequence diagram | activity diagram | projects, project_members |
| UC24 | View Project Details / Summary | pm, mem | Project Management | Project workspace Project overview Timeline | sequence diagram | activity diagram | projects |
| UC25 | Update Project Information | pm | Project Management | Project settings general | sequence diagram | activity diagram | projects |
| UC26 | Join Project | pm, mem | Project Management | Project dashboard / project list | sequence diagram | activity diagram | project_members |
| UC27 | Leave Project | pm, mem | Project Management | Project workspace | sequence diagram | activity diagram | project_members |
| UC28 | Close / Archive Project | pm | Project Management | Project settings general | sequence diagram | activity diagram | projects |
| UC29 | View Project Member List | pm, mem | Project Members | Project settings members | sequence diagram | activity diagram | project_members, users |
| UC30 | View Member Details | pm, mem | Project Members | Project settings members | sequence diagram | activity diagram | project_members, users, user_skills |
| UC31 | Add Member to Project | pm, mem | Project Members | Project settings members | sequence diagram | activity diagram | project_members |
| UC32 | Update Member Role | pm | Project Members | Project settings members | sequence diagram | activity diagram | project_members |
| UC33 | Remove Member from Project | pm, mem | Project Members | Project settings members | sequence diagram | activity diagram | project_members |
| UC34 | View Sprint List | pm, mem | Sprint Management | Sprint backlog | sequence diagram | activity diagram | sprints |
| UC35 | View Sprint Details | pm, mem | Sprint Management | Sprint backlog | sequence diagram | activity diagram | sprints |
| UC36 | Create New Sprint | pm, mem | Sprint Management | Sprint backlog | sequence diagram | activity diagram | sprints |
| UC37 | Update Sprint Information | pm, mem | Sprint Management | Sprint backlog | sequence diagram | activity diagram | sprints |
| UC38 | Start / Complete Sprint | pm, mem | Sprint Management | Sprint backlog | sequence diagram | activity diagram | sprints |
| UC39 | Delete Sprint | pm, mem | Sprint Management | Sprint backlog | sequence diagram | activity diagram | sprints, tasks |
| UC40 | View Kanban Board | pm, mem | Task Management | Kanban board | sequence diagram | activity diagram | tasks |
| UC41 | View Backlog | pm, mem | Task Management | Sprint backlog | sequence diagram | activity diagram | tasks, sprints |
| UC42 | View Workload | pm, mem | Task Management | Project settings members Task detail | sequence diagram | activity diagram | tasks, users |
| UC43 | View Task Details | pm, mem | Task Management | Task detail | sequence diagram | activity diagram | tasks, task_required_skills, task_labels |
| UC44 | Create Task or Sub-task | pm, mem | Task Management | Kanban board Task detail | sequence diagram | activity diagram | tasks, task_required_skills, task_labels |
| UC45 | Update Task Information | pm, mem | Task Management | Task detail | sequence diagram | activity diagram | tasks, task_required_skills, task_labels |
| UC46 | Update Task Status / Drag and Drop on Kanban | pm, mem | Task Management | Kanban board | sequence diagram | activity diagram | tasks |
| UC47 | Assign Assignee and Reporter | pm, mem | Task Management | Task detail | sequence diagram | activity diagram | tasks, users, user_skills, project_members |
| UC48 | Delete Task | pm, mem | Task Management | Kanban board Task detail | sequence diagram | activity diagram | tasks |
| UC49 | View Comments | pm, mem | Interaction & Communication | Comment | sequence diagram | activity diagram | comments |
| UC50 | Write Comment | pm, mem | Interaction & Communication | Comment | sequence diagram | activity diagram | comments, comment_mentions, notifications |
| UC51 | Edit Comment | pm, mem | Interaction & Communication | Comment | sequence diagram | activity diagram | comments, comment_mentions |
| UC52 | Delete Comment | pm, mem | Interaction & Communication | Comment | sequence diagram | activity diagram | comments |
| UC53 | Receive Notification | ad, pm, mem | Notification Management | Notification panel | sequence diagram | activity diagram | notifications |
| UC54 | Mark Notification as Read | ad, pm, mem | Notification Management | Notification panel | sequence diagram | activity diagram | notifications |
| UC55 | Create New AI Chat Session | pm, mem | AI Assistant | AI chat | sequence diagram | activity diagram | chat_sessions |
| UC56 | Chat with AI | pm, mem | AI Assistant | AI chat Pending action confirmation | sequence diagram | activity diagram | chat_sessions, chat_messages, ai_logs |
| UC57 | View AI Chat History | pm, mem | AI Assistant | AI chat | sequence diagram | activity diagram | chat_sessions, chat_messages |
| UC58 | View AI Activity Logs | ad, pm, mem | AI Assistant | AI chat | sequence diagram | activity diagram | ai_logs |
| UC59 | Request AI Task Assignment Recommendation | pm | AI Assistant | AI assignment recommendation Pending action confirmation | sequence diagram | activity diagram | tasks, users, user_skills, project_members, system_settings, ai_logs |
Representative use cases
The following six use cases are completed from the current report and existing PlantUML sequence/activity diagrams: UC01, UC23, UC44, UC46, UC47 and UC59.
UC01 — Sign In
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC01 |
| Name | Sign In |
| Actor(s) | ad, pm, mem |
| Priority | High |
| Trigger | Access login page |
| Pre-condition(s) | An active account exists and the authentication service is operational. |
| Post-condition(s) | Generate JWT token Redirect to home page |
| Basic Flow | 1. Access login page 2. Display login form 3. Enter username/email and password 4. Click "Sign In" 5. Validate data format 6. Query user by username or email 7. Verify password hash 8. Check account lock status 9. Generate JWT token 10. Redirect to home page |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display format error 2. Display "Invalid credentials" error 3. Display "Account locked. Please contact support" error |
| Related UI screen(s) | Login screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC23 — Create New Project
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC23 |
| Name | Create New Project |
| Actor(s) | pm |
| Priority | High |
| Trigger | Access Projects page |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Generate default invite code for project Notify success and redirect to new project page |
| Basic Flow | 1. Access Projects page 2. Display project list with "Create Project" button 3. Click "Create Project" 4. Display form (name, description, start/end date, heuristic_mode) 5. Enter project information 6. Click "Create" 7. Validate name not empty and start date before end date 8. Insert project (status=ACTIVE) 9. Initialize empty sprint backlog 10. Add creator as MANAGER in project_members 11. Generate default invite code for project 12. Notify success and redirect to new project page |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. |
| Exception Flow | 1. Display validation error |
| Related UI screen(s) | Create project screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | projects, project_members |
UC44 — Create Task or Sub-task
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC44 |
| Name | Create Task or Sub-task |
| Actor(s) | pm, mem |
| Priority | High |
| Trigger | Access project task board or backlog |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Send notification to assignee if assigned Notify success and display task in Kanban/Backlog |
| Basic Flow | 1. Access project task board or backlog 2. Display task list with "Create Task" button 3. Click "Create Task" 4. Display form (title, description, status, priority, assignee, sprint, required_skills, parent_task for sub-task) 5. Enter task information 6. Click "Create" 7. Validate title not empty 8. Insert task record 9. Set initial task history entry 10. If assignee selected: update assignee's current_workload (+1) 11. Send notification to assignee if assigned 12. Notify success and display task in Kanban/Backlog |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. |
| Exception Flow | 1. Display validation error |
| Related UI screen(s) | Kanban board Task detail |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, task_required_skills, task_labels |
UC46 — Update Task Status / Drag and Drop on Kanban
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC46 |
| Name | Update Task Status / Drag and Drop on Kanban |
| Actor(s) | pm, mem |
| Priority | High |
| Trigger | Drag task card to new column or click status button |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display updated kanban card in new column View updated board |
| Basic Flow | 1. Drag task card to new column or click status button 2. Query current task status 3. Verify new status is a valid transition (e.g. TODO → IN_PROGRESS → REVIEW → DONE) 4. Update task status (TODO / IN_PROGRESS / REVIEW / DONE) and position in column 5. Display updated kanban card in new column 6. View updated board |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. 2. Status can be updated either by drag and drop on Kanban or from task detail controls. |
| Exception Flow | 1. Display "Invalid status transition" error 2. Decrement assignee's current_workload 3. Re-increment assignee's current_workload |
| Related UI screen(s) | Kanban board |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks |
UC47 — Assign Assignee and Reporter
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC47 |
| Name | Assign Assignee and Reporter |
| Actor(s) | pm, mem |
| Priority | High |
| Trigger | Click "Assign" on a task |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update assignee's current_workload (+1 if assigning, -1 if unassigning) Notify success |
| Basic Flow | 1. Click "Assign" on a task 2. Query project members list (join users, user_skills) 3. Display assignment form (assignee dropdown showing workload, reporter dropdown) 4. Select assignee and/or reporter 5. Check if selected assignee is overloaded (current_workload > threshold) 6. Display warning "This member is overloaded (workload: N)" 7. Click "Save" 8. Update task assignee_id and reporter_id 9. Update assignee's current_workload (+1 if assigning, -1 if unassigning) 10. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. 2. The user may update only assignee, only reporter, or both fields. |
| Exception Flow | 1. Check if selected assignee is overloaded (current_workload > threshold) 2. Display warning "This member is overloaded (workload: N)" |
| Related UI screen(s) | Task detail |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, users, user_skills, project_members |
UC59 — Request AI Task Assignment Recommendation
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC59 |
| Name | Request AI Task Assignment Recommendation |
| Actor(s) | pm |
| Priority | High |
| Trigger | Click "AI Auto-Assign" on a project |
| Pre-condition(s) | User is authenticated and has an available AI chat/session or project context as required by the action. |
| Post-condition(s) | Apply accepted assignments Notify members of assignments |
| Basic Flow | 1. Click "AI Auto-Assign" on a project 2. Verify user has MANAGER role 3. Query member skills and workloads 4. Send to AI API for assignment suggestions 5. Display suggested assignments 6. Review suggestion 7. Click "Confirm" or "Reject" 8. Record user decision 9. Apply accepted assignments 10. Notify members of assignments |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. 3. The Project Manager may reject the recommendation, leaving task assignment unchanged. |
| Exception Flow | 1. Display "Access denied" error |
| Related UI screen(s) | AI assignment recommendation Pending action confirmation |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, users, user_skills, project_members, system_settings, ai_logs |
Full use case specifications
The remaining use cases retain the required SRS fields. Textual flows are derived from the existing PlantUML activity diagrams where those diagrams exist, so the SRS stays traceable to the current diagram source.
UC02 — Register / Sign Up
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC02 |
| Name | Register / Sign Up |
| Actor(s) | ad, pm, mem |
| Priority | Medium |
| Trigger | Access sign up page |
| Pre-condition(s) | User is not required to be authenticated and the authentication service is operational. |
| Post-condition(s) | Generate JWT token and send welcome email Redirect to home page |
| Basic Flow | 1. Access sign up page 2. Display registration form 3. Enter username, email, password and confirm password 4. Click "Sign Up" 5. Validate input format (username, email, password strength, passwords match) 6. Check email and username uniqueness 7. Create user record 8. Hash password before storing 9. Set initial status = AVAILABLE, workload = 0 10. Generate JWT token and send welcome email 11. Redirect to home page |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display validation error 2. Display "Email or username already in use" error |
| Related UI screen(s) | Register screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC03 — Forgot Password
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC03 |
| Name | Forgot Password |
| Actor(s) | ad, pm, mem |
| Priority | High |
| Trigger | Access forgot password page |
| Pre-condition(s) | A registered account and password reset flow are available. |
| Post-condition(s) | Update password and clear reset token Display success message |
| Basic Flow | 1. Access forgot password page 2. Display email input form 3. Enter email 4. Click "Send Reset Link" 5. Validate email format 6. Check user exists and not locked 7. Log warning but show success 8. Display generic success message 9. Generate reset token with 24h expiry 10. Save token to database 11. Send reset email to user 12. Display generic success message 13. Receive email 14. Click reset link 15. Validate reset token and expiry 16. Display password reset form 17. Enter new password 18. Click "Reset Password" 19. Validate password format 20. Hash new password 21. Update password and clear reset token 22. Display success message |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Check user exists and not locked 2. Display "Invalid or expired token" error |
| Related UI screen(s) | Forgot password screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users, password_reset_tokens |
UC04 — Reset Password
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC04 |
| Name | Reset Password |
| Actor(s) | ad, pm, mem |
| Priority | High |
| Trigger | Click reset password link from email |
| Pre-condition(s) | A registered account and password reset flow are available. |
| Post-condition(s) | Update password hash and clear token Redirect to sign in page with success message |
| Basic Flow | 1. Click reset password link from email 2. Validate reset token 3. Display reset password form 4. Enter new password 5. Click "Reset Password" 6. Validate password strength 7. Update password hash and clear token 8. Redirect to sign in page with success message |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Invalid or expired token" error 2. Display strength error |
| Related UI screen(s) | Forgot password screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users, password_reset_tokens |
UC05 — Update Personal Information
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC05 |
| Name | Update Personal Information |
| Actor(s) | ad, pm, mem |
| Priority | Medium |
| Trigger | Select Edit Profile |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Update session token with new profile data Notify success |
| Basic Flow | 1. Select Edit Profile 2. Query current user profile 3. Display edit form (full_name, email, avatar_url pre-filled) 4. Modify information 5. Click "Save" 6. Validate format and check email uniqueness 7. Update user record 8. Update session token with new profile data 9. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Profile not found" error 2. Display validation error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC06 — View User Profile
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC06 |
| Name | View User Profile |
| Actor(s) | ad, pm, mem |
| Priority | Medium |
| Trigger | Select "My Profile" from menu |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Display profile page (full_name, email, avatar, role, status, current_workload, skills list, active projects list, edit profile / delete account buttons) |
| Basic Flow | 1. Select "My Profile" from menu 2. Query user info by user_id (full_name, email, avatar_url, role, status, current_workload) 3. Query user's skill list (join user_skills + skills table, ordered by level DESC) 4. Query user's active project memberships (projects where user is member and project status != ARCHIVED) 5. Display profile page (full_name, email, avatar, role, status, current_workload, skills list, active projects list, edit profile / delete account buttons) 6. View profile details |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "User not found" error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC07 — Delete Personal Account
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC07 |
| Name | Delete Personal Account |
| Actor(s) | ad, pm, mem |
| Priority | Medium-High |
| Trigger | Click "Delete Account" |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Delete user and cascade data Redirect to landing page |
| Basic Flow | 1. Click "Delete Account" 2. Display confirmation dialog 3. Enter current password 4. Click "Confirm Delete" 5. Verify current password 6. Delete user and cascade data 7. Clear session 8. Redirect to landing page |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Incorrect password" error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC08 — View Personal Skill List
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC08 |
| Name | View Personal Skill List |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Access Skills page |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Display "No results found" notification Display filtered skill list (skill name, level 1-5) |
| Basic Flow | 1. Access Skills page 2. Query user skills (join user_skills with skills tables) 3. Display "No skills added yet" notification with add skill button 4. Display skill list (skill name, level 1-5) 5. Enter filter criteria (keyword: skill name, level: 1-5) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered skill list (skill name, level 1-5) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | user_skills, skills |
UC09 — View Personal Skill Details
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC09 |
| Name | View Personal Skill Details |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click on a skill from personal skill list |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Query user skill record (level, date added) by user_id + skill_id Display skill details (skill name, level 1–5, skill description, date added to profile, edit / delete buttons) |
| Basic Flow | 1. Click on a skill from personal skill list 2. Query user skill record (level, date added) by user_id + skill_id 3. Query system skill info by skill_id (name, description if available) 4. Display skill details (skill name, level 1–5, skill description, date added to profile, edit / delete buttons) 5. View skill details |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Skill not found" error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | user_skills, skills |
UC10 — Add Personal Skill
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC10 |
| Name | Add Personal Skill |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Add Skill" |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Update user's skill profile summary Notify success |
| Basic Flow | 1. Click "Add Skill" 2. Query available system skills not yet added by user 3. Display "You have added all available skills" notification 4. Display form (skill dropdown, level 1-5) 5. Select skill and level 6. Click "Save" 7. Validate and check for duplicate skill 8. Insert new user_skill record 9. Update user's skill profile summary 10. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display validation error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | user_skills, skills |
UC11 — Update Personal Skill
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC11 |
| Name | Update Personal Skill |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Edit" on a skill in personal skill list |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Notify success and reload skill details View updated skill level |
| Basic Flow | 1. Click "Edit" on a skill in personal skill list 2. Query skill details by user_id + skill_id (name, current level, date added) 3. Display edit form (skill name read-only, level 1–5 editable, current level pre-filled) 4. Adjust skill level using slider or input 5. Click "Save" 6. Validate level range (1–5 integer) 7. Update user_skill record (set level, update updated_at = NOW()) 8. Notify success and reload skill details 9. View updated skill level |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Skill not found" error 2. Display "Level must be between 1 and 5" error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | user_skills, skills |
UC12 — Delete Personal Skill
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC12 |
| Name | Delete Personal Skill |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click "Delete" on a skill |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Update skill list display Notify success |
| Basic Flow | 1. Click "Delete" on a skill 2. Verify skill exists in user's profile (lookup user_skill by user_id + skill_id) 3. Display confirmation dialog "Remove this skill from your profile?" 4. Click "Confirm" 5. Delete user_skill record 6. Update skill list display 7. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Skill not found" error |
| Related UI screen(s) | Profile screen |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | user_skills, skills |
UC13 — Configure System Parameters
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC13 |
| Name | Configure System Parameters |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Access System Settings |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Upsert settings record Notify success and display updated values |
| Basic Flow | 1. Access System Settings 2. Verify admin privileges 3. Query all settings 4. Display config form (key_name, value_json, description, e.g. max_workload, ai_model, sprint_duration_days) 5. Modify setting value 6. Click "Save" 7. Validate JSON format 8. Upsert settings record 9. Reload active settings in memory (cache invalidation) 10. Notify success and display updated values |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display format error 3. Reload active settings in memory (cache invalidation) |
| Related UI screen(s) | Admin system configuration |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | system_settings |
UC14 — View System Skill Directory
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC14 |
| Name | View System Skill Directory |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Access Skill Directory |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Display "No results found" notification Display filtered skill list (id, name) |
| Basic Flow | 1. Access Skill Directory 2. Query all system skills 3. Display "No skills defined yet" notification with add skill button 4. Display skill list (id, name) 5. Enter filter criteria (keyword: skill name) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered skill list (id, name) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Admin skill directory |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | skills |
UC15 — Add System Skill
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC15 |
| Name | Add System Skill |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Select function Skill Directory |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Insert skill record Notify success |
| Basic Flow | 1. Select function Skill Directory 2. Display skill directory with "Add Skill" button 3. Click "Add Skill" 4. Display form (skill_name field, required) 5. Enter skill name 6. Click "Save" 7. Validate name not empty 8. Check skill name uniqueness 9. Insert skill record 10. Index skill for search and assignment 11. Notify success 12. Refresh skill list in directory |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. |
| Exception Flow | 1. Display validation error |
| Related UI screen(s) | Admin skill directory |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | skills |
UC16 — Edit System Skill
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC16 |
| Name | Edit System Skill |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Click "Edit" on a skill |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Propagate name update to task skill references Notify success and refresh skill list |
| Basic Flow | 1. Click "Edit" on a skill 2. Query skill details by skill_id 3. Display edit form with current name 4. Modify skill name 5. Click "Save" 6. Validate not empty and check uniqueness 7. Update skill record 8. Propagate name update to task skill references 9. Notify success and refresh skill list |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Skill not found" error 2. Display validation error |
| Related UI screen(s) | Admin skill directory |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | skills |
UC17 — Delete System Skill
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC17 |
| Name | Delete System Skill |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Select function Skill Directory |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Notify success and reload skill list View updated skill directory |
| Basic Flow | 1. Select function Skill Directory 2. Display skill list 3. Click "Delete" on a skill 4. Query skill details by skill_id 5. Display "Skill not found" notification 6. Query count of users who have this skill in their profile (user_skills table) 7. Display confirmation dialog "Delete [skill name]? This will remove it from [N] user profiles. This action cannot be undone." 8. Close confirmation dialog 9. Delete skill record (CASCADE to user_skills records) 10. Notify success and reload skill list 11. View updated skill directory |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Skill not found" notification |
| Related UI screen(s) | Admin skill directory |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | skills |
UC18 — View Global User List
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC18 |
| Name | View Global User List |
| Actor(s) | ad |
| Priority | Medium |
| Trigger | Access User Management |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Display "No results found" notification Display filtered user list (name, email, role, status, workload) |
| Basic Flow | 1. Access User Management 2. Query all users (with role, status, workload) 3. Display "No users found" notification with invite action 4. Display user list (name, email, role, status, workload) 5. Enter filter criteria (keyword: name/email, role: ADMIN/MANAGER/MEMBER, status: AVAILABLE/BUSY/OFFLINE) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered user list (name, email, role, status, workload) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Admin user management |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC19 — Add System User
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC19 |
| Name | Add System User |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Access User Management |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Send welcome email with credentials Notify success and display new user in list |
| Basic Flow | 1. Access User Management 2. Display user list with "Add User" button 3. Click "Add User" 4. Display form (email, full name, password, role) 5. Enter user information 6. Click "Save" 7. Validate format and check email uniqueness 8. Hash password 9. Verify password hash integrity 10. Insert user (status=AVAILABLE, workload=0) 11. Send welcome email with credentials 12. Notify success and display new user in list |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. |
| Exception Flow | 1. Display validation error |
| Related UI screen(s) | Admin user management |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC20 — Edit System User
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC20 |
| Name | Edit System User |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Click "Edit" on a user |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | If email changed: send notification to user's new email Notify success and reload user details |
| Basic Flow | 1. Click "Edit" on a user 2. Query user info by user_id 3. Display edit form (full_name, email, role, status) 4. Modify user information 5. Click "Save" 6. Validate and check email uniqueness 7. Update user record 8. If email changed: send notification to user's new email 9. Notify success and reload user details |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "User not found" error 2. Display validation error |
| Related UI screen(s) | Admin user management |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC21 — Delete System User
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC21 |
| Name | Delete System User |
| Actor(s) | ad |
| Priority | Medium-High |
| Trigger | Click "Delete" on a user |
| Pre-condition(s) | User is authenticated as System Administrator. |
| Post-condition(s) | Delete user (CASCADE) Notify success |
| Basic Flow | 1. Click "Delete" on a user 2. Check if target is current logged-in admin 3. Display confirmation dialog 4. Click "Confirm" 5. Delete user (CASCADE) 6. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Cannot delete own account" error |
| Related UI screen(s) | Admin user management |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | users |
UC22 — View Joined Projects
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC22 |
| Name | View Joined Projects |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Access Projects page |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display "No results found" notification Display filtered project list (name, status, role, start/end date, member count) |
| Basic Flow | 1. Access Projects page 2. Query projects user is member of (with role, member count, dates) 3. Display "You have not joined any projects yet" notification with browse action 4. Display project list (name, status, role, start/end date, member count) 5. Enter filter criteria (keyword: project name, status: ACTIVE/COMPLETED/ARCHIVED) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered project list (name, status, role, start/end date, member count) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Project dashboard / project list |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | projects, project_members |
UC24 — View Project Details / Summary
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC24 |
| Name | View Project Details / Summary |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click on project name from project list |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display project overview (name, description, status, heuristic_mode, dates, member count, user role, active sprint summary, invite code) |
| Basic Flow | 1. Click on project name from project list 2. Check user is member of project 3. Query project info (name, description, status, heuristic_mode, start_date, end_date, invite_code) 4. Query member count and user's role in project 5. Query active sprint info (current sprint name, status, task completion %, start/end date) 6. Display project overview (name, description, status, heuristic_mode, dates, member count, user role, active sprint summary, invite code) 7. View project details |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "You are not a member of this project" error |
| Related UI screen(s) | Project workspace Project overview Timeline |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | projects |
UC25 — Update Project Information
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC25 |
| Name | Update Project Information |
| Actor(s) | pm |
| Priority | Medium |
| Trigger | Click "Edit Project" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update project record Notify success |
| Basic Flow | 1. Click "Edit Project" 2. Verify user has MANAGER role 3. Display edit form (name, description, dates, heuristic_mode) 4. Modify project information 5. Click "Save" 6. Validate project data 7. Update project record 8. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display validation error |
| Related UI screen(s) | Project settings general |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | projects |
UC26 — Join Project
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC26 |
| Name | Join Project |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Access Projects page |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Send project join notification to project manager Notify success and redirect to project page |
| Basic Flow | 1. Access Projects page 2. Display "Join Project" option 3. Select Join Project 4. Display form (invite link/code) 5. Enter invite code 6. Click "Join" 7. Validate invite code format 8. Query project by invite code 9. Check user is not already a member 10. Insert user into project_members (role=MEMBER) 11. Update user's project membership count 12. Send project join notification to project manager 13. Notify success and redirect to project page |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. |
| Exception Flow | 1. Display specific error (invalid format / project not found / already a member) |
| Related UI screen(s) | Project dashboard / project list |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members |
UC27 — Leave Project
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC27 |
| Name | Leave Project |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Leave Project" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Delete project_member record Redirect to project list |
| Basic Flow | 1. Click "Leave Project" 2. Display confirmation dialog 3. Click "Confirm" 4. Check if user is the only MANAGER 5. Delete project_member record 6. Redirect to project list |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Must transfer role first" error |
| Related UI screen(s) | Project workspace |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members |
UC28 — Close / Archive Project
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC28 |
| Name | Close / Archive Project |
| Actor(s) | pm |
| Priority | Medium-High |
| Trigger | Click "Close" or "Archive" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update project status (COMPLETED or ARCHIVED) Notify success |
| Basic Flow | 1. Click "Close" or "Archive" 2. Verify user has MANAGER role 3. Display confirmation dialog 4. Click "Confirm" 5. Update project status (COMPLETED or ARCHIVED) 6. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error |
| Related UI screen(s) | Project settings general |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | projects |
UC29 — View Project Member List
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC29 |
| Name | View Project Member List |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Select Members section |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display "No results found" notification Display filtered member list (name, email, role, performance_score, workload) |
| Basic Flow | 1. Select Members section 2. Query project members (join project_members with users) 3. Display "No members in this project yet" notification with invite action 4. Display member list (name, email, role, performance_score, workload) 5. Enter filter criteria (keyword: name/email, role: MANAGER/MEMBER) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered member list (name, email, role, performance_score, workload) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Project settings members |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members, users |
UC30 — View Member Details
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC30 |
| Name | View Member Details |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click on a member from member list |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display member details (name, email, role, performance_score, current_workload, skills list, task count by status, joined_at, update role / remove member buttons if MANAGER) |
| Basic Flow | 1. Click on a member from member list 2. Query member info (name, email, role, performance_score, current_workload, joined_at) by project_id + target_user_id 3. Query member's skills (join user_skills + skills table) 4. Query member's current tasks in project (count by status: TODO / IN_PROGRESS / REVIEW / DONE) 5. Display member details (name, email, role, performance_score, current_workload, skills list, task count by status, joined_at, update role / remove member buttons if MANAGER) 6. View member details |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Member not found" error |
| Related UI screen(s) | Project settings members |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members, users, user_skills |
UC31 — Add Member to Project
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC31 |
| Name | Add Member to Project |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Access Project Members page |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Send project invitation notification to user Notify success and refresh member list |
| Basic Flow | 1. Access Project Members page 2. Display member list with "Add Member" button 3. Click "Add Member" 4. Display form (user email, role selection) 5. Enter user email 6. Click "Add" 7. Check email format valid 8. Query user by email 9. Check user not already in project 10. Insert project_member record (role=MEMBER) 11. Update project member count 12. Send project invitation notification to user 13. Notify success and refresh member list |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. |
| Exception Flow | 1. Display specific error (invalid format / user not found / already a member) |
| Related UI screen(s) | Project settings members |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members |
UC32 — Update Member Role
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC32 |
| Name | Update Member Role |
| Actor(s) | pm |
| Priority | Medium |
| Trigger | Select new role for a member |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update member role in project_members Notify success |
| Basic Flow | 1. Select new role for a member 2. Verify user has MANAGER role 3. Display confirmation dialog 4. Click "Confirm" 5. Update member role in project_members 6. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error |
| Related UI screen(s) | Project settings members |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members |
UC33 — Remove Member from Project
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC33 |
| Name | Remove Member from Project |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Remove" on a member |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Delete project_member record Notify success |
| Basic Flow | 1. Click "Remove" on a member 2. Check if target is the only MANAGER 3. Display confirmation dialog 4. Click "Confirm" 5. Delete project_member record 6. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Cannot remove only manager" error |
| Related UI screen(s) | Project settings members |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | project_members |
UC34 — View Sprint List
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC34 |
| Name | View Sprint List |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Select Sprints section |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display "No results found" notification Display filtered sprint list (name, status, goal, start/end date, task count) |
| Basic Flow | 1. Select Sprints section 2. Query all sprints for the project (with task count) 3. Display "No sprints created yet" notification with create sprint button 4. Display sprint list (name, status, goal, start/end date, task count) 5. Enter filter criteria (status: PLANNING/IN_PROGRESS/COMPLETED) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered sprint list (name, status, goal, start/end date, task count) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | sprints |
UC35 — View Sprint Details
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC35 |
| Name | View Sprint Details |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click on a sprint from sprint list |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display sprint details (name, goal, status, heuristic_mode, start/end date, task list, status breakdown, progress %) |
| Basic Flow | 1. Click on a sprint from sprint list 2. Query sprint details by sprint_id (name, goal, status, heuristic_mode, start_date, end_date) 3. Query sprint's tasks (list with title, status, priority, assignee) 4. Count tasks by status (TODO / IN_PROGRESS / REVIEW / DONE) 5. Calculate sprint progress (% tasks in DONE status) 6. Display sprint details (name, goal, status, heuristic_mode, start/end date, task list, status breakdown, progress %) 7. View sprint details |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Sprint not found" error |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | sprints |
UC36 — Create New Sprint
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC36 |
| Name | Create New Sprint |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Create Sprint" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Insert sprint record Notify success |
| Basic Flow | 1. Click "Create Sprint" 2. Verify user has MANAGER role 3. Display form (name, start/end date) 4. Enter sprint information 5. Click "Create" 6. Validate sprint data 7. Insert sprint record 8. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display validation error |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | sprints |
UC37 — Update Sprint Information
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC37 |
| Name | Update Sprint Information |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Edit" on a sprint |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update sprint record Notify success |
| Basic Flow | 1. Click "Edit" on a sprint 2. Verify user has MANAGER role 3. Display edit form (name, dates) 4. Modify sprint information 5. Click "Save" 6. Validate sprint data 7. Update sprint record 8. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display validation error |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | sprints |
UC38 — Start / Complete Sprint
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC38 |
| Name | Start / Complete Sprint |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click "Start Sprint" or "Complete Sprint" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update sprint status (IN_PROGRESS or COMPLETED) Notify success |
| Basic Flow | 1. Click "Start Sprint" or "Complete Sprint" 2. Verify user has MANAGER role 3. Query current sprint status 4. Verify valid status transition (PLANNING→IN_PROGRESS, IN_PROGRESS→COMPLETED) 5. Display confirmation dialog 6. Click "Confirm" 7. Update sprint status (IN_PROGRESS or COMPLETED) 8. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display "Invalid status transition" error |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | sprints |
UC39 — Delete Sprint
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC39 |
| Name | Delete Sprint |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click "Delete Sprint" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Delete sprint record Notify success |
| Basic Flow | 1. Click "Delete Sprint" 2. Query sprint details by sprint_id 3. Verify user has MANAGER role 4. Display confirmation dialog "Delete [sprint name]? All tasks in this sprint will be moved to backlog." 5. Click "Confirm" 6. Move remaining tasks to backlog (set sprint_id = NULL) 7. Delete sprint record 8. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Sprint not found" error 2. Display "Access denied" error |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | sprints, tasks |
UC40 — View Kanban Board
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC40 |
| Name | View Kanban Board |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Select Kanban Board |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display kanban board columns (TODO / IN_PROGRESS / REVIEW / DONE) with task cards Display "No tasks" placeholder in empty column |
| Basic Flow | 1. Select Kanban Board 2. Query active sprints for the project 3. Fall back to backlog items (tasks where sprint_id = NULL) 4. Display sprint selector (list of sprints to choose from) 5. Select sprint to view (or keep default active sprint) 6. Query tasks for selected sprint grouped by status 7. Display empty board with "No tasks in this sprint" notification and create task button 8. Display kanban board columns (TODO / IN_PROGRESS / REVIEW / DONE) with task cards 9. Check each column for emptiness 10. Display "No tasks" placeholder in empty column 11. View kanban board |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Kanban board |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks |
UC41 — View Backlog
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC41 |
| Name | View Backlog |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Select Backlog |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display "No results found" notification Display filtered backlog list (title, priority, assignee, tags, difficulty_level) |
| Basic Flow | 1. Select Backlog 2. Query tasks where sprint_id = NULL (with assignee info, tags) 3. Display "Backlog is empty" notification with create task button 4. Display backlog list (title, priority, assignee, tags, difficulty_level) 5. Enter filter criteria (keyword: task title, priority: LOW/MEDIUM/HIGH/CRITICAL, assignee) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered backlog list (title, priority, assignee, tags, difficulty_level) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Sprint backlog |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, sprints |
UC42 — View Workload
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC42 |
| Name | View Workload |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Select Workload view |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display "No members in project" notification Display workload chart (member name, current_workload, assigned task count, overloaded flag) |
| Basic Flow | 1. Select Workload view 2. Query project members (join project_members with users) 3. Display "No members in project" notification 4. Query assigned tasks per member (count tasks grouped by assignee_id) 5. Calculate workload per member (current_workload = assigned task count, flag members exceeding threshold as overloaded) 6. Display workload chart (member name, current_workload, assigned task count, overloaded flag) 7. View workload chart |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Calculate workload per member (current_workload = assigned task count, flag members exceeding threshold as overloaded) 2. Display workload chart (member name, current_workload, assigned task count, overloaded flag) |
| Related UI screen(s) | Project settings members Task detail |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, users |
UC43 — View Task Details
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC43 |
| Name | View Task Details |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click on a task |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Query comments for this task (join with users for author info, ordered by created_at ASC) Display task details (title, description, status, priority, assignee, reporter, tags, difficulty_level, required_skills, dates, sub-tasks list, comments list, edit / delete / assign buttons) |
| Basic Flow | 1. Click on a task 2. Query task details by task_id (title, description, status, priority, assignee, reporter, tags, difficulty_level, required_skills, start_date, end_date) 3. Query sub-tasks (tasks where parent_id = task_id, ordered by created_at ASC) 4. Query comments for this task (join with users for author info, ordered by created_at ASC) 5. Display task details (title, description, status, priority, assignee, reporter, tags, difficulty_level, required_skills, dates, sub-tasks list, comments list, edit / delete / assign buttons) 6. View task details |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Task not found" error |
| Related UI screen(s) | Task detail |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, task_required_skills, task_labels |
UC45 — Update Task Information
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC45 |
| Name | Update Task Information |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Edit" on a task |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Notify task watchers of changes Notify success |
| Basic Flow | 1. Click "Edit" on a task 2. Query current task details 3. Display edit form (title, description, priority, sprint, tags, difficulty, required_skills) with current data pre-filled 4. Modify task information 5. Click "Save" 6. Validate task data 7. Update task record 8. Notify task watchers of changes 9. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Task not found" error 2. Display validation error |
| Related UI screen(s) | Task detail |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks, task_required_skills, task_labels |
UC48 — Delete Task
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC48 |
| Name | Delete Task |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click "Delete Task" |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Delete task (CASCADE sub-tasks and comments) Notify success and redirect to Kanban / Backlog view |
| Basic Flow | 1. Click "Delete Task" 2. Verify user is project member (MANAGER role, or task reporter/assignee) 3. Check if task has sub-tasks 4. Display confirmation dialog "Delete this task? Sub-tasks will also be deleted (N sub-tasks)." 5. Click "Confirm" 6. Delete task (CASCADE sub-tasks and comments) 7. Notify success and redirect to Kanban / Backlog view |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error |
| Related UI screen(s) | Kanban board Task detail |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | tasks |
UC49 — View Comments
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC49 |
| Name | View Comments |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | View task details page |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Display comment list (author, content, created_at) Show edit and delete buttons alongside own comments |
| Basic Flow | 1. View task details page 2. Query comments for the task (join with users for author info) 3. Display "No comments yet" notification with add comment prompt 4. Display comment list (author, content, created_at) 5. Check if current user owns each comment 6. Show edit and delete buttons alongside own comments 7. View comments |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Comment |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | comments |
UC50 — Write Comment
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC50 |
| Name | Write Comment |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Write Comment" on task details page |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Send notification to task assignee/reporter Notify success and display new comment |
| Basic Flow | 1. Click "Write Comment" on task details page 2. Verify user is a project member 3. Display comment input area 4. Enter comment text 5. Click "Submit" 6. Validate comment not empty 7. Insert comment record 8. Send notification to task assignee/reporter 9. Notify success and display new comment |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display validation error |
| Related UI screen(s) | Comment |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | comments, comment_mentions, notifications |
UC51 — Edit Comment
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC51 |
| Name | Edit Comment |
| Actor(s) | pm, mem |
| Priority | Medium |
| Trigger | Click "Edit" on own comment |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Update comment record Notify success |
| Basic Flow | 1. Click "Edit" on own comment 2. Verify user is comment owner 3. Display edit form with current content 4. Modify comment text 5. Click "Save" 6. Validate comment not empty 7. Update comment record 8. Notify success |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error 2. Display validation error |
| Related UI screen(s) | Comment |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | comments, comment_mentions |
UC52 — Delete Comment
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC52 |
| Name | Delete Comment |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Click "Delete" on own comment |
| Pre-condition(s) | User is authenticated and has access to the target project/resource. |
| Post-condition(s) | Delete comment record Notify success |
| Basic Flow | 1. Click "Delete" on own comment 2. Verify user is comment owner 3. Display confirmation dialog 4. Click "Confirm" 5. Delete comment record 6. Notify success |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error |
| Related UI screen(s) | Comment |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | comments |
UC53 — Receive Notification
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC53 |
| Name | Receive Notification |
| Actor(s) | ad, pm, mem |
| Priority | Medium-High |
| Trigger | Click notification bell (badge shows unread count) |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Display each notification (title, message, type: TASK_ASSIGNED / SPRINT_STARTED / etc., created_at, is_read status) Show "Mark all as read" button |
| Basic Flow | 1. Click notification bell (badge shows unread count) 2. Query all notifications for user (ordered by created_at DESC) 3. Count unread notifications (is_read = false) 4. Display "No notifications" message 5. Display notification panel (unread items highlighted, read items dimmed, badge count updated) 6. Display each notification (title, message, type: TASK_ASSIGNED / SPRINT_STARTED / etc., created_at, is_read status) 7. Show "Mark all as read" button 8. View notifications |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | Notification panel |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | notifications |
UC54 — Mark Notification as Read
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC54 |
| Name | Mark Notification as Read |
| Actor(s) | ad, pm, mem |
| Priority | Medium-High |
| Trigger | Click notification bell |
| Pre-condition(s) | User is authenticated and the required subsystem data exists. |
| Post-condition(s) | Display notification list View updated notifications |
| Basic Flow | 1. Click notification bell 2. Display notification list 3. View updated notifications |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Fetch notification record 2. Verify user owns notification (notification.user_id = current user) 3. Display "Access denied" error 4. Update notification is_read = true 5. Navigate to link_action target 6. Update all user's notifications (is_read = true) |
| Related UI screen(s) | Notification panel |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | notifications |
UC55 — Create New AI Chat Session
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC55 |
| Name | Create New AI Chat Session |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Select AI Assistant from menu |
| Pre-condition(s) | User is authenticated and has an available AI chat/session or project context as required by the action. |
| Post-condition(s) | Create new chat_session record (user_id, project_id if selected, auto-generated title, created_at) Display new empty chat interface (session title editable, project context shown) |
| Basic Flow | 1. Select AI Assistant from menu 2. Query existing chat sessions for user (ordered by created_at DESC) 3. Display session list (session title, date, message count) with "New Chat" button 4. Click "New Chat" 5. Query user's active projects (for optional project context) 6. Display new session form (optional: link to a project for context) 7. Optionally select a project context 8. Click "Start" 9. Create new chat_session record (user_id, project_id if selected, auto-generated title, created_at) 10. Display new empty chat interface (session title editable, project context shown) 11. View new chat session |
| Alternate Flow | 1. No separate alternate flow is specified beyond the activity diagram path. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | AI chat |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | chat_sessions |
UC56 — Chat with AI
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC56 |
| Name | Chat with AI |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Open AI Assistant |
| Pre-condition(s) | User is authenticated and has an available AI chat/session or project context as required by the action. |
| Post-condition(s) | Receive AI response and save to chat_messages Display AI response |
| Basic Flow | 1. Open AI Assistant 2. Load available chat sessions 3. Click "New Chat" 4. Create new chat session record 5. Select existing session 6. Load session context (previous messages in session) 7. Display chat history and input area 8. Enter message 9. Click "Send" 10. Validate message not empty 11. Save user message to chat_messages 12. Send to AI API (with session context and project context if relevant) 13. Receive AI response and save to chat_messages 14. Display AI response 15. Read AI response |
| Alternate Flow | 1. User may correct invalid input and resubmit until the validation checks pass. 2. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Message cannot be empty" error |
| Related UI screen(s) | AI chat Pending action confirmation |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | chat_sessions, chat_messages, ai_logs |
UC57 — View AI Chat History
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC57 |
| Name | View AI Chat History |
| Actor(s) | pm, mem |
| Priority | Medium-High |
| Trigger | Select AI Chat History |
| Pre-condition(s) | User is authenticated and has an available AI chat/session or project context as required by the action. |
| Post-condition(s) | Query messages for session (ordered by created_at ASC) Display full conversation history (user and AI messages) |
| Basic Flow | 1. Select AI Chat History 2. Query all chat sessions for the user (ordered by created_at DESC) 3. Display session list (title, date, message count) 4. Click on a session 5. Verify user owns this session (session.user_id = current user) 6. Query messages for session (ordered by created_at ASC) 7. Display full conversation history (user and AI messages) 8. View conversation history |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Display "Access denied" error |
| Related UI screen(s) | AI chat |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | chat_sessions, chat_messages |
UC58 — View AI Activity Logs
Sequence diagram
Activity diagram
| Field | Value |
|---|---|
| ID | UC58 |
| Name | View AI Activity Logs |
| Actor(s) | ad, pm, mem |
| Priority | Medium-High |
| Trigger | Select AI Activity Logs |
| Pre-condition(s) | User is authenticated and has an available AI chat/session or project context as required by the action. |
| Post-condition(s) | Display "No results found" notification Display filtered log list (user, request summary, action_taken, timestamp) |
| Basic Flow | 1. Select AI Activity Logs 2. Query AI logs (auto-assignment events, action_taken, timestamps) 3. Display "No AI activity recorded yet" notification 4. Display log list (user, request summary, action_taken, timestamp) 5. Enter filter criteria (project, date range, action type) 6. Click "Filter" 7. Apply filter criteria to query 8. Display "No results found" notification 9. Display filtered log list (user, request summary, action_taken, timestamp) |
| Alternate Flow | 1. Conditional branches in the activity diagram handle allowed business-state differences. |
| Exception Flow | 1. Unauthorized or insufficient permission rejects the request. 2. Invalid input or missing target resource returns an error and leaves data unchanged. |
| Related UI screen(s) | AI chat |
| Related sequence diagram(s) | sequence diagram |
| Related activity diagram(s) | activity diagram |
| Related database table(s) | ai_logs |
Pending action confirmation
AI Copilot may propose data-changing actions, but write actions are not executed immediately. The backend creates a pending action that contains the action id, user/session context, summary, arguments, optional preview and an executable operation. The user reviews the action and confirms or cancels it. On confirmation, TaskPilot checks the same user/session ownership and expiry before executing the action through the appropriate domain service. Authorization and business rules remain enforced by the target service. The current implementation stores pending actions in runtime memory with a 10-minute TTL, so this state is not durable across backend restarts.
Related artefacts: pending action confirmation sequence, AI chat UI, pending action confirmation UI.