• The Journal of Society for e-Business Studies
• /
• v.12 no.4
• /
• pp.1-15
• /
• 2007

Traceability links are logical links between individual requirements and other system elements such as architecture descriptions, source code, and test cases. These are useful for requirements change impact analysis, requirements conflict analysis, and requirements consistency checking. However, establishing and maintaining traceability links places a big burden since complex systems have especially yield an enormous number of various artifacts. We propose a feature-oriented requirements tracing method to manage requirements with cost benefit analysis, including value consideration and intermediate catalysis using features. Our approach offers two contributions to the study of requirements tracing: (1)We introduce feature modeling as intermediate catalysis to generate traceability links between user requirements and implementation artifacts. (2)We provide value consideration with cost and efforts to identify traceability links based on prioritized requirements, thus assigning a granularity level to each feature. In this paper, we especially present the results of a case study which is carried out in Apartment Ubiquitous Platform to integrate and connect home services in an apartment complex in details.

• Review of KIISC
• /
• v.25 no.1
• /
• pp.47-52
• /
• 2015

보안에서 인적보안(Personal Security)의 예방통제 중 하나로 개발/운영을 분리하는 직무분리(Separation of Duty)를 해오고 있다. 고의적인 시스템의 오용을 줄이기 위한 방법이며, 많은 국제 표준과 국내 표준(COBIT, ISMS, 등)에서 직무분리를 명시하고 있다. 하지만 무중단 시스템이면서, 운영자가 특정 전문가 집단으로 한정되고, 수 많은 변경이 발생하는 무중단 환경에서 개발/운영이 분리 됨으로 인한 여러 가지 문제점이 발생 하고 있다. 체계를 운영하면서 전문지식을 기반으로 한 요구사항을 명확하게 이해하지 못하면, 추가적인 요구사항이 발생한다. 이는 체계의 품질저하와 위험(Risk)증가로 이어지게 된다. 따라서 본 연구에서는 개발운영조직 통합관리(DevOps) 방법론을 SCADA와 같이 운영자가 해당 분야의 전문성을 가지고, 무중단으로 운영되며, 수많은 변경이 반영되는 시스템에서 개발 및 운영을 통합하였을 때, 발생할 수 있는 문제점과 개선방안을 제시하고자 한다.

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

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

• Journal of Internet Computing and Services
• /
• v.9 no.1
• /
• pp.115-127
• /
• 2008

The component for satisfying several domain requirements must be developed to support variety. But, when the application is developed using the component, it happens other requirements. So, it is difficult to design component to satisfy severaldomain requirements. Also, it is impossible to support the special business logic. As this problem, the component must provide to the white-box component, it is not the black-box component. So, in this paper, we propose the variability design technique and the customization technique using the design technique that can support the various requirements. This technique is not focus on designing the component to analyze various domains. The variability of the component is designed to the initial variability in the component development phase and we use the customization technique for applying the variability to developing application. The variability can be re-designed during developing the application to use the component applying the variability. The variability of the component is evolved and the generation of the component is increased via the iteration Generally, the range of the component variability is classified the function modification within the component and the component internal structure modification as requirements in the component outside. As the range of the variability, we propose the variability design technique of the behavior and the message flow. This paper proposes a message flow design technique for modifying function call.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.531-538
• /
• 2009

Domestic software market is struggling with product's low quality and low return-on-investment. The cause for the problems is due to unclear requirements at the early stage of software project. Studies show that, to lessen the problem, the requirements specification must reflect the right project scope and quantifiable quality goal. To achieve such features, this paper describes a standard guideline for SRS (Software Requirements Specification), which helps in defining the scope of project, measuring and quantifying quality, linking and tracing of requirements, and improving usability. The proposed SRS enables separating the requirements analysis activity from implementation activity and thus can improve subcontract management process in software project.

• Journal of KIISE
• /
• v.44 no.1
• /
• pp.27-35
• /
• 2017

Many studies have addressed 'Adaptive User Interface (AUI)', wherein the user interface changes in accordance with the situation and the environment of each user at runtime. Nevertheless, previous papers for AUI barely reflected the viewpoints from requirements engineering field, since most of them focused on proposing the architecture and design. In this study, we outline AUI with the perspective of requirements engineering and propose the requirements elicitation and specification method based on concepts which have been researched in the area of self-adaptive system. Step by step, we first redefine and reinterpret the well-known concepts of self-adaptive software, after which the AUI requirements are elicited and specified. Finally, we illustrate a case study, which demonstrates the effectiveness of our method.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.10
• /
• pp.3075-3085
• /
• 2000

According to distributed, large-caled environment of software development and operation, the elicitation and specivication of correct and complete requrement is the most important factor for the system. In addition contiuous and dramatic systerm canging requests in cooperative environment with internet require more efficient, requirement management. In this paper we detine the specification architecture and techruques for requrements, so that we improve the efficiency ofnatural language-based requirement speciticationand management in a cooperatie work environment. Also, we propose a software requirement engineering process model and environment based on requirements in a CSC@(Computer Supported Cjooperative Work) environment, therefore transfer them into analysis phase.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2008.06a
• /
• pp.105-110
• /
• 2008

웹서비스는 XML기반의 표준인 SOAP, WSDL, UDDI를 이용하여 인터넷을 통해 기능을 제공해 주는 서비스 기반 아키텍처의 대표적 기술이다. 웹서비스의 개수가 많아지고 종류가 다양해짐에 따라, 요청자의 요구사항에 맞는 웹서비스를 선택하는 것이 중요하게 되었으며, 여기서 웹서비스의 선택 시 QoS(Quality of Service)는 중요한 기준이 된다. 하지만 웹서비스의 QoS는 동적으로 변하고, 이로 인해 요청자의 QoS요구사항에 만족하지 않는 웹서비스가 되기도 한다. 본 논문에서는 요청자의 QoS요구사항에 적합한 웹서비스를 찾고, 웹서비스의 QoS변화로 인하여 웹서비스를 동적으로 변경하는 프레임워크를 제안한다. 그리고 웹서비스를 동적으로 변경하는 경우에 필요한, 각 웹서비스의 인터페이스 적응 및 기존 작업의 보장에 대한 해결방법도 함께 제시한다.

• KIPS Transactions on Software and Data Engineering
• /
• v.8 no.12
• /
• pp.465-472
• /
• 2019

Today, in many area the rise of software necessity there has been increasing the issue of the impotance of Good Software. Our reality in software industrial world has been happening to frequently change requirements at any stage of software life cycle. Furthermore this frequent changing will be increasing the design complexity, which will result in being the lower quality of software against our purpose the original design goals. To solve this problem, we suggest how to improve software design through refactoring based on reverse engineering. This is our way of diverse approaches to visually identify bad smell patterns in source code. We expect to improve software quality through refactoring on even frequently changing requirements.

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

소프트웨어 개발초기에 모든 요구사항을 정의하는 것은 불가능하며 모든 요구사항이 최고의 우선순위를 가지는 것 또한 아니다. 따라서, 올바른 일(Right Thing)을 올바른 순서(Right Order)로 하고, 변경에 따른 시소관계(Trade-off) 의사결정에 도움되는 고객가치 지향적인 요구사항 정제 방법이 필요하다. 본 논문은 고객 입장에서 핵심 서비스와 제품기능 만족도를 판단하는 긍정적인 가치요소와 프로젝트 팀 입장에서 구현 시 발생 비용과 기술적인 위험도를 판단하는 부정적인 가치요소에 의해 고객가치를 정량화하여 요구사항의 우선순위화 방법을 제안한다. 본 논문의 목적은 정해진 일정과 한정된 자원 내에서 반드시 필요한 모든 기능을 포함한 시스템을 고객에게 제공하고 모든 이해당사자들에게 실효성 있는 가치를 제공하여 요구 결항 축소 및 시스템 만족도를 높이는데 있다.