Known Issues and Limitations in Codebeamer AI Requirement Assistant
The following are known issues.
• Rewrite and Format Limitations
◦ Rewrite functionality sometimes adds a system placeholder if added in the wrong position. For example, rewrite of The car stops within 10 seconds when the brake is pressed. will return The [system] shall cause the car to stop within 10 seconds when the brake is pressed..
◦ The Requirement Assistant Rewrite action may split, clarify, and format requirements using predefined templates. While this improves structure and consistency, the process can introduce limitations in certain scenarios.
◦ The Format option restructures requirements by extracting semantic elements (such as subject, action, and condition) and rebuilding the requirement using a fixed template. As part of this process, only text mapped to supported template nodes is preserved.
◦ Adverbs or qualifying phrases that do not map to a template node may be omitted during formatting.
▪ Commonly affected elements include adverbs describing how an action is performed (for example, automatically, securely)
▪ Soft qualifiers or conditional phrases (for example, if possible, as needed)
Example
Original: The system shall automatically stop operations when motion is detected.
Formatted: The system shall stop operations when motion is detected.
◦ Modal verb standardization
The Format action enforces standardized requirement language, which may replace the original modal verb and change optionality.
◦ Logical operator changes (“and/or”)
If a requirement is split before formatting, alternative or optional conditions may be rewritten as mandatory statements.
◦ Causal or means relationships
Requirements describing how an outcome is achieved (for example, by using X) may lose that coupling if split and formatted separately.
PTC recommends reviewing rewritten and formatted requirements before saving and manually restoring critical qualifiers, conditions, or optionality where required. The Format option is intended as a structuring aid and does not guarantee preservation of all semantic nuances.
• German Language Improvements and Remaining Limitations
Starting with Codebeamer AI 1.1, the Requirement Assistant includes several improvements to German (de‑DE) rewrite and format behavior. These enhancements improve grammatical correctness and reduce mixed‑language output. However, some limitations still remain.
◦ Improvements in Codebeamer AI 1.1
The following improvements apply when using Analyze and Rewrite actions (including Format, Split, and Clarify) on German requirements:
▪ Improved German grammar and article usage
The Requirement Assistant corrects common grammatical errors, including:
▪ Incorrect article forms. For example, Die Motor to Der Motor
▪ Missing articles
▪ Incorrect case and declension
▪ Reduced German–English language mixingEnglish determiners and keywords (such as the, when, while) are replaced with appropriate German equivalents.
▪ Improved handling of rationale and intent relationships
When merging intent and rationale, the Requirement Assistant:
▪ Uses German equivalents for common phrases such as um zu, um sicherzustellen.
▪ Adds required punctuation (for example, commas before rationales) to produce natural German output.
▪ Cleaner split behavior for enumerations and combined statements When splitting German requirements, qualifiers and phrases are preserved more consistently and are no longer duplicated across all generated intents.
◦ Remaining Limitations for German Requirements
Despite these improvements, the following limitations may still occur:
▪ Standardized modal verbs may change the original intent
As with English requirements, formatting may replace modal verbs and strengthen the obligation (for example, replacing sollte with muss).
▪ Semantic nuances may not be fully preserved
Soft qualifiers, optional constraints, or contextual nuances may be omitted or rewritten for structural clarity.
▪ German formatting is not yet fully template‑native
German rewrite currently relies on English‑based prompt logic, which may not always follow strict German normative or regulatory writing conventions.
◦ Recommendation for German Requirements
When working with German requirements, PTC recommends that you:
▪ Review rewritten and formatted output carefully before saving
▪ Validate modal verbs and obligation level (muss, soll, darf nicht)
▪ Manually restore critical qualifiers or contextual wording where required
The Requirement Assistant is designed to improve structure and readability, but it does not replace domain‑specific or regulatory review for German language requirements.
• Codebeamer AI Requirement Assistant supports only plain text. The following content types in trackers are not supported:
◦ Images, any inserted diagrams
◦ Links: external URLs and links to other Codebeamer items
◦ Files Uploaded within the tracker
◦ Emojis
◦ Table Data
A warning is shown when selecting a requirement with images, but not for other unsupported content types.