Hyper-Wireframe Data Structure for Multi-Target Software Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing software for multiple targets, such as different devices and platforms, is often hindered by the time-consuming process of determining implementation strategies and managing assets, with last-minute changes complicating documentation and project management.
Innovation Solution
A hyper-wireframe data structure that integrates architecture-level planning with design and coding tasks, allowing for efficient management of assets and project oversight by defining cells representing master screens, their logical relationships, and associating assets with permission data to enable or disable editing features based on target characteristics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software is developed for multiple targets with separate implementation processes, then each target can be optimized specifically, but the development time and complexity increase significantly
Solution Approach 1:
The patent segments the development process into distinct phases: wireframe creation, mockup development, and implementation. Each phase produces artifacts that can be reused across multiple targets. The wireframe data structure is divided into reusable components that can be instantiated for different platforms, reducing redundant work while maintaining target-specific optimizations.
Solution Approach 2:
The patent performs preliminary actions by creating comprehensive wireframes and mockups before actual implementation begins. These preliminary artifacts define the complete structure, layout, and behavior of the application across all targets upfront, allowing implementation to proceed in parallel without rework. Documentation is also prepared in advance rather than at the last minute.
2Loss of information
If comprehensive documentation is prepared during development, then project requirements are met, but last-minute changes make documentation maintenance formidable
Solution Approach 1:
The patent implements feedback mechanisms where the wireframe data structure automatically tracks changes and updates documentation accordingly. When modifications are made to wireframes or mockups, the system detects these changes and propagates them through to implementation specifications and documentation, reducing manual maintenance effort while maintaining completeness.
Solution Approach 2:
The documentation system is designed to be self-updating based on the wireframe data structure. Rather than requiring manual updates whenever changes occur, the system automatically generates and maintains documentation from the structured wireframe data, reducing the burden of documentation management while ensuring completeness.
3Adaptability or versatility
If assets are managed separately for each target platform, then platform-specific requirements are met, but asset management becomes time-consuming and error-prone
Solution Approach 1:
The patent creates a universal asset management system where assets are defined once in the wireframe data structure with platform-specific properties. Each asset can be configured to work across multiple targets with automatic adaptation, eliminating the need to manage separate asset versions for each platform while still meeting specific requirements through conditional logic and platform detection.
Data Source
AI summary
Embodiments include a computer-readable medium embodying program code comprising code for receiving input defining a plurality of cells and a logical relationship between the cells, each cell representing a master screen of an application under development. Additional code for associating an asset with a cell, and code for storing a hyper-wireframe data structure identifying the plurality of cells, the logical relationship between the cells, and the asset may be included. The cells may be part of a hyper-wireframe embodied in a data structure alongside a plurality of assets and a target characteristic value of an intended target of the application under development. An application may determine whether to enable or disable an editing feature of an editing application based on the asset and the target characteristic value. Additionally or alternatively, permission data associated with assets may be used to enable or disable the editing feature.