In simple terms
A friendly intro before the formal notes — no formulas yet.
Upgrading Your Digital Toolkit
Introducing a new computer system in a company is like swapping your old, trusty but limited phone for a brand new smartphone. It requires careful planning to ensure everything transfers smoothly and everyone knows how to use the new features without causing chaos.
Imagine you're rearranging your entire bedroom. You wouldn't just throw all your furniture out onto the landing and hope for the best. First, you'd measure the space and plan where the new bed and desk will go (Analysis & Design). You might try putting the new desk in a corner to see how it feels before moving everything else (Pilot). Then, you'd move the furniture, perhaps section by section (Phased). Finally, you'd live in it for a bit and see if the new layout works (Evaluation). Implementing a new IT system in a business follows a very similar, structured process to avoid disruption.
- 1
First, an organisation analyses its current system to identify problems and defines the requirements for a new one.
- 2
Next, a feasibility study is conducted to see if the new system is technically, economically, and operationally possible.
- 3
Then, a changeover strategy is chosen to switch from the old system to the new one, such as running both side-by-side for a while.
- 4
Finally, after implementation, the new system is evaluated and maintained, and users are trained to ensure it's used effectively.
Explore the concept
Use the live diagram and synced steps — play it or tap a step card to walk through.
Full topic notes
Formal explanation with the rigour you need for the exam.
The Rationale for New Systems
Organisations don't decide to implement new systems on a whim; it's a major undertaking with significant costs and risks. The primary drivers for change often stem from the limitations of existing systems, known as legacy systems. These older systems can be inefficient, incompatible with new technologies, difficult to maintain, and may no longer meet the evolving needs of the business.
Legacy Systems: Often slow, lack modern security features, and finding programmers who can maintain them is difficult and expensive.
Business Mergers & Acquisitions: When two companies merge, they need to integrate their disparate IT systems into a single, cohesive one.
New Business Opportunities: A company might want to launch an e-commerce platform or a mobile app, which their current system cannot support.
Changes in Law or Regulations: New data protection laws (like GDPR) might require system changes to ensure compliance.
Planning and System Analysis
Before any new system is built or bought, extensive planning is required. This begins with a feasibility study to determine if the project is a viable idea. The study assesses the project from multiple angles to ensure it makes sense for the organisation to proceed.
If the project is deemed feasible, the next step is a detailed analysis of the existing system and the requirements for the new one. This involves collecting information from various stakeholders through methods like interviews, questionnaires, and direct observation of the current workflow.
Feasibility Study (TELOS):
Technical: Is the technology available? Do we have the expertise?
Economic: Can we afford it? Will it provide a good return on investment?
Legal: Does it comply with all laws and regulations?
Operational: Will the system be used effectively? Will it be accepted by users?
Schedule: Can the system be developed and implemented in the required timeframe?
Changeover Methods
The changeover (or 'go-live') is the critical moment when the organisation switches from the old system to the new one. There are four main methods, each with its own advantages and disadvantages. The choice of method depends on the nature of the system, the level of risk the organisation is willing to take, and the resources available.
Direct Changeover: The old system is switched off and the new one is switched on, often overnight or over a weekend. High risk, low cost.
Parallel Running: Both old and new systems run simultaneously for a set period. Low risk, high cost.
Phased Implementation: The new system is rolled out in modules or stages. Medium risk, medium cost.
Pilot Running: The entire new system is implemented in a single department or location as a trial before a full-scale rollout. Medium risk, allows for testing in a live environment.
Worked examples
See the formulas applied — reveal one step at a time, like the exam.
A small independent bookshop with 5 employees is replacing its paper-based sales ledger with a new off-the-shelf accounting software package. The owner is concerned about disruption to the business. Evaluate the suitability of Direct Changeover and Parallel Running for this scenario.
- 1
Here is a possible mark scheme breakdown:
A national hospital network is implementing a new, unified Patient Record System (PRS) to replace different legacy systems in its 20 hospitals. The new system will handle patient appointments, medical history, and prescriptions. Identify two key stakeholder groups and explain why user training is critical for a successful implementation.
- 1
Here is a possible mark scheme breakdown:
How it all connects
The big idea sits in the middle — tap a linked idea to explore the link.
Tap a linked idea to see how it connects back to the main topic — that connection is what examiners reward.
Glossary
Try to recall each definition before you reveal it.
Quick check
Answer in your head first — then tap to check. No pressure.
Revision flashcards
Flip the card. Test yourself before the exam.
What is a legacy system?
An old technology, hardware, computer system, or application program that may still be in use. These systems are often outdated and difficult to maintain or update.
Key takeaways
Review these before you close the topic — retrieval beats re-reading.
- ✓
Legacy Systems: Often slow, lack modern security features, and finding programmers who can maintain them is difficult and expensive.
- ✓
Business Mergers & Acquisitions: When two companies merge, they need to integrate their disparate IT systems into a single, cohesive one.
- ✓
New Business Opportunities: A company might want to launch an e-commerce platform or a mobile app, which their current system cannot support.
- ✓
Changes in Law or Regulations: New data protection laws (like GDPR) might require system changes to ensure compliance.
Practice — then mark it
The whole point: a real Cambridge question, marked mark-by-mark.
Test Your Knowledge on Systems in Organisations
Test Your Knowledge on Systems in Organisations
Extra simulations & links
PhET, GeoGebra and other curated tools — open in a new tab.
Frequently asked
Checkpoint
One marked question is worth ten re-reads — close the loop before you move on.
Reading it isn’t knowing it — prove it.
Before you move on: do Test Your Knowledge on Systems in Organisations on paper, snap a photo, and get examiner-style feedback on exactly where you win and lose marks.