IT question and answers

Generic Change Management Cycle

The generic Change Management Cycle can be compehensively described for any organisation running an RDBMS and attendant (Third Level) applications software products (A, B, C, etc) as a cyclical process with eleven distinct phases, many of them significantly cost incurring to the organisation. Whereas the cycles of change within the 1st and 2nd level software environments are usually of long period (eg: an upgrade to these environments may occur once every few years), the cycle of change management within the applications environment is often of substantially smaller duration (eg: a few times each year, and more in rapidly developing applications environments). The following schematic outlines these eleven phases or steps that characterise the cyclic nature of change management in the applications software environment. At the center of the flowchart, depicted as a number of large sets of boxes, is shown the atomic nature of the actual program objects physically loaded into this environment. These program objects A1 to An, B1 to Bn, etc, are the constituent program code for the packages A, B, etc. As mentioned earlier in this series of articles, a few decades ago these objects would have been largely Cobol programs. In todays world, these program objects could have been developed by any one of a large number of modern program development tools. While the applications software environment may already have been rewritten any number of times in various new technologies of program development tools, the fact remains that its physical and theoretical nature has not substantially changed over the decades. The objects amassed in the center of the flowchart below might change their form and their inner language and expressionisms, but in terms of acting as an interface between the people of the organsation and the RDBMS, nothing much has altered, as the following diagram will clearly show: