Systems and methods of a metadata orchestrator augmenting application development

• US 10,521,223 B1
• Filed: 08/22/2017
• Issued: 12/31/2019
• Est. Priority Date: 08/22/2017
• Status: Active Grant

• Current Assignee: Wells Fargo Bank NA (Wells Fargo & Company)
• Original Assignee: Wells Fargo Bank NA (Wells Fargo & Company)
• Inventors: Bogushefsky, III, Joseph Albert, Miller, Christopher Thomas, Wilson, Dennis Wayne
• Primary Examiner(s): Rivera, Anibal
• Application Number:
  US15/683,305
• Time in Patent Office: 861 Days
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 40/177 of tables; using ruled lines
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/73 Program documentation
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• CPC Class Codes: G06F 9/44589 Program code verification, e.g. Java bytecode verification, proof-carrying code high-level semantic checks G06F8/43; testing and debugging software G06F11/36
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

Systems and methods that augment an entity'"'"'s building and deployment of multiple applications using a metadata library component and a metadata orchestrator that controls details of the configurations of data stores, metadata which may include linkage rules of the metadata structures and that leverages the metadata across individual application development and completed application silos are discussed.

Claims

1. A system for building and deploying applications, comprising:

a processor that executes the following computer executable components stored in a memory;

a data store that stores data to be utilized by applications;

a metadata library component that holds details of configurations of the data store, metadata describing data in the data store, and rules concerning linkages of the data store configuration details;

a metadata orchestrator that centralizes control of the metadata library across multiple applications, generates documentation, controls data integrity rules and processes, provides automatic mapping from data structure to established data store links, and prompts a user to supply a pre-determined metadata input in response to a query for metadata related to an application item when no record of the metadata related to the application item exists; and

one or more adaptor components that utilize the metadata library through the metadata orchestrator so that adaptor functions are generated automatically by the metadata orchestrator without writing additional code, wherein the one or more adaptor components are employable to build and deploy the multiple applications,

wherein the documentation is at least one of technical API data, snapshots of data definitions available to users for quality control efforts, and end-user help documentation write up.

2. The system of claim 1, wherein the metadata orchestrator provides for a platform/technology agnostic control such that regardless of the platform or technology interacting with the one or more adaptors, metadata passed through to the metadata orchestrator generates at least one of dynamic screen rendering, documentation generation, and provisioning of program code or interfaces to the one or more adaptors outside of code written by users.

3. The system of claim 2, wherein the metadata orchestrator and metadata library generate and execute test scripts automatically, based on metadata of items being used by developers, wherein the metadata captures descriptions of data access and methods used, and wherein the documentation contains predetermined test data and results.

4. The system of claim 1, wherein the data store configuration details include rules for configuration details and extensible options.

5. The system of claim 1, wherein the metadata orchestrator controls data access and security of data based on metadata library rules.

6. The system of claim 1, wherein the metadata orchestrator and the metadata library components operate on a heterogeneous level, not specific to any single technology.

7. A system for building and deploying applications, comprising:

a processor that executes the following computer executable components stored in a memory;

a metadata orchestrator incorporating details of configurations of data stores, metadata describing data associated with potential data in the data stores, and rules concerning linkages of the data store configuration details that centralizes control of the metadata across multiple applications, generates documentation, controls data integrity rules and processes, provides automatic mapping from data structure to established data store links, and prompts a user to supply a pre-determined metadata input in response to a query for metadata related to an application item when no record of metadata related to the application item exists; and

one or more adaptor components that employ the metadata orchestrator so that application code for adaptor functions is generated automatically by the metadata orchestrator without a user writing additional code, and that adaptor components interact with third party system components to produce the multiple applications,

wherein the documentation is at least one of technical API data, snapshots of data definitions available to users for quality control efforts, and end-user help documentation write up.

8. The system of claim 7, wherein the metadata orchestrator controls code writing for one or more adaptor components based on metadata passed through in the data calls of the adaptor components.

9. The system of claim 8, wherein the one of the one or more adaptor components is a data access adaptor that interacts with a database, and that another of the one or more adaptor components is a user-interface adaptor that interfaces with at least one of a smart phone, computer, laptop, tablet, web browser, or POS terminal.

10. The system of claim 7, wherein the metadata orchestrator employs optimistic locking across applications.

11. The system of claim 7, wherein the metadata orchestrator alleviates manual mapping, updating, changing, or linking data items based on metadata orchestrator calls, absent changes in user coding for user interfaces or other user middle layer code changes.

12. The system of claim 7, wherein the metadata orchestrator and metadata library generate and execute test scripts automatically, based on metadata of items being used by developers, wherein the metadata captures descriptions of data access and methods used.

13. The system of claim 7, wherein the metadata orchestrator dynamically provides for user interface edits, updates to security and backend piping related to one or more associated adaptors based on predetermined metadata structure.

14. A method of augmenting application development comprising:

controlling metadata through a metadata orchestrator, wherein the controlling is centralized across multiple applications;

querying the metadata orchestrator for presence of metadata related to an application item, and

wherein if the query returns no records of metadata related to the application item,

prompting a user to supply a pre-determined metadata input and persisting the input into a metadata library; and

running the metadata orchestrator that controls and interacts with the metadata library and, for application items,

generates code for a predetermined adaptor that enables the predetermined adaptor to perform functions associated with the application item,

generates API documentation, and

deploys the adaptor with the code to a host environment associated with the adaptor for employment by the multiple applications;

wherein the API documentation is at least one of strictly technical API data, snapshots of data definitions available to users for quality control efforts, and an end user help documentation write up, and the API documentation is presented at least on a user device or captured as a file.

15. The method of claim 14, wherein the user prompted population effort entails information being received from the user guided by business rules present in the metadata library.

16. The method of claim 14, wherein the generated code for a predetermined adaptor is dynamically provided code to the adaptor and presents data properly, with no additional user written code required.

17. The method of claim 14, wherein the items captured in the metadata library can be effectively propagated through the metadata orchestrator across a number of disparate applications, thereby leveraging a change or update once completed in one application across applications associated with the metadata.

18. The method of claim 14, comprising a further step of

querying a user whether a pre-determined item is desired to be customized, and

handling extensibility of associated metadata under control of the metadata orchestrator according to pre-determined rules.