URAT: astrometric requirements and design history

The U.S. Naval Observatory Robotic Astrometric Telescope (URAT) project aims at a highly accurate (5 mas), ground-based, all-sky survey. Requirements are presented for the optics and telescope for this 0.85 m aperture, 4.5 degree diameter field-of-view, specialized instrument, which are close to the capability of the industry. The history of the design process is presented as well as astrometric performance evaluations of the toleranced, optical design, with expected wavefront errors included.Comment: 12 pages, 7 figures, SPIE 2006 Orlando conf. proc. Vol. 626

Fighter aircraft flight control technology design requirements

The evolution of fighter aircraft flight control technology is briefly surveyed. Systems engineering, battle damage considerations for adaptive flutter suppression, in-flight simulation, and artificial intelligence are briefly discussed

Design science, engineering science and requirements engineering

For several decades there has been a debate in the computing sciences about the relative roles of design and empirical research, and about the contribution of design and research methodology to the relevance of research results. In this minitutorial we review this debate and compare it with evidence about the relation between design and research in the history of science and technology. Our review shows that research and design are separate but concurrent activities, and that relevance of research results depends on problem setting rather than on rigorous methods. We argue that rigorous scientific methods separate design from research, and we give simple model for how to do this in a problem-driven way

Advanced EVA system design requirements study

The results are presented of a study to identify specific criteria regarding space station extravehicular activity system (EVAS) hardware requirements. Key EVA design issues include maintainability, technology readiness, LSS volume vs. EVA time available, suit pressure/cabin pressure relationship and productivity effects, crew autonomy, integration of EVA as a program resource, and standardization of task interfaces. A variety of DOD EVA systems issues were taken into consideration. Recommendations include: (1) crew limitations, not hardware limitations; (2) capability to perform all of 15 generic missions; (3) 90 days on-orbit maintainability with 50 percent duty cycle as minimum; and (4) use by payload sponsors of JSC document 10615A plus a Generic Tool Kit and Specialized Tool Kit description. EVA baseline design requirements and criteria, including requirements of various subsystems, are outlined. Space station/EVA system interface requirements and EVA accommodations are discussed in the areas of atmosphere composition and pressure, communications, data management, logistics, safe haven, SS exterior and interior requirements, and SS airlock

Requirements for a Research-oriented IC Design System

Computer-aided design techniques for integrated circuits grown in an incremental way, responding to various perceived needs, so that today there are a number of useful programs for logic generation, simulation at various levels, test preparation, artwork generation and analysis (including design rule checking), and interactive graphical editing. While the design of many circuits has benefitted from these programs, when industry wants to produce a high-volume part, the design and layout are done manually, followed by digitizing and perhaps some graphic editing before it is converted to pattern generation format, leading to the often heard statement that computer-aided design of integrated circuits doesn't work. If progress is to be made, it seems clear that the entire design process has to be thought through in basic terms, and much more attention must be paid to the way in which computational techniques can complement the designer's abilities. Currently, it is appropriate to try to characterize the design process in abstract terms, so that implementation and technological biases don't cloud the view of a desired system. In this paper, we briefly describe the conversion of algorithms to masks at a very general level, and then describe several projects at MIT which aim to provide contributions to an integrated design system. It is emphasized that no complete system design exists now at MIT, and that we believe that general design considerations must constantly be tested by building (and rebuilding) the various subcomponents, the structure of which is guided by our view of the overall design process

Identifying Design Requirements for Wireless Routing Link Metrics

In this paper, we identify and analyze the requirements to design a new routing link metric for wireless multihop networks. Considering these requirements, when a link metric is proposed, then both the design and implementation of the link metric with a routing protocol become easy. Secondly, the underlying network issues can easily be tackled. Thirdly, an appreciable performance of the network is guaranteed. Along with the existing implementation of three link metrics Expected Transmission Count (ETX), Minimum Delay (MD), and Minimum Loss (ML), we implement inverse ETX; invETX with Optimized Link State Routing (OLSR) using NS-2.34. The simulation results show that how the computational burden of a metric degrades the performance of the respective protocol and how a metric has to trade-off between different performance parameters

SDN management layer: design requirements and future direction

Computer networks are becoming more and more complex and difficult to manage. The research community has been expending a lot of efforts to come up with a general management paradigm that is able to hide the details of the physical infrastructure and enable flexible network management. Software Defined Networking (SDN) is such a paradigm that simplifies network management and enables network innovations. In this survey paper, by reviewing existing SDN management layers (platforms), we identify the general common management architecture for SDN networks, and further identify the design requirements of the management layer that is at the core of the architecture. We also point out open issues and weaknesses of existing SDN management layers. We conclude with a promising future direction for improving the SDN management layer.This work is supported in part by the National Science Foundation (NSF grant CNS-0963974)

NSSC-2 operating system design requirements specification

The design requirements and implementation standards for an NSSC-2 operating system are defined. An operating system diagram is presented along with system concepts and terminology

Flight software requirements and design support system

The desirability and feasibility of computer-augmented support for the pre-implementation activities occurring during the development of flight control software was investigated. The specific topics to be investigated were the capabilities to be included in a pre-implementation support system for flight control software system development, and the specification of a preliminary design for such a system. Further, the pre-implementation support system was to be characterized and specified under the constraints that it: (1) support both description and assessment of flight control software requirements definitions and design specification; (2) account for known software description and assessment techniques; (3) be compatible with existing and planned NASA flight control software development support system; and (4) does not impose, but may encourage, specific development technologies. An overview of the results is given