Coordinating distributed software development : a resource relationships perspective on analyzing the spatial effects

This paper analyzes how organizational culture is intertwined with usability work in software (SW) development organizations. Usability is an important quality characteristic of software products and systems. However, the development of usability is challenging in SW development. Organizational culture has been argued to affect usability work in SW development organizations, thus, this paper takes a culture-oriented approach in the analysis of usability work in two SW development organizations operating in the product development context. First, based on a literature review, a definition of usability work is offered. An interpretive view of organizational culture, acknowledging its recent critique, is then introduced and utilized in the empirical analysis. The empirical results suggest that differences exists in how usability work is modified and interpreted in the organizations with divergent cultural contexts, those advocating different motives and practices for usability work. Finally, the importance of understanding the cultural context into which usability work is introduced is emphasized, and it is argued that culturally compatible strategies to usability work should be adopted.

In recent years, agile software development methods have gained increasing popularity. Distributed software development have been becoming a common business reality also. Software development organizations are striving to blend agile development methods like Scrum and distributed development to reap the benefits of both. However, agile and distributed development approaches differ significantly in their key tenets. While agile methods mainly rely on informal processes to facilitate coordination, distributed development typically relies on formal mechanisms. This paper aims at implementing modular design of software products to identify feature clusters that can be implemented co-located to minimize the communication needs between distributed teams. Presented method is evaluated with simulations that demonstrate how this method can produce 1) lower-risk feasible plans, 2) balanced workload on teams, and 3) provide higher quality feature distributions. Finally, the paper analyzes benefits and issues from the use of this method.Keywordsdistributed software developmentagile release planning

The increasing demand for rapid software development has led to the growing use of code generators, which significantly accelerate the programming process. This study investigates the impact of code generators on programming resource needs by comparing the time required by programmers of varying skill levels to develop applications using three code generators PHPMaker, PHPRunner, and CakePH versus manual coding with Laravel. Results indicate that code generators allow programmers, regardless of experience, to produce applications more quickly than manual methods. Interestingly, even novice programmers using code generators outperform senior programmers coding manually. This research contributes to the field by providing a clearer understanding of the efficiency gains offered by code generators and suggesting their potential to optimize programming resources in software development. However, the study also highlights the need for future research to evaluate additional factors, such as application complexity and quality, to further refine resource estimation models like SLIM and COCOMO when integrating code generators into the software development process. Keywords: Code Generator, programming resource, software development

Age stereotypes in distributed software development: The impact of culture on age-related performance expectations

Reuse in Software Development Organizations in Latvia The paper presents the results of a survey, which aims to investigate the field of software reuse in software development organizations in Latvia. The topic has a particular significance since reuse may provide some economic benefits by reducing software development and operating costs, and by efficient utilization of development knowledge and corporate expertise. The objective of the study is to identify the key factors to be considered by the companies interested in establishing a software reuse program, thus improving time-to-market, costs and quality of software products by ingraining reuse into the entire software development process. Twenty factors organized into four categories were considered important within the framework of the survey. The results were obtained through the questionnaire involving software organizations in Latvia, whose responses were analyzed and used to relate the characteristics of organizations with their reuse experience. As a result, the influence of the selected factors on the success of the reuse is evaluated using four different levels (strong, weak, none, no data). Additionally, the paper includes review of related researches and comparison of the results. In conclusion, the author provides suggestions for the improvement of the reuse in Latvian software development organizations on the basis of the survey.

work of W. Edwards Deming has convinced industry that must first measure quality and then emphasise process to improve quality. In response to Deming's arguments and in light of perception that software industry is unable to produce quality products on schedule, and within budget, more software development organisations are now emphasising process measurement, monitoring, and assessment. This paper describes what is meant by software process and discusses an approach for its measurement and improvement. INTRODUCTION Unreliable software makes big news, from emergency services disasters to social security payment blunders. Improved software quality is essential to ensure reliable products and services, and gain customer satisfaction. While software development has existed for more than four decades, we failed so far to make as an industry and as an engineering discipline rather than craft. Developing reliable and usable software that is delivered on and within budget still represents difficult endeavour for many organisations. As role of software becomes increasingly critical for businesses as well as for human lives, problems caused by software products that are late, over budget, or that do not work, become magnified. If lives are lost or people inconvenienced due to incapable computer software, news media is there to make big stories. Organisations are realising that their fundamental problems is immaturity of their software process. Robert Lai (1993) proposes that process improvement is second maturity wave of software industry. He states that the first wave of software was developed using waterfall model in 1970's. Today we are Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 216 Software Management in midst of second wave maturity movement as we attempt to formally define development process and best ways to continuously improve it (Lai 1993). Taking lead in this area has been Watts Humphrey (Humphrey 1989, 1990, 1991), and Software Engineering Institute (SEI) at Carnegie Mellon University. SEI started in 1986 to develop process maturity framework to help organisations appraise maturity of their software process, and to provide guidance for organisations to improve their software process capability. A brief description of framework was released in September 1987, including maturity questionnaire. SEI evolved model and questionnaire into 5 -Level Capability Maturity Model (CMM) in 1991. In February 1993, released CMM version 1.1 (Paulk et al 1993). This paper discusses software process and describes capability maturity model (CMM). It also shows how CMM can be used as basis to measure maturity of software process of an organisation and plan its improvement. SOFTWARE QUALITY AND PROCESS IMPROVEMENT In his book Quality is Free Phil Crosby states that: Quality is free. It is not gift, is free. What cost money are unqualify of things all actions that involve not doing jobs right first time (Crosby 1980). If such statement is true for many disciplines, is particularly true for evidence is abundant in number of software products which exceeded their budget, were produced late, failed to satisfy user requirements, and are full of bugs. demand for improved software quality is increasing to ensure reliable products and services. benefits of improved quality comes in form of reduction in failure costs. For software projects failure costs include (DTI 1992): • costs of correcting defects, both before and after delivery • overruns against and budget • unnecessary high maintenance costs • indirect costs which users incur due to poor quality software link between process maturity and software quality is expressed in premise that The quality of software system is governed by quality of process used to develop and maintain it. One stumbling block to improving software quality seems to be that not enough attention is paid to overall development process itself. While software professionals typically devote their to developing, testing or documenting software products, no one has prime responsibility for improving software process. Experience has shown that if Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 Managing Systems 217 no one is working on software process, orderly improvement is unlikely. process certainly won't improve itself, rather, most likely, will deteriorate over time. Continuous improvement can occur only if process infrastructure is in place. Watts Humphrey argues in an early article published in Datamation, April 1989 that: Without work on process, there will be little or no progress in improving software. THE SOFTWARE PROCESS Adopting process view of software development represents revolutionary change in perspective. A process orientation to software development involves elements of structure, focus, measurement, ownership, skills, and supporting technology. In this section we investigate what is meant by software process. What Is Software Process According to Webster's dictionary, process is a system of operations in producing something .. series of actions, changes, or functions that achieve an end result. Chambers Concise Dictionary defines process as a series of actions or events .. sequence of operations or changes undergone. IEEE defines process as a sequence of steps performed for given purpose. In general business context, process is defined as a structured, measured set of activities designed to produce specified output for particular customer or market (Davenport 1993). These definitions put strong emphasis on HOW work is done, in contrast to product focus's emphasis on WHAT. Accordingly, process can be considered as a specific ordering of work activities across and place, with beginning, an end, and clearly identified inputs and outputs: structure for action. In this paper we will adopt following definitions quoted in (Humphrey 1990, Paulk et al 1993) are intended to encompass software throughout its life, which covers new development, enhancement, and repair. software process is The set of activities, methods, and practices used in production and evolution of software. software engineering process is The total set of software engineering activities needed to transform user's requirements into software. Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 218 Software Management People and Software Process Software development is still people-intensive activity. Talented people are most important element in any software organisation. Even if you get best people available, if they do not follow common process, if everyone wrote in different programming languages, used different conventions, or didn't co-ordinate their design and code changes with their peers, results will be chaos. Successful software organisations have learned that even best professionals need structured and disciplined environment in which to do cooperative work. Software organisations that do not establish such disciplines condemn their people to endless hours of repetitively solving technically trivial problems. obvious fact is that attracting best people is vital, but is also essential to support them with an effectively managed software process. Technology and Software Process Another myth is widespread belief that some technologically advanced tool or method will provide magic answer to software crisis. This is not only wrong, but is dangerous. Organisations which jumped on bandwagon of CASE tools, and ended up in failure and wasted and effort have learned their lesson hard way. Just ask yourself before introducing technology: What do I want to automate? In absence of defined, practised, and managed process, introducing automation can lead to increased chaos. There are several factors which limit effective use of software technology: an illdefined process, inconsistent process implementation, and poor process management. Software technology cannot be fully effective until these problems have been properly addressed. Need for Defined Process If no effort is made to define and enhance software development process across whole organisation, each software development project latches on to its own tools, methods, and practices with little guidance available on how to use them. This ad hoc approach will not be sufficient to tackle task of developing complex software systems. goal of software process management is to enable organisations to produce software that meets cost, schedules, and quality objectives. principles are same that underpins statistical process control-principles that have been successfully used in controlling scientific experiments and in high -volume manufacturing operations. Statistical concepts have been found to be just as applicable to software development as they are to production of manufactured goods such as motor cars. Applying such concepts will only be possible if there is defined and managed process. Software Process Models Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517

In large projects, software developers struggle with two sources of complexity - the complexity of the code itself, and the complexity of the process of producing it. Both of these concerns have been subjected to considerable research investigation, and tools and techniques have been developed to help manage them. However, these solutions have generally been developed independently, making it difficult to deal with problems that inherently span both dimensions. We describe Augur, a visualization tool that supports distributed software development processes. Augur creates visual representations of both software artifacts and software development activities, and, crucially, allows developers to explore the relationship between them. Augur is designed not for managers, but for the developers participating in the software development process. We discuss some of the early results of informal evaluation with open source software developers. Our experiences to date suggest that combining views of artifacts and activities is both meaningful and valuable to software developers.

Software development in a context where development locations are separated across geographical regions, either nearby or internationally, is quickly becoming a popular practice. This software development agreement is often mentioned as Global Software. "Global Software Development (GSD) is also known as Distributed Software Development (DSD) or Global Software Engineering (GSE)". Plans carried out by a scattered squad have been identified by way of a more dangerous and hard enterprise than projects carried out by teams working below a similar roof. As a result, considering the possible obstacles and appropriate mitigation techniques for GSD is critical for operating a successful project. Software development is divided into stages of requirements, analysis, designs, coding, and testing. The creation of software in globalized settings is frequent and significant in today's world of software development. This paper emphasizes the condition of software product transmission, which deals with software testing in an overseas site, as part of numerous globalized scenarios.

The maturation of the technical infrastructure has enabled the emergence and growth of distributed software development. This has created tempting opportunities for companies to distribute their software development, for example, to economically favourable countries so as to gain needed expertise or to get closer to customers. Nonetheless, such distribution potentially creates problems that need to be understood and addressed in order to make possible the gains offered. To clarify and understand the most difficult problems and their nature, a survey of individuals engaged in distributed software development was conducted. The purpose of this survey was to gather and share lessons learned in order to better understand the nature of the software development process when operating in a distributed software development environment and the problems that may be associated with such distributed processes. Through a clear appreciation of the risks associated with distributed development it becomes possible to develop approaches for the mitigation of these risks. This paper presents the results of the survey, focusing on the most serious problems raised by the respondents. Some practical guidelines that have been developed by industry to overcome these problems are also briefly summarized. Copyright © 2005 John Wiley & Sons, Ltd.

Uptake of HCI and usability engineering by software development organisations can be terminally impeded by lack of appreciation of the benefits of HCI activities. However, descriptions of HCI offerings in terms of activities (e.g. task analysis, user mapping, allocation of function, interaction design) and methods (e.g. user profiling, prototyping, GOMS modelling) do not convey to product managers a readily comprehensible conception of the value of such offerings. Similarly, descriptions of HCI activities and methods give little indication of how these are to be associated and managed with reference to stages and deliverables in a software development life cycle. This lack of clear association between usability engineering and software engineering contributes to the marginalisation of usability related activities. Even when investment is made in usability resources its eventual pay off can be minimal, with resulting disillusionment on both sides. Specification of usability deliverables can provide a solid basis for a manageable usability perspective on the development of software products. The article identifies usability deliverables and describes their content and relation to deliverables in a software design and development process. More general implications for an approach to the specification of quality processes for the creation of interactive software products are discussed.

In this paper, we present a management system for distributed software development in cloud computing environments, called DDMan. Cloud computing environments provide more flexibility than conventional computing environments. In particular, the platform as a service (PaaS) in cloud computing environments provides benefits for users in a variety of aspects, such as application design, development testing, software deployment, team collaboration, web service integration, database integration, and scalability. Although the process of distributed software development evolves and changes by a lot in the past decade, there are still some user needs remaining unsatisfied. For managing distributed software development in cloud computing systems, we present the DDMan system, which extends the WebSD model of distributed software development management. In DDMan, the interactions among the roles in the software development are precisely defined. In addition to the conventional web-based interface, the DDMan system also supports the interface for the Amazon cloud environment, which is an approach to a fully automatic service of distributed software development management in cloud computing environments.

Along the last decade, many companies started using Distributed Software Development (DSD). The distribution of the software development teams over the globe has become almost a rule in large companies. However, in this context, new problems arise, which mainly involve the physical and temporal distance among the participants. Some studies show that deploying a version control system to alleviate this problem is a big challenge for distributed teams. This paper presents a systematic mapping study about works about version control that focus on DSD. We found 29 studies related to DSD version control, published between 2002 and 2012. Using the systematically extracted data from these works, we present challenges, tools, and other solutions proposed to version control in DSD. These results can support practitioners and researchers to better understand and overcome the challenges related do DSD version control, and devise more effective solutions to improve version control in a distributed setting.

ABSTRACTDevOps is a collaborative software development process where practitioners work as a team to continuously develop, deploy, and deliver software. DevOps practices still need to be mature, and practitioners face numerous challenges while considering DevOps as a software development process. The mainstream research community has helped simplify the DevOps adoption process and eliminate complexities by developing DevOps maturity models. However, the current maturity frameworks cannot measure every component of DevOps and do not mention metrics as parameters for measuring different DevOps practices or features. Therefore, this study aims to identify metrics for measuring practices and activities responsible for DevOps implementation. The systematic literature review (SLR) method was used to determine the metrics needed to measure DevOps practices. Using SLR, we have identified 32 metrics from 57 articles. The metrics identified in this study can be used to measure the impact of the practices adopted for DevOps implementation within software development organizations. Furthermore, we divided the identified metrics into Dev and Ops categories and five significant categories based on the DevOps lifecycle. The classification of metrics in our study into diverse regions provides a conceptual framework and understanding of DevOps measures.

In todays world, software security has become essential for protecting the overall organizations operations. Mostly software development companies are adopting various strategies to build secure software to cope with the challenges of the client organization. Information become threatened due to connection with the cyber world, and it requires better security mechanisms. Software development organizations are receiving pressure from their clients to focus on the enhancement of security during the whole software development life cycle (SDLC). This protocol aims to review the literature in a systematic way to identify the state-of-the-art of software security to be considered by Global Software Development (GSD) vendor organizations during the development of a secure software as it evolves from requirements engineering to its final disposal. In order to improve security processes in the context of software development, our current research developed a Systematic Mapping Study (SMS) protocol. Presently, we are in the implementation phase of the protocol for the development of secure software. The expected outcomes of this SMS will be a list of security measurements and their solutions to be incorporated by GSD vendor organizations in each phase of the SDLC. This will also give a direction for new research in this area.

The geographically distributed software development has attained a significant attraction in software development industry since last few decades due to its wide acceptance across the globe. The main essence of geographically distributed software development is to expand company working by follow-the-sun strategy, get skilled labors at cheaper rates from low economy regions of world and pool-up company resources to raise their utilization graph. The requirements elicitation process is considered as one of the most challenging tasks during software development process in traditional as well as geographically distributed software development projects due to its social and collaborative nature. This article presents a comprehensive insight about major challenges faced by requirements elicitation teams engaged in geographically distributed software development projects. The article also elaborates the possible strategies, which can be adopted to minimize the negative impact of geological distribution of software development activities. The presented study will help the requirements elicitation teams to better plane their requirements elicitation sessions for geological distributed software development projects by encountering the expected hurdles.