Four-class labels
int64 0
3
| Binary labels
int64 0
1
| Entity
stringlengths 8
33
| Definition1
stringlengths 15
259
| Definition2
stringlengths 14
253
|
|---|---|---|---|---|
1 | 0 | cache memory | fast memory that stores frequently accessed information close to the processor | type of small, high-speed memory used to hold frequently used data |
2 | 1 | cache memory | a separate ram memory used to optimize performance by storing frequently accessed data. | very fast memory speeds up processing by storing recently used instructions so no need to fetch from memory |
1 | 0 | cache memory | a small-sized type of volatile computer memory that provides high-speed data access to a processor. | a type of high-speed memory that a processor can access more rapidly than main memory. sits between the data bus and memory |
1 | 0 | cache memory | the more cache memory on the cpu, the faster instructions can be stored, accessed and executed. | fast memory used by the cpu to store data required by the cpu |
1 | 0 | cache memory | a processor may contain a small amount of ram on its own chip accessible in one clock tick rather than several, for maintaining a copy of the most-used instructions/data | typically two or three levels of cache typical, including one on the same chip as cpu uses static random access memory (sram) |
1 | 0 | cache memory | a small unit of memory near the cpu. stores data and instructions that the cpu is likely to use. | small amount of fast memory located on the cpu chip or near it stores recent or frequently used instructions and data |
1 | 0 | cache memory | type of memory used to temporarily store frequently used data or programs, expensive and very fast | a type of memory used to temporarily store frequently used data or programs for quick access; similar to ram but faster. - a primary storage |
0 | 0 | cache memory | creating hierarchical access techniques that takes advantage of smaller but faster memories | small and fast memory used to hold selected data and to provide fast access (instructions used most frequently) |
3 | 1 | cache memory | is r.a.m. that the computer can access more quickly that normal r.a.m. | is random access memory that a computer processer can acess more quicly than it can access regular ram |
2 | 1 | cache memory | closest available memory for the cpu stores important data for rapid availability | a small unit of memory near the cpu. stores data and instructions that the cpu is likely to use. |
2 | 1 | cache memory | fast memory that stores frequently accessed information close to the processor | stores regularly used instructions and allows programs to run more efficiently and much faster. |
3 | 1 | cache memory | small and fast memory used to hold selected data and to provide fast access (instructions used most frequently) | small, fast memory to hold select data for faster access then would be possible otherwise. |
2 | 1 | cache memory | high speed memory where data from frequently used memory locations may be temporarily stored | a small, fast memory used to hold selected data and to provide faster access than would otherwise be possible. |
1 | 0 | cache memory | creating hierarchical access techniques that takes advantage of smaller but faster memories | a small, fast memory used to hold selected data and to provide faster access than would otherwise be possible. |
3 | 1 | cache memory | fast memory that stores frequently accessed information close to the processor | high speed memory that stores most frequently and recently used data |
3 | 1 | cache memory | special high speed memory used by a computer | a portion of memory used for high speed storage |
1 | 0 | cache memory | high speed memory where data from frequently used memory locations may be temporarily stored | small, fast memory to hold select data for faster access then would be possible otherwise. |
2 | 1 | cache memory | a type of high-speed memory that a processor can access more rapidly than main memory. sits between the data bus and memory | high-speed that sits between the processor and main memory. contains a subset of what is stored in main memory for faster access. |
0 | 0 | cache memory | fast and expensive memory type that is used by a cpu to increase read and write operations. | typically two or three levels of cache typical, including one on the same chip as cpu uses static random access memory (sram) |
0 | 0 | cache memory | typically integrated on the motherboard and directly embedded on the processor or main random access memory | a type of high-speed memory that a processor can access more rapidly than main memory |
3 | 1 | cache memory | small, fast memory to hold select data for faster access then would be possible otherwise. | a small, fast memory used to hold selected data and to provide faster access than would otherwise be possible. |
3 | 1 | cache memory | cpu and ram that a computer can access more quickly. | ram that can be accessed faster. |
1 | 0 | cache memory | -a special group of very fast circuitry usually built into the cpu (internal cache memory) -more of this means faster processing | typically two or three levels of cache typical, including one on the same chip as cpu uses static random access memory (sram) |
2 | 1 | cache memory | extremely quick memory that holds whatever data and code are being used at any one time | is a form of ram that gets data to the cpu for processing much faster than bringing the data in from the computers ram |
2 | 1 | cache memory | small and fast memory used to hold selected data and to provide fast access (instructions used most frequently) | high speed memory where data from frequently used memory locations may be temporarily stored |
1 | 0 | cache memory | typically integrated on the motherboard and directly embedded on the processor or main random access memory | a small-sized type of volatile computer memory that provides high-speed data access to a processor. |
1 | 0 | cache memory | creating hierarchical access techniques that takes advantage of smaller but faster memories | a small, fast memory used to hold selected data and to provide faster access. |
2 | 1 | cache memory | -a special group of very fast circuitry usually built into the cpu (internal cache memory) -more of this means faster processing | fast and expensive memory type that is used by a cpu to increase read and write operations. |
0 | 0 | cache memory | a processor may contain a small amount of ram on its own chip accessible in one clock tick rather than several, for maintaining a copy of the most-used instructions/data | -a special group of very fast circuitry usually built into the cpu (internal cache memory) -more of this means faster processing |
3 | 1 | cache memory | small, fast memory to hold select data for faster access then would be possible otherwise. | a small, fast memory used to hold selected data and to provide faster access. |
0 | 0 | cache memory | stores regularly used instructions and allows programs to run more efficiently and much faster. | type of small, high-speed memory used to hold frequently used data |
2 | 1 | cache memory | high speed memory that stores most frequently and recently used data | type of small, high-speed memory used to hold frequently used data |
1 | 0 | dimensionality reduction | purpose: - reduce time and memory requirements - easier visualization - eliminant irrelevant features | goal to represent numbers or faces with fewer variables. to preserve the structure of data. feature selection |
1 | 0 | dimensionality reduction | simplify the data without losing too much information. (merge several correlated features into one) | a typical unsupervised learning algorithm - simplifies the data without losing too much information - one way of doing this is feature extraction |
1 | 0 | dimensionality reduction | process which fixes unnecessarily many components of data | a typical unsupervised learning algorithm - simplifies the data without losing too much information - one way of doing this is feature extraction |
1 | 0 | dimensionality reduction | process which fixes unnecessarily many components of data | the goal is to simplify the data without losing too much information |
2 | 1 | dimensionality reduction | simplify the data without losing too much information. (merge several correlated features into one) | the goal is to simplify the data without losing too much information |
1 | 0 | dimensionality reduction | a typical unsupervised learning algorithm - simplifies the data without losing too much information - one way of doing this is feature extraction | the goal is to simplify the data without losing too much information |
2 | 1 | functional requirements | - services that a system should provide - how the system reacts to particular inputs - how it behaves in particular situations | statements of the services the system should provide, how the system should react to particular input and how it should behave. or what it shouldn't do |
2 | 1 | functional requirements | services the system should provide (e.g. how it should react to inputs) | the requirements that describe the capabilities of the system - what it must do or be able to do. |
0 | 0 | functional requirements | end-user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system | outlines what the system should do and can explicitly say what it cannot do |
0 | 0 | functional requirements | specify requirements that are related to the product features | define what the system does/should do example: the system will allows user to upload data |
0 | 0 | functional requirements | - state what users of your software should be able to accomplish - always state from perspective of user | specific system functionalities are listed, and developers begin to think about how the parts of the system should inter-operate to meet the functional requirements. |
3 | 1 | functional requirements | they describe system behaviors. statements of services the system should provide, how the system should act to particular inputs and how the system should behave in particular situations | statements of the services the system should provide, how the system should react to particular input and how it should behave. or what it shouldn't do |
2 | 1 | functional requirements | specify what the product must do, the actions it must perform to satisfy the fundamental reasons for its existence | state what the system must do, and how it must behave or react to runtime stimuli; are satisfied by assigning an appropriate sequence of responsibilities throughout the design. |
2 | 1 | functional requirements | a set of requirements that defines specific behavior and functions | -define how a system should/should not function -define specific facilities/service to be provided |
1 | 0 | functional requirements | what the system does. an action. a task the system provides to allow someone to achieve a goal. | describe user tasks that the system must support. |
1 | 0 | functional requirements | - state what users of your software should be able to accomplish - always state from perspective of user | requirements, which are related to functional aspect of software fall into this category. ex: user should be able to mail any report to management. |
0 | 0 | functional requirements | describe the interactions between the system and its environment independent from the implementation example: the user must be able to rent a car | specific system functionalities are listed, and developers begin to think about how the parts of the system should inter-operate to meet the functional requirements. |
2 | 1 | functional requirements | ~describe what the system should do ~statements of services provided by the system ~details of how the system should react in certain senarios. | define services the system should provide, behavior of the system and in some cases also what the system should not do |
1 | 0 | functional requirements | describe the interactions between the system and its environment independent from the implementation example: the user must be able to rent a car | outlines what the system should do and can explicitly say what it cannot do |
0 | 0 | functional requirements | the requirements that describe the capabilities of the system - what it must do or be able to do. | - define provided services - system functionalities - behaviors - reactions |
2 | 1 | functional requirements | detailed statements of the system's functionality | a description of what the system is to do. |
2 | 1 | functional requirements | - state what users of your software should be able to accomplish - always state from perspective of user | functional requirements specify what functions a system must provide to meet stated and implied stakeholder needs when the software is used under specific conditions [iso/iec 2001]. |
0 | 0 | functional requirements | - state what users of your software should be able to accomplish - always state from perspective of user | actions the system should perform and can be assigned to individual components of the system. |
2 | 1 | functional requirements | specific system functionalities are listed, and developers begin to think about how the parts of the system should inter-operate to meet the functional requirements. | requirements, which are related to functional aspect of software fall into this category. ex: user should be able to mail any report to management. |
2 | 1 | functional requirements | statements of the services the system should provide, how the system should react to particular input and how it should behave. or what it shouldn't do | define services the system should provide, behavior of the system and in some cases also what the system should not do |
1 | 0 | functional requirements | end-user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system | describe the interactions between the system and its environment independent from the implementation example: the user must be able to rent a car |
0 | 0 | functional requirements | the activities the system must perform to support the users' work | the activities the system must perform business uses, functions the users carry out use cases in chapter 1 |
2 | 1 | functional requirements | the product characteristics needed for the product to perform. | these define what the product of the project will do by focusing on how the end user will interact with the product. input/output, processing, error handling |
1 | 0 | functional requirements | these define what the product of the project will do by focusing on how the end user will interact with the product. | the product characteristics needed for the product to perform. |
1 | 0 | functional requirements | statements of service a system must provide.(isolated to individual components) | they describe system behaviors. statements of services the system should provide, how the system should act to particular inputs and how the system should behave in particular situations |
1 | 0 | functional requirements | the activities the system must perform to support the users' work | specific features and functions that a proposed it system must have. |
1 | 0 | functional requirements | relates directly to a process a system has to perform or information it needs to contain. | - define provided services - system functionalities - behaviors - reactions |
2 | 1 | functional requirements | - define provided services - system functionalities - behaviors - reactions | statement of services the system should provide, how the sys should react to particular inputs and how the sys should behave in situations |
3 | 1 | functional requirements | ~describe what the system should do ~statements of services provided by the system ~details of how the system should react in certain senarios. | - services that a system should provide - how the system reacts to particular inputs - how it behaves in particular situations |
1 | 0 | functional requirements | relates directly to a process a system has to perform or information it needs to contain. | statement of services the system should provide, how the sys should react to particular inputs and how the sys should behave in situations |
2 | 1 | functional requirements | the requirements that describe the capabilities of the system - what it must do or be able to do. | statement of services the system should provide, how the sys should react to particular inputs and how the sys should behave in situations |
2 | 1 | functional requirements | what inputs the system should accept what outputs the system should produce what data the system should store that other systems might use what computations the system may perform | specify the external behavior of the system such as the functionalities of the system from the end-user's view. |
1 | 0 | functional requirements | statement of services the system should provide, how the sys should react to particular inputs and how the sys should behave in situations | specify the external behavior of the system such as the functionalities of the system from the end-user's view. |
2 | 1 | functional requirements | statements of service a system must provide.(isolated to individual components) | - services that a system should provide - how the system reacts to particular inputs - how it behaves in particular situations |
1 | 0 | functional requirements | actions the system should perform and can be assigned to individual components of the system. | functional requirements specify what functions a system must provide to meet stated and implied stakeholder needs when the software is used under specific conditions [iso/iec 2001]. |
1 | 0 | functional requirements | - state what users of your software should be able to accomplish - always state from perspective of user | end-user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system |
2 | 1 | functional requirements | - services that a system should provide - how the system reacts to particular inputs - how it behaves in particular situations | they describe system behaviors. statements of services the system should provide, how the system should act to particular inputs and how the system should behave in particular situations |
0 | 0 | functional requirements | describe the interactions between the system and its environment independent from the implementation example: the user must be able to rent a car | actions the system should perform and can be assigned to individual components of the system. |
0 | 0 | functional requirements | the task the system must accomplish is completed | how the system will function from the user's perspective. |
2 | 1 | functional requirements | are &"statements of services the system should provide, how the system should react to particular inputs, and how the system should behave in particular situations&" (sommerville, 2015). | they describe system behaviors. statements of services the system should provide, how the system should act to particular inputs and how the system should behave in particular situations |
0 | 0 | functional requirements | describes how a system should interact with users and other systems | relates directly to a process a system has to perform or information it needs to contain. |
1 | 0 | functional requirements | statements of service a system must provide.(isolated to individual components) | statements of the services the system should provide, how the system should react to particular input and how it should behave. or what it shouldn't do |
0 | 0 | functional requirements | end-user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system | specific system functionalities are listed, and developers begin to think about how the parts of the system should inter-operate to meet the functional requirements. |
0 | 0 | functional requirements | what inputs the system should accept what outputs the system should produce what data the system should store that other systems might use what computations the system may perform | relates directly to a process a system has to perform or information it needs to contain. |
1 | 0 | functional requirements | requirements that define specific behavior or functions. what a system is supposed to do. they are stated such as &"the system shall do...&" | specify what the system must do |
1 | 0 | functional requirements | what the system needs to do according to the customer | define what the system does/should do example: the system will allows user to upload data |
1 | 0 | functional requirements | end-user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system | functional requirements specify what functions a system must provide to meet stated and implied stakeholder needs when the software is used under specific conditions [iso/iec 2001]. |
0 | 0 | functional requirements | specific system functionalities are listed, and developers begin to think about how the parts of the system should inter-operate to meet the functional requirements. | outlines what the system should do and can explicitly say what it cannot do |
1 | 0 | functional requirements | specific features and functions that a proposed it system must have. | the activities the system must perform business uses, functions the users carry out use cases in chapter 1 |
1 | 0 | functional requirements | relates directly to a process a system has to perform or information it needs to contain. | specify the external behavior of the system such as the functionalities of the system from the end-user's view. |
2 | 1 | functional requirements | the task the system must accomplish is completed | describe user tasks that the system must support. |
2 | 1 | functional requirements | describes how a system should interact with users and other systems | specify the external behavior of the system such as the functionalities of the system from the end-user's view. |
1 | 0 | functional requirements | actions the system should perform and can be assigned to individual components of the system. | requirements, which are related to functional aspect of software fall into this category. ex: user should be able to mail any report to management. |
1 | 0 | functional requirements | statements of service a system must provide.(isolated to individual components) | ~describe what the system should do ~statements of services provided by the system ~details of how the system should react in certain senarios. |
2 | 1 | functional requirements | - services that a system should provide - how the system reacts to particular inputs - how it behaves in particular situations | define services the system should provide, behavior of the system and in some cases also what the system should not do |
2 | 1 | functional requirements | services the system should provide (e.g. how it should react to inputs) | describes how a system should interact with users and other systems |
1 | 0 | functional requirements | what inputs the system should accept what outputs the system should produce what data the system should store that other systems might use what computations the system may perform | - define provided services - system functionalities - behaviors - reactions |
1 | 0 | functional requirements | outlines what the system should do and can explicitly say what it cannot do | functional requirements specify what functions a system must provide to meet stated and implied stakeholder needs when the software is used under specific conditions [iso/iec 2001]. |
0 | 0 | functional requirements | services the system should provide (e.g. how it should react to inputs) | relates directly to a process a system has to perform or information it needs to contain. |
0 | 0 | functional requirements | end-user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system | actions the system should perform and can be assigned to individual components of the system. |
1 | 0 | functional requirements | statements of service a system must provide.(isolated to individual components) | define services the system should provide, behavior of the system and in some cases also what the system should not do |
2 | 1 | functional requirements | ~describe what the system should do ~statements of services provided by the system ~details of how the system should react in certain senarios. | statements of the services the system should provide, how the system should react to particular input and how it should behave. or what it shouldn't do |
1 | 0 | functional requirements | what inputs the system should accept what outputs the system should produce what data the system should store that other systems might use what computations the system may perform | the requirements that describe the capabilities of the system - what it must do or be able to do. |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.