Four-class labels
int64 0
3
| Binary labels
int64 0
1
| Entity
stringlengths 8
33
| Definition1
stringlengths 15
259
| Definition2
stringlengths 14
253
|
|---|---|---|---|---|
3 | 1 |
fault tolerance
|
a property of computer design that enables a system to continue functioning in the event of a partial failure
|
is the property that enables a system to continue operating properly in the event of the failure of some (one or more faults within) of its components
|
2 | 1 |
fault tolerance
|
the capability of the software product to maintain a specified level of performance in cases of software faults ( defects ), or of infringement of its specified interface.
|
the capability of a system to continue normal operation despite the presence of (hardware or software) faults. fault tolerance may be stated as a quality requirement.
|
1 | 0 |
fault tolerance
|
the ability of a network or system to withstand a foreseeable component failure and still continue to provide an acceptable level of service.
|
the ability of a system to respond to unexpected failures. consists of availability (immediate) and durability (long term).
|
0 | 0 |
fault tolerance
|
- must be fault tolerant in critical situations - required when high availability requirements or system failure costs are high
|
the capability of a system to continue normal operation despite the presence of (hardware or software) faults. fault tolerance may be stated as a quality requirement.
|
3 | 1 |
fault tolerance
|
the ability of a system or component to continue its normal operation despite the presence of hardware or software faults.
|
the ability of a system to continue functioning even in the event of one or more component failures
|
2 | 1 |
fault tolerance
|
the capability of a system to suffer a fault; but continue to operate. the system can tolerate the fault as if it never occurred.
|
ability of system to maintain its operations in event of failure. ex. power going out, generator coming in.
|
1 | 0 |
fault tolerance
|
if one cable breaks, all other connections can still communicate
|
the capability of a system to continue performing when there is a hardware failure; so if one of the cables breaks, all of the other computers can still communicate.
|
3 | 1 |
fault tolerance
|
systems that are capable of continuing operation even if a component fails
|
enables a system to continue functioning even in the presence of faults
|
2 | 1 |
fault tolerance
|
is the property that enables a system to continue operating properly in the event of the failure of some (one or more faults within) of its components
|
enables a system to continue to operate if one or more components fail
|
2 | 1 |
fault tolerance
|
the design on the networks that can continue to operate without interruption in the case of hardware, software, or communications failures.
|
if one cable breaks, all other connections can still communicate
|
2 | 1 |
fault tolerance
|
-is the ability of a system to remain in operation even if some of the components used to build the system fail.
|
ability to withstand a certain amount of failure and still remain functional
|
2 | 1 |
fault tolerance
|
the capacity for a system to continue performing despite an unexpected hardware or software malfunction
|
techniques that employ hardware and software to provide assurance against equipment failures, computer service interruptions, and data loss.
|
1 | 0 |
fault tolerance
|
the ability of a network or system to withstand a foreseeable component failure and still continue to provide an acceptable level of service.
|
distributed systems must maintain availability even at low levels of hardware/software/network reliability through recovery and redundancy.
|
3 | 1 |
fault tolerance
|
-is the ability of a system to remain in operation even if some of the components used to build the system fail.
|
the ability of a network or system to withstand a foreseeable component failure and still continue to provide an acceptable level of service.
|
3 | 1 |
fault tolerance
|
ability to withstand a certain amount of failure and still remain functional
|
the ability of a network or system to withstand a foreseeable component failure and still continue to provide an acceptable level of service.
|
3 | 1 |
fault tolerance
|
the ability for a system to respond to unexpected failures or system crashes as the backup system immediately and automatically takes over with no loss of service
|
a general concept that a system has the ability to respond to unexpected failures or systems immediately and automatically takes over with no loss of service
|
2 | 1 |
fault tolerance
|
the ability of a system to continue functioning even in the event of one or more component failures
|
systems that are capable of continuing operation even if a component fails
|
0 | 0 |
fault tolerance
|
assume that a system can be released with faults and that system failures can be dealt with by recovering from them at runtime
|
the capability of the software product to maintain a specified level of performance in cases of software faults ( defects ), or of infringement of its specified interface.
|
0 | 0 |
human-computer interaction
|
the study, planning and design of what happens when a computer and human work together.
|
investigates how people perceive and think about computer-based technologies, what human constraints affect human-machine interaction, and what factors improve usability of computer systems
|
1 | 0 |
human-computer interaction
|
-human factors principles in the understanding, design, and evaluation of human-computer systems. -focus= interface
|
the study, planning and design of what happens when a computer and human work together.
|
1 | 0 |
human-computer interaction
|
the study of how people design, implement, and use it systems, and how it systems affect individuals, organizations, and society
|
describes the relationship between computers and people who use them to perform their jobs
|
1 | 0 |
human-computer interaction
|
is a cross-disciplinary area that deals with the theory, design, implementation, and evaluation of ways human use and interact with computing devices.
|
-human factors principles in the understanding, design, and evaluation of human-computer systems. -focus= interface
|
2 | 1 |
human-computer interaction
|
is a cross-disciplinary area that deals with the theory, design, implementation, and evaluation of ways human use and interact with computing devices.
|
the study, planning and design of what happens when a computer and human work together.
|
0 | 0 |
human-computer interaction
|
-human factors principles in the understanding, design, and evaluation of human-computer systems. -focus= interface
|
investigates how people perceive and think about computer-based technologies, what human constraints affect human-machine interaction, and what factors improve usability of computer systems
|
1 | 0 |
security policies
|
collection of standards, policies, and procedures created to guarantee security. ensures auditing and compliance
|
sets out general info access strategies that should apply across the organization
|
0 | 0 |
security policies
|
acceptable use policy privacy policy security-related human resource policy password management and complexity policy disposal and destruction policy classification of information policy ethics policy
|
collection of several documents
|
1 | 0 |
security policies
|
policies with requirements that evidently make their creation
|
acceptable use policy privacy policy security-related human resource policy password management and complexity policy disposal and destruction policy classification of information policy ethics policy
|
0 | 0 |
security policies
|
rules that the information system enforces relative to the resources under its control to reflect the organizational security policy.
|
policies with requirements that evidently make their creation
|
1 | 0 |
security policies
|
rules that the information system enforces relative to the resources under its control to reflect the organizational security policy.
|
acceptable use policy privacy policy security-related human resource policy password management and complexity policy disposal and destruction policy classification of information policy ethics policy
|
3 | 1 |
case-based reasoning
|
system searches for stored cases with problem characteristics similar to the new one, finds closest fit, and applies solutions of old case to new case
|
a method whereby new problems are solved based on the solutions from similar cases solved in the past
|
0 | 0 |
case-based reasoning
|
represents knowledge as a database as past cases and their solutions. the system uses a six-step process to generate solutions to new problems encountered by the user
|
knowledge and past experiences of human specialists are represented as cases and stored in a database for later retrieval; medical and customer support systems
|
2 | 1 |
case-based reasoning
|
method of solving problems based on similar problems
|
methodology of solving a new problem established on the solutions of similar problems -applied in case-based ess -esp useful in medical decision making
|
3 | 1 |
case-based reasoning
|
system searches for stored cases with problem characteristics similar to the new one, finds closest fit, and applies solutions of old case to new case
|
system searches through stored cases for problem with similar characteristics and applies solutions of old case to new one
|
3 | 1 |
case-based reasoning
|
method of solving problems based on similar problems
|
methodology of solving a new problem established on the solutions of similar problems
|
0 | 0 |
data loss
|
when data becomes lost, unavailable or destroyed
|
threats that occur due to the loss of relevant encryption keys
|
1 | 0 |
data loss
|
an error condition in information systems in which information is destroyed by failures or neglect in storage, transmission, or processing.
|
occurs when info on a storage device is damaged or made unusable.
|
0 | 0 |
data loss
|
a type of attack in which the intruder deletes or encrypts the data, which if not paid results in the data being deleted.
|
the unauthorized use and or transmission of confidential information. typically refers to information leaving the control of the owning organization, for example on portable devices/media or via email.
|
0 | 0 |
data loss
|
a type of attack in which the intruder deletes or encrypts the data, which if not paid results in the data being deleted.
|
some apps (e.g., audio) can tolerate some loss • other apps (e.g., file transfer, telnet) require 100% reliable data transfer
|
1 | 0 |
data loss
|
circumstances that cause loss of stored data arise less frequently for disk secondary storage than for primary storage
|
occurs when info on a storage device is damaged or made unusable.
|
0 | 0 |
data loss
|
an error condition in information systems in which information is destroyed by failures or neglect in storage, transmission, or processing.
|
circumstances that cause loss of stored data arise less frequently for disk secondary storage than for primary storage
|
1 | 0 |
access control policy
|
organizational policy definition that defines how authorized users gain access to resources based on their role, job functions, and duties.
|
a set of rules established by an organization that specify how users can access resources on the system;
|
2 | 1 |
access control policy
|
defines the implementation of the files concerning who or what can gain access to a system or network
|
a set of rules established by an organization that specify how users can access resources on the system;
|
0 | 0 |
convex hull
|
the smallest intersection of linear inequalities that contain a certain set of points
|
a spatial representation of the vector space between two vectors
|
1 | 0 |
convex hull
|
the smallest intersection of linear inequalities that contain a certain set of points
|
the smallest convex set that contains x in the euclidean plane or euclidean space.
|
1 | 0 |
convex hull
|
is the minimum convex polygon which contains the blob
|
the smallest intersection of linear inequalities that contain a certain set of points
|
1 | 0 |
convex hull
|
is the minimum convex polygon which contains the blob
|
a spatial representation of the vector space between two vectors
|
1 | 0 |
web service
|
method of communication that allows two systems to exchange data over the internet
|
a software solution designed to enable interaction between two devices over a network is generally referred to as:
|
1 | 0 |
web service
|
the actual api implementation being called or the interface of the api implementation; a method of communication that allows two software systems to exchange data over the internet
|
open-standards way of supporting interoperability; application programming interfaces (api) that can be accessed over a network and executed on a remote system hosting the requested services
|
2 | 1 |
web service
|
any piece of software that makes itself available over the internet, using a standardized messaging system. allows for communication between disparate systems
|
a software solution designed to enable interaction between two devices over a network is generally referred to as:
|
1 | 0 |
web service
|
a component that exists on a web server which can be called from a client application (extension .asmx). can be accessed thru the internet or network connection
|
a software service accessed over the internet using web protocols
|
1 | 0 |
web service
|
a software service accessed over the internet using web protocols
|
the actual api implementation being called or the interface of the api implementation; a method of communication that allows two software systems to exchange data over the internet
|
0 | 0 |
web service
|
software function or related set of functions that can be executed via web standards
|
is a collection of software components that perform a certain purpose or function, and that can be used by other programs over the web
|
3 | 1 |
web service
|
a loosely coupled reusable software component that encapsulates discrete functionality which may be distributed and programatically accessed
|
an instance of a service: a loosely coupled, reusable software component that encapsulates discrete functionality, which may be distributed and programmatically accessed over the web.
|
2 | 1 |
web service
|
a software service accessed over the internet using web protocols
|
open-standards way of supporting interoperability; application programming interfaces (api) that can be accessed over a network and executed on a remote system hosting the requested services
|
1 | 0 |
web service
|
a method of communication between 2 electronic devices over a network
|
is a service offered by an electronic device to another electronic device, communicating with each other via the world wide web
|
0 | 0 |
web service
|
a component that exists on a web server which can be called from a client application (extension .asmx). can be accessed thru the internet or network connection
|
open-standards way of supporting interoperability; application programming interfaces (api) that can be accessed over a network and executed on a remote system hosting the requested services
|
0 | 0 |
dynamic content
|
content that changes often
|
nonstatic information constructed in response to a web client's request
|
0 | 0 |
dynamic content
|
content that changes often
|
content-based generated based on program parameters, http request and responses and database queries
|
1 | 0 |
dynamic content
|
content-based generated based on program parameters, http request and responses and database queries
|
nonstatic information constructed in response to a web client's request
|
1 | 0 |
dynamic content
|
content that is generated and code is created for response.
|
nonstatic information constructed in response to a web client's request
|
0 | 0 |
dynamic content
|
content-based generated based on program parameters, http request and responses and database queries
|
content that is generated and code is created for response.
|
1 | 0 |
dynamic content
|
content that changes often
|
content that is generated and code is created for response.
|
2 | 1 |
use cases
|
written descriptions of user's interaction with the software product to accomplish a goal
|
set of scenarios that describes an interaction between a user and a system
|
0 | 0 |
use cases
|
-used to explain and document the interaction between the users and the system -used as a means of user requirements
|
structured, well-documented and verbose descriptions of what a system should do used for testing. they are not the same as user stories
|
1 | 0 |
use cases
|
are the mechanism for capturing the desired behavior for the system that is under development, but they do not specify how the behavior is to be implemented.
|
a standard form of expressing requirements as a scenario-based task that the system must automate
|
1 | 0 |
use cases
|
a standard form of expressing requirements as a scenario-based task that the system must automate
|
a more traditional mechanism for articulating a specific customer goal for system use and the interaction sequence(s) needed to achieve the goal; associated with software engineering
|
0 | 0 |
use cases
|
are the mechanism for capturing the desired behavior for the system that is under development, but they do not specify how the behavior is to be implemented.
|
• used for functional requirements analysis and specification • a step-by-step description of how a user will use the system-to-be to accomplish business goals
|
2 | 1 |
use cases
|
set of scenarios that describes an interaction between a user and a system
|
a set of use cases that illustrate the basic processes that the system needs to support
|
1 | 0 |
use cases
|
define the interactions between the &"actor&" and the system. use case document + use case (uml) diagram of user interactions w. system
|
things actors do with the system
|
0 | 0 |
use cases
|
the primary driver for all uml diagramming techniques. depicts major activities performed by actors. describe basic high-level functions of a system. building blocks for continued design activities.
|
assume an interaction with a system as well as detailed understanding of the interaction.
|
1 | 0 |
use cases
|
are the mechanism for capturing the desired behavior for the system that is under development, but they do not specify how the behavior is to be implemented.
|
a more traditional mechanism for articulating a specific customer goal for system use and the interaction sequence(s) needed to achieve the goal; associated with software engineering
|
0 | 0 |
use cases
|
are descriptions of the way users will employ the features and functions of the new information system
|
structured, well-documented and verbose descriptions of what a system should do used for testing. they are not the same as user stories
|
0 | 0 |
use cases
|
a standard form of expressing requirements as a scenario-based task that the system must automate
|
emphasis on user-system interactions, rather than user's task itself identify &"actors&" define the &"normal course&" id alternative courses with #s corresponding to steps replaced
|
0 | 0 |
use cases
|
key features of the system. something that provides some measurable result to the user or an external system
|
set of scenarios that describes an interaction between a user and a system
|
0 | 0 |
use cases
|
are the mechanism for capturing the desired behavior for the system that is under development, but they do not specify how the behavior is to be implemented.
|
emphasis on user-system interactions, rather than user's task itself identify &"actors&" define the &"normal course&" id alternative courses with #s corresponding to steps replaced
|
2 | 1 |
use cases
|
-used to explain and document the interaction between the users and the system -used as a means of user requirements
|
are descriptions of the way users will employ the features and functions of the new information system
|
2 | 1 |
use cases
|
• used for functional requirements analysis and specification • a step-by-step description of how a user will use the system-to-be to accomplish business goals
|
a more traditional mechanism for articulating a specific customer goal for system use and the interaction sequence(s) needed to achieve the goal; associated with software engineering
|
0 | 0 |
use cases
|
• used for functional requirements analysis and specification • a step-by-step description of how a user will use the system-to-be to accomplish business goals
|
a standard form of expressing requirements as a scenario-based task that the system must automate
|
1 | 0 |
use cases
|
• used for functional requirements analysis and specification • a step-by-step description of how a user will use the system-to-be to accomplish business goals
|
emphasis on user-system interactions, rather than user's task itself identify &"actors&" define the &"normal course&" id alternative courses with #s corresponding to steps replaced
|
2 | 1 |
use cases
|
a more traditional mechanism for articulating a specific customer goal for system use and the interaction sequence(s) needed to achieve the goal; associated with software engineering
|
emphasis on user-system interactions, rather than user's task itself identify &"actors&" define the &"normal course&" id alternative courses with #s corresponding to steps replaced
|
1 | 0 |
use cases
|
universal modelling language (uml) defined diagram that outlines the different user types and their potential interactions with the system
|
the primary driver for all uml diagramming techniques. depicts major activities performed by actors. describe basic high-level functions of a system. building blocks for continued design activities.
|
1 | 0 |
use cases
|
text stories of some actor using a system to meet goals
|
stories or scenarios of how people use the application
|
1 | 0 |
use cases
|
universal modelling language (uml) defined diagram that outlines the different user types and their potential interactions with the system
|
assume an interaction with a system as well as detailed understanding of the interaction.
|
0 | 0 |
use cases
|
piece of functionality performed by a system, that can be identified using a short description
|
a more traditional mechanism for articulating a specific customer goal for system use and the interaction sequence(s) needed to achieve the goal; associated with software engineering
|
0 | 0 |
use cases
|
universal modelling language (uml) defined diagram that outlines the different user types and their potential interactions with the system
|
described interactions between a system and external actors
|
0 | 0 |
use cases
|
piece of functionality performed by a system, that can be identified using a short description
|
• used for functional requirements analysis and specification • a step-by-step description of how a user will use the system-to-be to accomplish business goals
|
0 | 0 |
use cases
|
piece of functionality performed by a system, that can be identified using a short description
|
a standard form of expressing requirements as a scenario-based task that the system must automate
|
0 | 0 |
use cases
|
are descriptions of the way users will employ the features and functions of the new information system
|
way of describing interactions between users and a system using a graph and text
|
0 | 0 |
use cases
|
structured, well-documented and verbose descriptions of what a system should do used for testing. they are not the same as user stories
|
way of describing interactions between users and a system using a graph and text
|
0 | 0 |
use cases
|
key features of the system. something that provides some measurable result to the user or an external system
|
a set of use cases that illustrate the basic processes that the system needs to support
|
0 | 0 |
use cases
|
piece of functionality performed by a system, that can be identified using a short description
|
are the mechanism for capturing the desired behavior for the system that is under development, but they do not specify how the behavior is to be implemented.
|
0 | 0 |
use cases
|
piece of functionality performed by a system, that can be identified using a short description
|
emphasis on user-system interactions, rather than user's task itself identify &"actors&" define the &"normal course&" id alternative courses with #s corresponding to steps replaced
|
0 | 0 |
use cases
|
key features of the system. something that provides some measurable result to the user or an external system
|
written descriptions of user's interaction with the software product to accomplish a goal
|
2 | 1 |
use cases
|
assume an interaction with a system as well as detailed understanding of the interaction.
|
described interactions between a system and external actors
|
0 | 0 |
use cases
|
the primary driver for all uml diagramming techniques. depicts major activities performed by actors. describe basic high-level functions of a system. building blocks for continued design activities.
|
described interactions between a system and external actors
|
0 | 0 |
congestion control
|
throttle sender when network overloaded
|
+ many computers sending data at the same time -> packets lost (router's buffer overflows, delayed (queuing im router's buffer).
|
2 | 1 |
congestion control
|
service for the general welfare of the internet rather than end hosts, throttles sending when network is congested
|
a service for the general welfare in the internet rather than for the direct benefit of communicating processes
|
2 | 1 |
congestion control
|
throttle sender when network overloaded
|
src determines current capacity of the network, so that it doesn't overload it
|
3 | 1 |
matrix multiplication
|
performed by multiplying the elements of each row of the first matrix by the elements of each column of the second matrix. add the products.
|
multiply each row of matrix a by each column of matrix b use dot product - multiply matching items and sum result
|
3 | 1 |
data cache
|
a shared, reserved memory area that stores the most recently accessed data blocks in ram. also called buffer cache.
|
shared memory that stores the most recently accessed data blocks in ram
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.