ABSTRACT. to follow

ABSTRACT. Providing computer-based services for vehicular systems has evolved to the point where majority of functions are realised by software. However, the need to provide safety in critical functions such as braking and engine control requires an approach that can guarantee reliable operation of the functions. At the same time, there are a variety of vehicle functions that are less critical. The main challenge for the vehicle manufacturers is to provide both types of functions in an economic and reliable manner. To meet this challenge, this paper considers the Rubus tool chain for model- and component-based development of vehicle software and a well-proven (in the industrial use for over twenty years) and certified (according to ISO 26262) real-time operating system for its execution. The paper provides an overview of the Rubus approach and driving concepts as well as the research results that are used in providing its tool chain. Moreover, the paper presents a success story of a unique academic-industrial collaboration in the vehicle domain that has resulted in sustained development of the tool chain. The collaborators form a clear value chain from academia, through tool developer, to the end users of the technology. The paper also highlights the perspectives of the collaborators and discusses the challenges faced, experiences gained and lessons learned from several technology transfer projects.

ABSTRACT. In Brazil, software industry and academia have formed partnerships more often due to funding agencies, such as CNPq and FINEP, and tax incentives originated, for example, from Brazil's Informatics Law. Like in many relationships, each party brings different experiences, goals, targets and outcomes to be achieved. However, for a partnership to be successful, it is necessary to learn how to deal with these differences, respecting the limits of each party and fostering mutual growth. The aim of this paper is to present challenges and lessons learned faced by the GREat research group at the Federal University of Ceará over the past 15 years of partnership with industry. Besides, we present the GREat Business process for projects with industry and how the software engineering evolved in our group within these projects. We believe this report can help other industry and academia partnerships around the world not only because our main partners are international companies but also because what we have learned from practice is globally applied.

ABSTRACT. Open Innovation, through partnerships across a community such as a network of university researchers, is an alternative mechanism to stimulate corporate growth and build value in contrast to proprietary innovation. In this paper, we build on our experience and strategies presented at previous workshops. We outline a business process model based on use cases for establishing and leveraging company-university collaborations, both to extract value in terms of the development and inspiration of new intellectual property and the recruitment of top technical university talent.

ABSTRACT. In order for the conduct of collaborative research projects and their outcomes to be valuable for both research and practice it is necessary to successfully address a number of socio-technical challenges in the field of software engineering. Collaborative research involving researchers and practitioners related to software systems have utilised a variety of different research approaches. Adoption of an effective research approach for the situation at hand in a research project may significantly contribute to project success. Experiences from collaborative research show that action case can be an appropriate choice of approach for addressing socio-technical challenges in the software domain, which is appealing to both practitioners and researchers. This paper elaborates on a number of challenges for successful conduct of collaborative research projects and reports on experiences from use of action case as a research approach for conduct of collaborative research related to software systems.

ABSTRACT. It is a common belief that, if you want to do research in industry, you should follow one of two ways: you either work for a large corporation, or you work for a startup that will eventually be acquired by one large corporation. In this presentation we address the following question: is it possible and worthwhile to develop meaningful research in an SMB (small and medium-sized business)? In doing so, we will present a case in the context of IoT (Internet of Things).

ABSTRACT. This paper presents our results from identifying and documenting false positives generated by static code analysis tools. By false positives, we mean a static code analysis tool generates a warning message, but the warning message is not really an error. The goal of our study is to understand the different kinds of false positives generated so we can (1) automatically determine if an error message is truly indeed a true positive, and (2) reduce the number of false positives developers and testers must triage. We have used two open-source tools and one commercial tool in our study. The results of our study have led to 14 core false positive patterns, some of which we have confirmed with static code analysis tool developers.

ABSTRACT. In this paper we present our experience during design, development, and pilot deployments of a data-driven machine learning based application maintenance solution. We implemented a proof of concept to address a spectrum of interrelated problems encountered in application maintenance projects including duplicate incident ticket identification, assignee recommendation, theme mining, and mapping of incidents to business processes. In the context of IT services, these problems are frequently encountered, yet there is a gap in bringing automation and optimization. Despite long-standing research around mining and analysis of software repositories, such research outputs are not adopted well in practice due to the constraints these solutions impose on the users. We discuss need for designing pragmatic solutions with low barriers to adoption and addressing right level of complexity of problems with respect to underlying business constraints and nature of data.

ABSTRACT. Research collaborations provide opportunities for both practitioners and researchers: practitioners need solutions for difficult business challenges and researchers are looking for hard problems to solve and publish. Nevertheless, research collaborations carry the risk that practitioners focus on quick solutions too much and that researchers tackle theoretical problems, resulting in products which do not fulfill the project requirements.

In this paper we introduce an approach extending the ideas of agile and lean software development. It helps practitioners and researchers keep track of their common research collaboration goal: a scientifically enriched software product which fulfills the needs of the practitioner’s business model.

This approach gives first-class status to application-oriented metrics that measure progress and success of a research collaboration continuously. Those metrics are derived from the collaboration requirements and help to focus on a commonly defined goal.

An appropriate tool set evaluates and visualizes those metrics with minimal effort, and all participants will be pushed to focus on their tasks with appropriate effort. Thus project status, challenges and progress are transparent to all research collaboration members at any time.

ABSTRACT. The Service Oriented Software Development (SOSD) approach is a common software development paradigm. Previous qualitative and quantitative studies looked at the main reasons for the delay in software development so as to help project’s stakeholders to take appropriate actions for improvement in their planning. In SOSD projects, due to the high level of user involvement in new service and product development, service providers need to make dynamic trade-offs to address their clients’ demands. In this paper, we look at interruptions and their impact on tasks du- ration. We used text classification, Natural Language Processing (NLP), and quantitative time series analysis techniques to analyze 7, 770 development tasks of five real SOSD projects at Arcurve Inc. Our results show that fixing an issue, addressing changes, and adding new features are the most frequently perceived causes of interruption in SOSD projects. Furthermore, we have found that requirements engineering and project management tasks experience less delay time over a project’s life-cycle. We also visualized the association between the interruption length and the extra tasks’ duration resulted from these interruptions within various development task types, which shows there is no strong association between task type with regard to these two parameters.

ABSTRACT. http://2017.softstart.org/wp/index.php/program/