1. What is the syllabus's central claim about AI and the Requirements Engineer's role?
2. In addition to eliciting, documenting and validating requirements, what does the Requirements Engineer become in AI-supported processes?
3. Selecting an LLM to remove duplicate requirements, integrating it with the team repository, and defining how duplicates are flagged and reviewed illustrates which role?
4. What is the non-negotiable rule attached to the prompt designer and quality reviewer role?
5. Which duties does the syllabus assign to the Requirements Engineer as risk and compliance manager? Select all that apply.
6. A team plans to run an LLM continuously in the background to re-classify all requirements in real time. What does the syllabus suggest the Requirements Engineer should consider?
7. What risks does unreflective or unnecessarily intensive use of AI tools introduce, according to version 1.0.0 of the syllabus?
8. What does building stakeholder trust require beyond sharing AI-supported outputs?
9. Why does the syllabus say human-centric activities require particular attention when parts of the RE process are automated?
10. Which statement best reflects the syllabus's position on discussing ethical concerns about AI with stakeholders?