Next generation software environments : principles, problems, and research directions

The past decade has seen a burgeoning of research and development in software environments. Conferences have been devoted to the topic of practical environments, journal papers produced, and commercial systems sold. Given all the activity, one might expect a great deal of consensus on issues, approaches, and techniques. This is not the case, however. Indeed, the term "environment" is still used in a variety of conflicting ways. Nevertheless substantial progress has been made and we are at least nearing consensus on many critical issues.The purpose of this paper is to characterize environments, describe several important principles that have emerged in the last decade or so, note current open problems, and describe some approaches to these problems, with particular emphasis on the activities of one large-scale research program, the Arcadia project. Consideration is also given to two related topics: empirical evaluation and technology transition. That is, how can environments and their constituents be evaluated, and how can new developments be moved effectively into the production sector

On the Notion of Abstract Platform in MDA Development

Although platform-independence is a central property in MDA models, the study of platform-independence has been largely overlooked in MDA. As a consequence, there is a lack of guidelines to select abstraction criteria and modelling concepts for platform-independent design. In addition, there is little methodological support to distinguish between platform-independent and platform-specific concerns, which could be detrimental to the beneficial exploitation of the PIM-PSM separation-of-concerns adopted by MDA. This work is an attempt towards clarifying the notion of platform-independent modelling in MDA development. We argue that each level of platform-independence must be accompanied by the identification of an abstract platform. An abstract platform is determined by the platform characteristics that are relevant for applications at a certain level of platform-independence, and must be established by balancing various design goals. We present some methodological principles for abstract platform design, which forms a basis for defining requirements for design languages intended to support platform-independent design. Since our methodological framework is based on the notion of abstract platform, we pay particular attention to the definition of abstract platforms and the language requirements to specify abstract platforms. We discuss how the concept of abstract platform relates to UML

Technical alignment

This essay discusses the importance of the areas of infrastructure and testing to help digital preservation services demonstrate reliability, transparency, and accountability. It encourages practitioners to build a strong culture in which transparency and collaborations between technical frameworks are valued highly. It also argues for devising and applying agreed-upon metrics that will enable the systematic analysis of preservation infrastructure. The essay begins by defining technical infrastructure and testing in the digital preservation context, provides case studies that exemplify both progress and challenges for technical alignment in both areas, and concludes with suggestions for achieving greater degrees of technical alignment going forward

Space Transportation Materials and Structures Technology Workshop

The Space Transportation Materials and Structures Technology Workshop was held on September 23-26, 1991, in Newport News, Virginia. The workshop, sponsored by the NASA Office of Space Flight and the NASA Office of Aeronautics and Space Technology, was held to provide a forum for communication within the space materials and structures technology developer and user communities. Workshop participants were organized into a Vehicle Technology Requirements session and three working panels: Materials and Structures Technologies for Vehicle Systems, Propulsion Systems, and Entry Systems

The development of service provider's BPO-IT framework

Purpose The decision to operate BPO-IT organisational model by a business process outsourcing (BPO) service provider has far reaching benefits. The purpose of this paper is to develop a service provider’s BPO-IT framework that provides in-house IT function (software) required to process client services. Design/methodology/approach The multi-case study adopted an exploratory sequential mixed method research approach. In the first instance, seven BPO service provider organisations were investigated in the qualitative phase and 156 in the quantitative phase, respectively. Findings The adoption of the developed framework indicates that it could reduce failures in BPO relationships through reduced turnaround time in processing client services, improved quality of service, reduced cost, improved client and provider’s competitiveness, and confidentiality of client operations. Outsourcing clients could lay the foundation for a successful relationship by adopting a selection process that could choose the right provider. Originality/value The paper reveals BPO-IT organisation’s operation towards in-house provision of software required to process client services. A research exploring BPO service providers from a top outsourcing destination like India could provide offshore outsourcing clients the information to move towards onshore outsourcing. </jats:sec

Methods for measurement-based COTS assessments and selection

During recent years, new software engineering paradigms like component-based software engineering and COTS-based development have emerged. Both paradigms are concerned with reuse and customisation of existing components. The use of COTS software has become more and more important in state-of-the-art and state-of-the-practice software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, COTS software introduces risks such as unknown quality properties of the COTS software in use that can inject harmful side effects into the final product. In this paper, we present a brief comparison of well-known COTS evaluation methods. Our work is focused on identifying the main goals and features of the methods in order to extend their uses on evaluating COTS products as well as COTS development processes.Eje: Ingeniería de Software y Base de DatosRed de Universidades con Carreras en Informática (RedUNCI

A NASA-wide approach toward cost-effective, high-quality software through reuse

NASA Langley Research Center sponsored the second Workshop on NASA Research in Software Reuse on May 5-6, 1992 at the Research Triangle Park, North Carolina. The workshop was hosted by the Research Triangle Institute. Participants came from the three NASA centers, four NASA contractor companies, two research institutes and the Air Force's Rome Laboratory. The purpose of the workshop was to exchange information on software reuse tool development, particularly with respect to tool needs, requirements, and effectiveness. The participants presented the software reuse activities and tools being developed and used by their individual centers and programs. These programs address a wide range of reuse issues. The group also developed a mission and goals for software reuse within NASA. This publication summarizes the presentations and the issues discussed during the workshop

Unsolved Tricky Issues on COTS Selection and Evaluation

Component Based Software Engineering (CBSE) approach is based on the idea to develop software systems by selecting appropriate components and then to assemble them with a well-defined software architecture. (CBSE) offers developers the twin benefits of reduced software life cycles, shorter development times , saving cost and less effort as compare to build own component. However the success of the component based paradigm depends on the quality of the commercial off-the-shelf (COTS) components purchased and integrated into the existing software systems. It is need of the time to present a quality model that can be used by software programmer to evaluate the quality of software components before integrating them into legacy systems. The evaluation and selection of the COTS components are the most critical process. These evaluation and selection method cannot be resolved by the IT professionals itself. In this study the author tried to compare the twenty three available systematic methods for best evaluation and selection of COTS components

Structures and materials technology issues for reusable launch vehicles

Projected space missions for both civil and defense needs require significant improvements in structures and materials technology for reusable launch vehicles: reductions in structural weight compared to the Space Shuttle Orbiter of up to 25% or more, a possible factor of 5 or more increase in mission life, increases in maximum use temperature of the external surface, reusable containment of cryogenic hydrogen and oxygen, significant reductions in operational costs, and possibly less lead time between technology readiness and initial operational capability. In addition, there is increasing interest in hypersonic airbreathing propulsion for launch and transmospheric vehicles, and such systems require regeneratively cooled structure. The technology issues are addressed, giving brief assessments of the state-of-the-art and proposed activities to meet the technology requirements in a timely manner

Integrating testing techniques through process programming

Integration of multiple testing techniques is required to demonstrate high quality of software. Technique integration has three basic goals: incremental testing capabilities, extensive error detection, and cost-effective application. We are experimenting with the use of process programming as a mechanism of integrating testing techniques. Having set out to integrate DATA FLOW testing and RELAY, we proposed synergistic use of these techniques to achieve all three goals. We developed a testing process program much as we would develop a software product from requirements through design to implementation and evaluation. We found process programming to be effective for explicitly integrating the techniques and achieving the desired synergism. Used in this way, process programming also mitigates many of the other problems that plague testing in the software development process