Converting to New System

AI Summary

An AI-generated summary of this video lecture.

The lecture provides a detailed explanation of the "Converting to the New System" phase in System Analysis and Design. It begins by stating that the actual conversion process involves significant resources including equipment, personnel, data, and financial resources. The instructor explains that the method of conversion depends on the criticality of the system. Four primary strategies are detailed: Direct, Pilot, Phased, and Parallel conversion. Each method is analyzed regarding its risk, cost, and implementation approach, with the instructor using underlining and diagrams to emphasize key characteristics like risk levels and operational continuity.

Chapters

1. 0:00 – 2:00 00:00-02:00

   The video focuses on system conversion, noting it involves "equipments, personnel, data and financial resources." It then focuses on "Direct Conversion," described in the text as an "abrupt approach" where the "old system is shutdown and the new system starts." The instructor underlines phrases such as "economical" and "very risky," explaining that users are "at the mercy of the new system." A hand-drawn diagram illustrates this transition: a box marked with an 'X' (representing the old system) points directly to a box with a checkmark (the new system). The text notes that while this is the only option when systems cannot run parallel, it is often the "least preferred for critical business applications" because if the new system fails, there is no way to revert.

2. 2:00 – 5:00 02:00-05:00

   The lecture covers "Pilot Conversion," defined as a "middle path approach." Unlike direct conversion, this method avoids converting "all at once throughout the organization." Instead, it involves "conversion at one selected location or system at a single pre-decided location," such as a "branch office." The instructor underlines the text to highlight that the "potential risk in case of failure of the system is limited to a single location." This allows the team to "test all functionalities of the new system" before replicating it elsewhere. The text mentions that while beneficial for the user, it places a "substantial burden on the implementation team as it has to maintain two systems in parallel" during the testing phase.

3. 5:00 – 7:34 05:00-07:34

   The lecture covers "Phased Conversion" and "Parallel Conversion." Phased conversion is described as an "incremental approach" where "Different sub-systems of the new system is used in conjunction until the whole new system is converted." The instructor draws a sequence of boxes (Admin -> Pay -> ...) to visualize this. Parallel conversion is labeled "least risk prone," where the "old system is allowed to run alongside the new system." The text explains that outputs are compared to ensure the new system covers all functionalities. The instructor notes this is "costly as two systems are run in parallel." Handwritten notes compare the methods, labeling Direct as "Small" duration but risky, and Parallel as "Long" duration but safe.

The lesson systematically breaks down system conversion strategies, moving from the most risky (Direct) to the safest (Parallel). Direct conversion is a "big bang" approach suitable only when parallel running is impossible. Pilot conversion mitigates risk by testing in a single location first. Phased conversion reduces risk incrementally by converting sub-systems one by one. Parallel conversion offers the highest safety by running both systems simultaneously but incurs high costs. The instructor emphasizes that the choice depends on the "criticality of the system," with handwritten notes summarizing the trade-offs between duration, cost, and risk for each method.