Global software development : the next RE frontier?

Requirements Engineers face an emerging set of challenges, which compound the traditional Requirements Engineering (RE) challenges (stakeholder identification, domain expertise, communication, analytic skills, problem solving, ...) that have arguably still not been fully addressed. This is the challenge of RE in the world of global software development, with requirements teams working in virtual mode (possibly on different continents), with the software having to operate in multiple contexts, addressing the needs of different cultures and legal jurisdictions, and having to build sales in different marketplaces. Further the need arises to specify software that is progressively enhanced through regular releases, rather than the “green field” specification of products.

This theoretical paper introduces these challenges, and presents an initial selection of theoretical models, drawn from many and varied source disciplines, which might be employed to gain insight into various features of RE in support of global software development. To illustrate the potential relevance of this selection of models, a longitudinal case study with a recently identified software developer, to follow the specification and subsequent roll-out of a future release of a software product for sale globally, is introduced. Features of the situation faced by that organisation are highlighted, to illustrate the potential relevance of the diverse models that have been identified.

Requirements engineering during global software development : some impediments to the requirements engineering process : a case study

Requirements engineering is not straightforward for any software development team. Developing software when team members are located in widely distributed geographic locations poses many challenges for developers, particularly during the requirements engineering phase. This paper reports on a case study concerning a large software development project that was completed in just seven months between users located in the UK and software developers from an international software house based in New Zealand. The case indicates that while “true” global requirements engineering may be desirable in achieving economy of resources, a “hybrid” structure of requirements engineering processes is more realistic so that lasting relationships with clients may be formed, and requirements engineering activities achieved. The main impediment to the process of requirements engineering during global software development, as recounted by the team members in this case, is communication. Communication issues may be further described in terms of four categories: distribution of the clients and the development team, distribution of the development team, cultural differences between the clients and the development team and cultural differences among the development team.

Exploring the influences on requirements engineering during global software development

Through an interpretive study of global virtual teams, this research has explored the influences on the requirements engineering processes during global software development. Complex layers of explicit and implicit elements in the project environment, including systems methodology, project steering, management commitment and cultural differences, were found to influence these processes.

Exploring the sociotechnical systems perspectives in global software development

Global software development teams expressed dissatisfaction with their structures. Job satisfaction was reduced by the inefficiencies of communication technologies and from the functional structures imposed by the management. This led to a reduced contextual understanding of projects which could be improved if employees were to participate in the work designs.

A taxonomy of dependencies in agile software development

Dependencies in a software project can contribute to unsatisfactory progress if they constrain or block the flow of work. Various studies highlight the importance of dependencies in the organisation of work; however dependencies in agile software development projects have not previously been a research focus. Drawing on three case studies of agile software projects, and the IS literature, this paper develops an initial taxonomy of agile software project dependencies. Three distinct categories of dependency are found: task, resource, and knowledge dependencies. This paper contributes to theory by providing a taxonomy of dependency types occurring in the area of agile software development. Practitioners can use this taxonomy as sensitising device to ensure they consider dependencies they might face that could hinder their projects, enabling them to take appropriate and timely mitigating action.

Global software development : measuring, approximating and reducing the complexity of global software development using extended axiomatic design theory

This paper considers GSD projects as designed artefacts, and proposes the application of an Extended Axiomatic Design theory to reduce their complexity in order to increase the probability of project success. Using an upper bound estimation of the Kolmogorov complexity of the so-called ‘design matrix’ (as a proxy of Information Content as a complexity measure) we demonstrate on two hypothetical examples how good and bad designs of GSD planning compare in terms of complexity. We also demonstrate how to measure and calculate the ‘structural’ complexity of GSD projects and show that by satisfying all design axioms this ‘structural’ complexity could be minimised.

Software warehouse: its design management and application

To have an effective and efficient mechanism to store, manage and utilize software sources is essential to the automation of software engineering. The paper presents an innovative approach in managing software resources using software warehouse where software assets are systematically accumulated, deposited, retrieved, packaged, managed and utilized, driven by data-mining and OLAP technologies. The results lead to streamlined high efficient software development process and enhance the productivity in response to modern challenges of the design and development of software applications.

Knowledge mediation in software quality engineering

The risk of failure of the software development process remains high despite many attempts to improve the quality of software engineering. Contemporary approaches to process assurance, such as the capability maturity model have not prevented systemic failures, nor have project management methodologies provided guarantees of software quality. The paper proposes an approach to software quality assurance based on a knowledge mediated concurrent audit, which incorporates essential feedback processes. Through a tightly integrated approach to quality audit, programmers would be empowered to use any chosen methodology to advantage, supported by intelligent monitoring of the essential interactions which occur in the development process. An experimental application implementing some aspects of the proposal is described

Foundation software engineering practices for capstone projects and beyond

This paper outlines an introductory course in software engineering undertaken by computing students at Deakin University. The course focuses on areas of that are often not emphasized in introductory software engineering. These areas include formal problem solving, management of software development, communication, and working in groups. The approach includes the application of concepts in a collaborative group setting. Enhancements to the course have been made over a number of semesters and evidence suggests that our overall approach is working. The skills acquired by students taking this course can be applied to later courses in software engineering, particularly the capstone project course, and to professional life

Automatic refinement of user requirements : a case study in software tool evaluation

This paper presents an assessment of system effectiveness in automatic requirements refinement by comparing results obtained from experts and novices with those achieved by the system. As the investigated system was a combination of a tightly inter-connected methods and a tool, the evaluation framework melded together a number of distinct methodological approaches structured into three empirical studies, which aimed at the construction of a case problem domain, calibrating the system using this defined domain elements and finally using the calibrated system to assess its effectiveness. In consequence, it was concluded that the evaluated methods and tools were effective in supporting requirements refinement.

Software warehouse and software mining : the impact of data mining to software engineering

Automating Software Engineering is the dream of software Engineers for decades. To make this dream to come to true, data mining can play an important role. Our recent research has shown that to increase the productivity and to reduce the cost of software development, it is essential to have an effective and efficient mechanism to store, manage and utilize existing software resources, and thus to automate software analysis, testing, evaluation and to make use of existing software for new problems. This paper firstly provides a brief overview of traditional data mining followed by a presentation on data mining in broader sense. Secondly, it presents the idea and the technology of software warehouse as an innovative approach in managing software resources using the idea of data warehouse where software assets are systematically accumulated, deposited, retrieved, packaged, managed and utilized driven by data mining and OLAP technologies. Thirdly, we presented the concepts and technology and their applications of data mining and data matrix including software warehouse to software engineering. The perspectives of the role of software warehouse and software mining in modern software development are addressed. We expect that the results will lead to a streamlined high efficient software development process and enhance the productivity in response to modern challenges of the design and development of software applications.

Using the sociotechnical approach in global software developments : Is the theory relevant today?

Global software development teams are highly dependent on technology for daily activities and production. Researchers have investigated the areas such as communication and time-zone difficulties when working across global boundaries during the last decade. However, this research explores job satisfaction, efficiency and the quality of working life of people working in a medium sized globally distributed software development organisation. It is assumed that the work structures of organisations of today are influenced by the theories from the past. This paper focus upon the issues that faces an Australian organisation involved in global software development, the research compares and contrasts the feelings of the employees using a Sociotechnical approach. The discussion highlights several problems areas specific to the organisation which will lay the foundation for future research.

Critical success factors for the requirements engineering process, with reference to quality management of information systems development

Preliminary research into the critical factors associated with software development/implementation identified three dimensions for successful implementation based on alignment of the requirements engineering process with business needs, change management process and quality of the implementation process. Research results demonstrate the link between the conceptual model for process quality and the process management attributes determined during the research.