Patent application number | Description | Published |
20110271286 | SYSTEM AND METHOD FOR APPLICATION FUNCTION CONSOLIDATION - Systems and methods that facilitate keeping or improving the current/prior level of complexity in a software package, despite enhancement package additions. To keep the current number of business functions (e.g., some software configuration or functionality), new packages may have to consolidate older ones. Consolidating business functions may include dissolving those functions into the core set of functions (e.g., those functions that are “always on”) or to merge them with other business functions (e.g., to be switched on or off as a set). Additionally, if a function is simply not used, and will never be used again, the function may be dissolved completely. Regardless, disruption to the customer should be minimized by any consolidation of functions. Systems and methods identify functions that can be automatically consolidated, and facilitate the consolidation of any remaining functions. | 11-03-2011 |
20120030651 | SYSTEM AND METHOD FOR TEST STRATEGY OPTIMIZATION - A test strategy optimizer for minimizing the impact of software update correctness testing is provided for software having several processes. Each process may have a criticality level associated with it and a test effort level associated with it. An update analyzer may determine what functions are modified and a dependency analyzer may determine what processes are connected to modifications, and thus require testing. User input may specify global test parameters related to test time, test completeness per criticality level, test iterations, etc. The test strategy optimizer will then take the process parameters, process dependencies, and user criteria to calculate the most efficient test procedure and provide information about the same. The test strategy optimizer may also provide adjustment tools, so users may modify parameters, based on the resulting information. | 02-02-2012 |
20120102360 | SYSTEM AND METHOD FOR BUSINESS FUNCTION REVERSIBILITY - The invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status. | 04-26-2012 |
20120102364 | SYSTEM AND METHOD FOR BUSINESS FUNCTION REVERSIBILITY - Embodiments of the present invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status. | 04-26-2012 |
20120137271 | DECOUPLED DEVELOPMENT IN A SHARE DEVELOPMENT SYSTEM - A computer-implemented method of optimizing software components. The method may include receiving a software component including a layered hierarchy of structure packages, main packages, and common packages each including objects, grouping common packages into groups according to pre-determined criteria, encapsulating each group with an encapsulation package, wherein the encapsulation package is one of a structure package and a main package, allowing objects in the encapsulation package to communicate directly by bypassing common packages in the encapsulation package, and eliminating package interfaces of the common packages in the encapsulation package that are solely used for communicating with other common packages in the encapsulation package. | 05-31-2012 |
20120137272 | SYSTEM AND METHOD FOR MODULAR BUSINESS APPLICATIONS - A tailored add-on component for a released software product having internal and released development objects. The released development objects are designed for external use, such as end-user customization. The internal development objects are designed for use within the released software product, with no access from outside components. The tailored add-on component adds a functional application that makes calls to both released and internal objects. Access to internal objects is made while maintaining stability by confining internal object calls to a single adaptation component within the add-on, while also implementing an interface for the objects of the software product that are used by the add-on. The interface includes a function to freeze objects that are in the interface, and a set of automatic test components to identify changes in the objects that are in the interface. | 05-31-2012 |
20120159431 | SYSTEM AND METHOD FOR MODULAR BUSINESS APPLICATIONS - A method of providing tailored add-on applications to an underlying foundational software suite that frequently receives updated versions that would otherwise overwrite changes in the foundational software that are required by the tailored add-on. Instead of functional changes to the foundation, the tailored add-on makes a fairly uniform and simple change in the place of each needed change, by inserting a call to an add-in definition object. The add-in definition object then contains code for performing the functionality needed by the add-on application. The add-in definition object is down-ported to all supported versions of the foundational software. The calls of the add-in definition object are integrated into the foundational software in a way which minimizes conflicts, allows for concurrent implementation while maintaining a clear separation between foundational code and modified code, and minimizes ongoing maintenance development of the add-on application's conflicts with the foundational application. | 06-21-2012 |
20120167034 | SYSTEM AND METHOD FOR MINI-EHP DEVELOPMENT AND DELIVERY - A more tailored and flexible update schedule is provided for large enterprise software development and delivery through mini-releases. Instead of delivering update packages after a development and delivery period, e.g., 18 months, where the update packages include an update release for the entire software package, the software package may be broken down into component parts. Mini-releases may then be issued several times during the same delivery period (e.g., 18 months). Each mini-release may include a small subset of the component parts to be focused on, allowing greater flexibility, without greatly increasing code release efforts (e.g., as required by releasing the whole software suite in an update). | 06-28-2012 |
20130339881 | Database View Systems - Embodiments of methods and systems for database viewing, create a copy of a vendor view in a customer view layer that is present between an interface layer and the database layer. In certain embodiments this copy of the vendor view may contain no customer specific logic, simply serving as a 1:1 projection in the customer view allowing the vendor to track customer access to particular vendor views. According to some embodiments, the copy of the vendor view may be changed to create a modification view. Changes are applied to the modification view only, leaving the original vendor view unchanged with a link to the stored modification copy. This link can be used to adjust the modification copy whenever a hot fix or a new version of the ‘modified’ database content is installed to the customer system. Embodiments may support consumer extensions to the vendor views and/or to the database itself. | 12-19-2013 |
20140013316 | System and method for modular business applications - A method of adding a program module to an installed program code. A data object having an interface for importation of data into and exportation of data out of the data object, the data object further comprising the program module, a switch identifier and a specification of a call to be inserted into the installed code is provided. Insert the call as specified by the specification of the data object into the installed program code and receive a setting for the switch from a user and storing the setting in a database table. | 01-09-2014 |
20140019410 | Using Database Content for Multiple Business Data Systems Connected to One Database - A data model specific to a database schema is received in a database system. The received data model may be applied to a first instance of the database schema to generate a data view of the first database schema. The received data model may be applied to a second instance of the database schema to generate a second data view of the second database schema. | 01-16-2014 |
20140019473 | Database View Modeling Using Existing Data Model - A data model may be designed based views of a pre-existing data model. Metadata associated with the pre-existing data model may be presented to the user to support the user's design effort. The metadata may inform and otherwise guide the user's design choices to reduce the likelihood of inconsistencies between the new data model and the pre-existing data model. The metadata may also be used to identify and warn the user of potential inconsistencies between the new data model and the pre-existing data model. | 01-16-2014 |