Reusable Architecture Syntax for Computer System Manufacturing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The traditional method of creating computer systems requires manual mapping of high-level design specifications to individual commands, leading to inefficiencies and loss of information, especially when transitioning between technologies, as engineers must recreate mappings and much initial implementation information is not retained for subsequent designs.
Innovation Solution
A method and system for generating a computer architecture representation in reusable syntax and grammar, using language definitions for technical, business, and supplementary details, which allows for parsing, semantic grammar analysis, and dynamic compilation to produce architectural specifications and documents, enabling rapid generation of different architectures based on various inputs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual mapping of high-level design specifications to individual commands is used, then implementation can be performed with existing tools and knowledge, but significant time is consumed and information is lost during transitions
Solution Approach 1:
The patent creates a virtual machine image that copies the entire manual mapping process results into a reusable template. This virtual machine contains all the command mappings, configurations, and implementations derived from the high-level design, allowing rapid deployment without manual recreation of mappings.
Solution Approach 2:
The system performs preliminary action by pre-mapping all high-level design specifications to individual commands during the initial virtual machine creation. This preliminary mapping is stored in the virtual machine image, so when the same architecture needs to be deployed again, the mappings are already prepared and can be instantly applied without manual intervention.
2Adaptability or versatility
If manual mapping and execution of commands is performed for each system deployment, then specific technology requirements can be met, but the process cannot be efficiently reused when transitioning between technologies
Solution Approach 1:
The virtual machine image serves as a universal template that can be deployed across different technology platforms. The same virtual machine image can be instantiated multiple times to create different physical systems, and the system can adapt to different technology requirements by modifying the high-level design specifications while maintaining the same underlying mapping framework.
Solution Approach 2:
When transitioning between technologies, instead of manually recreating mappings, the system copies the virtual machine image and modifies it according to the new technology requirements. This copying approach preserves all the mapping logic and implementation details, allowing efficient transition while maintaining productivity.
3Manufacturing precision
If engineers manually create bills of materials and implementation instructions from high-level designs, then detailed implementation can be achieved, but much initial information is not retained for subsequent designs
Solution Approach 1:
The virtual machine image copies and stores all implementation information including bills of materials, command mappings, and configuration details. This information is preserved within the virtual machine image and can be extracted and reused for subsequent designs, preventing information loss while maintaining implementation precision.
Solution Approach 2:
The system performs preliminary action by capturing and storing all implementation details during the initial virtual machine creation process. This preliminary information capture ensures that bills of materials, command mappings, and other implementation information are retained and available for future reference and reuse.
Data Source
AI summary
Techniques and a system for creating a vendor independent computer language and compiling the language into an architecture specification language allowing for taking a source data stream (file, WSDL, XML) and passing thru a language parser, populating a storage medium with a plurality of technical inputs and vendor technical specifications for generic technologies and probable technologies required for desired architectures generated by the language parser, and optimizing the inputs and creating relationships between technologies and groups of technologies and storing results in the storage medium.