Use Cases for Viewing and Data Integration¶

1. As a user:¶

View Supercoach Fantasy Player Points Predictions¶

Title: View live fantasy points predictions for Supercoach players during the game.
Goal: Engage with live updates of fantasy player points predictions.
Preconditions: The user has logged into the platform.
Flow of Events: 1. User selects a live game from the available sporting events. 2. The system retrieves and displays the current fantasy player points predictions. 3. As the game progresses, the system dynamically updates the player points predictions. 4. The user can track player performance in real-time.
Postconditions: The user is continuously updated with the latest fantasy player points predictions during the game.

View List of Sporting Events¶

Title: View a list of upcoming and live sporting events for a specific sport.
Goal: Provide users with a comprehensive list of sporting events for easy navigation.
Preconditions: The user has access to the platform.
Flow of Events: 1. User selects a sport (e.g., Rugby, Football). 2. The system displays a list of all sporting events for that sport. 3. The user selects a specific sporting event to view detailed information.
Postconditions: The user can access a full list of sporting events for their chosen sport.

View List of Competitions for a Sport¶

Title: View a list of all competitions for a given sport.
Goal: Provide the user with a list of all competitions related to a selected sport.
Preconditions: The user has selected a sport.
Flow of Events: 1. The user selects a sport. 2. The system retrieves and displays all available competitions for that sport. 3. The user can select a competition for further details.
Postconditions: The user can see all competitions associated with the selected sport.

View List of Seasons for a Competition¶

Title: View a list of all seasons for a selected competition.
Goal: Enable users to view available seasons for a specific competition.
Preconditions: The user has selected a competition.
Flow of Events: 1. The user selects a competition. 2. The system retrieves and displays the list of seasons for that competition. 3. The user can select a season to view more details.
Postconditions: The user can see all seasons related to the selected competition.

View List of Players¶

Title: View a list of players associated with a team or competition.
Goal: Display the players within a team or competition.
Preconditions: The user has selected a team or competition.
Flow of Events: 1. The user selects a team or competition. 2. The system displays a list of players in that team or competition. 3. The user can interact with player information.
Postconditions: The user can see and explore a list of players.

View List of Teams¶

Title: View a list of teams for a selected competition or sport.
Goal: Allow users to view a list of teams associated with a competition or sport.
Preconditions: The user has selected a sport or competition.
Flow of Events: 1. The user selects a sport or competition. 2. The system retrieves and displays the teams participating. 3. The user selects a team for more details.
Postconditions: The user can view teams associated with the selected sport or competition.

2. As a content administrator:¶

Import Data from SuperCoach and FoxSports to Luckbox¶

Title: Import player and sporting event data from SuperCoach and FoxSports to Luckbox.
Goal: Enable the system to import data from external providers (SuperCoach, FoxSports) and map it to the internal Luckbox data model, ensuring data consistency.
Preconditions:
- SuperCoach and FoxSports data sources are available.
- Content administrator has appropriate permissions to run data imports.
- The internal system is ready to process incoming data and map it accordingly.

Flow of Events:
1. SuperCoach and FoxSports data is ingested by the system.
2. The SuperCoach SportingEvent Mapper and FoxSports SportingEvent Mapper convert the data to internal CreateSportingEventCommand.
3. The system processes the commands and raises the appropriate event (SportingEventCreatedEvent).
4. Internal mappings between Luckbox and external sources are created or updated.

Postconditions:
- The system is updated with new player statistics, sporting events, and other relevant data.
- Events are triggered to update the internal system.

Map SuperCoach SportingEvent to Internal SportingEvent Command¶

Title: Map SuperCoach sporting event data to the internal sporting event command.
Goal: Convert and map external SuperCoach sporting event data into the internal system's sporting event creation command.
Preconditions: SuperCoach sporting event data is ingested by the system.
Flow:
1. SuperCoach sporting event data is received.
2. The SuperCoach SportingEvent Mapper converts the data to an internal CreateSportingEventCommand.
3. The system processes the command and raises the appropriate event (SportingEventCreatedEvent).
Postconditions:
- The internal sporting event is created, and the data is synchronized with Luckbox.

Map FoxSports SportingEvent to Internal SportingEvent Command¶

Title: Map FoxSports sporting event data to the internal sporting event command.
Goal: Convert and map external FoxSports sporting event data into the internal system's sporting event creation command.
Preconditions: FoxSports sporting event data is ingested by the system.
Flow:
1. FoxSports sporting event data is received.
2. The FoxSports SportingEvent Mapper converts the data to an internal CreateSportingEventCommand.
3. The system processes the command and raises the appropriate event (SportingEventCreatedEvent).
Postconditions:
- The internal sporting event is created, and the data is synchronized with Luckbox.

Map SuperCoach Player Data to Internal Player Command¶

Title: Map SuperCoach player data to the internal player command.
Goal: Convert and map external SuperCoach player data into the internal system’s player creation command.
Preconditions: SuperCoach player data is ingested by the system.
Flow:
1. SuperCoach player data is received.
2. The SuperCoach Player Mapper converts the data to an internal CreatePlayerCommand.
3. The system processes the command and raises the appropriate event (PlayerCreatedEvent).
Postconditions:
- The internal player is created, and the data is synchronized with Luckbox.

Map FoxSports Player Data to Internal Player Command¶

Title: Map FoxSports player data to the internal player command.
Goal: Convert and map external FoxSports player data into the internal system’s player creation command.
Preconditions: FoxSports player data is ingested by the system.
Flow:
1. FoxSports player data is received.
2. The FoxSports Player Mapper converts the data to an internal CreatePlayerCommand.
3. The system processes the command and raises the appropriate event (PlayerCreatedEvent).
Postconditions:
- The internal player is created, and the data is synchronized with Luckbox.

Map SuperCoach Team Data to Internal Team Command¶

Title: Map SuperCoach team data to the internal team command.
Goal: Convert and map external SuperCoach team data into the internal system’s team creation command.
Preconditions: SuperCoach team data is ingested by the system.
Flow:
1. SuperCoach team data is received.
2. The SuperCoach Team Mapper converts the data to an internal CreateTeamCommand.
3. The system processes the command and raises the appropriate event (TeamCreatedEvent).
Postconditions:
- The internal team is created, and the data is synchronized with Luckbox.

Map FoxSports Team Data to Internal Team Command¶

Title: Map FoxSports team data to the internal team command.
Goal: Convert and map external FoxSports team data into the internal system’s team creation command.
Preconditions: FoxSports team data is ingested by the system.
Flow:
1. FoxSports team data is received.
2. The FoxSports Team Mapper converts the data to an internal CreateTeamCommand.
3. The system processes the command and raises the appropriate event (TeamCreatedEvent).
Postconditions:
- The internal team is created, and the data is synchronized with Luckbox.

Map SportingEvent Data from Luckbox to External Source (SuperCoach, FoxSports)¶

Title: Map internal sporting event data from Luckbox to an external source like SuperCoach or FoxSports.
Goal: Convert and map internal sporting event data from Luckbox to external formats for data export.
Preconditions: Internal sporting event data is available in the system.
Flow:
1. Internal sporting event data is queried from the Luckbox system.
2. The Luckbox-to-External SportingEvent Mapper converts it to the appropriate format for SuperCoach or FoxSports.
3. The data is exported to the relevant external system.
Postconditions:
- SportingEvent data is successfully synchronized to the external sources.

Map Player Data from Luckbox to External Source (SuperCoach, FoxSports)¶

Title: Map internal player data from Luckbox to an external source like SuperCoach or FoxSports.
Goal: Convert and map internal player data from Luckbox to external formats for data export.
Preconditions: Internal player data is available in the system.
Flow:
1. Internal player data is queried from the Luckbox system.
2. The Luckbox-to-External Player Mapper converts it to the appropriate format for SuperCoach or FoxSports.
3. The data is exported to the relevant external system.
Postconditions:
- Player data is successfully synchronized to the external sources.

Reconcile Data from Multiple Sources¶

Title: Reconcile discrepancies in data from multiple sources (SuperCoach, FoxSports, Luckbox).
Goal: Ensure that data discrepancies between Luckbox, SuperCoach, and FoxSports are identified and reconciled, maintaining accurate and consistent data.
Preconditions: Data from SuperCoach, FoxSports, and Luckbox is ingested and mapped.
Flow:
1. Content administrator reviews flagged discrepancies in data from the sources.
2. The system displays mismatched data points for the administrator to review (e.g., different points for the same player across sources).
3. The content administrator selects the correct data point (or performs an update to reconcile the data).
4. The system updates the data accordingly and triggers reconciliation events.
Postconditions:
- Data discrepancies are resolved, and the system maintains accurate data for all sources.
- Reconciled data is updated in the system.

Conclusion¶

These use cases define how external data (from SuperCoach, FoxSports) can be mapped into the internal Luckbox system. The use cases also cover the processes involved in reconciling data, ensuring consistency, and synchronizing data across multiple sources.