• 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 Information Processing Systems
• /
• v.6 no.3
• /
• pp.385-402
• /
• 2010

Most of the data warehouse (DW) requirements engineering approaches have not distinguished the early requirements engineering phase from the late requirements engineering phase. There are very few approaches seen in the literature that explicitly model the early & late requirements for a DW. In this paper, we propose an AGDI (Agent-Goal-Decision-Information) model to support the early and late requirements for the development of DWs. Here, the notion of agent refers to the stakeholders of the organization and the dependency among agents refers to the dependencies among stakeholders for fulfilling their organizational goals. The proposed AGDI model also supports three interrelated modeling activities namely, organization modeling, decision modeling and information modeling. Here, early requirements are modeled by performing organization modeling and decision modeling activities, whereas late requirements are modeled by performing information modeling activities. The proposed approach has been illustrated to capture the early and late requirements for the development of a university data warehouse exemplifying our model's ability of supporting its decisional goals by providing decisional information.

• Korean Journal of Construction Engineering and Management
• /
• v.21 no.6
• /
• pp.3-15
• /
• 2020

For a successful construction project, the requirements of the client should be clearly defined and this should be reflected in the project based on the expertise of each project participant throughout the entire life-cycle. Therefore, it is necessary to establish the concept of Requirements Management to systematize and manage project requirements in terms of information management. This study aims to comprehensively define the concept of requirements management in the architecture industry and to provide a methodological basis for efficiently managing design requirements information by suggesting category of requirements information type and information analysis criteria. In addition, based on the case study, the requirements information was analyzed to propose a systemization methods of requirements management for PMO' design management and information management.

• Journal of Information Science Theory and Practice
• /
• v.5 no.2
• /
• pp.17-32
• /
• 2017

We compared nanotechnology web portal requirements using a Kano method, to identify similarities and dissimilarities in Kano-categorizations of features and functions required of nanotechnology among users in universities, government research institutes, and industry. Based upon data obtained from 130 user members of the National Nanotechnology Policy Centre, this study analyzed assessed asymmetries in web users' feelings based on hypothesized provision and non-provision of web portal requirements. In doing this, this study utilized measures and procedures suggested in the literature such as the most frequent-response categorization, customer satisfaction (dissatisfaction) coefficient, category strength and total strength, and Fong test. This study found that overall, sectors were an important factor in explaining the relationships between web portal requirements and user satisfaction/expectations. When these requirements were classified, users' perceptions of information contents requirements were consistent across the sectors, but the other functional requirements including communication and collaborations considerably varied.

• Industrial Engineering and Management Systems
• /
• v.11 no.1
• /
• pp.70-81
• /
• 2012

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

• Journal of information and communication convergence engineering
• /
• v.10 no.3
• /
• pp.284-294
• /
• 2012

The quality of requirements is one of the key factors in the success of a project. One of the studies on successful projects is the reuse of requirements. However, the rate of failed projects is about 70%, and these projects often fail because of improper requirements. The current techniques for software reuse may not perform requirement engineering appropriately or develop requirements having good characteristics. In order to improve this situation, we propose a model for reusing requirements. We expect that our model will contribute toward increasing project productivity using requirement reuse in existing projects, and reusing requirements that have good quality.

• 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 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 Korea Multimedia Society
• /
• v.6 no.4
• /
• pp.723-735
• /
• 2003

This research focuses ell an approach for the building of a requirements model for the development of large-scale information systems. It will suggest a set of requirements engineering processes as a procedure of the implementation for building the requirements model. It will also emphasise the evaluation requirements model aimed to refine and complete the requirements model by the different user groups as a cross reference. This paper provides an advanced user-construction requirements within the Event Flow Diagram as a set of requirements engineering process.

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