Software Challenges For HL-LHC Data Analysis

The high energy physics community is discussing where investment is needed to prepare software for the HL-LHC and its unprecedented challenges. The ROOT project is one of the central software players in high energy physics since decades. From its experience and expectations, the ROOT team has distilled a comprehensive set of areas that should see research and development in the context of data analysis software, for making best use of HL-LHC's physics potential. This work shows what these areas could be, why the ROOT team believes investing in them is needed, which gains are expected, and where related work is ongoing. It can serve as an indication for future research proposals and cooperations

Global perspectives on legacy systems

Summarises findings of two international workshops on legacy systems, held in conjunction with an EPSRC managed programme. Issues covered include the nature and dynamics of legacy systems, the co-evolution of software and organisations, issues around software as a technology (its engineering and its management), and organisational/people issues

Going on-line on a shoestring: An experiment in concurrent development of requirements and architecture

A number of on-line applications were built for a small university using a micro-sized development team. Four ideas were tested during the project: the Twin Peaks development model, using fully functional prototypes in the requirements elicitation process, some core practices of Extreme Programming, and the use of open-source software in a production environment. Certain project management techniques and their application to a micro-sized development effort were also explored. These ideas and techniques proved effective in developing many significant Internet and networked applications in a short time and at very low cost

Flight Operations and Engineering Documentation Managing and Distribution Supported by Intelligent Transport Systems

Aviation as a multitude of activities is meant to satisfy needs of its customers to overcome distance and time between any departure and arrival point in the world. Airlines and other aircraft operators (governments, armed forces, general aviation, and business aviation) differ in their structure depending on their size and services they provide. Some departments are to be found in larger airlines only. However, core departments, to every airline or aircraft operator, are flight operations department and engineering department. Sophistication and the size of these departments depend on the size of the system they are incorporated in. Business logistics of an airline consist of numerous distinctive activities and functions. These activities have to be planned and completed in synchronisation. The paper presents an overview to intelligent systems for the support to these activities with particular stress on flight operations and maintenance functions in a medium sized airline. Authors show how the approach to documentation management, as a part of logistics in the production of transportation service, has evolved since the early 1990s when aviation has started to recognise the value of digital technical data. In light of this, authors analyse conceptual framework adopted by today's aircraft manufacturers towards their logistics activities supported by Internet as a new means of transferring data. The advent of new sophisticated pilot-machine interfaces and aircraft systems tends to increase the volume of the documentation describing these tools drastically. The paper communicates how operational documentation has to change to move towards a more easy and modern media. Intelligent systems that prove aviation entering a period where the "written book" is going to be complemented if not largely supplemented by the "electronic book" are presented from the early beginnings of digital data application to the most recent achievements

The space physics environment data analysis system (SPEDAS)

With the advent of the Heliophysics/Geospace System Observatory (H/GSO), a complement of multi-spacecraft missions and ground-based observatories to study the space environment, data retrieval, analysis, and visualization of space physics data can be daunting. The Space Physics Environment Data Analysis System (SPEDAS), a grass-roots software development platform (www.spedas.org), is now officially supported by NASA Heliophysics as part of its data environment infrastructure. It serves more than a dozen space missions and ground observatories and can integrate the full complement of past and upcoming space physics missions with minimal resources, following clear, simple, and well-proven guidelines. Free, modular and configurable to the needs of individual missions, it works in both command-line (ideal for experienced users) and Graphical User Interface (GUI) mode (reducing the learning curve for first-time users). Both options have “crib-sheets,” user-command sequences in ASCII format that can facilitate record-and-repeat actions, especially for complex operations and plotting. Crib-sheets enhance scientific interactions, as users can move rapidly and accurately from exchanges of technical information on data processing to efficient discussions regarding data interpretation and science. SPEDAS can readily query and ingest all International Solar Terrestrial Physics (ISTP)-compatible products from the Space Physics Data Facility (SPDF), enabling access to a vast collection of historic and current mission data. The planned incorporation of Heliophysics Application Programmer’s Interface (HAPI) standards will facilitate data ingestion from distributed datasets that adhere to these standards. Although SPEDAS is currently Interactive Data Language (IDL)-based (and interfaces to Java-based tools such as Autoplot), efforts are under-way to expand it further to work with python (first as an interface tool and potentially even receiving an under-the-hood replacement). We review the SPEDAS development history, goals, and current implementation. We explain its “modes of use” with examples geared for users and outline its technical implementation and requirements with software developers in mind. We also describe SPEDAS personnel and software management, interfaces with other organizations, resources and support structure available to the community, and future development plans.Published versio