PROJECT SPECIFIC SOFTWARE DELIVERY PLANNING
Various embodiments of systems and methods for project specific software delivery planning are described herein. Development objects used by development projects and dependent development objects that depend on one or more of the development objects are determined. Dependency levels are assigned to the development projects based on one or more of the development objects that cause dependency. The dependency levels comprise a first dependency level indicating two or more of the development projects changed a same development object and a second dependency level indicating a first development object changed by a first development project depends on a second development object changed by a second development project. A list of the development projects, the dependency levels assigned to the development projects, and the development objects causing the dependency are then displayed.
1 . An article of manufacture including a computer readable storage medium to tangibly store instructions, which when executed by a computer, cause the computer to:
determine development objects used by development projects;
determine dependent development objects that depend one or more of the development objects;
assign dependency levels to the development projects based on one or more of the development objects that cause dependency, the dependency levels comprising:
a first dependency level indicating two or more of the development projects changed a same development object; and
a second dependency level indicating a first development object changed by a first development project depends on a second development object changed by a second development project; and
display a list of the development projects, the dependency levels assigned to the development projects, and the development objects causing the dependency.
2 . The article of manufacture of claim 1 , further comprising instructions which when executed by the computer further causes the computer to:
collect development transports to determine which of the development objects belong to which of the development projects.
3 . The article of manufacture of claim 1 , further comprising instructions which when executed by the computer further causes the computer to:
assign the development projects to a same shipment cluster if the development projects belong to a same development wave and dependent under the first dependency level or the second dependency level; and
assign an installation precondition between the development projects if the development projects belong to different development waves and dependent under any of the dependency levels.
4 . The article of manufacture of claim 3 , further comprising instructions which when executed by the computer further causes the computer to:
display the shipment cluster assignment and the installation precondition assignment for the development projects.
5 . The article of manufacture of claim 1 , wherein the dependency levels further comprises a third dependency level indicating that one or more of the development projects depend on a same unchanged development object which depends on another development object changed by another development project.
6 . The article of manufacture of claim 5 , wherein the dependency levels further comprises a fourth dependency level indicating that two or more of the development projects use one or more same unchanged development objects.
7 . The article of manufacture of claim 6 , wherein the instructions to display the dependency levels further comprise instructions to:
display the development projects using unique graphical identifiers representing the dependency levels.
8 . The article of manufacture of claim 1 , further comprising instructions which when executed by the computer further causes the computer to:
receive an exception to dependency for one or more of the development objects.
9 . A computerized method for software delivery planning, the method comprising:
determining development objects used by development projects;
determining dependent development objects that depend on one or more of the development objects;
assigning dependency levels to the development projects based on one or more of the development objects that cause dependency, the dependency levels comprising:
a first dependency level indicating two or more of the development projects changed a same development object; and
a second dependency level indicating a first development object changed by a first development project depends on a second development object changed by a second development project; and
displaying a list of the development projects, the dependency levels assigned to the development projects, and the development objects causing the dependency.
10 . The method of claim 9 , further comprising:
collecting development transports to determine which of the development objects belong to which of the development projects
11 . The method of claim 9 , further comprising:
assigning the development projects to a same shipment cluster if the development projects belong to a same development wave and dependent under the first dependency level or the second dependency level; and
assigning an installation precondition between the development projects if the development projects belong to different development waves and dependent under any of the dependency levels.
12 . The method of claim 11 , further comprising:
displaying the shipment cluster assignment and the installation precondition assignment for the development projects
13 . The method of claim 9 , wherein the dependency levels further comprises a third dependency level indicating that one or more of the development projects depend on a same unchanged development object which depends on another development object changed by another development project.
14 . The method of claim 13 , wherein the dependency levels further comprises a fourth dependency level indicating that two or more of the development projects use one or more same unchanged development objects.
15 . The method of claim 14 , wherein displaying the dependency levels comprises:
displaying the development projects using unique graphical identifiers representing the dependency levels.
16 . The method of claim 9 , further comprising:
receiving an exception to dependency for one or more of the development objects.
17 . A computer system for software delivery planning, comprising:
a computer memory to store program code; and
a processor to execute the program code to:
determine development objects used by development projects;
determine dependent development objects that depend one or more of the development objects;
assign dependency levels to the development projects based on one or more of the development objects that cause dependency, the dependency levels comprising:
a first dependency level indicating two or more of the development projects changed a same development object; and
a second dependency level indicating a first development object changed by a first development project depends on a second development object changed by a second development project; and
display a list of the development projects, the dependency levels assigned to the development projects, and the development objects causing the dependency.
18 . The system of claim 17 , wherein the processor further executes the program code to:
collect development transports to determine which of the development objects belong to which of the development projects.
19 . The system of claim 17 , wherein the processor further executes the program code to:
assign the development projects to a same shipment cluster if the development projects belong to a same development wave and dependent under the first dependency level or the second dependency level;
assign an installation precondition between the development projects if the development projects belong to different development waves and dependent under any of the dependency levels; and
display the shipment cluster assignment and the installation precondition assignment for the development projects.
20 . The system of claim 17 , wherein the dependency levels further comprise a third dependency level indicating that one or more of the development projects depend on a same unchanged development object which depends on another development object changed by another development project and a fourth dependency level indicating that two or more of the development projects use one or more same unchanged development objects.
21 . The system of claim 20 , wherein the program code to display the dependency levels, further comprises program code to:
display the development projects using unique graphical identifiers representing the dependency levels.
22 . The system of claim 17 , wherein the processor further executes the program code to:
receive an exception to dependency for one or more of the development objects.