Naoyasu Ubayashi, Yasutaka Kamei, M. Hirayama, T. Tamai
{"title":"A context analysis method for embedded systems — Exploring a requirement boundary between a system and its context","authors":"Naoyasu Ubayashi, Yasutaka Kamei, M. Hirayama, T. Tamai","doi":"10.1109/RE.2011.6051648","DOIUrl":"https://doi.org/10.1109/RE.2011.6051648","url":null,"abstract":"Many embedded systems not only affect their context through actuators but also are affected by the context through sensors. It is important to provide a context-dependent development method for constructing safe and reliable embedded systems. However, most of the current requirements analysis methods do not explicitly provide a systematic way for deciding the boundary of the context that should be taken into account because it is essentially difficult to decide which context element should be included as the targets of requirements analysis. If a developer explores the context boundary in an ad-hoc manner, he or she will be faced with the frame problem because there are unlimited context elements in the real world where the target system exists. To deal with this problem, this paper proposes a context-dependent requirements analysis method called CAMEmb (Context Analysis Method for Embedded systems) in which only the value-context elements are extracted as the associated context elements. Applying the guide words provided by CAMEmb, we can explore only a sequence of context elements directly or indirectly affecting the data value observed or controlled by the system sensors and actuators. Other context elements not affecting the system observation and control are not taken into account because these context elements do not affect the system behavior. Using CAMEmb and lightweight formal tools, we can explore the context boundary that guarantees the expected system behavior. We developed CAMEmbModeler, a support tool consisting of a CAMEmb-based modeling editor and a model compiler that transforms system and context models into the design model reflecting the context boundary.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129969063","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Requirements are slipping through the gaps — A case study on causes & effects of communication gaps in large-scale software development","authors":"E. Bjarnason, K. Wnuk, B. Regnell","doi":"10.1109/RE.2011.6051639","DOIUrl":"https://doi.org/10.1109/RE.2011.6051639","url":null,"abstract":"Communication is essential for software development as its efficiency throughout the entire project life-cycle is a key factor in developing and releasing successful software products to the market. This paper reports on findings from an explanatory case study aiming at a deeper understanding of the causes and effects of communication gaps in a large-scale industrial set up. Based on an assumption of what causes gaps in communication of requirements and what effects such gaps have, a semi-structured interview study was performed with nine practitioners at a large market-driven software company. We found four main factors that affect the requirements communication, namely scale, temporal aspects, common views and decision structures. The results also show that communication gaps lead to failure to meet the customers' expectations, quality issues and wasted effort. An increased awareness of these factors is a help in identifying what to address to achieve a more efficient requirements management, and ultimately more efficient and successful software development. By closing the communication gaps the requirements may continue all the way through the project life-cycle and be more likely to result in software that meets the customers' expectations.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129388915","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Sabine Teufl, Maged Khalil, Dongyue Mou, Eva Geisberger
{"title":"Experience with content-based requirements engineering assessments","authors":"Sabine Teufl, Maged Khalil, Dongyue Mou, Eva Geisberger","doi":"10.1109/RE.2011.6051668","DOIUrl":"https://doi.org/10.1109/RE.2011.6051668","url":null,"abstract":"Identifying strengths and weaknesses in requirements engineering (RE) activities and deriving corresponding improvement and rectification recommendations are the main goals of the presented content-based RE assessment approach, which relies on a well-founded RE reference model. Two representative examples from our case study pool, carried out for companies with established RE practices in different domains, demonstrate the approach, its results and benefits.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128871804","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"How interaction between roles shapes the communication structure in requirements-driven collaboration","authors":"S. Marczak, D. Damian","doi":"10.1109/RE.2011.6051643","DOIUrl":"https://doi.org/10.1109/RE.2011.6051643","url":null,"abstract":"Requirements engineering involves collaboration among many project team members. Driven by coordination needs, this collaboration relies on communication and knowledge that members have of their colleagues and related activities. Ineffective coordination with those who work on requirements dependencies may result in project failure. In this paper, we report on a study of roles and communication structures in the collaboration driven by interdependent requirements in a software team. Through on-site observations, interviews with the developers and application of social network analysis, we found that there was significant communication between diverse roles in the project, and identified what were the reasons for communication between the different roles. We also found that these interactions typically involved a core of requirements analysts and testers in close communication, that most often they involved critical members whose absence, whether temporary or permanent, would disrupt the information flow if removed from the project, as well as that new hires were mostly isolated from the team collaboration. Most interestingly we found that the emergent communication structure between the different roles in the project did not conform to the planned communication structure prescribed by the organization. These findings further our knowledge about collaboration driven by requirements, and provide some useful implications for research and development of collaborative tools to support the effective coordination of cross-functional teams in software development.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134184862","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Finding incremental solutions for evolving requirements","authors":"Neil A. Ernst, Alexander Borgida, Ivan Jureta","doi":"10.1109/RE.2011.6051656","DOIUrl":"https://doi.org/10.1109/RE.2011.6051656","url":null,"abstract":"This paper investigates aspects of the problem of software evolution resulting from top-level requirements change. In particular, while most research on design for software focuses on finding some correct solution, this ignores that such a solution is often only correct in a particular, and often short-lived, context. Using a logic-based goal-oriented requirements modeling language, the paper poses the problem of finding desirable solutions as the requirements change. Among other possible criteria of desirability, we consider minimizing the effort required to implement the new solution, which involves reusing parts of the old solution. In general, the solution of requirements problems is viewed as an exploration using a “requirements engineering knowledge base” (REKB), whose specification is formalized. The paper reports on experience implementing the REKB on top of a so-called “reason-maintenance system”, and provides evidence that incremental solution finding is indeed more efficient.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"196 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114447831","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Run-time resolution of uncertainty","authors":"Kristopher Welsh, P. Sawyer, N. Bencomo","doi":"10.1109/RE.2011.6051673","DOIUrl":"https://doi.org/10.1109/RE.2011.6051673","url":null,"abstract":"Requirements awareness should help optimize requirements satisfaction when factors that were uncertain at design time are resolved at runtime. We use the notion of claims to model assumptions that cannot be verified with confidence at design time. By monitoring claims at runtime, their veracity can be tested. If falsified, the effect of claim negation can be propagated to the system's goal model and an alternative means of goal realization selected automatically, allowing the dynamic adaptation of the system to the prevailing environmental context.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"14 8 Pt 1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123697678","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Applying preference-based customization","authors":"S. Liaskos, V. Rogozhkin","doi":"10.1109/RE.2011.6051672","DOIUrl":"https://doi.org/10.1109/RE.2011.6051672","url":null,"abstract":"Preference-based analysis of goal variability has been found to be useful for understanding alternative ways by which actors can go about fulfilling their goals. More recently, a technique for using such preference analysis to customize software behavior has been proposed. This technique allows sets of goal alternatives that best satisfy a given preference to be provided as configuration parameters to an appropriately instrumented software system, so that the latter adapts its behavior to satisfy those alternatives. In this presentation, we show how this idea has been implemented in a prototypical tool and applied for customizing a simple ATM simulator.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"48 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133613728","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"What are the day-to-day factors that are preventing business analysts from effective business analysis?","authors":"Anja Wever, N. Maiden","doi":"10.1109/RE.2011.6051624","DOIUrl":"https://doi.org/10.1109/RE.2011.6051624","url":null,"abstract":"This industrial experience paper reports the results of a survey of business analysts to understand the barriers that they perceive are inhibiting effective requirements work in business-oriented projects. The survey was designed to investigate a mismatch between requirements education, training and practice that, we conjecture, was inhibiting effective requirements work by business analysts. Results revealed that, in spite of the education and training undertaken by many business analysts, their involvement in requirement projects appears to be often ad hoc and ineffective. This paper reports factors that business analysts cited as preventing them from applying their requirements analysis knowledge in practice and becoming effective professionals engaged in business analysis and associated systems engineering activities. Findings have implications not only for requirements education and training but also more effective use of requirements resources in projects.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"82 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122301947","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Are your sites down? Requirements-driven self-tuning for the survivability of Web systems","authors":"Bihuan Chen, Xin Peng, Y. Yu, Wenyun Zhao","doi":"10.1109/RE.2011.6051650","DOIUrl":"https://doi.org/10.1109/RE.2011.6051650","url":null,"abstract":"Running in a highly uncertain and greatly complex environment, Web systems cannot always provide full set of services with optimal quality, especially when work loads are high or subsystem failures are frequent. Hence, it is significant to continuously maintain a high satisfaction level of survivability, hereafter survivability assurance, while relaxing or sacrificing certain quality or functional requirements that are not crucial to the survival of the entire system. After giving a value-based interpretation to survivability assurance to facilitate a quantitative analysis, we propose a requirements-driven self-tuning method for the survivability assurance of Web systems. Maintaining an enriched and live goal model, our method adapts to runtime tradeoff decisions made by our PID (proportional-integral-derivative) controller and goal-oriented reasoner for both quality and functional requirements. The goal-based configuration plans produced by the reasoner is carried out on the live goal model, and then mapped into system architectural configurations. Experiments on an online shopping system are conducted to validate the effectiveness of the proposed method.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127736550","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Semi-automatic identification of features in requirement specifications","authors":"Ekaterina Boutkova, F. Houdek","doi":"10.1109/RE.2011.6051627","DOIUrl":"https://doi.org/10.1109/RE.2011.6051627","url":null,"abstract":"Reuse of requirements leads to reduction in time spent for specification of new products. Variant management of requirement documents is an essential prerequisite in terms of a successful reuse of requirements. It supports the decisions if available requirements can be reused or not. One possibility to document the variability is feature modelling. One main challenge while introducing feature modelling in a grown environment is to extract product features from large natural language specifications. The current practice is a manual review of specifications conducted by domain experts. This procedure is very costly in terms of time. A promising approach to optimize feature identification is a semi-automatic identification of features in natural language specifications based on lexical analysis. This paper presents the current approaches used for handling variability in automotive specifications at Daimler passenger car development along with first experiences gained in using the optimized approach for feature identification using a lexical analysis.","PeriodicalId":385129,"journal":{"name":"2011 IEEE 19th International Requirements Engineering Conference","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129023540","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}