Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
262:prepareprocessforagenticai [2026/11/18 16:59] – Iseler, Marc262: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 to MCP (permissions)+ 
 +Also ensure that users have access to all workspaces within a collection. A collection is exposed only if the user has the required permissions for every workspace it contains.
 ===== 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): lists all use-cases for a given projectID +  * Stages usecases list (projectID): lists all modelled use-cases for a given 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" element type. It is intended to use as a top-level element in this process element tree. It is a container element which contains phases and milestones and it defines the scope for a use-case package.+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 and Milestones and defines the scope of a use-case package.
  
-From a method perspective the scope of a use-case shall be aligned with the responsibility and tasks of a single agent, so an agent receives the right amount of process goverance at a time.+From a methodological perspective, the scope of a Use Case should be aligned with the responsibilities and tasks of a single agent. This ensures that the agent receives the appropriate amount of process governance for the task at hand.
  
-For generation of an use-case package the following modelling patterns are considered: +When generating a use-case package, the following modeling patterns are taken into account:
-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, including Decisions and their alternative branches. +
-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, are delivered as notes on the respective element.+
  
 +  * **Sections**: The sections, each represented by a Phase → Milestones tuple, are included in the order defined by the Use Case.
 +  * **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.