• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.13 no.9
• /
• pp.4207-4213
• /
• 2012

Software quality is strongly associated with requirement quality. Accordingly, companies are trying effect for enhancing requirement quality. But, it is difficult to verify the requirement of specification format, which have to rely on abnormal business knowledge of analyst. Also, it is insufficient to normal methodology or automated technique for enhancing requirement quality of specification format. In this paper, we propose the process of requirement verification and automated verification tool for enhancing requirement quality. we compare the external view design and internal view design for verifying requirement. In the case study, we evaluate the feasibility of the proposed automated verification technique of requirement.

• 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 KIISE:Software and Applications
• /
• v.37 no.3
• /
• pp.161-169
• /
• 2010

The requirement elicitation is the task of eliciting requirements from needs of stakeholders, and preparing for information for negotiation. However, there are methods for gathering needs, but there is no specific method for classifying them, generating information for negotiation. Therefore, To solve the problems, this paper proposes a method to classify requirement and to generate information for negotiation. The proposed methods use Kano model, statistical technique, and identifying relationship between requirements and problems within scope. Finally, we validate the proposed method on simulations, Rough Set Theory, and case study of model.

• Journal of Aerospace System Engineering
• /
• v.11 no.2
• /
• pp.1-8
• /
• 2017

Delivering clear requirements of the military in the defense acquisition process is a key activity for successful weapon acquisition. In the field of defense, Operational Requirements Documents (ORDs) are prepared to derive and deliver the requirements of the military. In this study, we compare and analyze the form and content of the recent domestic ORD with reference to the US Department of Defense (DoD) ORD. As a result of the study, it is found that the domestic ORD form needs to be supplemented with in accordance with the purpose of the operation, while the requirement parameter, which is a core item of ORD, is insufficient. In order to address these issues, detailed contents of the ORD form suitable for the purpose of this study are presented. Also, we provide clear definitions, explanations, and examples of the operational system's key performance parameters and suggest ways to clearly communicate the requirements of the military.

• Journal of KIISE:Software and Applications
• /
• v.31 no.5
• /
• pp.543-554
• /
• 2004

In Requirements engineering, requirements elicitation and analysis are very important tasks to develop software systems successfully. Even though various methods have been proposed including scenario-based analysis, goal based analysis, and coupling goal with scenario, each method has its own strengths and weaknesses. If you use only one method, it is very difficult to elicit and to analyze system requirements completely. Since these methods don't support a comprehensive elicitation process, this paper proposes an integrated approach. This integrated approach is focused on two viewpoints. One is what factors are comprised and the other is how they are integrated. This paper also shows how the proposed approach can be applied to Meeting Reservation System (MRS) development. An experiment has been conducted using this approach to demonstrate how complete requirements are elicited and analyzed and to show relative time savings during elicitation in comparison to each method.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.3
• /
• pp.99-109
• /
• 2021

In recent machine learning studies, in order to consider the quality and completeness of data, derivation of non-functional requirements for data has been proposed from the viewpoint of requirements engineering. In particular, requirements engineers have defined data requirements in machine learning. In this study, data requirements were derived at the data acquisition (DAQ) stage, where data is collected and stored before data preprocessing. Through this, it is possible to express the requirements of all data required in the existing DAQ system, the presence of tasks (functions) satisfying them, and the relationship between the requirements and functions. In addition, it is possible to elicit requirements and to define the relationship, so that a software design document can be produced, and a systematic approach and direction can be established in terms of software design and maintenance. This research using existing DAQ system cases, scenarios and use cases for requirements engineering approach are created, and data requirements for each case are extracted based on them, and the relationship between requirements, functions, and goals is illustrated through goal modeling. Through the research results, it was possible to extract the non-functional requirements of the system, especially the data requirements, from the DAQ system using requirements engineering.

• Journal of Advanced Navigation Technology
• /
• v.12 no.5
• /
• pp.509-515
• /
• 2008

The requirement analysis which is clear essential important matter of the software development which is successful about demand of the user. Influences big in the software configuration which will be developed. With the development where existing the many softwares the Internet are sudden changed together in web base Web Application, complicated termination the demand of the user increases and many expense and manpower are becoming disturbance in development. However, So far Web Application about the justice of the development environment which is accurate is not becoming well. There is to development and stands but does not reflect the requirement of the user not to be able, the user became freely plan of the function which approaches information with difficult. This paper, Amended a software requirement analysis process, analyzed the method will be able to identify proposed a requirement.

• The KIPS Transactions:PartD
• /
• v.13D no.7 s.110
• /
• pp.909-922
• /
• 2006

The core assets include all properties which consist of an application in Product Line Engineering. The requirement, one of the core assets, is a basis of other core assets and commonality and variability of other core assets are classified by the requirement. accordingly, commonality and variability of the domain requirement should be managed objectively and it is necessary to make a process to reuse the domain requirements. However the requirement is analyzed by domain experts or developers without proper process. In this paper, we proposed the 4 activities: (1)the domain scoping, (2)the extraction and generalization of the domain requirement, (3)the domain requirement analyzing and modeling, (4)the change management, and sub activities. For all reasons given previously, it is possible to reduce the development time and cost by reusing the architectures and components related to the domain requirement. In addition, it is possible to increase the quality of the artifacts produced based on the requirements by managing them systematically.

• Journal of the Korean Society for Library and Information Science
• /
• v.39 no.3
• /
• pp.75-91
• /
• 2005

The popularization of the internet has produced an explosion in amount of the information. The importance of web personalization is being more and more increased. The personalization is realized by learning user's interest. User's interest is changing continuously and rapidly. We use user's profile to represent user's interest. User's profile is updated to reflect the change of user's interest. In this paper we present an adaptive learning algorithm that can be used to reflect user's interest that is changing with time. We propose the User's profile model. With this profile user's interest is learned based on user's feedback. This approach has applied to develop hybrid recommendation system.

• Korean Journal of Logic
• /
• v.19 no.2
• /
• pp.185-232
• /
• 2016

In order to explain why begging the question is a fallacy, some of the challenges must be met. First we need to understand what begging the question is in subtle ways. In addition, it is necessary to reflect on the nature and the purpose of arguments in order to explain why begging the question is a fallacy. In this paper, I first have a general proposal about the main purpose of arguments. Then I place my own multi-layered theory of begging the question proposed in a previous study in the context of the proposals in this paper for the main purpose of arguments. Moreover, I develop a more comprehensive theory of why begging the question is a fallacy. Finally, I examine and criticize the main previous theories of begging the question, such as Frank Jackson's theory, Douglas Walton's theory, David Sanford's theory, John Biro's theory.