Hello
suppose that we have a system analyst that collect requirements from users then sends them to development team in a document;
the developers needs ONLY the areas of business that were selected for automation, and I think that Use Case is more than enough to tell the developer IN DETAILS how the automation will be because the components of the Use Case are very rich in information
BUT some people think that use case are deticated for TRADITIONAL requirements!! and in SCRUM the new technique is USER STORY