Team support in change recording and versioning systems

• US 8,204,908 B2
• Filed: 11/24/2009
• Issued: 06/19/2012
• Est. Priority Date: 11/24/2009
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Misch, Frank, Sudrow, Karin
• Primary Examiner(s): Coby, Frantz
• Application Number:
  US12/624,702
• Publication Number:
  US 20110125798A1
• Time in Patent Office: 938 Days
• Field of Search: 707/625, 707/612, 707783-788
• US Class Current: 707/783
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Implementations of the present disclosure provide computer-implemented methods including generating a changelist corresponding to at least one computer code object that is digitally stored in a repository database, assigning a team to the changelist, the team comprising a plurality of members, initiating access to the computer code object using a computer that is in communication with the repository database, enabling access to the computer code object when a user of the computer is a member of the team, and prohibiting access to the computer code object when the user of the computer is not a member of the team.

Claims

1. A computer-implemented method, comprising:

generating a changelist corresponding to at least one computer code object that is digitally stored in a repository database;

defining a plurality of development teams, each development team including one or more members including software developers;

assigning a development team of the plurality of development teams to the changelist;

determining that a first user is attempting to access the at least one computer code object using a first computer that is in communication with the repository database;

determining that the first user is a member of the development team;

enabling access to the at least one computer code object by the first user in response to determining that the first user is a member of the development team;

determining that a second user is attempting to access the at least one computer code object using a second computer that is in communication with the repository database;

determining that the second user is not a member of the development team; and

prohibiting access to the at least one computer code object by the second user in response to determining that the second user is not a member of the development team.

2. The method of claim 1, further comprising:

instantiating an editor program at the first computer;

modifying the at least one computer code object using the editor program.

3. The method of claim 1, further comprising:

determining that a third user is attempting to access the at least one computer code object using a third computer;

determining that the third user is a member of the development team;

determining that the first user is currently accessing the at least one computer code object; and

prohibiting access of the third user to the at least one computer code object in response to determining that the first user is currently accessing the at least one computer code object.

4. The method of claim 1, further comprising:

initiating activation of the changelist by a user;

determining that the user initiating the activation is an authorized user; and

activating the changelist in response to determining that the user initiating the activation is an authorized user.

5. The method of claim 4, further comprising:

assigning the user to a role as an activation user; and

determining that the user initiating the activation is an authorized user when the user is assigned as the activation user.

6. The method of claim 1, further comprising:

initiating activation of the changelist by the first user;

alerting a third user that activation has been initiated, the third user being a member of the development team;

generating an approval signal based on an input of the third user; and

activating the changelist upon generation of the approval signal.

7. The method of claim 1, further comprising:

initiating activation of the changelist by the first user;

activating objects of the changelist that were only modified by the first user;

initiating activation of the changelist by a third user, the third user being a member of the development team;

activating objects of the changelist that were only modified by the third user; and

activating objects of the changelist that were modified by the first and third users.

8. A computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

generating a changelist corresponding to at least one computer code object that is digitally stored in a repository database;

defining a plurality of development teams, each development team including one or more members including software developers;

assigning a development team of the plurality of development teams to the changelist;

determining that a first user is attempting to access the at least one computer code object using a first computer that is in communication with the repository database;

determining that the first user is a member of the development team;

enabling access to the at least one computer code object by the first user in response to determining that the first user is a member of the development team;

determining that a second user is attempting to access the at least one computer code object using a second computer that is in communication with the repository database;

determining that the second user is not a member of the development team; and

prohibiting access to the at least one computer code object by the second user in response to determining that the second user is not a member of the development team.

9. The computer-readable storage medium of claim 8, wherein the operations further comprise:

instantiating an editor program at the first computer; and

modifying the at least one computer code object using the editor program.

10. The computer-readable storage medium of claim 8, wherein the operations further comprise:

determining that a third user is attempting to access the at least one computer code object using a third computer;

determining that the third user is a member of the development team;

determining that the first user is currently accessing the at least one computer code object; and

prohibiting access of the third user to the at least one computer code object in response to determining that the first user is currently accessing the at least one computer code object.

11. The computer-readable storage medium of claim 8, wherein the operations further comprise:

initiating activation of the changelist by a user;

determining that the user initiating the activation is an authorized user; and

activating the changelist in response to determining that the user initiating the activation is an authorized user.

12. The computer-readable storage medium of claim 11, wherein the operations further comprise:

assigning the user to a role as an activation user;

determining that the user initiating the activation is an authorized user when the user is assigned as the activation user.

13. The computer-readable storage medium of claim 8, wherein the operations further comprise:

initiating activation of the changelist by the first user;

alerting a third user that activation has been initiated, the third user being a member of the development team;

generating an approval signal based on an input of the third user; and

activating the changelist upon generation of the approval signal.

14. The computer-readable storage medium of claim 8, wherein the operations further comprise:

initiating activation of the changelist by the first user;

activating objects of the changelist that were only modified by the first user;

initiating activation of the changelist by a third user, the third user being a member of the development team;

activating objects of the changelist that were only modified by the third user; and

activating objects of the changelist that were modified by the first and third users.

15. A system, comprising:

a database having a plurality of computer code objects stored thereon; and

a plurality of computers that are in communication with the database to enable respective users of the computers to access the objects; and

one or more processors operable to execute instructions to cause the one or more processors to perform operations comprising;

defining a plurality of development teams, each development team including one or more members including software developers;

assigning a development team of the plurality of development teams to a changelist;

determining that a first user is attempting to access the at least one computer code object using a first computer that is in communication with the repository database;

determining that the first user is a member of the development team;

enabling access to the at least one computer code object by the first user in response to determining that the first user is a member of the development team;

determining that a second user is attempting to access the at least one computer code object using a second computer that is in communication with the repository database;

determining that the second user is not a member of the development team; and

prohibiting access to the at least one computer code object by the second user in response to determining that the second user is not a member of the development team.

16. The system of claim 15, wherein the operations further comprise:

instantiating an editor program at the first computer; and

modifying the at least one computer code object using the editor program.

17. The system of claim 15, wherein the operations further comprise:

determining that a third user is attempting to access the at least one computer code object using a third computer;

determining that the third user is a member of the development team;

determining that the first user is currently accessing the at least one computer code object; and

prohibiting access of the third user to the at least one computer code object in response to determining that the first user is currently accessing the at least one computer code object.

18. The system of claim 15, wherein the operations further comprise:

initiating activation of the changelist by a user;

determining that the user initiating the activation is an authorized user; and

activating the changelist in response to determining that the user initiating the activation is an authorized user.

19. The system of claim 18, wherein the operations further comprise:

assigning the user to a role as an activation user;

determining that the user initiating the activation is an authorized user when the user is assigned as the activation user.

20. The system of claim 15, wherein the operations further comprise:

initiating activation of the changelist by the first user;

alerting a third user that activation has been initiated, the third user being a member of the development team;

generating an approval signal based on an input of the third user; and

activating the changelist upon generation of the approval signal.

21. The system of claim 15, wherein the operations further comprise:

initiating activation of the changelist by the first user;

activating objects of the changelist that were only modified by the first user;

initiating activation of the changelist by a third user, the third user being a member of the development team;

activating objects of the changelist that were only modified by the third user; and

activating objects of the changelist that were modified by the first and third users.