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%
|
Both systems work simultaneously for short time, and outputs can be compared | Parallel changeover | 69%
|
New system is implemented while retiring the old system | Direct changeover | 68%
|
Old technology, hardware, computer system, or application that can run programs that can no longer be upgraded. | Legacy system | 67%
|
New system is implemented in one site or group at first and then expands to other sites periodically | Pilot changeover | 61%
|
Finding and correcting bugs/errors in program | Debugging | 60%
|
Transfer of data between formats, storage types, or systems | Data {migration} | 59%
|
Different parts of system are changed at different times | Phased changeover | 58%
|
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} | 53%
|
Inputting normal, abnormal, and extreme data into system | {Data} testing | 48%
|
Combining of two or more business entities, mainly to reduce costs | Business merger | 46%
|
Improve product marginally by adding new functionalities or fixing bugs. Most times free | Updates | 46%
|
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 | 45%
|
Process of replacing old system with new system | Changeover | 43%
|
Unexpected data, e.g. "two" instead of "2," "4 2" instead of "42" | {Abnormal} data | 42%
|
Process of shifting individuals, teams, departments, and organizations from present to desired state. Goal: Maximize benefits and minimize negative impacts of change. | Change management | 42%
|
Evaluates and analyzes project and its potential based on: Technical, Economical, Legal, Operational, and Schedule | {Feasibility} report/study | 42%
|
Allows software and data to be hosted and managed centrally on remote datacentre | Software-as-a-Service (SaaS) | 41%
|
Data within limits. Used to check if "pass" and "fail" messages are appropriately displayed | {Normal} data | 38%
|
Evaluating whether input follows appropriate specifications and is within reasonable limits | Validation | 38%
|
Ensuring input is same as original data e.g. confirm password | Verification | 38%
|
Testing pen-and-paper by programmer | {Dry-run} testing | 37%
|
Individual parts of system tested separately | {Unit} testing | 37%
|
Updates applications by fixing known bugs and vulnerabilities, although may introduce new bugs as side effects | Patches | 36%
|
Situation where different software entities or systems cannot operate satisfactorily on same computer or different computers linked by LAN or WAN | Incompatibility | 34%
|
To determine if system satisfies customer needs. Mostly conducted by user prior to transfer of ownership. | {User acceptance} testing | 32%
|
Always contain new functionalities or characteristics, as well as cumulative bug fixes. Most times need to be bought. | Upgrades | 31%
|
Teaching user how to use a system | User training | 31%
|
System on standby but can switch to spare computer system, which becomes primary upon error such as hardware failure or network failure. | {Failover} system | 27%
|
Entire system is tested at same time to verify all components can work together | {Integration} testing | 26%
|
Duplication of storage devices and stored data of computer system to secure stored data | Redundancy | 25%
|
User can learn at his/her own time until mastery of subject is achieved. | Self-instruction | 25%
|
Tests individual commands, text input, menu functions, etc. | {Functional} testing | 24%
|
Offers open and free discussions between students and teacher/instructor | Formal class | 22%
|
Typically separate document for program itself, e.g. user guide, software requirements, description of design and implementation features of program | External documentation | 21%
|
Final, working versions of software applications that already underwent alpha and beta testing. | Releases | 21%
|
Documentation for code comprehension and details as part of source code itself | Internal documentation | 19%
|
Participants can take part in courses from anywhere in the world 24/7 provided they have PC and Internet access | Online training | 18%
|
For fast data backup and storage, non-volatile. Examples include CD, DVD, USB | Removable media | 13%
|
Like above but primary and secondary system exchange roles | {Switchover} system | 12%
|
Copyright H Brothers Inc, 2008–2024
Contact Us | Go To Top | View Mobile Site