• The KIPS Transactions:PartD
• /
• v.13D no.7 s.110
• /
• pp.909-922
• /
• 2006

The core assets include all properties which consist of an application in Product Line Engineering. The requirement, one of the core assets, is a basis of other core assets and commonality and variability of other core assets are classified by the requirement. accordingly, commonality and variability of the domain requirement should be managed objectively and it is necessary to make a process to reuse the domain requirements. However the requirement is analyzed by domain experts or developers without proper process. In this paper, we proposed the 4 activities: (1)the domain scoping, (2)the extraction and generalization of the domain requirement, (3)the domain requirement analyzing and modeling, (4)the change management, and sub activities. For all reasons given previously, it is possible to reduce the development time and cost by reusing the architectures and components related to the domain requirement. In addition, it is possible to increase the quality of the artifacts produced based on the requirements by managing them systematically.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2013.11a
• /
• pp.1222-1225
• /
• 2013

오늘날 기업의 시스템은 훨씬 복잡해지고 다루는 데이터의 규모는 점점 대형화됨에 따라 환경 변화에 기업이 대응하기가 어려워지고 있다. IT 환경의 변화에 기업이 대응하기 위해서는 메타데이터 관리시스템의 기능을 개선할 필요가 있다. 본 논문에서는 데이터 모델링에 대한 새로운 요구사항을 신속히 반영하기 위해서 모델의 변경 이력을 참조하지 않고 이관해야 할 목표 데이터베이스의 테이블의 형상을 비교하여 이관 관리 프로세스를 향상시킨 알고리즘을 설계하였다. 본 논문서 설계한 알고리즘을 통해 모델의 변경 이력을 참조할 경우 발생하는 데이터베이스 변경의 처리 횟수를 줄임으로써 프로세스 개선의 효과를 기대할 수 있는 알고리즘을 제시하였다.

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

• Proceedings of the Korea Information Processing Society Conference
• /
• 2015.04a
• /
• pp.567-570
• /
• 2015

기업, 개인에 있어 현재 많은 사람들이 인터넷을 통해 많은 행위를 하고 있다. 이중에 특히나 많은 Needs와 수요가 일어나고 관심 받고 있는 것은 e-Marketplace 이며 이중 구매하는 비중이 상당히 큰 분야가 B2B 구매시스템이다. 이에 해당 관련 시스템을 변경요청의 특성과 WBS에 미치는 영향을 분석하고 이를 개선해야 하는 방법에 대해 사례 분석을 통해 연구하였다.

• KIPS Transactions on Software and Data Engineering
• /
• v.7 no.9
• /
• pp.325-334
• /
• 2018

Requirement traceability should be continuously maintained in software development and evolution. However, it is usually updated in practice in the quality assurance phase. The gap between "is" and "should" exists due to the fact that developers must invest considerable effort to update requirement traceability while being able to obtain only marginal benefit from the updated traceability. To close this gap, we propose a spreadsheet application that enables developers to flexibly change mappings in a requirement traceability matrix. In this way, developers can reduce their effort in updating the requirement traceability matrix, but still obtain the common form of a requirement traceability matrix on a spreadsheet. The proposed application maintains the mappings between two artifacts on each sheet so that, whenever an artifact item changes, developers can instantly insert the relevant mapping changes. Then, when developers desire the common form of a requirement traceability matrix, the proposed application calculates the mappings among several artifacts and creates the matrix. The application also checks traceability errors and calculates the metrics so that developers can understand the completeness of the matrix. To understand the applicability of the proposed approach, we conducted a case study, which shows that the proposed application can be applied to the real project and easily incorporate the mapping changes.

• Product Safety
• /
• s.87
• /
• pp.50-59
• /
• 2001

기술표준원은 전기용품안전관리법의 개정시행으로 2000. 7. 1부터 전기용품형식제도가 안전인증제도로 변경되면서 전기용품기술기준을 연차적으로 국제기준(IEC)체제의 안전기준으로 전환됨에 따라 새로이 적용되는 국제기준 체제에 부합하는 전기용품안전기준의 조기정착과 전기용품의 안전성 확보를 지원하기 위하여 안전기준에 대한 토론회를 개최하고 있다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.471-473
• /
• 2000

소프트웨어의 대형화, 복잡화에 따라 아키텍처의 중요성이 더욱 강조되고 있다. 또한, 복잡한 사용자의 요구사항을 소프트웨어에 혹은 아키텍처에 잘 반영시킬 수 있는 방안이 연구되어지고 있다. 이 논문에서는 주요한 소프트웨어 아키텍처 분석, 검증 방법들 중의 하나인 ATAM을 지원하는 도구로서 WSMS를 제안하고 있다. WSMS는 웹 기반의 시나리오 관리도구로서, ATAM에서 아키텍처의 다양한 면을 기술하는 시나리오의 효율적인 관리를 위해 시나리오의 추출, 분류, 우선순위 결정, 변경관리 등의 기능을 수행한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.10a
• /
• pp.457-464
• /
• 2004

소프트웨어의 품질을 향상시키기 위해 결함을 찾고 시정하는 것을 통제하는데 가장 중요한 요소가 바로 오류/장애/실패(통칭하여 결함(defects)를 효과적으로 추적하는 것이며, 결함을 추적하기 위해서는 효과적인 결함 추적시스템(Defect Tracking System)의 도입이 필요하다. 기존의 결함 추적 시스템은 고객/사용자로부터의 문제보고, 테스팅 기간 중의 결함보고, 변경관리 기능 등을 통합적으로 제공하고 있지 못하다는 점과 테스팅을 포함한 개발과정의 정량적 통제를 위한 데이터를 효과적으로 축적 제공하지 못하고, 더욱이 결함의 근본적인 원인을 찾아 해결할 수 있도록 하기 위한 정보를 효과적으로 제공하지 못하고 있는 문제가 있다. 본 논문에서는 이러한 기존의 결함 추적 시스템의 문제점을 해결하고자 설계/구축되어 현재 사내에서 활용되고 있는 결함관리 시스템인 Promise System을 소개하고자 한다. Promise 시스템은 고객의 불만 및 요구사항, 인스펙션 및 테스팅 시의 결함 및 요구사항에 대하여 각 담당자별로 업무를 할당, 추적할 수 있게 하고, 결함 및 요구사항에 관한 각종 상태정보와 통계 정보를 제공하여, 각 개발 및 테스팅 단계별로 결함 제거 목표의 수립, 정량적 통제, 결함 원인 분석을 통한 프로세스 개선 등을 지원하는 시스템이다.

• Journal of Intelligence and Information Systems
• /
• v.10 no.2
• /
• pp.111-131
• /
• 2004

Software change is an essential operation for software evolution. To maintain the system competently, managers as well as developers must be able to understand the structure of the system but the structure of software is hidden to the developers and managers who need to change it. In this paper, we present a system (OntCIA) for supporting change impact analysis for rating and billing domain based on the semantic web technology. The basic idea of OntCIA is to build a domain knowledge base using an OWL ontology and RDF to implement change impact analysis system that would support the managers and software developers in finding out information about structure of large software system. OntCIA allows users to incrementally build an ontology in rating and billing domain and provides useful information in response to user queries concerning the code, such as, for example 'Find the modules which have a role for confirming new subscription'. The strengths of OntCIA are its architecture for easy maintenance as well as semantic indexing by automatic reasoning.

• Korean Journal of Construction Engineering and Management
• /
• v.11 no.2
• /
• pp.74-82
• /
• 2010

A government agency has been announced to increase 23,663 hundred million wons by cost of design change which occurred in the pre-construction and construction phase. As design change is a phenomenon to occur by means of a characteristic of the building design that standardization is difficult, even if it is said that a perfect design is done in design phase, design change is prevented, and it is going to decrease, and there is a limit. Because there are some causes in all of the construction project, it is change order of client, relative system, unfit design and field condition, etc. In this study, we are suggested logic and basic model of the decision making support process model that it should selecting the optimal alternative through complex and quantitative analyzed: that is cost, performance and constructability as respect Owner or CMr is executing project under the CM delivery system construction project which it occurred design change.