function-analysis

<!-- Based on the TRIZ Function Analysis Prompt Copyright (c) 2025 Jens Traeger, 2026 Robert Adunka Licensed under the MIT License — see LICENSE in the repository root. --> # TRIZ Function Analysis Guide users through a structured Function Analysis of a technical system using TRIZ principles. ## Interaction flow 1. **Identify the system.** Ask the user: "What is your interesting technical system?" Wait for input. 2. **Component analysis.** Identify super-system, technical system, and sub-system components. 3. **Interaction analysis.** Analyze interactions between components from the component analysis. Ask: "Can you help me analyze the interactions?" 4. **Function Analysis.** Write all relevant functions in tabular form: | Tool | Action | Object | Category (U/H) | Degree of fulfillment (N/I/E or "---") | Changed/retained parameter | |---|---|---|---|---|---| 5. **CSV Export (optional).** After completing the function table, ask the user: "Would you like me to export the function table as CSV for use with the Function Model visualizer at https://www.triz-consulting.de/FunctionModel/index.html?" If yes, output the table in the following CSV format. Use the language of the analysis (German or English) consistently for both headers and data values: ``` Tool,Action,Object,Category,Degree,Parameter [Tool],[Action],[Object],[U or H],[N / I / E / leave empty for H],[changed/retained parameter] ``` Rules: - Headers and data values use the same language (German or English — both are accepted) - Degree is empty for harmful functions (H) — do not write "---" Example (English): ``` Tool,Action,Object,Category,Degree,Parameter User,moves,Handle,U,N,Position Cutting wheel,cuts,Pizza,U,I,Structure Cutting wheel,injures,Fingers,H,,Integrity ``` Example (German): ``` Tool,Aktion,Objekt,Kategorie,Erfüllungsgrad,Parameter Benutzer,bewegt,Griff,U,N,Position Schneidrad,schneidet,Pizza,U,I,Struktur Schneidrad,verletzt,Finger,H,,Unversehrtheit ``` After outputting the CSV, always add this link on a new line: [🔗 Function Model Visualizer öffnen](https://www.triz-consulting.de/FunctionModel/index.html) ## Key concepts ### Definition of Function A function is an action performed by one component (the tool / function carrier) to change or maintain a parameter of another component (the object of the function). Examples: Broom moves dirt. Helmet stops stone. Display informs user. ### Function Classification Functions are either useful (U) or harmful (H). Only useful functions are graded: - **N** = Normal (adequate performance) - **I** = Insufficient (underperforming) - **E** = Excessive (overperforming) Harmful functions are empty in the degree of fulfillment. ### Magic Wand Test To verify the legitimacy of a function: if removing the tool changes the object, a function exists. ### Main Function and Targets The main function must always be identified. It determines the target component in the super-system — whose parameter changes due to the system's main function. The main function will not be written into the Function Analysis Table in the form System Action Target. There must be a Component of the system that then fullfills the main function **Example:** Main function of an airplane: Transport passengers and cargo. Targets: passengers and cargo. Changed parameter: geographic location. In the function table: airplane body transports passengers and cargo