System for relating workflow status to code component status in a software project

• US 8,341,590 B1
• Filed: 12/12/2007
• Issued: 12/25/2012
• Est. Priority Date: 12/12/2007
• Status: Expired due to Fees

• Current Assignee: Accurev Incorporated (Open Text Corporation)
• Original Assignee: Accurev Incorporated (Open Text Corporation)
• Inventors: Poole, Damon B.
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): Nguyen, Duy Khuong
• Application Number:
  US12/001,710
• Time in Patent Office: 1,840 Days
• Field of Search: 717/101, 717120-122
• US Class Current: 717/101
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Embodiments of the invention are directed to a configuration management (CM) system, method, and product adapted to carry out workflow management tasks, which integrates status of software projects and issues, such that software projects may be more easily and reliably tracked and management of software projects may be streamlined. In some embodiments of the invention, a CM system is adapted to maintain records of software projects and/or issues managed by the CM system, the records comprising an indicator of a workflow progress stage for the project/issue. The CM system may be further adapted to update concurrently and automatically, according to an input from a user, both (1) a workflow progress stage value for the project/issue and (2) a record for software code associated with a project/issue, the record for the software code indicating a version and the project/issue in which the version is included.

Claims

1. A method for associating a workflow transition and a version of a software project, the workflow transition indicating a relationship between workflow stages of an associated workflow, the version of the software project including at least one software component, a status of at least one issue being identified by a workflow stage for the at least one issue, each issue of the at least one issue corresponding to a software development task and corresponding to one or more software components, the method comprising computer-implemented acts of:

A) accepting a first indication of the workflow transition of the associated workflow, said workflow transition to be associated with the version of the software project, such that a change is made to one or more software components of the version of the software project when the workflow transition is applied to an issue corresponding to the software components;

B) accepting a second indication of the version of a software project, wherein the version of the software project is to be associated with the workflow transition such that the workflow transition is applied to an issue when at least one software component of the version of the software project is promoted to a second version of the software project; and

C) storing information in at least one computer-readable storage medium identifying a relationship between the workflow transition and the version, the relationship identifying the version as an originating version for software components to be promoted when the workflow transition is applied to an issue corresponding to the software components and identifying the workflow transition as an action to be taken on an issue when a software component corresponding to the issue is promoted from the version,

wherein the at least one computer-readable storage medium stores information regarding the version as at least one data structure comprising information describing the version of the software project and describing the at least one software component included in the version of the software project.

2. The method of claim 1, further comprising accepting from a user an indication of the software project with which version is associated.

3. The method of claim 1, further comprising identifying a workflow for the software project, the workflow comprising a plurality of workflow stages and at least one workflow transition.

4. The method of claim 1, wherein the first indication and the second indication are accepted from a user.

5. The method of claim 4, wherein the first indication and the second indication are accepted from the user via a graphical user interface.

6. The method of claim 4, wherein the information stored in the at least one computer-readable storage medium comprises data accepted from the user as the first indication and the second indication.

7. The method of claim 1, wherein the version is implemented as a stream.

8. The method of claim 1, wherein the information is stored in an Extensible Markup Language (XML) file.

9. The method of claim 1, wherein the information is stored in a database.

10. The method of claim 1, wherein the acts of accepting the first indication, accepting the at least one second indication, and storing are performed via at least one processor.

11. The method of claim 1, wherein:

accepting the second indication comprises accepting a second indication of the version of the software project and the second version of the software project; and

storing the information in the at least one computer-readable storage medium identifying the relationship comprises storing information identifying the version as an originating version for software components to be promoted when the workflow transition is applied to an issue corresponding to the software components and identifying the second version as a destination version for the software components that are to be promoted when the workflow transition is applied.

12. The method of claim 11, wherein storing the information in the at least one computer-readable storage medium identifying the relationship comprises storing information identifying the workflow transition as an action to be taken on an issue when a software component corresponding to the issue is promoted from the version to the second version.

13. A computer-implemented method for transitioning an issue in a workflow of a software development effort based on a change made to at least one software component corresponding to the issue, the method comprising:

A) identifying as an originating version for a promotion operation a first version of a software project comprising the at least one software component corresponding to the issue and identifying as a destination version for the promotion operation a second version of the software project;

B) promoting the at least one software component such that the second version of the software project comprises the at least one software component;

C) determining whether the first version and/or the second version is associated with a workflow transition such that the workflow transition should be applied when a promotion involving the first version and/or the second version is carried out; and

D) when the first version and/or the second version is associated with a workflow transition, applying the associated workflow transition to the issue to transition the issue in the workflow from a first workflow stage to a second workflow stage, wherein applying the associated workflow transition comprises editing a workflow status for the issue stored in at least one computer-readable storage medium,

wherein the at least one computer-readable storage medium stores information regarding the first version as at least one data structure comprising information describing the first version of the software project and describing the at least one software component included in the first version of the software project.

14. The method of claim 13, wherein editing the workflow status of the issue comprises writing values to one or more fields of a data structure associated with the issue.

15. The method of claim 14, wherein writing values to one or more fields of a data structure associated with the issue comprises editing a value stored in a field of the one or more fields.

16. The method of claim 13, wherein promoting the at least one software component comprises editing at least one software component data structure associated with the at least one software component to indicate that the software component is included in the second version.

17. The method of claim 13, wherein the first version is implemented as a stream.

18. The method of claim 13, wherein the acts of identifying, promoting, determining, and applying are performed via at least one processor.

19. A computer-implemented method for promoting at least one software component from a first version of a software project to a second version of the software project based on a change made to an issue to which the at least one software component corresponds, the method comprising:

A) applying a workflow transition to the issue to move the issue from a first workflow stage of the workflow to a second workflow stage of the workflow;

B) determining whether the workflow transition is associated with a first version of the software project and/or a second version of the software project such that a promotion operation should be performed using the first version as an originating version and/or the second version as a destination version when the workflow transition is applied; and

C) when it is determined that the workflow transition is associated with the first version and/or the second version of the software project, promoting at least one software component corresponding to the issue from the first version to the second version of the software project such that the second version of the software project comprises the at least one software component, wherein promoting the at least one software component comprises editing at least one data structure, stored in at least one computer-readable storage medium, that stores information regarding a version of the software project that includes the at least one software component,

wherein the at least one computer-readable storage medium stores information regarding the first version as at least one data structure comprising information describing the first version of the software project and describing the at least one software component included in the first version of the software project.

20. The method of claim 19, wherein promoting the at least one software component from the first version to the second version of the software project comprises associating in a data structure the at least one software component with the second version of the software project.

21. The method of claim 20, wherein associating in a data structure the at least one component with the second version of the software project comprises editing at least one software component data structure associated with the at least one software component to indicate that the software component is included in the second version.

22. The method of claim 19, wherein applying the workflow transition to the issue comprises:

retrieving from the at least one computer-readable storage medium first information regarding at least one action to be taken when the workflow transition is applied, wherein the at least one action comprises prompting a user for a value of a property of the issue.

23. The method of claim 22, wherein the property is an assigned user for the issue and the value is an indicator of the user to which the issue is assigned.

24. The method of claim 19, wherein promoting at least one software component from the first version to the second version comprises associating the at least one software component with a version of the software project one hierarchical level above the first version that is associated with the workflow transition.

25. The method of claim 19, wherein the first version is implemented as a stream.

26. The method of claim 19, wherein the acts of applying, determining, and promoting are performed via at least one processor.

27. An apparatus for use in managing a software development effort, the software development effort comprising a plurality of software components associated with a plurality of versions of a software project, each of the plurality of versions comprising an instance of at least one software component, the software development effort further comprising one or more issues associated with a workflow, each said issue of the one or more issues corresponding to a software development task to be performed for the software development effort and corresponding to one or more software components of the plurality of software components related to the software development task, wherein the workflow associated with the one or more issues includes a plurality of workflow stages and one or more workflow transitions indicating a relationship between workflow stages and each issue is associated with a workflow stage, the apparatus comprising:

at least one processor; and

at least one computer-readable medium storing information comprising processor-executable instructions and data, the data identifying a relationship between a first workflow transition of the one or more workflow transitions and a first and second version of the plurality of versions of the software project,

wherein the data identifies a first version of the software project as a source for software components to be promoted to a second version of the software project when a first workflow transition is applied to an issue that corresponds to the software components and identifies the first workflow transition as an action to be taken on the issue corresponding to the software components when the software components of the first version are promoted to the second version, and

wherein the processor-executable instructions, when executed by the at least one processor, cause the at least one processor to carry out a method, the method comprising

(a) upon detecting a promotion operation that promotes the software components of the first version to the second version, determining, from a review of the data of the at least one computer-readable medium, that the first workflow transition is an action to be taken when software components of the first version are promoted and, in response to the determining, applying the first workflow transition to the issue corresponding to the software components, and

(b) upon detecting a transition operation that applies a workflow transition to the issue, determining, from a review of the data of the at least one computer-readable medium, that software components of the first version should be promoted to the second version when the first workflow transition is applied and, in response to the determining, promoting the software components corresponding to the issue from the first version to the second version.

28. The apparatus of claim 27, wherein the method further comprises:

receiving input from a user identifying the relationship between first workflow transition, the first version, and the second version.

29. The apparatus of claim 27, wherein promoting the software components corresponding to the issue comprises associating in a data structure the software components corresponding to the issue with the second version of the software project different from the first version.

30. The apparatus of claim 27, wherein applying the first workflow transition to the issue comprises writing values to one or more fields of a data structure stored in the at least one computer-readable medium and associated with the issue.

31. The apparatus of claim 27, wherein the data stored on the at least one computer-readable medium further comprises first information describing at least one version of the software project and second information describing a workflow associated with the workflow transition.