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

• Archives of design research
• /
• v.12 no.1
• /
• pp.63-72
• /
• 1999

Customer needs are considered as being quite remarkable in product design. The elaborate fulfillment of them in the design solution is closely related to the success of a product. They, however, are generally collected and presented by marketers. Consequently those needs are difficult for designers to understand and therefore might not get fulfilled in the final product design. Here the goal of this study is set that the process of design information elicitation based on customer needs is developed as a guideline of utilizing them in design activity in effective manners. findings of this study can be summarized as follows: First, customer needs are expected to get interpreted into the designer-oriented language in the aspect of function and image of a product. Those interpreted needs play a role as a base for concept establishment and the development of it with the help of various techniques from the fold of statistics and systematic product development. Second, designer-oriented manner of understanding customer needs requires designers to take parts in from collecting to interpreting them for better design solution that fulfills them, which brings up a necessity that available techniques shouldn't be beyond understanding of designers and for the styling activity customer needs of image aspect should be interpreted and presented visually. In this study, those visual information is presented through the image maps and image information sheet. It is image information sheet that is suggested to contain visual and verbal information altogether such as the overall and major elements images expressing a specific image need and the correlation between them showing how much the elements image contributes to building the overall image.

• Proceedings of the Korea Society of Design Studies Conference
• /
• 1998.10a
• /
• pp.24-25
• /
• 1998

• IE interfaces
• /
• v.17 no.3
• /
• pp.261-268
• /
• 2004

The primary goal of the requirement analysis phase during information system development is to identify and document what is really needed, in a form that clearly communicates to the user and to development team members. Presented in this paper is a QFD(Quality Function Deployment)-based requirement analysis method and procedure for developing a large-scale enterprise information system. For the purpose of elicitation of software functional requirements, this paper adopts the method of HOQ(House Of Quality) and proposes a simplified HOQ which is more suitable for the software requirement analysis. As a result of this paper, it suggests desired functionalities for an integrated design &manufacturing information system.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2012.06b
• /
• pp.229-231
• /
• 2012

일반적으로 현업에서 통합테스트 시나리오를 작성하는 개발자는 개발 단계의 이슈와 그들만의 요구사항을 테스트시나리오에 포함하는 경향이 있다. 즉 설계 단계에서 중요시 되던 사용자 요구 사항이나 우회 흐름과 같은 이슈들은 빠지기 쉽다. 이번 연구에서는 통합 테스트 시나리오 작성시 상태전이기법과 같은 테스트 설계 기법을 사용하여 개발자가 빠뜨리기 쉬운 설계 단계에서의 사용자 요구 사항과 같은 항목들이 고려되는 통합 테스트 시나리오를 도출하는 방법을 제시하였다. 이 방법을 활용한 결과 생각하지 못했던 테스트 케이스와 테스트 시나리오를 도출 할 수 있었고, 이로 인해 높은 만족도를 얻을 수 있었다.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2001.01a
• /
• pp.448-455
• /
• 2001

Recently, many enterprises have attempted to capitalize knowledge assets on data warehouse (DW). It has been recognized as strategic core process to create corporate competitive advantage and implement enterprise e-biz strategies. However, most approaches to represent knowledge and decision process have limits in considering various knowledge types, their relationships and continuity in knowledge formulation. In addition, they are so inclined to one side such as concept-oriented frameworks or technology-oriented ones. They lack universal and wide-ranging features. This paper presents a comprehensive methodology to accumulate knowledge capital on DW via a properly grained hypermedia model. The methodology consists of three phases: knowledge requirement elicitation, hypermedia modeling, and system implementation. A real-life case for medical DW development is presented to demonstrate the usefulness of the proposed methodology. This methodology is effective when an organization accumulates knowledge assets to put the corporate e-biz or cre-biz strategy into practice.

• Journal of the Society of Disaster Information
• /
• v.15 no.4
• /
• pp.493-501
• /
• 2019

Purpose: The purpose of this study is to prevent construction safety accidents, and the design safety systems were reviewed. This paper aims to establish as an effective system by looking at the implementation procedures and contents of the design safety review system. Method: We reviewed the purpose and content of the law, accident statistics, etc. for the study. In addition, we looked at the implementation plans for actual construction sites using the 'design safety' assessment process as defined by the Act. Results: We divided it into the data review phase, the risk factor elicitation and alternative setup phase, and the design safety assessment report preparation stage. Conclusion: it is necessary to derive risk factors that take into account the diversity of construction sites. However, the effectiveness of other reports is questioned as they are often copied and written. Therefore, it is necessary to strengthen external verification procedures attended by construction safety experts.

• Journal of KIISE:Computing Practices and Letters
• /
• v.15 no.3
• /
• pp.167-177
• /
• 2009

This paper is about our experience of developing a context-aware exhibit guide system called MyGuide by applying Simtext development methodology. In particular, we introduce some issues to be considered in development process, the way that we solved them, and other things related to context. In requirements elicitation phase, we reduced the complexity of requirements by separating business logic requirements and context-awareness related requirements. After that, we modeled context, and designed software architecture, classes, and database in sequence during design phase. We considered system requirements and context modeling issues for context modeling because it influences class and database design.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.10
• /
• pp.3075-3085
• /
• 2000

According to distributed, large-caled environment of software development and operation, the elicitation and specivication of correct and complete requrement is the most important factor for the system. In addition contiuous and dramatic systerm canging requests in cooperative environment with internet require more efficient, requirement management. In this paper we detine the specification architecture and techruques for requrements, so that we improve the efficiency ofnatural language-based requirement speciticationand management in a cooperatie work environment. Also, we propose a software requirement engineering process model and environment based on requirements in a CSC@(Computer Supported Cjooperative Work) environment, therefore transfer them into analysis phase.