• Journal of The Institute of Information and Telecommunication Facilities Engineering
• /
• v.9 no.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.

• Journal of the Korea Society of Computer and Information
• /
• v.24 no.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.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.7
• /
• pp.27-37
• /
• 2020

In this paper, we propose the methodology based on data-driven approach using Natural Language Processing and Machine Learning for classifying requirements into functional requirements and non-functional requirements. Through the analysis of the results of the requirements classification, we have learned that the trained models derived from requirements classification with data-preprocessing and classification algorithm based on the characteristics and information of existing requirements that used term weights based on TF and IDF outperformed the results that used stemming and stop words to classify the requirements into functional and non-functional requirements. This observation also shows that the term weight calculated without removal of the stemming and stop words influenced the results positively. Furthermore, we investigate an optimized method for the study of classifying software requirements into functional and non-functional requirements.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.58-68
• /
• 2006

Requirements are very important to model software architecture. Requirements are divided into functional and quality requirements. Functional requirements are pinpointed subsystems and components. Quality requirements affect the structure of architecture. Thus requirements are essential to understand clearly in order to design software architecture. This paper focuses on a quantitative approach to requirements analysis for modeling architectures. In our proposal, functional requirements are quantified through calculating each priority of components. Quality requirements are quantified through calculating the correlation degree between components and quality attributes. The proposed method is implemented by DRAMA (Domain Requirements Analysis for Modeling Architectures), which fully supports our approach and are developed in Java environments. Our proposal is validated to apply some industrial examples.

• Journal of KIISE:Software and Applications
• /
• v.33 no.7
• /
• pp.615-623
• /
• 2006

A non-functional requirement is a property or quality that the proposed systems have to support the functional requirements. A non-functional requirement is reflected by quality attribute These non-functional requirements playa crucial role during system development, serving as selection criteria for choosing among decisions. It should be continuously considered through the software development process. In spite of the importance of the non-functional requirements, it received little attention because of ambiguousness and invisibility of non-functional requirements. Therefore non-functional model which is a process to analyze the non-functional requirement is proposed for improving the management efficiency of non-functional requirements. Also, this paper presents the trace among the UML diagrams to the conceptual model. According to the non-functional requirement development process, this paper achieved performance-based case study. After then, non-functional requirement should be traced using the UML diagrams.

• Journal of Navigation and Port Research
• /
• v.43 no.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.

• Journal of the Korea Society of Computer and Information
• /
• v.24 no.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
• /
• v.2 no.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.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.11 no.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
• /
• v.15 no.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.