Welcome to Implementation: Bringing Systems to Life!
Hello and welcome! In the Systems Development Life Cycle (SDLC), you have already looked at analysis, design, and development/testing. Now comes one of the most exciting stages: Implementation.
Think of implementation as the grand opening night of a theatre production. All the scripts have been written (design) and the rehearsals are finished (testing). Now, it is time to put the system into real-world use! In this chapter, we will break down how organizations switch to new systems, how they train staff, migrate data, and write documentation. Don't worry if this seems like a lot to take in at first—we will explore each concept step-by-step with clear real-world examples.
1. System Changeover Methods
When a business decides to stop using an old software system and start using a new one, they cannot just flip a switch without careful planning. The method they choose to make the transition is called the changeover method (or conversion method).
There are four main changeover methods you must know for your CCEA AS exam: Direct, Parallel, Pilot, and Phased.
Method A: Direct Changeover (The "Big Bang")
What is it? The old system is completely stopped at a specific time (e.g., midnight on Friday), and the new system takes over immediately (e.g., 8:00 AM on Monday).
Everyday Analogy: Tearing off a plaster in one quick pull, or throwing away your old phone the exact minute your new phone arrives in the post.
• Advantages:
- Cheapest option: The organization does not have to pay to run two systems at once.
- Immediate benefits: Users get access to the new features right away.
- No duplication of work: Staff only enter data into one system.
• Disadvantages:
- High risk: If the new system crashes or contains a critical bug, there is no backup system to fall back on.
- Stressful for staff: Users must adapt immediately without room for error.
• Best suited for: Situations where failure is not life-threatening or business-critical, or when two systems cannot run side-by-side (e.g., a simple retail barcode upgrade over a weekend).
Method B: Parallel Running
What is it? Both the old system and the new system are run alongside each other for a set period until the organization is completely confident that the new system works perfectly.
Everyday Analogy: Keeping your old car insured and parked in the driveway for a month while you test out your new car, just in case the new one breaks down.
• Advantages:
- Lowest risk / Complete safety net: If the new system fails, the business continues running on the old system without any data loss or downtime.
- Output comparison: Results from both systems can be compared to verify that the new software calculates data accurately.
• Disadvantages:
- Very expensive: Running two systems requires double the electricity, hardware, and maintenance costs.
- High workload: Staff have to enter every single piece of data twice (once into the old system and once into the new one).
• Best suited for: Mission-critical environments where errors cannot be tolerated, such as hospital patient databases, bank transaction systems, or air traffic control.
Method C: Pilot Running
What is it? The entire new system is rolled out to one small part of the organization (such as one branch, department, or regional office). Once it proves successful there, it is rolled out across the rest of the company.
Everyday Analogy: A high school testing a brand new uniform policy on Year 13 students only. If it works well, the whole school adopts it next term.
• Advantages:
- Controlled risk: If the system fails, only the pilot branch is affected; the rest of the company continues normally.
- Real-world feedback: The pilot group can discover bugs and suggest improvements before the nationwide launch.
- Peer training: Staff from the pilot branch can help train colleagues in other branches later.
• Disadvantages:
- Data synchronization issues: It can be difficult to share data between the pilot branch (using the new system) and other branches (using the old system).
- Takes time: The full rollout is delayed while waiting for the pilot test to complete.
• Best suited for: Multi-branch businesses, such as supermarket chains (e.g., testing self-checkouts in one Belfast store before rolling them out across Northern Ireland).
Method D: Phased Implementation
What is it? The new system is broken down into modules or sections. One module is introduced at a time. Once that part works properly, the next module is introduced.
Everyday Analogy: Renovating your house room-by-room. You finish the kitchen first, then the bathroom, then the living room, rather than tearing up the entire house all at once.
• Advantages:
- Manageable adjustment: Staff only have to learn one small part of the new system at a time.
- Gradual cost: Expenses and training can be spread over several months.
- Isolated failures: If one module has a bug, only that specific feature is disrupted.
• Disadvantages:
- Complex integration: The newly installed module must be compatible with the remaining parts of the old system (temporary bridge software might be required).
- Prolonged process: It can take a very long time for the organization to become fully updated.
• Best suited for: Large, modular software systems such as Enterprise Resource Planning (ERP) packages (e.g., introducing the invoicing module first, then inventory, then payroll).
Memory Aid: The "4 Ps and D"
To remember the changeover methods, think of: Direct, Parallel, Pilot, and Phased.
• Direct: All at once, everywhere.
• Parallel: Side-by-side, everywhere.
• Pilot: All at once, in one place.
• Phased: Part by part, everywhere.
Key Takeaway for Changeover: Direct is fast but risky; Parallel is safe but expensive; Pilot tests the whole system in one branch; Phased introduces one feature at a time across all branches.
2. Data Migration and File Conversion
When moving to a new system, organizations rarely start with a blank database. They need to move their existing data (such as customer records, sales history, and product details) from the old system to the new one. This process is known as Data Migration.
The Key Stages of Data Migration
1. Data Extraction: Pulling raw data out of the old system's storage.
2. Data Cleansing (Scrubbing): Finding and fixing errors in the old data before moving it. This includes removing duplicate records, correcting spelling mistakes, and deleting obsolete information.
Did you know? Moving "dirty" or corrupt data into a shiny new system is a major cause of project failure! As the saying goes: Garbage In, Garbage Out.
3. Data Transformation / Conversion: Changing the format of the data so that the new system can read it. For example, if the old system stored dates as DD/MM/YYYY and the new system requires YYYY-MM-DD, the format must be converted.
4. Data Loading: Importing the cleansed, converted data into the new database tables.
5. Data Validation & Verification: Running checks to confirm that no records were lost, corrupted, or altered during the transfer.
Key Takeaway for Migration: Data migration isn't just copying files; it requires cleaning, reformatting, and verifying data to prevent errors in the new system.
3. User Training
Even the most advanced computer system will fail if the people using it do not know what they are doing! User training ensures that staff have the confidence and skills to operate the new system efficiently.
Common Training Methods
1. One-to-One Training:
An expert trainer sits down with a single employee to teach them the software.
• Advantage: Highly personalized; the pace can be adjusted to the learner's individual needs.
• Disadvantage: Very expensive and extremely time-consuming for large organizations.
2. Instructor-Led Classroom Training:
A group of employees attends a structured training session led by a tutor in a computer lab or seminar room.
• Advantage: Cost-effective for training many staff members at once; allows group discussion and hands-on practice.
• Disadvantage: One-size-fits-all approach; fast learners may get bored while slower learners may get left behind.
3. Online / E-Learning (Computer-Based Training - CBT):
Employees complete interactive tutorials, video modules, and quizzes on their own computers at their own pace.
• Advantage: Highly flexible; staff can learn whenever and wherever they want; easy to track employee progress automatically.
• Disadvantage: Requires high self-discipline; lacks face-to-face interaction to answer unexpected or complex questions.
4. User Manuals & Self-Instruction Guides:
Printed booklets or digital PDFs that provide step-by-step instructions and reference guides.
• Advantage: Cheap to distribute; available at all times as an on-the-spot reference.
• Disadvantage: Many people find manuals dry and difficult to follow without interactive demonstration.
Key Takeaway for Training: Effective training reduces employee anxiety, minimizes operational errors, and ensures a smooth return to full business productivity.
4. System Documentation
Documentation refers to all the written manuals, guides, diagrams, and technical specifications produced during the development life cycle. In AS Level Digital Technology, you must distinguish clearly between User Documentation and Technical Documentation.
A. User Documentation
Purpose: Designed to help everyday, non-technical people operate the software to carry out their daily tasks.
Analogy: The instruction booklet that comes in the box with a new television or microwave.
Typical Contents:
• Step-by-step instructions (e.g., "How to create a new customer account")
• Screenshots showing the user interface and button layouts
• Frequently Asked Questions (FAQs)
• Troubleshooting guide (e.g., "What to do if your password is not accepted")
• Hardware/software requirements needed to run the program
• Contact details for technical support or helpdesk services
B. Technical Documentation
Purpose: Designed for systems analysts, programmers, and IT technicians who need to maintain, update, repair, or extend the system in the future.
Analogy: The wiring schematic and engineering blueprint used by an electrician to repair a machine.
Typical Contents:
• Program code listings with explanatory comments
• Data Dictionaries (defining field names, data types, validation rules, and sizes)
• System flowcharts and Data Flow Diagrams (DFDs)
• Entity-Relationship Diagrams (ERDs) showing database structures
• Test plans, test cases, and actual test results
• Security and backup procedures
Quick Comparison Checklist
• Target Audience: End users / employees (User Doc) vs Programmers / IT staff (Technical Doc).
• Main Goal: Operating the software (User Doc) vs Maintaining and updating the software (Technical Doc).
• Language Used: Simple, non-technical terms (User Doc) vs Technical jargon, code, and diagrams (Technical Doc).
Key Takeaway for Documentation: User documentation teaches people how to use the system; technical documentation enables programmers to fix and update the system.
5. Common Exam Pitfalls to Avoid
Pitfall 1: Confusing Pilot and Phased Changeover.
Remember: Pilot = the whole system in one location. Phased = one part of the system across all locations.
Pitfall 2: Forgetting data conversion in migration questions.
Do not just state that data is "copied across". Always mention data cleansing (removing duplicates/errors) and format conversion (matching data types).
Pitfall 3: Mixing up documentation contents.
Never include program code listings or database schemas in user documentation! End users do not need to read SQL statements to print an invoice.
Chapter Review Summary
• Implementation is the phase where the new system is delivered, installed, and handed over to users.
• The four changeover strategies are Direct (fast, high risk), Parallel (safe, expensive), Pilot (tested in one location), and Phased (introduced module by module).
• Data Migration involves extracting, cleansing, transforming, loading, and validating legacy data.
• Training (One-to-one, Classroom, E-learning, Manuals) ensures users can comfortably adopt the system.
• Documentation is divided into User Documentation (for operational use) and Technical Documentation (for ongoing maintenance).