• Journal of the Korean Society of Systems Engineering
• /
• v.6 no.2
• /
• pp.37-45
• /
• 2010

Requirements engineering is an important phase in a system's life cycle. It is important to perform it correctly. The increasing complexity of systems makes requirements engineering activities more difficult. Non-functional requirements are drivers to emerge how much emergent system properties to aim for success. All functional requirements may be satifsfied, but if the level of desired non-functional requirements are overlooked, the system development will fail. There is growing awareness of the importance of defining non-functional requirements early in the process among the requirements engineering (RE) community. This paper propses a SysML based approach for non-functional requirements to identify and specify very early in the process or requirements engineering.

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

• Proceedings of the KSR Conference
• /
• 2011.05a
• /
• pp.1591-1598
• /
• 2011

The objective of this paper is to study how to apply the functional models in the design reviews and the validation of the subsequent design specifications and standards in the urban rail transit standardization program. The functional models can be obtained based on the requirements. Specifically, the requirements are first represented by the use case and sequence diagrams and then the results are transformed into the functional models using the Systems Modeling Language (SysML) diagrams and the FFBD (Functional Flow Block Diagram) and others. Based on the results of the study, it can be checked whether the original requirements have been reflected properly in the designs. Also, it can be seen that how the possible changes in the requirements affect the functions and thus how the designs should be changed accordingly.

• International Journal of Knowledge Content Development & Technology
• /
• v.10 no.1
• /
• pp.7-20
• /
• 2020

For research data to be shared without legal, financial and technical barriers in the Open Science era, data repositories must have the functional requirements asked by DMP and CoreTrustSeal. In order to derive functional requirements for the data repository, this study analyzed the Data Management Plan (DMP) and CoreTrustSeal, the criteria for certification of research data repositories. Deposit, Ethics, License, Discovery, Identification, Reuse, Security, Preservation, Accessibility, Availability, and (Meta) Data Quality, commonly required by DMP and CoreTrustSeal, were derived as functional requirements that should be implemented first in implementing data repositories. Confidentiality, Integrity, Reliability, Archiving, Technical Infrastructure, Documented Storage Procedure, Organizational Infrastructure, (Meta) Data Evaluation, and Policy functions were further derived from CoreTrustSeal. The functional requirements of the data repository derived from this study may be required as a key function when developing the repository. It is also believed that it could be used as a key item to introduce repository functions to researchers for depositing data.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.2 no.2
• /
• pp.52-60
• /
• 1999

By implementing the Systems Engineering process for the aircraft preliminary design, functional analysis study is performed, hence Functional Interface Data Flow(FIDF) and Functional Flow Block Diagram(FFBD) are generated. Based on FIDF and FFBD, allocable and non-allocable design/performance/RM＆S requirements are allocated to the appropriate levels. Weight and cost tracking and design margin management methodologies are studied and implemented for the balanced aircraft design.

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

• 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 the Korean Society for Aviation and Aeronautics
• /
• v.16 no.4
• /
• pp.41-48
• /
• 2008

Functional analysis of air transport mission is conducted to establish the performance requirements of the commercial transport designs. The analysis process begins by making a top-down analysis to the aircraft system level mission functions. Correctly interpreting the top-level performance requirements is the first step in designing and building an aircraft system. Each function and sub-function is allocated and examined to the aircraft level and flight operations phase to optimize the system performance and design requirements, such that these lower-level requirements can be traced back to the top-level requirements they are designed to fulfill. Special attention is given to making sure all interfaces, both internal and external, are addressed. The results are also in good resources of functional hazard assessment involved in certification processes.