• 정보처리학회논문지D
• /
• 제15D권5호
• /
• pp.647-658
• /
• 2008

자연어로 작성된 고객의 요구사항은 개발과정에서 모델링 언어로 재작성 된다. 그러나 개발에 참여하는 다양한 계층의 사람들은 모델링 언어로 작성된 요구사항을 이해하지 못하는 경우가 많이 발생한다. 본 논문에서는 REED(REquirement EDitor)로 작성된 요구사항 모델을 자연어로 번역하여 개발에 참여하는 모든 계층의 사람들이 요구사항 모델을 이해할 수 있도록 도와주는 방안을 제시한다. 제시한 방법은 3단계로 구성되어 있다. 1단계 IORT(Input-Output Relation Tree) 생성, 2단계 RTT(Requirement Translation Tree) 생성, 3단계 자연어로 번역의 단계를 거친다.

• International journal of advanced smart convergence
• /
• 제13권1호
• /
• pp.92-98
• /
• 2024

The current software industry has an emerging issue with natural language-based requirement specifications. However, the accuracy of such requirement analysis remains a concern. It is noted that most errors still occur at the requirement specification stage. Defining and analyzing requirements based on natural language has become necessary. To address this issue, the linguistic theories of Chomsky and Fillmore are applied to the analysis of natural language-based requirements. This involves identifying the semantics of morphemes and nouns. Consequently, a mechanism was proposed for extracting object state designs and automatically generating code templates. Building on this mechanism, I suggest generating natural language-based comic images. Utilizing state diagrams, I apply changes to the states of comic characters (protagonists) and extract variations in their expressions. This introduces a novel approach to comic image generation. I anticipate highly productive comic creation by applying software processes to Cartoon ART.

• International journal of advanced smart convergence
• /
• 제13권1호
• /
• pp.99-107
• /
• 2024

In AI image generation tools, most general users must use an effective prompt to craft queries or statements to elicit the desired response (image, result) from the AI model. But we are software engineers who focus on software processes. At the process's early stage, we use informal and formal requirement specifications. At this time, we adapt the natural language approach into requirement engineering and toon engineering. Most Generative AI tools do not produce the same image in the same query. The reason is that the same data asset is not used for the same query. To solve this problem, we intend to use informal requirement engineering and linguistics to create a toon. Therefore, we propose a sequence diagram and image generation mechanism by analyzing and applying key objects and attributes as an informal natural language requirement analysis. Identify morpheme and semantic roles by analyzing natural language through linguistic methods. Based on the analysis results, a sequence diagram and an image are generated through the diagram. We expect consistent image generation using the same image element asset through the proposed mechanism.

• International Journal of Knowledge Content Development & Technology
• /
• 제3권2호
• /
• pp.43-65
• /
• 2013

In this work, we first introduce two main approaches to writing requirements and then propose a method based on Natural Language Processing to improve requirement authoring and the overall coherence, cohesion and organization of requirement documents. We investigate the structure of requirement kernels, and then the discourse structure associated with those kernels. This will then enable the system to accurately extract requirements and their related contexts from texts (called requirement mining). Finally, we relate a first experimentation on requirement mining based on texts from seven companies. An evaluation that compares those results with manually annotated corpora of documents is given to conclude.

• 정보처리학회논문지D
• /
• 제15D권4호
• /
• pp.505-512
• /
• 2008

임베디드 시스템에 대한 RBT(Requirement-Based Testing)를 수행하기 위하여 정확한 요구사항 명세서가 존재해야 한다. 그러나 고객이 자연어로 작성하는 요구사항은 모호성, 부정확성, 불일치성을 가지고 있다. 이를 해결하기 위해서 UML, Simulink등의 모델링 언어를 이용하여 요구사항을 다시 모델링 하지만, 이 과정에서 요구사항을 use-case단위로 조합하고 재해석하는 단점이 생겨나게 되었다. 본 논문에서는 임베디드 시스템에 대한 고객의 요구사항을 use-case단위의 조합이나 재해석이 필요 없이 곧바로 모델로 표현할 수 있는 그래픽 언어를 이용한 1:1 요구사항 모델링 기법을 소개한다. 제안한 방법은 1) 임베디드 시스템의 요구사항을 자연어가 아닌 의미가 분명한 그래픽 언어를 이용하여 표현하고, 2) 하나의 요구사항을 하나의 그래픽 모델로 표현한다. 또한 제안한 방법은 시스템의 입출력을 기반으로 "what-to-do"만을 기술하기 때문에 상위레벨의 요구사항이나 하위레벨의 요구사항 모두에 적용할 수 있는 기법이다. 이 기법이 적용된 REED라는 도구를 통하여 실제 프로젝트에 적용한 예를 살펴본다.

• International Journal of Internet, Broadcasting and Communication
• /
• 제15권2호
• /
• pp.218-226
• /
• 2023

In Korea, we still use function point based cost estimations for software size and cost of a project. The current problem is that we make difficultly calculating function points with requirements and also have less accurate. That is, it is difficult for non-experts to analyze requirements and calculate function point values with them, and even experts often derive different function points. In addition, all stakeholders strongly make the validity and accuracy of the function point values of the project before /after the development is completed. There are methods for performing function point analysis using source code [1][2][3][4] and some researchers [5][6][7] attempt empirical verification of function points about the estimated cost. There is no research on automatic cost validation with source code after the final development is completed. In this paper, we propose automatically how to calculate Function Points based on natural language requirements before development and prove FP calculation based on the final source code after development. We expect validation by comparing the function scores calculated by forward engineering and reverse engineering methods.

• 한국인터넷방송통신학회논문지
• /
• 제17권6호
• /
• pp.97-103
• /
• 2017

고품질의 소프트웨어를 개발하기 위해서는 개발 초기단계에 정확한 요구사항 정의 및 분석이 필요하다. 그러나 대부분의 자연어 기반의 요구사항 문장 표현은 부정확성과 이해도 어려운 실정이다. 또한 요구사항은 같은 의미를 가진 객체나 용어들이 중복 식별된다. 이를 해결하기 위해 고객 요구사항을 언어학적 및 의미적 문맥 분석을 통한 효율적인 요구사항 분석 방법이 필요하다. 본 논문에서는 요구공학 언어학자인 Fillmore의 의미론적 분석 방법을 요구공학에 접목하고, 의미론적 분석 개선 방안을 제안한다. 이 방법은 자연어 기반의 요구사항을 Goal Oriented Use Case Modeling 통해 쉽게 읽고 이해 가능한 요구 사항 분석이 기대된다.

• Nuclear Engineering and Technology
• /
• 제36권4호
• /
• pp.295-303
• /
• 2004

Software inspection is widely believed to be an effective method for software verification and validation (V&V). However, software inspection is labor-intensive and, since it uses little technology, software inspection is viewed upon as unsuitable for a more technology-oriented development environment. Nevertheless, software inspection is gaining in popularity. KAIST Nuclear I&C and Information Engineering Laboratory (NICIEL) has developed software management and inspection support tools, collectively named "SIS-RT. "SIS-RT is designed to partially automate the software inspection processes. SIS-RT supports the analyses of traceability between a given set of specification documents. To make SIS-RT compatible for documents written in Korean, certain techniques in natural language processing have been studied [9]. Among the techniques considered, case grammar is most suitable for analyses of the Korean language [3]. In this paper, we propose a methodology that uses a case grammar approach to analyze the traceability between documents written in Korean. A discussion regarding some examples of such an analysis will follow.

• 한국정보처리학회:학술대회논문집
• /
• 한국정보처리학회 2007년도 추계학술발표대회
• /
• pp.325-327
• /
• 2007

Software testing 은 소프트웨어 개발 과정 중에 1/3 을 차지 할 만큼 중요한 부분 중 하나이다. Software testing 는 Requirement 작성이 제대로 이루어져야만이 제대로 testing 을 할 수 있고, 그에 따라 정확한 결과를 얻을 수 있다. 그 만큼 Requirement 작성이 중요시 되고 있지만, 수동적으로 기술자에 의해서 작성되는 Requirement 에는 많은 문제점을 안고 있다. 본 논문에서는 Requirement를 Graph 하게 표현한 방법을 소개하고, 표현된 방식을 이용하여 다시 자연어로 표현할 수 있도록 Database 를 설계하는 방식을 제안한다. 그 결과로 Design 된 패턴들을 이용하여 Requirement 자연어로 기술한다. 이를 통하여 Requirment 기술 방식을 통일화 시킬 수 있으며, 기술자간에 의사소통을 원할하게 수행할 수 있으며, Software testing 의 중요 기반으로 제공할 수 있다.

• International journal of advanced smart convergence
• /
• 제13권1호
• /
• pp.85-91
• /
• 2024

Currently, generative artificial intelligence is a hot topic around the world. Generative artificial intelligence creates various images, art, video clips, advertisements, etc. The problem is that it is very difficult to verify the internal work of artificial intelligence. As a requirements engineer, I attempt to create a toon image by applying linguistic mechanisms to the current issue. This is combined with the UML object model through the semantic role analysis technique of linguists Chomsky and Fillmore. Then, the derived properties are linked to the toon creation template. This is to ensure productivity based on reusability rather than creativity in toon engineering. In the future, we plan to increase toon image productivity by incorporating software development processes and reusability.