Individuals from analysis, architecture, departmental analysis, business analysis, process owners, testers, QM participants, team leaders 

No prior knowledge of Artificial Intelligence or Requirements Engineering necessary.

1.    Fundamentals of AI and RE
       1.1.    Requirements Engineering in a development project
       1.2.    Why Requirements Engineering (despite Artificial Inetelligence)
       1.3.    The role of Artificial Intelligence (AI) in Requirements Engineering
       1.4.    Interaction between humans and AI
       1.5.    Basics of Prompt Engineering
       1.6.    Prompt Frameworks and Prompt Techniques

2.    Structuring of Requirements
       2.1.    Strucuture of a Requirements document
       2.2.    Requirements of different architectural levels
       2.3.    Document analysis with AI
       
3.    Context definition
       3.1.    Importance and problems of context when using AI
       3.2.    Project context of the System of Interest
       3.3.    Technical context of the System of Interest
       3.4.    Prompt Engineering context 

4.    Requirement elicitation with AI
       4.1.    Creating Personas for Stakeholder(s) groups
       4.2.    Deriving requirements for Personas
       4.3.    Deriving requirements from standards and laws 
       4.4.    Deriving requirements from a specification document
       4.5.    Elicitation techniques and chatbots 

5.    SOPHIST Prompt Engineering Rulebook
       5.1.    Importance of language for Prompt Engineering 
       5.2.    Rules of the SOPHIST Prompt Engineering Rulebook 
       5.3.    Output formats for Requirements Engineering 

6.    Requirements documentation in prose 
       6.1.    Fundamentals of the SOPHIST Rulebook (for requirements) 
       6.2.    Rules of the Rulebook (for requirements) 
       6.3.    Application of the Rulebook (for requirements) 
       6.4.    MASTeR for functional requirements with and without AI 
       6.5.    MASTeR for non-functional requirements with and without AI 

7.    Generating views on requirements model-based and with AI 
       7.1.    Deriving Use Cases from Stakeholder Needs including Traceability 
       7.2.    Filling out Use Case Templates 
       7.3.    Creating Use Case Diagrams 
       7.4.    Deriving flows for the Use Cases from Personas and Stakeholder Needs 
       7.5.    Deriving states of the System of Interest (as text) 
       7.6.    Deriving states of business-relevant objects (as text) 
       7.7.    Information models and glossary for the System of Interest 

To provide our participants with the most valuable training, we reserve the right to make minor content changes or didactic adjustments during the training. 

For in-person training, it is mandatory to bring your own computer. Participants need access to at least one chatbot (Chat GPT, BART, Copilot) for which an account (whether free or paid) must be set up in advance of the training.