How onap/usecase-ui-intent-analysis works
Main Components
• Intent Analysis Application: At the center of the system is the Java application represented by IntentAnalysisApplication.java. This is the entry point into the system.
• API/Controller Layer: Under the “controller” package, you have several REST endpoints (e.g., IntentController, IntentInstanceController, IntentReportController, IMFRegInfoController, etc.). These components handle incoming HTTP requests.
• Service Layer: The “service” and “service/impl” packages encapsulate the business logic (e.g., IntentService, ConditionService, ContextService, etc.).
• Business Modules: There are specialized intent management functions (for business, assurance, delivery, format intent input) located under packages like cllBusinessIntentMgt, cllassuranceIntentmgt, clldeliveryIntentmgt, and formatintentinputMgt. Each of these is further divided into Actuation, Decision, and Knowledge modules.
• Data Access Layer: The “mapper” packages and MyBatis SQL files (under intentanalysis/src/main/resources/mybatis/sql) indicate that persistence is handled via MyBatis. The “bean” models define the data structures going in and out of the data access layer.
• External Adapter Integrations: Multiple adapter packages exist for external incoming and outgoing communications:
• AAI Adapter: Provides integration with the AAI system.
• DCAE/DMAAP Adapter: Manages interactions with DCAE for notifications, DMAAP for messaging.
• Policy Adapter: Connects with Policy services.
• SO (Service Orchestrator) Adapter: Facilitates communication with SO systems.
• Framework & Configurations: Configuration files such as application.yaml, keystore files, and MyBatis mapping resources are critical to understand how the app is configured and deployed.
• Thread/Async Execution: The “ThreadPoolConfig” and related components under the “Thread” package indicate the usage of concurrent processing, which should be represented.
Relationships and Interactions
• Business Logic: From services, indicate the delegation to the appropriate Business Modules (for instance, different intent management functions – Business, Assurance, Delivery, and Format Intent Input) where Actuation, Decision, and Knowledge modules are executed.
Architectural Patterns and Design Principles
• Layered Architecture: The separation into controllers, services, and data access layers is a classic layered (or n-tier) architecture.
• Modular Design: The existence of discrete modules for each intent management function (business, assurance, delivery, etc.) demonstrates modular design.
• Adapter Pattern: The adapter packages describe how external integrations are abstracted behind interface implementations.
• Asynchronous Event Handling: The use of thread pools and event listeners emphasizes asynchronous processing for notification handling.
• Dependency Injection & Configuration: Spring’s conventions are likely in place given the use of application.yaml and SpringContextUtil.