I'm a programmer currently working in rounds of meetings along with BAs and PM to gather/describe modules and functionality of our case management system; after a few meetings I saw that using 'use cases' would be a very very good fit to document many of the things and functions discuessed and/or proposed for the new system. When I suggested we needed to create 'use cases' so that we don't forget what we said/concluded and also to have programers know what they should code, the leading BA mentioned don't like 'use cases'.What can be used to gather/document requirements when people supposed to write user requirements say they don't like 'use cases', or when you realize that they don't want to write 'use cases' to describe what the system should do?I'm trying to find out if there's a close or effective substitution to using 'use cases' to document system functionality/scenarios.
What can be used in lieu of use cases to gather requirements?
requirements;user story;use case
Depending on your/their definition of a 'use case' you could instead look at 'user stories'. I say this if you define a use case similar to Usability.gov's definitionA use case is a description of how users will perform tasks on your Web site.  A use case includes two main parts:  the steps a user will take to accomplish a particular task on your site  the way the Web site should respond to a user's actions. A use case begins with a user's goal and ends when that goal is fulfilled.You can instead use user stories, which come from the agile development methodologies. They are more about what you want to do, then how to do it. There are many different articles and definitions about user stories out there. This older article actually presents what they see as the difference between use cases and user stories (New to User Stories?) And in the end, they really do the same thing. They just frame them differently. You still need the same information, who, what and why (goal). Their meant to be more narrative, with personas linked to real user types of your system. They're more descriptive, but still contain all the information you need.It sounds like in your case, representing the same information you need differently might be exactly what you need.