ores Namespace Reference

ORE Studio - Graphical interface and data management for Open Source Risk Engine. More...

Namespaces
namespace	assets
	Asset management module for ORE Studio.
namespace	cli
	Console tool for ORE Studio.
namespace	comms
	Communications library providing client-server connectivity for ORE Studio.
namespace	connections
	Manages server connection bookmarks with hierarchical organization.
namespace	dq
	Data Quality component for tracking and ensuring data integrity.
namespace	eventing
	Event-driven architecture infrastructure for decoupled component communication.
namespace	fpml
	Component for handling Financial Products Markup Language (FPML) operations.
namespace	geo
	Geolocation services module for ORE Studio.
namespace	iam
	Identity and Access Management (IAM) module for ORE Studio.
namespace	logging
	Implements logging infrastructure for ORE Studio.
namespace	ore
	ORE (Open Source Risk Engine) component.
namespace	platform
	Platform abstraction layer for ORE Studio.
namespace	qt
	Qt-based graphical user interface for ORE Studio.
namespace	refdata
	Reference data domain model.
namespace	security
	Shared security primitives for ORE Studio.
namespace	synthetic
	Provides core functionality for creating synthetic DQ data catalogs.
namespace	telemetry
	Telemetry and observability infrastructure for ORE Studio.
namespace	testing
	Testing infrastructure common to all test projects.
namespace	utility
	Foundation utilities used across all ORE Studio components.
namespace	variability
	System variability and configuration management module for ORE Studio.

Detailed Description

ORE Studio - Graphical interface and data management for Open Source Risk Engine.

ORE Studio is a C++20 application providing persistent storage, graphical user interface, and orchestration tools for quantitative risk analysis using the Open Source Risk Engine (ORE). The system is built on a layered architecture with clear separation of concerns.

System Architecture

The system is organized into five architectural layers:

Foundation Layer (ores.utility)

• Core infrastructure: database connectivity, logging, filesystem utilities
• UUID generation, environment variables, string conversion
• No dependencies on other ORE Studio components

Infrastructure Layer (ores.comms, ores.testing)

• Communications: Binary protocol over SSL/TLS for client-server messaging
• Testing: Catch2 integration with database isolation and logging
• Depends on: Foundation

Domain Layer (ores.refdata, ores.iam)

• Risk: ORE domain model with XML/CSV/JSON I/O and temporal versioning
• IAM: User authentication, authorization, and session management
• Depends on: Foundation, Infrastructure

Client Layer (ores.client)

• Deprecated REPL client (functionality moved to ores.comms)
• Depends on: Foundation, Infrastructure, Domain

Application Layer (ores.cli, ores.qt, ores.comms.service)

• CLI: Command-line import/export of currencies in multiple formats
• Qt: Desktop GUI with MDI interface for visual data management
• Service: Multi-client server hosting all backend services
• Depends on: All layers

Component Documentation

For detailed component documentation, see:

• Component class diagrams: projects/COMPONENT/modeling/COMPONENT.puml
• Component headers: projects/COMPONENT/include/COMPONENT/COMPONENT.hpp
• System architecture: projects/modeling/ores.puml

Further Documentation

• Full API documentation: See Doxygen mainpage
• Source code: https://github.com/OreStudio/OreStudio
• Project website: https://orestudio.github.io/OreStudio

Note

This project has no affiliation with Acadia, Open Source Risk Engine, or QuantLib. See Doxygen documentation for full context.