It is said that the first algorithm was the one that determines the greatest common divisor for two natural numbers that Euclid worked out in the 3rd century BC. Algorithm are at heart mathematical solution and calculations such as solving equations&sbquo calculating determinants of finding. The word refers to the methods or procedures to find solutions to problems that exist as gaps between reality and theory. Accordingly&sbquo software can be thought of as simply an algorithm. Since design itself is a method to solve problems&sbquo I believe it's possible to divide the algorithm of design methodology into "design as algorithm" and "algorithm as design." If the problem at hand is regarded as impossible to solve&sbquo then the process that identifies the difficulty in designing the solution and somehow solving the problem can itself be seen as a design method. In order to show that the design solution is valid&sbquo the design method itself must be sufficiently persuasive and convincing. The relationship between design and algorithms lies in their similarity as methods. But if the validity of the method begins and ends with its formalistic procedure&sbquo then while that method might be convenient for general solutions&sbquo it would be extremely difficult to reach specific solutions. Therefore&sbquo it's very important to introduce design as an algorithm in to the initial design procedure that deals with the theme of intractable problems. At that time&sbquo if the methodology we must consider is taken as the solution&sbquo the question will be whether it is an approximated design solution or one that can lead to a convincing design solution in terms of probability. Design is by no means a method that requires theoretical solutions for practical problems. Whether the solution is theoretical or not can only be determined when we have recognized the optimal design solution. When it's meaningful to demand a solution&sbquo has the same roots as an algorithm.