• 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 Internet of Things and Convergence
• /
• v.9 no.6
• /
• pp.45-50
• /
• 2023

In software development, the elicitation and analysis of requirements is a crucial phase, and it involves considerable time and effort due to the involvement of various stakeholders. ChatGPT, having been trained on a diverse array of documents, is a large language model that possesses not only the ability to generate code and perform debugging but also the capability to be utilized in the domain of software analysis and design. This paper proposes a method of requirements engineering that leverages ChatGPT's capabilities for eliciting software requirements, analyzing them to align with system goals, and documenting them in the form of use cases. In software requirements engineering, it suggests that stakeholders, analysts, and ChatGPT should engage in a collaborative model. The process should involve using the outputs of ChatGPT as initial requirements, which are then reviewed and augmented by analysts and stakeholders. As ChatGPT's capability improves, it is anticipated that the accuracy of requirements elicitation and analysis will increase, leading to time and cost savings in the field of software requirements engineering.

• Journal of the Korean Society of Systems Engineering
• /
• v.2 no.1
• /
• pp.11-17
• /
• 2006

According to the change of customer needs, integration with other systems, and the advent of new technology, it is inevitable for the existing system requirements to be requested to redesign. However, there are actually no methodologies and processes to be able to reorganize the existing requirements or integrate a number of requirements different from each other. The traditional requirements processes do not work when solving such problems. Thus, since the existing approaches to develop requirements are not helpful, many traditional requirement engineering processes can not help falling in Red Ocean. In this paper, in order to solve such the problems, we propose a novel requirements engineering process applying Blue ocean strategy which is used to open a non-competition market not discovered yet. Blue Ocean approach is a novel effective method to elicit and build up new requirements from customers. In order to accomplish the strategy, this paper presents a framework and processes to discover new perspectives and analyze the corresponding requirements. In addition, some pieces of case study are presented to introduce how our approach is applied to practical system developments and the evaluation analysis for how valid it is.

• The Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

The requirements have been changed during development progresses, since it is impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software's structure and behavior, or they cannot discover all parts affected by a change. Requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense and contribute to the business needs of the customer organization. We propose a feature-oriented requirements change management method to manage requirements change with value analysis and feature-oriented traceability links including intermediate catalysis using features. Our approach offers two contributions to the study of requirements change: (1) We define requirements change tree to make user requirements change request generalize by feature level. (2) We provide overall process such as change request normalization, change impact analysis, solution dealing with change request, change request implementation, change request evaluation. In addition, we especially present the results of a case study which is carried out in asset management portal system in details.

• Journal of KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.120-133
• /
• 2000

Major obstruction of using formal methods for hybrid real-time systems in industry is the difficulty that engineers have in understanding and applying the quantitative methods in an abstract requirements phase. While formal methods technology in safety-critical systems can help increase confidence of software, difficulty and complexity in using them can cause another hazard. In order to overcome this obstruction, we propose a framework for qualitative requirements engineering of the hybrid real-time systems. It consists of a qualitative method for requirements specification, called QFM (Qualitative Formal Method), and a safety analysis method for the requirements based on a causality information, called CRSA (Causal Requirements Safety Analysis). QFM emphasizes the idea of a causal and qualitative reasoning in formal methods to reduce the cognitive burden of designers when specifying and validating the software requirements of hybrid safety systems. CRSA can evaluate the logical contribution of the software elements to the physical hazard of systems by utilizing the causality information that is kept during specification by QFM. Using the Shutdown System 2 of Wolsong nuclear power plants as a realistic example, we demonstrate the effectiveness of our approach.

• Journal of the Korea Safety Management & Science
• /
• v.6 no.2
• /
• pp.199-209
• /
• 2004

Kano(1984) distinguishes five types of Quality requirement which influence customer satisfaction; Attractive, One-dimensional, Must-be, Indifferent, Reverse Quality element. Attractive requirements lead more than proportional satisfaction. Attractive Quality requirements are the key factors of order winner and the sources of customer delight. Attractive requirements do not influence customer satisfaction equally. This study presents Kano's model using AHP(Analysis Hierarchy Process) for the priorities of attractive Quality requirements.

• Journal of Korea Multimedia Society
• /
• v.21 no.6
• /
• pp.685-697
• /
• 2018

(Most companies that perform BPR have not achieved satisfactory results or have not performed successful BPRs. There are many reasons for this, but the most important one has caused problems that do not accurately reflect the requirements of various stakeholders. In this paper, we will apply the BPR consulting methodology to a new value innovation requirements engineering process based on the Blue Ocean strategy, which is a way to create a new market without competition by customerizing potential customers by satisfying new customer expectations and needs. This paper uses a requirements engineering process that can generate customer value by applying the ERRC(Erasure Reduce Raise Create) analysis method, which is the core of the Blue Ocean Strategy Framework[1,2]. We will also apply the Six Sigma DFSS (Design For Six Sigma) methodology to improve quality and process through quantitative and systematic analysis. The proposed approach was presented to the BPR consulting to present a practical case, and the results of the empirical analysis of the system user to validate the results of BPR consulting.

• Proceedings of the KSR Conference
• /
• 2001.10a
• /
• pp.35.1-40
• /
• 2001

This study is on the behavior analysis which can define and verify a system requirement through a behavior diagram for High speed rail system. The model considered in this study is limited to the preconditioning control of the control system specification for HSRS. To build an executable model, requirements should be decomposed first into leaf node requirements. The behavior model is composed of input, output, and functions which are linked with leaf node requirements. It is important that a single requirement must specify a single Auction. Using the developed executable model and the traceability between requirements and functions, this study found out a lot of static and dynamic inconsistency, missed and derived requirements. This is to develop and executable behavior model to do functional analysis and be able to verify the integrity of a specification.

• Journal of KIISE:Software and Applications
• /
• v.27 no.4
• /
• pp.384-392
• /
• 2000

As a software becomes more complicated and large-scaled, it is very important for a software engineer to analyze user's requirements precisely and apply them effectively in the development stage. Due to the growth of the internet, the necessity of requirements elicitation and analysis in distributed environments has also become larger. This paper proposes a requirements elicitation supporting system that offer the basis for effectively analyzing requirements collected in distributed environments. The proposed system automatically categorizes collected requirements sentences into selected subject fields by measuring their similarity using a similarity measurement technique. Therefore, it reduces the difficulties in the initial stage of requirements analysis and it supports rapid and correct requirements analysis. This paper verifies the efficiency of the proposed system in similarity measurement techniques through experiments, and presents a process for requirements specifications elicitation using the embodied system

• IE interfaces
• /
• v.17 no.3
• /
• pp.261-268
• /
• 2004

The primary goal of the requirement analysis phase during information system development is to identify and document what is really needed, in a form that clearly communicates to the user and to development team members. Presented in this paper is a QFD(Quality Function Deployment)-based requirement analysis method and procedure for developing a large-scale enterprise information system. For the purpose of elicitation of software functional requirements, this paper adopts the method of HOQ(House Of Quality) and proposes a simplified HOQ which is more suitable for the software requirement analysis. As a result of this paper, it suggests desired functionalities for an integrated design &manufacturing information system.