How eidu/integration-library works
Main Components
a. Core Library Components:
• Three main class components within:
• RunLearningUnitRequest
• RunLearningUnitResult
• ResultItem
b. Integration Points:
• An "EIDU Platform" cloud/external system
• A "Host Android App" component
c. Build System Layer:
• A Gradle build system component
• Maven Central publishing pathway
Relationship Flows
• Host App → Integration Library (implementation dependency)
• Integration Library ↔ EIDU Platform (data exchange)
• Build System → Maven Central (deployment)
Component Details
• Rectangle with rounded corners for the main library module (blue)
• Rectangles for internal classes (light blue)
• Hexagon for Host Android App (green)
Technical Specifications
Annotations showing:
• Java as the implementation language
• Android platform compatibility
• MIT License indicator
• Maven Central distribution channel
Testing Layer
A testing component that includes:
• Unit Tests (RunLearningUnitRequestTest, RunLearningUnitResultTest)
• Android Instrumentation Tests (ResultItemTest)
Build/CI Pipeline
A small section showing:
• GitHub Actions workflows
• Gradle build process
• Publication process
Specific Considerations:
Important Elements to Highlight
• The library's role as a bridge between host apps and EIDU platform
• The simplicity of the integration process
• The testing coverage
Notes Section
A notes section mentioning:
• Version compatibility
• License information
• Support contact information
Remember to use standard UML notation where appropriate but prioritize clarity and understanding over strict UML compliance, as this is an architectural overview rather than a detailed technical specification.