• JSTS:Journal of Semiconductor Technology and Science
• /
• v.5 no.4
• /
• pp.243-248
• /
• 2005

The UAV (Unmanned Aerial Vehicle) systems like unmanned autonomous helicopters are used in various missions of flight navigation and used to collect the environmental information of the surroundings. To realize the full functionalities of the UAV, the software part becomes a challenging problem. In this paper embedded real-time software architecture for unmanned autonomous helicopter is proposed that guarantee real-time performance of hard-real time tasks and re-configurability of soft-real time and non-real time tasks. The proposed software architecture has four layers: hardware, execution, service agent and remote user interface layer according to the reactiveness level for external events. In addition, the layered separation of concurrent tasks makes different kinds of mission reconfiguration possible in the system. An Unmanned autonomous helicopter system was implemented (Kyosho RC Helicopter) in our lab to test and evaluate the performance of the proposed system.

• Healthcare Informatics Research
• /
• v.24 no.4
• /
• pp.376-380
• /
• 2018

Objectives: This research presents the design and development of a software architecture using natural language processing tools and the use of an ontology of knowledge as a knowledge base. Methods: The software extracts, manages and represents the knowledge of a text in natural language. A corpus of more than 200 medical domain documents from the general medicine and palliative care areas was validated, demonstrating relevant knowledge elements for physicians. Results: Indicators for precision, recall and F-measure were applied. An ontology was created called the knowledge elements of the medical domain to manipulate patient information, which can be read or accessed from any other software platform. Conclusions: The developed software architecture extracts the medical knowledge of the clinical histories of patients from two different corpora. The architecture was validated using the metrics of information extraction systems.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.11a
• /
• pp.1555-1557
• /
• 2010

위성 탑재 소프트웨어는 기본적인 위성의 상태 데이터 획득에서부터 지상국과의 송수신 및 위성 고유의 임무 수행의 전 과정을 담당하고 있다. 이러한 위성 탑재 소프트웨어에 있어 무엇보다 강조되는 점이 신뢰성이며, 이를 위한 많은 연구가 진행되어 왔다. 위성 탑재 소프트웨어의 개발 과정에서 여러 단계의 검증 및 테스트가 수반되게 되며, 이러한 위성 탑재 소프트웨어의 개발에는 많은 시간과 노력이 요구된다. 또한, 위성의 소프트웨어는 그 특성상 위성 발사 후 탑재 소프트웨어에 대한 수정 및 개선에 많은 어려움이 따르게 된다. 본 연구에서는 위성 탑재 소프트웨어 개발 과정에서 재사용성을 높이고 소프트웨어 및 위성 임무 변경에 보다 용이하게 대응할 수 있는 Reconfigurable Software Architecture 를 제안한다.

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2005

S/W product line is a S/W product or a set of S/W system, which has common functions. We can develop a specific S/W product, which satisfiesrequirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed S/W architecture through the S/W product line. S/W development methodology based on the S/W product line can develop a S/W more easily and fast by reusing the developed S/W core asset. An advanced country of S/W technology selects S/W product line as a core field of S/W production technology, and support technology development. In case of USA, CMU/SEI (Carnegie Mellon University / Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Ministry of National Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. In this paper, we aim to construct reference architecture of S/W product line for production of the S/W product line.

• Journal of Software Assessment and Valuation
• /
• v.17 no.2
• /
• pp.19-29
• /
• 2021

Blockchain technology fulfills the reliance requirement and is now entering a new stage of performance. However, the current blockchain technology has significant disadvantages in scalability and latency because of its architecture. Therefore, to adopt blockchain technology to real industry, we must overcome the performance issue by redesigning blockchain architecture. This paper introduces several element technologies and a novel blockchain architecture TPAC, that preserves blockchain's technical advantage but shows more stable and faster transaction processing performance and low latency.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.328-341
• /
• 2007

When the decision to initiate a software product line has been taken, the first step is the domain analysis describing the variability in the requirements, the second important step is the definition of a domain architecture that captures the overall structure of a series of closely related products. A domain architecture can be a core asset in product line by describing the commonalities and variabilities of the products contained in the software product line. The variabilities, which are identified at each phase of the core assets development, are diverse in the level of abstraction. Therefore, it is important to clearly define, systematically identify, and explicitly represent variability at the architectural level. However, it is difficult to identify and represent the variability which should be considered at the architecture level, because these may be appeared in architecture elements and in architecture configuration. In this paper, we suggest a method of developing domain architecture as a core asset in product line where commonality and variability are explicitly considered. First of all, we will describe a domain architecture metamodel that can explicitly define commonality and variability concepts by extending the Object Management Group's ($OMG^{TM}$ Reusable Asset Specification eRAS) model. Using the domain architecture metamodel, architecture elements are defined and the variations that can be identified at the architecture level are classified into two types in according th abstract level. Additionally, we describe a domain architecture where commonality and variability are explicitly considered on basis of this metamodel.

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

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.6
• /
• pp.637-647
• /
• 2010

Recent embedded systems are being more complicated due to their hierarchical software architecture including operating systems. The performance of such complicated software architecture could not be well analyzed through separate analysis of each software layer; the combined effect and the interactions among the whole software layers should be considered. In this paper, we show the design and implementation of a performance analysis framework that enables hierarchical analysis of performance of Linux-based embedded systems considering interactions among the software layers. By using the proposed framework, we can obtain useful run-time information about a hierarchical software structure which usually consists of user-defined function layer, library function layer, system call layer, and kernel events layer. Experimental results reveal that the proposed framework could accurately identify the performance bottlenecks with the corresponding software layers during executions of target applications through the accompanying sub-steps of the analysis: the actual execution paths, the execution time of each observed event in each software layer, and the control flows across the software layers.

• Electronics and Telecommunications Trends
• /
• v.39 no.1
• /
• pp.62-73
• /
• 2024

Artificial intelligence relies on data-driven analysis, and the data processing performance strongly depends on factors such as memory capacity, bandwidth, and latency. Fast and large-capacity memory can be achieved by composing numerous high-performance memory units connected via high-performance interconnects, such as Compute Express Link (CXL). CXL is designed to enable efficient communication between central processing units, memory, accelerators, storage, and other computing resources. By adopting CXL, a composable computing architecture can be implemented, enabling flexible server resource configuration using a pool of computing resources. Thus, manufacturers are actively developing hardware and software solutions to support CXL. We present a survey of the latest software for CXL memory utilization and the most recent CXL memory emulation software. The former supports efficient use of CXL memory, and the latter offers a development environment that allows developers to optimize their software for the hardware architecture before commercial release of CXL memory devices. Furthermore, we review key technologies for improving the performance of both the CXL memory pool and CXL-based composable computing architecture along with various use cases.

• Journal of Information Technology Applications and Management
• /
• v.22 no.3
• /
• pp.143-167
• /
• 2015

This paper addresses the issue how the total life cycle cost may be minimized and how the cost should be allocated to the acquirer and developer. This paper differentiates post life cycle change (PLCC) endeavors from PLCC activities, rigorously classifies PLCC endeavors according to the result of PLCC endeavors, and rigorously defines the life cycle cost of a software product. This paper reviews classical definitions of software 'maintenance' types and proposes a new typology of PLCC activities too. The proposed classification schemes are exhaustive and mutually exclusive, and provide a new paradigm to review existing literatures regarding software cost estimation, software 'maintenance,' software evolution, and software architecture from a new perspective. This paper argues that the long-term interest of the acquirer is not protected properly because warranty period is typically too short and because the main concern of warranty service is given to removing the defects detected easily. Based on the observation that defects are caused solely by errors the developer has committed for software while defects are often induced by using for hardware (so, this paper cautiously proposes not to use the term 'maintenance' at all for software), this paper argues that the cost to remove defects should not be borne by the acquirer for software.