This paper outlines directions for an evaluation of Real-Time Java suitability to be used in ESA spacecraft onboard software. It starts with an overview of related existing standards and ongoing standardisation efforts, as well as several use cases in the avionics and space domain. Then it identifies steps which should be followed to research how particular Java features match particular requirements of different spacecraft on-board software application domains. The paper takes into account the goals of the upcoming ESA Real-Time Java Assessment Project [1].

For most computer end–users, web browsers and Internet services act as the providers and protectors of their personal information, from bank accounts to personal correspondence. These systems are critical to users ’ continued lifestyles but often show no evidence of survivability [45], or robustness against present and future attacks. Software defects, considered the largest risk to survivability [45], are quite prevalent in consumer products and Web service software components [12]. Recent widespread security issues [20] [19] serve to emphasize this fact and show a lack investment in survivability engineering

As I scratch my head for the thousandth time wondering who came up with the bright idea of the standard desktop computer, it occurs to me that this month’s CrossTalk theme is extremely pertinent. I am sure that the promoters of the standard desktop did not consider that a software maintenance group might need multiple versions of a single software package loaded onto the same desktop. Nor did they imagine that continually pushing out patches would create a configuration management nightmare in our software integration laboratories. Commercial off-the-shelf (COTS) software solutions have long been touted as the best- or least-cost solution to many software design requirements. We save major development costs by using commercial products and, in theory, can significantly accelerate the delivery schedule. The Air Force is engaging in this venture on a massive scale with the implementation of Expeditionary Combat Support System (ECSS) – based on a commercially available Enterprise Resource Planning system. The projected life-cycle cost savings due to phasing out legacy information systems are staggering. However, the success of ECSS, and of all COTS software implementations, is dependent on a realistic assessment of all costs, benefits, and risks.

Abstract — Development of high-integrity software requires a programming language that promotes good engineering across domains in highly reliable real-time systems. The new Ada 2005 has introduced more robust capabilities based on user experience. The language offers particular innovations which helps make safety assurance less costly and further improves high integrity features in all major facets. The US Federal Aviation Administration’s (FAA) current operational core En Route air traffic control (ATC) systems Display System and User Requested Evaluation Tool use Ada as the primary language. The replacement of the huge En Route Host System, called En Route Automation Modernization (ERAM) is currently completing development and beginning deployment with a majority of critical real-time applications in Ada. These systems were completed ahead of schedule and under budget. The paper discusses the evolution of Ada 2005, its vendor support and several excellent academic initiatives. Discussions include the architecture and software of the ATC systems developed in Ada. Since the FAA has a long-term vested interest in the language for mission-critical systems with a very high availability requirement, it continuously monitors the long-term supportability of Ada and trends in its commercial product evolution.

Why do some programming languages fail and others succeed? What does the answer tell us about programming language design, implementation, and principles? To help answer these and other questions, we argue for a sociologicallygrounded programming language theory: socio-PLT. Researchers in the social sciences have studied adoption in many contexts. We show how their findings are applicable to programming language design. For example, many programming language features provide benefits that programmers cannot directly or immediately observe and therefore may not find compelling. From clean water to safe sex, the health community has long examined how to surmount similar observability barriers. We use such results from outside of programming language theory to frame a research agenda that should help us understand the social foundations of languages. Finally, we examine implications of our approach, such as for the design space of language features and the assessment of scientific research into programming languages. 1.