Change management for structure objects
A structure object is locked to prevent changes to the structure object in previous phases of a software life cycle. When a request to change the structure object in a previous phase is received, a change request file is opened. The changed request is approved or denied based at least in part on the previous phase. If the changes request is approved, a document is generated for the change request. Any changes made to the structure object are integrated into the previous phase of the structure object and are also stored in the document. If the change request is denied, the change request file is closed.
1. A computer-implemented method for managing changes to a project during a software life-cycle, the method comprising:
creating a plurality of phases representing a project, the phases ordered in time, each phase organized into objects, the objects belonging to one or more phases;
locking the objects in a previous phase to prevent changing the objects in the previous phase during subsequent phases of the project;
receiving a request to change an object in the previous phase during a subsequent phase of the project;
opening a change request file that identifies the object in the previous phase and for which the request was received;
determining whether to approve the change request based on the previous phase, wherein the change request is approved depending on how many phases have transpired between the previous phase and the subsequent phase during which the change request is received; and
if the change request is approved,
generating a document for the change request file,
storing one or more changes in the document,
unlocking the object in the previous phase, and
integrating the one or more changes into the object in the previous phase,
else, closing the change request file.
2. The method of claim 1 , wherein the change request is approved when the previous phase of the object for which the change request was received immediately precedes the subsequent phase during which the change request is received.
3. The method of claim 2 , wherein the request to change the object includes a selection of one or more associated objects assigned to the object.
4. The method of claim 3 , wherein determining whether to approve the change request further comprises determining whether to approve the change request based at least in part on the previous phase and the selection of the one or more associated objects.
5. The method of claim 1 , wherein the object comprises one of a scenario, a process, a master data object, and an organizational unit.
6. The method of claim 3 , wherein the one or more associated objects comprise at least one of a document, a configuration item, and a test case.
7. The method of claim 1 , wherein the change request file is an existing change request file.
8. An article of manufacture comprising a computer-readable storage medium having content stored thereon to provide instructions to result in an electronic device performing operations including:
creating a plurality of phases representing a project, the phases ordered in time, each phase organized into objects, the objects belonging to one or more phases;
locking the objects in a previous phase to prevent changing the objects in the previous phase during subsequent phases of the project;
receiving a request to change an object in the previous phase during a subsequent phase of the project;
opening a change request file that identifies the object in the previous phase and for which the request was received;
determining whether to approve the change request based on the previous phase, wherein the change request is approved depending on how many phases have transpired between the previous phase and the subsequent phase during which the change request is received; and
if the change request is approved,
generating a document for the change request file,
storing one or more changes in the document,
unlocking the object in the previous phase, and
integrating the one or more changes into the object in the previous phase,
else, closing the change request file.
9. The article of manufacture of claim 8 , further having content to provide instructions to result in the electronic device performing additional operations including:
wherein the change request is approved when the previous phase of the object for which the change request was received immediately precedes the subsequent phase during which the change request is received.
10. The article of manufacture of claim 9 , wherein the request to change the object includes a selection of one or more associated objects assigned to the object.
11. The article of manufacture of claim 10 , wherein determining whether to approve the change request further comprises determining whether to approve the change request based at least in part on the previous phase and the selection of the one or more associated objects.
12. The article of manufacture of claim 8 , wherein the object comprises one of a scenario, a process, a master data object, and an organizational unit.
13. The article of manufacture of claim 10 , wherein the one or more associated objects comprise at least one of a document, a configuration item, and a test case.
14. The article of manufacture of claim 8 , wherein the change request file is an existing change request file.
15. A computer system for managing changes to a project during a software life-cycle, the system comprising:
a platform distributed over one or more devices in a network, the platform for developing a plurality of phases representing a project, the phases ordered in time, each phase organized into objects, the objects belonging to one or more phases, the platform communicably coupled to a change request management server on the network, the platform and change request management server implementing logic to lock the objects in a previous phase to prevent changing the objects in the previous phase during subsequent phases of the project, wherein responsive to receiving a request to change an object in the previous phase during a subsequent phase of the project; the platform and change request management server implementing logic for further performing:
opening a change request file that identifies the object in the previous phase and for which the request was received;
determining whether to approve the change request based on the previous phase, wherein the change request is approved depending on how many phases have transpired between the previous phase and the subsequent phase during which the change request is received; and
if the change request is approved,
generating a document for the change request file,
storing one or more changes in the document,
unlocking the object in the previous phase, and
integrating the one or more changes into the object in the previous phase,
else, closing the change request file.
16. The system of claim 15 , wherein the change request is approved when the previous phase of the object for which the change request was received immediately precedes the subsequent phase during which the change request is received.
17. The system of claim 16 , wherein the request to change the object includes a selection of one or more associated objects assigned to the object.
18. The system of claim 17 , wherein determining whether to approve the change request further comprises determining whether to approve the change request based at least in part on the previous phase and the selection of the one or more associated objects.
19. The system of claim 17 , further comprising:
an enterprise resource planning system on the network, the enterprise resource planning system communicably coupled to the platform
wherein the platform issues a notification to the change request management server about a problem detected in the enterprise resource planning system;
wherein the platform receives the change request from the change request management server in response to the notification; and
further wherein the platform includes in the change request the selection of the one or more associated objects assigned to the object, the one or more associated objects including a solution object for solving the problem.
20. The system of claim 15 , wherein:
the object comprises one of a scenario, a process, a master data object, and an organizational unit; and
the one or more associated objects comprise at least one of a document, a configuration item, and a test case.