• Journal of the Korea Society of Computer and Information
• /
• v.24 no.3
• /
• pp.95-104
• /
• 2019

Crowdsourcing is growing its interests in designing where various designers work independently to a given design task. Recent researchers discovered that collaboration by sharing designs among designers helps to produce high-quality designs. However, design task may still be hard even with that collaboration in case the requirements are not well-defined. Most customers sometimes do not know what they really want and do not know how to clearly define the requirements. Consequently, the lack of requirements creates issues on designers, such as spending much time and effort on collecting requirements alone or from the customers. The designers even end up missing important necessities to complete their tasks. To address this issue, we proposed a collaborative requirements elicitation method that supports designers who are working on the same task. We developed CREFD (Collaborative Requirements Elicitation For Designers and Developers) tool to enable designers collaboratively provide requirements, identify dependencies, add annotations and votes to the provided requirements. We performed the hypothetical and empirical evaluations to test and compare the proposed method with one of the existing elicitation methods, the results show that the proposed method helps in collecting accepted and well-organized requirements better than individual requirements elicitation.

• Journal of KIISE:Computer Systems and Theory
• /
• v.35 no.8
• /
• pp.394-406
• /
• 2008

Even though context is the most important feature in context-aware systems, the existing requirements engineering cannot support methodology for elicitation and specification of contexts. In this paper, we propose a requirements elicitation method and a requirements specification method for context-aware systems. Our requirements elicitation method is a 6-stepped, incremental, and iterative process. At the beginning steps in the process, we identify the requirements for business logic. Afterwards, we gather the requirements for context logic, model contexts, and identify subsystems. For requirements specification, we suggest a context-aware use case diagram, a context diagram for context modeling, and a context-type-use-case-dependency diagram for the traceability of use cases on the change of context types. We also introduce a case study that we apply our approaches to a real system, and a qualitative evaluation of our approaches. Our study will help stakeholders to efficiently elicit requirements for context-aware systems and to specify them clearly.

• Journal of KIISE:Software and Applications
• /
• v.33 no.8
• /
• pp.655-667
• /
• 2006

This paper proposes a method for counting function point using goal and scenario based requirements. Function Point is a software sizing method and widely used as a basis to estimate software development cost. Requirements elicitation and analysis should be performed before function point analysis but function point analysis method doesn't deal with requirements elicitation and analysis. For that reason, Function point extraction method from existing requirements method is needed and if the requirements method has advantage for traceability and elicitation, it is suitable for managing cost. Goal and scenario method is widely used as requirements elicitation and analysis. It has also good traceability. Therefore, this paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed methodology has been applied to Order Processing System development.

• 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

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.5 no.10
• /
• pp.1733-1750
• /
• 2011

In the early stages of a software project, it is critical to understand the needs of the customers and elicit their customer requirements. Various requirements elicitation methods have been proposed. However, existing methods still have the limitations such as a limited number of target customers, limited expression of customers' opinions, and difficulty in collecting the customers' opinions continuously. A novel method for eliciting customer requirements is proposed by utilizing a social network service (SNS), which is a shared source of raw information of the customers' needs and opinions. The proposed method is validated to show its effectiveness in overcoming the limitations of existing methods.

• 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.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 KIISE
• /
• v.44 no.1
• /
• pp.27-35
• /
• 2017

Many studies have addressed 'Adaptive User Interface (AUI)', wherein the user interface changes in accordance with the situation and the environment of each user at runtime. Nevertheless, previous papers for AUI barely reflected the viewpoints from requirements engineering field, since most of them focused on proposing the architecture and design. In this study, we outline AUI with the perspective of requirements engineering and propose the requirements elicitation and specification method based on concepts which have been researched in the area of self-adaptive system. Step by step, we first redefine and reinterpret the well-known concepts of self-adaptive software, after which the AUI requirements are elicited and specified. Finally, we illustrate a case study, which demonstrates the effectiveness of our method.

• International Journal of Computer Science & Network Security
• /
• v.23 no.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.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.12
• /
• pp.1259-1263
• /
• 2010

SaaS is an emerging paradigm for software development and deployment, expected to able to reduce cost. SaaS is also considered as a crucial technology for implementation of cutting-edge technology, such as distributed computing, green computing, and cloud computing. SaaS is requested to be configurable software to satisfy various customers, therefore it is very important to consider every configurability requirement during requirement elicitation. Our research suggests a classification technique to secure completeness of configuration requirement.