Unified Code Base for Airline Check-in Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The airline and other industries face inefficiencies due to the proliferation of individual code bases for similar functions like check-in and ticketing, leading to complex support, maintenance, and certification cycles, as well as difficulties in enhancing and integrating systems across different channels and airlines.
Innovation Solution
A software development method using a common code base with a declarative data description language, a device abstraction layer, and a graphical tool to model workflows, allowing developers to assemble applications without coding, and enabling backwards compatibility and reusability of system components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If individual code bases are developed by each airline and airport to handle check-in functions, then specific business requirements and rules can be met, but system complexity and maintenance difficulty increase significantly
Solution Approach 1:
The patent implements a universal code base that can serve multiple airlines and airports through configuration rather than customization. The system uses a common core with configurable parameters that allow different business requirements to be met without creating separate code bases. This resolves the contradiction by making one system serve multiple specific purposes through adaptability mechanisms like configuration files, parameter settings, and modular components that can be tailored to different clients' needs.
2Adaptability or versatility
If separate code bases are maintained for different check-in modes, then specific channel requirements can be satisfied, but support and maintenance cycles become prolonged
Solution Approach 1:
The patent segments the system into a stable core code base and configurable overlay layers. The core remains unchanged across different check-in modes (self-service, agent-assisted, mobile), while specific channel requirements are handled through configuration parameters and modular plugins. This segmentation allows rapid deployment and certification because the core is already certified, and only configuration changes are needed for different channels, dramatically reducing maintenance and certification cycles.
3Adaptability or versatility
If original developers must write changes to existing code bases, then system functionality can be enhanced, but development time and costs increase
Solution Approach 1:
The patent enables clients to perform self-service enhancements by providing tools and mechanisms for configuration-based customization. Instead of requiring original developers to write code changes, the system allows clients to modify behavior through configuration files, parameter adjustments, and visual configuration interfaces. This self-service capability dramatically reduces development time and costs while maintaining the ability to enhance system functionality for different business needs.
4Adaptability or versatility
If multiple airlines each have their own code bases, then individual business rules can be implemented, but integration and collaboration between airlines become difficult
Solution Approach 1:
The patent merges multiple individual code bases into a single unified code base that serves all airlines. The unified system maintains the ability to implement individual business rules through configuration parameters specific to each airline, while eliminating integration complexity by having all systems communicate through a common interface and shared core functionality. This merging approach allows multiple airlines to collaborate more easily while preserving their individual operational requirements.
Data Source
AI summary
A software development tool for use with external systems and services uses a common code base and defines all data and messages using XML Schema System components are defined which include a device abstraction layer which handles interactions between the application and devices. A host abstraction layer handles interactions between a host system and the application. A graphical tool models the work flow of the application and includes screens and services defined by Schema. The application is assembled using the graphical tool, declarative XML rules and customizations of system components without the user having to generate any coding.