8.2 Use Case Analysis

The Use Case Analysis report is part of the Data Foundation Reports repository within the Catalog system. It serves as a structured analysis tool for understanding different business use cases, entities, attributes, and related business terms. This report is essential for organizations that need insights into various data use cases and their associated metadata.

To access DQ dashboards:

  1. Navigate to Data Visualization, click Source Data Visualization.
  2. Navigate to the Catalog menu, and open the Catalog application.
  3. Click on the Shared Folders tab.
  4. Navigate to Data Foundation Reports.
  5. Locate the Use Case Analysis folder in the list and click Use Case Analysis.
  6. Inside the folder, open the Use Case Analysis report.
    The Use Case Analysis > Visualize window appears.

    Figure 8-72 Visualize Window


    Visualize Window

8.2 Use Case Analysis Window

The Use Case Analysis window consists of several key elements that help users explore and visualize data effectively. Here’s a breakdown of the main items available in the Use Case Analysis window:
  • On the Visualize window, the following canvas are available in the Use Case Analysis report:
    • Summary – Overview of all use cases and attributes.
    • Use Case Details – In-depth details for each use case.
    • Use Case Comparison – Side-by-side comparison of use cases.
    • Attribute Details – Breakdown of attributes within each use case.
The left pane consists of the following options:

Figure 8-73 Left Navigation Pane


Left Navigation Pane

  • Data: Lists the data attributes such as Use Case ID, Name, Entity details, Grain details, Attribute details and Download Type

    Note:

    Click on Add to add Dataset, create Scenario, and Add Calculations.
    .
  • Visualization: Includes tiles, charts, and tables to facilitate data exploration, trend analysis, and issue resolution. It displays the following key metrics:
    • Number of Use Cases (e.g., 9)
    • Number of Entities (e.g., 209)
    • Number of Business Terms (e.g., 2,058)
    • Number of Attributes (e.g., 5,380)
    • Additional charts and insights include:
      • Number of Attributes by Use Case – a word cloud representation highlighting key areas such as Profitability Management, Liquidity Risk Management, Balance Sheet Planning, and Funds Transfer Pricing.
      • Number of Attributes by Grain – a bar chart showing attribute distribution across different grains.
  • Analytics: Enables users to drill down into specific entities, understanding the nature and scope of data inconsistencies.

    Note:

    You can search for relevant options from the search box.

8.2 Summary

The Summary section provides an overview of how to use the tool effectively, including how to assess additional elements required for integration with other financial products.

Figure 8-74 Summary Window


Summary Window

  • Determine the impact of additional financial products.
  • Identify missing elements needed for full integration.
  • Understand table relationships between different applications.
  • Percentage-Wise Requirement AnalysisIdentifies percentage gaps (e.g., a customer needs to bring in the remaining 25%).
  • Helps determine which additional datasets, calculations, or reports are necessary for complete functionality.
  • Balance Sheet & Customer Data IntegrationEvaluates which balance sheet elements must be incorporated.
  • Assesses customer data integration requirements for analytics and compliance.

8.2 Use Case Details

The Use Case Details section provides an overview on how to analyze entity usage across various use cases in financial or business management.

Figure 8-75 Use Case Details


Use Case Details

  • Check the percentage indicator to see what portion of the required data is already available.
  • Review the missing components and determine what additional elements must be integrated.

8.2 Use Case Comparison

This section provides an overview on how to compare attributes across different financial/business use cases. It displays percentage coverage of attributes between the reference use case and comparative use case.

Figure 8-76 Use Case Comparison


Use Case Comparison

  • Reference Use Case: Acts as a benchmark for evaluating other use cases.
  • Comparative Use Case: The use case that is directly compared to the Reference Use Case.
  • Number of Common Attributes: The count of shared Entity.Attributes between the Reference and Comparative Use Cases.
  • Number of Additional Attributes Required: The count of extra Entity.Attributes needed for the Comparative Use Case that are not included in the Reference Use Case.
  • % of Comparative Use Case Attributes Available in Reference: The percentage of attributes from the Comparative Use Case that are present in the Reference Use Case.

Example

The pop-up tooltip (hovered over any entity) provides:
  • Number of attributes in the Reference Use Case (1,210).
  • Number of attributes in the Comparative Use Case (1,881).
  • Number of Common Attributes (194).
  • Number of Additional Attributes Required (1,687).
  • Percentage of Comparative Use Case Attributes available in the Reference Use Case (10%).
  • Insights:
    • High percentages (green areas) indicate a strong overlap of attributes between reference and comparative use cases.
    • Low percentages (red areas) suggest gaps or differences between the datasets.
    • Some cells show 100% coverage (e.g., "Funds Transfer Pricing"), meaning the attributes completely match between the two use cases.

8.2 Attribute Details

Attributes Details report within a Use Case Analysis dashboard is structured as a data table showing attributes related to financial or business processes.

Figure 8-77 Attribute Details


Attribute Details

The interface consists of two main sections:

Data Table (Attributes Details) – Displays key dataset details:
  • Use Case – Business process or scenario
  • Grain – Level of data detail
  • Entity – Business data objects
  • Attribute – Specific data fields (e.g., "Account or Contract Number")
  • Usage Type – Classification of attributes (e.g., "Mandatory" means required)