Understanding Self-Efficacy in Software Engineering Industry: An Interview study

Context: It is known that men practitioners are predominant in software development teams over women. In recent years, researchers have investigated gender inequality from different perspectives, such as gender bias and suggestions to increase diversity in development teams. However, while most of the existing literature investigates the perception of women practitioners, the vast majority of the software development workforce – men – has received less attention. Goal: This work investigates men’s perceptions of gender inequality in software development teams and their experiences compared in software development to women. Method: Our study conducted a survey with 217 male practitioners, using a questionnaire consisting of 27 questions. The collected data was analyzed using a combination of quantitative and qualitative techniques, including graphical representations, percentages, and the grounded theory methodology. Results: Our findings reveal that most men do not perceive any sexist behavior among their team members and they are satisfied with the performance of their functions. In addition, their main suggestions to increase their participation in software development projects are offering training courses and improving the interaction among team members. Conclusions: The barriers and challenges that men practitioners face in software development teams are not the same as those faced by women. In addition, they consider that women do not work in software development due to a lack of affinity and knowledge about coding.

Background: Software organizations increasingly need developers with high skills for social interactions. Managers, leaders, and academics need to know the human factors influencing the individuals, the development team, and the software project activities. Despite the increasing number of secondary studies about human factors in Software Engineering (SE) and in Agile Software Development (ASD), there is no study synthesizing which human factors influence software development without a specific perspective from SE or human factor thematic. Objective: We aim to summarise human factors and their influence on SE development teams and ASD teams. Method: We executed a tertiary study. We used thematic analysis to examine the resulting data. Results: We found 29 systematic literature reviews and systematic mapping studies addressing the human perspective in SE teams. We identified 101 human factors and 79 influences grouped in 4 categories (Team member, Team, Project, and Organization). Also, we identified 71 human factors and 60 influences on ASD. The most investigated human factors are Communication, Collaboration, Knowledge, and Motivation. Conclusions: The identified human factors and their influences can be considered most significant by software organizations, researchers, and academics in SE practices. Based on our results, practitioners might propose activities that enhance human capital behaviors that influence individual motivation, agile mindset, team climate, software quality, or agile transition in traditional organizations.

Research problem: Communication affects many aspects of the software engineering process. In addition, poor team communication is often a root cause of failure for complex engineering projects. In global software engineering, communication and coordination become more challenging, and that fact affects the quality of the product. The goal of this study is to analyze the type and quality of research performed on software development team communication, and to present data to guide future research in these areas. Research questions: (1) How much communication research activity in the area of software development teams has been described in the literature from 2005 to 2015? (2) What is the current state of software development team communication research (what has been done and to what degree)? (3) What is the predominant research methodology of software development team communication research? (4) Where are the gaps in the current state of software development team communication research? (5) What are the major, common findings about communication in software development teams? Methodology: We reviewed 184 journal papers and performed a content analysis of the keywords from the relevant papers to create a software engineering team research taxonomy. We utilized this taxonomy to categorize the context of communication research papers. We then used the categorization results to determine the most active software development team communication research areas. In addition, we analyzed the quality of the journals (using impact factor and H-index as metrics) and the type of research performed in these areas (i.e., qualitative, quantitative, survey, social network analysis, or literature review). Results and conclusions: The results showed that the most active software development team communication research areas are global software development, project effectiveness, and effective teamwork. The most prevalent research methodology is a survey among those research areas. We conclude this paper with a presentation and discussion of the major findings of each research paper as well as the common themes among those findings in each of the top research areas.

Software development projects face significant risks of going over budget, over schedule, and of failing to deliver expected benefits. These risks have endured despite methodological changes within the industry, such as the rise in popularity of Agile. This research looks outside of the software industry and seeks inspiration from film production, which has developed different management strategies to address challenges similar to those faced by software development projects.First, an analysis of film production project management reveals four principles, each evidenced by a set of practices used throughout the industry. Next, we identify sets of practices that would enable software development projects to also align to those same four principles. The synthesis of each principle from its set of supporting film production practices is then validated through structured interviews with veteran film producers. Lastly, the derivation of each principle to a parallel set of supporting practices within the context of software development is validated in a second series of interviews with experienced software development project managers.In total, this research identifies a set of software development project management practices that mirror film production practices. These practices offer a framework for software development project managers to consider when seeking to tailor existing methodologies, particularly in scenarios that present challenges similar to those encountered in film production.

In the past decade, there have been a number of notable changes in industrial software engineering, including the movement towards agility. The Agile Manifesto characterizes the term “agile”, and lists a set of principles that form a basis for agile methodologies [1], such as Extreme Programming (XP), OpenUP, and Scrum. There is creation, communication, and consumption of knowledge during (agile) software development [2]. For the success of an agile project, it is crucial that such knowledge be managed effectively. In doing so, an appropriate selection and use of certain tools and technologies can be helpful. In the past few years, there has been a proliferation of Social Web Applications, such as Wiki [3]. Indeed, a number of noteworthy uses of Wiki in software engineering have been reported [4]. However, these studies are largely independent of any software development methodology, and are centered mostly on collaboration. The primary reasons for selecting Wiki for agile software development include the following: (1) the deployment of agile methodologies, especially XP and Scrum, with teams that are increasingly geographically-dispersed, (2) the involvement in sustainable software development by organizations with basic infrastructure and modest budgets for resources, and (3) the need of inexpensive, mature, and widely-available tools for supporting iterative development, by almost anybody, at anytime, anywhere, using almost any device. The purpose of this research is to provide a framework for integrating Wiki for the purpose of facilitating the dynamics of knowledge during agile software development.

The existing software engineering seldom considers software usability, and human-computer interaction (HCI) techniques which can improve the software usability cannot guarantee development efficiency. Recently, more and more stakeholders and users begin to regard the usability as an important software requirement. In order to bring respective advantages of software engineering and HCI techniques into full play to improve software usability and development efficiency, the paper presents user model driven software development, which integrates HCI techniques into software development method by eliciting user model under the participation of user, HCI designer and software engineer. Applications show that the method can be effectively applied to small software development team, and can raise software usability and development efficiency.

agile information systems, flexible information systems development, distributed information systems development, global software development, software development, special issue

Software process is the most important part of software project management, and software process models are important means of implementing the software process in any software organization. When there is need to improve the software process, then the need to improve the work-task part (software process models) of the software process must arise. As, there is need of increasing the commitment of software project managers through out the software development life cycle (SDLC), so we need to give them the list of activities in Waterfall Model, which should be made efficient by the software development team, to get the 80% productivity (output) easily, by reducing the effort of software development and ultimately increasing the performance of the software process. So, the idea of 80/20 rule (Pareto Principle, 1935) can be applied in the software engineering process model, in this regard. The Pareto Principle (1935) directed us to focus on what is really important in any field and field's work. Software process is most important part of software project management (SPM). This is also then ultimately needed for software project management (SPM) improvement. Our main research work is to improve the work-task part of the software process (i.e. software process models by applying the Pareto Principle - 80/20 Rule (1935) (or law of vital few) (1935), in the software engineering process models (or work-task part of the software process). This will be to facilitate the software project manager, using the software process models practically more efficient than without application of 80/20 Rule in software engineering Waterfall model. This has resulted in the reduction of the software development effort and increase in the performance of the software process. The results (efficient and improved software process models) will be implemented in the software industry, by software project managers, by focusing on the list of activities giving 80 percent of the overall productivity of the software process. The results will be the list of activities having the capability to give 20 percent of the overall productivity of the software Waterfall process, to be ignored, eliminated or designated to reduce the effort.

The development of software systems is a complex process involving a variety of individual tasks, collaborative work, and lifecycle management of the resulting products and product parts. Software development teams are supported in their work by a number of methods for the various production phases, and by appropriate tools of varying degrees of sophistication. Due to the immaterial nature of software, its development can be regarded as the goal-oriented production of a heterogeneous set of mostly highly-structured, interrelated units of informationNinformation that usually needs to be persistently stored and managed to meet various quality and reliability criteria. Database technology, over the past 30 years, has provided a wealth of concepts, methods, systems and tools that exactly address this problemNalbeit for information as it is typically encountered in more business and bookkeeping kinds of environments. Database management systems are in everyday use widely today, and have recently extended their range of application areas to engineering and scientific fields. Thus it looks very promising to investigate how database technology might be beneficially used in software engineering, and indeed many such approaches have been taken during the last decade and a half. To be fair, success so far has been rather limited. In this paper, we summarize the various requirements software engineering poses on database technology, then briefly describe past and present achievements, and discuss the challenges that need to be met in order to better achieve the goals in the future.

Design management systems have been developed and researched for traditional product and service industries. For interaction design little research has been performed on design management. The objective of this paper is to describe aspects of and provisions for industrial interaction design that influence approaches to design management within system and software development. We discuss whether there are specific conditions for design management of interaction design within the software and system development industries. The research is based on three short case studies from industrial software development. We identify some of these specific conditions; the difference between a usage and a product perspective, the design tools and practices, and the modularized and distributed processes. These issues point towards challenges facing design management within the software and system development context, as well as the need for interaction design to clarify its position as a strategic resource in software companies. The conclusions point towards the need for continued research on strategic possibilities and alternatives to organize and manage design work in software and system development.

This research aims to improve the learning quality of Computer Network course through the implementation of Waterfall method in the development of learning model. Waterfall method, with its focus on systematic and sequential approach in software development, is adapted to design and implement effective learning structure. This study uses qualitative research design with data collection through observation, interview, and documentation. Data analysis was conducted using content analysis method to evaluate the effectiveness of Waterfall-based learning model implementation. The results show that the implementation of Waterfall method facilitates structured planning, systematic development of learning materials, and continuous evaluation, which overall contribute to the improvement of learning quality. The developed learning model encourages students' active participation and improves the understanding of key concepts in Computer Networking. This research confirms that the Waterfall method can be effectively used outside the context of software development, particularly in improving the quality of learning in the academic field.

The complexity management of software code has become one of the major problems in software development industry. With growing complexity the maintenance effort of code increases. Moreover, various aspects of complexity create difficulties for complexity assessment. The objective of this paper is to investigate the relationships of various aspects of code complexity and propose a method for identifying the most complex functions. We have conducted an action research project in two software development companies and complemented it with a study of three open source products. Four complexity metrics are measured, and their nature and mutual influence are investigated. The results and possible explanations are discussed with software engineers in industry. The results show that there are two distinguishable aspects of complexity of source code functions: Internal and outbound complexities. Those have an inverse relationship. Moreover, the product of them does not seem to be greater than a certain limit, regardless of software size. We present a method that permits identification of most complex functions considering the two aspects of complexities. The evaluation shows that the use of the method is effective in industry: It enables identification of 0.5% most complex functions out of thousands of functions for reengineering.

This paper investigates the biological, psychological and societal reasoning for the disparity of females in the software engineering industry and how a more diverse workforce can have an advantage in this sector. Studies show that diversity in a company positively correlates to its financial profits. Furthermore, a severe lack of women in software engineering causes companies to limit themselves to smaller talent pools, decrease the creative outlook on fresh ideas and resolution of problems. There are superficially inherent reasons why computing appeals to men more than women, observations in multiple reports suggest that men may have a small advantage when it comes to mathematical and problem-solving skills. Additionally, it is elsewhere suggested that females interests reside in other fields related to ‘people’, whereas males are generally more interested in ‘things’. However, while societal factors and bias plays a role in the discouragement of women from the software engineering industry, studies have shown that countries with more gender-inegalitarian societies show an increase in the number of women in software engineering and STEM. This may imply that gender disparity in software engineering primarily emerges from personal choice rather than any discrimination or stereotyping.

Application software is all about logic ,problem solving and , creativity. It is based on user requirments.Requirments arebridge between end-user and the software development team. Planning, data collection, analysis, design, programming, testing, implementation, and maintenance processes are a few of the procedures used in software development.During the software development process, planning and requirement analysis carry a significant level of risks.A problem that begins during the requirement analysis phase of the SDLC will persist throughout the entire life cycle of the software, making it a crucial phase of the SDLC.When automated technologies are used in the requirement analysis process, then it reduces the cost and duration of software development. Natural Language Processing (NLP) helps to identify problems in user requirements.Software requirements are classified and identified using supervised classification methods like SVM, K-Nearest Neighbour, and Naive Bayes Algorithm with text vectorization techniques like BoW and TF-IDF.The main purpose of this chapter is to identify user requirement problems during requirement analysis and provide AI techniques to overcome these problems.

Software development is a fast-changing area. New methods and new technologies emerge all the time. As a result, the education of software engineering is generally considered not to be keeping pace with the development of software engineering in industry. Given the limited resources in academia, it is unrealistic to purchase all the latest software tools for classroom usage. In this chapter, the authors describe how free/open-source data and free/open-source tools are used in an upper-level software engineering class at Indiana University South Bend. Depending on different learning objectives, different free/open-source tools and free/open-source data are incorporated into different team projects. The approach has been applied for two semesters, where instructor’s experiences are assembled and analyzed. The study suggests (1) incorporating both free/open-source tools and free/open-source data in a software engineering course so that students can better understand both development methods and development processes and (2) updating software engineering course regularly in order to keep up with the advance of development tools and development methods in industry.