Data Driven Software Development Using Value and Timing Attributes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computing system software development lacks a standardized approach, leading to inconsistencies and inefficiencies due to varying methods among developers, and there is a lack of clear criteria for measuring software safety, resulting in ambiguous and incomplete specifications and inefficient safety mechanisms.
Innovation Solution
A method is introduced that focuses on two systematic attributes: Data Value and Data Timing, using Input Data, Middle Data, and Output Data, with defined calculations and safety mechanisms to ensure accurate and efficient system development by detecting deviations in these attributes and preventing impacted systems from outputting deviated data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If developers use different experience-based methods to construct software, then development flexibility is maintained, but software quality consistency and development efficiency deteriorate
Solution Approach 1:
The patent changes the fundamental parameters of software construction by defining only two systematic attributes (Data Value and Data Timing) that all software must satisfy. This parameter-based approach replaces diverse developer methodologies with a unified framework, ensuring consistent software quality while maintaining adaptability through the flexibility of defining specific data attributes for different systems.
Solution Approach 2:
The patent creates a universal software construction framework that applies to all computing systems regardless of their specific function. The two-attribute model (Data Value and Data Timing) serves multiple purposes: it defines system behavior, enables safety verification, and provides a common language for development across different teams and projects, thereby improving quality consistency without requiring complex project-specific methodologies.
2Measurement precision
If text-based specification tools are used, then documentation flexibility is maintained, but specification accuracy and completeness deteriorate
Solution Approach 1:
The patent substitutes text-based specification mechanics with a mathematical/formal attribute-based system. Instead of using natural language descriptions that are prone to ambiguity, the invention defines precise mathematical relationships between Data Value and Data Timing attributes. This substitution improves specification accuracy while the standardized attribute framework actually simplifies the creation process by providing a repeatable template.
3Loss of information
If notation-based specification tools are used, then visual representation is improved, but system functionality coverage and relationship clarity deteriorate
Solution Approach 1:
The patent extracts the essential functionality description from complex notation systems by focusing only on the two critical attributes: Data Value and Data Timing. This extraction eliminates unnecessary notational complexity while preserving complete system functionality coverage, as these two attributes fundamentally define any computing system's behavior from an external perspective.
4Measurement precision
If safety mechanisms are developed using high-level activities, then development speed is maintained, but safety measurement accuracy and adjudgment reliability deteriorate
Solution Approach 1:
The patent introduces feedback mechanisms through systematic verification of Data Value and Data Timing attributes. Safety is measured by checking whether actual system behavior matches the defined attribute relationships. This feedback loop provides accurate safety measurement while maintaining development efficiency because the verification process follows a standardized, automated-friendly framework rather than requiring complex manual adjudgment.
Data Source
AI summary
The present invention is based on the data value and data timing attributes realizations and provides an explicitly defined definite or fixed method for constructing a computing system software consisting of (1). A definite system development method; (2). A definite safety relevant system development method in the furthermore manner; (3) the specific and definite criteria to measure the software and the safety. Said method is based on the exclusive disclosure that is: computing system functionalities can be fully represented by the data comprising Input Data, Middle Data and Output Data, in which the Output Data represent fully the system functionalities under the input data from the system black-box point of view, the Middle Data represent fully the middle functionalities that are transporting and transforming the Input Data to the Output Data. In the system, each data has two and only two systematic attributes: data value and data timing attributes. So, the software development goal is to derive the two systematic attributes for each required output data correctly, and the safety development goal is to make sure that the two attributes of each output data are derived correctly and reliably. And such developments will be complete, consistent, accurate and efficient because all required information and development activities are covered, and any other information and other activities are not included.