• The Journal of Society for e-Business Studies
• /
• v.22 no.2
• /
• pp.39-60
• /
• 2017

Software product line engineering is widely recognized as an effective way for systematic software reuse, and many studies have been conducted to convert existing software development practices and processes into software product line. In order to convert existing software development into product line, a lot of investments are required such as dedicated development units, appropriate process selection and adaptation, and tool support. In particular, small businesses need business cases and specific practices for applying software product line engineering before its full-scale adoption. In this paper, we present a practical case of applying software product line engineering to the development of web system families and a process of systematically building and reusing software assets. To do this, we analyzed a number of web development projects and presented the experiences and various considerations of small software companies adopting software product line.

• The Journal of the Korea Contents Association
• /
• v.21 no.1
• /
• pp.147-161
• /
• 2021

Through photogrammetry techniques, what current researches can achieve at present is rough 3D mesh and color map of objects, rather than usable photo-realistic 3D assets. This research aims to propose a new method to create photo-realistic 3D assets that can be used in the field of visualization applications. The new method combines photogrammetry with computer graphics modeling. Through the description of the production process of three objects in the real world - "Bullet Box", "Gun" and "Metal Beverage Bottle," it introduces in details the concept, functions, operating skills and software packages used in the steps including the photograph object, white balance, reconstruction, cleanup reconstruction, retopology, UV unwrapping, projection, texture baking, De-Lighting and Create Material Maps. In order to increase the flexibility of the method, alternatives to the software packages are also recommended for each step. In this research, 3D assets are produced that are accurate in shape, correct in color, easy to render and can be physically interacted with dynamic lighting in texture. The new method can obtain more realistic visual effects at a faster speed. It does not require large-scale teams, expensive equipment and software packages, therefore it is suitable for small studios and independent artists and educational institutions.

• Journal of Software Engineering Society
• /
• v.24 no.3
• /
• pp.77-89
• /
• 2011

Software product line engineering is a software reuse paradigm that helps organizations improve software productivity and quality by developing software products from reusable core assets. For the satisfaction of common and variable requirements among products in the product line, the core assets must be configurable according to the selection of variable features. Therefore, unlike software architecture model of a single product, product line architecture model must embed and express variabilities among the products. Many researches have proposed methods of embedding and expressing variabilities in the product line architecture models, but there are few comparative studies on the proposed methods. In this paper we discuss strong points and weak points of the proposed methods and compare expressiveness of the methods, which helps select a proper method.

• Journal of Convergence for Information Technology
• /
• v.8 no.5
• /
• pp.101-106
• /
• 2018

Software are being studied to register and manage assets. And Methods for evaluating software systems have been based on subjective evaluation criteria. We propose an evaluation model for evaluating complex assets obtained from the complexity measurement of the preceding asset management system. We used scales to measure and provide logical complexity to measure the complexity of our architectural assets. And we used a method to evaluate whether it expresses attribute value of architecture asset. We have also built an evaluation model criterion for evaluating the usability of the asset data based on the ISO/IEC 25010 quality model characteristics of the SQuaRE Series. When the designers design the asset as a composite asset, the optional evaluation of the negative property that weights are assigned according to the characteristics of each asset is applied to secure the flexibility of the evaluation model.

• Journal of Industrial Convergence
• /
• v.20 no.5
• /
• pp.77-82
• /
• 2022

Evaluating methods for software asset have been made based on subjective evaluation criteria. In this study, we try to evaluate the usability of complex assets obtained from the previous measurement of the complexity of the asset management system. The evaluation used a scale provided by measuring logical complexity to measure the complexity of the asset, and evaluated the relationship with the usability of the software asset by measuring the index related to reusability. Therefore, it can be seen that HVs maintain a constant ratio according to the composition of various assets for the two types of assets and maintain the applied consistency. Therefore, it can be determined that an asset optimized in terms of usability can be applied consistently in the architectural design process while securing as much diversity as possible.

• 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 Digital Convergence
• /
• v.19 no.8
• /
• pp.219-224
• /
• 2021

The convergence of various industries has removed the boundaries of software application fields and reduced the restrictions on convergence fields. Software requirements are diversified and they want to reconfigure software requirements in a fast cycle. Since various changes in requirements have to be accepted technically, research on methodologies and standards to increase the efficiency of software productivity and methods for standardizing and producing software are needed. In this study, we studied how the reusability and complexity of the software asset reconfiguration system appeared according to the developer's characteristics and environment to utilize the assets optimized in previous studies. At this time, we measured how the change in complexity according to the usability and asset composition method that appears according to the developer's characteristics appears, but there is a limit to the collected data, so it is necessary to secure the quality of the measured value through continuous data collection. In addition, an intelligent system application plan is needed to supplement the problem of context classification in the use stage of complex assets.

• Journal of Digital Convergence
• /
• v.17 no.12
• /
• pp.229-234
• /
• 2019

The software market has diversified service needs due to the expansion of the mobile market. To this end, the company intends to produce various apps by extending to the design domain based on the structured architectural assets of the domain market. In this study, we propose an evaluation model that can evaluate the efficiency for servicing assets that reflect the domain characteristics of architecture based on cloud. Based on the characteristics of ISO/IEC 25010 quality model of SQuaRE Series, a software evaluation standard, evaluation model sub-features for evaluating the efficiency of cloud-based asset data were constructed. When the architectural assets were designed as composite assets, they were designed to provide the flexibility of the evaluation model by applying the mandatory and optional evaluation elements of the sub-features that weighted the evaluation items according to the characteristics of the design domain.

• Proceeding of Spring/Autumn Annual Conference of KHA
• /
• 2011.04a
• /
• pp.197-202
• /
• 2011

The purpose of this study was to investigate the current situation of physical and intangible assets, and to analyze the use of planning in a new cultural space creation project areas. For this study, literature survey, filed survey and participant observation methods were used for data collection. The results were as follows. 1) The project's characteristics had a variety of space utilization's scope. It was to emphasize the organizations and participants in the human side. 2) There are the pumping stations, mokgammak, mills, barbershops, marketplaces etc in physical assets, and it was worth the historic or agricultural facility. 3) The using plans of three kinds in hardware facilities, software programs, human ware(human abilities)are linked to each other organically. 4) The problems in the project's process include the administrative and institutional factors rather than planning matters.

• Journal of Convergence for Information Technology
• /
• v.7 no.5
• /
• pp.111-116
• /
• 2017

In this paper, we propose a method to measure the complexity of assets when a software component is constructed as a basic asset, a standardized design model is acquired, and a reusable extended asset is designed based on the standardized design model. However, each asset of our proposed asset management system consists of composite assets that combine assets of two domains. So this method can not make accurate measurements. Therefore, the complexity of the overall asset can be measured by reflecting the property value of the basic asset stored under the architecture. In conclusion, it is possible to measure the composite-complexity of a composed asset that is inversely proportional to cohesion and proportional to the cumulative sum of the associated values of each asset in the asset-related design.