• Journal of the KSME
• /
• v.55 no.1
• /
• pp.41-44
• /
• 2015

이 글에서는 스마트폰의 하드웨어 및 소프트웨어 앱을 활용한 공학교육의 적용 방안과 교육의 질적 수준 향상 방안에 대해 소개하고자 한다.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.1
• /
• pp.1-6
• /
• 2014

Many companies have tried to adopt Software Product Line Engineering for improving the quality and productivity of information systems and software product. There are several models defined in software product line methodology and each model has different abstraction level. Therefor it is important to maintain the traceability and consistency between models. In this paper, consistency checking rules are suggested by traceability matrix of work products.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2009.11a
• /
• pp.849-850
• /
• 2009

하드웨어와 소프트웨어의 통합설계를 이용한 시스템 개발에서는 하드웨어와 소프트웨어 요소가 가지는 비용, 개발 시간, 유연성, 재사용성, 수행성능과 같은 특징간 trade-off를 고려해야 한다. 개발조직에서는 통합설계 및 개발을 위한 릴리스 플랜 수립 시에 개념적 수준의 하드웨어/소프트웨어 분할 아키텍처 스타일 후보들을 도출하고, 요구사항 선택을 위해 도출된 후보들에 대한 상대적 중요도를 결정한다. 본 논문에서는 제품의 릴리스 플랜 수립을 목표로 우선순위에 기반한 아키텍처 스타일 우선순위 선정 프로세스를 제안한다. 이를 위해 하드웨어와 소프트웨어 요소 사이의 trade-off를 고려하여 우선순위를 결정한다. 개발조직의 이해당사자는 주어진 자원 및 제약사항 내에서 제품의 목표를 달성할 수 있도록 우선순위화를 통해 릴리스 플랜의 완성도를 높일 수 있다.

• Journal of Convergence Society for SMB
• /
• v.1 no.1
• /
• pp.9-17
• /
• 2011

While software globalization is becoming more important, little research has been undertaken into what is meant by globalization and the degree of globalization capability in the Korean software industry. A survey study was conducted among software engineering professionals, gathering the data from 31 IT companies across 7 large-scale projects in Korea. The results indicate that the evaluation score for globalization capability is 2.51 out of 5 points, which is the lowest compared to other areas of software engineering such as team capability (2.88), process and tool supports (2.96), project management (2.97) and development (3.64). We also discuss how to introduce software globalization technologies in Korea based on the successful experiences of leading global IT companies.

• KIPS Transactions on Software and Data Engineering
• /
• v.11 no.7
• /
• pp.273-282
• /
• 2022

Testing approaches for configurable software product lines differs significantly from a single software testing, as it requires consideration of common parts used by all member products of a product line and variable parts shared by some or a single product. Test coverage is a measure of the adequacy of testing performed. Test coverage measurements are important to evaluate the adequacy of testing at the software product line level, as there can be hundreds of member products produced from configurable software product lines. This paper proposes a method for measuring code coverage at the product line level in configurable software product lines. The proposed method tests the member products of a product line after hierarchizing member products based on the inclusion relationship of the selected features, and quantifies SPL(Software Product Line) test coverage by synthesizing the test coverage of each product. As a result of applying the proposed method to 11 configurable software product line cases, we confirmed that the proposed method could quantitatively visualize how thoroughly the SPL testing was performed to help verify the adequacy of the SPL testing. In addition, we could check whether the newly performed testing for a member product covers the newly added code parts of a feature.

• Journal of the Korea Society of Computer and Information
• /
• v.18 no.2
• /
• pp.127-140
• /
• 2013

We explored the relationship between the level of change awareness and deployment of software process improvement (SPI) approaches using a competing values framework. To measure awareness level of organization's change, we used DICE framework provides means for predicting the outcome of change management initiatives. The four factors for organizaton's change: duration, integrity, commitment, and effort are evaluated and a score is calculated. The DICE(R) score is used to classify projects into win, worry, or woe zones. In this paper, we apply the DICE(R) score as an independent variable to predict the outcome of a software process improvement. Our results indicated that the Organization have a higher chance of success have the better outcome in software process improvement.

• The KIPS Transactions:PartD
• /
• v.13D no.3 s.106
• /
• pp.383-390
• /
• 2006

Product-line engineering is a dreaming goal in software engineering research. Unfortunately, the current underlying technologies do not seem to be still not much matured enough to make it viable in the industry. Based on our experiences in working on mobile telephony systems over 3 years, now we are in the course of developing an approach to product-line engineering for mobile telephony system software. In this paper, the experiences are shared together with our research motivation and idea. Consequently, we propose an approach to building and maintaining telephony application logics from the perspective of scenes. As a Domain-Specific Language(DSL), Menu Navigation Viewpoint(MNV) DSL is designed to deal with the problem domain of telephony applications. The functional requirements on how a set of telephony application logics are configured can be so various depending on manufacturer, product concept, service carrier, and so on. However, there is a commonality that all of the currently used telephony application logics can be generally described from the point of user's view, with a set of functional features that can be combinatorially synthesized from typical telephony services(i.e. voice/video telephony, CBS/SMS/MMS, address book, data connection, camera/multimedia, web browsing, etc.), and their possible connectivity. MNV DSL description acts as a backbone software architecture based on which the other types of telephony application logics are placed and aligned to work together globally.

• Journal of Software Engineering Society
• /
• v.28 no.1
• /
• pp.7-12
• /
• 2019

Recently, as the weight of software in the weapon system increases, the quality of the software becomes a very important factor. In order to improve the quality of the weapon system software, DAPA(Defense Acquisition Program Administration) has institutionalized software reliability in Weapon System Software Development and Management Manual. The manual presents specific methods and procedures to improve the weapon system software quality. In order to meet the required reliability test standards specified in the manual, it is necessary to continuously detect and correct defects throughout the entire development period. However, it is difficult to build proper reliability test environment due to the cost of software reliability tools, setting up secured and separated network environment, and etc. Therefore, in this study, we propose an efficient environment construction method for software reliability test of defense industry field in restricted development environment and limited resources.

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

본 연구에서는 소프트웨어 프로세스 개선모델인 CMMI에 기반한 소프트웨어 프로세스 품질인증 모델을 적용하여 중소기업 SW개발 프로세스의 개선성과를 보인다. 프로세스 개선영역은 프로젝트 관리, 개발, 지원 영역이며 소프트웨어 프로세스 품질인증 모델 대비 프로세스 이행수준 및 개선영역을 식별하고, SW개발 프로세스를 분석하였다. 분석결과를 토대로 SW개발 프로세스를 개선하여 프로세스 체계 수립, 요구사항과 산출물간의 추적성 관리체계 정립, 형상변경 통제체계 성립 등의 성과를 보인다.

• Journal of KIISE:Software and Applications
• /
• v.31 no.1
• /
• pp.20-28
• /
• 2004

Estimation of software project cost, effort, and duration in the early stage of software development cycle is a difficult and key problem in software engineering. Most of development effort and duration estimation models presented by regression model of simple relation function point vs. effort and effort vs. duration instead of considering developer's productivity. But different project have need for different effort according to developer's productivity if the projects are same software size. Also, different duration takes according to developer's productivity if the projects require the same effort. Therefore, models that take into account of productivity have a limited application in actual development project. This paper presents models that can be estimate the duration according to productivity in order to compensate a shortcoming of the previous models. Propose model that could presume development period by various methods based on productivity and compared models' performance. As a result of performance comparison, an estimating model of development period from software size got simple and most good result. The model gives decision-making information of development duration to project management in the early stage of software life cycle.