• Journal of Korea Multimedia Society
• /
• v.8 no.5
• /
• pp.715-720
• /
• 2005

In a software development process, it is necessary to have a method which verifies and satisfies users' requirements in their point of view. This allows the system developer to design a high qualify software system and have it developed and used in an effective way since users' requirements have well been shown through it. In this paper, we propose the RV-UI model system that can verify users' requirements a step ahead of system implementation step. This RV-UI model system has standardized user interface which is in practical use into functional model for each process and it is designed to satisfy users' requirements and manage configuration of them through the interface which has the Kano model.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.263-271
• /
• 2016

Software requirement analysis is necessary for successful software development project. Specially, incomplete requirement is the most influential causes of software project failure. Incomplete requirement can bring late delay and over budget because of the misunderstanding and ambiguous criteria for project validation. Software requirement patterns can help writing more complete requirement. These can be a reference model and standards when author writing or validating software requirement. Furthermore, when a novice writes the software scenario, the requirement patterns can be one of the guideline. In this paper proposes an automatic approach to identifying software scenario patterns from various software scenarios. In this paper, we gathered 83 scenarios from eight industrial systems, and show how to extract 54 scenario patterns and how to find omitted action of the scenario using extracted patterns for the feasibility of the approach.

• The Journal of the Korea Contents Association
• /
• v.8 no.5
• /
• pp.61-71
• /
• 2008

It is often claimed that the descriptive way of documentation is insufficient to define software requirements as being unambiguous. This is caused by not only the difference of knowledge and understanding of the stakeholder as to system but also the difference in the way of documentation like method of representation as well as depth of description. The study explains the process and results of applying a diagraming tool like UML to improve the requirements of GLORY(GLObal Resource management sYstem) initially defined in descriptive way. Especially, the result shows that the requirements are more accurately improved with the good hierarchies and well-leveled functionalities, with the help of diagraming tool, expecting easy maintenance of requirements and prevention of omission of requirements.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.17 no.7
• /
• pp.425-433
• /
• 2016

The construction of a light rail transit (LRT) system is a large and complex infrastructure project involving hundreds of billions of won in construction costs for a single route, and it is very important to carry out such a project from a life-cycle perspective because of its long-term operation. Systems engineering is a means and methodology to successfully implement customers' needs, and it is useful in large projects such as light rail transit. An application model called Systems Engineering for Light Rail Transit (SELRT) was developed to support systems engineering activities in light rail transit projects. In order to utilize SELRT, it is necessary to ensure that system requirements are met. As such, in this paper, we present a verification procedure and architecture based on a systems engineering-based methodology, thereby identifying the system requirements and deriving the verification requirements to confirm the SELRT model for the proposed method. The results show that the traceability of the system requirements and verification requirements, the verification method for each requirement, and the demonstration results for computerized tools are mutually connected, and that the initial requirements are clearly implemented in the SELRT. The proposed method is valid for verifying the SELRT, which can also be utilized in a LRT project.

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

시스템 또는 소프트웨어의 개발에 있어서 요구사항은 가장 중요한 산출물 중 하나이며, 요구사항의 오류를 수정하는 비용은 프로젝트가 진행됨에 따라 급격히 증가하기 때문에 잘 작성된 요구사항은 개발비용의 절감효과를 가져올 수 있다. 자연어의 모호성으로 발생될 수 있는 오류들을 줄이기 위해 정형적인 언어를 사용하여 요구사항을 명세하고, 요구사항의 완전성을 높일 수 있다. 본 논문에서는 열차제어시스템의 핵심 기능 중 하나인 간격제어모듈의 요구사항을 상태차트로 명세 및 검증 하였다.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.346-348
• /
• 2004

최근 개발되는 임베디드 시스템의 경우 하드웨어와 소프트웨어의 구조가 매우 복잡해짐에 따라, 시스템에 탑재되는 소프트웨어의 신뢰성 확보를 위한 테스트 절차가 요구되고 있다. 특히 시스템에 탑재되는 소프트웨어는 다중 함수에 의해 의사결정이 되면서. 시스템 디자인 단계에서 요구되는 스펙(Specification)을 만족하지 못하는 경우가 빈번하게 발생한다 본 논문에서는 임베디드 소프트웨어의 자동화된 테스트를 위해 요구되는 검증 모듈을 디자인하고 구현하였다 검증 모듈은 요구사항 기반으로 설계되었으며, 각각의 요구사항을 만족하는 검증 모듈을 구현하여 실제 상용화 제품에 대한 테스트를 진행하였다.

• Journal of the Korea Society for Simulation
• /
• v.18 no.3
• /
• pp.113-122
• /
• 2009

Software is getting more complex due to a variety of requirements that include desired functions and properties. Therefore, verifying and testing the software are complicated problems. Moreover, if the software is already implemented, inserting and deleting tracing/logging code into the source code may cause several problems, such as the code tangling and the code scattering problems. This paper proposes the Aspect DEVS Verification Framework which supports the verification and testing process. The Aspect DEVS Verification Framework utilizes Aspect Oriented Programming features to handle the code tangling and the code scattering problems. By applying aspect oriented features, a user can find and fix the inconsistency between requirement and implementation of a software without suffering the problems. The first step of the verification process is the building aspect code to make a software act as a generator. The second step is developing a requirement specification using DEVS diagrams and implementing it using the DEVSIM++. The final step is comparing the event traces from the software with the possible execution sequences from DEVS model.

• ETRI Journal
• /
• v.10 no.2
• /
• pp.52-62
• /
• 1988

소프트웨어 검증과 확인은 소프트웨어 시스팀의 높은 신뢰도를 보증하기 위한 활동이다. 즉, 더 신뢰성 있는 소프트웨어 제품 생성, 더 낮은 가격의 생명 순기(life-cycle), 요구사항과 일치하지 않는 사항들과 설계 에러들을 초기에 발견하여 개발 가격을 줄이는데 큰 의의를 갖는다. 본고에서는 대형 소프트웨어 개발에서 필요한 검증에 관하여 그 정의와 이제까지 검증 활동을 통하여 제시된 여러 사항들 및 일반적인 자동화된 검증시스팀에 대하여 살펴보고, 특히 General Research Corporation(Santa Barbara, California)에서 개발하고 Huges 항공사에서 프로젝트에 적용을 시켜 성공을 거둔 상용화된 검증시스팀에 대해 고찰하였다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2023.05a
• /
• pp.644-646
• /
• 2023

스마트팩토리는 협동 로봇과 같은 프로그래머블한 설비의 유기적인 협업을 통해 최적화된 공정을 수행한다. 따라서 수집되는 센서 데이터의 특징과 환경 조건의 복잡도가 높아, 예지보전을 위한 AI 소프트웨어의 개발 시 요구사항 기반의 체계적인 개발 및 검증이 필수적이다. 본 논문에서는 AI 소프트웨어의 요구사항을 사용자와 시스템 관점에서 정의하고, AI 모델 개발 프로세스와 스마트팩토리 예지보전 측면에서 분석한다. 도출된 요구사항을 CNN 기반의 협동 로봇 기어 마모 예측 모델의 개발에 적용하여 데이터 관리와 모델 신뢰성 관점의 요구사항을 분석 및 검증하였다.