• The KIPS Transactions:PartD
• /
• v.8D no.4
• /
• pp.401-408
• /
• 2001

Object-oriented software development methods are used to develop object-oriented software systems. Object-oriented systems are believed to habe better modularity, reusability, maintainability, and extensibility than systems modeled in conventional methods. Current object-oriented software development methods, however, are modeled in terms of procedural, functional, and structural models. There models cause problems such as tight coupling among activities, and uncontrolled access to global artifacts. In this paper, were introduce OMOS(Object-oriented software development Method for Object-oriented software System), an object-oriented modeling of object-oriented software development methods. Artifacts and their related activities are modeled as classes and objects. Development lifecycles are modeled as interactions among the objects. By modeling the software development method in an object-oriented way, OMOS achieves better reusability, flexibility, extensibility, and maintainability.

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

• Proceedings of the Korea Society of Information Technology Applications Conference
• /
• 2005.11a
• /
• pp.1-6
• /
• 2005

The purpose of this paper is to propose a novel modeling approach called Services Ecosystem that applies the concept of ecosystems in ecology to Service-Oriented Software Development and Integration. For this purpose, an ecological system for software systems is proposed for the emerging Service-Oriented Computing paradigm, describing how participants interact with each other within their environments. Three emerging concepts, Service-Oriented Programming, Software Factories, and Service Grid, are employed to explain biotic and abiotic environments. Based upon the Services Ecosystem model, we demonstrate Services Ecosystem Model transformations by using a case example. The Services Ecosystem model is a novel approach for envisioning the Service-Oriented Computing paradigm in terms of an ecosystem in which the roles/perspectives of each participant and their relationships/interactions to environments are clearly described with a holistic view.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.10
• /
• pp.2680-2692
• /
• 1999

Software quality is classified by quality of process and product. In experience of Quality Management, it is known that quality level of product as it depends on goodness and badness of process and organization. As a result, improvement of software process has been important subject. According as this trends, ISO 12207 is publicated as standard of software life cycle process by ISO. For UML based object oriented development process, it is necessary that we should research detailed definition of activity and task of ISO 12207 process which is added, deleted or tailored in according to organization and project characteristics. In this thesis, by according with ISO 12207 software life cycle process, UML based object oriented development process is proposed. This process is composed of 7 steps and 19 activities including development phase, activity and product to improve quality of reliability. Usefulness of object oriented process for improvement of software quality is proved at three ways, which are comparative analysis of process characteristics, SPICE process evaluation and SPICE rick analysis.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.4
• /
• pp.100-105
• /
• 2008

Cost reduction, time to market, and quality improvement of software product are critical issues to the software companies which try to survive in recent competitive market environments. Software Product Line Engineering (SPLE) is one of the approaches to address these issues. The goal of software product line is to maximize the software reuse and achieve the best productivity with the minimum cost. In software product line, software components are classified into the common and variable modules for composition work. In this paper, we proposed a dynamic composition process based on aspect-oriented programming methodology in which software requirements are classified into the core-concerns and cross-cutting concerns, and then assembled into the final software product. It enables developers to concentrate on the core logics of given problem, not the side-issues of software product such as transactions and logging. We also proposed useful composition patterns based on aspect oriented programming paradigm. Finally, we implemented a prototype of the proposed process using Java and Aspect to show the proposed approach's feasibility. The scenario of the prototype is based on the embedded analysis software of telecommunication devices.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.3
• /
• pp.149-159
• /
• 2009

Nowadays, as the importance of service-oriented architecture software is recognized, the market of service-oriented software is getting bigger. In response to this, the requirements of high reliability and quality about service-oriented architecture software is getting increased. In this research, we clearly suggested the evaluation method by giving a specific evaluation example to evaluate the reliability qualify of service-oriented architecture software. It is expected to raise the objectivity and the utilization by inducing the reliability qualify improvement from this research.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.3
• /
• pp.622-632
• /
• 1999

As the complexity of software development is increasing due to networking, multimedia, and diverse system architecture, the need for effective software development methodology is increasing. Especially, due to software standard and internalization of software market, it is necessary to accept international quality such as ISO 9000-3. In addition, object oriented development methodology is required due to rapid propagation of OO technology and standardization. Recently, UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we develop Java and CORBA-based software, often UML is applied to Java and CORBA-based projects. However, current structural or OMT-based object-oriented methodologies. In this paper, we proposed UML-based development and concrete guidelines for each phase in order to apply UML to software development practically and effectively. Also, we define the transition guidelines and semantics between various development tasks. In addition, the analysis and design techniques of user interface and system development techniques needed in Web application development are presented.

• International journal of advanced smart convergence
• /
• v.5 no.1
• /
• pp.51-58
• /
• 2016

Regarding the role of infrastructure in the university and education sector, which is the most important factor for securing future competitiveness of a country, timely application from qualified applicants is an important factor. Thus, this study is to propose creative value regarding education and certification for smart IT sector, which will be a major topic in continuous technology development over the next 10 more years, and to bring out ripple effects by policy research regarding education and certification for smart IT sector in the software-oriented society. This research on policy regarding education and certification for smart IT sector in the software oriented society can be used as a guideline in education and certification for smart IT sector at colleges and can be also used for establishing groundwork for completing practical education required in smart ICT field at colleges and for cultivating mobile app program developers required by enterprises.

• The Journal of Korea Robotics Society
• /
• v.5 no.3
• /
• pp.240-250
• /
• 2010

A URC, which is a Ubiquitous Robot Companion, provides services to users in ubiquitous computing environments and has advantage of simplifying robot's hardware and software by distributing the complicated functionality of robots to other system. In this paper, we propose SOWL, which is a software architecture for URC robots and a mixed word of SOMAR and CAWL. SOWL keeps the advantages of URC and it also has the loosely-coupled characteristics. Moreover it makes it easy to develop of URC robot software. The proposed architecture is composed of 4 layers: device software, robot software, robot application, and end user layer. Developers of the each layer is able to build software suitable for their requirements by combining software modules in the lower layer. SOWL consists of SOMAR and CAWL engine. SOMAR, which is a middleware for the execution of device software and robot software, is based on service-oriented architecture(SOA) for robot software. CAWL engine is a system to process CAWL which is a context-aware workflow language. SOWL is able to provide a layered architecture for the execution of a robot software. It also makes it possible for developers of the each layer to build module-based robot software.