Innovation among different classes of software development organizations

Software development organizations (SDOs) innovate in diverse ways. In this paper, based on an extensive review of innovation typologies, we develop a theory‐driven typology of SDO innovator classes. We theorize about the driving forces behind these classes, with specific attention given to knowledge‐based dispositions that relate to the SDO's knowledge‐based competencies in technology appropriation, technology generation, and network intensity within ecological niches. Through a survey of 136 SDOs, which adopted Internet technologies during 1995‐2006, we empirically verify that these classes also determine different ways that SDOs innovate around software services they provide to their clients. Our findings suggest that the knowledge‐based dispositions of different SDO innovator classes impact how they innovate. Overall, the study involves theorizing around different types of innovation behaviours and associated knowledge‐based factors that influence the way SDOs innovate.     

Measuring the ROI of software process improvement

Software process improvement has been on the agenda of both academics and practitioners, with the Capability Maturity Model as its de facto method. Many companies have invested large sums of money in improving their software processes, and several research papers document SPI's effectiveness. SPI aims to create more effective and efficient software development and maintenance by structuring and optimizing processes. SPI assumes that a well-managed organization with a defined engineering process is more likely to produce products that consistently meet the purchaser's requirements within schedule and budget than a poorly managed organization with no such engineering process. We discuss about the measuring the ROI in software process improvement.     

ICT-supported knowledge representation for development of routines in industry

Organizational Learning (OL) is important for a firm’s productivity growth. According to some literatures, information and communication technology do not support organizational learning and therefore not enhanced productivity. This research however has demonstrated that in the case of manufacturing companies some computer-based systems representing organizational knowledge—knowledge management systems (KMS) do support organizational learning. For OL to take place through KMS, our findings suggest that a deliberate organizational learning structure must be in place within the organization. This article demonstrates how knowledge management systems deliberately developed and implemented by management, can support the development of operating routines for manufacturing industries. KMS, if deliberately implemented for the purpose of empowering employee participation, may be a supporting mechanism for process and product improvement and innovation in manufacturing organizations. Such a structure may results, as our case demonstrates, in a dynamic and iterative employee—management knowledge development process resulting in productivity enhancement.     

Assessment methodology for software process improvement in small organizations

ContextDiagnosing processes in a small company requires process assessment practices which give qualitative and quantitative results; these should offer an overall view of the process capability. The purpose is to obtain relevant information about the running of processes, for use in their control and improvement. However, small organizations have some problems in running process assessment, due to their specific characteristics and limitations.ObjectiveThis paper presents a methodology for assessing software processes which assist the activity of software process diagnosis in small organizations. There is an attempt to address issues such as the fact that: (i) process assessment is expensive and typically requires major company resources and (ii) many light assessment methods do not provide information that is detailed enough for diagnosing and improving processes.MethodTo achieve all this, the METvalCOMPETISOFT assessment methodology was developed. This methodology: (i) incorporates the strategy of internal assessments known as rapid assessment, meaning that these assessments do not take up too much time or use an excessive quantity of resources, nor are they too rigorous and (ii) meets all the requirements described in the literature for an assessment proposal which is customized to the typical features of small companies.ResultsThis paper also describes the experience of the application of this methodology in eight small software organizations that took part in the COMPETISOFT project. The results obtained show that this approach allows us to obtain reliable information about the strengths and weaknesses of software processes, along with information to companies on opportunities for improvement.ConclusionThe assessment methodology proposed sets out the elements needed to assist with diagnosing the process in small organizations step-by-step while seeking to make its application economically feasible in terms of resources and time. From the initial application it may be seen that this assessment methodology can be useful, practical and suitable for diagnosing processes in this type of organizations.     

CIP-UQIM: A unified model for quality improvement in software SME's based on CMMI level 2 and 3

ContextSoftware Process Improvement (SPI) is among the most effective ways to improve the quality of software products and services. Despite many research and industrial reports, SPI planning and implementation in Multi-Model Environments (MMEs) still face various issues and difficulties which increase the risk of failure especially for Small and Medium size Enterprises (SMEs). As a popular approach, harmonization techniques are used to meet the MME's specific issues through recognizing the common or similar areas among the implemented models and developing an integrated solution for quality improvement throughout the organization.ObjectiveThis paper has two main objectives: (1) recognizing the set of most popular models used in worldwide harmonization projects and implemented or requested by Iranian software SMEs. (2) Comparing and integrating these models in Process Activity level to develop a unified quality improvement model.MethodA combination of literature review and questionnaire methods was used to identify the set of the most popular models. Then, based on harmonization techniques the common or similar areas among these models are recognized and then an initial version of the Unified Quality Improvement Model (UQIM) is developed, named CIP-UQIM. Next, this initial model was presented in a two-day workshop for SPI experts and it was refined and finalized by incorporating their feedbacks.ResultsInvestigations showed that the set {CMMI-DEV, ISO 9001, and PMBOK} was the most popular. Thus in CIP-UQIM, for the first time, the last version of these models was unified at the activity level details. Finally, the experience of using CIP-UQIM in an Iranian SME has been reported which demonstrate its applicability and advantages.ConclusionConsidering the high similarity among the three models and CIP-UQIM level of details, it can be concluded that CIP-UQIM can be beneficial to resolve or reduce SPI issues in MME's, especially in case of software SMEs.     

Software process modeling languages: A systematic literature review

ContextOrganizations working in software development are aware that processes are very important assets as well as they are very conscious of the need to deploy well-defined processes with the goal of improving software product development and, particularly, quality. Software process modeling languages are an important support for describing and managing software processes in software-intensive organizations.ObjectiveThis paper seeks to identify what software process modeling languages have been defined in last decade, the relationships and dependencies among them and, starting from the current state, to define directions for future research.MethodA systematic literature review was developed. 1929 papers were retrieved by a manual search in 9 databases and 46 primary studies were finally included.ResultsSince 2000 more than 40 languages have been first reported, each of which with a concrete purpose. We show that different base technologies have been used to define software process modeling languages. We provide a scheme where each language is registered together with the year it was created, the base technology used to define it and whether it is considered a starting point for later languages. This scheme is used to illustrate the trend in software process modeling languages. Finally, we present directions for future research.ConclusionThis review presents the different software process modeling languages that have been developed in the last ten years, showing the relevant fact that model-based SPMLs (Software Process Modeling Languages) are being considered as a current trend. Each one of these languages has been designed with a particular motivation, to solve problems which had been detected. However, there are still several problems to face, which have become evident in this review. This let us provide researchers with some guidelines for future research on this topic.     

BPMNt: A BPMN extension for specifying software process tailoring

ContextAlthough SPEM 2.0 has great potential for software process modeling, it does not provide concepts or formalisms for precise modeling of process behavior. Indeed, SPEM fails to address process simulation, execution, monitoring and analysis, which are important activities in process management. On the other hand, BPMN 2.0 is a widely used notation to model business processes that has associated tools and techniques to facilitate the aforementioned process management activities. Using BPMN to model software development processes can leverage BPMN’s infrastructure to improve the quality of these processes. However, BPMN lacks an important feature to model software processes: a mechanism to represent process tailoring.ObjectiveThis paper proposes BPMNt, a conservative extension to BPMN that aims at creating a tailoring representation mechanism similar to the one found in SPEM 2.0.MethodWe have used the BPMN 2.0 extensibility mechanism to include the representation of specific tailoring relationships namely suppression, local contribution, and local replacement, which establish links between process elements (such as in the case of SPEM). Moreover, this paper also presents some rules to ensure the consistency of BPMN models when using tailoring relationships.ResultsIn order to evaluate our proposal we have implemented a tool to support the BPMNt approach and have applied it for representing real process adaptations in the context of an academic management system development project. Results of this study showed that the approach and its support tool can successfully be used to adapt BPMN-based software processes in real scenarios.ConclusionWe have proposed an approach to enable reuse and adaptation of BPMN-based software process models as well as derivation traceability between models through tailoring relationships. We believe that bringing such capabilities into BPMN will open new perspectives to software process management.     

Software Process Improvement barriers: A cross-cultural comparison

ContextSoftware Process Improvement initiatives have been around for many years with the growing globalisation of software development is making them increasingly important.ObjectiveThe objective of this exploratory research is to gain an in-depth understanding of barriers that can undermine SPI, in the context of Global Software Development, from the perspective of software development practitioners; this will enable SPI managers to better manage SPI initiatives. We intend to discover if the barriers to SPI initiatives in a developed country are different to those in a developing country.MethodIn an empirical study, Vietnamese software practitioners’ experiences of SPI barriers are compared with barriers identified by Australian practitioners. Face-to-face questionnaire-based survey sessions with 23 Vietnamese SPI practitioners were conducted. Our survey included barriers to SPI improvement initiatives identified in previous research. We asked the participants to rank each SPI barrier on a three-point scale (high, medium, low) to determine the importance of each barrier. We then compare our results, with results (identified in previous work), from 34 Australian software development practitioners.ResultsWe identify (1) lack of project management, (2) lack of resources, (3) lack of sponsorship, (4) inexperienced staff/lack of knowledge, and (5) lack of SPI awareness as ‘high’ value SPI barriers in Vietnam. The results also reveal similarities and differences between the experiences of Australian and Vietnamese practitioners regarding the importance of the SPI barriers identified. While the Australian practitioners were also concerned with (1) lack of SPI awareness, they were even more concerned with (2) organisational politics, and (3) lack of support.ConclusionsPractitioners identify SPI barriers based on previous SPI implementation experience. Their role(s) in their different organisations have helped them to understand the importance of that barrier. Vietnamese software practitioners cited more SPI barriers than their counterparts in Australia. The Vietnamese SPI barriers relate to project management, resources, and sponsorship while the Australian barriers are concerned with organisational politics and lack of support.     

Associations between technological scaffolding and micro-level processes of self-regulated learning: A workplace study

This paper reports the results of a study of the association of a set of technological scaffolding interventions – implemented in a learning software called Learn-B – with micro-level processes of self-regulated learning in the workplace. The study was conducted in the context of two European organizations, in which the study participants (N = 53) used the learning software Learn-B for two months in their regular activities. Data about perceived usefulness of the technological scaffolding interventions and traces about the events of the actual use of the technological interventions and micro-level processes of self-regulated learning were collected and analyzed. The analysis of the data showed that when directly asked about their own perspectives, the participants tended to rely on their organizational context in their planning phase. The results also indicate that the participants did consider the social context of their organization when planning their learning goals, but it was not found as the most influential factor. The analysis of the trace data revealed a moderate balance between reliance on both social and organizational contexts. The analysis of the theorized contingencies via trace data showed that the participants’ usefulness perceptions of the proposed interventions for their self-regulated processes, poorly matched with their actual learning actions.     

IT Service Management Process Improvement based on ISO/IEC 15504: A systematic review

Context

In recent years, many software companies have considered Software Process Improvement (SPI) as essential for successful software development. These companies have also shown special interest in IT Service Management (ITSM). SPI standards have evolved to incorporate ITSM best practices.

Objective

This paper presents a systematic literature review of ITSM Process Improvement initiatives based on the ISO/IEC 15504 standard for process assessment and improvement.

Method

A systematic literature review based on the guidelines proposed by Kitchenham and the review protocol template developed by Biolchini et al. is performed.

Results

Twenty-eight relevant studies related to ITSM Process Improvement have been found. From the analysis of these studies, nine different ITSM Process Improvement initiatives have been detected. Seven of these initiatives use ISO/IEC 15504 conformant process assessment methods.

Conclusion

During the last decade, in order to satisfy the on-going demand of mature software development companies for assessing and improving ITSM processes, different models which use the measurement framework of ISO/IEC 15504 have been developed. However, it is still necessary to define a method with the necessary guidelines to implement both software development processes and ITSM processes reducing the amount of effort, especially because some processes of both categories are overlapped.     

Towards a theoretical framework of SPI success factors for small and medium web companies

ContextThe context of this research is software process improvement (SPI) success factors for small and medium Web companies.ObjectiveThe primary objective of this paper is to propose a theoretical framework of SPI success factors for small and medium Web companies.MethodThe theoretical framework presented in this study aggregated the results of three previous research phases by applying principles of theoretical integration and comparative analysis. Those three previous phases were all empirical in nature, and comprise: a systematic review of SPI in small and medium Web companies [1], [2]; a replication study [3] and a grounded theory-based initial exploratory framework of factors in small and medium Web companies [4].ResultsThe theoretical framework includes 18 categories of SPI success factors, 148 properties of these categories and 25 corresponding relationships, which bind these categories together. With the help of these relationships, the categories and properties of SPI success factors can be directly translated into a set of guidelines, which can then be used by the practitioners of small and medium Web companies to improve the current state of SPI in their companies and achieve overall company success.ConclusionThe comprehensive theoretical framework of SPI success factors presented herein provides evidence regarding key factors for predicting SPI success for small and medium Web companies. The framework can be used as a baseline for a successful implementation of SPI initiatives in the mentioned domain.     

Comparative case studies of open source software peer review practices

ContextThe power of open source software peer review lies in the involvement of virtual communities, especially users who typically do not have a formal role in the development process. As communities grow to a certain extent, how to organize and support the peer review process becomes increasingly challenging. A universal solution is likely to fail for communities with varying characteristics.ObjectiveThis paper investigates differences of peer review practices across different open source software communities, especially the ones engage distinct types of users, in order to offer contextualized guidance for developing open source software projects.MethodComparative case studies were conducted in two well-established large open source communities, Mozilla and Python, which engage extremely different types of users. Bug reports from their bug tracking systems were examined primarily, complemented by secondary sources such as meeting notes, blog posts, messages from mailing lists, and online documentations.ResultsThe two communities differ in the key activities of peer review processes, including different characteristics with respect to bug reporting, design decision making, to patch development and review. Their variances also involve the designs of supporting technology. The results highlight the emerging role of triagers, who bridge the core and peripheral contributors and facilitate the peer review process. The two communities demonstrate alternative designs of open source software peer review and their tradeoffs were discussed.ConclusionIt is concluded that contextualized designs of social and technological solutions to open source software peer review practices are important. The two cases can serve as learning resources for open source software projects, or other types of large software projects in general, to cope with challenges of leveraging enormous contributions and coordinating core developers. It is also important to improve support for triagers, who have not received much research effort yet.     

Understanding the implementation of software process improvement innovations in software organizations

Abstract. The development of software is a complex task frequently resulting in unfinished projects, project overruns and system failures. Software process improvement (SPI) approaches have been promoted as a promising remedy for this situation. The organizational implementation of such approaches is a crucial issue and attempts to introduce SPI into software organizations often fail. This paper presents a framework to understand, and subsequently successfully perform, the implementation of SPI innovations in software organizations. The framework consists of three perspectives on innovation: an individualist, a structuralist and an interactive process perspective. Applied to SPI, they emphasize different aspects of implementing SPI innovations. While the first focuses on leadership, champions and change agents, the second focuses on organization size, departmental and task differentiation and complexity, and the third perspective views the contents of the innovation, the social context and process of the implementation as related in an interactive process. We demonstrate the framework's applicability through two cases. We show that the three perspectives supplement each other and together provide a deeper understanding of the implementation process. Such understanding is crucial for the successful uptake of SPI approaches in software organizations.     

SECOL: a semantic environment based on social media to support organisational learning

Organisational learning (OL) helps companies to significantly improve their processes through the reuse of experiences, making knowledge accessible to the whole organisation. However, establishing learning in software development companies is not a trivial task, since it is an area in which processes and knowledge are usually hidden inside the employees’ mind. Generally, employees prefer to look for knowledge via Internet search engines rather than using the knowledge produced inside the company. Hence, we explored how better organising content produced within the company may minimise this problem. We investigated how a semantic collaborative environment, titled semantic collaborative environment for organisational learning (SECOL), based on social software, learning objects (LOs), and units of learning (UL) may assist to improve OL for software development companies. We defined an approach to generate LOs and UL from social software’s content used by companies. The environment was implemented based on ontologies in order to represent and organise acquired knowledge. Furthermore, an experiment was conducted using qualitative data analysis. The results indicated that the use of the environment is appropriate to improve OL in software development teams and the use of SECOL is efficient, particularly in order to acquire new knowledge, assisting the promotion of the use of organisational patterns and minimising repeated solutions.     

VIVACE: A framework for the systematic evaluation of variability support in process-aware information systems

ContextThe increasing adoption of process-aware information systems (PAISs) such as workflow management systems, enterprise resource planning systems, or case management systems, together with the high variability in business processes (e.g., sales processes may vary depending on the respective products and countries), has resulted in large industrial process model repositories. To cope with this business process variability, the proper management of process variants along the entire process lifecycle becomes crucial.ObjectiveThe goal of this paper is to develop a fundamental understanding of business process variability. In particular, the paper will provide a framework for assessing and comparing process variability approaches and the support they provide for the different phases of the business process lifecycle (i.e., process analysis and design, configuration, enactment, diagnosis, and evolution).MethodWe conducted a systematic literature review (SLR) in order to discover how process variability is supported by existing approaches.ResultsThe SLR resulted in 63 primary studies which were deeply analyzed. Based on this analysis, we derived the VIVACE framework. VIVACE allows assessing the expressiveness of a process modeling language regarding the explicit specification of process variability. Furthermore, the support provided by a process-aware information system to properly deal with process model variants can be assessed with VIVACE as well.ConclusionsVIVACE provides an empirically-grounded framework for process engineers that enables them to evaluate existing process variability approaches as well as to select that variability approach meeting their requirements best. Finally, it helps process engineers in implementing PAISs supporting process variability along the entire process lifecycle.     

Enhancing instructional outcomes with gamification: An empirical test of the Technology-Enhanced Training Effectiveness Model

BackgroundGamification, the use of game elements in non-game contexts, has become a popular technique to improve instructional outcomes in both organizational and educational contexts. In the organizational context, the Technology-Enhanced Training Effectiveness Model [TETEM] provides a framework to understand how technologies, like gamification, can effect change in various instructional outcomes. Specifically, application of TETEM suggests that gamification may not effect change in instructional outcomes when learner attitudes towards game-based learning and experience with video games are low.MethodIn this study, we test this model in the gamification context by assigning potential learners to read scenarios describing gamified instruction or traditional, PowerPoint instruction in a random order and assessing their training valence.ResultsOn average, participants anticipated greater value from gamified instruction, but as predicted by TETEM, this effect was moderated by both video game experience and attitudes towards game-based learning. Among potential learners with high experience and attitudes, gamification produces better outcomes than PowerPoint, but among potential learners with low experience and attitudes, gamification produces worse outcomes than PowerPoint.ImplicationsWe provide empirical support for TETEM and conclude that for gamification to be successful, the attitudes and experience of participants must be assessed and ensured before gamification is implemented.     

A systematic review of machine learning techniques for software fault prediction

BackgroundSoftware fault prediction is the process of developing models that can be used by the software practitioners in the early phases of software development life cycle for detecting faulty constructs such as modules or classes. There are various machine learning techniques used in the past for predicting faults.MethodIn this study we perform a systematic review of studies from January 1991 to October 2013 in the literature that use the machine learning techniques for software fault prediction. We assess the performance capability of the machine learning techniques in existing research for software fault prediction. We also compare the performance of the machine learning techniques with the statistical techniques and other machine learning techniques. Further the strengths and weaknesses of machine learning techniques are summarized.ResultsIn this paper we have identified 64 primary studies and seven categories of the machine learning techniques. The results prove the prediction capability of the machine learning techniques for classifying module/class as fault prone or not fault prone. The models using the machine learning techniques for estimating software fault proneness outperform the traditional statistical models.ConclusionBased on the results obtained from the systematic review, we conclude that the machine learning techniques have the ability for predicting software fault proneness and can be used by software practitioners and researchers. However, the application of the machine learning techniques in software fault prediction is still limited and more number of studies should be carried out in order to obtain well formed and generalizable results. We provide future guidelines to practitioners and researchers based on the results obtained in this work.     

Analyzing an automotive testing process with evidence-based software engineering

ContextEvidence-based software engineering (EBSE) provides a process for solving practical problems based on a rigorous research approach. The primary focus so far was on mapping and aggregating evidence through systematic reviews.ObjectivesWe extend existing work on evidence-based software engineering by using the EBSE process in an industrial case to help an organization to improve its automotive testing process. With this we contribute in (1) providing experiences on using evidence based processes to analyze a real world automotive test process and (2) provide evidence of challenges and related solutions for automotive software testing processes.MethodsIn this study we perform an in-depth investigation of an automotive test process using an extended EBSE process including case study research (gain an understanding of practical questions to define a research scope), systematic literature review (identify solutions through systematic literature), and value stream mapping (map out an improved automotive test process based on the current situation and improvement suggestions identified). These are followed by reflections on the EBSE process used.ResultsIn the first step of the EBSE process we identified 10 challenge areas with a total of 26 individual challenges. For 15 out of those 26 challenges our domain specific systematic literature review identified solutions. Based on the input from the challenges and the solutions, we created a value stream map of the current and future process.ConclusionsOverall, we found that the evidence-based process as presented in this study helps in technology transfer of research results to industry, but at the same time some challenges lie ahead (e.g. scoping systematic reviews to focus more on concrete industry problems, and understanding strategies of conducting EBSE with respect to effort and quality of the evidence).