Kevin Vinsen

The SKA software will most probably be developed by many groups distributed across the globe and coming from dierent backgrounds, like industries and research institutions. The SKA software subsystems will have to cover a very wide range of dierent areas, but still they have to react and work together like a single system to achieve the scientic goals and satisfy the challenging data ow requirements. Designing and developing such a system in a distributed fashion requires proper tools and the setup of an environment to allow for ecient detection and tracking of interface and integration issues in particular in a timely way. Agile development can provide much faster feedback mechanisms and also much tighter collaboration between the customer (scientist) and the developer. Continuous integration and continuous deployment on the other hand can provide much faster feedback of integration issues from the system level to the subsystem developers. This paper describes the results obtained ...

ABSTRACT The immense scale of data from modern radio interferometer arrays results in processing demands requiring HPC facilities to produce scientific results. However, in the modern era such facilities are more complex than a single monolithic HPC system. The transfer and processing of scientific data must be managed across hierarchies of storage and processing architectures; including traditional HPC, heterogeneous HPC, database and visualisation systems. The ICRAR Data Intensive Research Pathfinder (DIRP) will consist of an integrated system of the hardware, middleware, tools and interfaces to support ICRAR data intensive research primarily focused on data owing from the Australian SKA Pathfinder (ASKAP1) and the Murchison Widefield Array (MWA) telescopes.

ABSTRACT The SKA software will most probably be developed by many groups distributed across the globe and coming from dierent backgrounds, like industries and research institutions. The SKA software subsystems will have to cover a very wide range of dierent areas, but still they have to react and work together like a single system to achieve the scientic goals and satisfy the challenging data ow requirements. Designing and developing such a system in a distributed fashion requires proper tools and the setup of an environment to allow for ecient detection and tracking of interface and integration issues in particular in a timely way. Agile development can provide much faster feedback mechanisms and also much tighter collaboration between the customer (scientist) and the developer. Continuous integration and continuous deployment on the other hand can provide much faster feedback of integration issues from the system level to the subsystem developers. This paper describes the results obtained from trialing a potential SKA development environment based on existing science software development processes like ALMA, the expected distribution of the groups potentially involved in the SKA development and experience gained in the development of large scale commercial software projects.

... Parallel GAs for Multiobjective Functions Jon Rowe, Kevin Vinsen, and Nick Marvin ... If d1 (xi; xj) is the Hamming distance between any two population members xi and xj, and d2 (xi; xj) is a measure of tness distance then a sharing function can be de ned as follows: s(xi; xj) = ...

Abstract This paper presents different approaches to fully autonomous exploration of unknown terrain for individual as well as groups of mobile robots. All algorithms have been tested on a simulation environment and verified on the real robot platform WAMbot, the ...

The construction of the SKA and its pathfinders puts significant computational and power consumption constraints on the design of the computer hardware. However, hardware is only one aspect of the problem space, even if extremely fast and power efficient computers were available today, we still could not process the data coming from the SKA due to its volume and the time critical nature of the results. This talk outlines the challenges in the areas of: data flow; storage design and optimisation; database integration into HPC; and low-latency scheduling for ultrascale visualisation and analysis on HPC systems.

... 8. References [1] K. Moløkken and M. Jørgensen, "A review of surveys on software effortestimation," Proceedings of International Symposium on Empirical Software Engineering (ISESE'03), pp. ... [4] C. Larman, Agile & iterative development: a manager's guide. ...

Contemporary software is increasingly developed using an agile development approach, yet the supplier is generally selected as a result of a waterfall-style competitive tendering and contracting process. The procurement activity may be incompatible with an agile elaboration of requirements and development of functionality, and lead to sub-optimal outcomes. This paper examines the interaction of the procurement and software development lifecycles,

Summary Traditional approaches to procurement tend to assume that defined processes and toolsets can be applied in a logical, rational environment to produce predictable outcomes. However, there are many problems that fail to fit this model. This paper reports on some current research, which is now significantly advanced, that identifies the primary challenges within the complex social environment of buyers

Contemporary software is increasingly developed using an agile development approach, yet the supplier is generally selected as a result of a waterfall-style competitive tendering and contracting process. The procurement activity may be incompatible with an agile development of functionality and lead to sub-optimal outcomes. This paper examines the interaction of the procurement and software development lifecycles, explores potential causes of project or system failures and suggests some improvements based on a successful 10 year project between ADI Limited and the Australian Department of Defence.

Contemporary software is increasingly developed using an agile development approach, yet the supplier is generally selected as a result of a waterfall-style competitive tendering and contracting process. The procurement activity may be incompatible with an agile elaboration of requirements and development of functionality, and lead to sub-optimal outcomes. This paper examines the interaction of the procurement and software development lifecycles,