• Title/Summary/Keyword: Software reuse

Search Result 395, Processing Time 0.024 seconds

A Study on the Standard Architecture of Weapon Control Software on Naval Combat System

  • Lee, Jae-Geun
    • 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.

Product-Line Architecture Development for Self-Adaptive Software (적응형 소프트웨어를 위한 프로덕트 라인 아키텍처 개발)

  • Ye, Eun-Suk;Yeom, Keun-Hyuk;Moon, Mi-Kyeong
    • 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.

A Study on the Improving Performance of Massively Small File Using the Reuse JVM in MapReduce (MapReduce에서 Reuse JVM을 이용한 대규모 스몰파일 처리성능 향상 방법에 관한 연구)

  • Choi, Chul Woong;Kim, Jeong In;Kim, Pan Koo
    • Journal of Korea Multimedia Society
    • /
    • v.18 no.9
    • /
    • pp.1098-1104
    • /
    • 2015
  • With the widespread use of smartphones and IoT (Internet of Things), data are being generated on a large scale, and there is increased for the analysis of such data. Hence, distributed processing systems have gained much attention. Hadoop, which is a distributed processing system, saves the metadata of stored files in name nodes; in this case, the main problems are as follows: the memory becomes insufficient; load occurs because of massive small files; scheduling and file processing time increases because of the increased number of small files. In this paper, we propose a solution to address the increase in processing time because of massive small files, and thus improve the processing performance, using the Reuse JVM method provided by Hadoop. Through environment setting, the Reuse JVM method modifies the JVM produced conventionally for every task, so that multiple tasks are reused sequentially in one JVM. As a final outcome, the Reuse JVM method showed the best processing performance when used together with CombineFileInputFormat.

Defense software test procedure improvement measure reflecting the TMMi (TMMi를 반영한 국방 소프트웨어 테스트 절차 발전방안)

  • Park, Yeon-Dong
    • Journal of the Korea Academia-Industrial cooperation Society
    • /
    • v.22 no.1
    • /
    • pp.87-93
    • /
    • 2021
  • As the portion of modern weapons systems equipped with electronic components increases, the presence of embedded software has also increased, subsequently drawing interest in quality management and development methods. Unlike mechanical systems, software is logically intangible, hard to troubleshoot, and hard to reuse, making it hard to utilize limited resources when exposed to failures. The United States had successful results in establishing the Capability Maturity Model (CMM) by studying and applying separate processes for development and quality management of defense software. South Korea has also established, and utilizes, a standard of development and quality management for defense software based on international standards. However, some say those standards still remain at a basic level, and should be modified along with the progress in software. If the standard stays at a basic level, compared to software progression, the cost to reuse and restore resources will increase exponentially. This paper discusses improvement in the test processes for defense software through the Test Maturity Model-integration (TMMi)-derived from the CMM-and presents a blueprint for defense software quality management.

STRUCTURAL INCONSISTENCY OF INTERNAL REPRESENTATIONS OF COGNITIVE PROCESSES OF SOFTWARE REUSE (소프트웨어 재사용시의 인지과정상에 나타난 내적표상의 구조적 불일관성)

  • JinwooKim
    • Korean Journal of Cognitive Science
    • /
    • v.4 no.2
    • /
    • pp.201-262
    • /
    • 1994
  • This paper portrays software reuse as analogical mapping and rule development.In order to explore the impacts of inconsistent representationS on the cognitive process of software resuse,it manipulates the intermal representations of source and target problems and their program solutions.The experimental design for this study has two factors:1)the degree of structural consistency between the source problem and the target problem,and2) the degree of structural consistency between the source problem and the source solution.A full-scale protocol analysis reveals that these two factors influence the cognitive process of mapping between source and target,the process of developing rules,and the interrelation between analogical mapping and rule development.The paper concludes by discussing the implications of these results for software reuse.

The Information Retrieval System for Software Reuse (소프트웨어 재사용을 위한 정보검색시스템 구축)

  • Kim, Young-Geil
    • The Journal of Korea Institute of Information, Electronics, and Communication Technology
    • /
    • v.9 no.1
    • /
    • pp.1-8
    • /
    • 2016
  • In this paper, several problems functioning as the obstacles against software reuse were summarized. Among them, the issues dealt with in this paper include the effective method for constructing the library, the proper structure of the library, and the efficient retrieval technique. The knowledge-based approach and the information retrieval approach were integrated to construct and manage the library. The former is on the object- oriented model. Basically the object-oriented library is based on the classes and organized by inheritance. Because inheritance hierarchy is based on syntactical information, it dose not present the relationship of functionality. Using the information retrieval approach, the index file which characterizes the component and similarity among the components can be analyzed. Especially, we focused on the reusable library for the object-oriented programming environments.

A Study on the System Management CSCI Software Modularization in Naval Combat Management System

  • Hyeon-Tae Ha
    • 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.

Modeling FORM Architectures Based on UML 2.0 Profiling (UML 2.0 프로파일링을 이용한 FORM 아키텍처 모델링)

  • Yang, Kyung-Mo;Jo, Yoon-Ho;Kang, Kyo-Chul
    • Journal of KIISE:Software and Applications
    • /
    • v.36 no.6
    • /
    • pp.431-442
    • /
    • 2009
  • The Software Product Line (SPL) engineering is one of the most promising software development paradigms. With Feature-Oriented Reuse Method (FORM), reusable and flexible components can be built to aid the delivery of various software products such as mobile phone and digital TV applications based on commonalities and variabilities identified during Feature modeling. Model Driven Architecture (MDA) is also an emerging technology which supports developing software products to work on different platforms with platform independent models (PIM). Combining advantages of these two approaches is helpful to build a group of software products which share common Features while working on various platforms. As first step to combine FORM with MDA, we extend UML2.0 with profiles by which FORM architectures and parameterized Statecharts can be modeled. Secondly, we provide rules to examine whether Features are allocated at positions of elements of Statecharts consistently between a Feature model and a parameterized Statechart. Some rules are designed to check the consistency between FORM architectures and parameterized Statecharts. A case study on an elevator control system is provided to demonstrate the feasibility of our modeling approach and consistency checking rules.

- A Case Study on OOP Component Build-up for Reliability of MRP System - (MRP 시스템의 신뢰성을 위한 객체재향 컴포넌트 개발 사례)

  • Seo Jang Hoon
    • Journal of the Korea Safety Management & Science
    • /
    • v.6 no.3
    • /
    • pp.211-235
    • /
    • 2004
  • Component based design is perceived as a key technology for developing advanced real-time systems in a both cost- and time effective manner. Already today, component based design is seen to increase software productivity, by reducing the amount of effort needed to update and maintain systems, by packaging solutions for re-use, and easing distribution. Nowdays, a thousand and one companies in If(Information Technology) industry such as Sl(System Integration) and software development companies, regardless of scale of their projects, has spent their time and endeavor on developing reusable business logic. The component software is the outcome of software developers effort on overcoming this problem; the component software is the way propositioned for quick and easy implementation of software. In addition, there has been lots of investment on researching and developing the software development methodology and leading If companies has released new standard technologies to help with component development. For instance, COM(Component Object Model) and DCOM(Distribute COM) technology of Microsoft and EJB(Enterprise Java Beans) technology of Sun Microsystems has turned up. Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, It suggest that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. about implements and accomplishes the modeling for the Product Control component development by applying CCD(Contract-Collaboration Diagram), one of component development methodology, to MRP(Material Requirement Planning) System