System of systems and method for software component system design and optimization through testing
First Claim
1. A computer-implemented system for designing software-based components for systems of systems where the systems of systems consist of components that are themselves systems, the computer implemented system comprising:
- multiple software-based components saved in a relational database where the functions of each software component are defined by one or more examples of its operation using a natural language and where each software component is assigned a searchable, unique free-text field such that each of the components have multiple indexed levels in a literal restriction path;
and a processor and memory, the processor and memory controlling retrieval, synthesis, substitution, reuse and modification of the components in the relational database at every level of the multiple levels, including means for defining a new software component, including functional I/O definitions where each component saved in the relational database is associated with one or more tests that serve to map a random input vector to a correct output vector;
where the I/O definitions includes I/O specification vectors for testing the systems of systems;
where the I/O definitions includes I/O specification rules for component construction and including I/O specification vectors which are local to each component and where each component has an input vector holding bin and an output vector holding bin and where the output bins feed the input bins to which they are connected so that a component will only produce outputs for those respective inputs which are found in its respective specification vector.
1 Assignment
0 Petitions
Accused Products
Abstract
In one embodiment, the present invention is a computer-implemented system for designing software-based components for systems of systems including multiple software-based components saved in a relational database where the functions of each software component are defined by one or more examples of its operation using a natural language. Each software component is assigned a searchable, unique free-text field such that each of the components have multiple indexed levels in a literal restriction path. The system further includes means for retrieval, synthesis, substitution, reuse and modification of the components at every level of the multiple levels, including means for defining a new software component.
26 Citations
15 Claims
-
1. A computer-implemented system for designing software-based components for systems of systems where the systems of systems consist of components that are themselves systems, the computer implemented system comprising:
-
multiple software-based components saved in a relational database where the functions of each software component are defined by one or more examples of its operation using a natural language and where each software component is assigned a searchable, unique free-text field such that each of the components have multiple indexed levels in a literal restriction path; and a processor and memory, the processor and memory controlling retrieval, synthesis, substitution, reuse and modification of the components in the relational database at every level of the multiple levels, including means for defining a new software component, including functional I/O definitions where each component saved in the relational database is associated with one or more tests that serve to map a random input vector to a correct output vector;
where the I/O definitions includes I/O specification vectors for testing the systems of systems;
where the I/O definitions includes I/O specification rules for component construction and including I/O specification vectors which are local to each component and where each component has an input vector holding bin and an output vector holding bin and where the output bins feed the input bins to which they are connected so that a component will only produce outputs for those respective inputs which are found in its respective specification vector. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A computer-implemented method for designing software-based components for systems of systems comprising:
-
saving multiple software-based components saved in a relational database where the functions of each software component are defined by one or more examples of its operation using a natural language and where each software component is assigned a searchable, unique free-text field such that each of the components have multiple indexed levels in a literal restriction path; and retrieval, synthesis, substitution, reuse and modification of the components in the relational database at every level of the multiple levels, including defining a new software component, including functional I/O definitions where each component saved in the relational database is associated with one or more tests that serve to map a random input vector to a correct output vector;
where the I/O definitions includes I/O specification vectors for testing the systems of systems;
where the I/O definitions includes I/O specification rules for component construction and including I/O specification vectors which are local to each component and where each component has an input vector holding bin and an output vector holding bin and where the output bins feed the input bins to which they are connected so that a component will only produce outputs for those respective inputs which are found in its respective specification vector.
-
-
15. In a non-transitory computer-readable storage medium represented by a computer-readable programming code, the method comprising the steps of:
-
saving multiple software-based components saved in a relational database where the functions of each software component are defined by one or more examples of its operation using a natural language and where each software component is assigned a searchable, unique free-text field such that each of the components have multiple indexed levels in a literal restriction path; and retrieval, synthesis, substitution, reuse and modification of the components in the relational database at every level of the multiple levels, including defining a new software component, including functional I/O definitions where each component saved in the relational database is associated with one or more tests that serve to map a random input vector to a correct output vector;
where the I/O definitions includes I/O specification vectors for testing the systems of systems;
where the I/O definitions includes I/O specification rules for component construction and including I/O specification vectors which are local to each component and where each component has an input vector holding bin and an output vector holding bin and where the output bins feed the input bins to which they are connected so that a component will only produce outputs for those respective inputs which are found in its respective specification vector.
-
Specification