• 정보통신설비학회논문지
• /
• 제9권1호
• /
• pp.13-18
• /
• 2010

As the importance of non-functional requirements has increased, many researchers have become interested in the software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated and there are many topics which have not been solved until now. In order to address one of the unsolved problems, we propose a systematic software development process to support the management of non-functional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be managed and modeled more effectively and systematically than previous ones.

• 한국컴퓨터정보학회논문지
• /
• 제24권7호
• /
• pp.19-29
• /
• 2019

Requirements traceability is regarded as one of the important quality attributes in software requirements engineering field. If requirements traceability is guaranteed then we can trace the requirements' life throughout all the phases, from the customers' needs in the early stage of the project to requirements specification, deployment, and maintenance phase. This includes not only tracking the development artifacts that accompany the requirements, but also tracking backwards from the development artifacts to the initial customer requirements associated with them. In this paper, especially, we dealt with the traceability between functional requirements and non-functional requirements. Among many Information Retrieval (IR) techniques, we decided to utilize Latent Semantic Indexing (LSI) and Latent Dirichlet Allocation (LDA) in our research. Ultimately, we conducted an experiment on constructing traceability by using two techniques and analyzed the experiment results. And then we provided a comparative study between two IR techniques in constructing traceability between functional requirements and non-functional requirements.

• 한국컴퓨터정보학회논문지
• /
• 제25권7호
• /
• pp.27-37
• /
• 2020

본 연구의 목적은 다양한 도메인에 대한 소프트웨어 요구사항 명세서로부터 수집된 요구사항을 데이터로 활용하여 데이터 중심적 접근법(Data-driven Approach)의 연구를 통해 요구사항을 분류한다. 이 과정에서 기존 요구사항의 특징과 정보를 바탕으로 다양한 자연어처리를 이용한 데이터 전처리와 기계학습 모델을 통해 요구사항을 기능적 요구사항과 비기능적 요구사항으로 분류하고 각 조합의 결과를 제시한다. 그 결과로, 요구사항을 분류하는 과정에서, 자연어처리를 이용한 데이터 전처리에서는 어간 추출과 불용어제거와 같은 토큰의 개수와 종류를 감소하여 데이터의 희소성을 좀 더 밀집형태로 변형하는 데이터 전처리보다는 단어 빈도수와 역문서 빈도수를 기반으로 단어의 가중치를 계산하는 데이터 전처리가 다른 전처리보다 좋은 결과를 도출할 수 있었다. 이를 통해, 모든 단어를 고려하여 가중치 값은 기계학습에서 긍정적인 요인을 볼 수 있고 오히려 문장에서 의미 없는 단어를 제거하는 불용어 제거는 부정적인 요소로 확인할 수 있었다.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제33권1호
• /
• pp.58-68
• /
• 2006

요구사항은 아키텍처를 생성할 때 매우 중요한 요소로써 기능 요구사항과 품질 요구사항으로 구분된다. 기능 요구사항은 하위시스템 또는 컴포넌트 생성에 영향을 미치고 품질 요구사항은 아키텍처의 구조를 결정하는데 영향을 준다. 이와 같이 요구 사항은 아키텍처 설계에 중요한 영향을 끼치기 때문에 아키텍처 설계를 위해서는 요구사항에 대한 명확한 이해가 필요하다. 본 논문에서는 요구사항에 대한 명확한 이해를 돕기 위해 요구사항을 정량화하는 방법을 제안한다. 기능 요구사항은 기능적인 우선순위 계산을 통해 컴포넌트를 정량화하고 품질 요구사항은 정량화된 컴포넌트와 품질 속성의 연관성 계산을 통해 정량화한다. 제안된 방법은 DRAMA (Domain Requirements Analysis for Modeling Architectures) 도구를 통해 구현되었으며, 요구사항의 정량화 방법을 실 예제에 적용해본 결과를 소개한다.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제33권7호
• /
• pp.615-623
• /
• 2006

비기능적 요구사항은 대상 시스템이 지원해야 할 기능적 요구사항의 속성 또는 품질 요구사항을 말하며, 소프트웨어의 품질 속성으로 반영된다. 이러한 비기능적 요구사항은 특히 성능과 관계된 부분의 설계를 결정하기 위한 중요한 기준으로 사용된다. 따라서 비기능적 요구사항은 소프트웨어 개발 생명주기 전반에 걸쳐 계속적으로 고려되고, 관리되어야 한다. 하지만 비기능적 요구사항의 모호성과 비가시적 특성으로 인해 도출 및 명세뿐만 아니라, 관리에도 어려움이 많다. 이에 본 논문에서는 NFR 그래프를 이용해 비기능적 요구사항에 가시성을 부여하고 비기능적 요구사항을 설계에 반영하여 비기능적 요구사항 관리의 효율성을 높이기 위한 비기능적 요구사항의 추적 기법을 제안한다. 비기능적 요구사항 개발 절차에 따라 지능형 조명 제어 시스템의 성능 요구사항 추적 방법을 사례연구로 수행하였으며, 이를 통해 종합적으로 비기능적 요구사항 관리의 효율을 높이고자 한다.

• 한국항해항만학회지
• /
• 제43권6호
• /
• pp.353-360
• /
• 2019

Technology-driven development of a new system makes it difficult for users and stakeholders to identify or intervene in the development process, resulting in systems with unnecessary functions and poor quality services. Applying the software architecture design process to the initial design of the navigation system platform of autonomous ships enables the development of a system that reflects the required functions and service quality of the stakeholders. The design, which includes all of the subsystems that make up an autonomous ship platform, is close to an enterprise architecture. Thus, we strived to design a navigation system platform suitable for the design range of the software architecture. This study analyzed the definition of functional requirements, and quality attributes by applying the software architecture design procedure. This study was conducted to identify the characteristics of the navigation system and platform needs, and the stakeholders were identified. To derive the functional requirements and constraints of the platform, a quality attributes workshop was held engaging stakeholders, and the results of the analysis of functional requirements and quality attributes were listed. Based on the results of this study, the architect can establish the evidence and technical solutions that are integral for the architecture development, and will facilitate the creation of quality attribute scenarios.

• 한국컴퓨터정보학회논문지
• /
• 제24권3호
• /
• pp.65-75
• /
• 2019

Non-Functional Requirements (NFR) play a crucial role during the software development process. Currently, NFRs are considered more important than Functional Requirements and can determine the success of a software system. NFRs can be very complicated to understand due to their subjective manner and especially their conflicting nature. Self-adaptive systems (SAS) are operating in dynamically changing environment. Furthermore, the configuration of the SAS systems is dynamically changing according to the current systems context. This means that the configuration that manages the trade-off between NFRs in this context may not be suitable in another. This is because the NFRs satisfaction is based on a per-context basis. Therefore, one context configuration to satisfy one NFR may produce a conflict with another NFR. Furthermore, current approaches managing Non-Functional Requirements trade-off stops managing them during the system runtime which of concern. To solve this, we propose fragmentizing the NFRs and their alternative solutions in form of Multi-entity Bayesian network fragments. Consequently, when changes occur, our system creates a situation specific Bayesian network to measure the impact of the system's conditions and environmental changes on the NFRs satisfaction. Moreover, it dynamically decides which alternative solution is suitable for the current situation.

• KEPCO Journal on Electric Power and Energy
• /
• 제2권2호
• /
• pp.269-272
• /
• 2016

Distribution management system or microgrid energy management system plays an important role in monitoring, operation and control of electrical distribution systems by utilizing IT infrastructure. Nowadays, the rapid increase of the distributed resources makes the conventional management system have some additional functionality for the reliable operation due to intermittent renewables and the efficient operation on the economical purpose. In this paper, the brief standard software functional requirements of microgrid energy management system are provided through survey of the recent commercial products of the major vendors, and furthermore the architectures of microgrid energy management system are provided in comparison with major suppliers' microgrid energy management system. The summary of investigation will be able to make the developers and researchers focus on the specific functionality in the real world.

• 한국군사과학기술학회지
• /
• 제11권4호
• /
• pp.59-67
• /
• 2008

In the next near future, the human would like to use the small unmanned ground vehicle(SUGV) on the diverse fields. Specially the world of today is tried to apply with operating the task on very difficult working environments such as some dangerous or unreachable area. To work this task, this vehicle should be guaranteed with the high level of reliability, safety, and performance. In this paper, we propose to focus on not only the functional requirements, but also the non-functional requirements based on software architecture at the design stage for developing the embedded system. Through focusing on the non-functional requirements on this software architecture, we can obtain the design goal of the target system and also show the enhancement of reliability, safety and performance with 'Vtune' performance analysis tool.

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