Untitled
unknown
plain_text
a year ago
2.9 kB
4
Indexable
Here's a textual representation of the use case diagram i need you to create for the "Guardian View" project: [Security Personnel] | |-- Upload Video | |-- Process Video for Threat Detection | |-- Receive Alert Notifications | |-- Review Historical Alerts | |-- Authenticate User | [Admin] | |-- Register New User | |-- Manage User Accounts | [YOLO Model] | |-- Detect Weapons in Video | [System] | |-- Generate Alerts | |-- Store Video Data | |-- Manage User Authentication | |-- Update User Location This use case diagram represents the main actors and their interactions with the "Guardian View" system: Security Personnel can: Upload Video Process Video for Threat Detection Receive Alert Notifications Review Historical Alerts Authenticate User Admin can: Register New User Manage User Accounts (Plus all actions of Security Personnel) YOLO Model: Detect Weapons in Video System: Generate Alerts Store Video Data Manage User Authentication Update User Location This diagram illustrates the primary functions of the system and how different users interact with it. The YOLO Model is included as an actor since it performs a specific role in the system. Actors: Represented by stick figures Placed outside the system boundary Examples: Security Personnel, Admin, YOLO Model Use Cases: Represented by ovals Contain text describing the action/function Placed inside the system boundary Examples: "Upload Video", "Process Video for Threat Detection", etc. System Boundary: Represented by a rectangle Encloses all the use cases Relationships: Represented by lines Connect actors to the use cases they interact with Include/Extend Relationships: Represented by dashed arrows "Include" shows that one use case always includes another "Extend" shows optional behavior Here's how you would structure the diagram: Draw a large rectangle to represent the system boundary. Inside the rectangle, draw ovals for each use case: Upload Video Process Video for Threat Detection Receive Alert Notifications Review Historical Alerts Authenticate User Generate Alerts Store Video Data Manage User Authentication Update User Location Register New User Manage User Accounts Detect Weapons in Video Outside the rectangle, draw stick figures for: Security Personnel Admin YOLO Model Draw lines connecting the actors to the use cases they interact with. For relationships between use cases: Use a dashed arrow with <<include>> for actions that are always part of another action. Use a dashed arrow with <<extend>> for optional actions. For example: "Authenticate User" might have an <<include>> relationship with most other use cases. "Generate Alerts" might have an <<extend>> relationship with "Process Video for Threat Detection".
Editor is loading...
Leave a Comment