Patent Grant
9830142
Computer systems are currently in wide use. Some such systems are customized (some significantly) before they are deployed at an end user's site. Such systems often also have updates which can be installed.
By way of example, some such computer systems include business systems, such as customer relations management (CRM) systems, enterprise resource planning (ERP) systems, line-of-business (LOB) systems, etc. In these types of systems, a general business system is first purchased by a user or customer, and the user or customer often makes customizations, extensions or other modifications to that general business system, in order to obtain their own customized deployment.
Such systems often have updates published for them. The updates can include new releases, as well as bug fixes. For instance, when new releases of the business system are generated, they are often followed by a number of bug fixes for problems that were not fixed prior to release. The fixes are normally released, piecemeal, as they are generated. Periodically, however, a cumulative update package is released which includes all of the fixes generated, to that point. This may, for example, include hundreds or even thousands of fixes.
When customers wish to apply the fixes from the cumulative update to their own customer product, they have conventionally had to either apply all of the fixes in the cumulative update, or none of them. There has not been any ability to pick and choose which specific customizations to apply, from a cumulative update.
Further, a user may apply multiple different fixes to their product over time. It can be difficult for the user to know the comprehensive update status of the product. This is not tracked or stored.
Also, in such business systems, it is not uncommon for users to be operating in multiple different environments. For instance, a user may be a developer that is operating in a development environment, and a test environment, or multiple development and test environments. Similarly, where a product has been deployed, there may be a production environment as well, among other environments.
It is currently difficult for a user to decide whether to apply any updates, and if so, which ones. If the user operates in multiple environments, the user may need to apply the selected updates in all environments. This is time consuming. Also, the user is unable to determine how the updates will affect the underlying business processes and objects within the business system, before they are applied. Further, if the user chooses to apply all of the updates in the cumulative update, there are often conflicts. That is, a user's customization may conflict with an applied update. It can take the user a great deal of time and effort to resolve such conflicts.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
An update installer generates an update display for a user that allows the user to select updates be applied to a first environment. An export display allows the user to export the selected updates so they can be saved for installation in another environment.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
Customer business system 101 illustratively includes processor 102, data store 104, user interface component 105, update installer component 106, conflict resolution component 119 and business process component 121. Data store 104, itself, illustratively includes data 108, applications 110, business processes 112, workflows 114, and other items 116. In one embodiment, applications 110 illustratively include the business logic used to run business processes 112 and workflows 114 in business system 101. Applications 110 illustratively operate on data 108, which can include entities that represent items in the business system 101. Thus, applications 110 can include a general ledger application, inventory application, applications that allow a user to track business opportunities, track sales or production in a business system, or a wide variety of other business applications. The entities, for instance, include customer entities that represent customers, opportunity entities that represent business opportunities, inventory entities that represent inventory items, quote and proposal entities that represent quotes and proposals, etc. The data 108 can include a wide variety of other entities and data, and those mentioned above are mentioned for the sake of example only. User 114 (or other users) can illustratively access customer business system 101 in order to perform activities, tasks, workflows, etc. that are done in carrying out the business of the organization that deploys business system 101.
Life cycle system 200 illustratively includes project information 206, environment information 208 (which can include information representative of a set of business processes 209 that are used by the user in customer business system 101), update state tracking information 210, services 202-204, update information 203, update recommendation service 212, impact analysis information 211, code merge information 213 and report generator service 214. Services 202-204 can be used by various persons in order to identify, track and resolve issues that arise during various life cycle stages of a project (e.g., from presale to implementation and maintenance). For instance, as business system 101 is designed, built, deployed and tested, the various services 202-204 illustratively allow the developers as well as the user organization to track issues which arise, and to determine whether the user's expectations are met when the final instance of business system 101 is deployed at the organization.
User 114 can illustratively log in to life cycle system 200 to view the various information provided by services 202-204. In one embodiment, for instance, services 202-204 include a service that allows a user to identify the needs of an organization and the basic functionality that is provided with a business system and generate a fit gap list that identifies the functionality or customizations that need to be made, to the business system, in order to meet the needs of the customer that is deploying the business system. The services also illustratively include a diagnostic service that allows life cycle system 200 to identify the particular environmental information that defines the environment of the deployed business system 101. For instance, the environmental data may identify the version number and identity of the operating system, the version number of the base system 101, the particular fixes that have been applied to system 101, the version number of the database and other application platforms used by business system 101, whether business system 101 is in a production environment, a test environment, a user acceptance testing environment, etc., and a wide variety of other information.
User 114 can access life cycle system 200 to view project information 206 that defines the user's projects, environmental information 208 that includes the environmental data mentioned above, as well as an indication of the set of businesses processes 209 that are run on business system 101, update tracking information 210 that identifies the update state of business system 101 (for example, which updates have been applied and when), update information 203 that indicates available updates or detailed information corresponding to updates that have been installed, update recommendation service 212 that recommends updates for business system 101 based upon the information gathered from business system 101, impact analysis information 211 that shows the affect that selected updates have on business system 101 (such as the business processes 112, the objects, layers, etc.), code merge information 213 that shows the affect of automatic conflict resolution. and report generator service 214 that can be used to generate various reports that are discussed in greater detail below.
Before describing the overall operation of architecture 100 in more detail, a brief overview will be provided to enhance understanding. Cumulative updates 120 may intermittently become available to update customer business system 101, and specifically the applications 110 or information in data store 104, in system 101. The cumulative updates 120 may include hot fixes or a variety of other updates as well. In one embodiment, update installer component 106 uses user interface component 105, to generate user interface displays 115 that allow user 114 to select the various updates that are desired, and to also see an impact analysis which indicates the impact (e.g., in terms of potential conflicts) of those updates on the user's business system 101. Update installer component 106 also illustratively allows user 114 to search for various updates based on subject matter or otherwise, and to view the impact on the business processes 112, as well as to save selected updates for replay (or application) in other environments. Update installer component 106 also illustratively installs the selected updates, and can automatically resolve conflicts, when commanded to. The update state of customer business system 101 is illustratively uploaded to life cycle system 200 as update state tracking information 210. Thus, user 114 can also log on to life cycle system 200 in order to view the update state tracking information 210 and to receive recommended updates from update recommendation service 212, and to view various other information and reports as described in greater detail below.
In order to begin installing updates, user 114 first launches update installer component 106. This is indicated by block 250 in
Referring again to the flow diagram of
When the user does this, and actuates the next actuator, update installer component 106 illustratively generates a user interface display (such as display 298 shown in
By way of example, if user 114 actuates mechanism 302, update installer component 106 illustratively generates a display (such as display 304 shown in
Once the user has identified the particular update packages that are to be applied, and the particular environment where they are to be applied, update installer component 106 illustratively generates a user interface display, such as display 312 shown in
For instance, the user can choose an express installation in which all updates in the selected update package are be applied. This can be done, for instance, by actuating user input mechanism 314. Selecting all updates is indicated by block 313 in the flow diagram of
However, it may be that user 114 has already selected a set of updates for application to a different environment (other than the one that was chosen as described above). In that case, user 114 may have saved those selected updates as a list that can be applied to other environments. Thus, if the user actuates user input mechanism 324, the user can input the update list for application to the newly selected environment. In one embodiment, when the user actuates mechanism 324, “browse” button 326 becomes active and allows the user to enter a file in box 328 for importing into the update installation process. Importing a saved list of updates is indicated by block 330 in the flow diagram of
It is now assumed that the user has actuated user input mechanism 320 to select individual updates to be applied. In response to the user selecting the advanced installation and logging into life cycle system 200, update installer component 106 illustratively generates a user interface display, such as display 332 in
Display 332 also illustratively includes a set of filter user input mechanisms 336. Each of the filter user input mechanism 336 illustratively allow the user to select one or more items, upon which to filter the applicable updates. In the example shown, mechanisms 336 include a “module” user input mechanism that is shown as a drop down menu. The module mechanism allows the user to filter the applicable updates by module. In the embodiment shown in
The “license code” filter mechanism 336 allows the user to filter the applicable updates by license code elements. Such elements can include, for example, an electronic banking code element, the general ledger code element (or application), etc.
The “country context” filter mechanism 336 allows the user to filter the applicable updates by country context. For instance, systems that are deployed in one country may not be interested in some updates that were generated, in particular, for a system in another country. Thus, the applicable updates can be filtered by country context.
The “business process” filter mechanism 336 allows the user to filter the applicable updates based on the business processes to which they apply. By way of example, in one embodiment, life cycle system 200 includes a service 202-204 that uses a business process modeler to generate a model of the business processes in a given customer business system 101. Thus, the set of business processes 209 for the individual customer business system 101 is stored so that the user can view the various business processes in system 101. Update installer component 106 illustratively accesses the set of business processes 209 from life cycle system 200 and displays those processes in the user input mechanism. Thus, the user can select the particular business processes in business system 101 to filter applicable updates.
In the embodiment shown in
Display 332 also illustratively includes a results display pane 340. Display pane 340 illustratively displays information corresponding to the applicable updates that are identified by update search component 130 in update installer component 106 based upon all of the user selections, filters, and search terms. The returned results (or results update set) 342 can be grouped in a variety of different ways. For instance, the grouping user input mechanism 344 allows the user to select one of a variety of different sets of sort criteria for sorting the returned update results displayed in pane 340.
When the user selects or focuses on a non-patent node in pane 340 (such as on node 350) then details tab 362 displays details corresponding to the selected non-parent node. In the embodiment shown in
Also, when the user focuses on a non-parent node in pane 340, the conflicts tab 364 illustratively shows a conflict summary for that particular non-parent node (e.g., corresponding to the particular update identified by identifier 356). Again, this is described in greater detail below.
It will also be noted that, in another embodiment, update installer component 106 can display recommended updates, automatically, given the user's particular environment and configuration information stored in life cycle system 200.
Returning again to the flow diagram of
In one embodiment described herein, the impact of the selected updates on business system 101 can be shown in these different ways: the impact on the business processes, the impact on the objects and layers of business system 101, and the level of conflicts that will be generated. In one embodiment, business process analyzer component 134 in update installer component 106 illustratively generates a business process heat map that identifies the business processes in business system 101 that will be affected by the selected updates. This is indicated by block 384 in the flow diagram of
The affect of the selected updates on the underlying business process will first be described. Referring again to the user interface display 380 of
The hierarchical structure in pane 340 also shows that each of the parent nodes in the result set includes a heat map indicator 396. In the embodiment shown in
The thresholds for determining whether a parent node has a heat map indicator 396 indicating that it will be greatly affected or less affected can be set in a variety of different ways. For instance, they can be set anecdotally, they can be set based on user preference (for instance, a user may identify certain business processes as more important than others), they can be set heuristically, or in other ways. For example, in one embodiment, the top 20% most affected parent nodes may have a red heat map indicator 396. That is, if the total number of updates that will be applied to a given process is in the top 20% of all of the business processes, that given process is assigned a heat map indicator 396 that indicates that it will be one of the most affected business processes. The parent nodes with the next 60% of updates applied may be assigned an intermediate heat map indicator 396 indicating that they will be less affected than the most severely affected business processes. The parent nodes with the bottom 20% of updates applied to them may be given a heat map indicator 396 indicating that they will be least affected, among the various business processes. Of course, this is an exemplary breakdown only, and a wide variety of other thresholds or breakdowns can be used.
Before continuing with the description of
Generating a display to show the level of conflicts that will be created by the selected conflicts will now be described.
Generating a display showing object and layer level impact will now be described. It may be that the user wishes to view a more detailed impact analysis that shows the particular layers, models, object types, and specific objects, that are affected by the selected updates. In doing so, the user can illustratively actuate impact analysis wizard user input mechanism 434 in order to invoke impact analyzer component 132 in update installer component 106. When the user does this, impact analyzer component 132 generates an impact analysis pane such as pane 436 shown in
This causes impact analysis component 132 to generate a pane 458 shown in
In any case, impact analyzer component 132 then displays the overall configuration that the user has identified for analysis. This can be done by generating a display, such as display 466 shown in
When the user actuates start analysis button 474, impact analyzer component 132 performs the impact analysis, to generate information indicative of how the selected updates will impact the model files and other parts of system 101, in the configuration specified by the user. In doing so, impact analyzer component 132 can generate progress update displays, such as display 476 shown in
Once impact analyzer component 132 has completed its analysis, it illustratively generates an impact display that displays the impact information. The impact information generally indicates the impact that the selected updates will have on the objects identified by the user. One example of an impact analysis display is display 480 shown in
The displayed information can take a wide variety of different forms. For instance, it can identify the objects that will be changed as indicated by block 504. It can identify objects or conflicts that exist as indicated by block 506. It can also include a wide variety of other information such as the particular update identifier that caused the impact, the update model, the affected model, the layer, object type, object name, and number of conflicts, among other information. This is indicated at block 508. Impact analyzer component 132 can then store the impact analysis information, for the selected updates, for later use. This is indicated by block 510 in
Continuing on with the description of the flow diagram of
At this point in the description, the user has now selected a potential set of updates to be applied (or installed) and has reviewed not only the impact that the selected updates will have on the set of business processes in business system 101, but the impact it will have on the object and layer levels as well. The user has reviewed the conflicts that will be generated and can review even detailed information corresponding to the impact and to the conflicts. Thus, it may be that, after reviewing this information, the user wishes to select different updates and view the impact that they will have. This is indicated by block 516 in
By way of example, update installer component 106 can generate a user interface display, such as display 520 shown in
When the user is ready to install the updates, installation engine 136 illustratively generates a user interface display, such as display 528 that allows the user to confirm that the updates are to be installed. Display 528 illustratively includes a components display pane 530 which identifies the particular components that will be updated by the selected updates. Details display pane 532 displays relevant details corresponding to the installation process. For instance, in the embodiment shown in
Once the user has confirmed that installation is to commence, the user can illustratively actuate install button 534. This causes installation engine 136 to install the selected updates. This is also indicated by blocks 536 and 538 in the flow diagram of
When installation engine 136 completes installing the updates, it also illustratively updates the update state tracking information 210 in life cycle system 200. This is indicated by block 542 in the flow diagram of
After the installation is complete, conflict resolution component 119 illustratively generates a user interface display that allows the user to request that conflict resolution component 119 will automatically resolve as many conflicts as it can, without user intervention. Resolving conflicts is also referred to herein as performing a code merge. Displaying the user interface display allowing the user to select automatic conflict resolution (or code merging) is indicated by block 548 in the flow diagram of
Display 550 includes user input mechanism 552 that can be actuated by the user in order to indicate that the user wishes conflict resolution component 119 to automatically resolve conflicts, where possible. When the user actuates mechanism 552, conflict resolution component 119 illustratively generates a display, such as display 554 shown in
The conflict resolution component 119 can do this in a variety of different ways. For instance, it may be that the base system of business system 101 offered by the manufacturer of system 101 is being updated with cumulative update package 120. Thus, there may be an original base version of system 101, that is updated to obtain an updated version of system 101. However, it may also be that the organization deploying system 101 has modified or otherwise customized the base version of system 101. Thus, in one embodiment, conflict resolution component 119 does a three-way compare that compares the original base version of system 101, with the updated version of system 101, and with the customized version of system 101 that is actually deployed at the organization. Conflict resolution component 119 then performs operations so that the customized version of system 101 that is actually deployed will be updated in a way to eliminate conflicts.
An example may be helpful. For instance, assume that the base version of system 101 has an element named “string S clock”. Assume that the user has customized the base version of system 101 so that the element in the deployed version of system 101 is now called “string S+1 clock”. If the particular update being installed by the user changes the value of “string S clock” in the base version of system 101, then there is a conflict because the user has already customized that element to “string S+1 clock”. Thus, conflict resolution component 119 does a three-way text based comparison to revise the update so that it is consistent with the user's customization of “string S clock” to “sting S+1 clock”. Performing a multi-level text based comparison is indicated by block 562 in the flow diagram of
Conflict resolution component 119 then stores conflict resolution (or code merge) results information so that it can be reviewed, or used, later. This is indicated by block 566 in the flow diagram of
The code merge information 213 can be used by the manufacturer of business system 101, update installer component 106 and/or conflict resolution component 119, or others. For instance, it can be used to improve conflict resolution, add more features based on what is normally customized by the user, or other things.
Conflict resolution component 119 then generates a display of the conflict resolution (or code merge) results information for review by the user. This is indicated by block 578.
In one embodiment, the information in sections 582 and 584 is displayed in terms of user-actuatable input mechanisms. Therefore, when the user actuates one of the items, the user can be navigated to the code location in the code of business system 101 where the conflicts occurred. The user can thus view the details corresponding to those conflicts, or actually work to resolve the conflicts directly from that detailed display screen. For instance, if the user actuates the class declaration node 586 on display portion 582, the user will be navigated to that particular class that contains an unresolved conflict, so that the user can view and work to resolve the conflict. Receiving a user drill down input in this manner is indicated by block 588 in the flow diagram of
It will also be appreciated that, where the user has exported the selected updates, they can be applied using the overall operation shown in
The present discussion has mentioned processors and servers. In one embodiment, the processors and servers include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by, and facilitate the functionality of the other components or items in those systems.
Also, a number of user interface displays have been discussed. They can take a wide variety of different forms and can have a wide variety of different user actuatable input mechanisms disposed thereon. For instance, the user actuatable input mechanisms can be text boxes, check boxes, icons, links, drop-down menus, search boxes, etc. They can also be actuated in a wide variety of different ways. For instance, they can be actuated using a point and click device (such as a track ball or mouse). They can be actuated using hardware buttons, switches, a joystick or keyboard, thumb switches or thumb pads, etc. They can also be actuated using a virtual keyboard or other virtual actuators. In addition, where the screen on which they are displayed is a touch sensitive screen, they can be actuated using touch gestures. Also, where the device that displays them has speech recognition components, they can be actuated using speech commands.
A number of data stores have also been discussed. It will be noted they can each be broken into multiple data stores. All can be local to the systems accessing them, all can be remote, or some can be local while others are remote. All of these configurations are contemplated herein.
Also, the figures show a number of blocks with functionality ascribed to each block. It will be noted that fewer blocks can be used so the functionality is performed by fewer components. Also, more blocks can be used with the functionality distributed among more components.
Business system 101 and update component 106 or other items in architecture 100 can be on-premise or located (fully or partially) in a cloud (public or private) deployment.
The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
In the embodiment shown in
It will also be noted that architecture 100, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.
Under other embodiments, applications or systems are received on a removable Secure Digital (SD) card that is connected to a SD card interface 15. SD card interface 15 and communication links 13 communicate with a processor 17 (which can also embody processor 102 or processors in system 200 or device 116 from
I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.
Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.
Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. Processor 17 can be activated by other components to facilitate their functionality as well.
Examples of the network settings 31 include things such as proxy information, Internet connection information, and mappings. Application configuration settings 35 include settings that tailor the application for a specific enterprise or user. Communication configuration settings 41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
Applications 33 can be applications that have previously been stored on the device 16 or applications that are installed during use, although these can be part of operating system 29, or hosted external to device 16, as well.
The mobile device of
Note that other forms of the devices 16 are possible.
Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation,
The computer 810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 820 through a user input interface 860 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, computers may also include other peripheral output devices such as speakers 897 and printer 896, which may be connected through an output peripheral interface 895.
The computer 810 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 810. The logical connections depicted in
When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
The present application is based on and claims the benefit of U.S. provisional patent application Ser. No. 61/877,856, filed Sep. 13, 2013, and U.S. provisional patent application Ser. No. 61/902,093, filed Nov. 8, 2013, the content of which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5495610 | Shing | Feb 1996 | A |
| 5790856 | Lillich | Aug 1998 | A |
| 5860007 | Soni et al. | Jan 1999 | A |
| 5892953 | Bhagria | Apr 1999 | A |
| 5898872 | Richley | Apr 1999 | A |
| 6381694 | Yen | Apr 2002 | B1 |
| 6425126 | Branson et al. | Jul 2002 | B1 |
| 6477703 | Smith et al. | Nov 2002 | B1 |
| 6964044 | Hudson et al. | Nov 2005 | B1 |
| 7024471 | George et al. | Apr 2006 | B2 |
| 7055130 | Charisius et al. | May 2006 | B2 |
| 7069547 | Glaser | Jun 2006 | B2 |
| 7076778 | Brodersen et al. | Jul 2006 | B2 |
| 7096464 | Weinmann | Aug 2006 | B1 |
| 7127707 | Mishra et al. | Oct 2006 | B1 |
| 7194475 | DelMonaco | Mar 2007 | B2 |
| 7278163 | Banzhof et al. | Oct 2007 | B2 |
| 7313792 | Buban et al. | Dec 2007 | B2 |
| 7318226 | Chefalas et al. | Jan 2008 | B2 |
| 7334222 | Keller | Feb 2008 | B2 |
| 7516367 | Beltowski et al. | Apr 2009 | B1 |
| 7529780 | Braginsky et al. | May 2009 | B1 |
| 7536678 | Kothari et al. | May 2009 | B2 |
| 7565419 | Kwiatkowski et al. | Jul 2009 | B1 |
| 7577948 | Zomaya et al. | Aug 2009 | B2 |
| 7614042 | Hardy et al. | Nov 2009 | B1 |
| 7614046 | Daniels et al. | Nov 2009 | B2 |
| 7624086 | Keith | Nov 2009 | B2 |
| 7624393 | Egan et al. | Nov 2009 | B2 |
| 7676448 | Henderson et al. | Mar 2010 | B2 |
| 7702497 | Dombrowski et al. | Apr 2010 | B2 |
| 7716077 | Mikurak | May 2010 | B1 |
| 7735080 | Barturen et al. | Jun 2010 | B2 |
| 7778963 | Novik et al. | Aug 2010 | B2 |
| 7788119 | Najmi et al. | Aug 2010 | B2 |
| 7895592 | Subramanian et al. | Feb 2011 | B2 |
| 7945906 | Bourke-Dunphy et al. | May 2011 | B2 |
| 7966278 | Satish | Jun 2011 | B1 |
| 7966346 | Jameson | Jun 2011 | B1 |
| 7975265 | Schnoebelen et al. | Jul 2011 | B2 |
| 8074213 | Holtz | Dec 2011 | B1 |
| 8176483 | Hoefler et al. | May 2012 | B2 |
| 8185888 | Duplessis et al. | May 2012 | B2 |
| 8224472 | Maluf et al. | Jul 2012 | B1 |
| 8245216 | Felts | Aug 2012 | B2 |
| 8402452 | Baratti et al. | Mar 2013 | B2 |
| 8418150 | Thirumalai et al. | Apr 2013 | B2 |
| 8429610 | Clemm et al. | Apr 2013 | B2 |
| 8516308 | Gill | Aug 2013 | B1 |
| 8516471 | Bhakta et al. | Aug 2013 | B2 |
| 8516477 | Kearns et al. | Aug 2013 | B1 |
| 8539477 | Balascio et al. | Sep 2013 | B2 |
| 8555273 | Chia et al. | Oct 2013 | B1 |
| 8566391 | Saito et al. | Oct 2013 | B2 |
| 8635608 | Ramesh et al. | Jan 2014 | B2 |
| 8677348 | Ramanathpura et al. | Mar 2014 | B1 |
| 8701078 | Holler et al. | Apr 2014 | B1 |
| 8713525 | Attalla | Apr 2014 | B2 |
| 8745611 | Saraf et al. | Jun 2014 | B2 |
| 8782606 | Cohen | Jul 2014 | B1 |
| 8782608 | Ackerman et al. | Jul 2014 | B2 |
| 8799044 | Sudarshan et al. | Aug 2014 | B2 |
| 8806450 | Maharana | Aug 2014 | B1 |
| 8839222 | Brandwine | Sep 2014 | B1 |
| 8881136 | DeJana et al. | Nov 2014 | B2 |
| 8886571 | Mannava et al. | Nov 2014 | B2 |
| 9026851 | Mondal et al. | May 2015 | B2 |
| 9122422 | Johnston et al. | Sep 2015 | B2 |
| 9348585 | Eliáet al. | May 2016 | B2 |
| 20010052108 | Bowman-Amuah | Dec 2001 | A1 |
| 20020099728 | Lees | Jul 2002 | A1 |
| 20020198750 | Innes et al. | Dec 2002 | A1 |
| 20030046675 | Cheng | Mar 2003 | A1 |
| 20030051236 | Pace | Mar 2003 | A1 |
| 20030172368 | Alumbaugh et al. | Sep 2003 | A1 |
| 20030218628 | Deshpande | Nov 2003 | A1 |
| 20030221182 | Tip | Nov 2003 | A1 |
| 20030221190 | Deshpande | Nov 2003 | A1 |
| 20040006704 | Dahlstrom et al. | Jan 2004 | A1 |
| 20040015918 | Kawahito et al. | Jan 2004 | A1 |
| 20040122870 | Park et al. | Jun 2004 | A1 |
| 20040123234 | Anderson | Jun 2004 | A1 |
| 20040143811 | Kaelicke et al. | Jul 2004 | A1 |
| 20040210653 | Kanoor | Oct 2004 | A1 |
| 20040255290 | Bates et al. | Dec 2004 | A1 |
| 20050044187 | Jhaveri et al. | Feb 2005 | A1 |
| 20050055686 | Buban | Mar 2005 | A1 |
| 20050132348 | Meulemans | Jun 2005 | A1 |
| 20050132349 | Roberts | Jun 2005 | A1 |
| 20050132359 | McGuire | Jun 2005 | A1 |
| 20050144619 | Newman | Jun 2005 | A1 |
| 20050177617 | Banginwar et al. | Aug 2005 | A1 |
| 20050223117 | Terry et al. | Oct 2005 | A1 |
| 20060020937 | Schaefer | Jan 2006 | A1 |
| 20060064666 | Amaru et al. | Mar 2006 | A1 |
| 20060075001 | Canning et al. | Apr 2006 | A1 |
| 20060080656 | Cain et al. | Apr 2006 | A1 |
| 20060106806 | Sperling et al. | May 2006 | A1 |
| 20060117310 | Daniels | Jun 2006 | A1 |
| 20060123022 | Bird | Jun 2006 | A1 |
| 20060130040 | Subramanian | Jun 2006 | A1 |
| 20060130046 | O'Neill | Jun 2006 | A1 |
| 20060136327 | You | Jun 2006 | A1 |
| 20060200658 | Penkethman | Sep 2006 | A1 |
| 20060218548 | Mason et al. | Sep 2006 | A1 |
| 20060282830 | Kavalam et al. | Dec 2006 | A1 |
| 20070021116 | Okita et al. | Jan 2007 | A1 |
| 20070033276 | Brockhoff | Feb 2007 | A1 |
| 20070061732 | Bobbin et al. | Mar 2007 | A1 |
| 20070074172 | Bird et al. | Mar 2007 | A1 |
| 20070106978 | Felts | May 2007 | A1 |
| 20070106979 | Felts | May 2007 | A1 |
| 20070106980 | Felts | May 2007 | A1 |
| 20070113225 | Felts | May 2007 | A1 |
| 20070130561 | Siddaramappa et al. | Jun 2007 | A1 |
| 20070143735 | Clemm | Jun 2007 | A1 |
| 20070168201 | Chellam | Jul 2007 | A1 |
| 20070169079 | Keller | Jul 2007 | A1 |
| 20070180075 | Chasman et al. | Aug 2007 | A1 |
| 20070198599 | Tobies | Aug 2007 | A1 |
| 20070220506 | Maruyama | Sep 2007 | A1 |
| 20070220510 | Bell | Sep 2007 | A1 |
| 20070226794 | Howcroft et al. | Sep 2007 | A1 |
| 20070277167 | Smith et al. | Nov 2007 | A1 |
| 20070282914 | Sivapragasam et al. | Dec 2007 | A1 |
| 20070283321 | Hegde et al. | Dec 2007 | A1 |
| 20080033700 | Kano | Feb 2008 | A1 |
| 20080071844 | Gopal et al. | Mar 2008 | A1 |
| 20080109791 | Carteri et al. | May 2008 | A1 |
| 20080134145 | Halcrow et al. | Jun 2008 | A1 |
| 20080162509 | Becker | Jul 2008 | A1 |
| 20080201701 | Hofhansl | Aug 2008 | A1 |
| 20080201702 | Bunn | Aug 2008 | A1 |
| 20080215349 | Baran et al. | Sep 2008 | A1 |
| 20080262860 | Schneider et al. | Oct 2008 | A1 |
| 20080288934 | Ozawa | Nov 2008 | A1 |
| 20080295086 | Greenwood | Nov 2008 | A1 |
| 20080313626 | Kodaka | Dec 2008 | A1 |
| 20090144756 | Inami | Jun 2009 | A1 |
| 20090182567 | Stine | Jul 2009 | A1 |
| 20090216712 | Cohen et al. | Aug 2009 | A1 |
| 20090271696 | Bailor et al. | Oct 2009 | A1 |
| 20090307650 | Saraf et al. | Dec 2009 | A1 |
| 20100023919 | Chaar et al. | Jan 2010 | A1 |
| 20100063855 | Nguyen | Mar 2010 | A1 |
| 20100082803 | Nguyen | Apr 2010 | A1 |
| 20100095273 | Matthiesen | Apr 2010 | A1 |
| 20100131939 | Hieb et al. | May 2010 | A1 |
| 20100138812 | Narayanan | Jun 2010 | A1 |
| 20100153908 | Sarkar et al. | Jun 2010 | A1 |
| 20100191623 | Macy et al. | Jul 2010 | A1 |
| 20100235823 | Garbers et al. | Sep 2010 | A1 |
| 20100275263 | Bennett et al. | Oct 2010 | A1 |
| 20100299653 | Iyer | Nov 2010 | A1 |
| 20100306651 | Quennesson | Dec 2010 | A1 |
| 20100313179 | Groves et al. | Dec 2010 | A1 |
| 20110016461 | Bankston et al. | Jan 2011 | A1 |
| 20110041124 | Fishman et al. | Feb 2011 | A1 |
| 20110055544 | Vidal et al. | Mar 2011 | A1 |
| 20110099050 | Coldicott | Apr 2011 | A1 |
| 20110113493 | Moore | May 2011 | A1 |
| 20110173266 | Ohashi | Jul 2011 | A1 |
| 20110197099 | Mahajan et al. | Aug 2011 | A1 |
| 20110225575 | Ningombam | Sep 2011 | A1 |
| 20110231828 | Kaulgud et al. | Sep 2011 | A1 |
| 20110265077 | Collison et al. | Oct 2011 | A1 |
| 20110296394 | Vidal | Dec 2011 | A1 |
| 20110307336 | Smirnov et al. | Dec 2011 | A1 |
| 20110307798 | Lezama et al. | Dec 2011 | A1 |
| 20120030658 | Hu et al. | Feb 2012 | A1 |
| 20120053936 | Cardno et al. | Mar 2012 | A1 |
| 20120060144 | Novak et al. | Mar 2012 | A1 |
| 20120089964 | Sawano | Apr 2012 | A1 |
| 20120166458 | Laudanski et al. | Jun 2012 | A1 |
| 20120174073 | Rajopadhye | Jul 2012 | A1 |
| 20120210294 | Gores | Aug 2012 | A1 |
| 20120232948 | Wolf et al. | Sep 2012 | A1 |
| 20130036415 | Birtwhistle | Feb 2013 | A1 |
| 20130042221 | Mehalingam | Feb 2013 | A1 |
| 20130042227 | Little et al. | Feb 2013 | A1 |
| 20130060489 | Crossman et al. | Mar 2013 | A1 |
| 20130061167 | Rhodes et al. | Mar 2013 | A1 |
| 20130132777 | Froehlich et al. | May 2013 | A1 |
| 20130159989 | Deckert | Jun 2013 | A1 |
| 20130179868 | Greifeneder et al. | Jul 2013 | A1 |
| 20130268914 | Oslake | Oct 2013 | A1 |
| 20140047427 | Evans | Feb 2014 | A1 |
| 20140100676 | Scott et al. | Apr 2014 | A1 |
| 20140201573 | Huang et al. | Jul 2014 | A1 |
| 20140331200 | Wadhwani et al. | Nov 2014 | A1 |
| 20140337982 | Crosby et al. | Nov 2014 | A1 |
| 20150058822 | Eliás et al. | Feb 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2004057463 | Jul 2004 | WO |
| 2005033934 | Apr 2005 | WO |
| Entry |
|---|
| Barbara G. Ryder et al., Change Impact Analysis for Object-Oriented Programs, Jun. 2001, [Retrieved on May 23, 2016]. Retrieved from the internet: <URL: http://delivery.acm.org/10.1145/380000/379661/p46-ryder.pdf?> 8 Pages (46-53). |
| K. H. Bennett et al., Software Maintenance and Evolution: a Roadmap, ACM 2000, [Retrieved on May 23, 2016]. Retrieved from the internet: <URL: http://delivery.acm.org/10.1145/340000/336534/p73-bennett.pdf?> 14 Pages (73-87). |
| Shawn A. Bohner, Impact Analysis in the Software Change Process: A Year 2000 Perspective, 1996 IEEE, [Retrieved on Aug. 23, 2016]. Retrieved from the internet: <URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=564987> 10 Pages. (42-51). |
| James Law et al., Whole Program Path-Based Dynamic Impact Analysis, 2003 IEEE, [Retrieved on Aug. 23, 2016]. Retrieved from the internet: <URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1201210> 11 Pages. (1-11). |
| L.C. Briand et al., Impact Analysis and Change Management of UML Models, 2003 IEEE, [Retrieved on Jul. 11, 2017]. Retrieved from the internet: <URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1235428> 10 Pages (1-10). |
| Barbara G. Ryder et al., Change impact analysis for object-oriented programs, 2001, [Retrieved on Jul. 11, 2017]. Retrieved from the internet: <URL: http://dl.acm.org/citation.cfm?id=379661> 8 Pages (46-53). |
| International Search Report and Written Opinion for International Application No. PCT/US2014/054631, mailing date: Nov. 24, 2014, filing date: Sep. 9, 2014, 13 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2014/054632, mailing date: Nov. 24, 2014, filing date: Sep. 9, 2014, 12 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2014/055285, mailing date: Dec. 2, 2014, filing date: Sep. 12, 2014, 13 pages. |
| Prosecution History for U.S. Appl. No. 14/151,296 including: Response to Notice to File Corrected Application Papers dated Apr. 15, 2014, Notice to File Corrected Application Papers dated Jan. 27, 2014 and Application and Drawings filed Jan. 9, 2014, 90 pages. |
| Application and Drawings for U.S. Appl. No. 14/152,694, filed Jan. 10, 2014, 84 pages. |
| Application and Drawings for U.S. Appl. No. 14/151,306, filed Jan. 9, 2014, 84 pages. |
| Application and Drawings for U.S. Appl. No. 14/151,329, filed Jan. 9, 2014, 84 pages. |
| “Prism Deploy”, Published on: Jun. 3, 2002, Available at: http://amtsoft.com/prismdeploy/. |
| Cordero V, Randall, “Apply updates to database, AOS, and clients [AX 2012]”, Published on: Dec. 21, 2013, Available at: http://technet.microsoft.com/en-us/library/hh538446.aspx. |
| “Update System Center 2012 Configuration Manager”, Published on: Aug. 1, 2013, Available at: http://technet.microsoft.com/en-us/library/jj553405.aspx. |
| “SQL Server Distributed Replay”, Published on: Apr. 24, 2012, Available at: http://technet.microsoft.com/en-us/library/ff878183.aspx. |
| “Managing Multiple Environments from Development to Production”, Published on: Jan. 18, 2012, Available at: http://docs.oracle.com/cd/B28359—01/owb.111/b31280/configs—11.htm#WBINS12301. |
| Dunagan, et al., “Towards a Self-Managing Software Patching Process Using Black-Box Persistent-State Manifests”, In Technical Report, MSR-TR-2004-23, Mar. 21, 2004, 9 pages. |
| Terry, et al., “Managing Update Conflicts in Bayou, a Weakly Connected Replicated Storage System”, In Proceedings of the 15th ACM Symposium on Operating Systems Principles, Dec. 3, 1995, 12 pages. |
| “JD Edwards EnterpriseOne Tools—Software Updates Guide”, Published On: Mar. 2011, Available at: http://docs.oracle.com/cd/E17984—01/doc.898/e14719.pdf. |
| “Apply Updates and Hotfixes [AX 2012]”, Published On: Jun. 19, 2013, Available at: http://technet.microsoft.com/en-us/library/hh335183.aspx. |
| Sherriff, et al., “Empirical Software Change Impact Analysis using Singular Value Decomposition”, In 1st International Conference on Software Testing, Verification, and Validation, 10 pages. |
| Prosecution History for U.S. Appl. No. 14/151,306 including: Non-Final Office Action dated Jun. 23, 2015, Response to Notice to File Missing Parts dated Mar. 6, 2014 and Notice to File Missing Parts dated Jan. 27, 2014, 24 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/151,329 dated Jun. 23, 2015, 18 pages. |
| Prosecution History for U.S. Appl. No. 14/152,694 including: Non-Final Office Action dated Jul. 14, 2015, Response to Notice to File Missing Parts dated Apr. 8, 2014 and Notice to File Missing Parts dated Jan. 28, 2014, 29 pages. |
| “Second Written Opinion Received for PCT Patent Application No. PCT/US2014/054631”, Mailed Date: Jul. 21, 2015, 6 Pages. |
| The Second Written Opinion for International Application No. PCT/US2014/054632, mailing date: Aug. 25, 2015, filing date: Sep. 9, 2014, 9 pages. |
| Amendment for U.S. Appl. No. 14/151,306 dated Sep. 23, 2015, 12 pages. |
| Amendment for U.S. Appl. No. 14/151,329 dated Sep. 23, 2015, 12 pages. |
| Amendment for U.S. Appl. No. 14/152,694 dated Oct. 13, 2015, 13 pages. |
| Microsoft, Software Update Management Using SMS 2003, Mar. 15, 2007, [Retrieved on Oct. 30, 2015]. Retrieved from the internet: <URL:http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cnload%2Ff%2F6%2Fa%2Ff6acc021-a05a-48a1-88e2->103 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/151,306 dated Nov. 13, 2015, 23 pages. |
| Final Office Action for U.S. Appl. No. 14/152,694 dated Nov. 13, 2015, 27 pages. |
| Final Office Action for U.S. Appl. No. 14/151,329 dated Nov. 16, 2015, 25 pages. |
| International Preliminary Report on Patentability for International Application No. PCT/US2014/054631, date of mailing: Dec. 11, 2015, date of filing: Sep. 9, 2014, 21 pages. |
| International Preliminary Report on Patentability for International Application No. PCT/US2014/054632, date of mailing: Dec. 17, 2015, date of filing: Sep. 9, 2014, 16 pages. |
| Prosecution History for U.S. Appl. No. 14/151,329 including: Final Office Action dated Feb. 3, 2016, Applicant Initiated Interview Summary dated Feb. 3, 2016, and Interview Summary dated Jan. 26, 2016, 28 pages. |
| Amendment With RCE for U.S. Appl. No. 14/152,694 dated Feb. 3, 2016, 16 pages. |
| Amendment for U.S. Appl. No. 14/151,306 dated Feb. 26, 2016, 13 pages. |
| Final Office Action for U.S. Appl. No. 14/151,306 dated Mar. 31, 2016, 18 pages. |
| Michelle L. Lee, “Change Impact Analysis of Object-Oriented Software”, 1998, [Retrieved on Mar. 18, 2016], Retrieved from the Internet:<URL:http://cs.gmu.edu/˜offutt/rsrch/LiLiDiss.pdf>202 pages. |
| Prosecution History for U.S. Appl. No. 14/151,329 including: Applicant Initiated Interview Summary dated May 10, 2016 and Amendment with RCE dated May 3, 2016, 18 pages. |
| Jyotish Gogoi, “SAP Software Update Manager Tool—SPS Update Demo—Part I”, Dated Mar. 20, 2012 [Retrieved on Sep. 2, 2016]. Retrieved from the Internet: <URL:http://scn.sap.com/docs/DOC-25113>6 pages. |
| Konnie Daglis, et al. “Software Update Manager (SUM) for SAP Solutions”, Dated May 14, 2012 [Retrieved on Sep. 2, 2016]. Retrieved from the Internet: <URL:http://events.asug.com/2012AC/1602—Software—Update—Manager—for—SAP—Solutions.pdf>26 pages. |
| ALM Solution Management, “Test Automation with SAP Solution Manager 7.1 and HP QTP”, Dated Sep. 2012 [Retrieved on Sep. 2, 2016]. Retrieved from the Internet: <URL:http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e01fcb07-691b-3010-48b8-cf2881e14a64?overridelayout=true>31 pages. |
| Enda O'Connor, “Patch Management Best Practices”, Dated Apr. 2008 [Retrieved on Sep. 9, 2016]. Retrieved from the Internet: <URL:http://www.oracle.com/technetwork/systems/articles/patch-management-jsp-135385.html>4 pages. |
| David Marshall, “Patch Management Best Practices”, Dated Apr. 23, 2013 [Retrieved on Sep. 2, 2016]. Retrieved from the Internet: <URL: http://www.infoworld.com/article/2614556/server-virtualization/vmware-sells-off-shavlik-patch-management-to-landesk.html>3 pages. |
| ManageEngine, “Automated Patch Management for Windows”, Undated [Retrieved on Sep. 2, 2016]. Retrieved from the Internet: <URL: http://www.infoworld.com/article/2614556/server-virtualization/vmware-sells-off-shavlik-patch-management-to-landesk.html>2 pages. |
| “Oracle 6 Using the Software Update Impact Analysis Tool”, retrieved from, <https://docs.oracle.com/cd/E24705—01/doc.91/e24260/impactanalysistool.htm#EOTSU00104> accessed on Sep. 29, 2016. Believed to have been publically available at least as of Aug. 2013. 10 pages. |
| “Business Process Change Analyzer in SAP Solution Manager 7-1”, retrieved from: <http://sapassets.edgesuite.net/sapcomidocs/2015/07/9a426487-5b7c-0010-82c7-eda71a1511fa,pdf> accessed on Sep. 29, 2016, dated Jul. 11, 2012, Believed to have been publically available at least as of Aug. 2013, 13 pages. |
| “SAP Solution Manager 7.1 Business Process Change Analyzer (BPCA)”, retrieved from: <https://supportsap.com/content/dam/library/SAP%20Support%20Portal/support-programs-services/solution-manager/processes/Media%20Library/Test%20Management/Overview%20of%20Business%20Process%20Change%20Analyzer(BPCA).pdf>, accessed on Sep. 29, 2016, Believed to have been publically available at least as of Aug. 2013, 115 pages. |
| “Test Management with SAP Solution Manager 7.1”, retrieved from: <https://support.sap.com/content/dam/library/SAP%20Support%20Portal/support-programs-services/solution-manager/processes/Media%20Library/Test%20Managernent/SAP/%20Test%20Management%20with%20SAP%20SolMan%207.1.pdf>, accessed on Sep. 29, 2016. Believed to have been publically available at least as of Aug. 2013, 85 pages. |
| Amendment for U.S. Appl. No. 14/152,694 dated Nov. 15, 2016, 15 pages. |
| Amendment for U.S. Appl. No. 14/151,296 dated Nov. 11, 2016, 12 pages. |
| Notice of Allowance for U.S. Appl. No. 14/151,306 dated Dec. 6, 2016, 25 pages. |
| Chi-Keung Luk et al., “Pin: Building Customized Program Analysis Tools with Dynamic Instrumentation”, ACM 2005, [Retrieved on Sep. 1, 2016], Retrieved from the Internet <URL:http://gram.eng.uci.edu/students/swallace/papers—wallace/pdf/PLDI-05-Pin.pdf>11 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/152,694 dated Jul. 15, 2016, 33 pages. |
| Notice of Allowance for U.S. Appl. No. 14/151,329 dated Jul. 13, 2016, 23 pages. |
| Chengzheng Sun et al., “A Multi-version Approach to Conflict Resolution in Distributed Groupware Systems”, 2000 [Retrieved on Jun. 8, 2016]. Retrieved from the Internet <URL:http://ieeexplore.ieee.org/stamp/stamp.jsp.?tp=&arnumber=840944>10 pages. (1-10). |
| tra Brosch et al., “We can work it out: Collaborative Conflict Resolution in Model Versioning”, Sep. 2009, [Retrieved on Jun. 8, 2016]. Retrieved from the Internet: <URL:http://download.springer.com/static/pdf/607/chp%253A10.1007%252F978-1-84882-854-4—12.pdf>8 pages (207-214). |
| Amendment with RCE for U.S. Appl. No. 14/151,306 dated Aug. 1, 2016, 16 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/151,296 dated Aug. 12, 2015, 23 pages. |
| Final Office Action for U.S. Appl. No. 14/151,306 dated Dec. 21, 2016, 18 pages. |
| Amendment After Notice of Allowance for U.S. Appl. No. 14/151,306 dated Dec. 15, 2016, 9 pages. |
| Final Office Action for U.S. Appl. No. 14/152,694 dated Dec. 23, 2016, 25 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/151,296 dated May 19, 2017, 19 pages. |
| Amendment with RCE for U.S. Appl. No. 14/151,296 dated Apr. 21, 2017, 15 pages. |
| Jonghyun Park et al., “Monitoring Impact Events Using a System-Identification Method”, AIAA Journal vol. 47, No. 9, Sep. 2009, [Retrieved on Feb. 24, 2017], Retrieved from the Internet:<URL:http://arc.aiaa.org/doi/ pdf/10.2514/1.34895?>11 pages. |
| Olivier Crameri et al., “Staged Deployment in Mirage, an Integrated Software Upgrade Testing and Distribution System”, Oct. 14-17, 2007, [Retrieved on Feb. 24, 2017], Retrieved from the Internet:<URL:http://delivery.acm.org/10.1145/1300000/1294283/p221-crameri.pdf?>, 16 pages. |
| Notice of Allowance for U.S. Appl. No. 14/152,694 dated Mar. 2, 2017, 17 pages. |
| Shawn A. Bohner, “Impact Analysis in the Software Change Process: A Year 2000 Perspective”, 1996 IEEE, 10 pages. |
| Advisory Action for U.S. Patent Appl. No. 14/151,296 dated Feb. 24 2017, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150082296 A1 | Mar 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61902093 | Nov 2013 | US | |
| 61877856 | Sep 2013 | US |
