Software developer policies : economics and s 46 of the Competition and Consumer Act 2010

This article considers the impact of developer policies that hinder or restrict cross platform application development. We suggest that policies that hinder or restrict cross platform development have the potential to erode competition within the market for smartphones. The article also considers the relevance of dominance measures in software markets, arguing that conventional economic approaches may not be applicable. Furthermore, while most monitoring activities tend to focus primarily on protection of consumers, the article points out that modern electronic/information technology markets are multi-sided and there is a need for monitoring of practices designed to attract and retain the favour of developers. While the article is written in the context and application of the applicable Australian legislation, this being s 46 of the Competition and Consumer Act 2010 (Cth), our findings are equally relevant to other jurisdictions.

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.

Cross-platform urine metabolomics of experimental hyperglycemia in type 2 diabetes

Hyperglycemia causes diabetic nephropathy, a condition for which there are no specific diagnostic markers thatpredict progression to renal failure. Here we describe a multiplatform metabolomic analysis of urine from individualswith type 2 diabetes, collected before and immediately following experimental hyperglycemia. We used targetednuclear magnetic resonance spectroscopy (NMR), liquid chromatography - mass spectrometry (LC-MS) and gaschromatography - MS (GC-MS) to identify markers of hyperglycemia. Following optimization of data normalisation andstatistical analysis, we identified a reproducible NMR and LC-MS based urine signature of hyperglycemia. Significantincreases of alanine, alloisoleucine, isoleucine, leucine, N-isovaleroylglycine, valine, choline, lactate and taurine anddecreases of arginine, gamma-aminobutyric acid, hippurate, suberate and N-acetylglutamate were observed. GC-MSanalysis identified a number of metabolites differentially present in post-glucose versus baseline urine, but these could not be identified using current metabolite libraries. This analysis is an important first step towards identifying biomarkers of early-stage diabetic nephropathy.

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.

Benchmark generation algorithm for stochastic mixed model assembly shop simulation and optimization

The Operations Research (OR) community have defined many deterministic manufacturing control problems mainly focused on scheduling. Well-defined benchmark problems provide a mechanism for communication of the effectiveness of different optimization algorithms. Manufacturing problems within industry are stochastic and complex. Common features of these problems include: variable demand, machine part specific breakdown patterns, part machine specific process durations, continuous production, Finished Goods Inventory (FGI) buffers, bottleneck machines and limited production capacity. Discrete Event Simulation (DES) is a commonly used tool for studying manufacturing systems of realistic complexity. There are few reports of detail-rich benchmark problems for use within the simulation optimization community that are as complex as those faced by production managers. This work details an algorithm that can be used to create single and multistage production control problems. The reported software implementation of the algorithm generates text files in eXtensible Markup Language (XML) format that are easily edited and understood as well as being cross-platform compatible. The distribution and acceptance of benchmark problems generated with the algorithm would enable researchers working on simulation and optimization of manufacturing problems to effectively communicate results to benefit the field in general.

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.