A UseCase object formulates the modelling problem by associating a context with a target. UseCase objects facilitate the organization of your observation tables, feature tables and deployments. UseCase objects also play a crucial role in FeatureByte Copilot, enabling it to provide tailored feature suggestions.
Creating a UseCase¶
To construct a new Use Case, the following information is required:
Select a Context: Choose a registered Context that defines the environment of your UseCase.
Define a Target: Specify a registered Target that represents the goal of your UseCase.
The context and target must correspond to the same entities.
create() class method to add the UseCase to the active catalog:
For a comprehensive use case setup, include a detailed description:
You can also use the
description parameter in the
create() class method.
Providing a detailed description of the use case, context, and target ensures better documentation and enhances the effectiveness of the FeatureByte Copilot in suggesting relevant features and assessing their relevance.
Association with Observation Table¶
Observation tables are automatically linked to a Use Case when they are derived from
- an observation table that is linked to the use case's context
- a target that is linked to the use case
Finally, you can list observation tables associated with the UseCase using the
Association with Deployment¶
A deployment is associated with a use case when the use case is specified during the related feature list deployment.
Association with Feature Table¶
Feature tables are automatically associated with use cases via the observation tables they originate from.