Business Logic Visualization - Requirements

[AttilaMihaly]

On one of the previous community calls we identified visualization as one of the major areas where we can collaborate. To help the process get started I put together some initial requirements. Feel free to comment on the general format or with any additional requirements:

Objective: To enhance the Morphir platform's visualization capabilities, making complex business logic accessible, interpretable, and actionable for non-technical users. This project aims to bridge the gap between technical and non-technical stakeholders by developing intuitive visualizations that capture the complexity of business logic while remaining user-friendly.

User Stories

1. High-Level Overview of Business Logic

   • As a business analyst, I want to view a high-level overview of the business logic in a visually simplified format so that I can explore the relationships and structures without getting overwhelmed by technical details.
   • As a product manager, I want to see a high-level map of the business logic with key nodes highlighted so that I can quickly identify critical points in the process flow and make decisions on where further exploration is needed.

2. Drill-Down Details While Retaining Context

   • As a business analyst, I want to drill into specific areas of the business logic to view detailed information about a particular node or relationship so that I can understand how individual components fit into the broader context.
   • As a compliance officer, I want to explore different layers of detail without losing sight of where I am within the overall process flow so that I can ensure all steps are in compliance with regulatory standards.

3. Data Flow Exploration from Input to Output (Forward)

   • As a data scientist, I want to follow the data flow forward from a selected input dataset so that I can understand how it transforms through each step of the process and reaches specific outcomes.
   • As a business analyst, I want to visualize the forward flow of data from an input to its outputs so that I can assess the impact of specific input values on final outputs and validate that the data transformations align with business expectations.

4. Data Flow Exploration from Output to Source (Backward)

   • As a compliance auditor, I want to trace data flow backward from a specific output result to its original data sources so that I can verify the integrity and source of the information.
   • As a product manager, I want to track data backward from the result to the contributing inputs so that I can identify which inputs most heavily impact the final output and evaluate the model’s accuracy.

5. Data Flow Tracking with Specific Calculated Values

   • As a data scientist, I want to follow data flows with the actual calculated values highlighted at each stage, both forward and backward, so that I can spot any anomalies and validate intermediate results across the logic chain.
   • As a compliance officer, I want to monitor the calculated values across each stage in the data flow to confirm that calculations meet regulatory requirements and that the transformations maintain data accuracy.

6. Visual Indicators for Investigating Data Issues

   • As a data quality specialist, I want to identify and investigate data issues through visual indicators (e.g., warnings or alerts) in the data processing flow so that I can troubleshoot and resolve inconsistencies or errors effectively.
   • As a business analyst, I want to see visual markers for any data issues that occurred throughout the processing flow so that I can understand how these issues might impact final results and determine the root cause for future mitigation.