How penekhun/baekjoon-java-starter works
Core Components
• Problem Parser Module
• Code Generator Module
• File Generator Module
• Code Runner Module
• User Configuration Module
• Version Checker Module
External Integrations
• Baekjoon Online Judge Website
• IntelliJ IDEA
• GitHub (for version checking)
Input/Interface Layer
• CLI interface (BojStarter.java and Main.java)
• It to the user input flow (problem number)
Core Processing Layer
a. Problem Parser Component:
• BaekjoonProblemParser
• JsoupWebParser
• Problem and TestCase entities
• Connection to Baekjoon website
b. Code Generation Pipeline:
• FileContentGenerator
• JavaCodeGenerator
• JavaTemplate
• Template processing flow
c. File Management:
• JavaSourceCodeFile
• SourceCodeFile
• File system interactions
d. IDE Integration:
• CodeOpenManager
• IdeaCodeOpenManager
• Connection to IntelliJ IDEA
Support Systems
• Version Checker (connecting to GitHub)
• User Configuration System
• Operating System Detection
Visualization Guidelines:
Component Grouping
• Use clear labels for each group
• Clear boundaries between different responsibilities
Special Considerations:
Testing Infrastructure
• A separate section showing test components
• Relationship between production and test code
• How test helpers integrate with the main system
Configuration Flow
• How user configurations are loaded and applied
• Where template customization occurs
• Configuration feedback loop
Error Handling
• Validation and error reporting flows
Level of Detail:
• Problem parsing and test case extraction
• Code generation and template processing
• IDE integration flow
The test automation infrastructure
This system design should reflect the tool's main purpose: automating the setup process for competitive programming problems while maintaining a clean separation of concerns and extensibility for future enhancements.