Software redevelopment system

• US 5,812,849 A
• Filed: 12/18/1996
• Issued: 09/22/1998
• Est. Priority Date: 12/18/1996
• Status: Expired due to Term

• Current Assignee: FCA US LLC (Stellantis NV)
• Original Assignee: Chrysler Corporation (Stellantis NV)
• Inventors: Nykiel, Michael A., Weingart, Chuck, Oetjens, John R.
• Primary Examiner(s): Voeltz, Emanuel Todd
• Assistant Examiner(s): SMITH-STEWART, DEMETRA R
• Application Number:
  US08/769,040
• Time in Patent Office: 643 Days
• Field of Search: 395/701, 395/500, 395/703, 707/100, 707/102, 364/280, 364/281.3, 364/282.1, 364/283.4
• US Class Current: 717/101
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/5066 Algorithms for mapping a plurality of inter-dependent sub-tasks onto a plurality of physical CPUs mappping at compile time, see G06F8/451
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A predetermined change to a software system having a large number of highly connected and interrelated executables and data files is accomplished using a redevelopment database which is generated from a software library. The redevelopment database maintain resource and relational information on the executables and data files. This information is used by a partitioner which creates groups of executables and data files which have minimal connections to executables and data files outside a given group. The groups are assigned to a resource, with the resource performing the software changes in a given group with the aid of software change mechanisms. After the changes in a group are completed, a configuration management system of the software system receives the newly modified software, updating the software system. The configuration management system also notifies the redevelopment database so that the relational and resource information of the redevelopment database remains up to date, and continues to support the day-to-day modifications other than the predetermined software change.

Claims

1. An apparatus for implementing a predetermined change in a plurality of software objects of a software library, comprising:

a redevelopment database generated from said software library, said redevelopment database having relational information and resource information of said software objects;

a partitioner for creating a plurality of clusters having said plurality of software objects, said partitioner creating said plurality of clusters based upon said relational information;

an assigner for allocating each of said plurality of clusters created by said partitioner to a resource, said assigner allocating each of said plurality of cluster based upon said resource information and producing a plurality of resource allocated modules;

a software change tool for assisting in the implementation of said predetermined change in one of said resource allocated modules, said software change tool producing a changed resource allocated module; and

a configuration management system for receiving said changed resource allocated module once said predetermined change has been completed, said configuration management system updating said software library with said changed resource allocated module, whereby said predetermined change in said plurality of software objects of a software library is implemented.

2. The apparatus of claim 1, further comprising a synonym finder, said synonym finder generating an element portfolio from said redevelopment database, said element portfolio limited to said software objects in said software library which potentially require said predetermined change, said element portfolio being provided to said redevelopment database from which a flat file is generated having said relational information used by said partitioner.

3. The apparatus of claim 1 wherein said configuration management system notifies said redevelopment directory of changes to said software library, said redevelopment directory updating said relational information based upon said notification by said configuration management system.

4. The apparatus of claim 1 wherein said software change tool is a text editor.

5. The apparatus of claim 1 wherein said software change tool is a data name finder, said data name finder locating lines of executable code requiring said predetermined change.

6. The apparatus of claim 1 wherein said software change tool is a truncation detector, said truncation detector examining compiler output of said software objects to ensure proper modifications of said software objects with said predetermined change.

7. The apparatus of claim 1 wherein said software change tool is an IMS bridge, said IMS bridge providing a means by which said software objects can store or retrieve data from an IMS database despite said software objects and said IMS database having different formats for said IMS data.

8. The apparatus of claim 1 wherein said assignor is an Access database.

9. The apparatus of claim 1 wherein said predetermined change is said implemented in order to correct problems caused by the year 2000.

10. A method for altering software objects of a management information system, comprising the steps of:

(a) generating a redevelopment database from said management information system, said redevelopment database generated to include relational information and resource information of said software objects;

(b) dividing said software objects into a plurality of clusters based upon said relational information contained in said redevelopment database;

(c) assigning each of said plurality of clusters to a resource based upon said resource information and producing a plurality of resource allocated modules;

(d) altering one of said plurality of resource allocated modules with a predetermined change and producing a changed allocated resource module; and

(e) merging said changed allocated resource module into said management information system.

11. The method of claim 10 further comprising the step of generating an element portfolio, said element portfolio generated to have software objects of said management information system which potentially require said predetermined change.

12. The method of claim 10 further comprising the step of updating said redevelopment database when a change is made to the management information system.

13. The method of claim 10 further comprising the step of locating lines of executable code requiring said predetermined change using a data name finder.

14. The method of claim 10 further comprising the step of examining compiler output with a truncation detector in order to ensure proper modifications of said software objects with said predetermined change.

15. The method of claim 10 further comprising the step of bridging IMS data in order to allow said IMS data to be used by software objects having a different format specified for said IMS data than is specified in an IMS database holding said IMS data.

16. The method of claim 10 further comprising the step of notifying said redevelopment database that a change has been made to said management information system.

17. The method of claim 16 further comprising the step of updating said redevelopment database upon receiving said notification that said change has been made to said management information system.

18. The method of claim 10 further comprising the step of conducting day-to-day modifications in addition to said predetermined change.

19. The method of claim 10 wherein altering said software objects is performed in order to correct problems caused by the year 2000.