• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.13 no.9
• /
• pp.4207-4213
• /
• 2012

Software quality is strongly associated with requirement quality. Accordingly, companies are trying effect for enhancing requirement quality. But, it is difficult to verify the requirement of specification format, which have to rely on abnormal business knowledge of analyst. Also, it is insufficient to normal methodology or automated technique for enhancing requirement quality of specification format. In this paper, we propose the process of requirement verification and automated verification tool for enhancing requirement quality. we compare the external view design and internal view design for verifying requirement. In the case study, we evaluate the feasibility of the proposed automated verification technique of requirement.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.14 no.1
• /
• pp.37-49
• /
• 2014

This paper proposes a optimal process after analyzing the existing papers of software requirements engineering process. In analyzing it examines requirement pursuit management and origin, and considers a variety of starting points that draw requirement documents. Also, this paper considers carefully the multiple methods of stakeholder needs, problem analysis, processing priority of business modeling. From the analyzed result this paper proposes the best method that draws systematically the requirement documents. The proposed method can minimize the requirement changes, draw the higher project success ratio, and satisfy the customer.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.10
• /
• pp.117-127
• /
• 2012

Identifying user requirements efficiently and reflecting them on the existing system is very important in a rapidly changing web and mobile environments. This study proposes the strategies to refining requirements and to prioritizing those refined requirements for changing of web and mobile application based on user requirements (e.g. mobile application comments, Q&A, reported information as discomfort factors). In order to refining the user requirements, those requirements are grouped by using the advancement of the software business of the Forum of standardization and the existing configuration-based programs. Then, we mapped them onto the PIECES framework to identifying whether the refined requirements are correctly reflected to the system in a way of valid and pure. To determine the priority of refined requirements, first, relative weights are given to software structure, requirements and categories of PIECES. Second, integration points on each requirement are counted to obtain the relative value of partial and overall score of a set of software structural requirements. In order to verifying the possibility and proving the effectiveness of proposing technique in this study, survey was conducted on changing requirements of mobile application which have been serviced at S University by targeting 15 people of work-related stakeholders.

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

• Journal of KIISE:Software and Applications
• /
• v.37 no.5
• /
• pp.411-415
• /
• 2010

The Conflicts between requirements may cause a failure of functions or even project. Currently, most of researches have focused on identifying requirements and some researchers have tried to resolve requirements conflicts but it was only based on requirement priority. This paper proposes the Creative Requirements Conflict Resolution (CRRC) to resolve requirement conflicts in a creative way using TRIZ methodology. TRIZ, which means the theory of solving inventor's problems, is made based on the analysis of over 2 million patent cases and helpful for developing a creative solution to resolve conflicts. CRRC classifies requirement conflicts into groups and then apply TRIZ theory related to each group. At the result of control experiment, CRRC provides the various kinds of creative solution for requirement conflicts.

• Journal of the Korea Society for Simulation
• /
• v.27 no.2
• /
• pp.61-69
• /
• 2018

As the technology of information and communication has developed over recent years, an embedded system is applied in multiple industries and becomes more complicated. For this reason, embedded system development cost and time are also increased. For decreasing the cost and time, this paper suggests requirement evaluation method for concurrent development of an embedded system based on Discrete Event System(DEVS) Formalism. This paper proposes a method of describing the requirements specification in the form of DEVS atomic model. Also, the paper proposes the evaluator model that compares evaluation target system and the requirements model that is an implementation of requirement specification and proposes the evaluation method using them. In addition, we propose a method to utilize the requirement model created for requirements evaluation in the concurrent development process of the embedded system. As the case study, this paper proceeds requirement evaluation of Kinect depth data processing system.

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

• The KIPS Transactions:PartD
• /
• v.18D no.6
• /
• pp.433-442
• /
• 2011

As software is varied and grew in size, the importance of clear understanding and representing customer's need, has been emphasized. It is not easy to drive and define critical system needs, since requirements in early stage of the development, is and conceptual. Technical perspective view, Several theoretical analysis methods and validation techniques are introduced, but in practice, it is hard to drive clear customer's requirement. In this paper, to drive clear customer's requirements, Macrostruktur concept of textlinguistics is used. First, Macrostruktur of textlinguistics is used to analysis descriptive requirements. Second, Macrostruktur-rule is applied to analyzed Macrostruktur data in order to derive Macrostruktur-propositions. Finally, it is proposed to generating Use-case model using derived Macrostruktur-propositions.

• Proceedings of the Korea Institutes of Information Security and Cryptology Conference
• /
• 2002.11a
• /
• pp.625-628
• /
• 2002

생체인식 정보관리 보안표준인 X9.84는 금융서비스에서 금융산업 서비스를 위하여 생체인식정보에 대한 안전한 운영관리를 목적으로 관리메커니즘 및 보안 고려사항 등을 정의하기 위하여 미국 ANSI에서 개발한 국가표준이다. 본 논문에서는 X.9.84에서 제시하는 적용범위, 준용표준, 관리 및 보안요구사항, Biometric 등록, 보안 고려사항 등을 분석하여 금융서비스, 전자상거래 등의 국내 사용자 인증서비스에 적용가능한 생체인식 보안표준으로 개발하기 위하여 준용사항과 암호학적 메커니즘 사용, 관리 및 보안요구 사항, Biometric 등록, 보안고려사항, 감사기록 형식 등의 국내 고려사항을 적용하여 국내 생체인식 정보관리 및 보안표준(K-X9.84)으로 개발하고자 한다.

• 한국공간정보시스템학회:학술대회논문집
• /
• 2005.11a
• /
• pp.209-215
• /
• 2005

본 논문의 목적은 GIS특성이 반영되고 표준화를 적극 활용한 GIS 감리중점사항을 제시하는데 있다. 이를 위해 GIS를 정보시스템의 한 분야로 간주하여 정보시스템의 개발과정의 단계를 살펴본 후에 GIS의 데이터제작단계를 추가하여 GIS 감리중점사항을 제안하였다. 감리중점사항의 제시를 위해 GIS 감리에 관련된 기존연구와 감리사례별 연구를 통해 감리중점분야를 도출하여 각 분야의 중점감리사항을 제시하였다. 특히 현재 국내에 제정된 표준화목록을 대상으로 각각의 표준화를 분석, 정리하여 표준화 부분의 감리중점사항으로 제시하였다. 따라서 본 연구결과를 GIS 감리업무 종사자가 작업지침의 일부로 활용함으로써 감리수행 활동이 적절히 진행되고 있는지를 확인할 수 있고 궁극적으로 GIS 활용시스템의 효율성, 안전성, 확장성 등의 확보에 기여하리라 사료된다.