• Journal of the Korean Society of Systems Engineering
• /
• v.7 no.2
• /
• pp.39-43
• /
• 2011

Modern naval ships are large complex systems with the number of requirements ranges from thousands to tens of thousands. To build a quality ship, the satisfaction of the requirements should be traced. In most shipbuilding projects it is almost impossible to manage all the requirements without a proper CASE (computer aided systems engineering) tool. And for effective management of the shipbuilding project, the integrated database for technical data is very important. This paper describes how the requirements are managed, and the integrated database is built in the naval shipbuilding industry in Korea.

• 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 the Korean Society of Systems Engineering
• /
• v.18 no.2
• /
• pp.50-57
• /
• 2022

Along with the development of the 4^th Industrial Revolution technology, artificial intelligence technology is also being used in the field of systems engineering. This study analyzed the development status of artificial intelligence technology in the areas of systems engineering core processes such as stakeholder needs and requirements definition, system requirement analysis, and system architecture definition, and presented future technology development directions. In the definition of stakeholder needs and requirements, technology development is underway to compensate for the shortcomings of the existing requirement extraction methods. In the field of system requirement analysis, technology for automatically checking errors in individual requirements and technology for analyzing categories of requirements are being developed. In the field of system architecture definition, a technology for automatically generating architectures for each system sector based on requirements is being developed. In this study, these contents were summarized and future development directions were presented.

• Nuclear Engineering and Technology
• /
• v.56 no.8
• /
• pp.3286-3297
• /
• 2024

Traditional text-based system engineering, which has been used in the design and application of passive residual heat removal system (PRHRS) for lead-cooled fast reactors, is prone to several problems such as low development efficiency, long iteration cycles, and model ambiguity. This study aims to effectively address the abovementioned problems by adopting a model-based system engineering (MBSE) method, which has been preliminarily applied to meet the design requirements of a PRHRS. The design process has been implemented based on the preliminary design of the system architecture and consists of three stages: top-level requirement analysis, functional requirements analysis, and design requirements synthesis. The results of the top-level requirements analysis and the corresponding use case diagram can determine the requirements, top-level use cases, and scenario flow of the system. During the functional requirements analysis, the sequence, activity, and state machine diagrams are used to develop the system function model and provide early confirmation. By comparing these sequence diagrams, the requirements for omissions and inconsistencies can be effectively checked. In the design requirements synthesis stage, the Analytic Hierarchy Process is used to conduct preliminary trade-off calculations on the system architecture, after which a white box model is established during the system architecture design. Through these two steps, the analysis and design of the system architecture are ultimately achieved. The resulting system architecture ensures the consistency of the design requirements. Ultimately, a functional hazard analysis was conducted for a specific incident to validate case requirements and further refine the system architecture. Future research can further reduce the design risk, improve the design efficiency, and provide a practical reference for the design and optimization of PRHRS in digital lead-cooled fast reactors.

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

• International Journal of Knowledge Content Development & Technology
• /
• v.9 no.4
• /
• pp.95-114
• /
• 2019

The digitization of traditional medical knowledge in Tanzania will greatly enhance its preservation and dissemination. This is especially important given the challenges facing the current methods of preserving and managing such knowledge. This study presents the requirements engineering approaches and requirements for a web-mobile application that would successfully digitize indigenous knowledge of phytomedicine and relevant practitioners licensing and registration processes. To establish the requirements of such a digital system application, the study sought the opinion of 224 stakeholders whose suggestions were used to analyze and model the requirements for designing such a web-mobile tool. The study was carried out in Arusha, Kagera and Dar es Salaam regions of Tanzania which involved ethnobotanical researchers, herb practitioners, curators from herbaria and registrar officers from Traditional and Alternatives Health Practice Council. Structured interview, survey, observation and document review were employed to find out the basic functional and non-functional requirements for possible designing and implementation a web-mobile application that would digitize indigenous knowledge of medicinal plants. The requirements were modelled using the use case and context diagrams. Finally, the study came up with a list of items for both functional and non-functional requirements that can be used as guidelines to develop a web-mobile application that will capture and document traditional medical knowledge of medicinal plants in Tanzania and, enabling relevant authorities to regulate and manage stakeholders.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1164-1177
• /
• 2005

As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.

• 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 Ergonomics Society of Korea
• /
• v.12 no.2
• /
• pp.29-43
• /
• 1993

This paper presents a conceptual approach to convert customer requirements expressed in ordinary language into a form of qualitative and quantitative functions for developing new products. This approach attempts to combine the concepts of the value engineering and the Kansei engineering. It emphasizes that customer require- ments should be interpreted and reflected on the design of new product. Specific are discussed for extracting subjective requirements and transforming them into qualitative and quantitative functions for product design. This approach is expected to provide the product designer with a systematic efficient tool for incorporating subjective requirements into a product design.