Is a scenario a bigger picture with more details than a use-case or how much difference is there? I write a report where I prefer the word scenario but in my training we used the word use-case (in a course about OOP). I program in SMV which is not OOP. IIUC SMV is a domain-specific language specialized for model checking of hardware. The actual code is in my github. 
Difference between scenario and use-case
use case;test scenarios
A use case involves an actor and the flow that a particular actor takes in a given functionality or path.  These often get grouped so you have a set of use cases to account for each scenario.A Scenario involves a situation that may have a single or multiple actors that take a given functionality or path to resolve the scenario.You can see the main difference is perspective here.  Usually the use case is more granular than the scenario.  In the development of these it usually involves coming up with a scenario and then define all the use cases that fit into that particular scenario.  Since the use cases document the scenario after written the documentation footprint is usually just one or the other and not both, which is also likely why the name gets interchanged sometimes instead of standing as separate things.  Many projects don't require the granularity of the use case and stick with just scenarios instead of breaking it down to specific actor flows in use cases.