• Journal of KIISE:Software and Applications
• /
• v.37 no.3
• /
• pp.161-169
• /
• 2010

The requirement elicitation is the task of eliciting requirements from needs of stakeholders, and preparing for information for negotiation. However, there are methods for gathering needs, but there is no specific method for classifying them, generating information for negotiation. Therefore, To solve the problems, this paper proposes a method to classify requirement and to generate information for negotiation. The proposed methods use Kano model, statistical technique, and identifying relationship between requirements and problems within scope. Finally, we validate the proposed method on simulations, Rough Set Theory, and case study of model.

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

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.503-514
• /
• 2003

In conventional development methodologies, requirements are considered to be not changing after analysis phase, and requirements specifications are used for the next step system design purpose. But in the real world, requirements can be changed and modified throughout the development life cycle according to end-user's more understanding about the target system, new IT technologies, changes of customer environment and market situation, and so on. So there needs a requirements change management process that can extend requirements management over the entire development life cycle and can support managing changes to the requirements after design phase. In this paper, a requirements change management process that can be integrated into conventional development methodologies is proposed to support the extension of requirements life cycle and managing changes to the requirements after design phase. This process was evaluated through an verification test with a widely used development methodology‘MaRMI’.

• Proceedings of the Korean Information Science Society Conference
• /
• 2011.06a
• /
• pp.206-209
• /
• 2011

기존의 요구사항 추적테이블은 요구관리적 관점에서 요구사항의 일관성, 완전성 확보를 목표로 하거나 요구사항 누락과 충돌, 중복 방지 요구사항 변경관리 측면만을 강조해 왔다. 그러나 자체 솔루션 개발관점과 유지보수 측면에서 제시된 요구사항 추적테이블이 없었다. 따라서 본 논문에서는 Pain Chain을 근간으로 개발 후 유지보수 요청관리에 효과적인 요구사항 추적테이블 방안을 제시하고자 한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.283-286
• /
• 2004

소프트웨어 개발과정에서 사용자 요구사항을 정확히 만족하기 위해서는 사용자 관점에서 요구사항 검증을 위한 방법이 필요하다. 이것은 사용자의 요구사항이 시스템 개발자에게 적절히 반영되어 개발시스템이 보다 더 효과적으로 설계 및 구현이 가능하여 사용자가 요구하는 품질의 소프트웨어 시스템을 구현할 수 있기 때문이다. 본 논문에서는 시스템 구현 전 단계에서 사용자 요구사항을 효율적으로 검증할 수 있는 RV-UI 모델을 제안한다. RV-UI 모델 시스템은 상용화된 사용자 인터페이스를 프로세스별 기능 모델로 표준화하였고, 카노(Kano)의 이원적 품질이론을 적용한 인터페이스를 통해 명확한 사용자 요구사항의 검증과 체계적인 요구사항의 형상관리를 하도록 설계하였다.

• Proceedings of the Korea Multimedia Society Conference
• /
• 2004.05a
• /
• pp.753-757
• /
• 2004

소프트웨어 개발과정에서 사용자 요구사항을 만족하기 위한 유용한 소프트웨어 개발도구를 사용하면 매우 효과적이지만 사용자 관점에서 요구사항 검증을 위한 방법이 부족한 실정이다. 본 논문에서는 시스템 구현 전 단계에서 사용자 요구사항을 효율적으로 검증할 수 있는 프로토타입 RV-UI 모델을 제안하여 개발자와 사용자간 요구사항이 적절히 반영되어 개발 시스템이 효과적으로 설계되고 구현됨을 나타낸다. 본 논문에서 제안한 RV-Ul 모델은 기존의 상용화된 시스템 인터페이스를 기능별 모델로 분류하였으며, 이원적 품질이론을 적용한 인터페이스를 통해 사용자가 요구하는 명확한 요구사항과 요구사항에 따른 형상관리 효과를 극대화할 수 있게 설계하였다.

• Journal of the Korea Society of Computer and Information
• /
• v.6 no.4
• /
• pp.30-37
• /
• 2001

In the conventional development methodologies, requirements are considered to be not changing after the analysis phase. But in the real world requirements can be changed and modified through out the development life cycle according to end-user's more understanding about the target system. new IT technologies, changes of customer environment and market situation, and so on. In this paper, an idea of improving the requirements specification to extend requirements management over the whole development life cycle is proposed to resolve the requirements management problem of development methodologies.

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