• Journal of the Korea Society of Computer and Information
• /
• v.29 no.1
• /
• pp.139-149
• /
• 2024

In this paper, we propose the standard architecture for the IFF interface SW in naval combat management system(CMS). The proposed standard interface architecture is a method designed to reduce modification efforts and man-month of reliability test for the existing the IFF interface SW of 11 types. We identified highly dependent CMS and GFE information, leading to the redefinition of standard requirements and functions, and proceeded with the initial design applying the Naval Shield Component Platform(NSCP). Subsequently, using the Feature Model, we derived additional common and variable elements for the interface of multiple CMS and GFE. Considering the S.O.L.I.D principles, we designed the final architecture. The proposed IFF Interface SW, based on the standard architecture, is expected to enhance management efficiency through a common architecture, increase code reusability and scalability, and reduce development costs by shortening reliability testing times.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.51-60
• /
• 2006

Product Line Engineering(PLE) is an effective software development technique which produces applications using core assets. Because of reusing the core assets, PLE can save cost for developing products in a domain but increase reusability. There are about ten PLE methodologies available, but there are not yet common agreements on PLE process and artifacts. This makes developers harder to choose a methodology and to apply it in practice. A comprehensive technical evaluation and comparison on existing PLE methodologies would be essential for practitioners. In this paper, we present a technical assessment of representative PLE methodologies; FAST, SEI SPL, PuLSE, Bosch's PL proceis, FOPLE, ESAPS, KobrA/PoLITe, Alexandria, COPA, QADA. They are compared in the criteria of process, artifacts, instructions, and special features. And we identify common or variable elements between methodologies and confirm elements to be improved in each PLE methodology. The assessment result would be well utilized in defining a practical methodology for PLE projects and in choosing an appropriate methodology among available ones.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.11
• /
• pp.147-155
• /
• 2020

System support software is one of the software that makes up ship combat management system and has the characteristics of being mounted in the combat management systems of all ships but with little functional change. However, despite these characteristics, software modifications due to equipment, etc. are inevitable in the application of new ships. Modification of software causes software reliability testing which is a key factor in increasing development costs. In this paper, the structure of the existing system support software was analyzed to identify and supplement the code change factors, and the system support standardization architecture was designed. The feature model elicited common and variable elements of system support software, and applied white-box reuse to improve software design. In addition, the results of comparing existing system support software with the new architecture in terms of development elements and time to perform reliability test were presented to verify the effectiveness of the new one.

• KIPS Transactions on Software and Data Engineering
• /
• v.5 no.3
• /
• pp.125-138
• /
• 2016

The service identification in service-oriented developments has been conducted by based on workflow, goals, scenarios, usecases, components, features, and patterns. However, the identification of service by semantic approach at the business value view was not detailed yet. In order to enhance accuracy of identifying business service, this paper proposes a method for identifying business service by analyzing syntax and semantics in XL-BPMN model. The business processes based on business scenario are identified, and they are designed in a XL-BPMN business process model. In this business process model, an unit business service is identified through binding closely related activities by the integrated analysis result of syntax patterns and properties-based semantic similarities between activities. The method through XL-BPMN model at upper business levels can identify the reusable unit business service with high accuracy and modularity. It also can accelerate more service-oriented developments by reusing identified services.

• Journal of Software Engineering Society
• /
• v.24 no.2
• /
• pp.67-75
• /
• 2011

In order to improve working speed, add more functions and provide better user interface of ASADAL, the AWT based Java application to support FORM Software Product Line Development Methodology; we had to reengineer this application to be Eclipse based plug-in application. In order to improve working speed, add more functions and provide better user interface of ASADAL, the AWT based Java application to support FORM Software Product Line Development Methodology; we had to reengineer this application to be Eclipse based plug-in application. And then, this paper introduces the plug-in developed by applying guidelines presented in the reengineering cases of ASADAL's feature model editor and behavior model editor.

• Journal of the Korea Society of Computer and Information
• /
• v.28 no.1
• /
• pp.71-78
• /
• 2023

In this paper, we analyze the structure of TV video software, one of the warship combat management system software, and propose a standard architecture that minimizes software modification due to the discontinuation replacement of warship hardware. The class structure was newly designed to minimize the class modified when replacing the warship hardware by separating the variable elements and common elements of TV video software through FORM(Feature-Oriented Reuse Method), the common part that communicates with the warship combat management system and displays the TV screen and the variable part that communicates between the operator and the TV camera. In addition, the Strategy design pattern is applied to efficiently add and modify classes that directly use hardware-dependent APIs when replacing hardware discontinuation, and to make both discontinued and replacements available software. Finally, the reliability testing time and functional testing time of the existing TV video software and the proposed software were measured and compared, and finally, it was confirmed that the hardware discontinuation replacement cost was reduced.

• Journal of the Korea Society of Computer and Information
• /
• v.29 no.2
• /
• pp.119-126
• /
• 2024

The IISS(Integrated Interface Storage System) software performs the function of transmitting tactical domain messages of Combat Management System for interface analysis of Naval Combat System. The source code is relatively large because the IISS software handles most messages. The modifications of source code of the IISS software occur frequently due to changes in interconnected equipment and messages. Therefore, additional effort and cost are required during the development process. In this paper, we studied standardization of the IISS software to improve reusability. Through the feature model, the components of the IISS software were divided by function and modification elements were separated. And the structure of the IISS software was improved by applying design patterns. As a result, it was possible to minimize modifications of the IISS software by changes in interconnected equipment and messages and a reduction in development costs could be expected.

• Journal of the Korea Society of Computer and Information
• /
• v.29 no.8
• /
• pp.67-75
• /
• 2024

Frequently changeable functional requirements in System Management CSCI Software make it difficult to reuse an overall application, but only the partial class codes repeatedly as a new version of Naval Combat Management System is developed. This structural environment leads to increasing development time and expenses. This is why modularization for System Management CSCI Software is proposed as a solution, leveraging the advantages of proper standardization and functional expandability offered by Standard Interface Architecture. This paper outlines the comparisons of modified class ratios as well as software reliability test runtime results between before and after implementing the modularization for System Management CSCI Software. The findings demonstrate there is sufficient improvement in areas, such as higher maintenance and reusability, supporting the application of modularization for System Management CSCI Software with the implementation of Standard Interface Architecture.

• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.565-572
• /
• 2006

Product Line Engineering (PLE) is an effective reuse methodology where common features among members are captured into core assets and applications are developed by reusing the core assets, reducing development cost while increasing productivity. To maximize benefits in developing systems, business case analysis for PLE is essential. If the scope for core assets is excessively broad, it will result in high cost of asset development while lowering reusability. On the other hand, if the scope is too narrow, it will result in a limited applicability which only support a small number of members in the domain. In this paper, we propose a process for business case analysis for PLE and for deciding economical analysis of core asset scope. Then, we define guidelines for each activity of the process. Since variability often occurs in PLE, we significantly treat the variability of features among members in detailed level. By applying our framework for business case analysis, one can develop core assets of which scope provide the most economical value with applying PLE.

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.5
• /
• pp.53-67
• /
• 2008

At present, for reuse of similar domains between feature model and class model. researches of transformation at the model level and of transformation using ontology between two models are being made. but consistent transformation through metamodel is not made. And the factors of modeling transformation targets are not sufficient, and especially, automatic transformation algorithm and supporting tools are not provided so reuse of domains between models is not activated. This paper proposes a method of transformation from feature model to class model using ontology on the metamodel. For this, it re-establishes the metamodel of feature model, class model, and ontology, and it defines the properties of modelling factors for each metamodel. Based on the properties, it defines the profiles of transformation rules between feature mndel and ontology, and between ontology and class model, using set theory and propositional calculus. For automation of the transformation, it creates transformation algorithm and supporting tools. Using the proposed transformation rules and tools, real application is made through Electronic Approval System. Through this, it is possible to transform from the existing constructed feature model to the class model and to use it again for a different development method. Especially, it is Possible to remove ambiguity of semantic transformation using ontology, and automation of transformation maintains consistence between models.