Native terminology
Interactive customer-business interview patent US6701322B1; priority 2000-06-07.
Use question/answer data and branching rules to select the next interview step.
Preserve what the model says and how it works before interpreting its relevance to another system.
Interactive customer-business interview patent US6701322B1; priority 2000-06-07.
Rule-driven adaptive elicitation with persistent response data.
Strong antecedent for 20-questions-like inquiry; comparison should focus on what the collected answers construct and authorize.
Provisional author analysis; follow linked sources for the original descriptions and claims.
| 01. Identity | Interactive customer-business interview patent US6701322B1; priority 2000-06-07. |
|---|---|
| 02. Meaning | Composition assembles a situation-dependent sequence of questions from declared rules and prior answers. |
| 03. Purpose | Adapt customer or support interviews to respondent information without rewriting the whole software application. |
| 04. Elements | Questions, alternative answers, branch rules, respondent context, agent systems and stored results. |
| 05. Structure | Relational tables connect question identifiers, answer choices and next-question selection rules. |
| 06. Composition | A selected answer indexes a branching rule, which determines the subsequent question and script path. |
| 07. Operation | The system runs the interview interactively and can record results. |
| 08. Results | An adapted interview sequence and stored response data. |
| 09. Assurance | Determinate branching supports replay of rule choices; it does not by itself warrant the adequacy of subsequent functional models. |
| 10. Standing | Granted patent; a direct early precedent for interactive question-path control. |
This evaluation grammar is XTechGroup's, not necessarily native to the external model.
Purpose of the customer interview
Branch tables and answer selection
Capture and retention of responses
Interactive question presentation
Notes are saved locally in your browser when supported. Use Export to create a durable JSON backup; Import restores it. Editing notes does not change the authored model records.