Diagrams are recommended in systems analysis for all these r

Diagrams are recommended in systems analysis for all these reasons EXCEPT which one?

Teach stakeholders how to draw up their requirements for the Systems Analyst’s use (to educate users in how to make the systems analysis process faster)

Provide unambiguous, standardized specifications from the Systems Analyst to the system developers (to speak a common technical language and prevent misunderstanding)

Gain stakeholders’ clear understanding when the Systems Analyst is reconciling different stakeholders’ viewpoints (to help communication clarity between parties)

Guide the Systems Analyst’s own elicitation of requirements from the stakeholders (to serve as a kind of checklist for what to ask)

Solution

System analyst basically work on documenting the Information Systems work to make it understandable , improve it and they help to build the IT system . So we can say that they have full information about the work that is going in the IT project . They also predict the expected requirements in the system that is going to build in the future .

So the System Analyst prepare the user cases , activities , the whole data flow and the interactions of the system .

They also keep monitor the system and review the bugs report to come on the right predictions and information for the user .

So basically they use diagrams to tell a common technical language and prevent misunderstanding , to help communication clarity between parties and to serve as a kind of checklist for what to ask .

So the Option A is the correct one because except this all other options are the reasons for the diagrams are recommended in System Analysis.