• Computers and Concrete
• /
• v.31 no.4
• /
• pp.307-314
• /
• 2023

In this paper we back-analyze a failure event of a 9 m high concrete cantilever wall subjected to earth loading. Granular soil was deposited into the space between the wall and a nearby rock slope. The wall segments were not designed to carry lateral earth loading and collapsed due to excessive bending. As many geotechnical programs rely on the Mohr-Coulomb (MC) criterion for elastoplastic analysis, it is useful to apply this failure criterion to the concrete material. Accordingly, the back-analysis is aimed to search for the suitable MC parameters of the concrete. For this study, we propose a methodology for accelerating the back-analysis task by automating the numerical modeling procedure and applying a machine-learning (ML) analysis on FE model results. Through this analysis it is found that the residual cohesion and friction angle have a highly significant impact on model results. Compared to traditional back-analysis studies where good agreement between model and reality are deemed successful based on a limited number of models, the current ML analysis demonstrate that a range of possible combinations of parameters can yield similar results. The proposed methodology can be modified for similar calibration and back-analysis tasks.

• The Journal of the Korea Contents Association
• /
• v.2 no.1
• /
• pp.68-76
• /
• 2002

Clustering is representative method of components classification. But, previous clustering method that use cohesion and coupling can not be effective, because design pattern has consisted by relation between classes. In this paper, we classified design patterns with special quality of pattern structure. Classification by clustering had expressed higher correctness degree than classification by facet. Therefore, can do that it is effective that classify design patterns using clustering algorithms that is automatic classification method. When we are searching design patterns, classification of design patterns can compare and analyze similar patterns because similar patterns is saved to same category. Also we can manage repository efficiently because of using and storing link information of patterns.

• Journal of Korean Tunnelling and Underground Space Association
• /
• v.18 no.5
• /
• pp.469-485
• /
• 2016

The failure of rock mass around deep tunnel, different from shallow tunnel largely affected by discontinuities, is dominated by magnitudes and directions of stresses, and the failures dominated by stresses can be divided into ductile and brittle features according to the conditions of stresses and the characteristics of rock mass. It is important to know the range and the depth of the V-shaped notch type failure resulted from the brittle failure, such as spalling, slabbing and rock burst, because they are the main factors for the design of excavation and support of deep tunnels. The main features of brittle failure are that it consists of cohesion loss and friction mobilization according to the stress condition, and is progressive. In this paper, a three-dimensional numerical model has been developed in order to simulate the brittle behavior of rock mass around deep tunnel by introducing the bi-linear failure envelope cut off, elastic-elastoplastic coupling and gradual spread of elastoplastic regions. By performing a series of numerical analyses, it is shown that the depths of failure estimated by this model coincide with an empirical relation from a case study.

• Journal of KIISE:Software and Applications
• /
• v.31 no.10
• /
• pp.1286-1303
• /
• 2004

Component-based Development is gaining a wide acceptance as an economical software development paradigm to develop applications by utilizing reusable software components. Well-defined interface manages coupling and cohesion between components, minimizes the effect on the user in case of component evolvement, and enhances reusability, extendibility and maintainability. Therefore, study on systematic development process and design guidelines for component interface has been required since the component has been introduced. In this paper, we propose three types of interfaces based on software architecture layers and functionality types； Provided Interface which provides functionality of a component, Required Interface which specifies required functionality that is provided by other components, and Customize Interface which tailors the component to customer's requirement. In addition, we suggest design criteria for well-designed interface, and systematic process and instructions for designing interface. We firstly cluster operations extracted from use case model and class model to identify Provided interfaces, and design Customize interfaces based on artifacts for variability. We also specify Required interfaces by identifying dependency among interfaces. Proposed interface design method provides traceability, throughout the component interface design. And furthermore, proposed guidelines support practical design for high quality component based on a case study.

• KIISE Transactions on Computing Practices
• /
• v.23 no.9
• /
• pp.535-541
• /
• 2017

Today, the scale of the computer software market has increased, and massive sized software has been developed to satisfy diverse requirements. In this context, software complexity is increasing and the quality of software is becoming more difficult to manage. In particular, software reuse is important for the improvement of the environments of legacy systems and new system development. In this paper, we propose a method to reuse modules that are certified by quality. Reusable levels are divided into code area (method, class, and component), project domain, and business levels. Based on the coupling and cohesion of software complexity, we propose a reusable module extraction mechanism with reusability metrics, which constructs a visualization of the "reusable module's chunk" based on the method and class levels. By applying reverse engineering to legacy projects, it is possible to identify reusable modules/objects/chunks. If these modules/objects/chunks are to be reused to develop an extension system or similar new system, we need to ensure software reliability in order to reduce the time and cost of software development.

• Journal of Intelligence and Information Systems
• /
• v.16 no.1
• /
• pp.1-16
• /
• 2010

Several techniques and methods for ontology modularization have been proposed recently. However, there are few ontology evaluation frameworks to evaluate these techniques and methods. Most researches on ontology modularization have not been focused on ontology modularization evaluation but ontology modularization process itself. In this paper, we devise a novel ontology modularization evaluation framework to measure the quality of ontology modules, logical integrity during modularization process and modularization tools. Experiments were conducted to validate the proposed framework. Three representative modularization approaches SWOOP, Prompt, and PATO were chosen and used to partition or extract modules from an ontology. Then the proposed evaluation framework is applied to these modules. The experiment results indicate that the modularization framework works well. The proposed framework would help ontology engineers improve ontology module quality, anticipate and reduce future maintenance as well as help ontology users to choose ontology modules that best meet their requirements.

• Journal of the Korea Computer Industry Society
• /
• v.2 no.4
• /
• pp.443-454
• /
• 2001

Software design patterns are reusable solutions to recurring problems that occur during software development. As programmers gain experience, they recognize the similarity of new problems to problems they have solved before. With even more experience, they recognize that solutions for similar problems follow recurring patterns. In this paper, as one of these reusable design-patterns, the Intermediator pattern for the efficient communication between business component is designed and implemented. Existent business components were way that follow Facade pattern. But Facade pattern is almost like the existing Interface pattern in that the communication of all the object outside the set is done by only one representative object, and this causes the traffic system to be overloaded. Therefore, the Intermediator pattern supplements the traffic overloads by improving the inefficient system of business components' communication through multi-interface, and make all communication behavior between objects done by Intermediator object which controls all actual behavior by way of Intermediator method implementation. Consequently, the Intermediator pattern is designed and implemented in this paper can bring down the level of coupling and raise the cohesion among objects, and refer to many of other object flexibly through several interfaces.

• Journal of Navigation and Port Research
• /
• v.36 no.5
• /
• pp.363-370
• /
• 2012

Recently, International Maritime Organization has been developing e-navigation implementation strategy plan, which is focused on various services for vessel safety navigation. Then, different kinds of software will be developed in maritime area and with this, the quality issues are to be expected becoming more important. In this paper, we adopt software refactoring techniques to reduce the complexity of structure on source code level. It makes software program more effective to understand and modify, without any change of outward behavior. The existing AIS broadcast server program is used as an example for our trial, and calculating coupling and cohesion metric are introduced to analyze the refactoring effect, taking account of the maintainability of IEC/ISO9126 software quality standards.

• 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.

• 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.