• Journal of Software Engineering Society
• /
• v.24 no.3
• /
• pp.77-89
• /
• 2011

Software product line engineering is a software reuse paradigm that helps organizations improve software productivity and quality by developing software products from reusable core assets. For the satisfaction of common and variable requirements among products in the product line, the core assets must be configurable according to the selection of variable features. Therefore, unlike software architecture model of a single product, product line architecture model must embed and express variabilities among the products. Many researches have proposed methods of embedding and expressing variabilities in the product line architecture models, but there are few comparative studies on the proposed methods. In this paper we discuss strong points and weak points of the proposed methods and compare expressiveness of the methods, which helps select a proper method.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.6
• /
• pp.1803-1809
• /
• 2000

With the wide usage of the Internet, there use of pre-developed software is becoming important more and more in the development of various communication software. In this paper, the architecture to reuse the communication software is proposed. It is applied to the development of MIB-II system group of SNMP agent software for reusing. If Communication software is developed using this architecture, the software development life cycle will be abridged and the development cost will be reduced.

• Journal of Korea Society of Industrial Information Systems
• /
• v.7 no.3
• /
• pp.15-22
• /
• 2002

As the size and complexity of software systems increase, the design and specification of overall system structure become more significant issues than the choice of algorithms and data structures of computation. Software architecture serves as a framework for understanding system components and their interrelationships. Software architectures can be reusable assets to achieve low costs, high productivity, and consistent quality. We have developed a software architecture design environment, called Happy Work. In this paper, we would like to present the structure and functions of Happy Work. Happy Work has two main functions. First, it Provides a graphic editor for modeling of software architecture diagram. Second it provides an ADL, called HWL(Happy Work language). HWL is a language that describes software architect

• The KIPS Transactions:PartD
• /
• v.8D no.1
• /
• pp.54-61
• /
• 2001

Software architectures can be restructured by modification and replacement during design processes, and appropriate software architectures for developments can be more than one. Therefore, developers are required to specify efficiently the modification elements of architectures, and manage different versions of an architecture designed for various aspects. In this paper, we propose a mechanism that can restructure legacy architecture and a new software architecture designed with reuse of it in integrated form, and define the specification elements and structure of the proposed architecture restructuring specification. It provides the method that can reference and reuse architectures designed with various aspects of developers in architecture design processes.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.11
• /
• pp.101-110
• /
• 2021

The Weapon Control Software performs the function of supporting weapon operation within the Naval Combat System in connection with the Weapon System. As Weapon Control Software depends on an Weapon System, it has the characteristic that software modification is unavoidable with the change in Interface information. Modification of software causes an increase in development costs since it must take verification step such as software reliability test. In this paper, We design the standard architecture of weapon control software to minimize the modification elements of existing weapon control software. For Interface information management, Feature Model were applied to make a division between common factor and variable factor. In addition, Strategy Pattern were applied to improve the software design. Software evaluation test results show that new architecture provides better modifiability and reuse than existing software as well as the cost of development decrease.

• The KIPS Transactions:PartD
• /
• v.12D no.3 s.99
• /
• pp.395-408
• /
• 2005

Ubiquitous computing spans a very broad range of technologies and needs very complicated user's requirements. There are many scenarios and technologies involved in ubiquitous computing. We need new software development tools and methodology to meet the requirements. A software product line is one of promising new technology for it. A software product line is a set of software intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets. Software architecture-based development is the exploration and maturation of the role of software architecture in the product line life cycle. In this thesis, we identify the foundational concepts underlying software product lines and the essential activities to develop the mobile application systems. So, we define, design, and implement the Mobile Application System Architecture(MASA) that includes the development process for applying into mobile business domain and encompass scoping and gathering requirements for the Product line based on Component Based Development(CBD).

• The KIPS Transactions:PartD
• /
• v.15D no.3
• /
• pp.361-374
• /
• 2008

In the latest intelligent computing environments, the self-adaptive software, as new software paradigm, which modifies its own behavior in response to changes in its operating environment is needed. To develop the self-adaptive software, it is necessary to analyze and design the context of software as well as the structure and the behavior of software. We need more efforts for self-adaptive software development than for traditional software development because we need more activities and technologies like context modeling and adaptation to develop the self-adaptive software. In this paper, we present the product line architecture for self-adaptive software and templates of artifacts to improve the efficiency of development through a reuse methodology. The artifacts of the architecture support the systematic reuse activities of core assets by expressing the commonality and variability of product line.

• Journal of Institute of Control, Robotics and Systems
• /
• v.10 no.5
• /
• pp.442-449
• /
• 2004

As underwater robotic vehicles (URVs) become attractive for more sophisticated underwater tasks, the demand of high performance in terms of accuracy and dexterity has been increased. An autonomous underwater robotic vehicle, ODIN (Omni-Directional Intelligent Navigator) was designed and built at the Autonomous Systems Laboratory of the University of Hawaii in 1991. Since 1991, various studies were conducted on ODIN and have contributed to the advancement in underwater robotics. Its refurbished model ODIN II was based on VxWorks in VMEbus. Recently, ODIN was born again as a PC based system, ODIN III with unique features such as new vehicle system software architecture with an objective-oriented concept, a graphical user interface, and an independent and modular structure using a Dynamic Linking Library (DLL) based on the Windows operating system. ODIN III software architecture offers an ideal environment where various studies for advanced URV technology can be conducted. This paper describes software architecture of ODIN III and presents initial experimental results of fine motion control on ODIN III.

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

• Journal of Korea Society of Industrial Information Systems
• /
• v.5 no.3
• /
• pp.87-93
• /
• 2000

Recently Software Industry has tended to enhance the productivity and quality with using the software architecture in software development and administration. The research of software component technique and software development methodology are just doing and making many applications. The software architecture is considered as the essential element for analyzing and maintaining the entire structure with organizing the software into components and describing the relations with connectors. The software modeling methodology that we propose is generating Happy Work Language describing the software structure with the modeling tool as Happy Work. We can use System Context Diagram, Component Diagram, Component Sequence Diagram, and they are composed of four Elements as Users, Systems, Components, Connectors.