System fundamentals Flashcards
(41 cards)
Change management
A structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state during system change.
🧠 Includes planning, communication, training, and minimizing resistance.
Legacy systems
Older computer systems, software, or hardware that are still in use but may be outdated or incompatible with newer systems.
🧠 Can be difficult to replace or integrate due to cost or complexity.
Business mergers
When two companies combine, they may use different IT systems, requiring system integration, data migration, and resolution of compatibility issues.
🧠 Often leads to major system change and careful planning.
SaaS (software as a service)
A cloud-based model where users access software over the internet without installing it locally.
🧠 Example: Google Docs, Microsoft 365.
Implementation of systems using a client’s hardware vs hosting systems remotely
Client’s hardware:
The system runs on-site, on the user’s own computers or servers.
🧠 Greater control, but more maintenance.
Hosting remotely (e.g. cloud):
The system runs off-site on external servers (like in SaaS).
🧠 Easier updates, less local responsibility.
Parallel running
The old and new systems run at the same time for a period to compare results.
🧠 Safer, but more time- and resource-consuming.
Pilot running
The new system is tested in one part of the organization first.
🧠 If successful, it can then be rolled out to the rest.
Direct changeover
The old system is immediately replaced by the new system.
🧠 Fast but risky — no backup if the new system fails.
Phased conversion
The new system is introduced step by step, module by module.
🧠 Lower risk, easier to manage errors, but takes longer.
Problems due to data migration
incompatible file formats, data stractures, validation rules, incomplete data transfer and international conventions on dates, currencies and character sets
Example: Transferring dates from one system in MM/DD/YYYY format into one using DD/MM/YYYY.
User acceptance testing (testing types)
The final stage of testing where actual users test the system to make sure it meets their needs and requirements before it goes live.
Debugging (done after testing)
The process of finding and fixing errors (bugs) in a program after identifying them through testing.
Beta testing (testing types)
Real users try the system before full release, usually outside the company.
It’s done after internal testing, but before the final version is released — to catch bugs that weren’t found earlier.
Describe the importance of user documentation
A set of written materials that explains how to use a system or application. It is essential for helping end users understand and operate the system correctly and efficiently.
Methods of provoding user documentation
Help files, online support, and printed manuals
Methods of delivering user training
Self-instruction, formal classes, remote/online training
Causes of data loss
Malicious activities (eg. result of employees or intruders) and natural disasters
Consequences of data loss
Loss of medical records, cancellation of a hotel reservation without the knowledge of the traveller.
Methods to prevent data loss
Failover systems, redundancy, removable media, offsite/online storage
Failover systems
A failover system is a backup system that automatically takes over when the main system fails. It ensures that the system continues to operate with minimal interruption.
Redundancy
Having extra components or systems that are not currently in use but are kept ready in case of failure. It is a design strategy to increase reliability and prevent total system failure.
Strategies for managing releases & updates
Automatic updates received on a regular basis online
Hardware
The physical components of a computer system that you can touch.
🧠 Examples: CPU, RAM, hard drive, motherboard.
Software
The programs and instructions that run on hardware and control what the system does.
🧠 Examples: Operating systems, word processors, web browsers.
