IB Computer Science Topic 1.1 - Systems in Organizations

Guess the term of these definitions
Source: Core Computer Science
Some definitions are hidden until other definitions have been answered in order to avoid disclosure of answers to other definitions as much as possible.
Quiz by KRQC2000
Rate:
Last updated: May 3, 2018
First submittedMarch 19, 2018
Times taken183
Average score41.5%
Report this quizReport
7:00
Enter answer here
0
 / 41 guessed
The quiz is paused. You have remaining.
Scoring
You scored / = %
This beats or equals % of test takers also scored 100%
The average score is
Your high score is
Your fastest time is
Keep scrolling down for answers and more stats ...
Definition
Term
Planning and System Installation
Evaluates and analyzes project and its potential based on: Technical, Economical, Legal, Operational, and Schedule
Feasibility report/study
Process of shifting individuals, teams, departments, and organizations from present to desired state. Goal: Maximize benefits and minimize negative impacts of change.
Change management
Old technology, hardware, computer system, or application that can run programs that can no longer be upgraded.
Legacy system
Combining of two or more business entities, mainly to reduce costs
Business merger
Situation where different software entities or systems cannot operate satisfactorily on same computer or different computers linked by LAN or WAN
Incompatibility
Allows software and data to be hosted and managed centrally on remote datacentre
Software-as-a-Service (SaaS)
Process of replacing old system with new system
Changeover
New system is implemented while retiring the old system
Direct changeover
Both systems work simultaneously for short time, and outputs can be compared
Parallel changeover
New system is implemented in one site or group at first and then expands to other sites periodically
Pilot changeover
Different parts of system are changed at different times
Phased changeover
Transfer of data between formats, storage types, or systems
Data migration
Tests individual commands, text input, menu functions, etc.
Functional testing
Inputting normal, abnormal, and extreme data into system
Data testing
Data within limits. Used to check if "pass" and "fail" messages are appropriately displayed
Normal data
Unexpected data, e.g. "two" instead of "2," "4 2" instead of "42"
Abnormal data
Carried out by developers of software, prior to distributing product to general public
Alpha testing
Receiving comments and suggestions from users outside company
Beta testing
Testing pen-and-paper by programmer
Dry-run testing
Individual parts of system tested separately
Unit testing
Entire system is tested at same time to verify all components can work together
Integration testing
To determine if system satisfies customer needs. Mostly conducted by user prior to transfer of ownership.
User acceptance testing
Finding and correcting bugs/errors in program
Debugging
Evaluating whether input follows appropriate specifications and is within reasonable limits
Validation
Ensuring input is same as original data e.g. confirm password
Verification
User Focus
Either written or online, contains all instructions mandatory for system operation. Examples include manuals, email support, embedded assistance, FAQ, live chat, online portals.
User documentation
Documentation for code comprehension and details as part of source code itself
Internal documentation
Typically separate document for program itself, e.g. user guide, software requirements, description of design and implementation features of program
External documentation
Teaching user how to use a system
User training
User can learn at his/her own time until mastery of subject is achieved.
Self-instruction
Offers open and free discussions between students and teacher/instructor
Formal class
Participants can take part in courses from anywhere in the world 24/7 provided they have PC and Internet access
Online training
System Backup
When data is lost or destroyed due to system failure, storage negligence, or errors. Can be prevented with regular backups, firewall, antivirus, etc.
Data loss
Duplication of storage devices and stored data of computer system to secure stored data
Redundancy
For fast data backup and storage, non-volatile. Examples include CD, DVD, USB
Removable media
System on standby but can switch to spare computer system, which becomes primary upon error such as hardware failure or network failure.
Failover system
Like above but primary and secondary system exchange roles
Switchover system
Software Deployment
Updates applications by fixing known bugs and vulnerabilities, although may introduce new bugs as side effects
Patches
Always contain new functionalities or characteristics, as well as cumulative bug fixes. Most times need to be bought.
Upgrades
Improve product marginally by adding new functionalities or fixing bugs. Most times free
Updates
Final, working versions of software applications that already underwent alpha and beta testing.
Releases
No comments yet