Software development code management tool

• US 20050108685A1
• Filed: 11/17/2003
• Published: 05/19/2005
• Est. Priority Date: 11/17/2003
• Status: Abandoned Application

• Current Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Original Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Inventors: Ta, Jim C.
• Application Number:
  US10/715,061
• Publication Number:
  US 20050108685A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A method, system, and computer program product for controlling code in a multi-developer software development environment is provided. In one embodiment the software development tool identifies a plurality of software components as non-modifiable and prevents unauthorized access and modification to the non-modifiable objects. When a request from a requesting user to modify one of the software components is received by the development tool, the tool determines whether the software component has been checked out by another user and, if not, provides the requesting user with a modifiable copy of the one of the software. If the software component has been checked out by another user, the requesting user is presented with information as to who has checked out the software component and may send a message to that person if the requesting user so desires. When the user that has checked out the software component finishes, the component is saved and checked back in to indicate that others may now check out the software component to modify it.

Claims

1. A method for controlling code in a multi-developer software development environment, the method comprising:

identifying a plurality of software components as non-modifiable and preventing access and modification to the non-modifiable objects;

receiving a request from a requesting user to modify one of the software components;

determining whether the software component has been checked out by another user;

providing the requesting user with a modifiable copy of the one of the software component if the software component has not been checked out by another user.

2. The method as recited in claim 1, further comprising:

presenting the requesting user with an indication that the software component has been checked out by another user and is not available for modification if the object has been checked out by another user.

3. The method as recited in claim 1, further comprising:

creating a backup copy of the software component prior to providing the user with a modifiable copy of the software component.

4. The method as recited in claim 1, further comprising:

updating a file indicating that the software component is checked out, the identity of the user that checked out the software component, the date the software component was checked out, and the time the software component was checked out.

5. The method as recited in claim 1, further comprising:

prompting the requesting user to provide information about what is intended to be changed in the software component.

6. The method as recited in claim 5, further comprising:

updating a file indicating the changes intended to be made to the software component.

7. The method as recited in claim 1, wherein the software component is an object.

8. The method as recited in claim 4, wherein the file is one of a table and a database.

9. The method as recited in claim 6, wherein the file is one of a table and a database.

10. The method as recited in claim 2, further comprising:

determining whether the requesting user wishes to send a message to the user who currently has the object checked out;

prompting the requesting user to indicate the message to be sent to the user who currently has the software component checked out; and

sending the message to the user who currently has the software component checked out.

11. The method as recited in claim 10, further comprising:

determining the method the requesting user wished the message to be sent to the user who currently has the software component checked out; and

sending the message by the method specified by the requesting user.

12. The method as recited in claim 1, further comprising:

determining that the requesting user requests to check the software component back in;

prompting the requesting user to enter a description of what has changed to the software component; and

saving an updated software component, indicating that the software component is checked in, and indicating that the software component is not modifiable.

13. The method as recited in claim 12, further comprising:

updating a file indicating that the software component is checked back in, the date and time checked in, the identity of the developer who checked the software component back in, and the nature of the changes made to the software component.

14. A computer program product in a computer readable media for use in a data processing system for controlling code in a multi-developer software development environment, the computer program product comprising:

first instructions for identifying a plurality of software components as non-modifiable and preventing access and modification to the non-modifiable objects;

second instructions for receiving a request from a requesting user to modify one of the software components;

third instructions for determining whether the software component has been checked out by another user;

fourth instructions for providing the requesting user with a modifiable copy of the one of the software component if the software component has not been checked out by another user.

15. The computer program product as recited in claim 14, further comprising:

fifth instructions for presenting the requesting user with an indication that the software component has been checked out by another user and is not available for modification if the object has been checked out by another user.

16. The computer program product as recited in claim 14, further comprising:

fifth instructions for creating a backup copy of the software component prior to providing the user with a modifiable copy of the software component.

17. The computer program product as recited in claim 14, further comprising:

fifth instructions for updating a file indicating that the software component is checked out, the identity of the user that checked out the software component, the date the software component was checked out, and the time the software component was checked out.

18. The computer program product as recited in claim 14, further comprising:

fifth instructions for prompting the requesting user to provide information about what is intended to be changed in the software component.

19. The computer program product as recited in claim 18, further comprising:

sixth instructions for updating a file indicating the changes intended to be made to the software component.

20. The computer program product as recited in claim 14, wherein the software component is an object.

21. The computer program product as recited in claim 17, wherein the file is one of a table and a database.

22. The computer program product as recited in claim 19, wherein the file is one of a table and a database.

23. The computer program product as recited in claim 15, further comprising:

sixth instructions for determining whether the requesting user wishes to send a message to the user who currently has the object checked out;

seventh instructions for prompting the requesting user to indicate the message to be sent to the user who currently has the software component checked out; and

eighth instructions for sending the message to the user who currently has the software component checked out.

24. The computer program product as recited in claim 23, further comprising:

ninth instructions for determining the computer program product the requesting user wished the message to be sent to the user who currently has the software component checked out; and

tenth instructions for sending the message by the computer program product specified by the requesting user.

25. The computer program product as recited in claim 14, further comprising:

fifth instructions for determining that the requesting user requests to check the software component back in;

sixth instructions for prompting the requesting user to enter a description of what has changed to the software component; and

seventh instructions for saving an updated software component, indicating that the software component is checked in, and indicating that the software component is not modifiable.

26. The computer program product as recited in claim 25, further comprising:

eighth instructions for updating a file indicating that the software component is checked back in, the date and time checked in, the identity of the developer who checked the software component back in, and the nature of the changes made to the software component.

27. A system for controlling code in a multi-developer software development environment, the system comprising:

first means for identifying a plurality of software components as non-modifiable and preventing access and modification to the non-modifiable objects;

second means for receiving a request from a requesting user to modify one of the software components;

third means for determining whether the software component has been checked out by another user;

fourth means for providing the requesting user with a modifiable copy of the one of the software component if the software component has not been checked out by another user.

28. The system as recited in claim 27, further comprising:

fifth means for presenting the requesting user with an indication that the software component has been checked out by another user and is not available for modification if the object has been checked out by another user.

29. The system as recited in claim 27, further comprising:

fifth means for creating a backup copy of the software component prior to providing the user with a modifiable copy of the software component.

30. The system as recited in claim 27, further comprising:

fifth means for updating a file indicating that the software component is checked out, the identity of the user that checked out the software component, the date the software component was checked out, and the time the software component was checked out.

31. The system as recited in claim 27, further comprising:

fifth means for prompting the requesting user to provide information about what is intended to be changed in the software component.

32. The system as recited in claim 31, further comprising:

sixth means for updating a file indicating the changes intended to be made to the software component.

33. The system as recited in claim 27, wherein the software component is an object.

34. The system as recited in claim 30, wherein the file is one of a table and a database.

35. The system as recited in claim 32, wherein the file is one of a table and a database.

36. The system as recited in claim 28, further comprising:

sixth means for determining whether the requesting user wishes to send a message to the user who currently has the object checked out;

seventh means for prompting the requesting user to indicate the message to be sent to the user who currently has the software component checked out; and

eighth means for sending the message to the user who currently has the software component checked out.

37. The system as recited in claim 36, further comprising:

ninth means for determining the system the requesting user wished the message to be sent to the user who currently has the software component checked out; and

tenth means for sending the message by the system specified by the requesting user.

38. The system as recited in claim 27, further comprising:

fifth means for determining that the requesting user requests to check the software component back in;

sixth means for prompting the requesting user to enter a description of what has changed to the software component; and

seventh means for saving an updated software component, indicating that the software component is checked in, and indicating that the software component is not modifiable.

39. The system as recited in claim 38, further comprising:

eighth means for updating a file indicating that the software component is checked back in, the date and time checked in, the identity of the developer who checked the software component back in, and the nature of the changes made to the software component.