How legrin/smpr works
Main components
• Core Application (SMPR): This is the central user interface and orchestrator. It contains main forms (e.g., MainForm, ModulesListForm, LicenseForm) and configuration files. It is responsible for loading and interacting with various decision modules.
• Common Library (Common): Contains shared components (data types, user controls, reflection helpers, serialization, and helper classes) that are used by different modules.
• Modular Decision Methods: There are many subprojects/directories (e.g., ModuleCollectiveBenefitFunctions, ModuleConflictsAndCompromisesMethods, ModuleCooperativeProblemSolving, ModuleDecisionsUnderFuzzyConditionsMethods, ModuleDecisionsUnderRiskAndUncertainityMethods, ModuleExpertProcessingMethods, ModuleFuzzyLogic, ModuleMulticriterionProblemMethods, ModuleNumericalAnalysis, ModuleResults, ModuleVotingMethods, ModuleTests, etc.) that encapsulate individual methods and strategies. Each module implements particular decision-making/optimization algorithms and often includes its own UI forms, business logic, and resource files.
• Supplemental Components:
– KeyGenerator: Likely a utility for generating keys or licenses.
– BuildProcessTemplates: Contains templates for continuous integration and deployment.
– Test Projects: SMPR.Tests and ModuleTests provide unit tests to ensure reliability.
Out relationships and interactions
• The SMPR core interacts with the modular decision methods via a plug-in architecture. Components are likely designed to be loosely coupled so that new modules can be added seamlessly. You might represent this with a “Module Manager” inside SMPR that dynamically loads modules.
• The Common library serves as the shared backbone that provides re-usable classes (like data buffers, matrix and vector operations, serialization, and helper methods) that modules and the core application depend on.
• UI components (forms, user controls) from both SMPR and the modules exchange data (e.g., decision model parameters, matrices, test results) using services provided by the Common layer.
• Test projects and build templates exist outside the main runtime flow, ensuring that the architecture supports continuous integration and systematic testing.
Architectural patterns and design principles
• Modular / Plug-In Architecture: Modules encapsulate distinct decision methods that can be loaded and run independently.
• Separation of Concerns: The UI (SMPR forms), business logic (modules and methods), and shared utilities (Common) are clearly separated.
• Reusability: Shared data types and utility functions in the Common directory are used across modules.
• Possibly some Model-View-Controller (MVC) or similar pattern is implicitly used as many modules have separate views, controllers (logic forms), and underlying data classes.
Relevant technologies
• .NET Framework – The project is built with C# and Windows Forms.
• Visual Studio Build and Deployment (build process templates, solution files, project files).
• Localization resources in multiple languages (files like About.en-US.resx, About.ru-RU.resx, etc.)