Earticle

소비자를 파악하기 위해 활용되고 있는 사용자 중심 데이터 중 사용자 리뷰 데이터는 다량으로 상세하게 소비자 의 의견을 파악할 수 있다는 장점으로 인해 주목받고 있으며 많은 소비자들이 사용자 리뷰에 의존하고 신뢰하고 있다. 많 은 어플리케이션 개발사들은 중요성을 인지하고 사용자 리뷰를 관찰 및 대응하고 있지만 체계적인 방법의 부재로 고객의 만족과 관계없이 시간과 비용을 투자하고 있다. 따라서, 본 논문에서는 주어진 시간과 비용에서 고객의 만족을 최대화 시 킬 수 있도록 고객 만족과 서비스 품질을 다루는 카노 모델을 이용하여 어플리케이션 마켓에서 사용자 리뷰들을 선별하는 체계적인 방법을 제안하였다. 본 방법은 어플리케이션 마켓에서 사용자 리뷰들을 수집하고 요구사항을 도출하는 사용자 리 뷰 수집 및 요구사항 도출 단계, 도출된 요구사항에 카노 모델을 적용하고 품질 유형으로 선별하는 카노 모델 적용 및 선 별 단계, 그리고 관련자들이 모여 내부적인 측면에서 요구사항 검토 및 재정의하는 이해관계자들과 검토 및 재정의 단계로 구성되었다.

Among the customer-oriented data used to comprehend the customer, the user review data has received much attention as it provides insights into customer opinion in a detailed and large-scale manner; many customers have come to rely upon and trust the user reviews. Many application developers are cognizant of the importance of user reviews, so they monitor and respond to these reviews. However, due to the absence of a systematic method, developers have been investing their time and money without clear correlation to the customer satisfaction. Therefore, this paper suggests a systematic method to select user reviews from the application market using the Kano Model that deals with customer satisfaction and service quality, thereby maximizing the customer satisfaction under the given time period and budget. This method is constructed in the following phases: the user review collection and requirement elicitation phase in which the developers collect user reviews from the application market and elicit requirements, the Kano Model application and selection phase in which the Kano Model is applied to the elicited requirements and selection occurs based on the quality type, and the stakeholder review and redefinition phase in which relevant personnel gather to review and redefine requirements from an internal perspective.

소프트웨어 요구사항 분석은 성공적인 소프트웨어 프로젝트를 위해 필수적 요소이다. 특히 불완전한 요구사항 은 소프트웨어 프로젝트 실패의 가장 큰 원인으로 꼽힌다. 불완전한 요구사항은 소프트웨어 개발 시 개발자에게 이해 부족을 야기할 뿐 아니라, 소프트웨어 검증 시 에도 모호한 기준을 제공함으로써, 개발 후반부에 납기일 연기 및 비용 증가의 원인이 된다. 요구사항 패턴은 이러한 문제를 극복하는데 도움을 줄 수 있다. 요구사항 패턴은 요구사항 작성과 검토 시 참조모델이 될 뿐 아니라, 검증 기준이 될 수 있으며, 작성자가 누락한 부분을 보완해 줄 수 있다. 이와 더불 어 요구사항 작성의 경험이 적은 작성자는 요구사항 패턴을 통해 더 쉽고, 빠르고 정확하게 요구사항을 작성할 수 있 다. 본 논문에서는 다양한 요구사항의 시나리오를 통해 공통된 요구사항 시나리오를 추출하는 기법을 제안한다. 그리고 제안한 기법의 가시성 검증을 위해 여덟 개의 프로젝트에서 추출한 83개의 소프트웨어 시나리오를 통해 54개의 시나리 오 패턴을 추출하고 이 패턴을 이용하여 누락된 행위를 찾는 과정을 사례연구를 통해 보여준다.

Software requirement analysis is necessary for successful software development project. Specially, incomplete requirement is the most influential causes of software project failure. Incomplete requirement can bring late delay and over budget because of the misunderstanding and ambiguous criteria for project validation. Software requirement patterns can help writing more complete requirement. These can be a reference model and standards when author writing or validating software requirement. Furthermore, when a novice writes the software scenario, the requirement patterns can be one of the guideline. In this paper proposes an automatic approach to identifying software scenario patterns from various software scenarios. In this paper, we gathered 83 scenarios from eight industrial systems, and show how to extract 54 scenario patterns and how to find omitted action of the scenario using extracted patterns for the feasibility of the approach.

In the past years, the scale of software is growing quickly as more and more organizations begin to deploy their business on Internet. As a result, requirement analysis becomes a challenging issue and conventional approaches might significantly increase the costs of software development. Therefore, automatic requirement analysis techniques have attract more and more attentions, which allows for modeling and analyzing requirements formally, rapidly and automatically, avoiding mistakes made by misunderstanding between engineers and users, and saving lots of time and manpower. In this paper, we propose an approach to acquiring requirements automatically, which adopts automated planning techniques and machine learning methods to convert software requirement into an incomplete planning domain. By this approach, we design an algorithm called Intelligent Planning based Requirement Analysis (IPRA), to learn action models with uncertain effects. A concrete experiment is conducted to investigate the proposed algorithm, and the results indicate that it can obtain a complete planning domain and convert it into software requirement specification.

Software requirement prioritization aims at arriving at a prioritized list of requirements for further considerations during software development life cycle. In this research, we carry out a systematic review of literature to appreciate the different considerations that have influenced prioritization of software requirements, and examine some characterizations of requirement prioritization artifacts. Keyword based search is used on specific databases and conference proceedings in order to identify articles for systematic review. The results based on 96 full-text articles reveal internal and external considerations that have influenced prioritization of requirements, and reflect on certain artifact characteristics like the nature and type of the artifact. The results emphasize upon the heightened attention the domain of requirement prioritization has received in recent years. Future research opportunities are pointed out at the end, and are expected to stimulate research on the topic.

As software systems become increasingly large and complex, the need increases to predict and control the effects of software changes. Our research objective is to provide an impact analysis methodology that uses historical change record for executable and non executable files in a software system to identify and prioritize potentially affected area of a system modification based on risk. Software Change Impact Analysis captures the latest information on the science and art of determining what software parts affect each other. It provides ideas for doing impact analysis better, presents a framework for the field, and focuses attention on important results. To identifies key impact analysis definitions and themes and illustrates the important themes to give a solid understanding for tackling impact analysis problems specifically in ERP. It includes study on software source code dependency analysis and software traceability analysis and shows how results from both areas can more effectively support impact analysis in software engineering repositories.

In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn’t guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.

The delivery of new increments involves decision makings at various levels like decision aspect prioritization, requirement priorities and selections of regression test cases. The pressure to deliver high quality low cost software by employing limited resources and satisfying mass market invokes the need to have less dependence on regression testing activity. Earlier Proposed requirement prioritization technique categorizes the type of changes and the type of new implementations and then decides the neglection or minimization of test cases. Further minimizations are also possible due to existence of sound regression testing techniques. By focussing on common problems related to the development of mobile and embedded type software applications, one could have great improvement in software development quality and practices. The proposed requirement prioritization technique is applied in evolutionary mobile software application development and results were quite promising. This paper aims to have a deep insight into the ability of the proposed technique in minimization of regression testing of desktop software applications application. The results are very promising thus indicating the usefulness of proposal in low cost development of both mobile compatible and desktop software applications. The novel contribution of this paper lies in making the incremental development timely and low cost activity by making requirement prioritization effective and future increments less dependent on regression testing without having any compromise with the desktop software quality. This had been a result of analysis of proposed prioritization technique on desktop software application.

Software project management has emerged as a new discipline with wide-ranging ideas and across-the-board insights for effectively managing key areas of software projects. The remarkable work of the software project managers, professionals and researchers across the globe have resulted in substantial improvements in this field. Likewise, software project failure rate has decreased considerably due to the use of effective software project management tools and techniques by the software houses. Now more efficient, robust and quantitative measures are being practiced in the areas of software requirement gathering, analysis, design, architecture, development, quality assurance, integration, deployment and support. A number of metrics are used by the requirement engineers, system analysts, software engineers, team leads, software project managers and other professionals to successfully manage, execute and complete the software projects. As the software industry moves towards a more mature state, the need for employing more effective tools, techniques and benchmarks for managing software projects has become indispensable to minimize the negative risk factors and improved adherence to quality assurance. Particularly, requirement metrics are useful in identifying risks of a project by locating errors in the requirements document. These metrics validate the gathered requirements against the actual requirements by evaluating whether the requirements are complete or not. A range of metrics are used for measuring the requirements e.g., volatility metrics check changes in the requirements, traceability evaluates links among the requirements within a document and requirements completeness metrics verifies whether the specified requirements are complete or not. Multiple metrics are recommended to be used to assess the health of a software project to ensure overall quality as a single metric cannot suffice. In this paper, we explore how different metrics relating to different areas of software project, especially in requirement engineering, can be useful to manage the software projects for knowledgeably. The focus of this research study is to evaluate and highlight the importance of various performance metrics and propose additional metrics for requirement gathering and management.

Managing software changes and achieving an effective change acceptance decision is one of the crucial factors in ensuring the software project success. Accepting too many changes will cause expense and delay and rejecting the changes may cause customer dissatisfaction. One of the inputs that help in achieving an effective change acceptance decision is by having reliable estimation on the change effort. From software development perspective, the estimation has to take into account the inconsistent states of software artifacts across project lifecycle i.e., fully developed or partially developed. These inconsistent states require different ways of estimation such as the fully developed artifacts may have different calculation compared to the partially developed artifacts. Many change effort estimation approaches have been developed and one of them is using impact analysis. One main challenge of this technique from software development perspective is that this technique is specifically used for software maintenance phase in which all software artifacts have been completely developed. This research introduces a new change effort estimation approach that is able to use different estimation techniques for different states of software artifacts. The outcome of this research is a new change effort estimation approach for software development phase using the extended version of the static and dynamic analysis techniques from our previous works.

Context: Global Software Development (GSD) is the software development across the globe in which stakeholders are related to different countries and cultures, and they communicate each other by emails, fax, mobile, videoconferencing or any other communicating media. There are a lot of problems in implementing requirement engineering process for global software development. There is a need of requirement implementation model which guides us how to implement successfully requirement engineering in the context of GSD. Objective: To Find Critical Success factors (CSF) and challenges in requirement implementation in the context of GSD through Systematic literature Review (SLR), and to find the practices for the proper implementation CSF and challenges as proposed by Requirement Implementation Model (RIM). Method: - SLR is the methodology used to fulfill the objectives of this research. Expected Outcomes: - SLR protocol is developed for RIM. Expected output of this study is to list out all the factors and challenge which the stakeholders are facing in implementing requirement in the context of GSD through SLR.

이 논문은 실시간 소프트웨어의 요구 분석을 위한 구조이다. 이 방법은 실제 사용자들과의 쉬운 통신 수단으로 TNPN(Timed Numerical Petri Net)을 사용하는데, 시스템의 정확성을 위해서 RT시(Real Time Temporal Logic)에 기초한다. TNPT은 행위 명세언어로서 사용되며, 그 행위의 정당성은 RTTL로 표현되는데, 도달성 그래프를 통해 분석되었다. 그래서 사용자와 시스템의 두가지 요구사항이 모두 만족된다. 공유트랙 시스템의 예를 통하여 실시간의 성질(안전성, 응답성, 생존성, 우선순위)들이 검증되었다. 또한 이 구조는 자연스럽게 객체와 연결된다.

This paper is on the analysis for the real-time software requirement. This method can be used for TNPN(Timed Numerical Peri Net) as a easy communication means with real-users. It is based on the RTTL(Real Time Temporal Logic) for correctness the system. TNPN is used to represent a behavior specification language, the validity of specified behaviors in TNPN is expressed in RTTL, and analyzed through the teachability graph. Thus, the requirement between user and system is satisfied Using the example of shared track, the validity of the property of real-time(safetiness, responsiveness, liveness, priority) is verified. Also this framework if given to connection with a object, natually.

This paper describes what an operational change detection tool requires and the software which was designed and developed according to the requirements. The top requirement for the application of the software to operational change detection was identified: minimization of false detections, missing detections and operational cost. In order to meet such a requirement, the software was designed with the concept that the ultimate decision and isolation of changes must be performed manually by visual interpretation and all automatic algorithms and/or visualization techniques must be defined as support functions. In addition, the modular structure of the proposed software enables the addition of a new support function with the minimum development cost and minimum change of the operational environment.

본 연구원이 속한 연구실은 임베디드 소프트웨어 테스팅 프레임워크(이하 프레임워크)를 구축하고 있으며 임베디드 소프트웨어 요구사항 관리 도구(이하 REED)를 개발하였다. REED를 통해 작성된 요구사항은 프레임워크에서 테스트 케이스를 만들고 테스트를 수행하는 데 사용된다. 본 논문은 REED에서 기존에 개발된 요구사항 작성 및 분석 기능에 요구사항 관리 기능을 추가하는 개발에 관한 연구이다.

본 연구원이 속한 연구실은 임베디드 소프트웨어 테스팅 프레임워크(이하 프레임워크)를 구축하고 있으며 임베디드 소프트웨어 요구사항 관리 도구(이하 REED)를 개발하였다. REED를 통해 작성된 요구사항은 프레임워크에서 테스트 케이스를 만들고 테스트를 수행하는 데 사용된다. 본 논문은 REED에서 기존에 개발된 요구사항 작성 및 분석 기능에 요구사항 관리 기능을 추가하는 개발에 관한 연구이다.