A sequence diagram for the city's Webex ChatOps bot shows only the happy-path 200 from the Webex API. Design review asks how the diagram should also cover a 401 or timeout without turning into application source code. What belongs on the diagram?
Select an answer to reveal the explanation.
Short Explanation
Happy path alone is half a story. An alt or opt fragment on the diagram is the stage direction for 'what if the API says no or goes silent'—still design, not source code.
Full Explanation
Task 1.12 expects API-aware sequence diagrams, including alternate or optional fragments for failure paths such as 401 or timeout. That stays at diagram level and is not Domain 2 error-handling implementation. Pasting try/except code or redrawing topologies does not replace the fragment notation.