Patrick Reany
15 June 2024
How should the term 'use case' be defined? I've only recently learned the term and I'm having trouble understanding it. So, yesterday, when I heard the following presenter use the term in a way novel to me, I wanted to go to Copilot for its advice on the matter.
What is Explainable AI? IBM Technology. [Starting from timestamp about 5:50].
"And we've talked already about financial services as a use case. But there are plenty of use cases across many industries that we can apply this to. For example, let's consider healthcare. etc."So, to me, this seemed like a clear generalization of the meaning of 'use case' I had learned from the application-interface design perspective. The presenter, Martin Keem, seemed to be using the term as though it means -- at least for his use -- 'a specific example of' or 'instance of'.
Patrick:
Does 'use case' mean 'a specific example of' or 'instance of'?
Copilot:
A use case refers to how users interact with a system or product to achieve specific goals. It outlines the flow of user inputs, including successful and failed paths. In software and systems engineering, it can mean either:
1. A usage scenario for software, suggesting situations where the software may be useful [3].
2. A potential scenario in which a system receives an external request (such as user input) and responds to it [3].
Use cases vary in complexity, but they typically involve actors (users or software), the system, and the desired goals. Business use cases describe general interactions, while system use cases delve into technical details [2]. If you need further clarification or examples, feel free to ask!
Source: Conversation with Copilot, 6/15/2024
(1) Use case - Wikipedia. https://en.wikipedia.org/wiki/Use_case.
(2) What is a use case? How to write one, examples, + template. https://www.figma.com/resource-library/what-is-a-use-case/.
(3) . https://bing.com/search?q=use+case+meaning.
(4) USE CASE Definition & Meaning | Dictionary.com. https://www.dictionary.com/browse/Use-case.
(5) What is a Use Case? - Definition from Techopedia. https://www.techopedia.com/definition/25813/use-case.
(6) undefined. http://www.oxforddictionaries.com/us/.
Patrick:
How abstract can we generalize the notion of 'use case'? Let's see: If we define the 'system' as a collection of general-purpose management principles over a collection of disparate technologies, then a 'use case' in this scenario would be the use (i.e., tailored application) of those general principles as they would be applied to that specific technology. Therefore, from the viewpoint of the specific technology, 'use case' refers to how that technology interacts with this abstract system of principles.
Copilot:
Your analysis is insightful! Indeed, the concept of a use case can be abstracted beyond specific software or systems.
Let's break it down:
1. General Principles System: You've defined a system as a collection of general-purpose management principles. These principles could be anything from project management methodologies to organizational strategies.
2. Specific Technology: Each technology (software, hardware, or process) interacts with these principles differently. For instance:
- In software development, a use case might involve how a web application handles user authentication.
- In manufacturing, a use case could describe how a robotic arm assembles components based on quality control principles.
- In business operations, a use case might explore how supply chain management principles apply to a specific product line.
3. Tailored Application: The use case tailors those general principles to a specific context. It's like applying a template to a unique situation. For example:
- Applying agile project management principles to a software development team.
- Using lean manufacturing principles to optimize production in an automotive assembly line.
- Implementing customer relationship management (CRM) principles for a sales team.
4. Interaction: From the viewpoint of a specific technology, a use case describes how that technology interacts with the abstract system of principles. It's about aligning the principles with the technology's purpose, constraints, and goals.
Your perspective highlights the versatility of use cases -- they're not limited to software alone. They bridge theory and practice, adapting principles to real-world scenarios. If you have more thoughts or need further examples, feel free to share!
So, in the end Copilot understood what I was suggesting, and then offered a short essay of supporting evidence in the form of a company that has many functions and how those function have to align with the over-arching company policies. Bravo.
LLMs are not currently at the stage of being good at arriving at generalizations or abstractions on their own, but they are very good at logically presenting information to support a new idea or reject it. Humans and LLMs can therefore work quite well together to introduce and vet new ideas.