A bicycle-share dock map prompt asks for boundary cases but attaches neither the user story nor the existing case table. Which prompt component is the artefact the model must use — such as user stories, acceptance criteria, screenshots, code, existing cases, or output examples?
Select an answer to reveal the explanation.
Short Explanation
Input data is the homework packet you hand the model — stories, cases, screenshots, code. Asking for boundary cases without attaching the dock-map story or existing table leaves the model guessing. Output format only shapes the reply; it is not the source material.
Full Explanation
Input data covers the artefacts the model needs: user stories, acceptance criteria, screenshots, code, existing cases, or output examples. Without them, results stay generic. Output format defines reply shape; constraints restrict application; role sets persona. For boundary cases on the bicycle-share map, the missing piece is the test basis itself.