• 사물인터넷융복합논문지
• /
• 제9권6호
• /
• pp.45-50
• /
• 2023

소프트웨어 개발에서 요구사항 도출 및 분석은 매우 중요한 단계이며, 다양한 이해관계자가 관여하기 때문에 많은 시간과 노력을 필요로 한다. ChatGPT는 다양한 문서를 학습한 대규모 언어 모델로서 코드 생성, 디버깅 등의 능력은 물론 소프트웨어 분석 설계 영역에서도 활용할 수 있는 능력을 갖고 있는 것으로 연구되고 있다. 본 논문에서는 ChatGPT의 이러한 능력을 활용하여 소프트웨어 요구사항 도출, 시스템 목표에 적합한 요구사항 분석, 유스케이스 형태로 문서화하는 요구공학 방법을 제안한다. 소프트웨어 요구공학에서 이해관계자, 분석가, ChatGPT는 협업 모델을 가져야 하며, 요구사항 도출, 분석, 명세화에서 ChatGPT의 결과를 초기 요구사항으로 하여 분석가와 이해관계자가 점검 및 내용을 추가하는 형태로 요구공학이 진행하는 것을 제안한다. ChatGPT의 성능이 향상될수록 요구사항의 도출 및 분석이 점차 정확도를 높일 수 있을 것이며, 소프트웨어 요구공학에서 시간 및 비용을 절감할 수 있을 것이다.

• 정보과학회 논문지
• /
• 제43권8호
• /
• pp.857-868
• /
• 2016

소프트웨어 생태계의 시장 중심 개발 환경에서 소프트웨어 기업은 제품의 성공을 위해서 자신의 비즈니스와 고객에게 높은 가치를 제공할 수 있어야만 시장 경쟁력을 가지고 생존할 수 있다. 요구공학적 관점에서 제품 요구사항 선택을 통한 가치 제공을 위해서 이해관계자들 각자의 다른 이해가 조정되어 합의되어야 한다. 즉, 요구공학 단계에서 높은 가치 창출을 고려하는 합의된 요구사항을 선택할 필요가 있다. 기존 연구들은 소프트웨어 생태계에서 요구되는 이해관계자들의 다른 이해에 대한 요구공학적 기법의 필요성을 언급하였을 뿐, 구체적인 가이드라인 및 수행 방법에 대하여 제안하지 않았다. 본 연구에서는 요구공학에서 사용되는 Goal 개념 기반으로 협상 참가자의 의도를 분석하고 이를 바탕으로 요구사항 충돌의 근거를 구조화하여 관리할 수 있도록 한다. 궁극적으로 협상 참가자의 이기적 행동을 바탕으로 게임 이론적 개념을 이용한 요구사항 충돌 해결 방법론을 제안한다.

• 정보처리학회논문지D
• /
• 제11D권7호
• /
• pp.1459-1466
• /
• 2004

소프트웨어 응용 분야의 확대로 인해, 소프트웨어는 더 크고, 더 복잡해지고 있다. 게다가 개발 기간의 단축 및 비용의 절감${\cdot}$품질의 향상 또한 요구되고 있다. 이러한 요구를 충족시키기 위해 여러 효율적인 방법이 제안되었고, 구현되었다. 대표적으로 프로세스 개선과 객체지향 개발, 요구공학, 소프트웨어 메트릭스 등이 있다. 이러한 수많은 방법 중에서 요구공학은 고품질의 소프트웨어 개발의 기반이 된다. 즉, 고품질의 소프트웨어를 개발하기 위해서는 먼저 요구를 획득하고, 기술하여야 하며, 이에 대한 검증과 관리를 통해 요구사양서의 품질을 향상시켜 가야 한다. 본 논문에서는 IEEE Std-830-1998의 좋은 요구사양서가 가져야 할 특성을 중심으로, 요구사양서에 기술된 내용 자체를 정량적으로 품질 평가할 수 있는 메트릭스를 제안하였다.

• 인터넷정보학회논문지
• /
• 제20권3호
• /
• pp.69-75
• /
• 2019

The safety and performance of medical device software is managed through life-cycle processes, which represent the entire process of research and development (R&D). The life-cycle process of medical device software is represented by an international standard called IEC 62304, ISO/IEC 12207. In order to license the product, the manufacturer must have document artifacts that comply with the IEC 62304 standard. However, these standards only describe the content of the activity and do not provide a method or procedure for documentation. Therefore, this paper suggests R&D documentation guidelines that assist medical device software developers to have R&D documents conforming to the standards. For this purpose, this study identifies the requirements related to documentation among the requirements existing in the standard and extracts them in the form of guidelines showing only the core information of the requirements. In addition, through the Web framework implemented based on this research, the developer can evaluate whether the technical documents are written in accordance with the R&D document guidelines. Medical device software manufacturers can efficiently produce high-quality research and development documents through R&D documentation guidelines, and they can have standards-compliantresearch and development documentation required for licensing procedures.

• 시스템엔지니어링학술지
• /
• 제2권2호
• /
• pp.21-26
• /
• 2006

In modern systems technology, increasingly more systems are anticipated to operate in real-time environment. These systems are usually complex to implement since it is not easy to satisfy the real-time requirement for both hardware and software components simultaneously. In this paper, we first review an object-oriented development process that was proposed earlier for software-intensive real-time system using the Unified Modeling Language (UML). We then study how to improve the problems that the UML approach might have. Applying the systems engineering(SE) process yields useful results which include : 1) an improved requirements management over the whole system life-cycle ; 2) a detailed scenario on how to carry out the SE process ; and 3) a conversion process from the text-based requirements to the UML-based graphic ones.

• 반도체디스플레이기술학회지
• /
• 제22권1호
• /
• pp.88-93
• /
• 2023

In software engineering, requirement analysis is an important task throughout the process and takes up a high proportion. However, factors that fail to analyze requirements include communication failure, different understanding of the meaning of requirements, and failure to perform requirements normally. To solve this problem, we derived actors and behaviors using morpheme analysis and BERT algorithms in the Korean requirement document and constructed them as ontologies. A chatbot system with ontology data is constructed to derive a final system event list through Q&A with users. The chatbot system generates the derived system event list as a requirement diagram and a requirement specification and provides it to the user. Through the above system, diagrams and specifications with a level of coverage complied with Korean requirement documents were created.

• 한국CDE학회논문집
• /
• 제16권6호
• /
• pp.449-457
• /
• 2011

The productivity improvement is indispensible to shipbuilding industry for maintaining the world's No. 1. Simulation based production recently has been an issue as prat of efforts to high efficiency production and Korean shipyards requests simulation system tools specialized in a shipbuilding industry. IT convergence project between conventional shipbuilding industry and IT simulation technology has been carried out and integrated simulation framework was proposed as a way to overcome sporadic developments. The framework would provide reusability of kernels and modules and also ensure for expansibilities to other production simulations. The fact that production simulation system should reflect shipyard requirement would be most important. We suggest an analysis process of customer requirements and functional requirements for production simulations. It is partially based on concepts of software engineering and axiomatic design. The process is applied to a design of configuration for simulation framework.

• International Journal of Computer Science & Network Security
• /
• 제23권8호
• /
• pp.199-203
• /
• 2023

Influential trend that widely reflected the software engineering industry is service oriented architecture. Vendors are migrating towards cloud environment to benefit their organization. Companies usually offer products and services with a goal to solve problems at customer end. Because customers are more interested in solution of their problem rather than focusing on products or services. In software industry the approach in which customers' problems are solved by providing services is known as software as a service. However, software development life cycle encounters enormous changes when migrating software from product model to service model. Enough research has been done on the overall development process but a limited work has been done on the factors that influence requirements elicitation process. This paper focuses on those changes that influence requirement elicitation process and proposes a systematic methodology for transformation of software from product to service model in a successful manner. The paper then elaborates the benefits that inherently come along with elicitation process in cloud environment. The paper also describes the problems during transformation. The paper concludes that requirement engineering process turn out to be more profitable after transformation of traditional software from product to service model.

• International Journal of Internet, Broadcasting and Communication
• /
• 제15권3호
• /
• pp.219-230
• /
• 2023

With the development of autonomous driving technology, as the use of software in vehicles increases, the complexity of the system increases and the difficulty of development increases. Developments that meet ISO 26262 must be carried out to reduce the malfunctions that may occur in vehicles where the system is becoming more complex. ISO 26262 for the functional safety of the vehicle industry proposes to consider functional safety from the design stage to all stages of development. Specifically at the software level, the requirements to be complied with during development and the requirements to be complied with during verification are defined. However, it is not clearly expressed about specific design methods or development methods, and it is necessary to supplement development guidelines. The importance of analysis and verification of requirements is increasing due to the development of technology and the increase of system complexity. The vehicle industry must carry out developments that meet functional safety requirements while carrying out various development activities. We propose a process that reflects the perspective of system engineering to meet the smooth application and developmentrequirements of ISO 26262. In addition, the safety analysis/verification FMEA processforthe safety of the proposed ISO 26262 function was conducted based on the FCAS (Forward Collision Avoidance Assist System) function applied to autonomous vehicles and the results were confirmed. In addition, the safety analysis/verification FMEA process for the safety of the proposed ISO 26262 function was conducted based on the FCAS (Forward Collision Avoidance Assist System) function applied to the advanced driver assistance system and the results were confirmed.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• 제13권8호
• /
• pp.4174-4190
• /
• 2019

IEC 62304 is a standard for the medical device software lifecycle. Developers must develop software that complies with all specifications in the standard for licensing. However, because the standard contains not only a large number of specifications, but also domain-specific information and association relationships between specifications, it requires considerable effort and time for developers to understand and interpret the standard. To support developers, this paper presents a method for extracting the contents of the IEC 62304 standard as a goal model, which is the core methodologies of requirements engineering. The proposed method analyzes the grammar of the standard to robustly extract complex structures and various information from standard specifications and define rules that extract goals and links from syntactic element units. We validated the actual extraction process for the standard document experimentally. Based on the extracted goal model, developers can intuitively and efficiently comply with the standard and track specific information within the medical software and standard domains.