Component-Based Application Development Environment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing and maintaining software applications for various mobile devices is challenging due to restricted resources and the complexity of delivering large data sets, with current solutions either being resource-intensive or requiring multiple platform-specific versions, lacking platform independence and efficiency.

Innovation Solution

A component-based application development environment that uses structured definition languages and modular components for defining processing on device runtime environments, guided by a user interface with predefined steps to select and develop data, message, screen, and workflow components, facilitating platform-independent application development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If native applications are developed for each mobile device platform, then application performance and optimization for specific devices is improved, but platform independence is lost and multiple versions must be developed

Engineering Contradiction:
Improveapplication performanceVSAvoidplatform independence
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The application is divided into separate components: a platform-independent application layer written in Java that handles business logic, and platform-specific device drivers that handle device-specific operations. This segmentation allows the main application to remain portable while still achieving optimized performance on each platform through the device driver layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A device driver acts as an intermediary layer between the Java-based application and the native device platform. The device driver translates platform-independent requests into platform-specific operations, enabling the application to achieve native-like performance without being tied to a specific platform.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If browsers are used to access web services, then cross-platform adaptability is improved, but data persistence and resource efficiency deteriorate due to runtime rendering

Engineering Contradiction:
Improvecross-platform adaptabilityVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Application screens and interfaces are pre-defined using structured definition languages during the development phase, rather than being rendered dynamically at runtime by browsers. This preliminary definition of the user interface allows data to be persisted efficiently and reduces runtime processing requirements, improving resource efficiency while maintaining cross-platform compatibility.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If structured definition languages and component-based architecture are used, then development efficiency and platform independence are improved, but system complexity increases due to multiple components and patterns

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

A unified development environment is provided that handles multiple development tasks through a single interface. The environment supports defining application components, configuring device drivers, and managing deployment all through one system, reducing the complexity burden despite the multi-component architecture.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses configurable parameters and patterns that can be adjusted to match different application requirements. By allowing parameter-based configuration rather than hard-coded structures, the system manages complexity while maintaining flexibility and development efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7657868B2System and method for applying development patterns for component based applications
Publication Date: 2010.02.02 MALIKIE INNOVATIONS LTD
  • US7657868B2 patent drawing
  • US7657868B2 patent drawing
  • US7657868B2 patent drawing

AI summary

A computing device and method for coordinating the development of a client application including application components comprising one or more of at least one of a data component, a message component or a screen component, having corresponding component definitions, or a workflow component comprising a series of instructions. A first development pattern module configured for interaction with a development environment is provided by a computer user interface, the first development pattern module configured for selecting a first pattern from a plurality of patterns based on an application component type central to the client application, the developing definitions of at least one of the application components through interaction with a data model of the development environment providing a persistent state of the application components . . . the first pattern is selected from the group consisting of: a pattern for generating a suitable application based on an available backend data source messaging description; a pattern for developing the suitable application based on an available backend data source messaging description such that the entire application is developed including data components and screen components; a pattern for developing the application based on an existing database schema; a pattern for developing a standard set of data components that model a particular business domain for the application, a screen pattern for coordinating the development of a screen component as the first component; a message pattern for coordinating a development of a message component as the first component; and a script pattern for coordinating a development of a workflow component as a second component as recited in a manner in the independent claims 1 and 21.Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.”