Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 262:prepareprocessforagenticai [2026/11/18 17:00] – [Use-case modelling] Iseler, Marc | 262:prepareprocessforagenticai [2026/11/18 17:07] (current) – [Prepare your Process for Agentic AI] Iseler, Marc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Prepare your Process for Agentic AI ====== | ====== Prepare your Process for Agentic AI ====== | ||
| - | - define collection | + | Ensure that collections are properly defined so that the agent can identify the correct project based on the available context. |
| - | - define exposure | + | |
| + | Also ensure that users have access | ||
| ===== How it works ===== | ===== How it works ===== | ||
| Line 8: | Line 9: | ||
| * Stages projects list: lists all available collections | * Stages projects list: lists all available collections | ||
| - | * Stages usecases list (projectID): | + | * Stages usecases list (projectID): |
| - | * Stages usecases get (use-case ID): get the Use Case package in MarkDown for a given use-case-ID | + | * Stages usecases get (use-case ID): get the Use-Case-package in MarkDown for a given use-case-ID |
| ===== Use-case modelling ===== | ===== Use-case modelling ===== | ||
| - | Use-case is a subtype of the "Phases and Milestones" | + | A Use Case is a subtype of the Phases and Milestones element type. It is intended to serve as a top-level element in the process element tree. As a container element, it comprises Phases |
| - | From a method | + | From a methodological |
| - | For generation of an use-case package the following | + | When generating a use-case package, the following |
| - | * The sections (tupels of Phase → Milestones) in the order as the the Use Case defines it | + | |
| - | * For each Milestone, the gates: the required Work Products and Quality Levels, with their criteria as a checklist. | + | |
| - | * For each section, the Activities of the associated Workflows in the order given by their sequence associations, | + | |
| - | * For each Activity, the Responsible and other RASIC Roles, input and output work products and the agent policy regarding human only role execution | + | |
| - | * All Practices, Tools and Checklists associated with the Use Case, its subordinated Phases and Milestones and the associated Quality Levels, Activities and Work Products. Templates, Trainings and other Guidance elements are not passed on. | + | |
| - | * Association-comments, | + | |
| + | * **Sections**: | ||
| + | * **Milestone gates**: For each Milestone, the applicable gates are included. These comprise the required Work Products and Quality Levels, including their criteria presented as a checklist. | ||
| + | * **Activities and flow**: For each section, the Activities of the associated Workflows are included in the order defined by their sequence associations. This also includes Decisions and their alternative branches. | ||
| + | * **Roles and work products**: For each Activity, the Responsible Role and other RASIC Roles are included, together with the input and output Work Products and the applicable agent policy regarding roles that may only be performed by humans. | ||
| + | * **Supporting process elements**: All Practices, Tools, and Checklists associated with the Use Case, its subordinate Phases and Milestones, and the associated Quality Levels, Activities, and Work Products are included. Templates, Trainings, and other Guidance elements are excluded from the generated package. | ||
| + | * **Association comments**: Comments attached to associations are included as notes on the respective process element. | ||