"Use case" is an appropriate way to describe a solution. From the perspective of a Solution Architect, I'd say its mostly marketing fluff but the reason the ter

"Use case" is an appropriate way to describe a solution. From the perspective of a Solution Architect, I'd say its mostly marketing fluff but the reason the term caught on is the distinction between delivering a system vs. delivering a system plus the guidance/procedures to successfully leverage it. I rarely get to just code something; oftentimes I need to understand the goal, the entirety of the existing process (because most people only know their little piece) and then figure out what makes the most sense to solve for X. There's a lot of non-technical heavy lifting involved in successfully delivering something in the enterprise. That coupled with the obsession over buzz words is likely why "solution" has taken hold in the enterprise space and no where else.