Towards Other Planetary Systems (TOPS): A technology needs identification workshop

The workshop identified a strong commonality between the technology needs for NASA's TOPS program and the technology needs that were identified for NASA's astrophysics program through its Astrotech 21 survey. The workshop encourages NASA to have the Solar System Exploration and Astrophysics Div. work cooperatively to share in technology studies that are common to both programs, rather than to conduct independent studies. It was also clear, however, that there are technology needs specific to TOPS, and these should be pursued by the Solar System Exploration Div. There are two technology areas that appear to be particularly critical to realizing the ultimate performance that is being sought under the TOPS program, these areas are metrology and optics. The former is critical in calibration and verification of instrument performance, while the latter is needed to provide optical systems of sufficient quality to conduct a search for and characterization of other planetary systems at the more extreme levels of performance identified in TOPS program

Modelling process knowledge in architectural design: A case-based approach

The paper presents on-going research aimed at the understanding and support of process knowledge in architectural design, from early and not sufficiently defined, to satisfactorily-defined phases. Today, technical, planning, management and environmental issues have created a scenario of such complexity that traditionally efficient control tools (e.g. technical manuals) are inadequate and there is a demand for new, integrated instruments to handle the decision process underlying architectural design. We assume design as a recursive and incrementally specified intentional planning activity, involving goals, constraints and their relationships. The essence of architectural design is thus encapsulated in the continual recursive transformation of the initial model, in order to map the desired state onto the enacted one. On the basis of this concept of design we describe the model of an environment aimed at progressively representing the enlarging space of acquired knowledge, and at supporting the designer's central role in the management of complexity

A verification-driven framework for iterative design of controllers

Controllers often are large and complex reactive software systems and thus they typically cannot be developed as monolithic products. Instead, they are usually comprised of multiple components that interact to provide the desired functionality. Components themselves can be complex and in turn be decomposed into multiple sub-components. Designing such systems is complicated and must follow systematic approaches, based on recursive decomposition strategies that yield a modular structure. This paper proposes FIDDle–a comprehensive verification-driven framework which provides support for designers during development. FIDDle supports hierarchical decomposition of components into sub-components through formal specification in terms of pre- and post-conditions as well as independent development, reuse and verification of sub-components. The framework allows the development of an initial, partially specified design of the controller, in which certain components, yet to be defined, are precisely identified. These components can be associated with pre- and post-conditions, i.e., a contract, that can be distributed to third-party developers. The framework ensures that if the components are compliant with their contracts, they can be safely integrated into the initial partial design without additional rework. As a result, FIDDle supports an iterative design process and guarantees correctness of the system at any step of development. We evaluated the effectiveness of FIDDle in supporting an iterative and incremental development of components using the K9 Mars Rover example developed at NASA Ames. This can be considered as an initial, yet substantive, validation of the approach in a realistic setting. We also assessed the scalability of FIDDle by comparing its efficiency with the classical model checkers implemented within the LTSA toolset. Results show that FIDDle scales as well as classical model checking as the number of the states of the components under development and their environments grow

A requirements engineering framework for integrated systems development for the construction industry

Computer Integrated Construction (CIC) systems are computer environments through which collaborative working can be undertaken. Although many CIC systems have been developed to demonstrate the communication and collaboration within the construction projects, the uptake of CICs by the industry is still inadequate. This is mainly due to the fact that research methodologies of the CIC development projects are incomplete to bridge the technology transfer gap. Therefore, defining comprehensive methodologies for the development of these systems and their effective implementation on real construction projects is vital. Requirements Engineering (RE) can contribute to the effective uptake of these systems because it drives the systems development for the targeted audience. This paper proposes a requirements engineering approach for industry driven CIC systems development. While some CIC systems are investigated to build a broad and deep contextual knowledge in the area, the EU funded research project, DIVERCITY (Distributed Virtual Workspace for Enhancing Communication within the Construction Industry), is analysed as the main case study project because its requirements engineering approach has the potential to determine a framework for the adaptation of requirements engineering in order to contribute towards the uptake of CIC systems

Testing in the incremental design and development of complex products

Testing is an important aspect of design and development which consumes significant time and resource in many companies. However, it has received less research attention than many other activities in product development, and especially, very few publications report empirical studies of engineering testing. Such studies are needed to establish the importance of testing and inform the development of pragmatic support methods. This paper combines insights from literature study with findings from three empirical studies of testing. The case studies concern incrementally developed complex products in the automotive domain. A description of testing practice as observed in these studies is provided, confirming that testing activities are used for multiple purposes depending on the context, and are intertwined with design from start to finish of the development process, not done after it as many models depict. Descriptive process models are developed to indicate some of the key insights, and opportunities for further research are suggested

Software Engineering Timeline: major areas of interest and multidisciplinary trends

Ingeniería del software. EvolucionSociety today cannot run without software and by extension, without Software Engineering. Since this discipline emerged in 1968, practitioners have learned valuable lessons that have contributed to current practices. Some have become outdated but many are still relevant and widely used. From the personal and incomplete perspective of the authors, this paper not only reviews the major milestones and areas of interest in the Software Engineering timeline helping software engineers to appreciate the state of things, but also tries to give some insights into the trends that this complex engineering will see in the near future