• Journal of Digital Convergence
• /
• v.11 no.7
• /
• pp.165-171
• /
• 2013

Coding patterns that appeared frequently in the source code is a typical piece of code. The functionality that difficult to modularize, such as logging or synchronization processing, and the useful sentences in programming is extracted in software as codding pattern. Large-scale software could not be analyzed fully because the number of coding pattern that can be manually investigated is limited. In this paper, the characteristics of coding patterns perform the evaluation. The goal is to extract for codding-pattern to analyzed by developer. We was selected 6 indicators and performed analysis of 4 open-source. Matrix relations between the values and characteristics of the actual pattern analysis, pattern instances, the width of the distribution of instances, the pattern repeating structure of the elements included in the rates should be analyzed for patterns and indicators that help in choosing was confirmed.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.30 no.6
• /
• pp.1225-1236
• /
• 2020

Fuzzing is an automated software testing methodology that dynamically tests the security of software by inputting randomly generated input values outside of the expected range. KISA is releasing open source for standard cryptographic algorithms, and many crypto module developers are developing crypto modules using this source code. If there is a vulnerability in the open source code, the cryptographic library referring to it has a potential vulnerability, which may lead to a security accident that causes enormous losses in the future. Therefore, in this study, an appropriate security policy was established to verify the safety of block cipher source codes such as SEED, HIGHT, and ARIA, and the safety was verified using differential fuzzing. Finally, a total of 45 vulnerabilities were found in the memory bug items and error handling items, and a vulnerability improvement plan to solve them is proposed.

• KIPS Transactions on Software and Data Engineering
• /
• v.8 no.12
• /
• pp.465-472
• /
• 2019

Today, in many area the rise of software necessity there has been increasing the issue of the impotance of Good Software. Our reality in software industrial world has been happening to frequently change requirements at any stage of software life cycle. Furthermore this frequent changing will be increasing the design complexity, which will result in being the lower quality of software against our purpose the original design goals. To solve this problem, we suggest how to improve software design through refactoring based on reverse engineering. This is our way of diverse approaches to visually identify bad smell patterns in source code. We expect to improve software quality through refactoring on even frequently changing requirements.

• Journal of KIISE:Software and Applications
• /
• v.37 no.4
• /
• pp.252-263
• /
• 2010

The needs of low-power embedded software are being increased. Along with the needs, the studies to predict the power consumption of embedded software are also being increased. Although existing studies for power analysis have been performed in source code-based, these code-based analysis have some shortages of long analysis time and much feedback efforts. Recently some studies of power analysis based on software models are prompted. This paper describes on the model-based approach using UML diagrams in embedded software development process. Specially we focus on the extension of OMG's MARTE Profile to support model-based analysis. The MARTE extension gives the possibility of power analysis using just UML diagrams without any other analysis model in embedded software development.

• Proceedings of the KSR Conference
• /
• 2001.05a
• /
• pp.341-346
• /
• 2001

This paper presents a concept design of detail design software for high speed catenary system. In this software, M.D.(mounting diagram) can be peformed and parts D/B can be also managed. french one, used in Kyung-bu high-speed line, is not good at user's interface, and the source code is not opened. So, it is impossible to use it in the different environment and catenary system. Through this program, automation of detail design and user's convenience can be derived.

• Journal of Software Assessment and Valuation
• /
• v.15 no.1
• /
• pp.55-62
• /
• 2019

The needs for small size and low power consumption of information devices is being implemented with SOC technology that implements the program on a single chip in Internet of Thing. Copyright disputes due to piracy are increasing in semiconductor chips as well, arising from disputes in the chip implementation of the design house and chip implementation by the illegal use of the source code. However, since the final chip implementation is made in the design house, it is difficult to protect the copyright. In this paper, we deal with the analysis method for extracting similarity and the criteria for setting similarity judgment in the dispute of source code written in HDL language. Especially, the chip which is manufactured based on the same specification will be divided into the same configuration and the code type.

• 한국전산유체공학회:학술대회논문집
• /
• 2010.05a
• /
• pp.431-436
• /
• 2010

Recently, several open source codes for computational fluid dynamics (CFD) have been emerged and are spreading fast. Our group has chosen OpenFOAM as a platform to develop our own in-house code. In this paper, we would like to share the information on the codes and what we have experienced so far. We introduce several features of OpenFOAM, which include the performance compared with commercial packages, estimation for current user population and our own prospect for future improvement in performance and growth in user population. In addition, we briefly introduce our experience gained in embedding the level set method into the OpenFOAM.

• Journal of computational fluids engineering
• /
• v.15 no.3
• /
• pp.46-53
• /
• 2010

Recently, several open source codes for computational fluid dynamics (CFD) have been introduced and are spreading fast. Our group has chosen the OpenFOAM as a platform to develop our own in-house code. In this brief review, we would like to share the information on the codes and what we have experienced so far. We introduce several features of OpenFOAM, which include the performance compared with commercial packages, estimation for current user population, and our own prospect for future improvement in performance and growth in user population. In addition, we briefly introduce our experience gained in embedding the level set method into the OpenFOAM.

• Journal of KIISE
• /
• v.42 no.7
• /
• pp.860-867
• /
• 2015

In the defense field, weapon systems are increasing in importance, as well as the weight of the weapon system embedded software development as an advanced technology. As the development of a network-centric warfare has become important to secure the reliability and quality of embedded software in modern weapons systems in battlefield situations. Also, embedded software problems are transferred to the production stage in the development phase and the problem gives rise to an enormous loss at the national level. Furthermore, development companies have not systematically constructed a software reliability test. This study suggests that approaches about a qualityverification- system establishment of embedded software, based on a variety of source code reliability test verification case analysis.

• Journal of the Korea Society of Computer and Information
• /
• v.21 no.5
• /
• pp.119-126
• /
• 2016

Software maintenance becomes extremely difficult, especially caused by multiple versions in project-based or customer-oriented software development methodology. For reducing the maintenance cost, reengineering to software product line can be a solution to the software which either is a family of products nevertheless little different functionalities or are customized for each different customer's requirement. At an initial stage of the reengineering, the most important activity in software product line is feature extraction with respect to commonality and variability from the existing system due to verifying functional coverage. Several researchers have studied to extract features. They considered only a single version in a single product. However, this is an obstacle to classify the commonality and variability of features. Therefore, we propose a method for systematically extracting features from source code and its change history considering several versions of the existing system. It enables us to represent functionalities reflecting developer's intention, and to clarify the rationale of variation.