• Journal of Information Technology Services
• /
• v.8 no.3
• /
• pp.145-157
• /
• 2009

As the software development cycles is getting shorter, the software reusability is emphasized accordingly. Specifically, the design reusability is being recognized as one of the most important factor to increase the software quality and productivity and make the maintenance cost down. Two essential abilities are needed to improve the design reusability. One is the identification of the reusable objects, and the other is the organization of the relationships among the objects. However, the existing methods using such as a grammatical analysis, a scenario matching and a unit of design problems(design pattern) have not been proposed proper principles to identify the reusable objects on the basis of the abstraction which is the core of the object-oriented concept. In this paper, we will offer the Two-Pass abstraction principle based in the abstraction concept.

• Journal of Convergence for Information Technology
• /
• v.8 no.2
• /
• pp.91-103
• /
• 2018

Refactoring is an engineering technique for securing the quality of existing legacy code, improving the internal structure without changing the functionality of the software. Along with the reuse of open source software, reuse of source code through programming language conversion is increasingly required due to technical or market requirements. In this situation, the refactoring technique including language conversion as well as energy efficiency is considered to be an important means for improving the productivity and the quality of embedded software development. This paper proposes a code refactoring technique that converts the grammar and structure of a programming language into those of a different language through comparison and mapping, in addition to the existing energy efficient refactoring technique. The use of the proposed refactoring technique can expect to improve the competitiveness of the product through rapid software development and quality improvement by coping with the environment change of the software development language and enhancing the reuse of the existing code.

• International journal of advanced smart convergence
• /
• v.6 no.4
• /
• pp.50-55
• /
• 2017

Workers' demands for new applications, especially mobile applications, are increasing. Many industry analysts, researchers and corporate executives say the demand for mobile applications is becoming increasingly difficult to follow in the IT department. Gartner predicts that by 2021, the demand for mobile application development within the enterprise will increase about five times faster than IT can deliver applications. The purpose of this paper is to provide an environment where non-developers who are in charge of business development can develop apps and webs for their work. The basic concept of a new innovative App development tool, Smart Maker Authoring Tool is to develop Apps on the level using easy-to-learn Word or Excel in a computer. The main feature is that the app is developed by a non-developer worker. The coding technology is perfectly optimized to the structure and operation mechanism of the IT Infra such as hardware devices and operating system, which are the targets for implementing a desired function. Rather, it shows excellent software productivity. The most important feature of future business development is that it is developed by a non-developer worker. In this paper, we propose a no-code and low-code platform for non - developers to develop their business. In the future, we will link the IoT based Arduino system and artificial intelligent interpretation system.

• The KIPS Transactions:PartD
• /
• v.13D no.2 s.105
• /
• pp.271-278
• /
• 2006

This paper presents industry feedback and a case of improvement trial on enabling reuse driven software development which is one of several activities to improve software quality and productivity in a company which develops software that are embedded into consumer electronic products. Several case studies will be introduced that are related to software reuse strategies and practices to show how to establish environment for reuse basis in a company, how to apply it to development team and project and how to improve that through trials and errors. To enable reuse-oriented software development in a huge company, integrated and focused approach is needed among technical, management and environmental point of view. We tried to solve that problem in technical field with reuse method, in management filed with reuse metric and in environment field with reuse repository. The characteristics of our software development environment could be summarized as below. The first, embedded software which would not independent to hardware devices and the second, it is very huge company which develops extremely various products by many different organization with different domain characteristics and the third, development lead time is extremely short and many variation models are stems from basic models. We expect that our study would give contribution to industry struggling to solve similar problem for presenting our experience and could be a reference model for enabling software reuse in a real world practically.

• Journal of Navigation and Port Research
• /
• v.41 no.3
• /
• pp.137-148
• /
• 2017

Port service level is a metric of competitiveness among ports for the operating/managing bodies such as the terminal operation company (TOC), Port Authority, or the government, and is used as an important indicator for shipping companies and freight haulers when selecting a port. Considering the importance of metrics, we developed software to objectively define and manage six important service indicators exclusive to container and bulk terminals including: berth occupancy rate, ship's waiting ratio, berth throughput, number of berths, average number of vessels waiting, and average waiting time. We computed the six service indicators utilizing berth 1 through berth 5 in the container terminals and berth 1 through berth 4 in the bulk terminals. The software model allows easy computation of expected ship's waiting ratio over berth occupancy rate, berth throughput, counts of berth, average number of vessels waiting and average waiting time. Further, the software allows prediction of yearly throughput by utilizing a ship's waiting ratio and other productivity indicators and making calculations based on arrival patterns of ship traffic. As a result, a TOC is able to make strategic decisions on the trade-offs in the optimal operating level of the facility with better predictors of the service factors (ship's waiting ratio) and productivity factors (yearly throughput). Successful implementation of the software would attract more shipping companies and shippers and maximize TOC profits.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.18 no.11
• /
• pp.2593-2599
• /
• 2014

The way of mobile apps development using open source software have been becoming increasingly popular recently. In opensource mobile User Interface components case, there is tends to much more be used than mobile functional components. Because it is more easier that the reusability for implementation of User Interface. The problem is to apply as an open source mobile components selected for this reason all of the existing two studies. It is an open source software selection process and selection procedures shelf components. We revise to conform to existing mobile components selected for the study on open source software selection process in this paper. Can help increase the productivity of the mobile app development by the open source components to meet the functional requirements when developing mobile apps that can be easily retrieved and presented the selection process of this study is effective.

• Proceedings of the Korea Database Society Conference
• /
• 2010.06a
• /
• pp.13-19
• /
• 2010

Information competitiveness accounts for substantial parts of business competitiveness necessary for business management in the knowledge-information society in the 21st century. To improve quality. productivity and competitiveness through information in the fields of SMEs particularly having difficulties under rapidly changing business environment. the government has operated "SME Information Support Project" for the past 8 years. The methodology for developing the standard for this project known as EISDM (Enterprise Information System Development Methodology) provides communication between IT businesses and SMEs participating in this project. and standardized output document formats and how to make out such documents. Infortunately. the number of personnel partaking in the development project for SMEs is no more than 2~4 per site on average. Further. they are required to complete demand analyses. development. testing and operation in about 6 months. which is a very short period. Moreover, there is too much demand for documentation, which is likely to end up being formal work process just for supervision and inspection. That is, the documentation could be for noting but documents. which will prove useless outputs after the project finishes. Therefore, this study proposes an improvement approach as an information system development methodology taking into account SMEs' characteristics and environment so as to relieve developers from such excessive burden of documentation, to save time and resources through efficient management of software development as the original purpose of the methodology, and to produce required quality software.

• The KIPS Transactions:PartD
• /
• v.9D no.3
• /
• pp.435-446
• /
• 2002

Recently, many IT organizations develop software system with reusable component. Effective reusing of components increases software development productivity and quality. And, development of high quality component documents decrease maintenance problems, which are issues in component-based software development. In this paper, we propose a quality evaluation model of component development documents by empirical research. It consists of component quality reference model (CQRM) and quality evaluation model (CQEM). CQRM contains quality guidelines for component developers. CQEM contains evaluation guidelines for component consumers and distributors. We performed case study to verify this paper. Also, we presented quality improvement methods and improvement effects of component development documents. The quality evaluation model of component development documents proposed in this paper leads component development documents with high quality, and provides a rational quality evaluation model.

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.

• Journal of KIISE:Software and Applications
• /
• v.29 no.10
• /
• pp.703-725
• /
• 2002

It is well recognized that component-based development (CBD) is an effective approach to manage the complexity of modem software development. To achieve the benefits of low-cost development and higher productivity, effective techniques to maximize component reusability should be developed. Component is a set of related concepts and objects, and provides a particular coarse-grained business service. Often, these components include various message flows among the objects in the component, called 'business workflow`. Blackbox components that include but hide business workflow provide higher reusability and productivity. A key difficulty of using blackbox components with business workflow is to let the workflow be customized by each enterprise. In this paper, we provide techniques to model the variability of family members and to customize the business workflow of components. Our approach is to provide formal specification on the component variability, and to define techniques to customize them by means of the formalism.