Кіріспе
Параллельді қабылдау – ұйымдағы бұрынғы (АҚТ) жүйеден мақсатты (АҚТ) жүйеге көшу әдісі. Тәуекелді азайту мақсатында, ескі және жаңа жүйелер белгілі бір уақыт аралығында бірдей жұмыс істейді, содан кейін жаңа жүйеге қойылатын талаптар орындалса, ескі жүйе тоқтатылады. Бұл процеске мұқият жоспарлау, бақылау және көп еңбек ресурстары жұмсау қажет.
Parallel adoption is a method for transferring between a previous (IT) system to a target (IT) system in an organization. In order to reduce risk, the old and new system run simultaneously for some period of time after which, if the criteria for the new system are met, the old system is disabled. The process requires careful planning and control and a significant investment in labor hours.
Шолу
Бұл жазба параллель қабылдаудың жалпы процесіне тоқталады; (нақты әлемдегі) мысалдар қажет болған жағдайда процесті түсінуді нақтылау үшін пайдаланылады. Процесті визуализациялау үшін процестік деректер моделі қолданылады, ол параллель қабылдаудың барлық қадамдарын толық көрініс беруге бағытталған, бірақ параллель қабылдаудың ерекше ерекшеліктеріне баса назар аударылады. Барлық төрт түрлі қабылдауға ортақ сипаттамалар, әсіресе іске асыру стратегиясын анықтау, «Қабылдау (бағдарламалық қамтамасыз етуді іске асыру)» бөлімінде сипатталған.
This entry focuses on the generic process of parallel adoption; (real world) examples are used for a more meaningful interpretation of the process if necessary. Moreover a process data model is used for visualizing the process which is intended to provide a complete overview of all the steps involved in the parallel adoption, but emphasis will be laid on the unique characteristics of parallel adoption. Some common characteristics, especially defining an implementation strategy, that go for all four generic kinds of adoption are described in Adoption (software implementation).
Бала асырап алудың басқа түрлері
Параллель қабылдаудан басқа, қабылдаудың тағы үш жалпы түрін анықтауға болады. Нақты қабылдау әдісін таңдау ұйымдық сипаттамаларға байланысты; осы тақырып бойынша толыққанды мәліметтер төменде беріледі. Қалған үш қабылдау әдісі:
Үлкен серпіліс қабылдау / Түгелдей ауысу қабылдау: Үлкен серпіліс қабылдау – ұйымның ескі жүйеден жаңа жүйеге бірден, толығымен ауысуын білдіреді. Бұл ең арзан нұсқа, бірақ жаңа жүйе сәтсіз болса, ұйым қиын жағдайға түседі. Сондай-ақ, жүйе пайдаланушылар тарапынан қабылдамауына қауіп бар. Дегенмен, егер екі жүйе бір уақытта жұмыс істей алмайтын болса немесе жаңа жүйені іске қосу шұғыл қажет болса, бұл жалғыз мүмкін тәсіл болуы мүмкін. Кезеңдеп қабылдау (бағытталған түрлендіру деп те аталады): Кезеңдеп қабылдауда ұйым модульдер немесе кіші жүйелер бойынша жаңа жүйеге біртіндеп ауысады. Кейбір жүйелерді бөлік-бөлікпен енгізу мүмкін емес, себебі олар толық жүйеге тым тәуелді. Кезеңдеп қабылдаудың тәуекелі аз, бірақ ескі жүйеден жаңа жүйеге ауысуға ең көп уақыт кететіндіктен, көптеген бұзылыстарға себеп болуы мүмкін. Пілоттық қабылдау: Пілоттық қабылдау әдісі көп филиалдары немесе тәуелсіз бөлімшелері бар ірі ұйымдар үшін қолданылады. Жаңа жүйе бір филиалда немесе бөлімшеде енгізіліп, уақыт өте келе басқа филиалдарға немесе бөлімшелерге таратылады. (жаңа жүйе сәтсіз болған жағдайда шектеулі аумақ) (Турбан, 2002)
Параллель түрлендіруді тиімді түрлендіру стратегиясы ретінде қарастыруға болмайтын бірнеше жағдай бар. Біріншіден, жаңа жүйеде маңызды схемалық өзгерістер бар ма, жоқ па, соны қарастырайық. Бір жүйеге қажет, бірақ екінші жүйеге енгізілмеген дерек элементтері деректердің дұрыс еместігіне, ең нашар жағдайда деректердің бұзылуына әкелуі мүмкін. Тағы бір мәселе – егер жүйе тұтынушыға арналған стандартты технологияға (COTS) сүйенсе. Егер COTS жеткізушісінің құжаттамасында бірнеше қолданба бір деректер базасын бөлісе алмайтыны көрсетілсе, онда параллель түрлендіру мүмкін емес. Мысалы, Oracle компаниясының Siebel өнімдерін қарастыруға болады. Басқа COTS өнімдері де жаңартулар немесе негізгі жаңартулар үшін бірегей лицензиялық кілттерді қажет ететін жағдайларда шектеулер қоюы мүмкін. Олар қолданғаннан кейін деректер базасына өзгерістер енгізе алады, бұл қолданбаға лицензиялық бақылауды айналып өту үшін сол деректер базасына қарсы жұмыс істейтін параллель жүйелерді қате анықтауға және осылайша жүйені тоқтатуға әкелуі мүмкін.
Besides parallel adoption, three other generic kinds of adoption can be identified. The choice for a specific adoption method depends on the organizational characteristics; more insight on this topic will be provided below. The three other adoption methods are:
Big bang adoption/Plunge Adoption: A big bang adoption entails transferring the entire organization from the old system to the new system in an instant changeover. This is the cheapest option but if the new System fails, the organization is in big trouble. It also opens risks for the system not to be accepted by its users. However, this may be the only approach to take when the two systems can not coexist or activating the new system is an emergency. Phased adoption (also known as gradual conversion): In phased adoption implementation, the organization is gradually transferring to a new system in different phases, per module or sub system. Some systems are incapable of being introduced in pieces as it is too reliant on the whole system. Using the phased adoption has less risks, but causes the most disruptions due to it taking the most time to transfer from the old system to the new. Pilot adoption: The pilot adoption method is used for large organizations that have multiple locations or largely independent departments. The new system is introduced in one of the locations or departments and extended to other locations or departments over time. (limited boundary if a new system is a failure) (Turban, 2002)
There are several instances when parallel conversion can not be considered a viable conversion strategy. First consider if the new system contains significant schema changes. Data elements required by one system that are not being populated by the other can lead to at best data inaccuracies and at worst data corruption. Another concern is if the system relies on consumer off the shelf technology (COTS). If a COTS vendor's documentation states that more than one application can not share the same database, then parallel conversion is not an option. An example would be Oracle's Siebel products. Other COTS products may also place restrictions when patches or major upgrades require unique license keys. Once applied they may make database changes that might cause the application to falsely detect a parallel system running against the same database as an attempt at getting around licensing controls and thereby disable the system.
Big bang adoption/Plunge Adoption: A big bang adoption entails transferring the entire organization from the old system to the new system in an instant changeover. This is the cheapest option but if the new System fails, the organization is in big trouble. It also opens risks for the system not to be accepted by its users. However, this may be the only approach to take when the two systems can not coexist or activating the new system is an emergency. Phased adoption (also known as gradual conversion): In phased adoption implementation, the organization is gradually transferring to a new system in different phases, per module or sub system. Some systems are incapable of being introduced in pieces as it is too reliant on the whole system. Using the phased adoption has less risks, but causes the most disruptions due to it taking the most time to transfer from the old system to the new. Pilot adoption: The pilot adoption method is used for large organizations that have multiple locations or largely independent departments. The new system is introduced in one of the locations or departments and extended to other locations or departments over time. (limited boundary if a new system is a failure) (Turban, 2002)
There are several instances when parallel conversion can not be considered a viable conversion strategy. First consider if the new system contains significant schema changes. Data elements required by one system that are not being populated by the other can lead to at best data inaccuracies and at worst data corruption. Another concern is if the system relies on consumer off the shelf technology (COTS). If a COTS vendor's documentation states that more than one application can not share the same database, then parallel conversion is not an option. An example would be Oracle's Siebel products. Other COTS products may also place restrictions when patches or major upgrades require unique license keys. Once applied they may make database changes that might cause the application to falsely detect a parallel system running against the same database as an attempt at getting around licensing controls and thereby disable the system.
Орындау процесіндегі орны
Параллель қабылдау процесіне қатысты нақты келісімдер аз сияқты. Бірнеше дереккөздер (мысалы: Turban, 2002, Eason, 1988, Rooijmans, 2003, Brown, 1999) бір процесті сипаттау үшін бір атауды қолданбайды. Осы дереккөздерде параллель қабылдау термині қолданылады, бірақ әр дереккөз бойынша келесіше аталады: параллель түрлендіру, параллель жұмыс істеу, көлеңкелі жұмыс істеу, параллель ауысу және параллель іске асыру. Бұл, процестің жалпы сипаттамасына ерекше жіктеме қажет болмауынан туындайды. Көптеген стандартты іске асыру әдістері бар, онда әртүрлі қабылдау техникалары сипатталған, бірақ көбінесе практикалық контексте; нақты өмірдегі жағдайлар немесе Regatta сияқты іске асыру техникаларының кеңірек жиынтығы: қабылдау әдісі, SIM және PRINCE2. Жалпы, параллель қабылдауды жаңа жүйені енгізудің жүйелік инженерия әдісі деп қарастыруға болады. Принцип бойынша, параллель қабылдау әдісі ұйымда жүйені өзгерту туралы шешімнен өзгеше және осы мақсатқа жетудің бір жолы ретінде қарастырылуы мүмкін. Дегенмен, ең жақсы іске асыру стратегиясын анықтауда ескерілетін көптеген факторлар бар. Сонымен қатар, сәтті іске асырудың нәтижесі үлкен дәрежеде қабылдау әдісіне байланысты болуы мүмкін. (Ли, 2004)
There seem to be little conventions regarding the process of parallel adoption. Several sources (e. g.: Turban, 2002, Eason, 1988, Rooijmans, 2003, Brown, 1999), do not use a single process description name. The term parallel adoption is denoted in these sources, although consistent per source as: parallel conversion, parallel running, shadow running, parallel cutover and parallel implementation. This appears to be the case because a generic description of the process does not need a distinct classification. There are a quite some standard implementation methods, where different adoption techniques are described but often in a practical context; real world case scenario or a more comprehensive set of implementation techniques like Regatta: adoption method, SIM and PRINCE2. In general, parallel adoption can best be seen as a Systems Engineering method of implementation of a new system. In principle, the parallel adoption method is different from the decision to change a system in an organization and can be seen as one possible mean to achieve that goal. However, there are quite some factors that are being taken into account in determining the best implementation strategy. Moreover, a successful implementation can depend to a big extent on the adoption method. (Lee, 2004)
Процесс
Параллель қабылдау процесін нақты түрлендіруге дейінгі қадамдарға, атап айтқанда түрлендіру сценариін құруға және барлық талаптарды анықтау мен тестілеуге назар аудармай көзге елестетуге болмайды. Сондықтан, процесс 1-суретте көрсетілген анықталған барлық процестерді қарастырып, кез келген анықталған түрлендіру стратегиясы үшін қажетті ортақ іс-шараларды қысқаша қарастырып түсіндіріледі. 1-сурет параллель қабылдау процесінің жалпы көрінісін береді. Сол жақта процеске үлес қосатын іс-шаралар ағыны бейнеленген. Бір мезгілде орындалатын іс-шаралардың алдында қалың қара сызық тұрады. Бір мезгілде жүргізілетін іс-шаралар аяқталғаннан кейін, олар ұқсас қара сызықпен қайтадан біріктіріледі. Егер бір іс-шарадан екіншісіне жебе болмаса, бұл олардың жоғарыда көрсетілген үлкен іс-шараның құрамы екенін көрсетеді. Іс-шаралар төрт негізгі кезеңге бөлінеді: іске асыру стратегиясын анықтау, ол іске асыру стратегиясының түрін қарастырады; алдын ала іске асыру, ол іске асырумен байланысты барлық аспектілер мен талаптарды жоспарлаумен байланысты; ұйымды дайындау – ұйымды алдыңғы кезеңге сәйкес дұрыс дайындау қажет; түрлендіру – нақты түрлендіру процесімен және түрлендіру процесін жабумен, жаңа жүйемен жұмысты жалғастырумен байланысты. Негізгі кезеңдер 1.1 – 1.4 кестелерде қысқаша сипатталатын басқа да іс-шараларға бөлінеді. Модельдің оң жағында процестерге қатысы бар деректер сипатталады. Бұл ұғымдардың кейбіреулері, бір-біріне жабысып тұрған ашық тіктөртбұрыштар жұбы ретінде бейнеленген, бірнеше ұғымға бөлінуі мүмкін. Бір-біріне жабық тіктөртбұрыштар жұбы жабық ұғымды білдіреді, яғни оны бірнеше ұғымға бөлуге болады, бірақ ол параллель қабылдау процесі үшін маңызды емес. Алмаз пішіндес фигура оған байланысты ұғымның жиынтық ұғым ретінде қызмет ететінін және бұл ұғымның басқа ұғымдардан тұратындығын көрсетеді. Соңында, ашық жебе суперкласс-субкласс қатынасын көрсетеді. Жебемен байланысты ұғым оған байланысты ұғымдардың суперкласы болып табылады. 1-суреттегі синтаксис Бірыңғай модельдеу тілі (UML) стандарттарына сәйкес келеді. 1-суреттегі ұғымдар 2-кестеде анықталады. Бұл процестегі осы қосалқы іс-шараларға қосымша мән-жай кестелердің астында беріледі.
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
1-кесте: Іске асыру алдындағы кезең
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Іс-шара сипаттамасы
Іске асыру стратегиясын анықтау Іске асыру стратегиясы осы ерте кезеңде анықталады. (Brown, Vessey, 1999)
Жеткізудің негізгі сценарийін жасау Бірінші кезектегі қажеттіліктерді талдау жасалады, ол төмендегі талаптардан тұрады. (Venture, 2004)
Құрылыс уақытын жоспарлау Іске асыру процесінің алғашқы уақыт жоспары құрылады. (Rooijmans, 2003)
Ұйымдастыру талаптарын анықтау Ұйымдастыру талаптары осы жерде анықталады. (Rooijmans, 2003)
IT талаптарды анықтау IT талаптары анықталады. (Rooijmans, 2003)
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
1.2-кесте: Ұйымды дайындау
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Іс-шара сипаттамасы
Талаптарды орнату Ұйымды дайындау үшін анықталған талаптар орнатылады. Ұйым дайындалып жатыр және IT тест машиналарына орнатылды. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)
Сынақ талаптары Ұйымның іске асыруға дайындығын тексеру үшін талаптарды сынақтан өткізеді. (Rooijmans, 2003)
Басты іске асыру скриптін қайта анықтау Басты іске асыру скриптісі төменде көрсетілген іс-шаралар арқылы процесте жиналған жаңа ақпаратпен жетілдіріледі. (Rooijmans, 2003)
Критерийлік көрсеткіштерді анықтау Жаңа жүйені сынау үшін критерийлік көрсеткіштер жасалуда. (Rooijmans, 2003, Microsoft, 2004)
Амалдандыру/қайта қалпына келтіру жоспарын жасау Сонымен қатар, қайта қалпына келтіру сценарийі бар жұмыс жоспары жасалады. Бұл жоспарлар арқылы ұйым жасалған қателерді түзетуге тырыса алады және егер процестің белгілі бір кезеңінде іске асырылмаса, кері шегіне алады. (Microsoft, 2004, Rooijmans, 2003)
(сегменттік) сынақ түрлендіруін орындау Өте күрделі ұйымдарда "тірі" іске қосылғанға дейін сынақ түрлендіруді орындау пайдалы болуы мүмкін. (Microsoft, 2004, Rooijmans, 2003)
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
1.3-кесте: Түрлендіру
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Іс-шара сипаттамасы
Кезең алу Түрлендіру процесі басталды, бірқатар іс-шаралар қатар жүрді. Бұл кезеңде ескі жүйе бойынша жұмыс жүргізілуде. Ескі жүйе жетекші болып тұр, бірақ жаңасы параллельді жүреді. Жүйедегі барлық өзгерістер жаңа жүйеге енгізілуі тиіс. (Microsoft, 2004, Rooijmans, 2003)
Бақылау жүйесі Жүйе әрдайым бақылау жүйесімен бақыланады. Белгіленген көрсеткіштер мен жүйелік жұмыс сипаттамасы арқылы қателер мен қателер анықталады. (Microsoft, 2004, Rooijmans, 2003)
Ескі жүйені басқару Ескі жүйе басқару; нақты деректерді өңдеу.
Жаңа жүйені іске қосу Жаңа жүйе ескі жүйемен қатар жұмыс істейді және мұқият бақыланады. (Microsoft, 2004, Rooijmans, 2003)
Жаңа жүйеге аударма Егер критерийлер орындалса, аударма жаңа жүйеге көшіріледі, ал түрлендіру процесі келесі кезеңге өтеді. (Microsoft, 2004, Rooijmans, 2003)
Амалдандыру/қайта қалпына келтіру стратегиясын орындау Егер критерийлер орындалмаса, амалдандыру стратегиясы немесе қайта қалпына келтіру стратегиясы орындалады, қателердің сипатына байланысты. (Microsoft, 2004, Rooijmans, 2003)
Кезең алу Жаңа жүйе жетекші болғанда да, қауіпсіздік үшін кезеңдер алынады. (Microsoft, 2004, Rooijmans, 2003)
Ескі жүйені іске қосу Ескі жүйе қауіпсіздік үшін резервтік жүйе ретінде жұмыс істейді.
Жаңа жүйені басқару (1) Жаңа жүйе жетекші және толыққанды жұмыс істейді. Жүйедегі барлық транзакциялар мен өзгерістер осы жерде өңделеді. (Microsoft, 2004, Rooijmans, 2003)
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
1.4-кесте: Параллель қабылдауды жабу
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Іс-шара сипаттамасы
Жаңа жүйені басқару (2) Барлық кезеңдер мен бақылаулар жабылады. Жаңа жүйе – жұмыс істейтін жалғыз жүйе. (Microsoft, 2004, Rooijmans, 2003)
Ескі жүйені өшіру Ескі жүйе енді қажет емес және өшіріледі. (Microsoft, 2004, Rooijmans, 2003)
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
1-суреттегі ұғымдар төмендегі 2.1-кестеде анықталған.
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
2.1-кесте: Ұғымдар анықтамасы
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Ұғым анықтамасы
Іске асыру стратегиясы Жаңа жүйені іске асыру үшін таңдалған стратегия. Опциялар: бірден, кезеңдеп, параллель қабылдау, пилоттық түрлендіру немесе осы төртіншінің комбинациясы. (Turban, 2002, Rooijmans, 2003)
Іске асыру сценарийі Ұйымдық талаптарды, IT талаптарын және алғашқы уақыт жоспарын қамтитын нақты түрлендіру сценарийінің бастапқы нұсқасы. (Venture, 2004, Eason, 1988)
Ұйымдық талаптар Ұйымның ішіндегі сәтті іске асыру үшін болуы керек талаптар. Олар жаңа жүйе үшін ұйымды оптимизациялауды (өзгертуді) қамтиды. Көтерілетін мәселелер: Адам ресурстарын басқару, ұйымдық құрылымды өзгерту және жаңа бизнес құрылымдары. (Rooijmans, 2003)
IT талаптары Ақпараттық технологиялық талаптар – бағдарламалық және аппараттық талаптар, платформа таңдауы, бюджетті және қолданыстағы жүйелерді ескере отырып. (Rooijmans, 2003)
Уақыт жоспары Іс-шараларға олар аяқталуы керек уақыт кезеңі тағайындалған жоспар, қолданыстағы уақытқа қатысты іске асыру жобасының жалпы суретін береді. (Eason, 1988)
Талаптар сәйкестігі Сәйкестік – талаптарды орындау туралы. (ISO 9000)
Түрлендіру сценарийі Талаптарға сәйкестікті ескере отырып қайта қарастырылған іске асыру сценарийі. Сонымен қатар түрлендіру сценарийі амалдандыру және қайта қалпына келтіру жоспарынан тұрады. Түрлендіру сценарийі – іске асыру жобасының жоспары. (Rooijmans, 2003)
Амалдандыру стратегиясы Резервтік жоспар; түрлендіру процесіндегі қателерді болдырмау және оларды жұмыстың айналысына енгізу үшін түрлендіру сценарийінде қолданылатын стратегия, осылайша іске асыру сәтті болуы мүмкін. (Rooijmans, 2003)
Критерийлік көрсеткіштер Талаптарға қатысты сандық және өлшенетін критерийлер, іске асыру процесі сәтті болды ма, жоқ па, анықтау үшін. (Rooijmans, 2003)
Қайта қалпына келтіру…
The parallel adoption process can not be represented without paying attention to the steps before the actual conversion, namely the construction of a conversion scenario and the identification and testing of all the requirements. Therefore the process is explained by going through all the identified processes in figure 1, while addressing the common activities that are necessary for any of the identified conversion strategies briefly. Figure 1 gives an overview of the parallel adoption process. The left side depicts the flow of activities that contribute to the process. Activities that run simultaneously are preceded by a thick black line. When the parallel running of activities is over, the activities are joined again in a similar black line. When there is no arrow from an activity to another, this indicates that they are aggregates of a bigger activity above. The activities are divided in four main phases:
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Define implementation strategy, that deals with the kind of implementation strategy should be executed. Pre implementation, which has to do with constructing a planning of all aspects and requirements involved in the implementation. Prepare organization The organization should be prepared properly according to the previous phase. Conversion deals with the actual conversion process and closing the conversion process; proceeding with the new system. The main phases are subdivided in other activities that will be described briefly in tables 1 1 to 1 4. The right side of the model describes the data involved in the processes. Some of these concepts, depicted as a pair of overlapping open rectangles, can be subdivided in more than one concept. A pair of overlapping closed rectangles indicate a closed concept which means that it can be subdivided in more concepts, but it is not of further interest for the parallel adoption process. The diamond shapes figure indicates that the concept linked to it, serves as an aggregate concept and that this concepts consists of the other concepts. Finally the open arrow represents a super class subclass relation. The concept linked with the arrow is the super class of the concepts that are linked to it. This syntax in figure 1 is according to Unified Modeling Language (UML) standards. The concepts in figure 1 are defined in table 2. More context for these sub activities in the process will be given underneath the tables. table 1 1: Pre implementationActivityDescriptionDefine implementation strategyThe implementation strategy is determined in this early stage. (Brown, Vessey, 1999)Create master implementation scriptThe first initial requirements analysis is made, consisting of the requirements below. (Venture, 2004)Construct Time planningA first time planning of the implementation process is being constructed. (Rooijmans, 2003)Define Organizational requirementsThe organizational requirements are defined here (Rooijmans, 2003). Define IT requirementsIT requirements are determined (Rooijmans, 2003)
table 1 2: Prepare organizationActivityDescriptionInstall requirementsIn order to prepare the organization, the defined requirements are installed. The organization is being prepared and the IT installed on test machines. (Rooijmans, 2003, Eason, 1988, Microsoft, 2004)Test requirementsThe requirements are tested to see if the organization is ready for the implementation (Rooijmans, 2003)Redefine master implementation scriptThe master implementation script is refined with the new information gathered in the process with the activities below. (Rooijmans, 2003)Define criteria indicatorsIn order to test the new system, criteria indicators are being created. (Rooijmans, 2003, Microsoft, 2004)Formulate workaround/rollback planAlso, a workaround plan with a rollback scenario is made. With these plans, the organization can respectively attempt to correct the mistakes that are made and fall back if the implementation in a certain stage of the process fails. (Microsoft, 2004, Rooijmans, 2003)Perform (segmental) Test conversionIn very complex organizations it can be beneficial to perform a test conversion, before going “live”. (Microsoft, 2004, Rooijmans, 2003)
table 1 3: ConversionActivityDescriptionMake catch upsThe conversion process is started, a number of activities run parallel. During this stage, catch ups are being made using the old system. The old system is leading, but the new one runs parallel. All changes in the system, have to be put in the new system. (Microsoft, 2004, Rooijmans, 2003)Control systemThe system is being controlled at all times by the control system. With the defined indicators and system run characteristics, errors and mistakes are tracked down. (Microsoft, 2004, Rooijmans, 2003)Run leading old systemThe old system is leading; processing the actual data. Run new systemThe new system is running parallel with the old system and is closely monitored. (Microsoft, 2004, Rooijmans, 2003)Translate catch ups in new systemIf the criteria are met, the catch ups are translated and transferred in the new system and the conversion process comes in its next stage. (Microsoft, 2004, Rooijmans, 2003)Execute workaround / rollback strategyIf the criteria are not met, the workaround strategy or rollback strategy is performed, depending on the nature of the errors. (Microsoft, 2004, Rooijmans, 2003)Make catch upsCatch ups are made for safety purposes, even when the new system is leading. (Microsoft, 2004, Rooijmans, 2003) Run old systemThe old system runs as a backup, for safety purposesRun leading new system(1)The new system is leading and in full operation. All the transactions and changes in the system are being handled here. (Microsoft, 2004, Rooijmans, 2003)
table 1 4: Closing parallel adoptionActivityDescriptionRun leading new system(2)All catch ups and controls are closed down. The new system is the only system in operation. (Microsoft, 2004, Rooijmans, 2003)Disable old systemThe old system is not necessary anymore and is disabled. (Microsoft, 2004, Rooijmans, 2003)
The concepts from figure 1 are defined in table 2 1 below. table 2 1: Concept definition listConceptDefinitionImplementation strategyThe strategy that will be chosen to implement the new system. The options are big bang, phased, parallel adoption, pilot conversion or a combination of those four. (Turban, 2002, Rooijmans, 2003)Implementation scriptRaw version of the actual conversion scenario, consisting of organizational requirements, IT requirements and an initial time planning. (Venture, 2004, Eason, 1988)Organizational requirementsRequirements from within the organization that should be present for a successful implementation. They deal with optimizing (changing) the organization for the new system. Issues involved can be: Human resources management, changing organograms and new business structures. (Rooijmans, 2003)IT requirementsThe information Technology requirements are the software and hardware requirements, platform choices, taking into account budget and existing systems. (Rooijmans, 2003)Time planningA planning in which activities are assigned a time period wherein they should be completed, providing an overall picture of the implementation project with regard to available time. (Eason, 1988)RequirementsConformityConformity is all about meeting requirements. (ISO 9000)Conversion scenarioThe redefined implementation script, taking into account the conformity to the requirements. Furthermore the conversion scenario consists of a workaround and rollback plan. The conversion scenario is the blueprint of the implementation project. (Rooijmans, 2003)Workaround strategyA backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Rooijmans, 2003)Criteria indicatorsQuantifiable and measurable criteria with regard to the requirements, to determine if the implementation process was successful. (Rooijmans, 2003)Rollback planPlan that facilitates in reversing the direction of the replication in order to go back to the old system without loss in data or information. (Microsoft, 2004)Test conversionSegmental test conversion, before the actual conversion takes place with as goal to be better prepared against uncertainties or problems in the actual conversion process. (Microsoft, 2004)Old systemThe old system: when leading = true; the old system handles the system transactions live:
The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)New systemThe new system (goal): The new system, when leading = true; the new system handles the system transactions live. The principal functioning entities comprising the product, e. g. hardware, software. Also an organized and disciplined approach to accomplish a task, e. g., a failure reporting system (ISO 9000)ControlThe overall control system comprising performance indicators as well as a reliability assessment and catch ups. The control system is very broad and is the central command system of converting the old system and managing the new one during the parallel adoption process. (Rooijmans, 2003, Microsoft, 2004)PerformanceQuantifiable assessment of performance of the old and new system serves as input for the control system. (Rooijmans, 2003)Reliability assessmentA quantitative assessment of the reliability of a product, system or portion thereof. Such assessments usually employ mathematical modeling, directly applicable results of tests on the product, failure data, estimated reliability figures and non statistical engineering estimates. (ISO 9000)Catch upsCatch ups consist of automatically or non automatically created back ups of the system using the old system, to be translated in the new system. (Rooijmans, 2003)Automatic catch upsAutomatically created catch ups (Rooijmans, 2003)Catch up by handCatch ups created by manual input (Rooijmans, 2003)
Жақынырақ іске асыру стратегиясын анықтау
Параллельді қабылдауға кіріспес бұрын іске асыру стратегиясын анықтау қажет, бұл стратегия параллельді қабылдауға ғана тән емес, бірақ ұйымның өзгерістерді басқару процесінің бір бөлігі ретінде қарастырылуы мүмкін. (Ли, 2004). Қабылдау әдістеріне қатысты іске асыру стратегиясын анықтаудағы кейбір факторлар "Қабылдау (бағдарламалық қамтамасты іске асыру)" бөлімінде толығырақ сипатталған.
The parallel adoption is preceded with determining the implementation strategy, which is not unique for parallel adoption, but can be seen as part of the change management process that an organization enters. (Lee, 2004). Some factors involved in determining an implementation strategy regarding adoption methods is described more thoroughly in Adoption (software implementation).
Тәуекел мен шығындар
Ұйымның пилоттық түрлендіру, үлкен серпіліс немесе кезеңдік қабылдаудың орнына параллельді қабылдауды таңдауының себебі көбінесе шығындар мен тәуекел арасындағы теңгерім болып табылады (Андерсон, Хансон, 2003). Параллельді қабылдау – ең қымбат қабылдау әдісі (Chng, Vathanopas, 2002, Microsoft, 2004, Anderson et al., 2003), себебі ол ұйымнан екі жүйені белгілі бір кезеңде параллель жұмыс істеуді талап етеді. Екі жүйені бір уақытта іске қосу адам ресурстарында инвестиция жасауды білдіреді. (Қосымша) персоналды жақсы дайындаумен қатар, олар процедуралардың келісіп жатқан, стрестік параллель жұмыс кезеңінен өтуі керек (Rooijmans, 2003, Eason, 1988). Екі жүйе арасындағы деректердің дұрыстығын қамтамасыз ету және деректердің бұзылуын болдырмау үшін күш-жігер жұмсалуы тиіс (Chng et al. 2002, Yusuf, 2004). Бұл тек түрлендіру процесінде ғана емес, сонымен қатар жаңа жүйемен жұмыс істеуге оларды оқытуда да қажет. Егер жаңа жүйені үлкен серпіліс әдісімен енгізу қажет болса, сәтсіздікке ұшырау қаупі жоғары (Ли, 2004). Егер ұйым ескі (мұражайлық) жүйені өзгертуді қажет етсе, азайтылған тәуекелге ие параллельді тәсілге байланысты қосымша шығындарды қарастыру керек (Ли, 2004), дегенмен, ERP жүйесін қабылдаудың көп жағдайы үлкен серпіліс қабылдаудан кейін жүзеге асырылады (Microsoft, 2004, Yusuf, 2004). Бұл ұйым өз іске асыру стратегиясы туралы мұқият ойлануы және осы шешімді тәуекелдерді басқару немесе өзгерістерді басқару талдауына енгізуі керек екенін білдіреді.
The reason for an organization to choose for parallel adoption in favour of a pilot conversion, big bang or phased adoption is often a trade off between costs and risk (Andersson, Hanson, 2003). Parallel adoption the most expensive adoption method (Chng, Vathanopas, 2002, Microsoft, 2004, Anderson et al., 2003), because it demands from the organization that two systems run parallel for a certain period. Running two systems simultaneously means that an investment in Human Resources has to be made. Besides a good preparation of the (extra) personnel, that has to go through a stressful period of parallel running where procedures cross each other. (Rooijmans, 2003, Eason, 1988) Efforts should be placed on data consistency and preventing data corruption between the two systems. (Chng et al. 2002, Yusuf, 2004 ) Not only for the conversion process itself, but also in training them for handling the new system. When it is necessary for the new system to be implemented following a big bang approach, the risk of failure is high (Lee, 2004). When the organization demands heavily on the old (legacy) system to be changed, the trade off between extra involved costs for a less risky parallel approach, should be in favour of those extra costs (Lee, 2004), despite this, we see that ERP adoption follows a big bang adoption in most cases (Microsoft, 2004, Yusuf, 2004). This means that an organization should think clearly about their implementation strategy and integrate this decision in their Risk management or Change management analysis.
IT-талаптар
Ұйымды тиісті түрде дайындау үшін IT және ұйымдық талаптардың екеуінің де талаптар талдауы қажет. Талаптарды талдау және өзгерістерді басқару туралы толық ақпаратты басқа жерден табуға болады. Параллель енгізу үшін ең маңызды IT талабы (қажет болған жағдайда) екі жүйені бір уақытта іске қосуға назар аудару болып табылады. Ауысу кезеңінде ескі жүйенің басты жүйе болып табылатын уақыт терезесі болады. Ескі жүйеден деректерді жаңа жүйеге ауысу кезеңінде көшіру үшін ауысу модулі болуы керек (Microsoft, 2004). Басқа енгізу әдістерінде мұндай талап тікелей көзделмеген. IT талаптары туралы толық ақпаратты Бағдарламалық инженериядан табуға болады.
To prepare the organization properly a requirements analysis of both IT requirements as well as organizational requirements is necessary. More information on requirements analysis and change management can be found elsewhere. For parallel adoption, the most important IT requirement (if applicable) is attention for running the two systems simultaneously. In the conversion phase there is a timeslot, where the old system is the leading system. In order to transfer the data from the old system in the catch up period to the new system, there must be a transition module available (Microsoft, 2004). Other implementation methods do not directly have this requirement. More information about IT requirements can be found in Software Engineering.
Уақытты жоспарлау
Ұйымда жаңа жүйені енгізудің толыққанды жоспары болуы өте маңызды (Ли, 2004, Эсон, 1988). Параллель түрлендіруді уақыт бойынша жоспарлаудың ең маңыздысы – асығудан аулақ болу және нақты түрлендіру кезеңіндегі мүмкін болатын кешігулерден сескенбеу. (Ли, 2004). PRINCE2 әдісіне ұқсас, анық белгіленген кезеңдермен жұмыс істеу де пайдалы болуы мүмкін (Rooijmans, 2003). Уақытты жоспарлау туралы толық ақпаратты «Жоспарлау» және «Стратегиялық жоспарлау» бөлімдерінде табуға болады.
It is very important to have a detailed plan of conducting the new system in an organization (Lee, 2004, Eason, 1988). The most important thing about time planning for a parallel conversion is not to rush things and not be afraid of possible delays in the actual conversion phase. (Lee, 2004). It can be very beneficial also to work with clearly defined milestones (Rooijmans, 2003), similar to the PRINCE2 method. More information on time planning can be found in Planning and Strategic planning.
Талаптарды бағалау
Талаптарды бағалау іске асыру жоспарын қайта қарауды қамтиды. ІТ және (мүмкін болса) ұйымдық талаптар тексерілуі керек. Кейбір тесттер ұйымдық жауапкершіліктерді (Rooijmans, 2003) және ІТ талаптарын бағалау үшін жүргізілуі мүмкін. Мұнда да жоғары басшылықтың қолдауы мен қатысуы өте маңызды (Eason, 1988). Егер олар бағалау үшін ресурстар бөлмесе, іске асыру тікелей салдарынан сәтсіз аяқталуы мүмкін. Осы бағалаудан кейін іске асыру жоспары нақтырақ түрлендіру сценарийі ретінде қайта қаралады.
The requirements evaluation involves redefining the implementation script. The IT and (if possible) organizational requirements that were made should be tested. Some tests can be run where the organizational responsibilities can be evaluated (Rooijmans, 2003) as well as the IT requirements. Here it is also again important to have top management support and involvement (Eason, 1988). If they do not make resources available to evaluate, the implementation can be unsuccessful as a direct consequence. After this evaluation the implementation script is redefined into a more explicit conversion scenario.
Қайта құру сценарийі
Осылайша, түрлендіру сценарийі барлық аспектілердегі ұйымдық өзгерістердің жобалық жоспары болып табылады. Дегенмен, параллель енгізу аясында екі мәселеге әлі толық назар берілген жоқ. Шешім табу стратегиясы / кері қайтару жоспары: Басқа енгізу сценарийлерінен өзгеше, түрлендіру сценарийіне де шешім табу немесе резервтік стратегия және кері қайтару жоспары кіріктірілген. Шешім табу стратегиясы басқа жазбада кеңірек сипатталған, бірақ осы контексте жоғарыдағы кестеде көрсетілгендей: резервтік жоспар; түрлендіру процесіндегі қателерді алдын алу және оларды жою үшін түрлендіру сценарийінде қолданылатын стратегия, осылайша іске асыру сәтті болуы мүмкін. (Microsoft, 2004). Кері қайтару жоспары – бұл шешім табу стратегиясының бірі, егер түрлендіру кезеңінде қандай да бір мәселе туындаса, ол қолданылады. Екі жүйе параллель жұмыс істейтіндіктен, кері қайтару жоспары транзакцияларды өңдейтін деректер базасы немесе басқа да жүйенің бұрынғы жүйеде толыққанды қалпына келтіріле алатындығын көрсетеді (Microsoft, 2004). Шындығында, параллель енгізу өзінің басты жүйе және (қосалқы) резервтік жүйе ретіндегі табиғатына байланысты осы кері қайтару жоспарын қамтамасыз етеді. Критерийлер индикаторлары: Түрлендіру сценарийі екі жүйені алмастырудың жобалық жоспары болғандықтан, ол сандық критерийлерді де қамтиды. Жаңадан анықталған IT және ұйымдық талаптар өлшенетін компоненттерге айналдырылуда. Егер сынақ түрлендіру кезінде критерийлер орындалмаса, шешім табу стратегиясы қолданылуы керек.
The conversion scenario thus consists of a blueprint for the organizational change in all aspects. However, there are two topics that did not yet get the attention they deserve in the parallel adoption scope. Workaround strategy / Rollback plan: Being distinct from the other adoption scenarios, also integrated in the conversion scenario is the workaround or contingency strategy with a rollback plan. The workaround strategy is defined in a broader scope in another entry, but in this context it indicates as defined in the above table: A backup plan; strategy taken on, in the conversion scenario to prevent errors in the conversion process and attempt to work around them, so that the implementation can still be successful. (Microsoft, 2004). The rollback plan, as being one possible workaround strategy, is initiated if something goes wrong in the conversion phase. Since the two systems run simultaneously, in a parallel adoption, the rollback plan indicates that the database or other system that handles the transactions should be fully retraceable in the legacy system (Microsoft, 2004). In fact the parallel adoption provides per definition this rollback plan due to its nature of a leading system and a (non leading) backup system. Criteria indicators: Since the conversion scenario is a blueprint of executing the transfer of the two systems, is also entails quantifiable criteria. The redefined IT and organizational requirements are being transferred into measurable components. When the criteria are not being met in the test conversion, the workaround strategy should be deployed.
Қайта құру
Қазір нақты ауысу кезеңі іске қосылды. Осы процесте ұйым стрестік кезеңді бастан өткереді (Eason, 1988, Rooijmans, 2003). Екі жүйе де ауысу сценарийына сәйкес параллель жұмыс істейді және жаңа жүйе тығыз бақыланады. Жаңа жүйенің критерийлері орындалғанда, ескі жүйе басты жүйе болуын тоқтатады және жаңа жүйе оның орнына келеді. Шешімді жаңарту стратегиясының бөлігі болып табылатын ескі жүйенің резервтік көшірмелері сенімділік инженериясы және деректерді қалпына келтіру үшін мүмкіндіктер береді. Жаңартудың екі түрі бар: автоматты жаңарту және қолмен жаңарту. (Rooijmans, 2003). Қажет болған жағдайда, қашықтықтан резервтік қызметін де пайдалануға болады.
The actual conversion phase is now in place. During this process, the organization is in a stressful period (Eason, 1988, Rooijmans, 2003). The two systems run parallel according to the conversion scenario and the new system is being monitored closely. When the criteria of the new system are met, the old system will cease being the leading system and the new system takes over. The catch ups that are part of the workaround strategy are the back ups of the old system and provide the means for reliability engineering and data recovery. There are two kinds of ways to make catch ups: automatic catch ups and catch ups by hand. (Rooijmans, 2003). If applicable a remote backup service can be deployed as well.
Басқару жүйесі
Автоматты жинақтау: Ұйымды дайындау кезеңінде құрылған автоматтандырылған жүйе арқылы жүзеге асырылатын жинақтаулар. Бұл жүйе ескі басқару жүйесінен жаңа басқару жүйесіне көшкен кезде деректерді немесе ақпаратты автоматты түрде жаңа жүйеге ауыстырады. Автоматтандырылған жүйенің артықшылығы – оның жылдамдығы мен дәлдігі. Кемшілігі – бастапқы кезеңде деректерді ауыстыру жүйесін жасауға уақыт кетеді. Қолмен жинақтау: Егер нақты көшіруге аз уақыт кетсе немесе жаңа жүйеге ауыстырылатын ақпараттың күрделілігі төмен болса, ұйым жинақтауларды қолмен ауыстыруды таңдауы мүмкін. Бұл әдістің артықшылығы – ақпаратты ауыстыру үшін жүйеге (бағдарламаға) қажеттілік болмайды және мұндай бағдарламамен байланысты болатын проблемалардың алдын алуға болады. Бірақ мұнда дәлдік пен уақыттан құрбан ету керек. Жинақтауларды қолмен ауыстыруға көп уақыт кетеді және шағын адамдық қателерге осал (Rooijmans, 2003). Сонымен қатар, еңбек сағатына жұмсалатын қосымша инвестиция жоғары; қолмен жинақтау жүйесі қызметкерлерге одан да көп жүктеме түсіреді.
Automatic catch ups: Catch ups that are being transferred by an automated system, created in the preparing the organization phase. This system automatically transfers the data or information to the new system when the conversion goes from the old leading system to the new leading system. The benefit of an automated system is that it is fast and accurate. The disadvantage is that is takes time to produce a transfer system in an earlier stage. Catch ups by hand: When the actual conversion entails only a small amount of time, or the complexity of information that should be transferred to the new system is small, an organization can choose to transfer the catch ups manually. The advantage of this procedure is that there is no need for a system (software program) to transfer the information and the possible problems that come with such kind of a transfer program. The trade off is accuracy and time. It takes a considerable amount of extra time, to transfer the catch ups manually and it is more vulnerable for small human errors (Rooijmans, 2003). Moreover, the additional investment in labour hours is high already; a manual catch up system places even more pressure on the personnel.
Мақалалар
Андерсон И., Хансон К. (2003). Бағдарламалық қамтамасыз ету ұйымында технологияны тарату, қолданбалы ақпараттық технологиялар бойынша лицензиат диссертациясы, Гетеборг университеті.
Браун С. V. және Вессей И. (1999 ж.). ERP енгізу тәсілдері: Төтенше жағдайларға бейімделу аясында, Ақпараттық жүйелер жөніндегі 20-шы халықаралық конференцияның материалдары, Шарлотта, NC, 13–15 желтоқсан, 411–416 бб.
Чнг С. және Ватанофас В. (2002). Ұйымдар аралық кәсіпорын жүйесіне қарай: Топтық талқылау зерттеуі. Ақпараттық жүйелер жөніндегі 6-шы Тынық мұхиты аймақтық конференциясы (PACIS 2002). Токио, Жапония, 2–4 қыркүйек, 2002 ж.
Ли О. (2004). Невада DMV жүйесінің кейс-стадисі, Бизнес және экономика академиясының журналы, 3-том.
Рибберс П. және Ску К. С. (2002). Күрделі бағдарламалық қамтамасыз етуді енгізу бағдарламаларын жобалау, 35-ші жылдық Гавайи халықаралық жүйелік ғылымдар конференциясы (HICSS'02), 8-том.
Юсуф Y., Гунасекаран А. және Абторп М. С. (2004). Кәсіпорын жүйелері жобасын іске асыру: Роллс-Ройстегі ERP-нің кейс-стадисі. Өндірістік экономиканың халықаралық журналы, 87, 251–266 бб.
Andersson I. Hanson, K. (2003). Technology diffusion in a software organization, Licentiate Thesis in applied Information Technology, University of Goteborg
Brown, C. V. & Vessey, I. (1999). ERP Implementation Approaches: Toward a Contingency Framework, Proceedings of the 20th International Conference on Information Systems, Charlotte, NC, December 13–15, 411 416. Chng, S., & Vathanophas V. (2002). Towards an Inter Organizational Enterprise System: A Focus Group Study. The 6th Pacific Asia Conference on Information Systems (PACIS 2002). Tokyo, Japan. September 2–4, 2002. Lee, O. (2004). A Case Study of Nevada DMV system, Journal of the Academy of Business and Economics, Volume 3
Ribbers, P. & Schoo, K. C. (2002). Designing Complex Software Implementation Programs, 35th Annual Hawaii International Conference on System Sciences (HICSS'02), Volume 8
Yusuf, Y. & Gunasekaran, A. & Abthorpe M. S. (2004). Enterprise systems project implementation: A case study of ERP in Rolls Royce. International Journal of Production Economics, 87, 251 266.
Brown, C. V. & Vessey, I. (1999). ERP Implementation Approaches: Toward a Contingency Framework, Proceedings of the 20th International Conference on Information Systems, Charlotte, NC, December 13–15, 411 416. Chng, S., & Vathanophas V. (2002). Towards an Inter Organizational Enterprise System: A Focus Group Study. The 6th Pacific Asia Conference on Information Systems (PACIS 2002). Tokyo, Japan. September 2–4, 2002. Lee, O. (2004). A Case Study of Nevada DMV system, Journal of the Academy of Business and Economics, Volume 3
Ribbers, P. & Schoo, K. C. (2002). Designing Complex Software Implementation Programs, 35th Annual Hawaii International Conference on System Sciences (HICSS'02), Volume 8
Yusuf, Y. & Gunasekaran, A. & Abthorpe M. S. (2004). Enterprise systems project implementation: A case study of ERP in Rolls Royce. International Journal of Production Economics, 87, 251 266.