• Proceedings of the Korean Society of Computer Information Conference
• /
• 2023.01a
• /
• pp.399-402
• /
• 2023

본 논문에서는 빛에 영향에 따른 유화의 변화를 보여주기 위해 2D 이미지 재조명과 색채변화를 반영한 회화적 렌더링 방법을 제안한다. 이 방법은 2D 이미지를 재조명하고 해당 음영 값을 가중치로 하여 색채변화를 반영해 렌더링한다. 이때 재조명의 경우 2D 이미지를 3D 이미지로 근사 추정하여 노말값을 결정하고 해당 값과 조명 위치값 사이의 각을 음영 값으로 추출하여 반영한다. 조명 위치는 사용자가 지정 가능하며 빛에 영향에 따른 색채변화 결과는 기존에 연구된 결과를 참조한다. 본 논문에서는 기존의 로컬 이미지에 근사한 자동 회화적 렌더링이 보여주는 단순하고 평면적인 결과에 비해, 재조명을 통해 빛바랜 색과 양감을 반영함으로써 현실에 존재하는 작품처럼 생동적이고 입체적인 렌더링 결과를 제공하여 문화예술작품으로의 표현 및 색채변화 예측-복원에 기여하고자한다.

• Journal of Satellite, Information and Communications
• /
• v.7 no.2
• /
• pp.80-86
• /
• 2012

The software-based satellite simulator has been developed from the start of the project to resolve the restriction and limitation of using hardware-based software development platform. It enables the development of flight software to be performed continuously since initial phase. The satellite simulator emulates the on-board computer, I/O modules, electronics and payloads, and it can be easily adapted and changed on hardware configuration change. It supports the debugging and test facilities for software engineers to develop flight software. Also the flight software can be loaded without any modification and can be executed as faster than real-time. This paper presents the architecture and design of software-based GEO satellite simulator which has hot-standby redundancy mechanism, and flight software development and test under this environment.

• International journal of advanced smart convergence
• /
• v.8 no.3
• /
• pp.161-166
• /
• 2019

Viewed in the rate of change in the web environment, it is very difficult to remain the initial planning at the time until the time of launch, and there is a need for a method to accommodate changes and satisfy market demands during the development process. Unlike the traditional waterfall approach of maintaining initial planning, scrum is one of the agile methodologies that enables flexibility to respond to changes in the market and customers' needs and drive customer satisfaction and business success. However, to apply the scrum to a project in actual, the practice method itself is relatively simple but not easy to apply. The reason is that the members of the organization need to understand and participate in scrum's philosophy and principles and the continuous observation and change management should be carried out. Therefore, in this paper, we presented the feature dashboard and customized scrum methodology to enable continuous observation and change management using visibility, and we shared the case that periodically reflected inspection and adaptation with the explanation of the main points. Also, based on the experience with participants, the strengths and weakness of the feature dashboard and the customized scrum methodology are summarized.

• Journal of Distribution Science
• /
• v.11 no.2
• /
• pp.45-55
• /
• 2013

Purpose - The development and implementation of OSS (Open Source Software) led to a dramatic change in corporate IT infrastructure, from system server to smart phone, because the performance, reliability, and security functions of OSS are comparable to those of commercial software. Today, OSS has become an indispensable tool to cope with the competitive business environment and the constantly-evolving IT environment. However, the use of OSS is insufficient in small and medium-sized companies and software houses. This study examines the need for OSS Intermediaries in the Software Distribution Channel. It is expected that the role of the OSS Intermediary will be reduced with the improvement of the distribution process. The purpose of this research is to prove that OSS Intermediaries increase the efficiency of the software distribution market. Research design, Data, and Methodology - This study presents the analysis of data gathered online to determine the extent of the impact of the intermediaries on the OSS market. Data was collected using an online survey, conducted by building a personal search robot (web crawler). The survey period lasted 9 days during which a total of 233,021 data points were gathered from sourceforge.net and Apple's App store, the two most popular software intermediaries in the world. The data collected was analyzed using Google's Motion Chart. Results - The study found that, beginning 2006, the production of OSS in the Sourceforge.net increased rapidly across the board, but in the second half of 2009, it dropped sharply. There are many events that can explain this causality; however, we found an appropriate event to explain the effect. It was seen that during the same period of time, the monthly production of OSS in the App store was increasing quickly. The App store showed a contrasting trend to software production. Our follow-up analysis suggests that appropriate intermediaries like App store can enlarge the OSS market. The increase was caused by the appearance of B2C software intermediaries like App store. The results imply that OSS intermediaries can accelerate OSS software distribution, while development of a better online market is critical for corporate users. Conclusion - In this study, we analyzed 233,021 data points on the online software marketplace at Sourceforge.net. It indicates that OSS Intermediaries are needed in the software distribution market for its vitality. It is also critical that OSS intermediaries should satisfy certain qualifications to play a key role as market makers. This study has several interesting implications. One implication of this research is that the OSS intermediary should make an effort to create a complementary relationship between OSS and Proprietary Software. The second implication is that the OSS intermediary must possess a business model that shares the benefits with all the participants (developer, intermediary, and users).The third implication is that the intermediary provides an OSS of high quality like proprietary software with a high level of complexity. Thus, it is worthwhile to examine this study, which proves that the open source software intermediaries are essential in the software distribution channel.

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

• The KIPS Transactions:PartD
• /
• v.13D no.5 s.108
• /
• pp.709-716
• /
• 2006

As the software complexity increases, the development success rate decreases and failure rate increases exponentially. The failure rate related to the software size can be described by a growth function. Based on this phenomenon, this paper estimates the development success and completion rate using the Gompertz growth function. At first, we transformed a software size of numerically suggested $10^n$ into a logarithm and kept the data interval constantly. We tried to derive a functional relationship between the development success rate and the completion rate according to the change of logarithmic software size. However, we could not find a function which can represent this relationship. Therefore, we introduced the failure rate and the cancel rate which are inverse to the development success rate and completion rate, respectively. Then, we indicated the relation between development failure rate and cancel rate based on the change of software size, as a type of growth function. Finally, as we made the Gompertz growth function with the function which describes the cancel rate and the failure rate properly. We could express the actual data suitably. When you apply the growth function model that I suggested, you will be able to get the success rate and completion rate of particular site of software very accurately.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.22 no.4
• /
• pp.331-337
• /
• 2021

Owing to the limited development period and budget of the weapon system, many problems have arisen in the operation stage after mass production. Therefore, engineering changes are also increasing. On the other hand, an analysis of the cause of problems and improvement of the system equipment performed in engineering changes cannot be managed synthetically. Hence, important actual data can only be used once. In particular, unlike hardware where the shape of the equipment is changed or the part number is changed, the contents of software engineering changes are only partially included in the proposal. Moreover, only the extent to which the version of the source package and the executable file has been changed can be identified. Therefore, this paper proposes a method to build and utilize a database for cause analysis and improvement plan data of weapon-system software engineering changes and software technical support. The above utilization measure can contribute to the quality assurance of weapon-system software developed in the future by preemptively applying real-world data when developing similar weapon systems.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2009.10a
• /
• pp.861-865
• /
• 2009

Technical development in car has utilized electronic controls (ECU, Electronic Control Unit) recently if was achieved machine such as engine performance in priority and electronic side technical development that improve safety, convenience, expense etc. is proceeded vigorously. Also, preference of consumers for car is various model's number according to change at the fast speed and complexity of software required from vanguard service development was increased greatly. Software development expense dominated considerable weight in car manufacture expense by such change and automakers established OSEK/VDX that is standard of automobile embeded system to reuse application software by module to respond this and transplant easily to other control device. Do when search about all item that is necessary in real-time OS structure that examines OSEK/VDX standard that is presented as the alternative to respond environment that change rapidly that refer in dignified mien after it is original, and uses actuality OSEK/VDX.

• Journal of Digital Convergence
• /
• v.12 no.1
• /
• pp.371-377
• /
• 2014

Software quality is very important in software. We think, software testing is very important in point of functionality, usability. But, we have to consider about all of the software quality. We change our thinking about software quality from time to time. In this paper, we try to the best to find important factors by the number of testing dates and the number of testing in point of functionality, usability, reliability, efficiency, portability, maintainability. We study the mean of the number of faults according to products. We find the difference the number of errors by sex of tester.

• International Journal of Aeronautical and Space Sciences
• /
• v.9 no.2
• /
• pp.121-128
• /
• 2008

Modularized GPS software defined radio (SDR) has many advantages of applying and modifying algorithm. Hardware based GPS receiver uses many hardware parts (such as RF front, correlators, CPU and other peripherals) that process tracked signal and navigation data to calculate user position, while SDR uses software modules, which run on general purpose CPU platform or embedded DSP. SDR does not have to change hardware part and is not limited by hardware capability when new processing algorithm is applied. The weakness of SDR is that software correlation takes lots of processing time. However, in these days the evolution of processing power of MPU and DSP leads the competitiveness of SDR against the hardware GPS receiver. This paper shows a study of modulization of GPS software platform and it presents development of the GNSS software platform using MATLAB Simulink™. We focus on post processing SDR platform which is usually adapted in research area. The main functions of SDR are GPS signal acquisition, signal tracking, decoding navigation data and calculating stand alone user position from stored data that was down converted and sampled intermediate frequency (IF) data. Each module of SDR platform is categorized by function for applicability for applying for other frequency and GPS signal easily. The developed software platform is tested using stored data which is down-converted and sampled IF data file. The test results present that the software platform calculates user position properly.