• The KIPS Transactions:PartB
• /
• v.17B no.3
• /
• pp.255-262
• /
• 2010

When a system is developed, requirements document is generated by requirement analysts and then translated to formal specifications by specifiers. If a formal specification can be generated automatically from a natural language requirements document, system development cost and system fault from experts' misunderstanding will be decreased. A pronoun can be classified in personal and demonstrative pronoun. In the characteristics of requirements document, the personal pronouns are almost not occurred, so we focused on the decision of antecedent for a demonstrative pronoun. For the higher accuracy in analysis of requirements document automatically, finding antecedent of demonstrative pronoun is very important for elicitation of formal requirements automatically from natural language requirements document via natural language processing. The final goal of this research is to automatically generate formal specifications from natural language requirements document. For this, this paper, based on previous research [3], proposes an anaphora resolution system to decide antecedent of pronoun using natural language processing from natural language requirements document in Korean. This paper proposes heuristic rules for the system implementation. By experiments, we got 92.45%, 69.98% as recall and precision respectively with ten requirements documents.

• 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 Internet Computing and Services
• /
• v.17 no.5
• /
• pp.25-32
• /
• 2016

There has been a rapid growth in the development of mobile application resulting from its wide usage for online transaction, data storage and exchange of information. However, an important issue that has been overlooked is the lack of emphasis on the security issues at the early stage of the development. In fact, security issues have been kept until the later stage of the implementation of mobile apps. Requirements engineers frequently ignore and incorrectly elicit security related requirements at the early stage of mobile application development. This scenario has led to the failure of developing secure and safe mobile application based on the needs of the users. As such, this paper intends to provide further understanding of the real challenges in extracting security attributes for mobile application faced by novice requirements engineers. For this purpose, two experiments on eliciting security attributes requirements of textual requirements scenario were conducted. The performance related to the correctness and time taken to elicit the security attributes were measured and recorded. It was found that the process of eliciting correct security attributes for mobile application requires effort, knowledge and skills. The findings indicate that an automated tool for correct elicitation security attributes requirement could help to overcome the challenges in eliciting security attributes requirements, especially among novice requirements engineers.

• Journal of the Korean Society of Systems Engineering
• /
• v.5 no.2
• /
• pp.17-26
• /
• 2009

This paper is about that case study of the Tube Transportation System that the new transportation system offering passenger and logistic service in a metropolis having plenty of the floating population or between medium-sized cities, and solving large issues like terrible traffic jams and environmental problems etc. in this region. Also it presented that elicitation results of performance parameter and the categorization system of it applying a systematic analysis methodology. By the medium of this paper, It showed that definition, case study, performance parameters, and the categorization system of parameters of a general tube transportation system before developing requirements of a specific tube transportation system. From now on, it will come in pretty handy in systems engineering of activities to establish a concept of a new tube transportation systems and develop requirements.

• Journal of Information Technology Services
• /
• v.13 no.4
• /
• pp.397-410
• /
• 2014

For mobile service organizations, it is one of the most important tasks to reflect users' opinions rapidly and accurately. In this study, the process is defined to elicit requirements of software/system improvement for mobile application by extracting and refining from users' opinion in mobile app, and detailed activities procession method in this processing are also proposed. The process consists of 3 activities to get requirements of software/system improvement for mobile app. First activity is to transform mobile app to software structure and define term dictionary. Second activity is to elicit simple sentences based on software from users' opinion and refine them. The last activity is to integrate and adjust refined requirements. To verify the usability and validity of the proposed process and the methods, the outputs of manual processing and semi-automated processing were compared. As a result, efficiency and improvement possibility of the process were confirmed through extraction ratio of requirements, comparison of execution time, and analysis of agreement ratio.

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

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.198-202
• /
• 2020

User review sites are spaces where users can freely post and share their opinions, which are trusted by many people and directly influence sales. In addition, they overcome the limitations arising from existing requirements collection and are able to gather the needs of large numbers of different people at a low cost. Therefore, such sites are attracting attention as new spaces for understanding user needs. In a previous study, a user review analysis was attempted using 5W and 1H, and we inferred that a sentence containing "when" has special information based on the user experience. In addition, the requirements of the derivative activities in a user review can identify more user needs than the general requirements of derivative activities. In this paper, we propose a systematic method of deriving "when" sentences contain meaningful information from user reviews and converting them into use cases, which is one of the requirements of a specification method. This method converts unstructured data into structured data such that it can be included as the user requirements during software development from user comments expressed in natural language. This method will reduce project failures and increase the likelihood of success by enabling an efficient collection and analysis of user needs from valuable user reviews.

• Proceedings of the Korean Information Science Society Conference
• /
• 2010.06a
• /
• pp.80-81
• /
• 2010

• 시스템엔지니어링워크숍
• /
• s.1
• /
• pp.21-26
• /
• 2003

시스템엔지니어링을 수행하는데 있어서 요구사항의 중요성은 아무리 강조해도 지나치지 않을 것이다. 요구사항들의 명확한 정의는 개발문제의 명확한 정의를 의미하면 이는 개발사업의 위험부담을 초기에 제거하는 중요한 역할이 된다. 시스템 개발에 있어서 성패를 가름 지을 수 있는 첫 관문인 요구사항의 추출 방법들을 식별하고 비교 분석하였다. 본 논문에서는 요구사항 추출을 위한 방법들을 간략히 소개하고 각 방법의 장점과 단점을 기술하였으며, 각 방법의 학습난이도, 적용할 이해당사자의 특성별로 정리하였다.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.6 no.11
• /
• pp.2813-2826
• /
• 2012

Various stakeholders are involved in the creation of software projects. In general, the higher the number of stakeholders involved during the requirements elicitation phase, the better are the chances of success for the project. However, it is rather difficult to consider the opinion of all the stakeholders owing to constraints on time and resources. Furthermore, conflicts between stakeholders can become inevitable when the number of stakeholders increases. Thus, the identification of key stakeholders is an important factor in ensuring the success of a project. In this paper, a methodical stakeholder conflict resolution model (s-CRM) is proposed by considering an actual industrial case study. The proposed model uses information gain based on entropy when measuring the impurity of information. We believe that the proposed s-CRM is effective in identifying the key stakeholders and in intuitively indicating those stakeholders whose elicited requirements need to be weighted. In addition, the model provides a solution for conflicts among stakeholders during requirements engineering.