• The Transactions of the Korea Information Processing Society
• /
• v.5 no.10
• /
• pp.2533-2545
• /
• 1998

객체지향 소프트웨어척도는 객체들의 규모와 구성 및 객체들간의 관계를 고려하면서, 전반적인 객체지향 특성을 반영하여야 한다. 본 논문에서는 객체지향 소프트웨어의 규모 및 복잡도에 영향을 주는 4가지의 객체지향 패러다임 관련 특성(요인)들을 정하고, 객체지향 설계 스타일 지침들을 기반으로 객체지향 소프트웨어의 품질 측정을 위한 객체점수 척도를 제안한다. 그 지침들은 기존의 지침들에 하나의 새로운 지침을 추가한 것으로서 인지 심리학에서의 청크 이론을 기반으로 제시 된 것들이다. 제안된 객체점수 척도의 타당성 검증을 위해서 실험적 분석을 행하였는데, 이는 제안 척도가 전반적으로 객체 지향 개념 및 특성을 잘 반영하는지를 평가하기 위한 것으로 같은 출력을 갖는 두 C++ 프로그램을 제안된 척도로 측정하여 비교하였다. 이러한 실험 결과 제안한 객체점수 유용성이 입증되었다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.457-459
• /
• 2000

객체지향 방법론은 캡슐화(encapsulation), 상속(inherit), 다형성(polymorphism)과 같은 개념을 이용하기 때문에 기존의 절차적 방법론과는 다른 척도가 필요하다. 본 논문에서 제안하는 척도는 객체지향 시스템의 개발 절차 가운데 분석 단계에서 추출할 수 있는 정보만을 사용하여, 클래스가 객체지향 개념에 따라 잘 구성되었는지를 측량하게 된다. 이를 위하여 본 논문에서는 클래스의 품질을 측량하기 위한 척도로 협력의 복잡도와 인터페이스 복잡도를 제안한다. 협력의 복잡도는 클래스가 잠재적으로 얼마나 복잡할 수 있는지를 측량하기 위한 것으로서 클래스가 가지는 책임의 개수를 조사하여 정의된다. 인터페이스 복잡도는 클래스와 협력 관계에 있는 다른 클래스들의 인터페이스를 조사하여 정의된다. 제안된 척도는 기존의 척도들이 가지고 있는 문제점을 해결하기 위하여 이해하기 쉬운 수학적 명세를 용하였으며, 제안된 척도에 대한 수학적 증명과 사례 연구를 통한 검증을 하였다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.528-530
• /
• 2000

최근 객체지향 소프트웨어 개발이 일반화되면서 품질 좋은 객체지향 소프트웨어의 개발을 돕기 위한 목적으로 객체지향 소프트웨어 복잡도 척도에 관한 연구들이 다양하게 행해져 왔다. 대부분의 연구가 구조적 복잡도 측정에 중점을 두어 프로그램 크기와 관련된 요인들을 측정하는 척도들이 제시되었다. 한편 소프트웨어 개발이나 복잡도 측정에 대하여 인지 심리 이론을 적용하여, 인간의 단기 기억의 한계 7$\pm$2와 제어 논리 처리에 3$\pm$1을 고려한 연구들이 많이 행해졌다. 본 논문에서는 프로그램 볼륨과 복잡도의 관계를 조사하기 위해 13개 척도의 값을 추출한 후 통계적 분석을 수행하고, 인지 심리 이론과의 관계를 파악해 보았다.

• Proceedings of the Korean Institute of Intelligent Systems Conference
• /
• 2001.12a
• /
• pp.324-327
• /
• 2001

본 논문은 Chidamber와 Kemerer가 제안한 객체지향 설계를 위한 척도를 바탕으로 이를 확장하여 클래스 상속 구조의 유지보수성을 이해성과 변경성 측면에서 측정하는 새로운 객체지향 척도를 제안했다. 그리고 클래스 상속 구조의 예를 들어 비교 평가를 함으로써 Chidamber와 Kemerer의 척도 및 Henderson-Sellers의 척도보다 우수함을 보였다.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.15 no.6
• /
• pp.780-787
• /
• 2005

Many researches and validations for the complexity metrics of the object-oriented systems have been studied. Most of them are aimed for the measurement of the partial aspects of the systems, for example, the coupling between objects, the complexity of inheritance structures, the cohesion of methods, and so on. But the software practitioners want to measure the complexity of overall system, not partial. We studied the complexity of the overall structures of object-oriented systems by analyzing the class diagram of UML. The class diagram is composed of classes and their relations. There are three kinds of relations, association, generalization, and aggregation, which are making the structure of object-oriented systems to be difficult to understand. We proposed a heuristic metric to measure the complexity of object-oriented systems by putting together the three kinds of the relations. Tn analyze the complexity of the structure of a object-oriented system for the maintainability of the system, we measured the degree of understandability of it, the reverse engineering time to draw a class diagram from the source codes, and the number of errors in the diagram. The results of this experiment shows that our proposed metric has a considerable relationship with the complexity of object-oriented systems. The metric will be helpful to the software developers for their designing tasks by evaluating the complexity of the structures of object-oriented systems and redesigning tasks , of them for the future maintainability.

• Proceedings of the Korean Information Science Society Conference
• /
• 1999.10a
• /
• pp.632-634
• /
• 1999

다양한 소프트웨어 척도들이 절차적 패러다임에서 유용하다는 것이 밝혀졌고 객체지향 패러다임에 대해서도 많은 설계 척도들이 언어 독립적으로 제안되었다. 언어 독립적인 척도로부터 특정 프로그램밍 언어에 대한 척도를 명확하게 하는 것이 중요한데도 불구하고 Java 언어에 대한 척도는 거의 제안되지 않고 있는 형편이다. 따라서 본 논문에서는 Briand가 제안한 속성을 만족하는 척도들과 Java 언어의 특징인 내부 클래스를 반영한 척도와 크기 척도 등 13개의 척도를 Java 프로그램에 적용하여 척도들 사이의 관계를 분석하였다. 클래스의 크기와 메소드 호출 빈도, 응집도, 자식 클래스의 수, 내부 클래스와 상소 계층의 깊이가 주요 인자라는 것을 보여준다. 또한 응집도가 다른 척도들과 음의 관계를 가진다는 것이 발견되었다. 보다 적은 척도를 가지고 인자를 설명할 수 있는 회귀식을 도출하고 교차검증을 실시하였다.

• The KIPS Transactions:PartD
• /
• v.8D no.1
• /
• pp.71-80
• /
• 2001

Object-Oriented (OO) methodology to use the concept like encapsulation, inheritance, polymorphism, and message passing demands metrics that are different from structured methodology. There are many studies for OO software metrics such as program complexity or design metrics. But the metrics for the analysis class need to decrease the complexity in the analysis phase so that greatly reduce the effort and the cost of system development. In this paper, we propose new metrics to measure the complexity of analysis classes which draw out in the analysis phase based on Unified Process. By the collaboration complexity, is denoted by CC, we mean the maximum number of the collaborations can be achieved with each of the collaborator and detennine the potential complexity. And the interface complexity, is denoted by IC, shows the difficulty related to understand the interface of collaborators each other. We prove mathematically that the suggested metrics satisfy OO characteristics such as class size and inheritance. And we verify it theoretically for Weyuker' s nine properties. Moreover, we show the computation results for analysis classes of the system which automatically respond to questions of the it's user using the text mining technique. As we compared CC and IC to CBO and WMC, the complexity can be represented by CC and IC more than CBO and WMC. We expect to develop the cost-effective OO software by reviewing the complexity of analysis classes in the first stage of SDLC (Software Development Life Cycle).

• Journal of the Korean Institute of Intelligent Systems
• /
• v.14 no.6
• /
• pp.793-799
• /
• 2004

Many researches and validations for the complexity metrics of the object-oriented systems have been studied. Most of them are aimed for the measurement of the partial aspects of the systems, for example, the coupling between objects, the complexity of inheritance structures, the cohesion of methods, and so on. But the software practitioners want to measure the complexity of overall system, not partial. We studied the complexity of the overall structures of object-oriented systems by analyzing the class diagram of UML. The class diagram is composed of classes and their relations. There are three kinds of relations, association, generalization, and aggregation, which are making the structure of object-oriented systems to be difficult to understand. We proposed a heuristic metric to measure the complexity of object-oriented systems by putting together the three kinds of the relations. This metric will be helpful to the software developers for their designing tasks by evaluating the complexity of the structures of object-oriented system and redesigning tasks of the system.

• Journal of Korea Society of Industrial Information Systems
• /
• v.6 no.4
• /
• pp.22-29
• /
• 2001

As the importance of software measurement increases, there are more researches developing the new software measure. Given the importance of object-oriented development techniques, one specific area where this has occurred is coupling measurement in object-oriented systems. This thesis presents the coupling measure COM based on the methods and OOC based on the classes in measuring the coupling of object-oriented systems. And, it evaluates them using the coupling properties suggested by Briand while it compares them with other coupling measures by applying them to a system developed in the language of C++programming language.

• Journal of KIISE:Software and Applications
• /
• v.28 no.10
• /
• pp.720-731
• /
• 2001

Complexity metrics have been developed for the structured paradigm of software development are not suitable for use with the object-oriented(OO) paradigm, because they do not support key object-oriented concepts such as inheritance, polymorphism. message passing and encapsulation. There are many researches on OO software metrics such as program complexity or design metrics. But metrics measuring the complexity of classes at the OO analysis phase are needed because they provide earlier feedback to the development project. and earlier feedback means more effective developing and less costly maintenance. In this paper, we propose the new metrics to measure the complexity of analysis classes which draw out in the analysis based on RUP(Rational Unified Process). By the collaboration complexity, is denoted by CC, we mean the maximum number of the collaborations can be achieved with each of the collaborator and determine the potential complexity. And the interface complexity, is denoted by IC, shows the difficulty related to understand the interface of collaborators each other. We verify theoretically the suggested metrics for Weyuker's nine properties. Moreover, we show the computation results for analysis classes of the system which automatically respond to questions of the user using the text mining technique. As a result of the comparison of CC and CBO and WMC suggested by Chidamber and Kemerer, the class that have highly the proposed metric value maintain the high complexity at the design phase too. And the complexity can be represented by CC and IC more than CBO and WMC. We can expect that our metrics may provide us the earlier feedback and hence possible to predict the efforts, costs and time required to remainder processes. As a result, we expect to develop the cost-effective OO software by reviewing the complexity of analysis classes in the first stage of SDLC(Software Development Life Cycle).