• Journal of Korea Society of Digital Industry and Information Management
• /
• v.7 no.3
• /
• pp.37-42
• /
• 2011

Nowadays software developers are moving from conventional software process technologies to the object-oriented paradigm. To develope the object-oriented softwares efficiently, various software metrics have been suggested. Coupling refers to the degree of independence between components of the system. It has long been well known that good software practice calls for minimizing coupling interaction. Many researches have been studied coupling metrics of the object- oriented systems. We review Chidamber and Kemerer's work & Li's work. In this paper, we study the coupling of the overall structures of object-oriented systems by analyzing the class diagram of UML. We propose four coupling metrics for object-oriented softwares. First, we use an established coupling metric for object- oriented systems as a basic coupling metric. Then we modify the basic coupling metric by including indirect coupling between classes, We also suggest two relative coupling metrics to measure coupling between subsystems. We investigate the theoretical soundness of the proposed metrics by the axioms of Briand et al. Finally, we apply the presented metrics to a practical case study. This coupling metric will be helpful to the software developers for their designing tasks by evaluating the coupling metric of the structures of object-oriented system and redesigning tasks of the system.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.219-227
• /
• 2011

Service Oriented Architecture (SOA) is rapidly emerging as the efficient approach in contemporary complex, heterogeneous computing environments. SOA increases the adaptability by loose coupling and its main feature is that three elements such as service provider, service requester and service registry are connected with each other systematically. To design the service-oriented system efficiently, a metric to measure the coupling between services accurately is needed. In this paper, we propose four coupling metrics for SOA based softwares. First, we suggest a coupling metric for service-oriented systems by modifying an established coupling metric of object-oriented systems. Then we suggest another coupling metric which includes indirect coupling between services. We also suggest two relative coupling metrics to measure coupling between subsystems. We investigate the theoretical soundness of the proposed metrics by the axioms of Briand et al. Finally, we apply the presented metrics to an industrial-scale case study.

• The KIPS Transactions:PartD
• /
• v.12D no.4 s.100
• /
• pp.609-616
• /
• 2005

The component-based development methodology becomes famous as the reuse technology to improve the high productivity of software development. It is necessary component metrics for component-based systems, because the designed components should be measurable to improve the quality of the software. Therefore this paper propose a coupling metric for component design which is reflected in characteristics of component. This paper suggest a case study and comparative analysis result about conventional metrics to verify the accuracy of our coupling metric. The Uoposed coupling metric measure the quality of components accurately and satisfies necessary conditions of coupling metric suggested by Briand and others.

• Journal of Internet Computing and Services
• /
• v.9 no.5
• /
• pp.85-97
• /
• 2008

Recently, service-oriented systems have been issued by their properties of reducing software development time and effort by reusing functional service units. The reusability of services can effectively promote through loose coupling between services and loose coupling between services depends on component-based system. That is, the component-based system is designed by grouping the tightly coupled classes of the object-oriented system and the service-oriented system is designed by the component-based system. Therefore, to design the component-based system and service-oriented system efficiently, a metric to measure the coupling between classes accurately needs. In this paper, we propose a coupling metric between classes applying a structural property, a dynamic property, and the normalized value by 0-1. We prove the theoretical soundness of the proposed metric by the axioms of briand et al, and suggest the accuracy and practicality through a case study. We suggest the evaluation results of the proposed metric through a comparison with the conventional metrics.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.625-634
• /
• 2004

When constructing a component based system, It is understood that identifying reusable and independent business components is of utmost importance. However, according to conventional component based developing methodologies, most of developers depend on their experience and/or intuition for identification of business components. Furthermore, there are no criteria to evaluate whether the identified business components are more independently defined or not. Therefore, we propose a component identification metrics to apply to component properties In order to complement the difficulties of identifying business components through developers' experience and/or intuition. The metrics defined are the criteria for identifying the business Components and/or for evaluating the Identified components. We propose both a cohesion metric, and a coupling metric, to which component properties are applied, wherein those properties can be understood by high cohesion in, and low coupling between, components. Moreover, we propose an independence metric that can evaluate the degree of independence for a particular component by ratio of the cohesion and coupling of components. The metrics that we propose are applied to case study which demonstrates the identification of more independent business components and the validity of our metrics.

• Journal of KIISE:Computing Practices and Letters
• /
• v.14 no.1
• /
• pp.81-85
• /
• 2008

The coupling measurements of object oriented programs can be valuable information for various maintenance tasks and there exists a variety of metrics proposed by numerous researchers. Those metrics, however, cannot measure the strength of dependencies between classes, but only imply the existence of dependencies. Hence they are of limited value for assisting maintenance tasks such as refactoring and system decomposition, which requires information about the strength of dependency. In this paper, a coupling metric which can measure the strength of dependence as well as detect the existence of dependencies is proposed. Our coupling metric is evaluated based on the cost required for performing the maintenance tasks. We have applied the proposed coupling metric to an example of system decomposition in an effort to assess the potential benefits of our approach for maintenance tasks.

• Journal of KIISE:Software and Applications
• /
• v.27 no.6
• /
• pp.595-606
• /
• 2000

Software metrics evaluate the development process, measure the software development effort, and control the software quality effectively. Moreover in a current status to emphasize reusability, it is necessary to study of cohesion and coupling that plays an important role in evaluating reusability. Object oriented methodology to use the concept like encapsulation, inheritance, and polymorphism demands metrics that are different from existing procedural methodology, so a study for object oriented metrics is in progress at the present time. In this paper, we propose cohesion and coupling metrics for object oriented program, evaluate the proposed metrics by using the complexity properties proposed by Weyuker and Briand, and extract cohesion and coupling from C++ code.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.91-102
• /
• 2002

We need a component-based system to reflect software changes in user's requirements, to implement a system at a rapid speed as well as to efficiently manage the system in a maintenance phase and to easily change software. Moreover, the component-based system has a merit in development cost. However, existing component development methodology for implement of component-based system is inefficient in object identification for component identification. Moreover, the existing component development methodology also fails to provide any method to identify system component. It merely provides procedures and methods to identify business component focused on a whole system domain. In addition, it has another problem that it considerably relies on developer's experiences and intuitions for component identification. Therefore, according to this paper, RUP (Rational Unified Process) is applied from a requirement analysis phase to an object identification phase in order to improve the inefficiency of object identification. In addition, this paper procedures and methods for system component identification, and identifies business components based on the identified system component, rather than on the whole system domain. This paper also provides and applies cohesion metric and coupling metric so as to overcome the problem that component identification depends on developer's intuitions and experiences. Accordingly, the component identification method proposed in this paper, may identify components more effectively based on facility of object identification, functional reusability of components, traceability, and independence of components.

• Proceedings of the Korean Information Science Society Conference
• /
• 2007.06a
• /
• pp.33-34
• /
• 2007

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.980-990
• /
• 2004

The component-based development methodology aims at the high state of abstraction and the reusability with components larger than classes. It is indispensible to measure the component so as to improve the quality of the component-based system and the individual component. And, the quality of the component should be improved through putting the results into the process of the development. So, it is necessary to study the component metric which can be applied in the stage of the component analysis and design. Hence, in this paper, we propose component cohesion, coupling, independence metrics reflecting the information extracted in the step of component analysis and design. The proposed component metric bases on the similarity information about behavior patterns of operations to offer the component's service. Also, we propose the redesigning process for the improvement of component design. That process uses the techniques of clustering and is for the thing that makes the component as the independent functional unit having the low complexity and easy maintenance. And, we examine that the component design model can be improved by the component metrics and the component redesigning process.