How paed01/bpmn-engine works
Core Components (Main Layer)
• Key modules based on the src/ directory:
• JavaScripts Module (from JavaScripts.js)
• Logger Module (from Logger.js)
• Process Output Handler (from extensions/ProcessOutputDataObject.js)
Input/Output Layer
• Input side:
• BPMN XML Files (.bpmn)
• Configuration Options
• JavaScript Extensions
• Output side:
• Process Execution Results
• Event Emissions
• Debug/Logging Output
Integration Layer
• bpmn-moddle Parser (external dependency)
• Debug Module Integration
• Custom Logger Integration
Extension Points
• Extension mechanism (based on /src/extensions)
• Script Execution Interface
• Timer Management System
Use these specific visualization guidelines:
Component Representation
• Use rectangles for core modules
• Use hexagons for extension points
Specific flows
• BPMN XML parsing flow
• Process execution flow
• Event handling flow
• Extension integration flow
Key Architectural Elements to Highlight:
Modular Structure
• Clear separation between core engine and extensions
• Plugin architecture for JavaScript extensions
• Demonstrate the event-driven nature of the engine
Process Execution
• Workflow from BPMN input to execution
• How different BPMN elements are handled
• Timer and event management
Integration Points
• Debug/logging integration
• Extension points for custom implementations
• External dependency interactions
Specific labels:
Version and Compatibility
• BPMN 2.0 Specification Support
• Node.js Runtime Environment
• TypeScript Type Definitions
Key Features
• Core BPMN Element Support
• Custom Extension Support
• Debug/Logging Capabilities
Maintain these levels of detail:
High-level view
• Overall engine architecture
• Main component interaction
• External interface points
• Individual module responsibilities
• Extension mechanism details
• Error handling paths
Remember to:
• Separation between core and extension functionality
• Version information and supported BPMN element types