Featured Quizzes
User Quizzes
Create Quiz
Data and Charts
Word Search
Badges and Games
About JetPunk
Message Board
Random Quiz
Dark Mode
IB Computer Science Topic 1.1 - Systems in Organizations - Statistics
General Stats
-
This quiz has been taken 397 times
384 since last reset
- The average score is 17 of 41
Answer Stats
| Definition | Term | % Correct |
|---|---|---|
| Receiving comments and suggestions from users outside company | {Beta} testing | 79%
|
| Carried out by developers of software, prior to distributing product to general public | {Alpha} testing | 76%
|
| Old technology, hardware, computer system, or application that can run programs that can no longer be upgraded. | Legacy system | 71%
|
| Both systems work simultaneously for short time, and outputs can be compared | Parallel changeover | 70%
|
| New system is implemented while retiring the old system | Direct changeover | 66%
|
| New system is implemented in one site or group at first and then expands to other sites periodically | Pilot changeover | 62%
|
| Transfer of data between formats, storage types, or systems | Data {migration} | 61%
|
| Finding and correcting bugs/errors in program | Debugging | 61%
|
| Different parts of system are changed at different times | Phased changeover | 60%
|
| 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} | 57%
|
| Inputting normal, abnormal, and extreme data into system | {Data} testing | 49%
|
| Improve product marginally by adding new functionalities or fixing bugs. Most times free | Updates | 49%
|
| Process of replacing old system with new system | Changeover | 48%
|
| 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 | 48%
|
| Combining of two or more business entities, mainly to reduce costs | Business merger | 47%
|
| Evaluates and analyzes project and its potential based on: Technical, Economical, Legal, Operational, and Schedule | {Feasibility} report/study | 45%
|
| Process of shifting individuals, teams, departments, and organizations from present to desired state. Goal: Maximize benefits and minimize negative impacts of change. | Change management | 43%
|
| Ensuring input is same as original data e.g. confirm password | Verification | 43%
|
| Allows software and data to be hosted and managed centrally on remote datacentre | Software-as-a-Service (SaaS) | 42%
|
| Evaluating whether input follows appropriate specifications and is within reasonable limits | Validation | 42%
|
| Unexpected data, e.g. "two" instead of "2," "4 2" instead of "42" | {Abnormal} data | 41%
|
| Testing pen-and-paper by programmer | {Dry-run} testing | 37%
|
| Data within limits. Used to check if "pass" and "fail" messages are appropriately displayed | {Normal} data | 37%
|
| Updates applications by fixing known bugs and vulnerabilities, although may introduce new bugs as side effects | Patches | 36%
|
| Individual parts of system tested separately | {Unit} testing | 36%
|
| Situation where different software entities or systems cannot operate satisfactorily on same computer or different computers linked by LAN or WAN | Incompatibility | 35%
|
| Always contain new functionalities or characteristics, as well as cumulative bug fixes. Most times need to be bought. | Upgrades | 34%
|
| Teaching user how to use a system | User training | 34%
|
| To determine if system satisfies customer needs. Mostly conducted by user prior to transfer of ownership. | {User acceptance} testing | 33%
|
| System on standby but can switch to spare computer system, which becomes primary upon error such as hardware failure or network failure. | {Failover} system | 32%
|
| User can learn at his/her own time until mastery of subject is achieved. | Self-instruction | 28%
|
| Entire system is tested at same time to verify all components can work together | {Integration} testing | 27%
|
| Tests individual commands, text input, menu functions, etc. | {Functional} testing | 26%
|
| Duplication of storage devices and stored data of computer system to secure stored data | Redundancy | 26%
|
| Final, working versions of software applications that already underwent alpha and beta testing. | Releases | 26%
|
| Typically separate document for program itself, e.g. user guide, software requirements, description of design and implementation features of program | External documentation | 25%
|
| Offers open and free discussions between students and teacher/instructor | Formal class | 25%
|
| Documentation for code comprehension and details as part of source code itself | Internal documentation | 23%
|
| Participants can take part in courses from anywhere in the world 24/7 provided they have PC and Internet access | Online training | 22%
|
| Like above but primary and secondary system exchange roles | {Switchover} system | 15%
|
| For fast data backup and storage, non-volatile. Examples include CD, DVD, USB | Removable media | 14%
|
No matching quizzes found
Score Distribution
Percent of People with Each Score
Percentile by Number Answered
Your Score History
You have not taken this quiz since the last reset
New and Popular