In recent years, platforms have become important for allowing ecosystems to emerge that allow users to collaborate and create unprecedented forms of innovation. For the platform provider, the ecosystem represents a massive business opportunity if the platform succeeds to make the collaborations among the users value-creating and to facilitate trust. While the requirements flow for evolving existing ecosystems is understood, it is unclear how to analyse an ecosystem that is to be. In this paper, we draw on recent work on collaboration modelling in requirements engineering and propose an integrated framework for the analysis of multi-party collaboration that is to be supported by a platform. Drawing on a real-world case, we describe how the framework is applied and the results that have been obtained with it. The results indicate that the framework was useful to understand the ecosystem context for a planned platform in the domain of artificial intelligence, allowed identification of platform requirements and offered a basis to plan validation.
{"title":"Framework for Analysis of Multi-party Collaboration","authors":"Yuliyan V. Maksimov, Samuel Fricker","doi":"10.1109/REW.2019.00013","DOIUrl":"https://doi.org/10.1109/REW.2019.00013","url":null,"abstract":"In recent years, platforms have become important for allowing ecosystems to emerge that allow users to collaborate and create unprecedented forms of innovation. For the platform provider, the ecosystem represents a massive business opportunity if the platform succeeds to make the collaborations among the users value-creating and to facilitate trust. While the requirements flow for evolving existing ecosystems is understood, it is unclear how to analyse an ecosystem that is to be. In this paper, we draw on recent work on collaboration modelling in requirements engineering and propose an integrated framework for the analysis of multi-party collaboration that is to be supported by a platform. Drawing on a real-world case, we describe how the framework is applied and the results that have been obtained with it. The results indicate that the framework was useful to understand the ecosystem context for a planned platform in the domain of artificial intelligence, allowed identification of platform requirements and offered a basis to plan validation.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"93 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131757482","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 is an extended abstract of a keynote given at the Third International Workshop on Crowd-Based Requirements Engineering, held at RE'19. It provides a short guided tour through the landscape of CrowdRE, highlighting achievements, opportunities and pitfalls of CrowdRE.
{"title":"CrowdRE: Achievements, Opportunities and Pitfalls","authors":"M. Glinz","doi":"10.1109/REW.2019.00036","DOIUrl":"https://doi.org/10.1109/REW.2019.00036","url":null,"abstract":"This paper is an extended abstract of a keynote given at the Third International Workshop on Crowd-Based Requirements Engineering, held at RE'19. It provides a short guided tour through the landscape of CrowdRE, highlighting achievements, opportunities and pitfalls of CrowdRE.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"17 42","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114048162","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}
Taro Kishimoto, Reiji Yoshida, Y. Tobe, Midori Sugaya
In recent years, mechanisms to detect and correct human errors by AI and efforts to automate business operations have been advancing. Human errors are expected to be fatal in the future, and they need to be predicted and prevented in advance. Researches has also been proposed to analyze human errors from a model of human behavior and electroencephalograms, but no other useful biological information is considered. Therefore, in this research, we thought that prediction and detection could be performed by adding autonomic nerves that can be acquired from heart rate as biological information and observing patterns before and after mistakes. In order to realize it, we measured the pulse and EEG of the worker who is carrying out the computational task, developed an experimental system to investigate the question and timing of the task, assumed that it that it is possible to evaluate the electroencephalogram and pulse at the time of human error occurrence by the computational task. In addition, a questionnaire based on NASA Task Load Index was conducted to enable analysis using subjective assessment of the tasks. Through the evaluation experiments, it was suggested that it is possible to detect the occurrence of human error in the group that answered that emphasized a particular measure in the questionnaire.
{"title":"Examination of Evaluation Method on Human Error During Work by Bioinstrumentation","authors":"Taro Kishimoto, Reiji Yoshida, Y. Tobe, Midori Sugaya","doi":"10.1109/REW.2019.00019","DOIUrl":"https://doi.org/10.1109/REW.2019.00019","url":null,"abstract":"In recent years, mechanisms to detect and correct human errors by AI and efforts to automate business operations have been advancing. Human errors are expected to be fatal in the future, and they need to be predicted and prevented in advance. Researches has also been proposed to analyze human errors from a model of human behavior and electroencephalograms, but no other useful biological information is considered. Therefore, in this research, we thought that prediction and detection could be performed by adding autonomic nerves that can be acquired from heart rate as biological information and observing patterns before and after mistakes. In order to realize it, we measured the pulse and EEG of the worker who is carrying out the computational task, developed an experimental system to investigate the question and timing of the task, assumed that it that it is possible to evaluate the electroencephalogram and pulse at the time of human error occurrence by the computational task. In addition, a questionnaire based on NASA Task Load Index was conducted to enable analysis using subjective assessment of the tasks. Through the evaluation experiments, it was suggested that it is possible to detect the occurrence of human error in the group that answered that emphasized a particular measure in the questionnaire.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"226 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114588521","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}
Legacy software systems typically include vital data for organizations that use them and should thus to be regularly maintained. Ideally, organizations should rely on Requirements Engineers to understand and manage changes of stakeholder needs and system constraints. However, due to time and cost pressure, and with a heavy focus on implementation, organizations often choose to forgo Requirements Engineers and rather focus on ad-hoc bug fixing and maintenance. This position paper discusses what Requirements Engineers could possibly learn from other similar roles to become crucial for the evolution of legacy systems. Particularly, we compare the roles of Requirements Engineers (according to IREB), Building Architects (according to the German regulations), and Product Owners (according to "The Scrum-Guide"). We discuss overlaps along four dimensions: liability, self-portrayal, core activities, and artifacts. Finally we draw insights from these related fields to foster the concept of a Requirements Engineer as a distinguished profession.
{"title":"Renovating Requirements Engineering: First Thoughts to Shape Requirements Engineering as a Profession","authors":"Y. D. Pham, Lloyd Montgomery, W. Maalej","doi":"10.1109/REW.2019.00008","DOIUrl":"https://doi.org/10.1109/REW.2019.00008","url":null,"abstract":"Legacy software systems typically include vital data for organizations that use them and should thus to be regularly maintained. Ideally, organizations should rely on Requirements Engineers to understand and manage changes of stakeholder needs and system constraints. However, due to time and cost pressure, and with a heavy focus on implementation, organizations often choose to forgo Requirements Engineers and rather focus on ad-hoc bug fixing and maintenance. This position paper discusses what Requirements Engineers could possibly learn from other similar roles to become crucial for the evolution of legacy systems. Particularly, we compare the roles of Requirements Engineers (according to IREB), Building Architects (according to the German regulations), and Product Owners (according to \"The Scrum-Guide\"). We discuss overlaps along four dimensions: liability, self-portrayal, core activities, and artifacts. Finally we draw insights from these related fields to foster the concept of a Requirements Engineer as a distinguished profession.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121646649","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}
Security incidents can arise from the misuse of existing software systems. Thus, appropriate logging mechanisms should be implemented at the software level to support the detection and investigation of security incidents. However, due to insufficient logging, security incidents often go undetected for long periods. Moreover, even after a security incident is detected, there is not enough information to fully reconstruct how an incident occurred. Insufficient logging may be due to the limited security expertise of software developers, who may not know what are the most critical security incidents. Also, for large software systems and a multitude of potential misuse scenarios, it is cumbersome to identify when and what logging instructions should be implemented. In this paper, we propose a preliminary idea to automate the development of "forensic-ready" software systems. These systems can log a minimum amount of relevant data that can be used to detect and investigate potential security incidents. Our approach allows a security engineer to elicit a set of potential software misuse scenarios, expressed as annotated sequence diagrams. These diagrams are then used—together with a control flow graph of the software system— to identify the exact location where logging instructions should be placed and the information they should log. Finally, logging instructions can be injected into designated software system locations using Aspect-Oriented Programming. We illustrate our approach using an example of software misuse in a human resources management software system.
{"title":"Towards Automated Logging for Forensic-Ready Software Systems","authors":"Fanny Rivera-Ortiz, L. Pasquale","doi":"10.1109/REW.2019.00033","DOIUrl":"https://doi.org/10.1109/REW.2019.00033","url":null,"abstract":"Security incidents can arise from the misuse of existing software systems. Thus, appropriate logging mechanisms should be implemented at the software level to support the detection and investigation of security incidents. However, due to insufficient logging, security incidents often go undetected for long periods. Moreover, even after a security incident is detected, there is not enough information to fully reconstruct how an incident occurred. Insufficient logging may be due to the limited security expertise of software developers, who may not know what are the most critical security incidents. Also, for large software systems and a multitude of potential misuse scenarios, it is cumbersome to identify when and what logging instructions should be implemented. In this paper, we propose a preliminary idea to automate the development of \"forensic-ready\" software systems. These systems can log a minimum amount of relevant data that can be used to detect and investigate potential security incidents. Our approach allows a security engineer to elicit a set of potential software misuse scenarios, expressed as annotated sequence diagrams. These diagrams are then used—together with a control flow graph of the software system— to identify the exact location where logging instructions should be placed and the information they should log. Finally, logging instructions can be injected into designated software system locations using Aspect-Oriented Programming. We illustrate our approach using an example of software misuse in a human resources management software system.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133221740","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}
Socio-technical systems combine behaviour and actions from human operators, physical processes (e.g., thermodynamic or electromagnetism), computing and data communication. One often uses expression "cyber-physical system", or "systems of systems" in the case of systems composed of socio-technical systems of their own that each have different stakeholders, owners and lifecycles, but that must cooperate in order to achieve what none can achieve independently. Complex systems are systems that require the cooperation and coordination of multiple individuals, multiple teams, multiple engineering disciplines and multiple stakeholders to be fully understood in all necessary aspects. This coordination must be ensured all along the lifetime of the system, from scoping studies that aim at determining the nature of the system needed, to deconstruction. For systems such as power plants or passenger aircrafts, this lifetime may cover several decades, during which the system needs to be operated, maintained, retrofitted and upgraded, by multiple successive generations. EDF has developed a FOrmal Requirements Modelling Language (FORM-L) to help address this issue for what concerns dynamic phenomena. This paper provides a brief introduction to FORM-L and its underlying methodology, illustrated with short examples.
{"title":"Formal Requirements and Constraints Modelling in FORM-L for the Engineering of Complex Socio-Technical Systems","authors":"Thuy Nguyen","doi":"10.1109/REW.2019.00027","DOIUrl":"https://doi.org/10.1109/REW.2019.00027","url":null,"abstract":"Socio-technical systems combine behaviour and actions from human operators, physical processes (e.g., thermodynamic or electromagnetism), computing and data communication. One often uses expression \"cyber-physical system\", or \"systems of systems\" in the case of systems composed of socio-technical systems of their own that each have different stakeholders, owners and lifecycles, but that must cooperate in order to achieve what none can achieve independently. Complex systems are systems that require the cooperation and coordination of multiple individuals, multiple teams, multiple engineering disciplines and multiple stakeholders to be fully understood in all necessary aspects. This coordination must be ensured all along the lifetime of the system, from scoping studies that aim at determining the nature of the system needed, to deconstruction. For systems such as power plants or passenger aircrafts, this lifetime may cover several decades, during which the system needs to be operated, maintained, retrofitted and upgraded, by multiple successive generations. EDF has developed a FOrmal Requirements Modelling Language (FORM-L) to help address this issue for what concerns dynamic phenomena. This paper provides a brief introduction to FORM-L and its underlying methodology, illustrated with short examples.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127976136","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}
Process mining uses event log data to discover processes, hence enabling multiple requirements elicitation activities. As the number of applications deployed on a cloud infrastructure is increasing, it becomes important to understand their processes and the ways these existing systems are actually used. However, the cloud brings new challenges to process mining that deserve special attention. This paper reports on a systematic literature review based on a selection of 27 papers. The aim is to assess the applicability of process mining techniques to cloud-based applications, to document the processes of these existing systems. We observe there is a growing interest in applying process mining to these areas, and we report on algorithms, tools, and validation approaches taken. We also report on many cloud-specific challenges for process mining, which require further attention from the research community.
{"title":"Process Mining for Cloud-Based Applications: A Systematic Literature Review","authors":"Najah Mary El-Gharib, Daniel Amyot","doi":"10.1109/REW.2019.00012","DOIUrl":"https://doi.org/10.1109/REW.2019.00012","url":null,"abstract":"Process mining uses event log data to discover processes, hence enabling multiple requirements elicitation activities. As the number of applications deployed on a cloud infrastructure is increasing, it becomes important to understand their processes and the ways these existing systems are actually used. However, the cloud brings new challenges to process mining that deserve special attention. This paper reports on a systematic literature review based on a selection of 27 papers. The aim is to assess the applicability of process mining techniques to cloud-based applications, to document the processes of these existing systems. We observe there is a growing interest in applying process mining to these areas, and we report on algorithms, tools, and validation approaches taken. We also report on many cloud-specific challenges for process mining, which require further attention from the research community.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114333273","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 paper presents a novel approach to validation of behavioral requirements for control systems. A requirement is specified by a natural language pattern and its expression in Linear Temporal Logic (LTL). This way flexibility and understandability of natural language is combined with advantages of formalization that is a basis for various stages of system development, testing and verification. Still, validity of the requirements remains a major challenge. The paper considers application of mutation analysis for capturing of correct behavioral requirements. Generation and exploration of mutants supports a better understanding of requirements, The novelty of the approach is that the suggested mutations are semantic-based, as opposed to the more common syntax-based mutation analysis. A significant advantage of the approach is that it allows to focus only on plausible potential faults in understanding of the required system behavior, and to avoid generation of a vast amount of mutants that are irrelevant to the intended meaning of the requirements. Moreover, in many cases the effect of semantic-based mutations just can not be achieved by usual syntax-based mutations of LTL formulas associated with requirements. The approach is illustrated using a rail cross control example.
{"title":"An Approach to Validation of Combined Natural Language and Formal Requirements for Control Systems","authors":"M. Trakhtenbrot","doi":"10.1109/REW.2019.00025","DOIUrl":"https://doi.org/10.1109/REW.2019.00025","url":null,"abstract":"The paper presents a novel approach to validation of behavioral requirements for control systems. A requirement is specified by a natural language pattern and its expression in Linear Temporal Logic (LTL). This way flexibility and understandability of natural language is combined with advantages of formalization that is a basis for various stages of system development, testing and verification. Still, validity of the requirements remains a major challenge. The paper considers application of mutation analysis for capturing of correct behavioral requirements. Generation and exploration of mutants supports a better understanding of requirements, The novelty of the approach is that the suggested mutations are semantic-based, as opposed to the more common syntax-based mutation analysis. A significant advantage of the approach is that it allows to focus only on plausible potential faults in understanding of the required system behavior, and to avoid generation of a vast amount of mutants that are irrelevant to the intended meaning of the requirements. Moreover, in many cases the effect of semantic-based mutations just can not be achieved by usual syntax-based mutations of LTL formulas associated with requirements. The approach is illustrated using a rail cross control example.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"53 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126609240","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}
Chong Wang, Ju Li, Peng Liang, M. Daneva, M. V. Sinderen
Release planning for mobile apps has only recently become an area of active research. As a result, little is known about the types of requirements that app developers pay the most attention to when releasing an app. This research uses the changelogs of apps to shed light on this. We report the results of an exploratory study in which we analyzed the requirements that dominate the changes of apps, according to a set of 3000 changelogs collected from 120 apps from three categories in the Apple App Store: Travel, Social networking, and Books. We analyzed the changelogs in terms of functional and non-functional requirements, from a developers' perspective. Our results suggest that developers' releases are by far more concerned with non-functional requirements than with functional requirements. We also found that usability and maintainability are the most frequently mentioned non-functional requirements (NFRs) in the changelogs. Surprisingly, reliability requirements formed only a fraction of the total number of NFRs addressed in all changelogs of apps in the three selected App Store categories.
{"title":"Developers' Eyes on the Changes of Apps: An Exploratory Study on App Changelogs","authors":"Chong Wang, Ju Li, Peng Liang, M. Daneva, M. V. Sinderen","doi":"10.1109/REW.2019.00042","DOIUrl":"https://doi.org/10.1109/REW.2019.00042","url":null,"abstract":"Release planning for mobile apps has only recently become an area of active research. As a result, little is known about the types of requirements that app developers pay the most attention to when releasing an app. This research uses the changelogs of apps to shed light on this. We report the results of an exploratory study in which we analyzed the requirements that dominate the changes of apps, according to a set of 3000 changelogs collected from 120 apps from three categories in the Apple App Store: Travel, Social networking, and Books. We analyzed the changelogs in terms of functional and non-functional requirements, from a developers' perspective. Our results suggest that developers' releases are by far more concerned with non-functional requirements than with functional requirements. We also found that usability and maintainability are the most frequently mentioned non-functional requirements (NFRs) in the changelogs. Surprisingly, reliability requirements formed only a fraction of the total number of NFRs addressed in all changelogs of apps in the three selected App Store categories.","PeriodicalId":166923,"journal":{"name":"2019 IEEE 27th International Requirements Engineering Conference Workshops (REW)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128111438","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
扫码关注我们
求助内容：
应助结果提醒方式：