Bug Localization in Model-Based Systems in the Wild

The companies that have adopted the Model-Driven Engineering (MDE) paradigm have the advantage of working at a high level of abstraction. Nevertheless, they have the disadvantage of the lack of tools available to perform bug localization at the model level. In addition, in an MDE context, a bug can be related to different MDE artefacts, such as design-time models, model transformations, or run-time models. Starting the bug localization in the wrong place or with the wrong tool can lead to a result that is unsatisfactory. We evaluate how to apply the existing model-based approaches in order to mitigate the effect of starting the localization in the wrong place. We also take into account that software engineers can refine the results at different stages. In our evaluation, we compare different combinations of the application of bug localization approaches and human refinement. The combination of our approaches plus manual refinement obtains the best results. We performed a statistical analysis to provide evidence of the significance of the results. The conclusions obtained from this evaluation are: humans have to be involved at the right time in the process (or results can even get worse), and artefact-independence can be achieved without worsening the results.

The Role of Trustworthiness Facets for Developing Social Media Applications: A Structured Literature Review

This work reviews existing research about attributes, which are assessed by individuals to evaluate the trustworthiness of (i) software applications, (ii) organizations (e.g., service providers), and (iii) other individuals. As these parties are part of social media services, previous research has identified the need for users to assess their trustworthiness. Based on the trustworthiness assessment, users decide whether they want to interact with them and whether such interactions appear safe. The literature review encompasses 264 works from which so-called trustworthiness facets of 100 papers could be identified. In addition to an overview of trustworthiness facets, this work further introduces a guideline for software engineers on how to select appropriate trustworthiness facets during the analysis of the problem space for the development of specific social media applications. It is exemplified by the problem of “catfishing” in online dating.

Dynamic Testing Techniques of Non-Functional Requirements in Mobile Apps: A Systematic Mapping Study

Context: The mobile app market is continually growing offering solutions to almost all aspects of people’s lives, e.g., healthcare, business, entertainment, as well as the stakeholders’ demand for apps that are more secure, portable, easy to use, among other non-functional requirements (NFRs). Therefore, manufacturers should guarantee that their mobile apps achieve high-quality levels. A good strategy is to include software testing and quality assurance activities during the whole life cycle of such solutions. Problem: Systematically warranting NFRs is not an easy task for any software product. Software engineers must take important decisions before adopting testing techniques and automation tools to support such endeavors. Proposal: To provide to the software engineers with a broad overview of existing dynamic techniques and automation tools for testing mobile apps regarding NFRs. Methods: We planned and conducted a Systematic Mapping Study (SMS) following well-established guidelines for executing secondary studies in software engineering. Results: We found 56 primary studies and characterized their contributions based on testing strategies, testing approaches, explored mobile platforms, and the proposed tools. Conclusions: The characterization allowed us to identify and discuss important trends and opportunities that can benefit both academics and practitioners.

Improving bioinformatics software quality through incorporation of software engineering practices

Background Bioinformatics software is developed for collecting, analyzing, integrating, and interpreting life science datasets that are often enormous. Bioinformatics engineers often lack the software engineering skills necessary for developing robust, maintainable, reusable software. This study presents review and discussion of the findings and efforts made to improve the quality of bioinformatics software. Methodology A systematic review was conducted of related literature that identifies core software engineering concepts for improving bioinformatics software development: requirements gathering, documentation, testing, and integration. The findings are presented with the aim of illuminating trends within the research that could lead to viable solutions to the struggles faced by bioinformatics engineers when developing scientific software. Results The findings suggest that bioinformatics engineers could significantly benefit from the incorporation of software engineering principles into their development efforts. This leads to suggestion of both cultural changes within bioinformatics research communities as well as adoption of software engineering disciplines into the formal education of bioinformatics engineers. Open management of scientific bioinformatics development projects can result in improved software quality through collaboration amongst both bioinformatics engineers and software engineers. Conclusions While strides have been made both in identification and solution of issues of particular import to bioinformatics software development, there is still room for improvement in terms of shifts in both the formal education of bioinformatics engineers as well as the culture and approaches of managing scientific bioinformatics research and development efforts.

COMPETENCE ASSESSMENT AND DEVELOPMENT FOR MANAGING HUMAN CAPITAL IN IT SECTOR

With ever-increasing demand for software professionals, time has come for the information technology (IT) industry to unearth competencies required for software professionals. The majority of IT companies have been employing outsourcing software projects to inexpensive hubs in developing nations. Therefore expectations from highly skilled software professionals are rising. The purpose of the study is to recognize the technical competence levels associated with software professionals in a range of profiles which are found in India's major IT organizations. There are three basic objectives of the present study. The first objective is to conduct a literature survey of description of the software engineers in IT domain. The second objective is to quantify the competency levels of the software engineers in IT sector. Finally, the third objective is to conduct a survey-based empirical study on software engineers. The professional occupation is set up through seven successive profiles.

Control education in the software age

According to a commonplace saying, software is eating the world. Is software also eating control engineering? Software is currently transforming many industries including but not limited to automotive aiming at automated mobility services, agriculture moving to Agriculture 4.0, and factory automation with Industry 4.0. Software is simultaneously a flexible and universal functions enabler, and a driver of engineering complexity. At times, it seems that control engineers and software engineers are not understanding each other well enough. This article discusses two key engineering domains adjacent to control, systems and software engineering, covering engineering practice, design data exchange, and education. Finally, it suggests an extension to academic control curricula help to make control graduates even better team players.

Software vulnerability prediction using Grey wolf optimized Random forest on the unbalanced data sets

Any vulnerability in the software creates a software security threat and helps hackers to gain unauthorized access to resources. Vulnerability prediction models help software engineers to effectively allocate their resources to find any vulnerable class in the software, before its delivery to customers. Vulnerable classes must be carefully reviewed by security experts and tested to identify potential threats that may arise in the future. In the present work, a novel technique based on Grey wolf algorithm and Random forest is proposed for software vulnerability prediction. Grey wolf technique is a metaheuristic technique and it is used to select the best subset of features. The proposed technique is compared with other machine learning techniques. Experiments were performed on three datasets available publicly. It was observed that our proposed technique (GW-RF) outperformed all other techniques for software vulnerability prediction.

How does Leadership Motivate the Innovative Behaviors of Software Developers?

This study examines the relationship between transformational leadership types and the motivation of software engineers. The author uses full range leadership as a major theory and investigates how transformational leadership types influences the innovative behaviors of software developers by using a mediator of affective organizational commitment. For this, this study surveys 352 software developers working in 35 companies in Korea and analyzes the data using AMOS 24. The results show that charisma, inspirational motivation, intellectual stimulation and individualized consideration increase their affective organizational commitment affecting innovative behaviors positively in turn.

Towards a Security Competence of Software Developers

Software growth has been explosive as people depend heavily on software on daily basis. Software development is a human-intensive effort, and developers' competence in software security is essential for secure software development. In addition, ubiquitous computing provides an added complexity to software security. Studies have treated security competences of software developers as a subsidiary of security engineers' competence instead of software engineers' competence, limiting the full knowledge of the security competences of software developers. This presents a crucial challenge for developers, educators, and users to maintain developers' competences in security. As a first step in pushing for the developers' security competence studies, this chapter utilises a literature review to identify the security competences of software developers. Thirteen security competences of software developers were identified and mapped to the common body of knowledge for information security professional framework. Lastly, the implications for, with, and without the competences are analysed and presented.