• Proceedings of the Computational Structural Engineering Institute Conference
• /
• 1992.10a
• /
• pp.105-111
• /
• 1992

A computer program for matrix structural analysis by object-oriented programming technique using $C^{++}$ language has been developed. Object, class, method and inheritance which are used in object-oriented programming are illustrated using a graphical representation. The matrix operations and the structural analysis by matrix displacement method were satisfactorily performed by the proposed program. Numerical tests demonstrate that this proposed program can be widely used for the matrix structural analysis for personal computers.s.

• Journal of Applied Reliability
• /
• v.16 no.1
• /
• pp.48-55
• /
• 2016

Purpose: The purpose of this study is to identify the object-oriented metrics which have strong impact on the reliability and fault-proneness of software products. The reliability and fault-proneness of software product is closely related to the design properties of class diagrams such as coupling between objects and depth of inheritance tree. Methods: This study has empirically validated the object-oriented metrics to determine which metrics are the best to predict fault-proneness. We have tested the metrics using logistic regressions and artificial neural networks. The results are then compared and validated by ROC curves. Results: The artificial neural network models show better results in sensitivity, specificity and correctness than logistic regression models. Among object-oriented metrics, several metrics can estimate the fault-proneness better. The metrics are CBO (coupling between objects), DIT (depth of inheritance), LCOM (lack of cohesive methods), RFC (response for class). In addition to the object-oriented metrics, LOC (lines of code) metric has also proven to be a good factor for determining fault-proneness of software products. Conclusion: In order to develop fault-free and reliable software products on time and within budget, assuring quality of initial phases of software development processes is crucial. Since object-oriented metrics can be measured in the early phases, it is important to make sure the key metrics of software design as good as possible.

• Journal of the Korean Professional Engineers Association
• /
• v.30 no.2
• /
• pp.79-86
• /
• 1997

As network has high speed and wide communication capability, users demand diverse and new software to satisfy their needs. To meet users needs, the softwares for multimedia or groupware or distributed virtual environments can communicate the widely distributed information fast and accurately. Even though the technology for this is under development, it is deficient to support the reliable computer communication. Distributed Object System aims, as the new paradigm of distributed system software development to overcome this problem, to obtain in distributed environment the easiness of development and management, expandability, reusability which object oriented technologies support by solving the complexity of communication processing through the object oriented methods. This paper aims to introduce distributed object system, its technological properties and the current status and trend of technology development related to its standardization. Additionally, with explaining the Replicated Shared Object System(RSOS) which is developed in our country as one of the distributed object systems, its future prospects and technical issues are discussed.

• Korean Journal of Child Studies
• /
• v.26 no.5
• /
• pp.15-30
• /
• 2005

The subjects of this study were 31 mothers and their first-born infants from middle class families living in Seoul. Mother-infant interactions were filmed at 5 and 13 months of age during naturalistic play situations at home. Questionnaire data were also collected. Results revealed that both maternal didactic and social interactions decreased over the 5 to 13 month time period but (only for infants) object-oriented interaction increased over time. Infant object-oriented interaction at 13 months was predicted by cumulative effects of both mother's social stimulation at 5 months and infant social interaction at 13 months. Infant's social interaction at 13 months was predicted by infant's object-oriented interaction at 13 months. Infant language development was predicted by mother's didactic stimulation.

• Transactions of the Korean Society of Automotive Engineers
• /
• v.11 no.5
• /
• pp.147-155
• /
• 2003

The application of object-oriented modeling to develop a powertrain performance simulation program, called O-DYN, is introduced. Powertrain components, such as the engine, transmission, shaft, clutch are modeled as classes which have data and method by using object-oriented modeling methodology. O-DYN, a performance simulation program, based on the object-oriented modeling is made in C++. One powertrain simulation using O-DYN is proposed, and it is expected that the simulation program or individual class constructed in this paper would be useful for automotive engineers to predict the performance of powertrains and to develop a simulation program.

• Proceedings of the KSME Conference
• /
• 2003.04a
• /
• pp.693-698
• /
• 2003

The application of object-oriented modeling to develop a powertrain performance simulation program, called P-DYN, is introduced. Powertrain components, such as the engine, transmission, shaft, clutch are modeled as classes which have data and method by using object-oriented modeling methodology. P-DYN, a performance simulation program, based on the object-oriented modeling is made in C++. One powertrain example is simulated through the P-DYN. It is expected that the simulation program or individual class constructed in this paper would be useful for automotive engineers in predicting the performance of powertrains and developing a simulation program.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.1
• /
• pp.83-89
• /
• 1999

For the object-oriented development methods authorized by OMG a number of official methodologies such as Booch, Coad/Yourdon methods are used in the development of the object-oriented soft ware and each methodology represents its process of analysis and design using different symbols. Between those notation methodologies there exist some differences as a matter of development, information for transfer, accordingly they act on the transfer of the information in the object-oriented development as obstacle and give rise to they natural outcome of error. The aim of this study is in the presentation of ideas that decrease the probability of errors by means of verify8ing the transferring ability of information which the existing diagrammatic notation methodologies have had on the basis of cognitive science, minimizing the cognitive load from the object-oriented development through enhancing symbols in each obstacles to transferring information and removing them.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.4
• /
• pp.817-833
• /
• 1996

Most object-oriented analysis and design methodologies are based on structured analysis and information modeling and are using for intuitive analysis and design models based on object-oriented programming languages. Therefore there are many problems such as when a system is implemented incorrect semantics and inconsistency between models.This paper submits a decomposition and design method for object, dynamic and functional module of the methodology of a new system development life-cycle. Thus, we present a new system development life cycle, and suggestsa object-oriented design methodand standards of module decomposition for the decomposition of object, dynamic, functional models due to object-oriented design procedures and specifications. This proposed method enables developers to reflect user's software requirements conveniently. We prove the validity and practicality of this object-oriented design method through implementing a real-system.

• Journal of KIISE:Software and Applications
• /
• v.27 no.5
• /
• pp.488-498
• /
• 2000

Object-oriented methodologies are widely used in the development of huge and complex systems since these methodologies produce the comprehensible and extensible model of systems. In order to apply an object-oriented methodology to a software development, developers should derive a method customized to a specific project from the methodology and, then, construct a development process from the method. Unfortunately, existing object-oriented methodologies lack a systematic facility for the construction of a method and a process. In this paper, we present a customizable object-oriented methodology to support the systematic derivation of a project specific method from the generic methodology. To derive a project specific method from the methodology, we transform the problem of a derivation to a planning problem and apply planning techniques. Our planning technique uses the description of an architecture that captures the structure and characteristics of a software under development as input and constructs an appropriate method with respect to the architecture. The architecture-centered construction facilitates the effective handling for the characteristics of the software since an architecture capture the decisions that must be maintained consistently during the development.

• Journal of Information Technology Applications and Management
• /
• v.11 no.4
• /
• pp.121-132
• /
• 2004

This paper surveyed 30 system designers and developers who had been participating in a project for five months to examine the usefulness of design artifacts for object-oriented system development. A set of nine requirement and design documents was selected in consideration of the IEEE guidelines. Overall the respondents appeared to agree that the artifacts were useful for system development. On the other hand, the contribution of design artifacts to maintenance was rated lower due to the frequent changes over the iterative process. Of the artifacts, considered more useful were use case specifications, UI design and operation specifications. The respondents were the most reluctant to write test cases. Designers did not like to document more details in the design artifacts than did developers. A future study is required to determine the economics end change management of documentation.