Technical standards are established as a kind of norm or general requirement with respect to the development of technical systems. They shall ensure a uniform way of engineering, to gain benefits when it comes to product comparability, interoperability, assurance of product quality, reliability, safety, and similar properties. Usually, technical standards are developed iteratively, where text documents are used as work products which are subject to continuous negotiations. In this paper, we retrace the requirement-driven development process of the Distributed Co-Simulation Protocol~(DCP) specification. It is the main output of the ACOSAR ("Advanced Co-Simulation Open System Architecture") project. The DCP focuses on the integration of real-time systems into simulation environments. Therefore it poses a significant contribution to development and test of many technical systems. Typical examples are automotive advanced driver assistance system (ADAS), test beds for vehicles and engines, as well as components like electronic control units (ECU). The DCP specification is intended for standardization with a recognized standardization body. Unlike most other technical standards, the DCP specification was engineered on the foundation of written requirements, formulated by an inhomogeneous group of stakeholders. This paper highlights the applied development process, provides examples of requirements, and reports the overall outcome, including benefits and drawbacks.
{"title":"Requirements Engineering for Consensus-Oriented Technical Specifications","authors":"M. Krammer, Nadja Marko, M. Benedikt","doi":"10.1109/RE.2018.00039","DOIUrl":"https://doi.org/10.1109/RE.2018.00039","url":null,"abstract":"Technical standards are established as a kind of norm or general requirement with respect to the development of technical systems. They shall ensure a uniform way of engineering, to gain benefits when it comes to product comparability, interoperability, assurance of product quality, reliability, safety, and similar properties. Usually, technical standards are developed iteratively, where text documents are used as work products which are subject to continuous negotiations. In this paper, we retrace the requirement-driven development process of the Distributed Co-Simulation Protocol~(DCP) specification. It is the main output of the ACOSAR (\"Advanced Co-Simulation Open System Architecture\") project. The DCP focuses on the integration of real-time systems into simulation environments. Therefore it poses a significant contribution to development and test of many technical systems. Typical examples are automotive advanced driver assistance system (ADAS), test beds for vehicles and engines, as well as components like electronic control units (ECU). The DCP specification is intended for standardization with a recognized standardization body. Unlike most other technical standards, the DCP specification was engineered on the foundation of written requirements, formulated by an inhomogeneous group of stakeholders. This paper highlights the applied development process, provides examples of requirements, and reports the overall outcome, including benefits and drawbacks.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132786868","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}
The RE'18 theme is: "Crossing Boundaries and Increasing Impact". In this context we propose a tutorial on Requirements in an Agile context that aims at exploring the boundaries between requirements, specifications, stories, scenarios and tests. It follows the recent work started in the RE community about agility, from a practical point of view.
{"title":"Reconciling Requirements and Continuous Integration in an Agile Context","authors":"Sébastien Mosser, J. Bruel","doi":"10.1109/RE.2018.00076","DOIUrl":"https://doi.org/10.1109/RE.2018.00076","url":null,"abstract":"The RE'18 theme is: \"Crossing Boundaries and Increasing Impact\". In this context we propose a tutorial on Requirements in an Agile context that aims at exploring the boundaries between requirements, specifications, stories, scenarios and tests. It follows the recent work started in the RE community about agility, from a practical point of view.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"64 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131620902","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}
Software development is fault-prone especially during the fuzzy phases (requirements and design). Software inspections are commonly used in industry to detect and fix problems in requirements and design artifacts thereby mitigating the fault propagation to later phases where same faults are harder to find and fix. The output of an inspection process is natural language (NL) reviews that report the location and description of faults in software requirements specification document (SRS). The artifact author must manually read through the reviews and differentiate between true-faults and false-positives before fixing the faults. The time spent in making effective post-inspection decisions (number of true faults and deciding whether to re-inspect) could be spent in doing actual development work. The goal of this research is to automate the validation of inspection reviews, finding common patterns that describe high-quality requirements, identify fault prone requirements pre-inspection, and interrelated requirements to assist fixation of reported faults post-inspection. To accomplish these goals, this research employs various classification approaches, NL processing with semantic analysis and mining solutions from graph theory to requirement reviews and NL requirements. Initial results w.r.t. validation of inspection reviews have shown that our proposed approaches were able to successfully categorize useful and non-useful reviews.
{"title":"Automated Validation of Requirement Reviews: A Machine Learning Approach","authors":"Maninder Singh","doi":"10.1109/RE.2018.00062","DOIUrl":"https://doi.org/10.1109/RE.2018.00062","url":null,"abstract":"Software development is fault-prone especially during the fuzzy phases (requirements and design). Software inspections are commonly used in industry to detect and fix problems in requirements and design artifacts thereby mitigating the fault propagation to later phases where same faults are harder to find and fix. The output of an inspection process is natural language (NL) reviews that report the location and description of faults in software requirements specification document (SRS). The artifact author must manually read through the reviews and differentiate between true-faults and false-positives before fixing the faults. The time spent in making effective post-inspection decisions (number of true faults and deciding whether to re-inspect) could be spent in doing actual development work. The goal of this research is to automate the validation of inspection reviews, finding common patterns that describe high-quality requirements, identify fault prone requirements pre-inspection, and interrelated requirements to assist fixation of reported faults post-inspection. To accomplish these goals, this research employs various classification approaches, NL processing with semantic analysis and mining solutions from graph theory to requirement reviews and NL requirements. Initial results w.r.t. validation of inspection reviews have shown that our proposed approaches were able to successfully categorize useful and non-useful reviews.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"37 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121878507","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}
R. M. Carvalho, Rossana Andrade, K. Oliveira, C. Kolski
A new set of Non-Functional Requirements (NFRs) have appeared with the advent of Ubiquitous Computing (UbiComp) and more recently Internet of Things (IoT). Invisibility is one of these NFRs that means the ability to hide technology from users. Although invisibility is long seen as an essential characteristic for achieving the goals of UbiComp, it has not been cataloged regarding its subcharacteristics and solutions, making its design and requirements specification in such applications a challenging task. Considering the Softgoal Interdependency Graph (SIG), which is a well-known format to catalog NFRs, this work aims at capturing subcharacteristics and solutions for Invisibility and cataloging them in a SIG. Since there is no systematic approach on how to build SIGs, we also propose to systematize the definition of Invisibility SIG using the following well-defined research methods: snowballing, database search, grounded theory and questionnaires. As a result, we got an Invisibility SIG composed of two main subcharacteristics, twelve sub-subcharacteristics, ten general solutions and fifty-six specific solutions. This organized body of knowledge is useful for supporting software engineers to specify requirements and practical solutions for UbiComp and IoT applications. Furthermore, the proposed methodology used to capture and catalog requirements in a SIG can be reused for other NFRs.
{"title":"Catalog of Invisibility Requirements for UbiComp and IoT Applications","authors":"R. M. Carvalho, Rossana Andrade, K. Oliveira, C. Kolski","doi":"10.1109/RE.2018.00019","DOIUrl":"https://doi.org/10.1109/RE.2018.00019","url":null,"abstract":"A new set of Non-Functional Requirements (NFRs) have appeared with the advent of Ubiquitous Computing (UbiComp) and more recently Internet of Things (IoT). Invisibility is one of these NFRs that means the ability to hide technology from users. Although invisibility is long seen as an essential characteristic for achieving the goals of UbiComp, it has not been cataloged regarding its subcharacteristics and solutions, making its design and requirements specification in such applications a challenging task. Considering the Softgoal Interdependency Graph (SIG), which is a well-known format to catalog NFRs, this work aims at capturing subcharacteristics and solutions for Invisibility and cataloging them in a SIG. Since there is no systematic approach on how to build SIGs, we also propose to systematize the definition of Invisibility SIG using the following well-defined research methods: snowballing, database search, grounded theory and questionnaires. As a result, we got an Invisibility SIG composed of two main subcharacteristics, twelve sub-subcharacteristics, ten general solutions and fifty-six specific solutions. This organized body of knowledge is useful for supporting software engineers to specify requirements and practical solutions for UbiComp and IoT applications. Furthermore, the proposed methodology used to capture and catalog requirements in a SIG can be reused for other NFRs.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129746447","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}
M. Oriol, Melanie J. C. Stade, Farnaz Fotrousi, S. Nadal, Jovan Varga, N. Seyff, A. Abelló, Xavier Franch, Jordi Marco, Oleg Schmidt
Context: Software evolution ensures that software systems in use stay up to date and provide value for end-users. However, it is challenging for requirements engineers to continuously elicit needs for systems used by heterogeneous end-users who are out of organisational reach. Objective: We aim at supporting continuous requirements elicitation by combining user feedback and usage monitoring. Online feedback mechanisms enable end-users to remotely communicate problems, experiences, and opinions, while monitoring provides valuable information about runtime events. It is argued that bringing both information sources together can help requirements engineers to understand end-user needs better. Method/Tool: We present FAME, a framework for the combined and simultaneous collection of feedback and monitoring data in web and mobile contexts to support continuous requirements elicitation. In addition to a detailed discussion of our technical solution, we present the first evidence that FAME can be successfully introduced in real-world contexts. Therefore, we deployed FAME in a web application of a German small and medium-sized enterprise (SME) to collect user feedback and usage data. Results/Conclusion: Our results suggest that FAME not only can be successfully used in industrial environments but that bringing feedback and monitoring data together helps the SME to improve their understanding of end-user needs, ultimately supporting continuous requirements elicitation.
{"title":"FAME: Supporting Continuous Requirements Elicitation by Combining User Feedback and Monitoring","authors":"M. Oriol, Melanie J. C. Stade, Farnaz Fotrousi, S. Nadal, Jovan Varga, N. Seyff, A. Abelló, Xavier Franch, Jordi Marco, Oleg Schmidt","doi":"10.1109/RE.2018.00030","DOIUrl":"https://doi.org/10.1109/RE.2018.00030","url":null,"abstract":"Context: Software evolution ensures that software systems in use stay up to date and provide value for end-users. However, it is challenging for requirements engineers to continuously elicit needs for systems used by heterogeneous end-users who are out of organisational reach. Objective: We aim at supporting continuous requirements elicitation by combining user feedback and usage monitoring. Online feedback mechanisms enable end-users to remotely communicate problems, experiences, and opinions, while monitoring provides valuable information about runtime events. It is argued that bringing both information sources together can help requirements engineers to understand end-user needs better. Method/Tool: We present FAME, a framework for the combined and simultaneous collection of feedback and monitoring data in web and mobile contexts to support continuous requirements elicitation. In addition to a detailed discussion of our technical solution, we present the first evidence that FAME can be successfully introduced in real-world contexts. Therefore, we deployed FAME in a web application of a German small and medium-sized enterprise (SME) to collect user feedback and usage data. Results/Conclusion: Our results suggest that FAME not only can be successfully used in industrial environments but that bringing feedback and monitoring data together helps the SME to improve their understanding of end-user needs, ultimately supporting continuous requirements elicitation.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"69 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127272769","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}
The growth of our digital world makes it possible to record many types of events. In particular, the number of business processes whose events are being logged is significantly increasing. Process mining is an approach that exploits event logs to discover real processes executed in organizations, enabling them to (re) design and improve process models. Goal modeling, on the other hand, is a requirements engineering approach mainly used to analyze what-if situations and support decision making. Common problems with process mining include the complexity of discovered "spaghetti" processes and a lack of goal-process alignment. Current process mining practices are mainly oriented towards activities and do not profit from considering stakeholder goals and requirements to manage complexity and alignment. Involving goal-related factors can augment the precision and interpretability of mined models and lead to better opportunities to satisfy stakeholders. In this research, I propose two methods (for goal-oriented process and enhancement discovery, and for conformance checking) that show potentially synergetic effects achievable by combining process mining and goal-oriented modeling. The paper reports on the research method, the gap/problems being addressed, preliminary solutions, expected contributions, and main foreseen challenges.
{"title":"Towards Goal-Oriented Process Mining","authors":"Mahdi Ghasemi","doi":"10.1109/RE.2018.00066","DOIUrl":"https://doi.org/10.1109/RE.2018.00066","url":null,"abstract":"The growth of our digital world makes it possible to record many types of events. In particular, the number of business processes whose events are being logged is significantly increasing. Process mining is an approach that exploits event logs to discover real processes executed in organizations, enabling them to (re) design and improve process models. Goal modeling, on the other hand, is a requirements engineering approach mainly used to analyze what-if situations and support decision making. Common problems with process mining include the complexity of discovered \"spaghetti\" processes and a lack of goal-process alignment. Current process mining practices are mainly oriented towards activities and do not profit from considering stakeholder goals and requirements to manage complexity and alignment. Involving goal-related factors can augment the precision and interpretability of mined models and lead to better opportunities to satisfy stakeholders. In this research, I propose two methods (for goal-oriented process and enhancement discovery, and for conformance checking) that show potentially synergetic effects achievable by combining process mining and goal-oriented modeling. The paper reports on the research method, the gap/problems being addressed, preliminary solutions, expected contributions, and main foreseen challenges.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129218631","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}
This paper outlines the objectives, structure, and panelists of the data driven requirements engineering panel. This panel is intended to address challenges and opportunities that requirements engineering researchers face in accessing data.
{"title":"Data Driven Requirements Engineering: Implications for the Community","authors":"Maleknaz Nayebi","doi":"10.1109/RE.2018.00058","DOIUrl":"https://doi.org/10.1109/RE.2018.00058","url":null,"abstract":"This paper outlines the objectives, structure, and panelists of the data driven requirements engineering panel. This panel is intended to address challenges and opportunities that requirements engineering researchers face in accessing data.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114453692","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}
Mobile application (app) stores have lowered the barriers to app market entry, leading to an accelerated and unprecedented pace of mobile software production. To survive in such a highly competitive and vibrant market, release engineering decisions should be driven by a systematic analysis of the complex interplay between the user, system, and market components of the mobile app ecosystem. To demonstrate the feasibility and value of such analysis, in this paper, we present a case study on the rise and fall of Yik Yak, one of the most popular social networking apps at its peak. In particular, we identify and analyze the design decisions that led to the downfall of Yik Yak and track rival apps' attempts to take advantage of this failure. We further perform a systematic in-depth analysis to identify the main user concerns in the domain of anonymous social networking apps and model their relations to the core features of the domain. Such a model can be utilized by app developers to devise sustainable release engineering strategies that can address urgent user concerns and maintain market viability.
{"title":"Modeling User Concerns in the App Store: A Case Study on the Rise and Fall of Yik Yak","authors":"Grant Williams, Anas Mahmoud","doi":"10.1109/RE.2018.00-51","DOIUrl":"https://doi.org/10.1109/RE.2018.00-51","url":null,"abstract":"Mobile application (app) stores have lowered the barriers to app market entry, leading to an accelerated and unprecedented pace of mobile software production. To survive in such a highly competitive and vibrant market, release engineering decisions should be driven by a systematic analysis of the complex interplay between the user, system, and market components of the mobile app ecosystem. To demonstrate the feasibility and value of such analysis, in this paper, we present a case study on the rise and fall of Yik Yak, one of the most popular social networking apps at its peak. In particular, we identify and analyze the design decisions that led to the downfall of Yik Yak and track rival apps' attempts to take advantage of this failure. We further perform a systematic in-depth analysis to identify the main user concerns in the domain of anonymous social networking apps and model their relations to the core features of the domain. Such a model can be utilized by app developers to devise sustainable release engineering strategies that can address urgent user concerns and maintain market viability.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131365710","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}
Our previous work presented the Evolving Intentions framework, which specified how evolving qualitative goal models can be modeled and analyzed. Recent improvements to the framework allow for precise semantics of goal relationships with propagation of both evidence for and evidence against a goal's satisfaction (as in Tropos), and enables evaluation of evolution with absolute time (in addition to relative time). The reasoning is expressed as a constraint satisfaction problem. In this paper, we present BloomingLeaf, a new web-based tool that implements the new semantics. We showcase how the implementation and architecture of BloomingLeaf can be used to answer time-based questions.
{"title":"BloomingLeaf: A Formal Tool for Requirements Evolution Over Time","authors":"A. Grubb, M. Chechik","doi":"10.1109/RE.2018.00067","DOIUrl":"https://doi.org/10.1109/RE.2018.00067","url":null,"abstract":"Our previous work presented the Evolving Intentions framework, which specified how evolving qualitative goal models can be modeled and analyzed. Recent improvements to the framework allow for precise semantics of goal relationships with propagation of both evidence for and evidence against a goal's satisfaction (as in Tropos), and enables evaluation of evolution with absolute time (in addition to relative time). The reasoning is expressed as a constraint satisfaction problem. In this paper, we present BloomingLeaf, a new web-based tool that implements the new semantics. We showcase how the implementation and architecture of BloomingLeaf can be used to answer time-based questions.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114860627","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}
Federica Sarro, M. Harman, Yue Jia, Yuanyuan Zhang
In this paper we provide empirical evidence that the rating that an app attracts can be accurately predicted from the features it offers. Our results, based on an analysis of 11,537 apps from the Samsung Android and BlackBerry World app stores, indicate that the rating of 89% of these apps can be predicted with 100% accuracy. Our prediction model is built by using feature and rating information from the existing apps offered in the App Store and it yields highly accurate rating predictions, using only a few (11-12) existing apps for case-based prediction. These findings may have important implications for requirements engineering in app stores: They indicate that app developers may be able to obtain (very accurate) assessments of the customer reaction to their proposed feature sets (requirements), thereby providing new opportunities to support the requirements elicitation process for app developers.
{"title":"Customer Rating Reactions Can Be Predicted Purely using App Features","authors":"Federica Sarro, M. Harman, Yue Jia, Yuanyuan Zhang","doi":"10.1109/RE.2018.00018","DOIUrl":"https://doi.org/10.1109/RE.2018.00018","url":null,"abstract":"In this paper we provide empirical evidence that the rating that an app attracts can be accurately predicted from the features it offers. Our results, based on an analysis of 11,537 apps from the Samsung Android and BlackBerry World app stores, indicate that the rating of 89% of these apps can be predicted with 100% accuracy. Our prediction model is built by using feature and rating information from the existing apps offered in the App Store and it yields highly accurate rating predictions, using only a few (11-12) existing apps for case-based prediction. These findings may have important implications for requirements engineering in app stores: They indicate that app developers may be able to obtain (very accurate) assessments of the customer reaction to their proposed feature sets (requirements), thereby providing new opportunities to support the requirements elicitation process for app developers.","PeriodicalId":445032,"journal":{"name":"2018 IEEE 26th International Requirements Engineering Conference (RE)","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114762761","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}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：