Automated software modification facilitator

• US 5,860,007 A
• Filed: 09/29/1995
• Issued: 01/12/1999
• Est. Priority Date: 09/29/1995
• Status: Expired due to Fees

• Current Assignee: Siemens Corporate Research Incorporated (Siemens AG)
• Original Assignee: Siemens Corporate Research Incorporated (Siemens AG)
• Inventors: Greenberg, Michael, Soni, Dilip
• Primary Examiner(s): Poinvil, Frantzy
• Application Number:
  US08/536,547
• Time in Patent Office: 1,201 Days
• Field of Search: 395/703, 395/708, 395/182.13, 395/182.14, 706/60
• US Class Current: 717/121
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Analysis, planning and interrelated modifications of a software system across modular architectural, language and documentation levels are automated and facilitated by use of the Change Assistant (CA). CA automatically analyzes the impact of the intended change on all levels, identifying related changes that may be needed to achieve the programmer'"'"'s goal. When the plan is finalized and approved, CA automatically performs the change, modifying the code, as needed, to make it consistent with the changed architecture. Thereby, the need for human intervention in maintaining software is significantly reduced and the possibility of error minimized.

Claims

1. An automated method, performed by a digital computer, for interactively planning, changing and maintaining software programs composed of constructs, programs and files on interrelated modular architectural, language and text documentation levels, each of which is accessible and displayable as a separate view level through an object-oriented system, wherein a change made on one level automatically informs the operator of and generates all necessary corresponding changes on other levels, comprising the steps of:

selecting a view level for display;

choosing a type of change from a class of changes associated with the selected view level;

specifying a desired change;

analyzing the impact of the specified change across all interrelated levels of the software to identify and display other additional changes necessitated by said specified change, if any, including;

recursively analyzing each identified additional change to further identify and display still other additional changes necessitated by the additional change and subsequent other additional changes, if any, at each view level, determining whether the specified change and any additional changes can be implemented without operator intervention, displaying for an operator a selection of choices for implementing first the specified change and then any additional changes if more than one way of implementing the specified change or any resulting additional changes is available, and requesting operator guidance when the computer is unable to perform the specified change or any additional changes; and

implementing the originally specified change and any other changes necessitated as a result of said analysis on all view levels automatically without operator intervention.

2. The method of claim 1, wherein, when the name of a procedure is specified to be changed, analyzing includes the following steps:

checking for name conflicts in a defining module;

generating a list of all calling modules;

checking for name conflicts in each of the calling modules;

changing the name at the definition site;

changing the name at each declaration site;

changing the name at each call site; and

changing the name in each import/export specification.

3. The method of claim 1, wherein, when the location of a procedure is specified to be changed, analyzing includes the following steps;

checking for a name conflict in the new file;

moving the definition from the old file to the new file;

checking for visibility of the procedure to callers;

checking the accessibility of resources used by the procedure in the new file; and

moving the declaration from the old file to the new file.

4. The method of claim 1, wherein, analyzing at the language level includes for each object determining at what levels that object is visible, whether an identifier for an object is reusable, whether a separate declaration for the object is possible, whether there is a restriction on the location of the object, and whether and how the object may be shared across different files in a program.

5. The method of claim 1, wherein analyzing for any specified or additional change includes determining

whether there is an illegal location or illegal identifier name;

whether the used resource is no longer accessible, ambiguous or different;

whether an object becomes inaccessible to users;

whether two objects with the same name become accessible to users and how they differ from each other;

whether object names conform to the naming convention; and

whether the relationship between text comments and code should be altered or deleted as a result of the change.