Universal language of the project
It has been said, that the analyst is a translator between business and development in a project. And what if the project is complex and the system is large? Or there are several systems in the solution? Does an analyst have to become a polyglot and learn how to translate from the language of business into the language of architects, from the language of one team or system into the language of another team or system? How to eliminate all the difficulties of communication? Or maybe you shouldn't get involved in this dead business and acquire a single language of a project?
The author of the talk proposes an approach to acquiring a unified vocabulary of the project, which was successfully applied in the design and development of several Enterprise solutions in federal-level projects.