IEEE Standard 1500 Compliance Verification for Embedded Cores

Core-based design and reuse are the two key elements for an efficient system-on-chip (SoC) development. Unfortunately, they also introduce new challenges in SoC testing, such as core test reuse and the need of a common test infrastructure working with cores originating from different vendors. The IEEE 1500 Standard for Embedded Core Testing addresses these issues by proposing a flexible hardware test wrapper architecture for embedded cores, together with a core test language (CTL) used to describe the implemented wrapper functionalities. Several intellectual property providers have already announced IEEE Standard 1500 compliance in both existing and future design blocks. In this paper, we address the problem of guaranteeing the compliance of a wrapper architecture and its CTL description to the IEEE Standard 1500. This step is mandatory to fully trust the wrapper functionalities in applying the test sequences to the core. We present a systematic methodology to build a verification framework for IEEE Standard 1500 compliant cores, allowing core providers and/or integrators to verify the compliance of their products (sold or purchased) to the standar

Towards a methodology for rigorous development of generic requirements patterns

We present work in progress on a methodology for the engineering, validation and verification of generic requirements using domain engineering and formal methods. The need to develop a generic requirement set for subsequent system instantiation is complicated by the addition of the high levels of verification demanded by safety-critical domains such as avionics. We consider the failure detection and management function for engine control systems as an application domain where product line engineering is useful. The methodology produces a generic requirement set in our, UML based, formal notation, UML-B. The formal verification both of the generic requirement set, and of a particular application, is achieved via translation to the formal specification language, B, using our U2B and ProB tools

Automatic generation of human machine interface screens from component-based reconfigurable virtual manufacturing cell

Increasing complexity and decreasing time-tomarket require changes in the traditional way of building automation systems. The paper describes a novel approach to automatically generate the Human Machine Interface (HMI) screens for component-based manufacturing cells based on their corresponding virtual models. Manufacturing cells are first prototyped and commissioned within a virtual engineering environment to validate and optimise the control behaviour. A framework for reusing the embedded control information in the virtual models to automatically generate the HMI screens is proposed. Finally, for proof of concept, the proposed solution is implemented and tested on a test rig

AdaNET research project

The components necessary for the success of the commercialization of an Ada Technology Transition Network are reported in detail. The organizational plan presents the planned structure for services development and technical transition of AdaNET services to potential user communities. The Business Plan is the operational plan for the AdaNET service as a commercial venture. The Technical Plan is the plan from which the AdaNET can be designed including detailed requirements analysis. Also contained is an analysis of user fees and charges, and a proposed user fee schedule

The development and technology transfer of software engineering technology at NASA. Johnson Space Center

The United State's big space projects of the next decades, such as Space Station and the Human Exploration Initiative, will need the development of many millions of lines of mission critical software. NASA-Johnson (JSC) is identifying and developing some of the Computer Aided Software Engineering (CASE) technology that NASA will need to build these future software systems. The goal is to improve the quality and the productivity of large software development projects. New trends are outlined in CASE technology and how the Software Technology Branch (STB) at JSC is endeavoring to provide some of these CASE solutions for NASA is described. Key software technology components include knowledge-based systems, software reusability, user interface technology, reengineering environments, management systems for the software development process, software cost models, repository technology, and open, integrated CASE environment frameworks. The paper presents the status and long-term expectations for CASE products. The STB's Reengineering Application Project (REAP), Advanced Software Development Workstation (ASDW) project, and software development cost model (COSTMODL) project are then discussed. Some of the general difficulties of technology transfer are introduced, and a process developed by STB for CASE technology insertion is described

Generalization of an integrated cost model and extensions to COTS, PLE and TTM

There have been existing software reuse cost models related to estimating costs of software reuse, for example, COCOMO II, COCOTS, and so on. Chmiel\u27s model [Chmiel 2000] is a generalization of these cost models. This model is different from others in that the decisions are composed of four levels and treats reuse projects from a point of view of long term run. Each level corresponds one engineering cycle. Each level is a decision making process based on calculation of NPV, ROI, and other economic indices. Reuse investment decisions are made on different levels from the corporate to the programming.;Chmiel\u27s model doesn\u27t cover Commercial-Off-The-Shelf (COTS), Product Line Engineering (PLE) and benefits due to shortened Time-To-Market (TTM) and can only deal with internal traffic since the model assumes all of the reusable components are built from scratch in house. For example, Extra efforts caused by the use of COTS, assessment, tailoring, glue code and COTS volatility, are not covered in this model. And this model doesn\u27t treat the benefits of TTM, for example, business performance.;By extending Chmiel\u27s model, the new model is applied to CBSE (Component-Based Software Engineering), COTS reuse systems and PLE. In addition, attempts of quantifying benefits of shortened TTM are made within this study and a TTM submodel is developed to cover this issue.;This study also addresses the issue to analyze and optimize corporate Return On Investment (ROI). The rational is that optimizing (maximizing) the corporate ROI under the condition that all other ROI\u27s are positive. By designing an algorithm and applying it to the data, this study discovers the method how to make the maximized value of corporate ROI.;And this model is supported through a tool based on the model rationale. Users to this tool are corporate management and development engineers. The supporting tool has user-friendly interface and allows users to input values of related parameters. A detailed report is produced, which is composed of details about costs and benefits, final Net Present Value (NPV) and ROI of each cycle

GAMES: A new Scenario for Software and Knowledge Reuse

Games are a well-known test bed for testing search algorithms and learning methods, and many authors have presented numerous reasons for the research in this area. Nevertheless, they have not received the attention they deserve as software projects. In this paper, we analyze the applicability of software and knowledge reuse in the games domain. In spite of the need to find a good evaluation function, search algorithms and interface design can be said to be the primary concerns. In addition, we will discuss the current state of the main statistical learning methods and how they can be addressed from a software engineering point of view. So, this paper proposes a reliable environment and adequate tools, necessary in order to achieve high levels of reuse in the games domain

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