Systems and methods for computer assisted database change documentation
AssigneeWalmart Apollo, LLC
InventorsDaniel Bryan Austin, Chris Spicer
Life of this patent
Estimating the term…
Abstract
Systems and methods for generating database schema change documents based on a data model and model changes indicated by a user. Information items related to one or more objects defined in the data model are received, and user input regarding changed objects is requested. In embodiments, changes are evaluated against configurable design criteria. One or more human and/or machine readable database schema change documents, and are stored in memory. Design criteria and change documents can vary based on a target database platform in embodiments.
Claims18
A system for generating database schema change documents based on one or more changes in a data model, the system comprising:
- a non-volatile memory;
- a data model interpreter configured to receive information items related to one or more objects defined in the data model;
- a user interface configured to:
- display at least one of the one or more information items to a user,
- receive an indication of one or more changed objects from the user, and
- receive one or more documentation inputs from the user, each documentation input associated with at least one changed object;
- a validator configured to apply at least one rule defined by one or more design criteria to be met by the data model to each of the one or more changed objects and, in response to at least one changed object not satisfying the at least one rule, present a validation region including all changed objects not satisfying the at least one rule for the user to review prior to creation of one or more database schema change documents and prior to implementation of the data model on a target database, the validation region allowing the user to choose between deactivating the one or more design criteria or revising the one or more changed objects such that the at least one rule becomes satisfied;
- and
- a documentation generator configured to, in response to the at least one change object satisfying the at least one rule or the unsatisfied data model criteria being deactivated, create, and store in the memory, the one or more database schema change documents, each database schema change document including one or more change requests, and each change request associated with at least one of the one or more changed objects and including each of the one or more documentation inputs associated with each of the one or more associated changed objects.
A method for generating database schema change documents based on one or more changes in a data model, the method comprising:
- receiving one or more information items related to one or more objects defined in the data model;
- presenting a user interface and displaying at least one of the one or more information items to a user through the user interface;
- receiving an indication of one or more changed objects from the user;
- receiving one or more documentation inputs from the user, each documentation input associated with at least one changed object;
- applying at least one rule defined by one or more design criteria to be met by the data model to each of the one or more changed objects and, in response to at least one changed object not satisfying the at least one rule, presenting a validation region including all changed objects not satisfying the at least one rule for the user to review prior to creation of one or more database schema change documents and prior to implementation of the data model on a target database, the validation region allowing the user to choose between deactivating the one or more design criteria or revising the one or more changed objects such that the at least one rule becomes satisfied;
- and
- creating, in response to the at least one change object satisfying the at least one rule or the unsatisfied data model criteria being deactivated, one or more database schema change documents, each database schema change document including one or more change requests, and each change request associated with at least one of the one or more changed objects and including each of the one or more documentation inputs associated with each of the one or more associated changed objects;
- and
- storing the database schema changes in a non-volatile memory.
Dependencies are inferred from the claim text.