How r-zin/airport-runway-scheduler works
File structure
• Top-level:
• BackEnd/ – contains all code.
• BackEnd/Data Struct Logic/ – holds two modules:
◦ DataModel.py – defines your domain entities (Flights, Runways, Constraints).
◦ Scheduling.py – contains the runway‐assignment algorithm.
• There are no config files, API layers, or persistence modules visible; assume in-memory or to-be-added database integration.
Extract README insights
“A Python library that models airport operations and runs a scheduling algorithm to assign flights to runways under given constraints.”
Main components
a. Data Ingestion/Input
• Represents flight requests or schedules (could be a CSV parser, API consumer, or CLI input).
b. Data Model Layer (DataModel.py)
• Domain entities: Flight, Runway, Constraints.
c. Scheduling Engine (Scheduling.py)
• The algorithm that takes models and produces an assignment.
d. Data Store (optional)
e. Output/Reporting
• CLI output, API response, or generated reports.
f. External Systems (optional)
• Air traffic control API, airport operations dashboard, etc.
Interactions and data flow
• Input → Data Model Layer → Scheduling Engine → Data Store (read/write) → Output
Architectural patterns and design principles
• Layered architecture: separate input, domain, algorithm, and persistence.
• Single Responsibility: DataModel.py manages only data structures; Scheduling.py handles only scheduling logic.
• Dependency Injection (future enhancement): inject different scheduler implementations or data stores.
• Extensibility points: ability to plug in new constraint types or scheduling strategies.
Technologies and frameworks
• Python 3.x
• Testing: pytest (not shown, but recommended)
Diagramming recommendations
• Blue for modules (DataModel, Scheduling)
• Green for data stores
• Orange for external interfaces (CLI/API)