Processing Module, Integrated Development Environment, Methods, and Program Codes
A processing module is provided. The processing module includes one or more interfaces configured to communicate with at least one integrated development environment and processing circuitry configured to control the one or more interfaces. The processing circuitry is further configured to obtain information about at least one hardware microservice of a processing unit, adapt the information about the at least one hardware microservice to a universal format for informing the at least one IDE about the at least one hardware microservice and provide the at least one IDE access to the at least one hardware microservice.
1 . A processing module, comprising:
one or more interfaces configured to communicate with at least one integrated development environment, IDE; and
processing circuitry configured to control the one or more interfaces and to:
obtain information about at least one hardware microservice of a processing unit;
adapt the information about the at least one hardware microservice to a universal format for informing the at least one IDE about the at least one hardware microservice; and
provide the at least one IDE access to the at least one hardware microservice.
2 . The processing module according to claim 1 , wherein
the processing circuitry is further configured to:
generate a meta data construct comprising the information about the at least one hardware microservice; and
provide the at least one IDE access to the at least one hardware microservice by providing access to the meta data construct.
3 . The processing module according to claim 2 , wherein
the meta data construct exposes a core and/or a nucleus of the microservice for the at least one IDE.
4 . The processing module according to claim 2 , wherein
the meta data construct comprises a primary construct.
5 . The processing module according to claim 4 , wherein
a parent of the primary construct is none.
6 . The processing module according to claim 4 , wherein
the primary construct serves as root class.
7 . The processing module according to claim 4 , wherein
a cardinality of the primary construct is singleton.
8 . The processing module according to claim 4 , wherein
the primary construct comprises information about at least one element of the group of a collection name;
a version;
a physical file name; and
a file format.
9 . The processing module according to claim 4 , wherein
the primary construct comprises at least one secondary construct.
10 . The processing module according to claim 9 , wherein
the primary construct is a parent of the at least one secondary construct.
11 . The processing module according to claim 9 , wherein
a secondary construct of the at least one secondary construct provides information about the at least one hardware microservice.
12 . The processing module according to claim 11 , wherein
a second secondary construct of the at least one secondary provides a definition of a soft and/or hard functionality of the at least one hardware microservice.
13 . The processing module according to claim 12 , wherein
a third secondary construct of the at least one secondary construct provides a collection of functionalities of the at least one hardware microservice.
14 . The processing module according to claim 13 , wherein
a fourth secondary construct of the at least one secondary construct provides a collection of in and/or out parameters for the collection of functionalities.
15 . An integrated development environment, IDE, comprising
one or more interfaces configured to communicate with at least one processing module; and
processing circuitry configured to control the one or more interfaces and to:
receive a meta data construct; and
interpret the meta data construct to access at least one hardware microservice of a processing unit.
16 . The IDE according to claim 15 , wherein
the meta data construct comprises information about a plurality of hardware microservices, wherein at least two hardware microservices of the plurality of hardware microservices have a different interface to communicate with a different IDE.
17 . The IDE according to claim 16 , wherein
the processing circuitry is further configured to interpret a primary construct of the meta data construct of the processing module to access the at least one hardware microservice.
18 . The IDE according to claim 17 , wherein
the processing circuitry is further configured to interpret a second construct to access a functionality of the at least one hardware microservice.
19 . A non-transitory, computer-readable medium comprising a program code that, when the program code is executed on a computer, a processor, or a programmable hardware component, performs obtaining information about at least one hardware microservice of a processing unit, adapting the information about the at least one hardware microservice to an interface of the at least one IDE and providing the at least one IDE access to the at least one hardware microservice.
20 . Data structure, comprising
information about at least one hardware microservice of a processing unit, wherein the information comprises a universal format for informing the at least one IDE about the hardware microservices.