問題一覧
1
Only provides the list of supported operations, type of parameters they can accept and return type of these operations.
Interface
2
provides the internal representation of a data structure. also provides the definition of the algorithms used in the operations of the data structure.
Implementation
3
Data structure implementation should implement its interface correctly.
Correctness
4
Running time or the execution time of operations of data structure must be as small as possible.
Time Complexity
5
Memory usage of a data structure operation should be as little as possible.
Space Complexity
6
Consider an inventory of 1 million(106) items of a store. If the application is to search an item, it has to search an item in 1 million(106) items every time slowing down the search. As data grows, search will become slower.
Data Search
7
although being very high, falls limited if the data grows to billion records.
Processor Speed
8
As thousands of users can search data simultaneously on a web server, even the fast server fails while searching the data.
Multiple Requests
9
This is the scenario where a particular data structure operation takes maximum time it can take.
Worst Case
10
This is the scenario depicting the average execution time of an operation of a data structure.
Average Case
11
This is the scenario depicting the least possible execution time of an operation of a data structure.
Best Case
12
Data are values or set of values.
Data
13
Data item refers to single unit of values.
Data Items
14
Data items that are divided into sub items are called
Group Items
15
Data items that cannot be divided are called
Elementary Items
16
An entity is that which contains certain attributes or properties, which may be assigned values.
Attribute and Entity
17
Entities of similar attributes form an entity set.
Entity Set
18
is a single elementary unit of information representing an attribute of an entity.
Field
19
is a collection of field values of a given entity.
Record
20
collection of records of the entities in a given entity set.
File
21
Each of its steps (or phases), and their inputs/outputs should be clear and must lead to only one meaning.
Unambiguous
22
An algorithm should have 0 or more well-defined inputs.
Input
23
An algorithm should have 1 or more well-defined outputs,
Output
24
Algorithms must terminate after a finite number of steps.
Finiteness
25
Should be feasible with the available resources.
Feasibility
26
An algorithm should have step-by-step directions, which should be___of any programming code.
İndependent
27
This is a theoretical analysis of an algorithm. Efficiency of an algorithm is measured by assuming that all other factors, for example, processor speed, are constant and have no effect on the implementation.
A Priori Analysis
28
This is an empirical analysis of an algorithm. The selected algorithm is implemented using programming language. This is then executed on target computer machine. In this analysis, actual statistics like running time and space required, are collected.
A Posterior Analysis
29
Time is measured by counting the number of key operations such as comparisons in the sorting algorithm.
time factor
30
Space is measured by counting the maximum memory space required by the algorithm.
Space Factor
31
an algorithm refers to defining the mathematical foundation/framing of its run-time performance. Using asymptotic analysis, we can very well conclude the best case, average case, and worst case scenario of an algorithm.
Asymptotic Analysis
32
Minimum time required for program execution.
Best Case
33
Average time required for program execution.
Average Case
34
Maximum time required for program execution
Worst Case
35
is the formal way to express the upper bound of an algorithm's running time.
Big Oh Notation
36
is the formal way to express the lower bound of an algorithm's running time.
Omega Notation
37
is the formal way to express both the lower bound and the upper bound of an algorithm's running time.
Theta Notation
38
An algorithm is designed to achieve optimum solution for a given problem. In greedy algorithm approach, decisions are made from the given solution domain.
Greedy Algorithms
39
This problem is to count to a desired value by choosing the least possible coins and the greedy approach forces the algorithm to pick the largest possible coin.
Counting Coins
40
This step involves breaking the problem into smaller sub-problems. Sub-problems should represent a part of the original problem.
Divide/Break
41
This step receives a lot of smaller sub-problems to be solved. Generally, at this level, the problems are considered 'solved' on their own.
Conquer/Solve
42
When the smaller sub-problems are solved, this stage recursively combines them until they formulate a solution of the original problem. When the smaller sub-problems are solved, this stage recursively combines them until they formulate a solution of the original problem.
Merge/Combine
43
is similar to divide and conquer in breaking down the problem into smaller and yet smaller possible sub-problems.
Dynamic Programming
44
In contrast to greedy algorithms, where local optimization is addressed, dynamic algorithms are motivated for an overall optimization of the problem.
comprison
45
defines a particular data with the following characteristics.
Data Definition
46
Definition should define a single concept.
Atomic
47
Definition should be able to be mapped to some data element.
Traceable
48
Definition should be unambiguous.
Accurate
49
represents an object having a data.
Data Object
50
is a way to classify various types of data such as integer, string, etc. which determines the values that can be used with the corresponding type of data, the type of operations that can be performed on the corresponding type of data.
Data Type
51
Those data types for which a language has built-in support are known as Built-in Data types. For example, most of the languages provide the following built-in data types. • Integers • Boolean (true, false) • Floating (Decimal numbers) • Character and Strings
built in data
52
Those data types which are implementation independent as they can be implemented in one or the other way are known as derived data types. These data types are normally built by the combination of primary or built-in data types and associated operations on them. For example − • List • Array • Stack • Queue
derived data
53
The data in the data structures are processed by certain operations. The particular data structure chosen largely depends on the frequency of the operation that needs to be performed on the data structure. • Traversing • Searching • Insertion • Deletion • Sorting • Merging
Basic Operations
54
is a container which can hold a fix number of items and these items should be of the same type.
Array
55
Each item stored in an array is called an element.
Element
56
Each location of an element in an array has a numerical
Index