RASSP Enterprise Technologies for SignalProcessor Life-Cycle Support

Abstract

Enterprise integration technologies are a key contributor to improving time-to-market, cost, and design quality by a factor, which is the goal of the DARPA Rapid Prototyping of Application-Specific Signal Processors (RASSP) program [1]. The Lockheed Martin Advanced Technology Laboratories (ATL) RASSP team developed a productivity improvement model, shown in Fig. 1, that indicates the relative contributions of various RASSP technologies to the overall improvement. Enterprise technologies address the entire 17% enterprise partition, and more than half of the 30% reuse and model-year architecture partition, thus accounting for at least 35% of the overall RASSP productivity improvement. The ATL RASSP approach to implement enterprise systems is to extend commercial technologies so the results are available to a broad base of potential users. Unlike current automation concepts which start at later stages of the development cycle, the RASSP enterprise system supports the entire signal processor life cycle. Core concepts of the enterprise system include: Tools and tool frameworks integrated into an enterprise environment Program execution control through workflows Integrated data management functions Design reuse Concurrent engineering team support Integrated design engineering and manufacturing. The model-year architecture, which enables users to rapidly, efficiently upgrade systems with new technology, is supported in the enterprise system by a robust reuse management system. Manufacturing interface and communication services elements of the enterprise system provide improved concurrent engineering support for distributed product teams. The enterprise system will be provided to commercial and aerospace users as products, including a reusable set of workflows for electronics design, commercial tools supporting the enterprise system environment, and utilities to enable users to customize the RASSP enterprise system for a particular organization or project. The enterprise system development cycle includes four build cycles with increasing capabilities. The ATL team completed the Build 2 implementation in May‘96. This implementation supports the processes associated with detailed hardware/software design, architecture design, and trade-off analyses. It is being used at Lockheed Martin and multiple government sites for benchmarking and evaluation. Results to date indicate >5:1 productivity improvements in the manufacturing interface, and 5–10% improvements in design engineering, which is growing with increasing level of utilization.