• Journal of KIISE:Software and Applications
• /
• v.34 no.7
• /
• pp.603-615
• /
• 2007

Software changes for various kinds of reasons and they increase maintenance cost. Software metrics, as quantitative values about attributes of software, have been adopted for predicting maintenance cost and fault-proneness. This paper proposes relationship between some typical object-oriented metrics and software changes in industrial settings. We used seven metrics which are concerned with size, complexity coupling, inheritance and polymorphism, and collected data about the number of changes during the development of an Information system on .NET platform. Based on them, this paper proposes a model for predicting the number of changes from the object-oriented metrics using multiple regression analysis technique.

• Journal of KIISE:Software and Applications
• /
• v.30 no.10
• /
• pp.912-924
• /
• 2003

Design restructuring improves software quality by reorganizing design elements and reduces maintenance cost. Object-oriented metrics can help to detect design flaws and find transformations to reorganize design elements. Basically, the transformations must preserve the behavior of an initial system. This paper describes a metric based restructuring technique preserving the behavior of object-oriented designs, founded on set theory, and gives its validity by applying the technique to applications written in Java. This paper also compares the technique with a technique using simulated annealing algorithm to show its effectiveness.

• Journal of KIISE:Software and Applications
• /
• v.28 no.6
• /
• pp.414-428
• /
• 2001

객체 지향 설계를 재구조화하기 위해서는 메소드와 속성들 사이의 관계를 파악해야 한다. 메소드와 속성들이 동일한 클래스에 속하는지를 추론하는 과정은 클래스 자료 참조 분석과 메소드 호출 분석에 의존한다. 최근의 많은 소프트웨어들은 규모가 방대하고 복잡하여 개발자가 도구를 사용하지 않고 수작업으로 설계를 재구조화기 어려우며 또한 너무 많은 시간과 노력이 요구된다. 본 논문에서는 메트릭을 이용하여 객체 지향 설계를 자동적으로 재구조화하는 방법을 기술한다. 먼저 메소드, 속성, 클래스, 그리고 그들의 관계츨 추상화된 모델로 표시한다. 이 모델을 기반으로 객체 지향 설계를 정량적으로 측정할 응집도와 결합도 메트릭을 정의한다. 본 논문의 메크릭은 재고조화 과정 동안에 여러 다른 설계들을 효율적으로 비교하기 위한 유용한 기준을 제공한다. 기본 재구조화 행위들과 그 의미(semantics)를 정의하고 메트릭과 행위들을 사용하여 설계를 자동적으로 재구조화한다.

• The KIPS Transactions:PartD
• /
• v.13D no.2 s.105
• /
• pp.241-250
• /
• 2006

Software maintenance is an important and very expensive activity in software life cycle. To estimate the maintainability cost of software, many software metrics have been proposed. This paper presents the result of an experimental study to explore the relationship between maintainability and some software metrics. LCOM, RFC, DAC, and LOC are employed as metrics and time really spent for maintenance activity has been collected. In the experimental study, we have found that for some systems, the existing metrics may not be an indicator to maintenance effort, which is not consistent with our general knowledge on the relationship between them. Specifically speaking, we recognized that there should be more empirical study on the relationship between metrics and maintainability of softwares which have been developed using recent technologies such as software architecture and design pattern.

• Journal of KIISE:Computing Practices and Letters
• /
• v.7 no.2
• /
• pp.151-164
• /
• 2001

Java, used as the most representative object-oriented language, isil becoming the popular language for Internet/Intranet based program development. Moreover, it is used for development language in a variety of areas such as component based development language. In the view of reuse and maintenance of developed program, quality evaluation of program is becoming a more important issue. So, metrics measurement for quality evaluation of program that is developed at present including existing Java application is necessary. However, it is necessary that whether existing object-oriented software metrics is suitable on Java program is to be validated So, in this paper, we build an automated metrics measurement system that needs to validate on object-oriented software metrics and wish to support metrics measurement that is to determine it. The purpose of this system is to support a precise quality evaluation tool. In this system, we apply the metrics classified by Briand. Briand classified the metrics by formalizing mathematically them to verify feasibility of existing object-oriented software metrics. Using the proposed system, we can make comparison and analysis of validation on existing object-oriented metrics by calculating quantitative information more rapidly from Java source program. If there is any problem in feasibility of the metrics, we can establish a suitable metrics on Java program by considering reiJ,1forcement of the existing metrics or proposing new metrics.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.2
• /
• pp.373-384
• /
• 2000

There are many researches about metrics to measure a quality of Object-Oriented(OO) software. However, most of them have only discussed a concept or properties of metrics, and have not shown the detailed procedure for measuring them. They also define a measurement indicator as a threshold, but it has been influenced on a project size or application domains. In this paper, we propose metrics based on characteristics of OO design such as size, complexity, coupling and cohesion, and use a propotion to an average as the measurement indicator. It is easy to classify classes which have a result above the average, and to predict classes which reduced the quality of OO design. They will be modified to hold the average. Proposed metrics are analytically evaluated by Weyuker's nine properties. They are satisfied with seven properties except two properties co not apply to OO metrics. Also, we design a quality assessment system, ASSOD(ASsessment System of Object oriented Design), to measure the quality of the OO design independent of the platform.

• Journal of KIISE:Software and Applications
• /
• v.30 no.7_8
• /
• pp.618-641
• /
• 2003

Various quality models using quality factor, quality criteria and metrics have been proposed in order to evaluate quality of software products. However, a customized quality model which is specific to the characteristics of software component is required. In this paper, we propose external quality prediction techniques enable us to predict what external quality the final software product will have by using metrics as with internal attributes of software in development. We also propose a model not only for measuring quality by using metrics but also for applying internal attributes of ISO 9126 into artifacts of software component development.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.04b
• /
• pp.427-429
• /
• 2004

잘 설계된 모든 객체지향 구조들은 패턴들로 가득 차 있다는 점에서 볼 때, 디자인 패턴은 상당히 유용하다. 특히 정확성. 강건성, 유연성, 재사용성, 효율성 측면에서 볼 때, 디자인 패턴은 충분히 가치가 있다. 이 논문에서는 디자인 패턴을 사용한 소프트웨어에서 테스트 가능성은 어떻게 달라지는지를 분석하고자 한다. 테스트 가능성을 측정하는 메트릭을 이용하여, 패턴이 적용된 소프트웨어와 적용되지 않은 소프트웨어에서의 메트릭을 분석한다. 측정된 값은 디자인 패턴을 사용하지 않은 소프트웨어에 비해, 사용한 소프트웨어에서 몇몇 메트릭이 낮은 값을 보였다 이것은 디자인 패턴을 적용하는 것이 오류의 가능성이나 테스트 케이스의 수를 줄여 준다는 것을 의미한다. 또한 어떤 디자인 패턴이 적용되었는지를 알고 있을 때 그 디자인 패턴에 맞는 테스트 케이스가 무엇인지 분석하였다.

• The Journal of Society for e-Business Studies
• /
• v.8 no.2
• /
• pp.113-129
• /
• 2003

Component-based software development (CBSD) has been recognized effective reuse techniques for software development by many of researchers and companies. The purpose of CBSD is to produce a high quality software system quickly through using verified software component which is contained fine-grained business logics. This paper suggests the metrics and techniques for to extract component and its interface from legacy object oriented application. For extract component, we apply metrics to measure complexity, cohesion and coupling to the legacy system.

• Journal of KIISE:Software and Applications
• /
• v.31 no.6
• /
• pp.728-740
• /
• 2004

The increasing complexity and shorter life cycle of software have made it necessary to reuse software. Object-oriented development had not provided extensive reuse and computing infrastructures are evolving from mainframe to distributed environments. However, components provide more advanced means of structuring, describing and developing system, because they are more coarse-grained and have more domain-specific aspects than objects. And they are also suited for distributed environment due to their reusability and granularity. In this paper, we present a process including the static metrics and guidelines that can be applied to transform object-oriented systems into component-based systems. Our process consists of two parts: First, basic components are created based upon composition and inheritance relationships between classes. Second, intermediate system is refined into component-based system with the static metrics and guidelines we propose.