Automata learning algorithms and processes for providing more complete systems requirements specification by scenario generation, CSP-based syntax-oriented model construction, and R2D2C system requirements transformation

NASA Technical Reports Server (NTRS)

Margaria, Tiziana (Inventor); Hinchey, Michael G. (Inventor); Rouff, Christopher A. (Inventor); Rash, James L. (Inventor); Steffen, Bernard (Inventor)

2010-01-01

Systems, methods and apparatus are provided through which in some embodiments, automata learning algorithms and techniques are implemented to generate a more complete set of scenarios for requirements based programming. More specifically, a CSP-based, syntax-oriented model construction, which requires the support of a theorem prover, is complemented by model extrapolation, via automata learning. This may support the systematic completion of the requirements, the nature of the requirement being partial, which provides focus on the most prominent scenarios. This may generalize requirement skeletons by extrapolation and may indicate by way of automatically generated traces where the requirement specification is too loose and additional information is required.

From Goal-Oriented Requirements to Event-B Specifications

NASA Technical Reports Server (NTRS)

Aziz, Benjamin; Arenas, Alvaro E.; Bicarregui, Juan; Ponsard, Christophe; Massonet, Philippe

2009-01-01

In goal-oriented requirements engineering methodologies, goals are structured into refinement trees from high-level system-wide goals down to fine-grained requirements assigned to specific software/ hardware/human agents that can realise them. Functional goals assigned to software agents need to be operationalised into specification of services that the agent should provide to realise those requirements. In this paper, we propose an approach for operationalising requirements into specifications expressed in the Event-B formalism. Our approach has the benefit of aiding software designers by bridging the gap between declarative requirements and operational system specifications in a rigorous manner, enabling powerful correctness proofs and allowing further refinements down to the implementation level. Our solution is based on verifying that a consistent Event-B machine exhibits properties corresponding to requirements.

System requirement specification for the I-15 integrated corridor management system (ICMS) in San Diego, California.

DOT National Transportation Integrated Search

2008-03-31

This document presents a System Requirement Specification for an Integrated Corridor Management System (ICMS) in the I-15 Corridor in San Diego, California. The ICMS will consist of two major subsystems: the existing Intermodal Transportation Managem...

IDC System Specification Document.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Clifford, David J.

2014-12-01

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Reengineering Phase 2 project. Revisions Version Date Author/Team Revision Description Authorized by V1.0 12/2014 IDC Reengineering Project Team Initial delivery M. Harris

Knowledge-based requirements analysis for automating software development

NASA Technical Reports Server (NTRS)

Markosian, Lawrence Z.

1988-01-01

We present a new software development paradigm that automates the derivation of implementations from requirements. In this paradigm, informally-stated requirements are expressed in a domain-specific requirements specification language. This language is machine-understable and requirements expressed in it are captured in a knowledge base. Once the requirements are captured, more detailed specifications and eventually implementations are derived by the system using transformational synthesis. A key characteristic of the process is that the required human intervention is in the form of providing problem- and domain-specific engineering knowledge, not in writing detailed implementations. We describe a prototype system that applies the paradigm in the realm of communication engineering: the prototype automatically generates implementations of buffers following analysis of the requirements on each buffer.

W-026, Waste Receiving and Processing Facility data management system validation and verification report

DOE Office of Scientific and Technical Information (OSTI.GOV)

Palmer, M.E.

1997-12-05

This V and V Report includes analysis of two revisions of the DMS [data management system] System Requirements Specification (SRS) and the Preliminary System Design Document (PSDD); the source code for the DMS Communication Module (DMSCOM) messages; the source code for selected DMS Screens, and the code for the BWAS Simulator. BDM Federal analysts used a series of matrices to: compare the requirements in the System Requirements Specification (SRS) to the specifications found in the System Design Document (SDD), to ensure the design supports the business functions, compare the discreet parts of the SDD with each other, to ensure thatmore » the design is consistent and cohesive, compare the source code of the DMS Communication Module with the specifications, to ensure that the resultant messages will support the design, compare the source code of selected screens to the specifications to ensure that resultant system screens will support the design, compare the source code of the BWAS simulator with the requirements to interface with DMS messages and data transfers relating to the BWAS operations.« less

Lesson 7: From Requirements to Specific Solutions

EPA Pesticide Factsheets

CROMERR requirements set performance goals, they do not dictate specific system functions, operating procedures,system architecture, or technology. The task is to decide on a solution to meet the goals.

Smart roadside initiative : system requirements specifications.

DOT National Transportation Integrated Search

2015-09-01

This document describes the system requirements specifications (SyRS) for the Smart Roadside Initiative (SRI) Prototype for the delivery of capabilities related to wireless roadside inspections, electronic screening/virtual weigh stations, universal ...

Instrument constraints and interface specifications. Earth Observatory Satellite system definition study (EOS)

NASA Technical Reports Server (NTRS)

1974-01-01

The equipment specifications for the thematic mapper and high resolution pointable imager for use on the Earth Observatory Satellite (EOS) are presented. The interface requirements of the systems are defined. The interface requirements are extracted from the equipment specifications and are intended as a summary to be used by the system and spacecraft designer. The appropriate documentation from which the specifications of the equipment are established are identified.

Formal Specification of Information Systems Requirements.

ERIC Educational Resources Information Center

Kampfner, Roberto R.

1985-01-01

Presents a formal model for specification of logical requirements of computer-based information systems that incorporates structural and dynamic aspects based on two separate models: the Logical Information Processing Structure and the Logical Information Processing Network. The model's role in systems development is discussed. (MBR)

Advanced computer architecture specification for automated weld systems

NASA Technical Reports Server (NTRS)

Katsinis, Constantine

1994-01-01

This report describes the requirements for an advanced automated weld system and the associated computer architecture, and defines the overall system specification from a broad perspective. According to the requirements of welding procedures as they relate to an integrated multiaxis motion control and sensor architecture, the computer system requirements are developed based on a proven multiple-processor architecture with an expandable, distributed-memory, single global bus architecture, containing individual processors which are assigned to specific tasks that support sensor or control processes. The specified architecture is sufficiently flexible to integrate previously developed equipment, be upgradable and allow on-site modifications.

76 FR 19333 - Commission Information Collection Activities (FERC-725B); Comment Request; Submitted for OMB Review

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-07

... the Bulk-Power System to comply with specific requirements to safeguard critical cyber assets.\\2\\ These standards help protect the nation's Bulk-Power System against potential disruptions from cyber... recordkeeping requirements. Specifically, CIP- 008-1 requires responsible entities to report cyber security...

Specification for procurement of water-level sensing instrumentation, specification number HIF-I-1

USGS Publications Warehouse

Rapp, D.H.

1982-01-01

This specification is to communicate to instrument manufacturers the U.S. Geological Survey 's requirements. It covers systems for sensing the elevation of the water surface on open channels, rivers, lakes, reservoirs, storm-sewer pipes, and observation wells at Survey data-collection sites. The signal output (mechanical or electrical) must meet the signal input requirements of analog to digital and digital input recorders in use by the Survey. A classification of stage-sensing systems by common characteristics is used to aid Survey people making system selections. These characteristics are (1) system type (contact or noncontact), (2) sensor type and sensing distance, (3) accuracy, (4) range, (5) power requirements, (6) system size and weight, and (7) data output signal. Acceptable system requirements cover system configurations, signal outputs, materials, operation manuals, detailed environmental conditions, calibration procedures, system accuracy, power requirements, installation limitations, maintainability, safety, and workmanship. An outline of the qualification test procedures and failure criteria are also given. The Hydrologic Instrumentation Facility at NSTL Station, Mississippi will test available systems to determine if they meet the specification in this report for inclusion in the Survey 's 'Qualified Products List'. This list will be used for future procurement of water-level sensing systems by the Survey. (USGS)

Functional design specification for Stowage List And Hardware Tracking System (SLAHTS). [space shuttles

NASA Technical Reports Server (NTRS)

Keltner, D. J.

1975-01-01

This functional design specification defines the total systems approach to meeting the requirements stated in the Detailed Requirements Document for Stowage List and Hardware Tracking System for the space shuttle program. The stowage list and hardware tracking system is identified at the system and subsystem level with each subsystem defined as a function of the total system.

Development of simulation computer complex specification

NASA Technical Reports Server (NTRS)

1973-01-01

The Training Simulation Computer Complex Study was one of three studies contracted in support of preparations for procurement of a shuttle mission simulator for shuttle crew training. The subject study was concerned with definition of the software loads to be imposed on the computer complex to be associated with the shuttle mission simulator and the development of procurement specifications based on the resulting computer requirements. These procurement specifications cover the computer hardware and system software as well as the data conversion equipment required to interface the computer to the simulator hardware. The development of the necessary hardware and software specifications required the execution of a number of related tasks which included, (1) simulation software sizing, (2) computer requirements definition, (3) data conversion equipment requirements definition, (4) system software requirements definition, (5) a simulation management plan, (6) a background survey, and (7) preparation of the specifications.

Designing Specification Languages for Process Control Systems: Lessons Learned and Steps to the Future

NASA Technical Reports Server (NTRS)

Leveson, Nancy G.; Heimdahl, Mats P. E.; Reese, Jon Damon

1999-01-01

Previously, we defined a blackbox formal system modeling language called RSML (Requirements State Machine Language). The language was developed over several years while specifying the system requirements for a collision avoidance system for commercial passenger aircraft. During the language development, we received continual feedback and evaluation by FAA employees and industry representatives, which helped us to produce a specification language that is easily learned and used by application experts. Since the completion of the PSML project, we have continued our research on specification languages. This research is part of a larger effort to investigate the more general problem of providing tools to assist in developing embedded systems. Our latest experimental toolset is called SpecTRM (Specification Tools and Requirements Methodology), and the formal specification language is SpecTRM-RL (SpecTRM Requirements Language). This paper describes what we have learned from our use of RSML and how those lessons were applied to the design of SpecTRM-RL. We discuss our goals for SpecTRM-RL and the design features that support each of these goals.

25 CFR 900.45 - What specific minimum requirements shall an Indian tribe or tribal organization's financial...

Code of Federal Regulations, 2011 CFR

2011-04-01

... or tribal organization's financial management system contain to meet these standards? 900.45 Section... ASSISTANCE ACT Standards for Tribal or Tribal Organization Management Systems Standards for Financial Management Systems § 900.45 What specific minimum requirements shall an Indian tribe or tribal organization's...

A Highly Flexible, Automated System Providing Reliable Sample Preparation in Element- and Structure-Specific Measurements.

PubMed

Vorberg, Ellen; Fleischer, Heidi; Junginger, Steffen; Liu, Hui; Stoll, Norbert; Thurow, Kerstin

2016-10-01

Life science areas require specific sample pretreatment to increase the concentration of the analytes and/or to convert the analytes into an appropriate form for the detection and separation systems. Various workstations are commercially available, allowing for automated biological sample pretreatment. Nevertheless, due to the required temperature, pressure, and volume conditions in typical element and structure-specific measurements, automated platforms are not suitable for analytical processes. Thus, the purpose of the presented investigation was the design, realization, and evaluation of an automated system ensuring high-precision sample preparation for a variety of analytical measurements. The developed system has to enable system adaption and high performance flexibility. Furthermore, the system has to be capable of dealing with the wide range of required vessels simultaneously, allowing for less cost and time-consuming process steps. However, the system's functionality has been confirmed in various validation sequences. Using element-specific measurements, the automated system was up to 25% more precise compared to the manual procedure and as precise as the manual procedure using structure-specific measurements. © 2015 Society for Laboratory Automation and Screening.

Automated personnel data base system specifications, Task V. Final report

DOE Office of Scientific and Technical Information (OSTI.GOV)

Bartley, H.J.; Bocast, A.K.; Deppner, F.O.

1978-11-01

The full title of this study is 'Development of Qualification Requirements, Training Programs, Career Plans, and Methodologies for Effective Management and Training of Inspection and Enforcement Personnel.' Task V required the development of an automated personnel data base system for NRC/IE. This system is identified as the NRC/IE Personnel, Assignment, Qualifications, and Training System (PAQTS). This Task V report provides the documentation for PAQTS including the Functional Requirements Document (FRD), the Data Requirements Document (DRD), the Hardware and Software Capabilities Assessment, and the Detailed Implementation Schedule. Specific recommendations to facilitate implementation of PAQTS are also included.

46 CFR 107.305 - Plans and information.

Code of Federal Regulations, 2013 CFR

2013-10-01

... systems. Marine Engineering (z) Plans required for marine engineering equipment and systems by Subchapter F of this chapter. Electrical Engineering (aa) Plans required for electrical engineering equipment... materials that do not conform to ABS or ASTM specifications, complete specifications, including chemical and...

System requirement specification for the IH-10 Integrated Corridor Management System (ICMS) in San Antonio, Texas

DOT National Transportation Integrated Search

2008-03-31

This Requirements Specification Document (RSD) was developed under the project titled TransGuide Integrated Corridor Management Stage 1 as part of the United States Department of Transportation (USDOT) Integrated Corridor Management (ICM) p...

Power System Mass Analysis for Hydrogen Reduction Oxygen Production on the Lunar Surface

NASA Technical Reports Server (NTRS)

Colozza, Anthony J.

2009-01-01

The production of oxygen from the lunar regolith requires both thermal and electrical power in roughly similar proportions. This unique power requirement is unlike most applications on the lunar surface. To efficiently meet these requirements, both solar PV array and solar concentrator systems were evaluated. The mass of various types of photovoltaic and concentrator based systems were calculated to determine the type of power system that provided the highest specific power. These were compared over a range of oxygen production rates. Also a hybrid type power system was also considered. This system utilized a photovoltaic array to produce the electrical power and a concentrator to provide the thermal power. For a single source system the three systems with the highest specific power were a flexible concentrator/Stirling engine system, a rigid concentrator/Stirling engine system and a tracking triple junction solar array system. These systems had specific power values of 43, 34, and 33 W/kg, respectively. The hybrid power system provided much higher specific power values then the single source systems. The best hybrid combinations were the triple junction solar array with the flexible concentrator and the rigid concentrator. These systems had a specific power of 81 and 68 W/kg, respectively.

IDC System Specification Document Version 1.1.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Harris, James M.; Lober, Randall R.

2015-02-01

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Reengineering Phase 2 project. Revisions Version Date Author/Team Revision Description Authorized by V1.0 12/2014 IDC Reengineering Project Team Initial delivery M. Harris V1.1 2/2015 IDC Reengineering Project Team Iteration I2 Review Comments M. Harris

DEVS Unified Process for Web-Centric Development and Testing of System of Systems

DTIC Science & Technology

2008-05-20

gathering from the user. Further, methodologies have been developed to generate DEVS models from BPMN /BPEL-based and message-based requirement specifications...27] 3. BPMN /BPEL based system specifications: Business Process Modeling Notation ( BPMN ) [bpm] or Business Process Execution Language (BPEL) provide a...information is stored in .wsdl and .bpel files for BPEL but in proprietary format for BPMN . 4. DoDAF-based requirement specifications: Department of

Validation Methods Research for Fault-Tolerant Avionics and Control Systems: Working Group Meeting, 2

NASA Technical Reports Server (NTRS)

Gault, J. W. (Editor); Trivedi, K. S. (Editor); Clary, J. B. (Editor)

1980-01-01

The validation process comprises the activities required to insure the agreement of system realization with system specification. A preliminary validation methodology for fault tolerant systems documented. A general framework for a validation methodology is presented along with a set of specific tasks intended for the validation of two specimen system, SIFT and FTMP. Two major areas of research are identified. First, are those activities required to support the ongoing development of the validation process itself, and second, are those activities required to support the design, development, and understanding of fault tolerant systems.

Enabling Requirements-Based Programming for Highly-Dependable Complex Parallel and Distributed Systems

NASA Technical Reports Server (NTRS)

Hinchey, Michael G.; Rash, James L.; Rouff, Christopher A.

2005-01-01

The manual application of formal methods in system specification has produced successes, but in the end, despite any claims and assertions by practitioners, there is no provable relationship between a manually derived system specification or formal model and the customer's original requirements. Complex parallel and distributed system present the worst case implications for today s dearth of viable approaches for achieving system dependability. No avenue other than formal methods constitutes a serious contender for resolving the problem, and so recognition of requirements-based programming has come at a critical juncture. We describe a new, NASA-developed automated requirement-based programming method that can be applied to certain classes of systems, including complex parallel and distributed systems, to achieve a high degree of dependability.

Systems, methods and apparatus for modeling, specifying and deploying policies in autonomous and autonomic systems using agent-oriented software engineering

NASA Technical Reports Server (NTRS)

Sterritt, Roy (Inventor); Hinchey, Michael G. (Inventor); Penn, Joaquin (Inventor)

2011-01-01

Systems, methods and apparatus are provided through which in some embodiments, an agent-oriented specification modeled with MaCMAS, is analyzed, flaws in the agent-oriented specification modeled with MaCMAS are corrected, and an implementation is derived from the corrected agent-oriented specification. Described herein are systems, method and apparatus that produce fully (mathematically) tractable development of agent-oriented specification(s) modeled with methodology fragment for analyzing complex multiagent systems (MaCMAS) and policies for autonomic systems from requirements through to code generation. The systems, method and apparatus described herein are illustrated through an example showing how user formulated policies can be translated into a formal mode which can then be converted to code. The requirements-based programming systems, method and apparatus described herein may provide faster, higher quality development and maintenance of autonomic systems based on user formulation of policies.

Space station needs, attributes and architectural options study. Volume 3: Requirements

NASA Technical Reports Server (NTRS)

1983-01-01

A typical system specification format is presented and requirements are compiled. A Program Specification Tree is shown showing a high inclination space station and a low inclination space station with their typical element breakdown, also represented along the top blocks are the interfaces with other systems. The specification format is directed at the Low Inclination space station.

Enhancing requirements engineering for patient registry software systems with evidence-based components.

PubMed

Lindoerfer, Doris; Mansmann, Ulrich

2017-07-01

Patient registries are instrumental for medical research. Often their structures are complex and their implementations use composite software systems to meet the wide spectrum of challenges. Commercial and open-source systems are available for registry implementation, but many research groups develop their own systems. Methodological approaches in the selection of software as well as the construction of proprietary systems are needed. We propose an evidence-based checklist, summarizing essential items for patient registry software systems (CIPROS), to accelerate the requirements engineering process. Requirements engineering activities for software systems follow traditional software requirements elicitation methods, general software requirements specification (SRS) templates, and standards. We performed a multistep procedure to develop a specific evidence-based CIPROS checklist: (1) A systematic literature review to build a comprehensive collection of technical concepts, (2) a qualitative content analysis to define a catalogue of relevant criteria, and (3) a checklist to construct a minimal appraisal standard. CIPROS is based on 64 publications and covers twelve sections with a total of 72 items. CIPROS also defines software requirements. Comparing CIPROS with traditional software requirements elicitation methods, SRS templates and standards show a broad consensus but differences in issues regarding registry-specific aspects. Using an evidence-based approach to requirements engineering for registry software adds aspects to the traditional methods and accelerates the software engineering process for registry software. The method we used to construct CIPROS serves as a potential template for creating evidence-based checklists in other fields. The CIPROS list supports developers in assessing requirements for existing systems and formulating requirements for their own systems, while strengthening the reporting of patient registry software system descriptions. It may be a first step to create standards for patient registry software system assessments. Copyright © 2017 Elsevier Inc. All rights reserved.

30 CFR 23.7 - Specific requirements for approval.

Code of Federal Regulations, 2013 CFR

2013-07-01

..., EVALUATION, AND APPROVAL OF MINING PRODUCTS TELEPHONES AND SIGNALING DEVICES § 23.7 Specific requirements for... apply. (g) Line powered telephones and signaling devices or systems shall be equipped with standby power... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Specific requirements for approval. 23.7...

30 CFR 23.7 - Specific requirements for approval.

Code of Federal Regulations, 2014 CFR

2014-07-01

..., EVALUATION, AND APPROVAL OF MINING PRODUCTS TELEPHONES AND SIGNALING DEVICES § 23.7 Specific requirements for... apply. (g) Line powered telephones and signaling devices or systems shall be equipped with standby power... 30 Mineral Resources 1 2014-07-01 2014-07-01 false Specific requirements for approval. 23.7...

30 CFR 23.7 - Specific requirements for approval.

Code of Federal Regulations, 2012 CFR

2012-07-01

..., EVALUATION, AND APPROVAL OF MINING PRODUCTS TELEPHONES AND SIGNALING DEVICES § 23.7 Specific requirements for... apply. (g) Line powered telephones and signaling devices or systems shall be equipped with standby power... 30 Mineral Resources 1 2012-07-01 2012-07-01 false Specific requirements for approval. 23.7...

Connected Vehicle Pilot Deployment Program Phase 1, System Requirements Specification (SyRS) – New York City.

DOT National Transportation Integrated Search

2016-07-28

This document describes the System Requirements Specification (SyRS) for the New York City Department of Transportation (NYC) Connected Vehicle Pilot Deployment (CVPD) Project. This SyRS describes the results of the definition of need, the operationa...

Space Generic Open Avionics Architecture (SGOAA) standard specification

NASA Technical Reports Server (NTRS)

Wray, Richard B.; Stovall, John R.

1993-01-01

The purpose of this standard is to provide an umbrella set of requirements for applying the generic architecture interface model to the design of a specific avionics hardware/software system. This standard defines a generic set of system interface points to facilitate identification of critical interfaces and establishes the requirements for applying appropriate low level detailed implementation standards to those interface points. The generic core avionics system and processing architecture models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.

Spaceflight Human System Standards

NASA Technical Reports Server (NTRS)

Holubec, Keith; Tillman, Barry; Connolly, Jan

2009-01-01

NASA created a new approach for human system integration and human performance standards. NASA created two documents a standard and a reference handbook. The standard is titled NASA Space Flight Human-System Standard (SFHSS) and consists of two-volumes: Volume 1- Crew Health This volume covers standards needed to support astronaut health (medical care, nutrition, sleep, exercise, etc.) Volume 2 Human Factors, Habitability and Environmental Health This volume covers the standards for system design that will maintain astronaut performance (ie., environmental factors, design of facilities, layout of workstations, and lighting requirements). It includes classic human factors requirements. The new standards document is written in terms so that it is applicable to a broad range of present and future NASA systems. The document states that all new programs prepare system-specific requirements that will meet the general standards. For example, the new standard does not specify a design should accommodate specific percentiles of a defined population. Rather, NASA-STD-3001, Volume 2 states that all programs shall prepare program-specific requirements that define the user population and their size ranges. The design shall then accommodate the full size range of those users. The companion reference handbook, Human Integration Design Handbook (HIDH), was developed to capture the design consideration information from NASA-STD-3000, and adds spaceflight lessons learned, gaps in knowledge, example solutions, and suggests research to further mature specific disciplines. The HIDH serves two major purposes: HIDH is the reference document for writing human factors requirements for specific systems. HIDH contains design guidance information that helps insure that designers create systems which safely and effectively accommodate the capabilities and limitations of space flight crews.

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) OCEANOGRAPHIC RESEARCH VESSELS INSPECTION AND CERTIFICATION Plan Approval § 189.55-5 Plans and specifications..., carbon dioxide, foam and sprinkling systems. (e) Marine engineering. For plans required for marine engineering equipment and systems. See Subchapter F (Marine Engineering) of this chapter. (f) Electrical...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) OCEANOGRAPHIC RESEARCH VESSELS INSPECTION AND CERTIFICATION Plan Approval § 189.55-5 Plans and specifications..., carbon dioxide, foam and sprinkling systems. (e) Marine engineering. For plans required for marine engineering equipment and systems. See Subchapter F (Marine Engineering) of this chapter. (f) Electrical...

High performance VLSI telemetry data systems

NASA Technical Reports Server (NTRS)

Chesney, J.; Speciale, N.; Horner, W.; Sabia, S.

1990-01-01

NASA's deployment of major space complexes such as Space Station Freedom (SSF) and the Earth Observing System (EOS) will demand increased functionality and performance from ground based telemetry acquisition systems well above current system capabilities. Adaptation of space telemetry data transport and processing standards such as those specified by the Consultative Committee for Space Data Systems (CCSDS) standards and those required for commercial ground distribution of telemetry data, will drive these functional and performance requirements. In addition, budget limitations will force the requirement for higher modularity, flexibility, and interchangeability at lower cost in new ground telemetry data system elements. At NASA's Goddard Space Flight Center (GSFC), the design and development of generic ground telemetry data system elements, over the last five years, has resulted in significant solutions to these problems. This solution, referred to as the functional components approach includes both hardware and software components ready for end user application. The hardware functional components consist of modern data flow architectures utilizing Application Specific Integrated Circuits (ASIC's) developed specifically to support NASA's telemetry data systems needs and designed to meet a range of data rate requirements up to 300 Mbps. Real-time operating system software components support both embedded local software intelligence, and overall system control, status, processing, and interface requirements. These components, hardware and software, form the superstructure upon which project specific elements are added to complete a telemetry ground data system installation. This paper describes the functional components approach, some specific component examples, and a project example of the evolution from VLSI component, to basic board level functional component, to integrated telemetry data system.

Advanced information processing system: Input/output network management software

NASA Technical Reports Server (NTRS)

Nagle, Gail; Alger, Linda; Kemp, Alexander

1988-01-01

The purpose of this document is to provide the software requirements and specifications for the Input/Output Network Management Services for the Advanced Information Processing System. This introduction and overview section is provided to briefly outline the overall architecture and software requirements of the AIPS system before discussing the details of the design requirements and specifications of the AIPS I/O Network Management software. A brief overview of the AIPS architecture followed by a more detailed description of the network architecture.

Information Requirements Specification II: Brainstorming Collective Decision-Making Technique.

ERIC Educational Resources Information Center

Telem, Moshe

1988-01-01

Information requirements specification (IRS) constitutes an Achilles heel in the system life cycle of management information systems. This article establishes a systematic overall IRS technique applicable to organizations of all types and sizes. The technique's integration of brainstorming and theory Z principles creates an effective, stimulating,…

Integrated flight/propulsion control - Subsystem specifications for performance

NASA Technical Reports Server (NTRS)

Neighbors, W. K.; Rock, Stephen M.

1993-01-01

A procedure is presented for calculating multiple subsystem specifications given a number of performance requirements on the integrated system. This procedure applies to problems where the control design must be performed in a partitioned manner. It is based on a structured singular value analysis, and generates specifications as magnitude bounds on subsystem uncertainties. The performance requirements should be provided in the form of bounds on transfer functions of the integrated system. This form allows the expression of model following, command tracking, and disturbance rejection requirements. The procedure is demonstrated on a STOVL aircraft design.

Onboard Inert Gas Generation System/Onboard Oxygen Gas Generation System (OBIGGS/OBOGS) Study. Part 1; Aircraft System Requirements

NASA Technical Reports Server (NTRS)

Reynolds, Thomas L.; Bailey, Delbert B.; Lewinski, Daniel F.; Roseburg, Conrad M.; Palaszewski, Bryan (Technical Monitor)

2001-01-01

The purpose of this technology assessment is to define a multiphase research study program investigating Onboard Inert Gas Generation Systems (OBIGGS) and Onboard Oxygen Generation Systems (OBOGS) that would identify current airplane systems design and certification requirements (Subtask 1); explore state-of-the-art technology (Subtask 2); develop systems specifications (Subtask 3); and develop an initial system design (Subtask 4). If feasible, consideration may be given to the development of a prototype laboratory test system that could potentially be used in commercial transport aircraft (Subtask 5). These systems should be capable of providing inert nitrogen gas for improved fire cargo compartment fire suppression and fuel tank inerting and emergency oxygen for crew and passenger use. Subtask I of this research study, presented herein, defines current production aircraft certification requirements and design objectives necessary to meet mandatory FAA certification requirements and Boeing design and performance specifications. These requirements will be utilized for baseline comparisons for subsequent OBIGGS/OBOGS application evaluations and assessments.

MODIS Information, Data, and Control System (MIDACS) system specifications and conceptual design

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.; Sharts, B.; Folta, D.

1988-01-01

The MODIS Information, Data, and Control System (MIDACS) Specifications and Conceptual Design Document discusses system level requirements, the overall operating environment in which requirements must be met, and a breakdown of MIDACS into component subsystems, which include the Instrument Support Terminal, the Instrument Control Center, the Team Member Computing Facility, the Central Data Handling Facility, and the Data Archive and Distribution System. The specifications include sizing estimates for the processing and storage capacities of each data system element, as well as traffic analyses of data flows between the elements internally, and also externally across the data system interfaces. The specifications for the data system, as well as for the individual planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, and data archive and distribution components, do not yet fully specify the data system in the complete manner needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams have not yet been formed; however, it was possible to develop the specifications and conceptual design based on the present concept of EosDIS, the Level-1 and Level-2 Functional Requirements Documents, the Operations Concept, and through interviews and meetings with key members of the scientific community.

Flight software requirements and design support system

NASA Technical Reports Server (NTRS)

Riddle, W. E.; Edwards, B.

1980-01-01

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.

Satellite services system analysis study: Propellant transfer system

NASA Technical Reports Server (NTRS)

1982-01-01

General servicing requirements, a servicing mission concept and scenario, overall servicing needs, basic servicing equipment, and a general servicing mission configuration layout are addressed. Servicing needs, equipment concepts, system requirements equipment specifications, preliminary designs, and resource requirements for flight hardware for the propellant transfer system are also addressed.

Comparative Evaluations of Four Specification Methods for Real-Time Systems

DTIC Science & Technology

1989-12-01

December 1989 Comparative Evaluations of Four Specification Methods for Real - Time Systems David P. Wood William G. Wood Specification and Design Methods...Methods for Real - Time Systems Abstract: A number of methods have been proposed in the last decade for the specification of system and software requirements...and software specification for real - time systems . Our process for the identification of methods that meet the above criteria is described in greater

Inertial Navigation System for India's Reusable Launch Vehicle-Technology Demonstrator (RLV-TD HEX) Mission

NASA Astrophysics Data System (ADS)

Umadevi, P.; Navas, A.; Karuturi, Kesavabrahmaji; Shukkoor, A. Abdul; Kumar, J. Krishna; Sreekumar, Sreejith; Basim, A. Mohammed

2017-12-01

This work presents the configuration of Inertial Navigation System (INS) used in India's Reusable Launch Vehicle-Technology Demonstrator (RLV-TD) Program. In view of the specific features and requirements of the RLV-TD, specific improvements and modifications were required in the INS. A new system was designed, realised and qualified meeting the mission requirements of RLV-TD, at the same time taking advantage of the flight heritage attained in INS through various Launch vehicle Missions of the country. The new system has additional redundancy in acceleration channel, in-built inclinometer based bias update scheme for acceleration channels and sign conventions as employed in an aircraft. Data acquisition in micro cycle periodicity (10 ms) was incorporated which was required to provide rate and attitude information at higher sampling rate for ascent phase control. Provision was incorporated for acquisition of rate and acceleration data with high resolution for aerodynamic characterisation and parameter estimation. GPS aided navigation scheme was incorporated to meet the stringent accuracy requirements of the mission. Navigation system configuration for RLV-TD, specific features incorporated to meet the mission requirements, various tests carried out and performance during RLV-TD flight are highlighted.

Earth Observatory Satellite system definition study. Report 5: System design and specifications. Volume 5: Specification for EROS operations control center

NASA Technical Reports Server (NTRS)

1974-01-01

The functional, performance, and design requirements for the Operations Control Center (OCC) of the Earth Observatory Satellite (EOS) system are presented. The OCC controls the operations of the EOS satellite to acquire mission data consisting of: (1) thematic mapper data, (2) multispectral scanner data on EOS-A, or High Resolution Pointable Imager data on EOS-B, and (3) data collection system (DCS) data. The various inputs to the OCC are identified. The functional requirements of the OCC are defined. The specific systems and subsystems of the OCC are described and block diagrams are provided.

Requirements specification for nickel cadmium battery expert system

NASA Technical Reports Server (NTRS)

1986-01-01

The requirements for performance, design, test, and qualification of a computer program identified as NICBES, Nickel Cadmium Battery Expert System, is established. The specific spacecraft power system configuration selected was the Hubble Space Telescope (HST) Electrical Power System (EPS) Testbed. Power for the HST comes from a system of 13 Solar Panel Arrays (SPAs) linked to 6 Nickel Cadmium Batteries which are connected to 3 Busses. An expert system, NICBES, will be developed at Martin Marietta Aerospace to recognize a testbed anomaly, identify the malfunctioning component and recommend a course of action. Besides fault diagnosis, NICBES will be able to evaluate battery status, give advice on battery status and provide decision support for the operator. These requirements are detailed.

Space Station Food System

NASA Technical Reports Server (NTRS)

Thurmond, Beverly A.; Gillan, Douglas J.; Perchonok, Michele G.; Marcus, Beth A.; Bourland, Charles T.

1986-01-01

A team of engineers and food scientists from NASA, the aerospace industry, food companies, and academia are defining the Space Station Food System. The team identified the system requirements based on an analysis of past and current space food systems, food systems from isolated environment communities that resemble Space Station, and the projected Space Station parameters. The team is resolving conflicts among requirements through the use of trade-off analyses. The requirements will give rise to a set of specifications which, in turn, will be used to produce concepts. Concept verification will include testing of prototypes, both in 1-g and microgravity. The end-item specification provides an overall guide for assembling a functional food system for Space Station.

Rotor systems research aircraft predesign study. Volume 4: Preliminary draft detail specification

NASA Technical Reports Server (NTRS)

Miller, A. N.; Linden, A. W.

1972-01-01

The RSRA requirements are presented in a detail specification format. Coverage of the requirements includes the following headings: (1) aircraft characteristics, (2) general features of design and construction, (3) aerodynamics, (4) structural design criteria, (5) flight control system, (6) propulsion subsystem, and (7) secondary power and distribution subsystem.

47 CFR 73.317 - FM transmission system requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 4 2010-10-01 2010-10-01 false FM transmission system requirements. 73.317... RADIO BROADCAST SERVICES FM Broadcast Stations § 73.317 FM transmission system requirements. (a) FM... occupied by their emissions in accordance with the specification detailed below. FM broadcast stations...

47 CFR 73.317 - FM transmission system requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 4 2011-10-01 2011-10-01 false FM transmission system requirements. 73.317... RADIO BROADCAST SERVICES FM Broadcast Stations § 73.317 FM transmission system requirements. (a) FM... occupied by their emissions in accordance with the specification detailed below. FM broadcast stations...

Transforming Functional Requirements from UML into BPEL to Efficiently Develop SOA-Based Systems

NASA Astrophysics Data System (ADS)

Vemulapalli, Anisha; Subramanian, Nary

The intended behavior of any system such as services, tasks or functions can be captured by functional requirements of the system. As our dependence on online services has grown steadily, the web applications are being developed employing the SOA. BPEL4WS provides a means for expressing functional requirements of an SOA-based system by providing constructs to capture business goals and objectives for the system. In this paper we propose an approach for transforming user-centered requirements captured using UML into a corresponding BPEL specification, where the business processes are captured by means of use-cases from which UML sequence diagrams and activity diagrams are extracted. Subsequently these UML models are mapped to BPEL specifications that capture the essence of the initial business requirements to develop the SOA-based system by employing CASE tools. A student housing system is used as a case study to illustrate this approach and the system is validated using NetBeans.

Interface Control Specification

DOT National Transportation Integrated Search

1996-06-12

The Requirements Specification Document (#9933.04) identifies the overall system level requirements of the Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center (C-TIC). This document provides details about the data and control flow...

Network operating system focus technology

NASA Technical Reports Server (NTRS)

1985-01-01

An activity structured to provide specific design requirements and specifications for the Space Station Data Management System (DMS) Network Operating System (NOS) is outlined. Examples are given of the types of supporting studies and implementation tasks presently underway to realize a DMS test bed capability to develop hands-on understanding of NOS requirements as driven by actual subsystem test beds participating in the overall Johnson Space Center test bed program. Classical operating system elements and principal NOS functions are listed.

Flight Guidance System Validation Using SPIN

NASA Technical Reports Server (NTRS)

Naydich, Dimitri; Nowakowski, John

1998-01-01

To verify the requirements for the mode control logic of a Flight Guidance System (FGS) we applied SPIN, a widely used software package that supports the formal verification of distributed systems. These requirements, collectively called the FGS specification, were developed at Rockwell Avionics & Communications and expressed in terms of the Consortium Requirements Engineering (CoRE) method. The properties to be verified are the invariants formulated in the FGS specification, along with the standard properties of consistency and completeness. The project had two stages. First, the FGS specification and the properties to be verified were reformulated in PROMELA, the input language of SPIN. This involved a semantics issue, as some constructs of the FGS specification do not have well-defined semantics in CoRE. Then we attempted to verify the requirements' properties using the automatic model checking facilities of SPIN. Due to the large size of the state space of the FGS specification an exhaustive state space analysis with SPIN turned out to be impossible. So we used the supertrace model checking procedure of SPIN that provides for a partial analysis of the state space. During this process, we found some subtle errors in the FGS specification.

Draft Geologic Disposal Requirements Basis for STAD Specification

DOE Office of Scientific and Technical Information (OSTI.GOV)

Ilgen, Anastasia G.; Bryan, Charles R.; Hardin, Ernest

2015-03-25

This document provides the basis for requirements in the current version of Performance Specification for Standardized Transportation, Aging, and Disposal Canister Systems, (FCRD-NFST-2014-0000579) that are driven by storage and geologic disposal considerations. Performance requirements for the Standardized Transportation, Aging, and Disposal (STAD) canister are given in Section 3.1 of that report. Here, the requirements are reviewed and the rationale for each provided. Note that, while FCRD-NFST-2014-0000579 provides performance specifications for other components of the STAD storage system (e.g. storage overpack, transfer and transportation casks, and others), these have no impact on the canister performance during disposal, and are not discussedmore » here.« less

Framework for Architecture Trade Study Using MBSE and Performance Simulation

NASA Technical Reports Server (NTRS)

Ryan, Jessica; Sarkani, Shahram; Mazzuchim, Thomas

2012-01-01

Increasing complexity in modern systems as well as cost and schedule constraints require a new paradigm of system engineering to fulfill stakeholder needs. Challenges facing efficient trade studies include poor tool interoperability, lack of simulation coordination (design parameters) and requirements flowdown. A recent trend toward Model Based System Engineering (MBSE) includes flexible architecture definition, program documentation, requirements traceability and system engineering reuse. As a new domain MBSE still lacks governing standards and commonly accepted frameworks. This paper proposes a framework for efficient architecture definition using MBSE in conjunction with Domain Specific simulation to evaluate trade studies. A general framework is provided followed with a specific example including a method for designing a trade study, defining candidate architectures, planning simulations to fulfill requirements and finally a weighted decision analysis to optimize system objectives.

Specification and Design of Electrical Flight System Architectures with SysML

NASA Technical Reports Server (NTRS)

McKelvin, Mark L., Jr.; Jimenez, Alejandro

2012-01-01

Modern space flight systems are required to perform more complex functions than previous generations to support space missions. This demand is driving the trend to deploy more electronics to realize system functionality. The traditional approach for the specification, design, and deployment of electrical system architectures in space flight systems includes the use of informal definitions and descriptions that are often embedded within loosely coupled but highly interdependent design documents. Traditional methods become inefficient to cope with increasing system complexity, evolving requirements, and the ability to meet project budget and time constraints. Thus, there is a need for more rigorous methods to capture the relevant information about the electrical system architecture as the design evolves. In this work, we propose a model-centric approach to support the specification and design of electrical flight system architectures using the System Modeling Language (SysML). In our approach, we develop a domain specific language for specifying electrical system architectures, and we propose a design flow for the specification and design of electrical interfaces. Our approach is applied to a practical flight system.

Software Dependability and Safety Evaluations ESA's Initiative

NASA Astrophysics Data System (ADS)

Hernek, M.

ESA has allocated funds for an initiative to evaluate Dependability and Safety methods of Software. The objectives of this initiative are; · More extensive validation of Safety and Dependability techniques for Software · Provide valuable results to improve the quality of the Software thus promoting the application of Dependability and Safety methods and techniques. ESA space systems are being developed according to defined PA requirement specifications. These requirements may be implemented through various design concepts, e.g. redundancy, diversity etc. varying from project to project. Analysis methods (FMECA. FTA, HA, etc) are frequently used during requirements analysis and design activities to assure the correct implementation of system PA requirements. The criticality level of failures, functions and systems is determined and by doing that the critical sub-systems are identified, on which dependability and safety techniques are to be applied during development. Proper performance of the software development requires the development of a technical specification for the products at the beginning of the life cycle. Such technical specification comprises both functional and non-functional requirements. These non-functional requirements address characteristics of the product such as quality, dependability, safety and maintainability. Software in space systems is more and more used in critical functions. Also the trend towards more frequent use of COTS and reusable components pose new difficulties in terms of assuring reliable and safe systems. Because of this, its dependability and safety must be carefully analysed. ESA identified and documented techniques, methods and procedures to ensure that software dependability and safety requirements are specified and taken into account during the design and development of a software system and to verify/validate that the implemented software systems comply with these requirements [R1].

Preliminary Candidate Advanced Avionics System (PCAAS). [reduction in single pilot workload during instrument flight rules flight

NASA Technical Reports Server (NTRS)

Teper, G. L.; Hon, R. H.; Smyth, R. K.

1977-01-01

Specifications which define the system functional requirements, the subsystem and interface needs, and other requirements such as maintainability, modularity, and reliability are summarized. A design definition of all required avionics functions and a system risk analysis are presented.

An Object-Based Requirements Modeling Method.

ERIC Educational Resources Information Center

Cordes, David W.; Carver, Doris L.

1992-01-01

Discusses system modeling and specification as it relates to object-based information systems development and software development. An automated system model based on the objects in the initial requirements document is described, the requirements document translator is explained, and a sample application of the technique is provided. (12…

48 CFR 18.107 - AbilityOne specification changes.

Code of Federal Regulations, 2010 CFR

2010-10-01

... changes. 18.107 Section 18.107 Federal Acquisition Regulations System FEDERAL ACQUISITION REGULATION... AbilityOne specification changes. Contracting officers are not held to the notification required when changes in AbilityOne specifications or descriptions are required to meet emergency needs. (See 8.712(d...

Metal- and intermetallic-matrix composites for aerospace propulsion and power systems

NASA Astrophysics Data System (ADS)

Doychak, J.

1992-06-01

Successful development and deployment of metal-matrix composites and intermetallic- matrix composites are critical to reaching the goals of many advanced aerospace propulsion and power development programs. The material requirements are based on the aerospace propulsion and power system requirements, economics, and other factors. Advanced military and civilian aircraft engines will require higher specific strength materials that operate at higher temperatures, and the civilian engines will also require long lifetimes. The specific space propulsion and power applications require hightemperature, high-thermal-conductivity, and high-strength materials. Metal-matrix composites and intermetallic-matrix composites either fulfill or have the potential of fulfilling these requirements.

UTM UAS Service Supplier Specification

NASA Technical Reports Server (NTRS)

Rios, Joseph Lucio

2017-01-01

Within the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) system, the UAS Service Supplier (USS) is a key component. The USS serves several functions. At a high level, those include the following: Bridging communication between UAS Operators and Flight Information Management System (FIMS) Supporting planning of UAS operations Assisting strategic deconfliction of the UTM airspace Providing information support to UAS Operators during operations Helping UAS Operators meet their formal requirements This document provides the minimum set of requirements for a USS. In order to be recognized as a USS within UTM, successful demonstration of satisfying the requirements described herein will be a prerequisite. To ensure various desired qualities (security, fairness, availability, efficiency, maintainability, etc.), this specification relies on references to existing public specifications whenever possible.

Development of a web-based and mobile app to support physical activity in individuals with rheumatoid arthritis: results from the second step of a co-design process.

PubMed

Revenäs, Åsa; Opava, Christina H; Martin, Cathrin; Demmelmaier, Ingrid; Keller, Christina; Åsenlöf, Pernilla

2015-02-09

Long-term adherence to physical activity recommendations remains challenging for most individuals with rheumatoid arthritis (RA) despite evidence for its health benefits. The aim of this study was to provide basic data on system requirement specifications for a Web-based and mobile app to self-manage physical activity. More specifically, we explored the target user group, features of the future app, and correlations between the system requirements and the established behavior change techniques (BCTs). We used a participatory action research design. Qualitative data were collected using multiple methods in four workshops. Participants were 5 individuals with RA, a clinical physiotherapist, an officer from the Swedish Rheumatism Association, a Web designer, and 2 physiotherapy researchers. A taxonomy was used to determine the degree of correlation between the system requirements and established BCTs. Participants agreed that the future Web-based and mobile app should be based on two major components important for maintaining physical activity: (1) a calendar feature for goal setting, planning, and recording of physical activity performance and progress, and (2) a small community feature for positive feedback and support from peers. All system requirements correlated with established BCTs, which were coded as 24 different BCTs. To our knowledge, this study is the first to involve individuals with RA as co-designers, in collaboration with clinicians, researchers, and Web designers, to produce basic data to generate system requirement specifications for an eHealth service. The system requirements correlated to the BCTs, making specifications of content and future evaluation of effectiveness possible.

The Johnson Space Center Management Information Systems (JSCMIS). 1: Requirements Definition and Design Specifications for Versions 2.1 and 2.1.1. 2: Documented Test Scenario Environments. 3: Security Design and Specifications

NASA Technical Reports Server (NTRS)

1986-01-01

The Johnson Space Center Management Information System (JSCMIS) is an interface to computer data bases at NASA Johnson which allows an authorized user to browse and retrieve information from a variety of sources with minimum effort. This issue gives requirements definition and design specifications for versions 2.1 and 2.1.1, along with documented test scenario environments, and security object design and specifications.

Validation of a SysML based design for wireless sensor networks

NASA Astrophysics Data System (ADS)

Berrachedi, Amel; Rahim, Messaoud; Ioualalen, Malika; Hammad, Ahmed

2017-07-01

When developing complex systems, the requirement for the verification of the systems' design is one of the main challenges. Wireless Sensor Networks (WSNs) are examples of such systems. We address the problem of how WSNs must be designed to fulfil the system requirements. Using the SysML Language, we propose a Model Based System Engineering (MBSE) specification and verification methodology for designing WSNs. This methodology uses SysML to describe the WSNs requirements, structure and behaviour. Then, it translates the SysML elements to an analytic model, specifically, to a Deterministic Stochastic Petri Net. The proposed approach allows to design WSNs and study their behaviors and their energy performances.

Advanced information processing system: Input/output system services

NASA Technical Reports Server (NTRS)

Masotto, Tom; Alger, Linda

1989-01-01

The functional requirements and detailed specifications for the Input/Output (I/O) Systems Services of the Advanced Information Processing System (AIPS) are discussed. The introductory section is provided to outline the overall architecture and functional requirements of the AIPS system. Section 1.1 gives a brief overview of the AIPS architecture as well as a detailed description of the AIPS fault tolerant network architecture, while section 1.2 provides an introduction to the AIPS systems software. Sections 2 and 3 describe the functional requirements and design and detailed specifications of the I/O User Interface and Communications Management modules of the I/O System Services, respectively. Section 4 illustrates the use of the I/O System Services, while Section 5 concludes with a summary of results and suggestions for future work in this area.

Standard module approach to scanning requirements for second-generation airborne FLIRs

NASA Astrophysics Data System (ADS)

Ludwiszewski, Alan P.

1995-05-01

This paper examines the specification requirements for the development of standard module scanning components to be used in conjunction with SADA I and SADA II sensor arrays. System-level design considerations are presented to identify a selection of components that is consistent with optimum use of the SADA technology. A limited-rotation electromagnetic actuator, used in conjunction with an angular position sensor and a digital controller, is shown to have the necessary performance and flexibility to perform the frame scan function for a wide range of airborne systems. System level requirements and specifications for an optional interlace scan system are also provided.

Towards Requirements in Systems Engineering for Aerospace IVHM Design

NASA Technical Reports Server (NTRS)

Saxena, Abhinav; Roychoudhury, Indranil; Lin, Wei; Goebel, Kai

2013-01-01

Health management (HM) technologies have been employed for safety critical system for decades, but a coherent systematic process to integrate HM into the system design is not yet clear. Consequently, in most cases, health management resorts to be an after-thought or 'band-aid' solution. Moreover, limited guidance exists for carrying out systems engineering (SE) on the subject of writing requirements for designs with integrated vehicle health management (IVHM). It is well accepted that requirements are key to developing a successful IVHM system right from the concept stage to development, verification, utilization, and support. However, writing requirements for systems with IVHM capability have unique challenges that require the designers to look beyond their own domains and consider the constraints and specifications of other interlinked systems. In this paper we look at various stages in the SE process and identify activities specific to IVHM design and development. More importantly, several relevant questions are posed that system engineers must address at various design and development stages. Addressing these questions should provide some guidance to systems engineers towards writing IVHM related requirements to ensure that appropriate IVHM functions are built into the system design.

Saint Lawrence Seaway Navigation-Aid System Study : Volume III - Appendix C - User's Manual and Documentation of the Ship Maneuvering Requirements Computer Program

DOT National Transportation Integrated Search

1978-09-01

The requirements for a navigation guidance system which will effect an increase in the ship processing capacity of the Saint Lawrence Seaway (Lake Ontario to Montreal, Quebec) are developed. The requirements include a specification of system position...

76 FR 34287 - ITS Joint Program Office; Core System Requirements Walkthrough and Architecture Proposal Review...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-13

... Architecture Proposal Review Meetings and Webinars; Notice of Public Meeting AGENCY: Research and Innovative... webinars to discuss the Vehicle to Infrastructure (V2I) Core System Requirements and Architecture Proposal... review of System Requirements Specification and Architecture Proposal. The second meeting will be a...

Initiating Formal Requirements Specifications with Object-Oriented Models

NASA Technical Reports Server (NTRS)

Ampo, Yoko; Lutz, Robyn R.

1994-01-01

This paper reports results of an investigation into the suitability of object-oriented models as an initial step in developing formal specifications. The requirements for two critical system-level software modules were used as target applications. It was found that creating object-oriented diagrams prior to formally specifying the requirements enhanced the accuracy of the initial formal specifications and reduced the effort required to produce them. However, the formal specifications incorporated some information not found in the object-oriented diagrams, such as higher-level strategy or goals of the software.

Space Generic Open Avionics Architecture (SGOAA) standard specification

NASA Technical Reports Server (NTRS)

Wray, Richard B.; Stovall, John R.

1994-01-01

This standard establishes the Space Generic Open Avionics Architecture (SGOAA). The SGOAA includes a generic functional model, processing structural model, and an architecture interface model. This standard defines the requirements for applying these models to the development of spacecraft core avionics systems. The purpose of this standard is to provide an umbrella set of requirements for applying the generic architecture models to the design of a specific avionics hardware/software processing system. This standard defines a generic set of system interface points to facilitate identification of critical services and interfaces. It establishes the requirement for applying appropriate low level detailed implementation standards to those interfaces points. The generic core avionics functions and processing structural models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.

openEHR Based Systems and the General Data Protection Regulation (GDPR).

PubMed

Sousa, Mariana; Ferreira, Duarte; Santos-Pereira, Cátia; Bacelar, Gustavo; Frade, Samuel; Pestana, Olívia; Cruz-Correia, Ricardo

2018-01-01

The concerns about privacy and personal data protection resulted in reforms of the existing legislation in European Union (EU). The General Data Protection Regulation (GDPR) aims to reform the existing measures on the topic of personal data protection of the European Union citizens, with a strong input on the rights and freedoms of people and in the establishment of rules for the processing of personal data. OpenEHR is a standard that embodies many principles of interoperable and secure software for electronic health records. This work aims to understand to what extent the openEHR standard can be considered a solution for the requirements needed by GDPR. A list of requirements for a Hospital Information Systems (HIS) compliant with GDPR and an identification of openEHR specifications was made. The requirements were categorized and compared with the specifications. The requirements identified for the systems were matched with the openEHR specifications, which result in 16 requirements matched with openEHR. All the specifications identified matched at least one requirement. OpenEHR is a solution for the development of HIS that reinforce privacy and personal data protection, ensuring that they are contemplated in the system development. The institutions can secure that their Eletronic Health Record are compliant with GDPR while safeguarding the medical data quality and, as a result, the healthcare delivery.

77 FR 50726 - Software Requirement Specifications for Digital Computer Software and Complex Electronics Used in...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-08-22

... Computer Software and Complex Electronics Used in Safety Systems of Nuclear Power Plants AGENCY: Nuclear...-1209, ``Software Requirement Specifications for Digital Computer Software and Complex Electronics used... Electronics Engineers (ANSI/IEEE) Standard 830-1998, ``IEEE Recommended Practice for Software Requirements...

I-880 Integrated Corridor Management ICM System Requirements : Final Submittal : System Requirement Specification for the I-880 Corridor in Oakland, California

DOT National Transportation Integrated Search

2008-03-31

This document summarizes the efforts conducted by the I-880 ICM team for the development of the system requirements for the I-880 Integrated Corridor Management System (ICMS). It describes the approach that the I-880 team took in defining the ICMS an...

Navigating the Requirements Jungle

NASA Astrophysics Data System (ADS)

Langer, Boris; Tautschnig, Michael

Research on validation and verification of requirements specifications has thus far focused on functional properties. Yet, in embedded systems, functional requirements constitute only a small fraction of the properties that must hold to guarantee proper and safe operation of the system under design.

UML activity diagrams in requirements specification of logic controllers

NASA Astrophysics Data System (ADS)

Grobelna, Iwona; Grobelny, Michał

2015-12-01

Logic controller specification can be prepared using various techniques. One of them is the wide understandable and user-friendly UML language and its activity diagrams. Using formal methods during the design phase increases the assurance that implemented system meets the project requirements. In the approach we use the model checking technique to formally verify a specification against user-defined behavioral requirements. The properties are usually defined as temporal logic formulas. In the paper we propose to use UML activity diagrams in requirements definition and then to formalize them as temporal logic formulas. As a result, UML activity diagrams can be used both for logic controller specification and for requirements definition, what simplifies the specification and verification process.

Investigation of specification measures for the Software Engineering Laboratory (SEL)

NASA Technical Reports Server (NTRS)

1984-01-01

Requirements specification measures are investigated for potential application in the Software Engineering Laboratory. Eighty-seven candidate measures are defined; sixteen are recommended for use. Most measures are derived from a new representation, the Composite Specification Model, which is introduced. The results of extracting the specification measures from the requirements of a real system are described.

Software Requirements Specification for an Ammunition Management System

DTIC Science & Technology

1986-09-01

thesis takes the form of a software requirements specification. Such a specification, according to Pressman [Ref. 7], establishes a complete...defined by Pressman , is depicted in Figure 1.1. 11 Figure 1.1 Generalized Software Life Cycle The common thread which binds the various phases together...application of software engineering principles requires an established methodology. This methodology, according to Pressman [Ref. 8:p. 151 is an

Improving Building Construction Specifications in State and Local Governments

NASA Technical Reports Server (NTRS)

1980-01-01

State and local governments can benefit from master specifications systems that centralize data on all types of building materials, products, and processes. Most of these systems are organized according to the MASTERFORMAT system, which, along with guide specifications that require the insertion or deletion of standardized information, resulted from the specific needs of users and providers. For jurisdictions preparing their own specifications, staff time and cost are reduced. For those subcontracting the preparation, master specifications provide a means of evaluating the specifications submitted. Current management specification systems described include SPECINTACT, OMSPEC, MASTERPEC, and the NAVFAC, Corps of Engineers, and GSA guide specifications.

DRS: Derivational Reasoning System

NASA Technical Reports Server (NTRS)

Bose, Bhaskar

1995-01-01

The high reliability requirements for airborne systems requires fault-tolerant architectures to address failures in the presence of physical faults, and the elimination of design flaws during the specification and validation phase of the design cycle. Although much progress has been made in developing methods to address physical faults, design flaws remain a serious problem. Formal methods provides a mathematical basis for removing design flaws from digital systems. DRS (Derivational Reasoning System) is a formal design tool based on advanced research in mathematical modeling and formal synthesis. The system implements a basic design algebra for synthesizing digital circuit descriptions from high level functional specifications. DRS incorporates an executable specification language, a set of correctness preserving transformations, verification interface, and a logic synthesis interface, making it a powerful tool for realizing hardware from abstract specifications. DRS integrates recent advances in transformational reasoning, automated theorem proving and high-level CAD synthesis systems in order to provide enhanced reliability in designs with reduced time and cost.

Bipolar Nickel-hydrogen Batteries for Aerospace Applications

NASA Technical Reports Server (NTRS)

Koehler, C. W.; Vanommering, G.; Puester, N. H.; Puglisi, V. J.

1984-01-01

A bipolar nickel-hydrogen battery which effectively addresses all key requirements for a spacecraft power system, including long-term reliability and low mass, is discussed. The design of this battery is discussed in the context of system requirements and nickel-hydrogen battery technology in general. To achieve the ultimate goal of an aerospace application of a bipolar Ni-H2 battery several objectives must be met in the design and development of the system. These objectives include: maximization of reliability and life; high specific energy and energy density; reasonable cost of manufacture, test, and integration; and ease in scaling for growth in power requirements. These basic objectives translate into a number of specific design requirements, which are discussed.

Conceptual design studies of control and instrumentation systems for ignition experiments

DOE Office of Scientific and Technical Information (OSTI.GOV)

Nicholson, P.J.; Dewolf, J.B.; Heinemann, P.C.

1978-03-01

Studies at the Charles Stark Draper Laboratory in the past year were a continuation of prior studies of control and instrumentation systems for current and next generation Tokomaks. Specifically, the FY 77 effort has focused on the following two main efforts: (1) control requirements--(a) defining and evolving control requirements/concepts for a prototype experimental power reactor(s), and (b) defining control requirements for diverters and mirror machines, specifically the MX; and (2) defining requirements and scoping design for a functional control simulator. Later in the year, a small additional task was added: (3) providing analysis and design support to INESCO for itsmore » low cost fusion power system, FPC/DMT.« less

Quality requirements for reclaimed/recycled water

NASA Technical Reports Server (NTRS)

Janik, Daniel S.; Sauer, Richard L.; Pierson, Duane L.; Thorstenson, Yvonne R.

1987-01-01

Water used during current and previous space missions has been either carried or made aloft. Future human space endeavors will require some form of water reclamation and recycling. There is little experience in the U.S. space program with this technology. Water reclamation and recycling constitute engineering challenges of the broadest nature that will require an intensive research and development effort if this technology is to mature in time for practical use on the proposed U.S. Space Station. In order for this to happen, reclaimed/recycled water specifications will need to be devised to guide engineering development. Present NASA Potable Water Specifications are not applicable to reclaimed or recycled water. Adequate specifications for ensuring the quality of the reclaimed or recycled potable water system is reviewed, limitations of present water specifications are examined, world experience with potable water reclamation/recycling systems and systems analogs is reviewed, and an approach to developing pertinent biomedical water specifications for spacecraft is presented. Space Station water specifications should be designed to ensure the health of all likely spacecraft inhabitants including man, animals, and plants.

An iterative requirements specification procedure for decision support systems.

PubMed

Brookes, C H

1987-08-01

Requirements specification is a key element in a DSS development project because it not only determines what is to be done, it also drives the evolution process. A procedure for requirements elicitation is described that is based on the decomposition of the DSS design task into a number of functions, subfunctions, and operators. It is postulated that the procedure facilitates the building of a DSS that is complete and integrates MIS, modelling and expert system components. Some examples given are drawn from the health administration field.

From Science To Design: Systems Engineering For The Lsst

NASA Astrophysics Data System (ADS)

Claver, Chuck F.; Axelrod, T.; Fouts, K.; Kantor, J.; Nordby, M.; Sebag, J.; LSST Collaboration

2009-01-01

The LSST is a universal-purpose survey telescope that will address scores of scientific missions. To assist the technical teams to convergence to a specific engineering design, the LSST Science Requirements Document (SRD) selects four stressing principle scientific missions: 1) Constraining Dark Matter and Dark Energy; 2) taking an Inventory of the Solar System; 3) Exploring the Transient Optical Sky; and 4) mapping the Milky Way. From these 4 missions the SRD specifies the needed requirements for single images and the full 10 year survey that enables a wide range of science beyond the 4 principle missions. Through optical design and analysis, operations simulation, and throughput modeling the systems engineering effort in the LSST has largely focused on taking the SRD specifications and deriving system functional requirements that define the system design. A Model Based Systems Engineering approach with SysML is used to manage the flow down of requirements from science to system function to sub-system. The rigor of requirements flow and management assists the LSST in keeping the overall scope, hence budget and schedule, under control.

40 CFR 60.1275 - What additional requirements must I meet for the operation of my continuous emission monitoring...

Code of Federal Regulations, 2010 CFR

2010-07-01

... meet for the operation of my continuous emission monitoring systems and continuous opacity monitoring... additional requirements must I meet for the operation of my continuous emission monitoring systems and continuous opacity monitoring system? Use the required span values and applicable performance specifications...

40 CFR 60.1275 - What additional requirements must I meet for the operation of my continuous emission monitoring...

Code of Federal Regulations, 2011 CFR

2011-07-01

... meet for the operation of my continuous emission monitoring systems and continuous opacity monitoring... additional requirements must I meet for the operation of my continuous emission monitoring systems and continuous opacity monitoring system? Use the required span values and applicable performance specifications...

Identification of emergent off-nominal operational requirements during conceptual architecting of the more electric aircraft

NASA Astrophysics Data System (ADS)

Armstrong, Michael James

Increases in power demands and changes in the design practices of overall equipment manufacturers has led to a new paradigm in vehicle systems definition. The development of unique power systems architectures is of increasing importance to overall platform feasibility and must be pursued early in the aircraft design process. Many vehicle systems architecture trades must be conducted concurrent to platform definition. With an increased complexity introduced during conceptual design, accurate predictions of unit level sizing requirements must be made. Architecture specific emergent requirements must be identified which arise due to the complex integrated effect of unit behaviors. Off-nominal operating scenarios present sizing critical requirements to the aircraft vehicle systems. These requirements are architecture specific and emergent. Standard heuristically defined failure mitigation is sufficient for sizing traditional and evolutionary architectures. However, architecture concepts which vary significantly in terms of structure and composition require that unique failure mitigation strategies be defined for accurate estimations of unit level requirements. Identifying of these off-nominal emergent operational requirements require extensions to traditional safety and reliability tools and the systematic identification of optimal performance degradation strategies. Discrete operational constraints posed by traditional Functional Hazard Assessment (FHA) are replaced by continuous relationships between function loss and operational hazard. These relationships pose the objective function for hazard minimization. Load shedding optimization is performed for all statistically significant failures by varying the allocation of functional capability throughout the vehicle systems architecture. Expressing hazards, and thereby, reliability requirements as continuous relationships with the magnitude and duration of functional failure requires augmentations to the traditional means for system safety assessment (SSA). The traditional two state and discrete system reliability assessment proves insufficient. Reliability is, therefore, handled in an analog fashion: as a function of magnitude of failure and failure duration. A series of metrics are introduced which characterize system performance in terms of analog hazard probabilities. These include analog and cumulative system and functional risk, hazard correlation, and extensions to the traditional component importance metrics. Continuous FHA, load shedding optimization, and analog SSA constitute the SONOMA process (Systematic Off-Nominal Requirements Analysis). Analog system safety metrics inform both architecture optimization (changes in unit level capability and reliability) and architecture augmentation (changes in architecture structure and composition). This process was applied for two vehicle systems concepts (conventional and 'more-electric') in terms of loss/hazard relationships with varying degrees of fidelity. Application of this process shows that the traditional assumptions regarding the structure of the function loss vs. hazard relationship apply undue design bias to functions and components during exploratory design. This bias is illustrated in terms of inaccurate estimations of the system and function level risk and unit level importance. It was also shown that off-nominal emergent requirements must be defined specific to each architecture concept. Quantitative comparisons of architecture specific off-nominal performance were obtained which provide evidence to the need for accurate definition of load shedding strategies during architecture exploratory design. Formally expressing performance degradation strategies in terms of the minimization of a continuous hazard space enhances the system architects ability to accurately predict sizing critical emergent requirements concurrent to architecture definition. Furthermore, the methods and frameworks generated here provide a structured and flexible means for eliciting these architecture specific requirements during the performance of architecture trades.

Requirements Specification Language (RSL) and supporting tools

NASA Technical Reports Server (NTRS)

Frincke, Deborah; Wolber, Dave; Fisher, Gene; Cohen, Gerald C.

1992-01-01

This document describes a general purpose Requirement Specification Language (RSL). RSL is a hybrid of features found in several popular requirement specification languages. The purpose of RSL is to describe precisely the external structure of a system comprised of hardware, software, and human processing elements. To overcome the deficiencies of informal specification languages, RSL includes facilities for mathematical specification. Two RSL interface tools are described. The Browser view contains a complete document with all details of the objects and operations. The Dataflow view is a specialized, operation-centered depiction of a specification that shows how specified operations relate in terms of inputs and outputs.

Freight advanced traveler information system : functional requirements.

DOT National Transportation Integrated Search

2012-08-01

This report describes the System Requirement Specifications (SyRS) for a Freight Advanced Traveler Information System (FRATIS). The SyRS is based on user needs described in the FRATIS Concept of Operations (ConOps), which cover the essential function...

Earth Observatory Satellite system definition study. Report no. 5: System design and specifications. Part 2: Ground system element specifications

NASA Technical Reports Server (NTRS)

1974-01-01

The Ground System requirements for the Land Resources Management (LRM) type-A and type-B missions of the Earth Observatory Satellite (EOS) program are presented. Specifications for the Thematic Mapper data processing are provided (LRM A mission). The specifications also cover the R and D instruments (Thematic Mapper and High Resolution Pointable Imager) data processing for the LRM type-B mission.

NASA software specification and evaluation system: Software verification/validation techniques

NASA Technical Reports Server (NTRS)

1977-01-01

NASA software requirement specifications were used in the development of a system for validating and verifying computer programs. The software specification and evaluation system (SSES) provides for the effective and efficient specification, implementation, and testing of computer software programs. The system as implemented will produce structured FORTRAN or ANSI FORTRAN programs, but the principles upon which SSES is designed allow it to be easily adapted to other high order languages.

Modular space station phase B extension preliminary performance specification. Volume 1: Initial station systems

NASA Technical Reports Server (NTRS)

1971-01-01

The general, operational, design/construction, and subsystem design requirements are presented for a solar powered modular space station system. While these requirements apply only to the initial station system, the system is readily adaptable to a growth configuration.

Stakeholder Alignment for Requirements in GEOValue

NASA Astrophysics Data System (ADS)

Cutcher-Gershenfeld, J.; King, J. L.

2016-12-01

Observation systems that collect information on environmental parameters relevant to biological and physical earth resources provide value. This has been demonstrated so many times in so many ways that it is not worth deliberating. Earlier projects for research (whether it is possible to do this or that), or for "dual use," typically involving defense, have been successful. Wealthy parties have built their own systems. Less wealthy parties seek to sustain the systems they have built. The history of systems suggests that "requirements" will be the next step. The objective is to maximize the "return" on the substantial investment required for construction, deployment, maintenance and renewal of observation systems. Stakeholders and their interests are assessed to construct the requirements from which specifications are built. Specifications drive procurement, and procurement produces built systems. Complicated (e.g. space-based) systems have long times between requirements analysis and deployment. It all depends on getting the requirements right, which depends on understanding stakeholders and requirements. And this is where things get complicated. Stakeholders and interests change, sometimes rapidly, as what is possible is altered. It becomes increasingly difficult to achieve stakeholder alignment required for effective management of constituent politics at the heart of any expensive endeavor. This paper presents results from a major study of stakeholder alignment in the Earth Sciences, focused especially on EarthCube.

Design, Specification, and Synthesis of Aircraft Electric Power Systems Control Logic

NASA Astrophysics Data System (ADS)

Xu, Huan

Cyber-physical systems integrate computation, networking, and physical processes. Substantial research challenges exist in the design and verification of such large-scale, distributed sensing, actuation, and control systems. Rapidly improving technology and recent advances in control theory, networked systems, and computer science give us the opportunity to drastically improve our approach to integrated flow of information and cooperative behavior. Current systems rely on text-based specifications and manual design. Using new technology advances, we can create easier, more efficient, and cheaper ways of developing these control systems. This thesis will focus on design considerations for system topologies, ways to formally and automatically specify requirements, and methods to synthesize reactive control protocols, all within the context of an aircraft electric power system as a representative application area. This thesis consists of three complementary parts: synthesis, specification, and design. The first section focuses on the synthesis of central and distributed reactive controllers for an aircraft elec- tric power system. This approach incorporates methodologies from computer science and control. The resulting controllers are correct by construction with respect to system requirements, which are formulated using the specification language of linear temporal logic (LTL). The second section addresses how to formally specify requirements and introduces a domain-specific language for electric power systems. A software tool automatically converts high-level requirements into LTL and synthesizes a controller. The final sections focus on design space exploration. A design methodology is proposed that uses mixed-integer linear programming to obtain candidate topologies, which are then used to synthesize controllers. The discrete-time control logic is then verified in real-time by two methods: hardware and simulation. Finally, the problem of partial observability and dynamic state estimation is explored. Given a set placement of sensors on an electric power system, measurements from these sensors can be used in conjunction with control logic to infer the state of the system.

Towards the formal specification of the requirements and design of a processor interface unit: HOL listings

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1993-01-01

This technical report contains the HOL listings of the specification of the design and major portions of the requirements for a commercially developed processor interface unit (or PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU specification as it currently exists. Section two of this report contains general-purpose HOL theories that support the PIU specification. These theories include definitions for the hardware components used in the PIU, our implementation of bit words, and our implementation of temporal logic. Section three contains the HOL listings for the PIU design specification. Aside from the PIU internal bus (I-Bus), this specification is complete. Section four contains the HOL listings for a major portion of the PIU requirements specification. Specifically, it contains most of the definition for the PIU behavior associated with memory accesses initiated by the local processor.

40 CFR 63.1095 - What specific requirements must I comply with?

Code of Federal Regulations, 2012 CFR

2012-07-01

... according to any of the options in 40 CFR 61.342(c)(1) through (e) or transfer waste off-site. If you elect... Systems and Waste Operations Waste Requirements § 63.1095 What specific requirements must I comply with? For waste that is not transferred off-site, you must comply with the requirements in paragraph (a) of...

40 CFR 63.1095 - What specific requirements must I comply with?

Code of Federal Regulations, 2014 CFR

2014-07-01

... according to any of the options in 40 CFR 61.342(c)(1) through (e) or transfer waste off-site. If you elect... Systems and Waste Operations Waste Requirements § 63.1095 What specific requirements must I comply with? For waste that is not transferred off-site, you must comply with the requirements in paragraph (a) of...

Requirements Verification Report AN Farm to 200 E Waste Transfer System for Project W-314 Tank Farm Restoration & Safe Operations

DOE Office of Scientific and Technical Information (OSTI.GOV)

MCGREW, D.L.

2001-10-31

This Requirements Verification Report provides the traceability of how Project W-314 fulfilled the Project Development Specification requirements for the AN Farm to 200E Waste Transfer System Upgrade package.

International Low Impact Docking System (iLIDS) Project Technical Requirements Specification, Revision F

NASA Technical Reports Server (NTRS)

Lewis, James L.

2011-01-01

The NASA Docking System (NDS) is NASA's implementation for the emerging International Docking System Standard (IDSS) using low impact docking technology. The NASA Docking System Project (NDSP) is the International Space Station (ISS) Program's project to produce the NDS, Common Docking Adapter (CDA) and Docking Hub. The NDS design evolved from the Low Impact Docking System (LIDS). The acronym international Low Impact Docking System (iLIDS) is also used to describe this system as well as the Government Furnished Equipment (GFE) project designing the NDS for the NDSP. NDS and iLIDS may be used interchangeability. This document will use the acronym iLIDS. Some of the heritage documentation and implementations (e.g., software command names, requirement identification (ID), figures, etc.) used on NDS will continue to use the LIDS acronym. This specification defines the technical requirements for the iLIDS GFE delivered to the NDSP by the iLIDS project. This document contains requirements for two iLIDS configurations, SEZ29101800-301 and SEZ29101800-302. Requirements with the statement, iLIDS shall, are for all configurations. Examples of requirements that are unique to a single configuration may be identified as iLIDS (-301) shall or iLIDS (-302) shall. Furthermore, to allow a requirement to encompass all configurations with an exception, the requirement may be designated as iLIDS (excluding -302) shall. Verification requirements for the iLIDS project are identified in the Verification Matrix (VM) provided in the iLIDS Verification and Validation Document, JSC-63966. The following definitions differentiate between requirements and other statements: Shall: This is the only verb used for the binding requirements. Should/May: These verbs are used for stating non-mandatory goals. Will: This verb is used for stating facts or declaration of purpose. A Definition of Terms table is provided in Appendix B to define those terms with specific tailored uses in this document.

Decision Support System Requirements Definition for Human Extravehicular Activity Based on Cognitive Work Analysis

PubMed Central

Miller, Matthew James; McGuire, Kerry M.; Feigh, Karen M.

2016-01-01

The design and adoption of decision support systems within complex work domains is a challenge for cognitive systems engineering (CSE) practitioners, particularly at the onset of project development. This article presents an example of applying CSE techniques to derive design requirements compatible with traditional systems engineering to guide decision support system development. Specifically, it demonstrates the requirements derivation process based on cognitive work analysis for a subset of human spaceflight operations known as extravehicular activity. The results are presented in two phases. First, a work domain analysis revealed a comprehensive set of work functions and constraints that exist in the extravehicular activity work domain. Second, a control task analysis was performed on a subset of the work functions identified by the work domain analysis to articulate the translation of subject matter states of knowledge to high-level decision support system requirements. This work emphasizes an incremental requirements specification process as a critical component of CSE analyses to better situate CSE perspectives within the early phases of traditional systems engineering design. PMID:28491008

Decision Support System Requirements Definition for Human Extravehicular Activity Based on Cognitive Work Analysis.

PubMed

Miller, Matthew James; McGuire, Kerry M; Feigh, Karen M

2017-06-01

The design and adoption of decision support systems within complex work domains is a challenge for cognitive systems engineering (CSE) practitioners, particularly at the onset of project development. This article presents an example of applying CSE techniques to derive design requirements compatible with traditional systems engineering to guide decision support system development. Specifically, it demonstrates the requirements derivation process based on cognitive work analysis for a subset of human spaceflight operations known as extravehicular activity . The results are presented in two phases. First, a work domain analysis revealed a comprehensive set of work functions and constraints that exist in the extravehicular activity work domain. Second, a control task analysis was performed on a subset of the work functions identified by the work domain analysis to articulate the translation of subject matter states of knowledge to high-level decision support system requirements. This work emphasizes an incremental requirements specification process as a critical component of CSE analyses to better situate CSE perspectives within the early phases of traditional systems engineering design.

PIP-II Cryogenic System and the Evolution of Superfluid Helium Cryogenic Plant Specifications

DOE Office of Scientific and Technical Information (OSTI.GOV)

Chakravarty, Anindya; Rane, Tejas; Klebaner, Arkadiy

2017-01-01

PIP-II cryogenic system: Superfluid Helium Cryogenic Plant (SHCP) and Cryogenic Distribution System (CDS) connecting the SHCP and the SC Linac (25 cryomodules) PIP-II Cryogenic System Static and dynamic heat loads for the SC Linac and static load of CDS listed out Simulation study carried out to compute SHe flow requirements for each cryomodule Comparison between the flow requirements of the cryomodules for the CW and pulsed modes of operation presented From computed heat load and pressure drop values, SHCP basic specifications evolved.

46 CFR 161.002-4 - General requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... protected spaces. To meet this end, the basic requirements of the fire-protective systems are reliability... systems. (3) All parts of the system must pass the environmental tests for control and monitoring... tests of Lloyd's Register Type Approval System, Test Specification Number 1, as appropriate. (4) Those...

Systems Operation Studies for Automated Guideway Transit Systems: Feeder Systems Model Functional Specification

DOT National Transportation Integrated Search

1981-01-01

This document specifies the functional requirements for the AGT-SOS Feeder Systems Model (FSM), the type of hardware required, and the modeling techniques employed by the FSM. The objective of the FSM is to map the zone-to-zone transit patronage dema...

Capturing Requirements for Autonomous Spacecraft with Autonomy Requirements Engineering

NASA Astrophysics Data System (ADS)

Vassev, Emil; Hinchey, Mike

2014-08-01

The Autonomy Requirements Engineering (ARE) approach has been developed by Lero - the Irish Software Engineering Research Center within the mandate of a joint project with ESA, the European Space Agency. The approach is intended to help engineers develop missions for unmanned exploration, often with limited or no human control. Such robotics space missions rely on the most recent advances in automation and robotic technologies where autonomy and autonomic computing principles drive the design and implementation of unmanned spacecraft [1]. To tackle the integration and promotion of autonomy in software-intensive systems, ARE combines generic autonomy requirements (GAR) with goal-oriented requirements engineering (GORE). Using this approach, software engineers can determine what autonomic features to develop for a particular system (e.g., a space mission) as well as what artifacts that process might generate (e.g., goals models, requirements specification, etc.). The inputs required by this approach are the mission goals and the domain-specific GAR reflecting specifics of the mission class (e.g., interplanetary missions).

Evaluating Security Controls Based on Key Performance Indicators and Stakeholder Mission

DOE Office of Scientific and Technical Information (OSTI.GOV)

Sheldon, Frederick T; Abercrombie, Robert K; Mili, Ali

2008-01-01

Good security metrics are required to make good decisions about how to design security countermeasures, to choose between alternative security architectures, and to improve security during operations. Therefore, in essence, measurement can be viewed as a decision aid. The lack of sound practical security metrics is severely hampering progress in the development of secure systems. The Cyberspace Security Econometrics System (CSES) offers the following advantages over traditional measurement systems: (1) CSES reflects the variances that exist amongst different stakeholders of the same system. Different stakeholders will typically attach different stakes to the same requirement or service (e.g., a service maymore » be provided by an information technology system or process control system, etc.). (2) For a given stakeholder, CSES reflects the variance that may exist among the stakes she/he attaches to meeting each requirement. The same stakeholder may attach different stakes to satisfying different requirements within the overall system specification. (3) For a given compound specification (e.g., combination(s) of commercial off the shelf software and/or hardware), CSES reflects the variance that may exist amongst the levels of verification and validation (i.e., certification) performed on components of the specification. The certification activity may produce higher levels of assurance across different components of the specification than others. Consequently, this paper introduces the basis, objectives and capabilities for the CSES including inputs/outputs and the basic structural and mathematical underpinnings.« less

Flight Guidance System Requirements Specification

NASA Technical Reports Server (NTRS)

Miller, Steven P.; Tribble, Alan C.; Carlson, Timothy M.; Danielson, Eric J.

2003-01-01

This report describes a requirements specification written in the RSML-e language for the mode logic of a Flight Guidance System of a typical regional jet aircraft. This model was created as one of the first steps in a five-year project sponsored by the NASA Langley Research Center, Rockwell Collins Inc., and the Critical Systems Research Group of the University of Minnesota to develop new methods and tools to improve the safety of avionics designs. This model will be used to demonstrate the application of a variety of methods and techniques, including safety analysis of system and subsystem requirements, verification of key properties using theorem provers and model checkers, identification of potential sources mode confusion in system designs, partitioning of applications based on the criticality of system hazards, and autogeneration of avionics quality code. While this model is representative of the mode logic of a typical regional jet aircraft, it does not describe an actual or planned product. Several aspects of a full Flight Guidance System, such as recovery from failed sensors, have been omitted, and no claims are made regarding the accuracy or completeness of this specification.

Systems, methods and apparatus for implementation of formal specifications derived from informal requirements

NASA Technical Reports Server (NTRS)

Hinchey, Michael G. (Inventor); Rouff, Christopher A. (Inventor); Rash, James L. (Inventor); Erickson, John D. (Inventor); Gracinin, Denis (Inventor)

2010-01-01

Systems, methods and apparatus are provided through which in some embodiments an informal specification is translated without human intervention into a formal specification. In some embodiments the formal specification is a process-based specification. In some embodiments, the formal specification is translated into a high-level computer programming language which is further compiled into a set of executable computer instructions.

Formal specification and mechanical verification of SIFT - A fault-tolerant flight control system

NASA Technical Reports Server (NTRS)

Melliar-Smith, P. M.; Schwartz, R. L.

1982-01-01

The paper describes the methodology being employed to demonstrate rigorously that the SIFT (software-implemented fault-tolerant) computer meets its requirements. The methodology uses a hierarchy of design specifications, expressed in the mathematical domain of multisorted first-order predicate calculus. The most abstract of these, from which almost all details of mechanization have been removed, represents the requirements on the system for reliability and intended functionality. Successive specifications in the hierarchy add design and implementation detail until the PASCAL programs implementing the SIFT executive are reached. A formal proof that a SIFT system in a 'safe' state operates correctly despite the presence of arbitrary faults has been completed all the way from the most abstract specifications to the PASCAL program.

Transitioning from conceptual design to construction performance specification

NASA Astrophysics Data System (ADS)

Jeffers, Paul; Warner, Mark; Craig, Simon; Hubbard, Robert; Marshall, Heather

2012-09-01

On successful completion of a conceptual design review by a funding agency or customer, there is a transition phase before construction contracts can be placed. The nature of this transition phase depends on the Project's approach to construction and the particular subsystem being considered. There are generically two approaches; project retention of design authority and issuance of build to print contracts, or issuance of subsystem performance specifications with controlled interfaces. This paper relates to the latter where a proof of concept (conceptual or reference design) is translated into performance based sub-system specifications for competitive tender. This translation is not a straightforward process and there are a number of different issues to consider in the process. This paper deals with primarily the Telescope mount and Enclosure subsystems. The main subjects considered in this paper are: • Typical status of design at Conceptual Design Review compared with the desired status of Specifications and Interface Control Documents at Request for Quotation. • Options for capture and tracking of system requirements flow down from science / operating requirements and sub-system requirements, and functional requirements derived from reference design. • Requirements that may come specifically from the contracting approach. • Methods for effective use of reference design work without compromising a performance based specification. • Management of project team's expectation relating to design. • Effects on cost estimates from reference design to actual. This paper is based on experience and lessons learned through this process on both the VISTA and the ATST projects.

SU-E-T-785: Using Systems Engineering to Design HDR Skin Treatment Operation for Small Lesions to Enhance Patient Safety

DOE Office of Scientific and Technical Information (OSTI.GOV)

Saw, C; Baikadi, M; Peters, C

2015-06-15

Purpose: Using systems engineering to design HDR skin treatment operation for small lesions using shielded applicators to enhance patient safety. Methods: Systems engineering is an interdisciplinary field that offers formal methodologies to study, design, implement, and manage complex engineering systems as a whole over their life-cycles. The methodologies deal with human work-processes, coordination of different team, optimization, and risk management. The V-model of systems engineering emphasize two streams, the specification and the testing streams. The specification stream consists of user requirements, functional requirements, and design specifications while the testing on installation, operational, and performance specifications. In implementing system engineering tomore » this project, the user and functional requirements are (a) HDR unit parameters be downloaded from the treatment planning system, (b) dwell times and positions be generated by treatment planning system, (c) source decay be computer calculated, (d) a double-check system of treatment parameters to comply with the NRC regulation. These requirements are intended to reduce human intervention to improve patient safety. Results: A formal investigation indicated that the user requirements can be satisfied. The treatment operation consists of using the treatment planning system to generate a pseudo plan that is adjusted for different shielded applicators to compute the dwell times. The dwell positions, channel numbers, and the dwell times are verified by the medical physicist and downloaded into the HDR unit. The decayed source strength is transferred to a spreadsheet that computes the dwell times based on the type of applicators and prescribed dose used. Prior to treatment, the source strength, dwell times, dwell positions, and channel numbers are double-checked by the radiation oncologist. No dosimetric parameters are manually calculated. Conclusion: Systems engineering provides methodologies to effectively design the HDR treatment operation that minimize human intervention and improve patient safety.« less

Gary-Chicago-Milwaukee corridor : corridor transportation information center : system glossary

DOT National Transportation Integrated Search

1995-10-30

The following definitions, abbreviations and acronyms are generated from the : System Definition Document (Document #9931.GCM), the Interface Control : Specification (Document #9932.GCM), and the Requirements Specification (Document : #9933.GCM). The...

An Integrated Systems Approach: A Description of an Automated Circulation Management System.

ERIC Educational Resources Information Center

Seifert, Jan E.; And Others

These bidding specifications describe requirements for a turn-key automated circulation system for the University of Oklahoma Libraries. An integrated systems approach is planned, and requirements are presented for various subsystems: acquisitions, fund accounting, reserve room, and bibliographic and serials control. Also outlined are hardware…

Evaluating Recommender Systems for Technology Enhanced Learning: A Quantitative Survey

ERIC Educational Resources Information Center

Erdt, Mojisola; Fernandez, Alejandro; Rensing, Christoph

2015-01-01

The increasing number of publications on recommender systems for Technology Enhanced Learning (TEL) evidence a growing interest in their development and deployment. In order to support learning, recommender systems for TEL need to consider specific requirements, which differ from the requirements for recommender systems in other domains like…

Autonomous Integrated Receive System (AIRS) requirements definition. Volume 4: Functional specification for the prototype Automated Integrated Receive System (AIRS)

NASA Technical Reports Server (NTRS)

Chie, C. M.

1984-01-01

The functional requirements for the performance, design, and testing for the prototype Automated Integrated Receive System (AIRS) to be demonstrated for the TDRSS S-Band Single Access Return Link are presented.

Approach to developing reliable space reactor power systems

NASA Technical Reports Server (NTRS)

Mondt, Jack F.; Shinbrot, Charles H.

1991-01-01

During Phase II, the Engineering Development Phase, the SP-100 Project has defined and is pursuing a new approach to developing reliable power systems. The approach to developing such a system during the early technology phase is described along with some preliminary examples to help explain the approach. Developing reliable components to meet space reactor power system requirements is based on a top-down systems approach which includes a point design based on a detailed technical specification of a 100-kW power system. The SP-100 system requirements implicitly recognize the challenge of achieving a high system reliability for a ten-year lifetime, while at the same time using technologies that require very significant development efforts. A low-cost method for assessing reliability, based on an understanding of fundamental failure mechanisms and design margins for specific failure mechanisms, is being developed as part of the SP-100 Program.

Characterizing site specific considerations for protecting aircraft during LGS operations at W. M. Keck Observatory

NASA Astrophysics Data System (ADS)

Stomski, Paul J., Jr.; Campbell, Randy; McCann, Kevin; Shimko, Steve

2010-07-01

W. M. Keck Observatory (WMKO) routinely operates laser guide star (LGS) Adaptive Optics (AO) systems at the telescope facility on the Big Island of Hawaii. One of the operational requirements for the LGS system is that a safety system to prevent nearby aircraft from being adversely affected by the laser must be provided. We will support operations in the near term with human aircraft spotters until we can successfully develop and get the appropriate approvals needed for an Automated, Integrated and Reliable System for an Aircraft Friendly Environment (AIRSAFE). This report describes some of the preliminary requirements development work at WMKO in support of the future development of AIRSAFE. We discuss the results of recent work to characterize site specific considerations that impact requirements development. The site specific considerations include the proximity of WMKO laser operations to nearby commercial airports, the implications of military operations in the area and the character of the air traffic volume and flight patterns over the telescope facility. Finally, we discuss how the design and implementation of AIRSAFE will be impacted by these site specific considerations.

NOSS altimeter algorithm specifications

NASA Technical Reports Server (NTRS)

Hancock, D. W.; Forsythe, R. G.; Mcmillan, J. D.

1982-01-01

A description of all algorithms required for altimeter processing is given. Each description includes title, description, inputs/outputs, general algebraic sequences and data volume. All required input/output data files are described and the computer resources required for the entire altimeter processing system were estimated. The majority of the data processing requirements for any radar altimeter of the Seasat-1 type are scoped. Additions and deletions could be made for the specific altimeter products required by other projects.

Airborne Laser Remote Sensor for Oil Detection and Classification : Engineering Requirements and Technical Considerations Relevant to a Performance Specification

DOT National Transportation Integrated Search

1975-08-01

This report outlines the engineering requirements for an Airborne Laser Remote Sensor for Oil Detection and Classification System. Detailed engineering requirements are given for the major units of the system. Technical considerations pertinent to a ...

Thermal Storage Applications Workshop. Volume 2: Contributed Papers

NASA Technical Reports Server (NTRS)

1979-01-01

The solar thermal and the thermal and thermochemical energy storage programs are described as well as the technology requirements for both external (electrical) and internal (thermal, chemical) modes for energy storage in solar power plants. Specific technical issues addressed include thermal storage criteria for solar power plants interfacing with utility systems; optimal dispatch of storage for solar plants in a conventional electric grid; thermal storage/temperature tradeoffs for solar total energy systems; the value of energy storage for direct-replacement solar thermal power plants; systems analysis of storage in specific solar thermal power applications; the value of seasonal storage of solar energy; criteria for selection of the thermal storage system for a 10 MW(2) solar power plant; and the need for specific requirements by storage system development teams.

Exploration of the Trade Space Between Unmanned Aircraft Systems Descent Maneuver Performance and Sense-and-Avoid System Performance Requirements

NASA Technical Reports Server (NTRS)

Jack, Devin P.; Hoffler, Keith D.; Johnson, Sally C.

2014-01-01

A need exists to safely integrate Unmanned Aircraft Systems (UAS) into the United States' National Airspace System. Replacing manned aircraft's see-and-avoid capability in the absence of an onboard pilot is one of the key challenges associated with safe integration. Sense-and-avoid (SAA) systems will have to achieve yet-to-be-determined required separation distances for a wide range of encounters. They will also need to account for the maneuver performance of the UAS they are paired with. The work described in this paper is aimed at developing an understanding of the trade space between UAS maneuver performance and SAA system performance requirements, focusing on a descent avoidance maneuver. An assessment of current manned and unmanned aircraft performance was used to establish potential UAS performance test matrix bounds. Then, near-term UAS integration work was used to narrow down the scope. A simulator was developed with sufficient fidelity to assess SAA system performance requirements. The simulator generates closest-point-of-approach (CPA) data from the wide range of UAS performance models maneuvering against a single intruder with various encounter geometries. Initial attempts to model the results made it clear that developing maneuver performance groups is required. Discussion of the performance groups developed and how to know in which group an aircraft belongs for a given flight condition and encounter is included. The groups are airplane, flight condition, and encounter specific, rather than airplane-only specific. Results and methodology for developing UAS maneuver performance requirements are presented for a descent avoidance maneuver. Results for the descent maneuver indicate that a minimum specific excess power magnitude can assure a minimum CPA for a given time-to-go prediction. However, smaller amounts of specific excess power may achieve or exceed the same CPA if the UAS has sufficient speed to trade for altitude. The results of this study will support UAS maneuver performance requirements development for integrating UAS in the NAS. The methods described are being used to help RTCA Special Committee 228 develop requirements.

Civilian Radioactive Waste Management System Requirements Document

DOE Office of Scientific and Technical Information (OSTI.GOV)

C.A. Kouts

2006-05-10

The CRD addresses the requirements of Department of Energy (DOE) Order 413.3-Change 1, ''Program and Project Management for the Acquisition of Capital Assets'', by providing the Secretarial Acquisition Executive (Level 0) scope baseline and the Program-level (Level 1) technical baseline. The Secretarial Acquisition Executive approves the Office of Civilian Radioactive Waste Management's (OCRWM) critical decisions and changes against the Level 0 baseline; and in turn, the OCRWM Director approves all changes against the Level 1 baseline. This baseline establishes the top-level technical scope of the CRMWS and its three system elements, as described in section 1.3.2. The organizations responsible formore » design, development, and operation of system elements described in this document must therefore prepare subordinate project-level documents that are consistent with the CRD. Changes to requirements will be managed in accordance with established change and configuration control procedures. The CRD establishes requirements for the design, development, and operation of the CRWMS. It specifically addresses the top-level governing laws and regulations (e.g., ''Nuclear Waste Policy Act'' (NWPA), 10 Code of Federal Regulations (CFR) Part 63, 10 CFR Part 71, etc.) along with specific policy, performance requirements, interface requirements, and system architecture. The CRD shall be used as a vehicle to incorporate specific changes in technical scope or performance requirements that may have significant program implications. Such may include changes to the program mission, changes to operational capability, and high visibility stakeholder issues. The CRD uses a systems approach to: (1) identify key functions that the CRWMS must perform, (2) allocate top-level requirements derived from statutory, regulatory, and programmatic sources, and (3) define the basic elements of the system architecture and operational concept. Project-level documents address CRD requirements by further defining system element functions, decomposing requirements into significantly greater detail, and developing designs of system components, facilities, and equipment. The CRD addresses the identification and control of functional, physical, and operational boundaries between and within CRWMS elements. The CRD establishes requirements regarding key interfaces between the CRWMS and elements external to the CRWMS. Project elements define interfaces between CRWMS program elements. The Program has developed a change management process consistent with DOE Order 413.3-Change 1. Changes to the Secretarial Acquisition Executive and Program-level baselines must be approved by a Program Baseline Change Control Board. Specific thresholds have been established for identifying technical, cost, and schedule changes that require approval. The CRWMS continually evaluates system design and operational concepts to optimize performance and/or cost. The Program has developed systems analysis tools to assess potential enhancements to the physical system and to determine the impacts from cost saving initiatives, scientific and technological improvements, and engineering developments. The results of systems analyses, if appropriate, are factored into revisions to the CRD as revised Programmatic Requirements.« less

Software Requirements Engineering Methodology

DTIC Science & Technology

1976-09-01

common speech, so that the specification can be read by managers, systems enginetrs, and others who are not specially trained in the language. To...of the system and its DPS. They are usually implicit in the wording of the originating specifications, although the new SREM user must train ...to the name of the ENTITYjCLASS, the operation is applicable only to a single instance. This concentration of the requirements for creation and

Establishment of a tissue-specific RNAi system in C. elegans.

PubMed

Qadota, Hiroshi; Inoue, Makiko; Hikita, Takao; Köppen, Mathias; Hardin, Jeffrey D; Amano, Mutsuki; Moerman, Donald G; Kaibuchi, Kozo

2007-10-01

In C. elegans, mosaic analysis is a powerful genetic tool for determining in which tissue or specific cells a gene of interest is required. For traditional mosaic analysis, a loss-of-function mutant and a genomic fragment that can rescue the mutant phenotype are required. Here we establish an easy and rapid mosaic system using RNAi (RNA mediated interference), using a rde-1 mutant that is resistant to RNAi. Tissue-specific expression of the wild type rde-1 cDNA in rde-1 mutants limits RNAi sensitivity to a specific tissue. We established hypodermal-and muscle-specific RNAi systems by expressing rde-1 cDNA under the control of the lin-26 and hlh-1 promoters, respectively. We confirmed tissue-specific RNAi using two assays: (1) tissue-specific knockdown of GFP expression, and (2) phenocopy of mutations in essential genes that were previously known to function in a tissue-specific manner. We also applied this system to an essential gene, ajm-1, expressed in hypodermis and gut, and show that lethality in ajm-1 mutants is due to loss of expression in hypodermal cells. Although we demonstrate tissue-specific RNAi in hypodermis and muscle, this method could be easily applied to other tissues.

Establishment of a tissue-specific RNAi system in C. elegans

PubMed Central

Qadota, Hiroshi; Inoue, Makiko; Hikita, Takao; Köppen, Mathias; Hardin, Jeffrey D.; Amano, Mutsuki; Moerman, Donald G.; Kaibuchi, Kozo

2011-01-01

In C. elegans, mosaic analysis is a powerful genetic tool for determining in which tissue or specific cells a gene of interest is required. For traditional mosaic analysis, a loss-of-function mutant and a genomic fragment that can rescue the mutant phenotype are required. Here we establish an easy and rapid mosaic system using RNAi (RNA mediated interference), using a rde-1 mutant that is resistant to RNAi. Tissue-specific expression of the wild type rde-1 cDNA in rde-1 mutants limits RNAi sensitivity to a specific tissue. We established hypodermal- and muscle-specific RNAi systems by expressing rde-1 cDNA under the control of the lin-26 and hlh-1 promoters, respectively. We confirmed tissue-specific RNAi using two assays: (1) tissue-specific knockdown of GFP expression, and (2) phenocopy of mutations in essential genes that were previously known to function in a tissue-specific manner. We also applied this system to an essential gene, ajm-1, expressed in hypodermis and gut, and show that lethality in ajm-1 mutants is due to loss of expression in hypodermal cells. Although we demonstrate tissue-specific RNAi in hypodermis and muscle, this method could be easily applied to other tissues. PMID:17681718

Support requirements for remote sensor systems on unmanned planetary missions, phase 3

NASA Technical Reports Server (NTRS)

1971-01-01

The results of a study to determine the support requirements for remote sensor systems on unmanned planetary flyby and orbiter missions are presented. Sensors and experiment groupings for selected missions are also established. Computer programs were developed to relate measurement requirements to support requirements. Support requirements were determined for sensors capable of performing required measurements at various points along the trajectories of specific selected missions.

Integrated mass transportation system study/definition/implementation program definition

NASA Technical Reports Server (NTRS)

Ransone, R. K.; Deptula, D. A.; Yorke, G. G.

1975-01-01

Specific actions needed to plan and effect transportation system improvements are identified within the constraints of limited financial, energy and land use resources, and diverse community requirements. A specific program is described which would develop the necessary generalized methodology for devising improved transportation systems and evaluate them against specific criteria for intermodal and intramodal optimization. A consistent, generalized method is provided for study and evaluation of transportation system improvements.

Saint Lawrence Seaway Navigation-Aid System Study : Volume I - Text and Appendixes A and D

DOT National Transportation Integrated Search

1978-09-01

The requirements for a navigation guidance system which will effect an increase in the ship processing capacity of the Saint Lawrence Seaway (Lake Ontario to Montreal, Quebec) are developed. The requirements include a specification of system position...

Performance prediction evaluation of ceramic materials in point-focusing solar receivers

NASA Technical Reports Server (NTRS)

Ewing, J.; Zwissler, J.

1979-01-01

A performance prediction was adapted to evaluate the use of ceramic materials in solar receivers for point focusing distributed applications. System requirements were determined including the receiver operating environment and system operating parameters for various engine types. Preliminary receiver designs were evolved from these system requirements. Specific receiver designs were then evaluated to determine material functional requirements.

AMTD: Update of Engineering Specifications Derived from Science Requirements for Future UVOIR Space Telescopes

NASA Technical Reports Server (NTRS)

Stahl, H. Philip

2014-01-01

AMTD is using a Science Driven Systems Engineering approach to develop Engineering Specifications based on Science Measurement Requirements and Implementation Constraints. Science requirements meet the needs of both Exoplanet and General Astrophysics science. Engineering Specifications are guiding our effort to mature to TRL-6 the critical technologies needed to produce 4-m or larger flight-qualified UVOIR mirrors by 2018 so that a viable mission can be considered by the 2020 Decadal Review.

Crewed Space Vehicle Battery Safety Requirements

NASA Technical Reports Server (NTRS)

Jeevarajan, Judith A.; Darcy, Eric C.

2014-01-01

This requirements document is applicable to all batteries on crewed spacecraft, including vehicle, payload, and crew equipment batteries. It defines the specific provisions required to design a battery that is safe for ground personnel and crew members to handle and/or operate during all applicable phases of crewed missions, safe for use in the enclosed environment of a crewed space vehicle, and safe for use in launch vehicles, as well as in unpressurized spaces adjacent to the habitable portion of a space vehicle. The required provisions encompass hazard controls, design evaluation, and verification. The extent of the hazard controls and verification required depends on the applicability and credibility of the hazard to the specific battery design and applicable missions under review. Evaluation of the design and verification program results shall be completed prior to certification for flight and ground operations. This requirements document is geared toward the designers of battery systems to be used in crewed vehicles, crew equipment, crew suits, or batteries to be used in crewed vehicle systems and payloads (or experiments). This requirements document also applies to ground handling and testing of flight batteries. Specific design and verification requirements for a battery are dependent upon the battery chemistry, capacity, complexity, charging, environment, and application. The variety of battery chemistries available, combined with the variety of battery-powered applications, results in each battery application having specific, unique requirements pertinent to the specific battery application. However, there are basic requirements for all battery designs and applications, which are listed in section 4. Section 5 includes a description of hazards and controls and also includes requirements.

Space power development impact on technology requirements

NASA Technical Reports Server (NTRS)

Cassidy, J. F.; Fitzgerald, T. J.; Gilje, R. I.; Gordon, J. D.

1986-01-01

The paper is concerned with the selection of a specific spacecraft power technology and the identification of technology development to meet system requirements. Requirements which influence the selection of a given technology include the power level required, whether the load is constant or transient in nature, and in the case of transient loads, the time required to recover the power, and overall system safety. Various power technologies, such as solar voltaic power, solar dynamic power, nuclear power systems, and electrochemical energy storage, are briefly described.

Manned orbital systems concepts study. Book 2: Requirements for extended-duration missions

NASA Technical Reports Server (NTRS)

1975-01-01

In order to provide essential data needed in long-range program planning, the Manned Orbital Systems Concepts (MOSC) study attempted to define, evaluate, and compare concepts for manned orbital systems that provide extended experiment mission capabilities in space, flexibility of operation, and growth potential. Specific areas discussed include roles and requirements for man in future space missions, requirements for extended capability, mission/payload concepts, and preliminary design and operational requirements.

Space station integrated propulsion and fluid system study: Fluid systems configuration databook

NASA Technical Reports Server (NTRS)

Rose, L.; Bicknell, B.; Bergman, D.; Wilson, S.

1987-01-01

This databook contains fluid system requirements and system descriptions for Space Station program elements including the United States and International modules, integrated fluid systems, attached payloads, fluid servicers and vehicle accommodation facilities. Separate sections are devoted to each of the program elements and include a discussion of the overall system requirements, specific fluid systems requirements and systems descriptions. The systems descriptions contain configurations, fluid inventory data and component lists. In addition, a list of information sources is referenced at the end of each section.

An Approach for Implementation of Project Management Information Systems

NASA Astrophysics Data System (ADS)

Běrziša, Solvita; Grabis, Jānis

Project management is governed by project management methodologies, standards, and other regulatory requirements. This chapter proposes an approach for implementing and configuring project management information systems according to requirements defined by these methodologies. The approach uses a project management specification framework to describe project management methodologies in a standardized manner. This specification is used to automatically configure the project management information system by applying appropriate transformation mechanisms. Development of the standardized framework is based on analysis of typical project management concepts and process and existing XML-based representations of project management. A demonstration example of project management information system's configuration is provided.

Requirements Flowdown for Prognostics and Health Management

NASA Technical Reports Server (NTRS)

Goebel, Kai; Saxena, Abhinav; Roychoudhury, Indranil; Celaya, Jose R.; Saha, Bhaskar; Saha, Sankalita

2012-01-01

Prognostics and Health Management (PHM) principles have considerable promise to change the game of lifecycle cost of engineering systems at high safety levels by providing a reliable estimate of future system states. This estimate is a key for planning and decision making in an operational setting. While technology solutions have made considerable advances, the tie-in into the systems engineering process is lagging behind, which delays fielding of PHM-enabled systems. The derivation of specifications from high level requirements for algorithm performance to ensure quality predictions is not well developed. From an engineering perspective some key parameters driving the requirements for prognostics performance include: (1) maximum allowable Probability of Failure (PoF) of the prognostic system to bound the risk of losing an asset, (2) tolerable limits on proactive maintenance to minimize missed opportunity of asset usage, (3) lead time to specify the amount of advanced warning needed for actionable decisions, and (4) required confidence to specify when prognosis is sufficiently good to be used. This paper takes a systems engineering view towards the requirements specification process and presents a method for the flowdown process. A case study based on an electric Unmanned Aerial Vehicle (e-UAV) scenario demonstrates how top level requirements for performance, cost, and safety flow down to the health management level and specify quantitative requirements for prognostic algorithm performance.

Surface cleanliness of fluid systems, specification for

NASA Technical Reports Server (NTRS)

1995-01-01

This specification establishes surface cleanliness levels, test methods, cleaning and packaging requirements, and protection and inspection procedures for determining surface cleanliness. These surfaces pertain to aerospace parts, components, assemblies, subsystems, and systems in contact with any fluid medium.

The OMG Modelling Language (SYSML)

NASA Astrophysics Data System (ADS)

Hause, M.

2007-08-01

On July 6th 2006, the Object Management Group (OMG) announced the adoption of the OMG Systems Modeling Language (OMG SysML). The SysML specification was in response to the joint Request for Proposal issued by the OMG and INCOSE (the International Council on Systems Engineering) for a customized version of UML 2, designed to address the specific needs of system engineers. SysML is a visual modeling language that extends UML 2 in order to support the specification, analysis, design, verification and validation of complex systems. This paper will look at the background of SysML and summarize the SysML specification including the modifications to UML 2.0, along with the new requirement and parametric diagrams. It will also show how SysML artifacts can be used to specify the requirements for other solution spaces such as software and hardware to provide handover to other disciplines.

46 CFR 71.65-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

... dioxide, foam, and sprinkling systems. (7) Supervised Patrol Route. (e) Marine engineering. (1) For plans required for marine engineering equipment and systems, see subchapter F (Marine Engineering) of this... equipment and systems, see subchapter J (Electrical Engineering) of this chapter. (2) [Reserved] (g...

Shuttle mission simulator requirement report, volume 2, revision A

NASA Technical Reports Server (NTRS)

Burke, J. F.

1973-01-01

The training requirements of all mission phases for crews and ground support personnel are presented. The specifications are given for the design and development of the simulator, data processing systems, engine control, software, and systems integration.

Saguaro Power Plant Solar Repowering Project. Volume II. System requirements specification. Final technical report, September 1979-July 1980

DOE Office of Scientific and Technical Information (OSTI.GOV)

Weber, E.R.

1980-07-01

This specification defines the system and subsystem characteristics, design requirements, and system environmental requirements for the Saguaro Power Plant Solar Repowering Project. This project involves the solar repowering of all (120.2 MWe gross) of the 115 MWe net power No. One steam-Rankine unit of the Arizona Public Service Company's Saguaro station. The receiver heat transport fluid is draw salt (60% sodium nitrate and 40% potassium nitrate) that is also used to provide 3.8 hours of sensible heat thermal energy storage. The quad-cavity type receiver is mounted on a tower within a single surrounding collector field of 10,500 second generation heliostats.

Prefocal station mechanical design concept study for the E-ELT

NASA Astrophysics Data System (ADS)

Jolley, Paul; Brunetto, Enzo; Frank, Christoph; Lewis, Steffan; Marchetti, Enrico

2016-07-01

The Nasmyth platforms of the E-ELT will contain one Prefocal Station (PFS) each. The main PFS functional requirements are to provide a focal plane to the three Nasmyth focal stations and the Coudé focus, optical sensing supporting telescope low order optimisation and seeing limited image quality, and optical sensing supporting characterising and phasing of M1 and other telescope subsystems. The PFS user requirements are used to derive the PFS technical requirements specification that will form the basis for design, development and production of the system. This specification process includes high-level architectural decisions and technical performance budget allocations. The mechanical design concepts reported here have been developed in order to validate key system specifications and associated technical budgets.

Space station MSFC-DPD-235/DR no. MA-05 phase C/D program development plan. Volume 2: Phase C/D, programmatic requirements

NASA Technical Reports Server (NTRS)

1971-01-01

The design plan requirements define the design implementation and control requirements for Phase C/D of the Modular Space Station Project and specifically address the Initial Space Station phase of the Space Station Program (modular). It is based primarily on the specific objective of translating the requirements of the Space Station Program, Project, Interface, and Support Requirements and preliminary contract end x item specifications into detail design of the operational systems which comprise the initial space station. This document is designed to guide aerospace contractors in the planning and bidding for Phase C/D.

40 CFR 63.11552 - What are my monitoring requirements?

Code of Federal Regulations, 2010 CFR

2010-07-01

..., operate, and maintain a bag leak detection system for each fabric filter according to the requirements in..., operate, and maintain a bag leak detection system for each fabric filter according to paragraphs (c)(1) through (4) of this section. (1) Each bag leak detection system must meet the specifications and...

Saint Lawrence Seaway Navigation-Aid System Study : Volume II - Appendix B - User's Manual and Documentation of Seaway Capacity and Capacity Analysis Programs

DOT National Transportation Integrated Search

1978-09-01

The requirements for a navigation guidance system which will effect an increase in the ship processing capacity of the Saint Lawrence Seaway (Lake Ontario to Montreal, Quebec) are developed. The requirements include a specification of system position...

Software Requirements

DTIC Science & Technology

1990-01-01

Real-Time Systems Specifications 11 Convenient Auto Rental System Marea82 12 Systems Architecture Marca , D. A., and C. L. McGowan. "Static and...Requirements Marca88 Structured Analysis. Orr’s work is worthy of study Marca , D. A., and C. L. McGowan. SADT: Struc- by the instructor, since it enjoys

Urine sampling and collection system

NASA Technical Reports Server (NTRS)

Fogal, G. L.; Mangialardi, J. K.; Reinhardt, C. G.

1971-01-01

This specification defines the performance and design requirements for the urine sampling and collection system engineering model and establishes requirements for its design, development, and test. The model shall provide conceptual verification of a system applicable to manned space flight which will automatically provide for collection, volume sensing, and sampling of urine.

46 CFR 91.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

... systems. (e) Marine engineering. For plans required for marine engineering equipment and systems, see... electrical engineering, equipment and systems, see subchapter J (Electrical Engineering) of this chapter. (g... bottoms, etc., and including inboard and outboard profile. (b) Hull structure. 1 (1) *Inner Bottom Plating...

40 CFR Appendix E to Part 52 - Performance Specifications and, Specification Test Procedures for Monitoring Systems for Effluent...

Code of Federal Regulations, 2011 CFR

2011-07-01

..., Specification Test Procedures for Monitoring Systems for Effluent Stream Gas Volumetric Flow Rate E Appendix E... Stream Gas Volumetric Flow Rate 1. Principle and applicability. 1.1Principle. Effluent stream gas... method is applicable to subparts which require continuous gas volumetric flow rate measurement...

40 CFR Appendix E to Part 52 - Performance Specifications and, Specification Test Procedures for Monitoring Systems for Effluent...

Code of Federal Regulations, 2010 CFR

2010-07-01

..., Specification Test Procedures for Monitoring Systems for Effluent Stream Gas Volumetric Flow Rate E Appendix E... Stream Gas Volumetric Flow Rate 1. Principle and applicability. 1.1Principle. Effluent stream gas... method is applicable to subparts which require continuous gas volumetric flow rate measurement...

7 CFR 3550.57 - Dwelling requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... amount required to address the specific need. (b) New dwellings. Construction must meet the requirements..., heating, plumbing, water, and wastewater disposal systems; and be free of termites and other wood damaging...

Exploration Planetary Surface Structural Systems: Design Requirements and Compliance

NASA Technical Reports Server (NTRS)

Dorsey, John T.

2011-01-01

The Lunar Surface Systems Project developed system concepts that would be necessary to establish and maintain a permanent human presence on the Lunar surface. A variety of specific system implementations were generated as a part of the scenarios, some level of system definition was completed, and masses estimated for each system. Because the architecture studies generally spawned a large number of system concepts and the studies were executed in a short amount of time, the resulting system definitions had very low design fidelity. This paper describes the development sequence required to field a particular structural system: 1) Define Requirements, 2) Develop the Design and 3) Demonstrate Compliance of the Design to all Requirements. This paper also outlines and describes in detail the information and data that are required to establish structural design requirements and outlines the information that would comprise a planetary surface system Structures Requirements document.

Expert Recommender: Designing for a Network Organization

NASA Astrophysics Data System (ADS)

Reichling, Tim; Veith, Michael; Wulf, Volker

Recent knowledge management initiatives focus on expertise sharing within formal organizational units and informal communities of practice. Expert recommender systems seem to be a promising tool in support of these initiatives. This paper presents experiences in designing an expert recommender system for a knowledge- intensive organization, namely the National Industry Association (NIA). Field study results provide a set of specific design requirements. Based on these requirements, we have designed an expert recommender system which is integrated into the specific software infrastructure of the organizational setting. The organizational setting is, as we will show, specific for historical, political, and economic reasons. These particularities influence the employees’ organizational and (inter-)personal needs within this setting. The paper connects empirical findings of a long-term case study with design experiences of an expertise recommender system.

Automated personnel data base system specifications, Task V. Final report

DOE Office of Scientific and Technical Information (OSTI.GOV)

Bartley, H.J.; Bocast, A.K.; Deppner, F.O.

1978-09-01

This document is the General Research Corporation report on Task V of a study for the Office of Inspection and Enforcement of the Nuclear Regulatory Commission (NRC/IE). The full title of this study is ''Development of Qualification Requirements, Training Programs, Career Plans, and Methodologies for Effective Management and Training of Inspection and Enforcement Personnel.'' Task V required the development of an automated personnel data base system for NRC/IE. This system is identified as the NRC/IE Personnel, Assignment, Qualifications, and Training System (PAQTS). This Task V report provides the documentation for PAQTS including the Functional Requirements Document (FRD), the Data Requirementsmore » Document (DRD), the Hardware and Software Capabilities Assessment, and the Detailed Implementation Schedule. Specific recommendations to facilitate implementation of PAQTS are also included.« less

Information management system study results. Volume 2: IMS study results appendixes

NASA Technical Reports Server (NTRS)

1971-01-01

Computer systems program specifications are presented for the modular space station information management system. These are the computer program contract end item, data bus system, data bus breadboard, and display interface adapter specifications. The performance, design, tests, and qualification requirements are established for the implementation of the information management system. For Vol. 1, see N72-19972.

Expendable Second Stage Reusable Space Shuttle Booster. Volume 9; Preliminary System Specification

NASA Technical Reports Server (NTRS)

1971-01-01

The specification for establishing the requirements for the system performance, design, development, and ground and flight operations of the expendable second stage on a reusable space shuttle booster system is presented. The basic specification is that the system shall be capable of placing payloads in excess of 100,000 pounds into earth orbit. In addition, the expendable second stage provides a multimission, economical, large capability system suitable for a variety of space missions in the 1980 time period.

Crew interface specifications preparation for in-flight maintenance and stowage functions

NASA Technical Reports Server (NTRS)

Parker, F. W.; Carlton, B. E.

1972-01-01

The findings and data products developed during the Phase 2 crew interface specification study are presented. Five new NASA general specifications were prepared: operations location coding system for crew interfaces; loose equipment and stowage management requirements; loose equipment and stowage data base information requirements; spacecraft loose equipment stowage drawing requirements; and inflight stowage management data requirements. Additional data was developed defining inflight maintenance processes and related data concepts for inflight troubleshooting, remove/repair/replace and scheduled maintenance activities. The process of maintenance task and equipment definition during spacecraft design and development was also defined and related data concepts were identified for futher development into formal NASA specifications during future follow-on study phases of the contract.

Engineering Design of ITER Prototype Fast Plant System Controller

NASA Astrophysics Data System (ADS)

Goncalves, B.; Sousa, J.; Carvalho, B.; Rodrigues, A. P.; Correia, M.; Batista, A.; Vega, J.; Ruiz, M.; Lopez, J. M.; Rojo, R. Castro; Wallander, A.; Utzel, N.; Neto, A.; Alves, D.; Valcarcel, D.

2011-08-01

The ITER control, data access and communication (CODAC) design team identified the need for two types of plant systems. A slow control plant system is based on industrial automation technology with maximum sampling rates below 100 Hz, and a fast control plant system is based on embedded technology with higher sampling rates and more stringent real-time requirements than that required for slow controllers. The latter is applicable to diagnostics and plant systems in closed-control loops whose cycle times are below 1 ms. Fast controllers will be dedicated industrial controllers with the ability to supervise other fast and/or slow controllers, interface to actuators and sensors and, if necessary, high performance networks. Two prototypes of a fast plant system controller specialized for data acquisition and constrained by ITER technological choices are being built using two different form factors. This prototyping activity contributes to the Plant Control Design Handbook effort of standardization, specifically regarding fast controller characteristics. Envisaging a general purpose fast controller design, diagnostic use cases with specific requirements were analyzed and will be presented along with the interface with CODAC and sensors. The requirements and constraints that real-time plasma control imposes on the design were also taken into consideration. Functional specifications and technology neutral architecture, together with its implications on the engineering design, were considered. The detailed engineering design compliant with ITER standards was performed and will be discussed in detail. Emphasis will be given to the integration of the controller in the standard CODAC environment. Requirements for the EPICS IOC providing the interface to the outside world, the prototype decisions on form factor, real-time operating system, and high-performance networks will also be discussed, as well as the requirements for data streaming to CODAC for visualization and archiving.

Study of multiple cycles valves

NASA Technical Reports Server (NTRS)

Wichmann, H.

1973-01-01

A discussion is presented regarding valves which can be cycled repeatedly and are available from industry for application in the inlet system for the Pioneer Venus Probe mass spectrometer. Both solenoid type and latching type valves are considered. The study is divided into two principal areas: (1) preparation of a valve specification reflecting the requirements of the inlet system cyclic valves for the Pioneer Venus Probe mass spectrometer and the submittal of this specification to potential valve suppliers for their response and proposal; (2) preparation of a design layout of an optimum cyclic valve meeting all of the valve specification requirements.

46 CFR 62.35-40 - Fuel systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Fuel systems. 62.35-40 Section 62.35-40 Shipping COAST... Requirements for Specific Types of Automated Vital Systems § 62.35-40 Fuel systems. (a) Level alarms. Where high or low fuel tank level alarms are required, they must be located to allow the operator adequate...

46 CFR 62.35-40 - Fuel systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 2 2013-10-01 2013-10-01 false Fuel systems. 62.35-40 Section 62.35-40 Shipping COAST... Requirements for Specific Types of Automated Vital Systems § 62.35-40 Fuel systems. (a) Level alarms. Where high or low fuel tank level alarms are required, they must be located to allow the operator adequate...

46 CFR 62.35-40 - Fuel systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 2 2012-10-01 2012-10-01 false Fuel systems. 62.35-40 Section 62.35-40 Shipping COAST... Requirements for Specific Types of Automated Vital Systems § 62.35-40 Fuel systems. (a) Level alarms. Where high or low fuel tank level alarms are required, they must be located to allow the operator adequate...

46 CFR 62.35-40 - Fuel systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 2 2014-10-01 2014-10-01 false Fuel systems. 62.35-40 Section 62.35-40 Shipping COAST... Requirements for Specific Types of Automated Vital Systems § 62.35-40 Fuel systems. (a) Level alarms. Where high or low fuel tank level alarms are required, they must be located to allow the operator adequate...

PDSS/IMC requirements and functional specifications

NASA Technical Reports Server (NTRS)

1983-01-01

The system (software and hardware) requirements for the Payload Development Support System (PDSS)/Image Motion Compensator (IMC) are provided. The PDSS/IMC system provides the capability for performing Image Motion Compensator Electronics (IMCE) flight software test, checkout, and verification and provides the capability for monitoring the IMC flight computer system during qualification testing for fault detection and fault isolation.

Building Safer Systems With SpecTRM

NASA Technical Reports Server (NTRS)

2003-01-01

System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.

An airline study of advanced technology requirements for advanced high speed commercial engines. 3: Propulsion system requirements

NASA Technical Reports Server (NTRS)

Sallee, G. P.

1973-01-01

The advanced technology requirements for an advanced high speed commercial transport engine are presented. The results of the phase 3 effort cover the requirements and objectives for future aircraft propulsion systems. These requirements reflect the results of the Task 1 and 2 efforts and serve as a baseline for future evaluations, specification development efforts, contract/purchase agreements, and operational plans for future subsonic commercial engines. This report is divided into five major sections: (1) management objectives for commercial propulsion systems, (2) performance requirements for commercial transport propulsion systems, (3) design criteria for future transport engines, (4) design requirements for powerplant packages, and (5) testing.

GATOR: Requirements capturing of telephony features

NASA Technical Reports Server (NTRS)

Dankel, Douglas D., II; Walker, Wayne; Schmalz, Mark

1992-01-01

We are developing a natural language-based, requirements gathering system called GATOR (for the GATherer Of Requirements). GATOR assists in the development of more accurate and complete specifications of new telephony features. GATOR interacts with a feature designer who describes a new feature, set of features, or capability to be implemented. The system aids this individual in the specification process by asking for clarifications when potential ambiguities are present, by identifying potential conflicts with other existing features, and by presenting its understanding of the feature to the designer. Through user interaction with a model of the existing telephony feature set, GATOR constructs a formal representation of the new, 'to be implemented' feature. Ultimately GATOR will produce a requirements document and will maintain an internal representation of this feature to aid in future design and specification. This paper consists of three sections that describe (1) the structure of GATOR, (2) POND, GATOR's internal knowledge representation language, and (3) current research issues.

48 CFR 8.712 - Specification changes.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 1 2011-10-01 2011-10-01 false Specification changes. 8.712 Section 8.712 Federal Acquisition Regulations System FEDERAL ACQUISITION REGULATION ACQUISITION PLANNING REQUIRED SOURCES OF SUPPLIES AND SERVICES Acquisition From Nonprofit Agencies Employing People Who...

30 CFR 74.9 - Quality assurance.

Code of Federal Regulations, 2011 CFR

2011-07-01

... specifications and are reliable, safe, effective, and otherwise suitable for their intended use. To establish and... registration under ISO Q9001-2000, American National Standard, Quality Management Systems-Requirements... ISO Q9001-2000, American National Standard, Quality Management Systems-Requirements. The Director of...

CAD/CAM data management needs, requirements and options

NASA Technical Reports Server (NTRS)

Lopatka, R. S.; Johnson, T. G.

1978-01-01

The requirements for a data management system in support of technical or scientific applications and possible courses of action were reviewed. Specific requirements were evolved while working towards higher level integration impacting all phases of the current design process and through examination of commercially marketed systems and related data base research. Arguments are proposed for varied approaches in implementing data base systems ranging from no action necessary to immediate procurement of an existing data base management system.

NASIS data base management system - IBM 360/370 OS MVT implementation. 3: Data set specifications

NASA Technical Reports Server (NTRS)

1973-01-01

The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular set is prepared in a standard form and centralized in a single document. The format for the data set is provided.

NASIS data base management system: IBM 360 TSS implementation. Volume 3: Data set specifications

NASA Technical Reports Server (NTRS)

1973-01-01

The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular data set is prepared in a standard form and centralized in a single document. The format for the data set is provided.

Automated Derivation of Complex System Constraints from User Requirements

NASA Technical Reports Server (NTRS)

Muery, Kim; Foshee, Mark; Marsh, Angela

2006-01-01

International Space Station (ISS) payload developers submit their payload science requirements for the development of on-board execution timelines. The ISS systems required to execute the payload science operations must be represented as constraints for the execution timeline. Payload developers use a software application, User Requirements Collection (URC), to submit their requirements by selecting a simplified representation of ISS system constraints. To fully represent the complex ISS systems, the constraints require a level of detail that is beyond the insight of the payload developer. To provide the complex representation of the ISS system constraints, HOSC operations personnel, specifically the Payload Activity Requirements Coordinators (PARC), manually translate the payload developers simplified constraints into detailed ISS system constraints used for scheduling the payload activities in the Consolidated Planning System (CPS). This paper describes the implementation for a software application, User Requirements Integration (URI), developed to automate the manual ISS constraint translation process.

Systems engineering principles for the design of biomedical signal processing systems.

PubMed

Faust, Oliver; Acharya U, Rajendra; Sputh, Bernhard H C; Min, Lim Choo

2011-06-01

Systems engineering aims to produce reliable systems which function according to specification. In this paper we follow a systems engineering approach to design a biomedical signal processing system. We discuss requirements capturing, specification definition, implementation and testing of a classification system. These steps are executed as formal as possible. The requirements, which motivate the system design, are based on diabetes research. The main requirement for the classification system is to be a reliable component of a machine which controls diabetes. Reliability is very important, because uncontrolled diabetes may lead to hyperglycaemia (raised blood sugar) and over a period of time may cause serious damage to many of the body systems, especially the nerves and blood vessels. In a second step, these requirements are refined into a formal CSP‖ B model. The formal model expresses the system functionality in a clear and semantically strong way. Subsequently, the proven system model was translated into an implementation. This implementation was tested with use cases and failure cases. Formal modeling and automated model checking gave us deep insight in the system functionality. This insight enabled us to create a reliable and trustworthy implementation. With extensive tests we established trust in the reliability of the implementation. Copyright © 2010 Elsevier Ireland Ltd. All rights reserved.

NTP comparison process

NASA Technical Reports Server (NTRS)

Corban, Robert

1993-01-01

The systems engineering process for the concept definition phase of the program involves requirements definition, system definition, and consistent concept definition. The requirements definition process involves obtaining a complete understanding of the system requirements based on customer needs, mission scenarios, and nuclear thermal propulsion (NTP) operating characteristics. A system functional analysis is performed to provide a comprehensive traceability and verification of top-level requirements down to detailed system specifications and provides significant insight into the measures of system effectiveness to be utilized in system evaluation. The second key element in the process is the definition of system concepts to meet the requirements. This part of the process involves engine system and reactor contractor teams to develop alternative NTP system concepts that can be evaluated against specific attributes, as well as a reference configuration against which to compare system benefits and merits. Quality function deployment (QFD), as an excellent tool within Total Quality Management (TQM) techniques, can provide the required structure and provide a link to the voice of the customer in establishing critical system qualities and their relationships. The third element of the process is the consistent performance comparison. The comparison process involves validating developed concept data and quantifying system merits through analysis, computer modeling, simulation, and rapid prototyping of the proposed high risk NTP subsystems. The maximum amount possible of quantitative data will be developed and/or validated to be utilized in the QFD evaluation matrix. If upon evaluation of a new concept or its associated subsystems determine to have substantial merit, those features will be incorporated into the reference configuration for subsequent system definition and comparison efforts.

Mechanical Design and Optimization of Swarm-Capable UAV Launch Systems

DTIC Science & Technology

2015-06-01

stakeholders. The end result was the successful development and demonstration of a launching system prototype specifically developed to rapidly launch a...requirements for the stakeholders. The end result was the successful development and demonstration of a launching system prototype specifically developed to... Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 7 Conclusion 125 7.1 Summary of Findings

NASA TSRV essential flight control system requirements via object oriented analysis

NASA Technical Reports Server (NTRS)

Duffy, Keith S.; Hoza, Bradley J.

1992-01-01

The objective was to analyze the baseline flight control system of the Transport Systems Research Vehicle (TSRV) and to develop a system specification that offers high visibility of the essential system requirements in order to facilitate the future development of alternate, more advanced software architectures. The flight control system is defined to be the baseline software for the TSRV research flight deck, including all navigation, guidance, and control functions, and primary pilot displays. The Object Oriented Analysis (OOA) methodology developed is used to develop a system requirement definition. The scope of the requirements definition contained herein is limited to a portion of the Flight Management/Flight Control computer functionality. The development of a partial system requirements definition is documented, and includes a discussion of the tasks required to increase the scope of the requirements definition and recommendations for follow-on research.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Arion is a library and tool set that enables researchers to holistically define test system models. To define a complex system for testing an algorithm or control requires expertise across multiple domains. Simulating a complex system requires the integration of multiple simulators and test hardware, each with their own specification languages and concepts. This requires extensive set of knowledge and capabilities. Arion was developed to alleviate this challenge. Arion is a library of Java libraries that abstracts the concepts from supported simulators into a cohesive model language that allows someone to build models to their needed level of fidelity andmore » expertise. Arion is also a software tool that translates the users model back into the specification languages of the simulators and test hardware needed for execution.« less

Library Specifications for a New Circulation System for Concordia University Libraries.

ERIC Educational Resources Information Center

Tallon, James

This study of library requirements for a new circulation system is organized into three sections: (1) items required for initial implementation in July 1982; (2) items relating to notice generation and activity statistics, with implementation expected by fall 1982; and (3) items provided in the system as initially implemented, with additional…

40 CFR Table 7 to Subpart Bbbb of... - Model Rule-Requirements for Continuous Emission Monitoring Systems (CEMS)

Code of Federal Regulations, 2010 CFR

2010-07-01

...—Requirements for Continuous Emission Monitoring Systems (CEMS) For the following pollutants Use the following span values for CEMS Use the following performance specifications in appendix B of this part for your CEMS If needed to meet minimum data requirements, use the folloiwng alternate methods in appendix A of...

40 CFR Table 7 to Subpart Bbbb of... - Model Rule-Requirements for Continuous Emission Monitoring Systems (CEMS)

Code of Federal Regulations, 2011 CFR

2011-07-01

...—Requirements for Continuous Emission Monitoring Systems (CEMS) For the following pollutants Use the following span values for CEMS Use the following performance specifications in appendix B of this part for your CEMS If needed to meet minimum data requirements, use the folloiwng alternate methods in appendix A of...

76 FR 36954 - ITS Joint Program Office; Core System Requirements Walkthrough and Architecture Proposal Review...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-23

... Architecture Proposal Review Meetings and Webinars; Notice of Public Meeting AGENCY: Research and Innovative... Requirements and Architecture Proposal. The first meeting, June 28-30, 2011, 9 a.m.-4:30 p.m. at the University..., will walk through the review of System Requirements Specification and Architecture Proposal. The second...

Integrated Instrumentation and Sensor Systems Enabling Condition-Based Maintenance of Aerospace Equipment

DTIC Science & Technology

2012-01-01

systems . For some specific sensor requirements in the domains considered here, for example, assessing system behavior and component state in gas turbine ...Cost Objectives. In general , the implication of the suitability and life cycle cost [LCC] driven objectives for integrated instrumentation/sensor system ...section should be considered. In general , the systems engineering approach provided clear benefits in defining user significant IISS system requirements and

An Approach to Building a Traceability Tool for Software Development

NASA Technical Reports Server (NTRS)

Delgado, Nelly; Watson, Tom

1997-01-01

It is difficult in a large, complex computer program to ensure that it meets the specified requirements. As the program evolves over time, a11 program constraints originally elicited during the requirements phase must be maintained. In addition, during the life cycle of the program, requirements typically change and the program must consistently reflect those changes. Imagine the following scenario. Company X wants to develop a system to automate its assembly line. With such a large system, there are many different stakeholders, e.g., managers, experts such as industrial and mechanical engineers, and end-users. Requirements would be elicited from all of the stake holders involved in the system with each stakeholder contributing their point of view to the requirements. For example, some of the requirements provided by an industrial engineer may concern the movement of parts through the assembly line. A point of view provided by the electrical engineer may be reflected in constraints concerning maximum power usage. End-users may be concerned with comfort and safety issues, whereas managers are concerned with the efficiency of the operation. With so many points of view affecting the requirements, it is difficult to manage them, communicate information to relevant stakeholders. and it is likely that conflicts in the requirements will arise. In the coding process, the implementors will make additional assumptions and interpretations on the design and the requirements of the system. During any stage of development, stakeholders may request that a requirement be added or changed. In such a dynamic environment, it is difficult to guarantee that the system will preserve the current set of requirements. Tracing, the mapping between objects in the artifacts of the system being developed, addresses this issue. Artifacts encompass documents such as the system definition, interview transcripts, memoranda, the software requirements specification, user's manuals, the functional specifications, design reports, and system code. Tracing helps 1) validate system features against, the requirement specification, 2) identify error sources and, most importantly, 3) manage change. With so many people involved in the development of the system, it becomes necessary to identify the reasons behind the design requirements or the implementation decisions. This paper is concerned with an approach that maps documents to constraints that capture properties of and relationships between the objects being modeled by the program. Section 2 provides the reader with a background on traceability tools. Section 3 gives a brief description of the context monitoring system on which the approach suggested in this paper is based. Section 4 presents an overview of our approach to providing traceability. The last section presents our future direction of research.

Study of multi-megawatt technology needs for photovoltaic space power systems, volume 2

NASA Technical Reports Server (NTRS)

Peterson, D. M.; Pleasant, R. L.

1981-01-01

Possible missions requiring multimegawatt photovoltaic space power systems in the 1990's time frame and power system technology needs associated with these missions are examined. Four specific task areas were considered: (1) missions requiring power in the 1-10 megawatt average power region; (2) alternative power systems and component technologies; (3) technology goals and sensitivity trades and analyses; and (4) technology recommendations. Specific concepts for photovoltaic power approaches considered were: planar arrays, concentrating arrays, hybrid systems using Rankine engines, thermophotovoltaic approaches; all with various photovoltaic cell component technologies. Various AC/DC power management approaches, and battery, fuel cell, and flywheel energy storage concepts are evaluated. Interactions with the electrical ion engine injection and stationkeeping system are also considered.

40 CFR 63.1184 - What do I need to know about the design specifications, installation, and operation of a bag leak...

Code of Federal Regulations, 2010 CFR

2010-07-01

... design specifications, installation, and operation of a bag leak detection system? 63.1184 Section 63... bag leak detection system? A bag leak detection system must meet the following requirements: (a) The bag leak detection system must be certified by the manufacturer to be capable of detecting PM...

The LLRF System for the S-Band RF Plants of the FERMI Linac

NASA Astrophysics Data System (ADS)

Fabris, A.; Byrd, J.; D'Auria, G.; Doolittle, L.; Gelmetti, F.; Huang, G.; Jones, J.; Milloch, M.; Predonzani, M.; Ratti, A.; Rohlev, T.; Salom, A.; Serrano, C.; Stettler, M.

2016-04-01

Specifications on electron beam quality for the operation of a linac-based free-electron laser (FEL), as FERMI in Trieste (Italy), impose stringent requirements on the stability of the electromagnetic fields of the accelerating sections. These specifications can be met only with state-of-the-art low-level RF (LLRF) systems based on advanced digital technologies. Design considerations, construction, and performance results of the FERMI digital LLRF are presented in this paper. The stability requirements derived by simulations are better than 0.1% in amplitude and 0.1° S-band in phase. The system installed in the FERMI Linac S-band RF plants has met these specifications and is in operation on a 24-h basis as a user facility. Capabilities of the system allow planning for new developments that are also described here.

Turboelectric Aircraft Drive Key Performance Parameters and Functional Requirements

NASA Technical Reports Server (NTRS)

Jansen, Ralph H.; Brown, Gerald V.; Felder, James L.; Duffy, Kirsten P.

2016-01-01

The purpose of this paper is to propose specific power and efficiency as the key performance parameters for a turboelectric aircraft power system and investigate their impact on the overall aircraft. Key functional requirements are identified that impact the power system design. Breguet range equations for a base aircraft and a turboelectric aircraft are found. The benefits and costs that may result from the turboelectric system are enumerated. A break-even analysis is conducted to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Turboelectric Aircraft Drive Key Performance Parameters and Functional Requirements

NASA Technical Reports Server (NTRS)

Jansen, Ralph; Brown, Gerald V.; Felder, James L.; Duffy, Kirsten P.

2015-01-01

The purpose of this presentation is to propose specific power and efficiency as the key performance parameters for a turboelectric aircraft power system and investigate their impact on the overall aircraft. Key functional requirements are identified that impact the power system design. Breguet range equations for a base aircraft and a turboelectric aircraft are found. The benefits and costs that may result from the turboelectric system are enumerated. A break-even analysis is conducted to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Turboelectric Aircraft Drive Key Performance Parameters and Functional Requirements

NASA Technical Reports Server (NTRS)

Jansen, Ralph H.; Brown, Gerald V.; Felder, James L.; Duffy, Kirsten P.

2015-01-01

The purpose of this paper is to propose specific power and efficiency as the key performance parameters for a turboelectric aircraft power system and investigate their impact on the overall aircraft. Key functional requirements are identified that impact the power system design. Breguet range equations for a base aircraft and a turboelectric aircraft are found. The benefits and costs that may result from the turboelectric system are enumerated. A break-even analysis is conducted to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Feasibility study for the Swaziland/Mozambique interconnector. EPC specifications. Export trade information

DOE Office of Scientific and Technical Information (OSTI.GOV)

NONE

1997-11-01

This study, conducted by Black & Veatch, was funded by the U.S. Trade and Development Agency. The report, produced for the Ministry of National Resources, Energy and Environment (MNRE) of Swaziland, determines the least cost capacity expansion option to meet the future power demand and system reliability criteria of Swaziland, with particular emphasis on the proposed Interconnector between Swaziland and Mozambique. Volume 3 contains EPC Specifications and is divided into the following divisions: (1) Commercial; (2) General Technical Requirements; (3) Transmission Line Technical Requirements; (4) Substation Technical Requirements; (5) Specifications.

Specification and simulation of behavior of the Continuous Infusion Insulin Pump system.

PubMed

Babamir, Seyed Morteza; Dehkordi, Mehdi Borhani

2014-01-01

Continuous Infusion Insulin Pump (CIIP) system is responsible for monitoring diabetic blood sugar. In this paper, we aim to specify and simulate the CIIP software behavior. To this end, we first: (1) presented a model consisting of the CIIP system behavior in response to its environment (diabetic) behavior and (2) we formally defined the safety requirements of the system environment (diabetic) in the Z formal modeling language. Such requirements should be satisfied by the CIIP software. Finally, we programmed the model and requirements.

Systems Maintenance Automated Repair Tasks (SMART)

NASA Technical Reports Server (NTRS)

Schuh, Joseph; Mitchell, Brent; Locklear, Louis; Belson, Martin A.; Al-Shihabi, Mary Jo Y.; King, Nadean; Norena, Elkin; Hardin, Derek

2010-01-01

SMART is a uniform automated discrepancy analysis and repair-authoring platform that improves technical accuracy and timely delivery of repair procedures for a given discrepancy (see figure a). SMART will minimize data errors, create uniform repair processes, and enhance the existing knowledge base of engineering repair processes. This innovation is the first tool developed that links the hardware specification requirements with the actual repair methods, sequences, and required equipment. SMART is flexibly designed to be useable by multiple engineering groups requiring decision analysis, and by any work authorization and disposition platform (see figure b). The organizational logic creates the link between specification requirements of the hardware, and specific procedures required to repair discrepancies. The first segment in the SMART process uses a decision analysis tree to define all the permutations between component/ subcomponent/discrepancy/repair on the hardware. The second segment uses a repair matrix to define what the steps and sequences are for any repair defined in the decision tree. This segment also allows for the selection of specific steps from multivariable steps. SMART will also be able to interface with outside databases and to store information from them to be inserted into the repair-procedure document. Some of the steps will be identified as optional, and would only be used based on the location and the current configuration of the hardware. The output from this analysis would be sent to a work authoring system in the form of a predefined sequence of steps containing required actions, tools, parts, materials, certifications, and specific requirements controlling quality, functional requirements, and limitations.

Development of Integrated Programs for Aerospace-Vehicle Design (IPAD) - IPAD user requirements

NASA Technical Reports Server (NTRS)

Anderton, G. L.

1979-01-01

Results of a requirements analysis task for Integrated Programs for Aerospace Vehicle Design (IPAD) are presented. User requirements which, in part, will shape the IPAD system design are given. Requirements considered were: generation, modification, storage, retrieval, communication, reporting, and protection of information. Data manipulation and controls on the system and the information were also considered. Specific needs relative to the product design process are also discussed.

STS users study (study 2.2). Volume 2: STS users plan (user data requirements) study

NASA Technical Reports Server (NTRS)

Pritchard, E. I.

1975-01-01

Pre-flight scheduling and pre-flight requirements of the space transportation system are discussed. Payload safety requirements, shuttle flight manifests, and interface specifications are studied in detail.

Requirements' Role in Mobilizing and Enabling Design Conversation

NASA Astrophysics Data System (ADS)

Bergman, Mark

Requirements play a critical role in a design conversation of systems and products. Product and system design exists at the crossroads of problems, solutions and requirements. Requirements contextualize problems and solutions, pointing the way to feasible outcomes. These are captured with models and detailed specifications. Still, stakeholders need to be able to understand one-another using shared design representations in order to mobilize bias and transform knowledge towards legitimized, desired results. Many modern modeling languages, including UML, as well as detailed, logic-based specifications are beyond the comprehension of key stakeholders. Hence, they inhibit, rather than promote design conversation. Improved design boundary objects (DBO), especially design requirements boundary objects (DRBO), need to be created and refined to improve the communications between principals. Four key features of design boundary objects that improve and promote design conversation are discussed in detail. A systems analysis and design case study is presented which demonstrates these features in action. It describes how a small team of analysts worked with key stakeholders to mobilize and guide a complex system design discussion towards an unexpected, yet desired outcome within a short time frame.

ASRDI Oxygen Technology Survey. Volume 2: Cleaning Requirements, Procedures, and Verification Techniques

NASA Technical Reports Server (NTRS)

Bankaitis, H.; Schueller, C. F.

1972-01-01

The oxygen system cleaning specifications drawn from 23 industrial and government sources are presented along with cleaning processes employed for meeting these specifications, and recommended postcleaning inspection procedures for establishing the cleanliness achieved. Areas of agreement and difference in the specifications, procedures, and inspection are examined. Also, the lack of clarity or specificity will be discussed. This absence of clarity represents potential safety hazards due to misinterpretation. It can result in exorbitant expenditures of time and money in satisfying unnecessary requirements.

32 CFR 319.13 - Specific exemptions.

Code of Federal Regulations, 2011 CFR

2011-07-01

... PROGRAM DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM § 319.13 Specific exemptions. (a) All systems of records maintained by the Director Intelligence Agency shall be exempt from the requirements of 5 U.S.C... has been properly classified. (b) The Director, Defense Intelligence Agency, designated the systems of...

32 CFR 319.13 - Specific exemptions.

Code of Federal Regulations, 2012 CFR

2012-07-01

... PROGRAM DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM § 319.13 Specific exemptions. (a) All systems of records maintained by the Director Intelligence Agency shall be exempt from the requirements of 5 U.S.C... has been properly classified. (b) The Director, Defense Intelligence Agency, designated the systems of...

32 CFR 319.13 - Specific exemptions.

Code of Federal Regulations, 2014 CFR

2014-07-01

... PROGRAM DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM § 319.13 Specific exemptions. (a) All systems of records maintained by the Director Intelligence Agency shall be exempt from the requirements of 5 U.S.C... has been properly classified. (b) The Director, Defense Intelligence Agency, designated the systems of...

32 CFR 319.13 - Specific exemptions.

Code of Federal Regulations, 2010 CFR

2010-07-01

... PROGRAM DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM § 319.13 Specific exemptions. (a) All systems of records maintained by the Director Intelligence Agency shall be exempt from the requirements of 5 U.S.C... has been properly classified. (b) The Director, Defense Intelligence Agency, designated the systems of...

Rationale for windshield glass system specification requirements for shuttle orbiter

NASA Technical Reports Server (NTRS)

Hayashida, K.; King, G. L.; Tesinsiky, J.; Wittenburg, D. R.

1972-01-01

A preliminary procurement specification for the space shuttle orbiter windshield pane, and some of the design considerations and rationale leading to its development are presented. The windshield designer is given the necessary methods and procedures for assuring glass pane structural integrity by proof test. These methods and procedures are fully developed for annealed and thermally tempered aluminosilicate, borosilicate, and soda lime glass and for annealed fused silica. Application of the method to chemically tempered glass is considered. Other considerations are vision requirements, protection against bird impact, hail, frost, rain, and meteoroids. The functional requirements of the windshield system during landing, ferrying, boost, space flight, and entry are included.

Spaceborne computer executive routine functional design specification. Volume 2: Computer executive design for space station/base

NASA Technical Reports Server (NTRS)

Kennedy, J. R.; Fitzpatrick, W. S.

1971-01-01

The computer executive functional system design concepts derived from study of the Space Station/Base are presented. Information Management System hardware configuration as directly influencing the executive design is reviewed. The hardware configuration and generic executive design requirements are considered in detail in a previous report (System Configuration and Executive Requirements Specifications for Reusable Shuttle and Space Station/Base, 9/25/70). This report defines basic system primitives and delineates processes and process control. Supervisor states are considered for describing basic multiprogramming and multiprocessing systems. A high-level computer executive including control of scheduling, allocation of resources, system interactions, and real-time supervisory functions is defined. The description is oriented to provide a baseline for a functional simulation of the computer executive system.

Requirements-Based Conformance Testing of ARINC 653 Real-Time Operating Systems

NASA Astrophysics Data System (ADS)

Maksimov, Andrey

2010-08-01

Requirements-based testing is emphasized in avionics certification documents because this strategy has been found to be the most effective at revealing errors. This paper describes the unified requirements-based approach to the creation of conformance test suites for mission-critical systems. The approach uses formal machine-readable specifications of requirements and finite state machine model for test sequences generation on-the-fly. The paper also presents the test system for automated test generation for ARINC 653 services built on this approach. Possible application of the presented approach to various areas of avionics embedded systems testing is discussed.

Towards the formal specification of the requirements and design of a processor interface unit

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1993-01-01

Work to formally specify the requirements and design of a Processor Interface Unit (PIU), a single-chip subsystem providing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system, is described. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance free operation, or both. The approaches that were developed for modeling the PIU requirements and for composition of the PIU subcomponents at high levels of abstraction are described. These approaches were used to specify and verify a nontrivial subset of the PIU behavior. The PIU specification in Higher Order Logic (HOL) is documented in a companion NASA contractor report entitled 'Towards the Formal Specification of the Requirements and Design of a Processor Interfacs Unit - HOL Listings.' The subsequent verification approach and HOL listings are documented in NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit' and NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit - HOL Listings.'

Requirements for migration of NSSD code systems from LTSS to NLTSS

NASA Technical Reports Server (NTRS)

Pratt, M.

1984-01-01

The purpose of this document is to address the requirements necessary for a successful conversion of the Nuclear Design (ND) application code systems to the NLTSS environment. The ND application code system community can be characterized as large-scale scientific computation carried out on supercomputers. NLTSS is a distributed operating system being developed at LLNL to replace the LTSS system currently in use. The implications of change are examined including a description of the computational environment and users in ND. The discussion then turns to requirements, first in a general way, followed by specific requirements, including a proposal for managing the transition.

Effect of power system technology and mission requirements on high altitude long endurance aircraft

NASA Technical Reports Server (NTRS)

Colozza, Anthony J.

1994-01-01

An analysis was performed to determine how various power system components and mission requirements affect the sizing of a solar powered long endurance aircraft. The aircraft power system consists of photovoltaic cells and a regenerative fuel cell. Various characteristics of these components, such as PV cell type, PV cell mass, PV cell efficiency, fuel cell efficiency, and fuel cell specific mass, were varied to determine what effect they had on the aircraft sizing for a given mission. Mission parameters, such as time of year, flight altitude, flight latitude, and payload mass and power, were also altered to determine how mission constraints affect the aircraft sizing. An aircraft analysis method which determines the aircraft configuration, aspect ratio, wing area, and total mass, for maximum endurance or minimum required power based on the stated power system and mission parameters is presented. The results indicate that, for the power system, the greatest benefit can be gained by increasing the fuel cell specific energy. Mission requirements also substantially affect the aircraft size. By limiting the time of year the aircraft is required to fly at high northern or southern latitudes, a significant reduction in aircraft size or increase in payload capacity can be achieved.

E-ELT requirements flow down

NASA Astrophysics Data System (ADS)

Gonzalez, J. C.; Kurlandczyk, H.; Schmid, C.; Schneller, D.

2016-08-01

One of the critical activities in the systems engineering scope of work is managing requirements. In line with this, E-ELT devotes a significant effort to this activity, which follows a well-established process. This involves optimally deriving requirements from the user (Top-Level Requirements) through the system Level 1 Requirements and from here down to subsystems procurement specifications. This paper describes the process, which is illustrated with some practical examples, including in particular the role of technical budgets to derive requirements on subsystems. Also, the provisions taken for the requirements verification are discussed.

40 CFR 75.13 - Specific provisions for monitoring CO2 emissions.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 16 2010-07-01 2010-07-01 false Specific provisions for monitoring CO2... monitoring CO2 emissions. (a) CO 2 continuous emission monitoring system. If the owner or operator chooses to... operating requirements in § 75.10 for a CO2 continuous emission monitoring system and flow monitoring system...

40 CFR 75.13 - Specific provisions for monitoring CO2 emissions.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 16 2011-07-01 2011-07-01 false Specific provisions for monitoring CO2... monitoring CO2 emissions. (a) CO 2 continuous emission monitoring system. If the owner or operator chooses to... operating requirements in § 75.10 for a CO2 continuous emission monitoring system and flow monitoring system...

40 CFR 75.13 - Specific provisions for monitoring CO2 emissions.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 40 Protection of Environment 17 2012-07-01 2012-07-01 false Specific provisions for monitoring CO2... monitoring CO2 emissions. (a) CO 2 continuous emission monitoring system. If the owner or operator chooses to... operating requirements in § 75.10 for a CO2 continuous emission monitoring system and flow monitoring system...

The Development and Initial Evaluation of the Human Readiness Level Framework

DTIC Science & Technology

2010-06-01

View ICD Initial Capabilities Document ICW Interactive Course Ware ILE Interactive Learning Environment ILT Instructor Led Training IOC...Programmatic Environmental Safety and Health Evaluation PHA Preliminary Hazard Analysis PHL Preliminary Hazard List xiv PM Program Manager PQS...Occupational Health SOW Statement of Work SRD System Requirements Document SPS System Performance Specification SRR System Requirements Review SVR

46 CFR 162.060-14 - Information requirements for the ballast water management system (BWMS) application.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 6 2012-10-01 2012-10-01 false Information requirements for the ballast water management system (BWMS) application. 162.060-14 Section 162.060-14 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) EQUIPMENT, CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems §...

46 CFR 162.060-30 - Testing requirements for ballast water management system (BWMS) components.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 6 2012-10-01 2012-10-01 false Testing requirements for ballast water management system (BWMS) components. 162.060-30 Section 162.060-30 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) EQUIPMENT, CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems § 162.060...

ITS component specification. Appendix A, Requirements per component

DOT National Transportation Integrated Search

1997-01-01

The objective of the Polaris Project is to define an Intelligent Transportation Systems (ITS) architecture for the state of Minnesota. This appendix lists the requirements that have been allocated to each component. The requirements for each componen...

Characterization of advanced electric propulsion systems

NASA Technical Reports Server (NTRS)

Ray, P. K.

1982-01-01

Characteristics of several advanced electric propulsion systems are evaluated and compared. The propulsion systems studied are mass driver, rail gun, MPD thruster, hydrogen free radical thruster and mercury electron bombardment ion engine. These are characterized by specific impulse, overall efficiency, input power, average thrust, power to average thrust ratio and average thrust to dry weight ratio. Several important physical characteristics such as dry system mass, accelerator length, bore size and current pulse requirement are also evaluated in appropriate cases. Only the ion engine can operate at a specific impulse beyond 2000 sec. Rail gun, MPD thruster and free radical thruster are currently characterized by low efficiencies. Mass drivers have the best performance characteristics in terms of overall efficiency, power to average thrust ratio and average thrust to dry weight ratio. But, they can only operate at low specific impulses due to large power requirements and are extremely long due to limitations of driving current. Mercury ion engines have the next best performance characteristics while operating at higher specific impulses. It is concluded that, overall, ion engines have somewhat better characteristics as compared to the other electric propulsion systems.

Network, system, and status software enhancements for the autonomously managed electrical power system breadboard. Volume 3: Commands specification

NASA Technical Reports Server (NTRS)

Mckee, James W.

1990-01-01

This volume (3 of 4) contains the specification for the command language for the AMPS system. The volume contains a requirements specification for the operating system and commands and a design specification for the operating system and command. The operating system and commands sits on top of the protocol. The commands are an extension of the present set of AMPS commands in that the commands are more compact, allow multiple sub-commands to be bundled into one command, and have provisions for identifying the sender and the intended receiver. The commands make no change to the actual software that implement the commands.

Development of an expert system prototype for determining software functional requirements for command management activities at NASA Goddard

NASA Technical Reports Server (NTRS)

Liebowitz, J.

1985-01-01

The development of an expert system prototype for determining software functional requirements for NASA Goddard's Command Management System (CMS) is described. The role of the CMS is to transform general requests into specific spacecraft commands with command execution conditions. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Subjects covered include: the problem environment of determining CMS software functional requirements; the expert system approach for handling CMS requirements development; validation and evaluation procedures for the expert system.

Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

NASA Technical Reports Server (NTRS)

Lutz, Robyn R.

1993-01-01

This paper analyzes the root causes of safety-related software errors in safety-critical, embedded systems. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than non- safety-related software errors. Safety-related software errors are shown to arise most commonly from (1) discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system and (2) misunderstandings of the software's interface with the rest of the system. The paper uses these results to identify methods by which requirements errors can be prevented. The goal is to reduce safety-related software errors and to enhance the safety of complex, embedded systems.

The Open System Interconnection as a building block in a health sciences information network.

PubMed Central

Boss, R W

1985-01-01

The interconnection of integrated health sciences library systems with other health sciences computer systems to achieve information networks will require either custom linkages among specific devices or the adoption of standards that all systems support. The most appropriate standards appear to be those being developed under the Open System Interconnection (OSI) reference model, which specifies a set of rules and functions that computers must follow to exchange information. The protocols have been modularized into seven different layers. The lowest three layers are generally available as off-the-shelf interfacing products. The higher layers require special development for particular applications. This paper describes the OSI, its application in health sciences networks, and specific tasks that remain to be undertaken. PMID:4052672

46 CFR 162.060-22 - Marking requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... effects of normal wear and tear and exposure to water, salt spray, direct sunlight, heat, cold, and any...: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems § 162.060-22 Marking requirements. (a) Each ballast water management system (BWMS) manufactured under Coast Guard approval must have...

46 CFR 162.060-22 - Marking requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... effects of normal wear and tear and exposure to water, salt spray, direct sunlight, heat, cold, and any...: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems § 162.060-22 Marking requirements. (a) Each ballast water management system (BWMS) manufactured under Coast Guard approval must have...

46 CFR 162.060-22 - Marking requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... effects of normal wear and tear and exposure to water, salt spray, direct sunlight, heat, cold, and any...: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems § 162.060-22 Marking requirements. (a) Each ballast water management system (BWMS) manufactured under Coast Guard approval must have...

48 CFR 552.236-77 - Specifications and Drawings

Code of Federal Regulations, 2010 CFR

2010-10-01

... Drawings 552.236-77 Section 552.236-77 Federal Acquisition Regulations System GENERAL SERVICES....236-77 Specifications and Drawings As prescribed in 536.570-8, insert the following clause: Specifications and Drawings (SEP 1999) The requirements of the clause entitled “Specifications and Drawings for...

Slurry Coating System Statement of Work and Specification

DOE Office of Scientific and Technical Information (OSTI.GOV)

Chan, S. M.

2017-02-06

The Slurry Coating System will be used to coat crystals with a polymer to support Lawrence Livermore National Security, LLC (LLNS) research and development at Lawrence Livermore National Laboratory (LLNL). The crystals will be suspended in water in a kettle. A polymer solution is added, temperature of the kettle is raised and aggregates of the crystals and polymer form. The slurry is heated under vacuum to drive off the solvents and slowly cooled while mixing to room temperature. The resulting aggregates are then filtered and dried. The performance characteristics and fielding constraints define a unique set of requirements for amore » new system. This document presents the specifications and requirements for the system.« less

40 CFR 270.21 - Specific part B information requirements for landfills.

Code of Federal Regulations, 2013 CFR

2013-07-01

... surface water at any future time; (ii) The double liner and leak (leachate) detection, collection, and... system, leachate collection and removal system, leak detection system, cover system, and appurtenances...

40 CFR 270.21 - Specific part B information requirements for landfills.

Code of Federal Regulations, 2012 CFR

2012-07-01

... surface water at any future time; (ii) The double liner and leak (leachate) detection, collection, and... system, leachate collection and removal system, leak detection system, cover system, and appurtenances...

40 CFR 270.21 - Specific part B information requirements for landfills.

Code of Federal Regulations, 2011 CFR

2011-07-01

... surface water at any future time; (ii) The double liner and leak (leachate) detection, collection, and... system, leachate collection and removal system, leak detection system, cover system, and appurtenances...

40 CFR 270.21 - Specific part B information requirements for landfills.

Code of Federal Regulations, 2014 CFR

2014-07-01

... surface water at any future time; (ii) The double liner and leak (leachate) detection, collection, and... system, leachate collection and removal system, leak detection system, cover system, and appurtenances...

Some requirements and suggestions for a methodology to develop knowledge based systems.

PubMed

Green, D W; Colbert, M; Long, J

1989-11-01

This paper describes an approach to the creation of a methodology for the development of knowledge based systems. It specifies some requirements and suggests how these requirements might be met. General requirements can be satisfied using a systems approach. More specific ones can be met by viewing an organization as a network of consultations for coordinating expertise. The nature of consultations is described and the form of a possible cognitive model using a blackboard architecture is outlined. The value of the approach is illustrated in terms of certain knowledge elicitation methods.

Network Security Validation Using Game Theory

NASA Astrophysics Data System (ADS)

Papadopoulou, Vicky; Gregoriades, Andreas

Non-functional requirements (NFR) such as network security recently gained widespread attention in distributed information systems. Despite their importance however, there is no systematic approach to validate these requirements given the complexity and uncertainty characterizing modern networks. Traditionally, network security requirements specification has been the results of a reactive process. This however, limited the immunity property of the distributed systems that depended on these networks. Security requirements specification need a proactive approach. Networks' infrastructure is constantly under attack by hackers and malicious software that aim to break into computers. To combat these threats, network designers need sophisticated security validation techniques that will guarantee the minimum level of security for their future networks. This paper presents a game-theoretic approach to security requirements validation. An introduction to game theory is presented along with an example that demonstrates the application of the approach.

Using SysML for MBSE analysis of the LSST system

NASA Astrophysics Data System (ADS)

Claver, Charles F.; Dubois-Felsmann, Gregory; Delgado, Francisco; Hascall, Pat; Marshall, Stuart; Nordby, Martin; Schalk, Terry; Schumacher, German; Sebag, Jacques

2010-07-01

The Large Synoptic Survey Telescope is a complex hardware - software system of systems, making up a highly automated observatory in the form of an 8.4m wide-field telescope, a 3.2 billion pixel camera, and a peta-scale data processing and archiving system. As a project, the LSST is using model based systems engineering (MBSE) methodology for developing the overall system architecture coded with the Systems Modeling Language (SysML). With SysML we use a recursive process to establish three-fold relationships between requirements, logical & physical structural component definitions, and overall behavior (activities and sequences) at successively deeper levels of abstraction and detail. Using this process we have analyzed and refined the LSST system design, ensuring the consistency and completeness of the full set of requirements and their match to associated system structure and behavior. As the recursion process proceeds to deeper levels we derive more detailed requirements and specifications, and ensure their traceability. We also expose, define, and specify critical system interfaces, physical and information flows, and clarify the logic and control flows governing system behavior. The resulting integrated model database is used to generate documentation and specifications and will evolve to support activities from construction through final integration, test, and commissioning, serving as a living representation of the LSST as designed and built. We discuss the methodology and present several examples of its application to specific systems engineering challenges in the LSST design.

Space Tug Docking Study. Volume 1: Executive Summary

NASA Technical Reports Server (NTRS)

1976-01-01

Results of a detailed systems analysis of the entire rendezvous and docking operation to be performed by the all-up space tug are presented. Specific areas investigated include: generating of operational requirements and a data base of candidate operational techniques and subsystem mechanizations; selection and ranking of integrated system designs capable of meeting the requirements generated; and definition of this simulation/demonstration program required to select and prove the most effective manual, autonomous, and hybrid rendezvous and docking systems.

Managing Legal Texts in Requirements Engineering

NASA Astrophysics Data System (ADS)

Otto, Paul N.; Antón, Annie I.

Laws and regulations are playing an increasingly important role in requirements engineering and systems development. Monitoring systems for requirements and policy compliance has been recognized in the requirements engineering community as a key area for research. Similarly, legal compliance is critical in systems development, especially given that non-compliance can result in both financial and criminal penalties. Working with legal texts can be very challenging, however, because they contain numerous ambiguities, cross-references, domain-specific definitions, and acronyms, and are frequently amended via new statutes, regulations, and case law. Requirements engineers and compliance auditors must be able to identify relevant legal texts, extract requirements and other key concepts, and monitor compliance. This chapter surveys research efforts over the past 50 years in handling legal texts for systems development. This survey can aid requirements engineers and auditors to better specify, test, and monitor systems for compliance.

Can IR scene projectors reduce total system cost?

NASA Astrophysics Data System (ADS)

Ginn, Robert; Solomon, Steven

2006-05-01

There is an incredible amount of system engineering involved in turning the typical infrared system needs of probability of detection, probability of identification, and probability of false alarm into focal plane array (FPA) requirements of noise equivalent irradiance (NEI), modulation transfer function (MTF), fixed pattern noise (FPN), and defective pixels. Unfortunately, there are no analytic solutions to this problem so many approximations and plenty of "seat of the pants" engineering is employed. This leads to conservative specifications, which needlessly drive up system costs by increasing system engineering costs, reducing FPA yields, increasing test costs, increasing rework and the never ending renegotiation of requirements in an effort to rein in costs. These issues do not include the added complexity to the FPA factory manager of trying to meet varied, and changing, requirements for similar products because different customers have made different approximations and flown down different specifications. Scene generation technology may well be mature and cost effective enough to generate considerable overall savings for FPA based systems. We will compare the costs and capabilities of various existing scene generation systems and estimate the potential savings if implemented at several locations in the IR system fabrication cycle. The costs of implementing this new testing methodology will be compared to the probable savings in systems engineering, test, rework, yield improvement and others. The diverse requirements and techniques required for testing missile warning systems, missile seekers, and FLIRs will be defined. Last, we will discuss both the hardware and software requirements necessary to meet the new test paradigm and discuss additional cost improvements related to the incorporation of these technologies.

Hercules Single-Stage Reusable Vehicle (HSRV) Operating Base

NASA Technical Reports Server (NTRS)

Moon, Michael J.; McCleskey, Carey M.

2017-01-01

Conceptual design for the layout of lunar-planetary surface support systems remains an important area needing further master planning. This paper explores a structured approach to organize the layout of a Mars-based site equipped for routinely flying a human-scale reusable taxi system. The proposed Hercules Transportation System requires a surface support capability to sustain its routine, affordable, and dependable operation. The approach organizes a conceptual Hercules operating base through functional station sets. The station set approach will allow follow-on work to trade design approaches and consider technologies for more efficient flow of material, energy, and information at future Mars bases and settlements. The station set requirements at a Mars site point to specific capabilities needed. By drawing from specific Hercules design characteristics, the technology requirements for surface-based systems will come into greater focus. This paper begins a comprehensive process for documenting functional needs, architectural design methods, and analysis techniques necessary for follow-on concept studies.

Perspective on the combined use of an independent transgenic sexing and a multifactorial reproductive sterility system to avoid resistance development against transgenic Sterile Insect Technique approaches

PubMed Central

2014-01-01

Background The Sterile Insect Technique (SIT) is an accepted species-specific genetic control approach that acts as an insect birth control measure, which can be improved by biotechnological engineering to facilitate its use and widen its applicability. First transgenic insects carrying a single killing system have already been released in small scale trials. However, to evade resistance development to such transgenic approaches, completely independent ways of transgenic killing should be established and combined. Perspective Most established transgenic sexing and reproductive sterility systems are based on the binary tTA expression system that can be suppressed by adding tetracycline to the food. However, to create 'redundant killing' an additional independent conditional expression system is required. Here we present a perspective on the use of a second food-controllable binary expression system - the inducible Q system - that could be used in combination with site-specific recombinases to generate independent transgenic killing systems. We propose the combination of an already established transgenic embryonic sexing system to meet the SIT requirement of male-only releases based on the repressible tTA system together with a redundant male-specific reproductive sterility system, which is activated by Q-system controlled site-specific recombination and is based on a spermatogenesis-specifically expressed endonuclease acting on several species-specific target sites leading to chromosome shredding. Conclusion A combination of a completely independent transgenic sexing and a redundant reproductive male sterility system, which do not share any active components and mediate the induced lethality by completely independent processes, would meet the 'redundant killing' criteria for suppression of resistance development and could therefore be employed in large scale long-term suppression programs using biotechnologically enhanced SIT. PMID:25471733

A proposal of criteria for the classification of systemic sclerosis.

PubMed

Nadashkevich, Oleg; Davis, Paul; Fritzler, Marvin J

2004-11-01

Sensitive and specific criteria for the classification of systemic sclerosis are required by clinicians and investigators to achieve higher quality clinical studies and approaches to therapy. A clinical study of systemic sclerosis patients in Europe and Canada led to a set of criteria that achieve high sensitivity and specificity. Both clinical and laboratory investigations of patients with systemic sclerosis, related conditions and diseases with clinical features that can be mistaken as part of the systemic sclerosis spectrum were undertaken. Laboratory investigations included the detection of autoantibodies to centromere proteins, Scl-70 (topoisomerase I), and fibrillarin (U3-RNP). Based on the investigation of 269 systemic sclerosis patients and 720 patients presenting with related and confounding conditions, the following set of criteria for the classification of systemic sclerosis was proposed: 1) autoantibodies to: centromere proteins, Scl-70 (topo I), fibrillarin; 2) bibasilar pulmonary fibrosis; 3) contractures of the digital joints or prayer sign; 4) dermal thickening proximal to the wrists; 5) calcinosis cutis; 6) Raynaud's phenomenon; 7) esophageal distal hypomotility or reflux-esophagitis; 8) sclerodactyly or non-pitting digital edema; 9) teleangiectasias. The classification of definite SSc requires at least three of the above criteria. Criteria for the classification of systemic sclerosis have been proposed. Preliminary testing has defined the sensitivity and specificity of these criteria as high as 99% and 100%, respectively. Testing and validation of the proposed criteria by other clinical centers is required.

7 CFR 1724.54 - Requirements for RUS approval of plans and specifications.

Code of Federal Regulations, 2012 CFR

2012-01-01

... specifications for transmission construction projects which are not based on RUS approved line design data or do...) Communications and control facilities. (1) This paragraph (g) covers microwave and powerline carrier communications systems, load control, and supervisory control and data acquisition (SCADA) systems. (2) The...

7 CFR 1724.54 - Requirements for RUS approval of plans and specifications.

Code of Federal Regulations, 2014 CFR

2014-01-01

... specifications for transmission construction projects which are not based on RUS approved line design data or do...) Communications and control facilities. (1) This paragraph (g) covers microwave and powerline carrier communications systems, load control, and supervisory control and data acquisition (SCADA) systems. (2) The...

7 CFR 1724.54 - Requirements for RUS approval of plans and specifications.

Code of Federal Regulations, 2013 CFR

2013-01-01

... specifications for transmission construction projects which are not based on RUS approved line design data or do...) Communications and control facilities. (1) This paragraph (g) covers microwave and powerline carrier communications systems, load control, and supervisory control and data acquisition (SCADA) systems. (2) The...

System specification for the reusable reentry satellite

NASA Technical Reports Server (NTRS)

1991-01-01

The RRS design shall provide a relatively inexpensive method of access to micro and fractional gravity space environments for an extended period of time, with eventual intact recovery on the surface of the Earth. This specification establishes the performance, design, development, and test requirements for the Reusable Reentry Satellite (RRS) system.

Responding to an RFP: A Vendor's Viewpoint.

ERIC Educational Resources Information Center

Kington, Robert A.

1987-01-01

Outlines factors used by online vendors to decide whether to bid on RFPs (requests for proposals) for library automation systems, including specifications for software, hardware or performance requirements not met by the vendor; specifications based on competitors' systems; the size and complexity of the request itself; and vendors' time…

[Status and suggestions for adjuvant standard for Chinese materia medica processing in China].

PubMed

Yang, Chun-Yu; Cao, Hui; Wang, Xiao-Tao; Tu, Jia-Sheng; Qian, Zhong-Zhi; Yu, Zhi-Ling; Shang, Yue; Zhang, Bao-Xian

2017-04-01

In this paper, the status of adjuvant standard for Chinese materia medica processing in the Chinese Pharmacopoeia 2015 edition, the National Specification of Chinese Materia Medica Processing, and the 29 provincial specification of Chinese materia medica was summarized, and the the status including general requirements, specific requirements, and quality standard in the three grade official specifications was collected and analyzed according to the "medicine-adjuvant homology" and "food-adjuvant homology" features of adjuvants. This paper also introduced the research situation of adjuvant standard for Chinese materia medica processing in China; In addition, analyzed and discussed the problems existing in the standard system of adjuvant for Chinese materia medica processing, such as lack of general requirements, low level of standard, inconsistent standard references, and lack of research on the standard, and provided suggestions for the further establishment of the national standards system of adjuvant for Chinese materia medica processing. Copyright© by the Chinese Pharmaceutical Association.

40 CFR 63.10020 - How do I monitor and collect data to demonstrate continuous compliance?

Code of Federal Regulations, 2014 CFR

2014-07-01

...-of-control periods, or required monitoring system quality assurance or control activities in... monitoring system quality assurance or quality control activities including, as applicable, calibration... collect data according to this section and the site-specific monitoring plan required by § 63.10000(d). (b...

40 CFR 63.10020 - How do I monitor and collect data to demonstrate continuous compliance?

Code of Federal Regulations, 2012 CFR

2012-07-01

...-of-control periods, or required monitoring system quality assurance or control activities in... monitoring system quality assurance or quality control activities including, as applicable, calibration... collect data according to this section and the site-specific monitoring plan required by § 63.10000(d). (b...

40 CFR 63.10020 - How do I monitor and collect data to demonstrate continuous compliance?

Code of Federal Regulations, 2013 CFR

2013-07-01

...-of-control periods, or required monitoring system quality assurance or control activities in... monitoring system quality assurance or quality control activities including, as applicable, calibration... collect data according to this section and the site-specific monitoring plan required by § 63.10000(d). (b...

46 CFR 62.35-15 - Fire safety.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Fire safety. 62.35-15 Section 62.35-15 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-15 Fire safety. (a) All required fire pump...

46 CFR 62.35-15 - Fire safety.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Fire safety. 62.35-15 Section 62.35-15 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-15 Fire safety. (a) All required fire pump...

Study of industry information requirements for flight control and navigation systems of STOL aircraft

NASA Technical Reports Server (NTRS)

Gorham, J. A.

1976-01-01

Answers to specific study questions are used to ascertain the data requirements associated with a guidance, navigation and control system for a future civil STOL airplane. Results of the study were used to recommend changes for improving the outputs of the STOLAND flight experiments program.

Automatic Methods and Tools for the Verification of Real Time Systems

DTIC Science & Technology

1997-07-31

real - time systems . This was accomplished by extending techniques, based on automata theory and temporal logic, that have been successful for the verification of time-independent reactive systems. As system specification lanmaage for embedded real - time systems , we introduced hybrid automata, which equip traditional discrete automata with real-numbered clock variables and continuous environment variables. As requirements specification languages, we introduced temporal logics with clock variables for expressing timing constraints.

Skylab vectorcardiograph: System description and in flight operation

NASA Technical Reports Server (NTRS)

Lintott, J.; Costello, M. J.

1975-01-01

A vectorcardiograph system was used to measure cardiac electrical activity of Skylab crewmen. This system was chosen because of its data-quantification advantages. The vectorcardiograph was required to meet recommended American Heart Association specifications, to withstand space environmental extremes, and to facilitate data gathering in the weightless environment. The vectorcardiograph system performed without failure, and all projected data were acquired. The appendix lists the design specifications used for the Skylab vectorcardiograph system.

Automatically Grading Customer Confidence in a Formal Specification.

ERIC Educational Resources Information Center

Shukur, Zarina; Burke, Edmund; Foxley, Eric

1999-01-01

Describes an automatic grading system for a formal methods computer science course that is able to evaluate a formal specification written in the Z language. Quality is measured by considering first, specification correctness (syntax, semantics, and satisfaction of customer requirements), and second, specification maintainability (comparison of…

Opportunistic Computing with Lobster: Lessons Learned from Scaling up to 25k Non-Dedicated Cores

NASA Astrophysics Data System (ADS)

Wolf, Matthias; Woodard, Anna; Li, Wenzhao; Hurtado Anampa, Kenyi; Yannakopoulos, Anna; Tovar, Benjamin; Donnelly, Patrick; Brenner, Paul; Lannon, Kevin; Hildreth, Mike; Thain, Douglas

2017-10-01

We previously described Lobster, a workflow management tool for exploiting volatile opportunistic computing resources for computation in HEP. We will discuss the various challenges that have been encountered while scaling up the simultaneous CPU core utilization and the software improvements required to overcome these challenges. Categories: Workflows can now be divided into categories based on their required system resources. This allows the batch queueing system to optimize assignment of tasks to nodes with the appropriate capabilities. Within each category, limits can be specified for the number of running jobs to regulate the utilization of communication bandwidth. System resource specifications for a task category can now be modified while a project is running, avoiding the need to restart the project if resource requirements differ from the initial estimates. Lobster now implements time limits on each task category to voluntarily terminate tasks. This allows partially completed work to be recovered. Workflow dependency specification: One workflow often requires data from other workflows as input. Rather than waiting for earlier workflows to be completed before beginning later ones, Lobster now allows dependent tasks to begin as soon as sufficient input data has accumulated. Resource monitoring: Lobster utilizes a new capability in Work Queue to monitor the system resources each task requires in order to identify bottlenecks and optimally assign tasks. The capability of the Lobster opportunistic workflow management system for HEP computation has been significantly increased. We have demonstrated efficient utilization of 25 000 non-dedicated cores and achieved a data input rate of 30 Gb/s and an output rate of 500GB/h. This has required new capabilities in task categorization, workflow dependency specification, and resource monitoring.

Advanced Integrated Display System V/STOL Program Performance Specification. Volume I.

DTIC Science & Technology

1980-06-01

sensor inputs required before the sensor can be designated acceptable. The reactivation count of each sensor parameter which satisfies its veri...129 3.5.2 AIDS Configuration Parameters .............. 133 3.5.3 AIDS Throughput Requirements ............... 133 4 QUALITY ASSURANCE...lists the adaptation parameters of the AIDS software; these parameters include the throughput and memory requirements of the software. 3.2 SYSTEM

The National Map seamless digital elevation model specifications

USGS Publications Warehouse

Archuleta, Christy-Ann M.; Constance, Eric W.; Arundel, Samantha T.; Lowe, Amanda J.; Mantey, Kimberly S.; Phillips, Lori A.

2017-08-02

This specification documents the requirements and standards used to produce the seamless elevation layers for The National Map of the United States. Seamless elevation data are available for the conterminous United States, Hawaii, Alaska, and the U.S. territories, in three different resolutions—1/3-arc-second, 1-arc-second, and 2-arc-second. These specifications include requirements and standards information about source data requirements, spatial reference system, distribution tiling schemes, horizontal resolution, vertical accuracy, digital elevation model surface treatment, georeferencing, data source and tile dates, distribution and supporting file formats, void areas, metadata, spatial metadata, and quality assurance and control.

Systems, methods and apparatus for pattern matching in procedure development and verification

NASA Technical Reports Server (NTRS)

Hinchey, Michael G. (Inventor); Rouff, Christopher A. (Inventor); Rash, James L. (Inventor)

2011-01-01

Systems, methods and apparatus are provided through which, in some embodiments, a formal specification is pattern-matched from scenarios, the formal specification is analyzed, and flaws in the formal specification are corrected. The systems, methods and apparatus may include pattern-matching an equivalent formal model from an informal specification. Such a model can be analyzed for contradictions, conflicts, use of resources before the resources are available, competition for resources, and so forth. From such a formal model, an implementation can be automatically generated in a variety of notations. The approach can improve the resulting implementation, which, in some embodiments, is provably equivalent to the procedures described at the outset, which in turn can improve confidence that the system reflects the requirements, and in turn reduces system development time and reduces the amount of testing required of a new system. Moreover, in some embodiments, two or more implementations can be "reversed" to appropriate formal models, the models can be combined, and the resulting combination checked for conflicts. Then, the combined, error-free model can be used to generate a new (single) implementation that combines the functionality of the original separate implementations, and may be more likely to be correct.

The Importance of Water for High Fidelity Information Processing and for Life

NASA Technical Reports Server (NTRS)

Hoehler, Tori M.; Pohorille, Andrew

2011-01-01

Is water an absolute prerequisite for life? Life depends on a variety of non-covalent interactions among molecules, the nature of which is determined as much by the solvent in which they occur as by the molecules themselves. Catalysis and information processing, two essential functions of life, require non-covalent molecular recognition with very high specificity. For example, to correctly reproduce a string consisting of 600,000 units of information (e.g ., 600 kilobases, equivalent to the genome of the smallest free living terrestrial organisms) with a 90% success rate requires specificity > 107 : 1 for the target molecule vs. incorrect alternatives. Such specificity requires (i) that the correct molecular association is energetically stabilized by at least 40 kJ/mol relative to alternatives, and (ii) that the system is able to sample among possible states (alternative molecular associations) rapidly enough to allow the system to fall under thermodynamic control and express the energetic stabilization. We argue that electrostatic interactions are required to confer the necessary energetic stabilization vs. a large library of molecular alternatives, and that a solvent with polarity and dielectric properties comparable to water is required for the system to sample among possible states and express thermodynamic control. Electrostatic associations can be made in non-polar solvents, but the resulting complexes are too stable to be "unmade" with sufficient frequency to confer thermodynamic control on the system. An electrostatic molecular complex representing 3 units of information (e.g., 3 base pairs) with specificity > 107 per unit has a stability in non-polar solvent comparable to that of a carbon-carbon bond at room temperature. These considerations suggest that water, or a solvent with properties very like water, is necessary to support high-fidelity information processing, and can therefore be considered a critical prerequisite for life.

Requirement Assurance: A Verification Process

NASA Technical Reports Server (NTRS)

Alexander, Michael G.

2011-01-01

Requirement Assurance is an act of requirement verification which assures the stakeholder or customer that a product requirement has produced its "as realized product" and has been verified with conclusive evidence. Product requirement verification answers the question, "did the product meet the stated specification, performance, or design documentation?". In order to ensure the system was built correctly, the practicing system engineer must verify each product requirement using verification methods of inspection, analysis, demonstration, or test. The products of these methods are the "verification artifacts" or "closure artifacts" which are the objective evidence needed to prove the product requirements meet the verification success criteria. Institutional direction is given to the System Engineer in NPR 7123.1A NASA Systems Engineering Processes and Requirements with regards to the requirement verification process. In response, the verification methodology offered in this report meets both the institutional process and requirement verification best practices.

Approximating Fluid Flow from Ambient to Very Low Pressures: Modeling ISS Experiments that Vent to Vacuum

NASA Technical Reports Server (NTRS)

Minor, Robert

2002-01-01

Two ISS (International Space Station) experiment payloads will vent a volume of gas overboard via either the ISS Vacuum Exhaust System or the Vacuum Resource System. A system of ducts, valves and sensors, under design, will connect the experiments to the ISS systems. The following tasks are required: Create an analysis tool that will verify the rack vacuum system design with respect to design requirements, more specifically approximate pressure at given locations within the vacuum systems; Determine the vent duration required to achieve desired pressure within the experiment modules; Update the analysis as systems and operations definitions mature.

Design of a clinical notification system.

PubMed

Wagner, M M; Tsui, F C; Pike, J; Pike, L

1999-01-01

We describe the requirements and design of an enterprise-wide notification system. From published descriptions of notification schemes, our own experience, and use cases provided by diverse users in our institution, we developed a set of functional requirements. The resulting design supports multiple communication channels, third party mappings (algorithms) from message to recipient and/or channel of delivery, and escalation algorithms. A requirement for multiple message formats is addressed by a document specification. We implemented this system in Java as a CORBA object. This paper describes the design and current implementation of our notification system.

Flywheel energy storage for electromechanical actuation systems

NASA Technical Reports Server (NTRS)

Hockney, Richard L.; Goldie, James H.; Kirtley, James L.

1991-01-01

The authors describe a flywheel energy storage system designed specifically to provide load-leveling for a thrust vector control (TVC) system using electromechanical actuators (EMAs). One of the major advantages of an EMA system over a hydraulic system is the significant reduction in total energy consumed during the launch profile. Realization of this energy reduction will, however, require localized energy storage capable of delivering the peak power required by the EMAs. A combined flywheel-motor/generator unit which interfaces directly to the 20-kHz power bus represents an ideal candidate for this load leveling. The overall objective is the definition of a flywheel energy storage system for this application. The authors discuss progress on four technical objectives: (1) definition of the specifications for the flywheel-motor/generator system, including system-level trade-off analysis; (2) design of the flywheel rotor; (3) design of the motor/generator; and (4) determination of the configuration for the power management system.

Flywheel energy storage for electromechanical actuation systems

NASA Astrophysics Data System (ADS)

Hockney, Richard L.; Goldie, James H.; Kirtley, James L.

The authors describe a flywheel energy storage system designed specifically to provide load-leveling for a thrust vector control (TVC) system using electromechanical actuators (EMAs). One of the major advantages of an EMA system over a hydraulic system is the significant reduction in total energy consumed during the launch profile. Realization of this energy reduction will, however, require localized energy storage capable of delivering the peak power required by the EMAs. A combined flywheel-motor/generator unit which interfaces directly to the 20-kHz power bus represents an ideal candidate for this load leveling. The overall objective is the definition of a flywheel energy storage system for this application. The authors discuss progress on four technical objectives: (1) definition of the specifications for the flywheel-motor/generator system, including system-level trade-off analysis; (2) design of the flywheel rotor; (3) design of the motor/generator; and (4) determination of the configuration for the power management system.

Experience report: Using formal methods for requirements analysis of critical spacecraft software

NASA Technical Reports Server (NTRS)

Lutz, Robyn R.; Ampo, Yoko

1994-01-01

Formal specification and analysis of requirements continues to gain support as a method for producing more reliable software. However, the introduction of formal methods to a large software project is difficult, due in part to the unfamiliarity of the specification languages and the lack of graphics. This paper reports results of an investigation into the effectiveness of formal methods as an aid to the requirements analysis of critical, system-level fault-protection software on a spacecraft currently under development. Our experience indicates that formal specification and analysis can enhance the accuracy of the requirements and add assurance prior to design development in this domain. The work described here is part of a larger, NASA-funded research project whose purpose is to use formal-methods techniques to improve the quality of software in space applications. The demonstration project described here is part of the effort to evaluate experimentally the effectiveness of supplementing traditional engineering approaches to requirements specification with the more rigorous specification and analysis available with formal methods.

Cultural Competency Training Requirements in Graduate Medical Education

PubMed Central

Ambrose, Adrian Jacques H.; Lin, Susan Y.; Chun, Maria B. J.

2013-01-01

Background Cultural competency is an important skill that prepares physicians to care for patients from diverse backgrounds. Objective We reviewed Accreditation Council for Graduate Medical Education (ACGME) program requirements and relevant documents from the ACGME website to evaluate competency requirements across specialties. Methods The program requirements for each specialty and its subspecialties were reviewed from December 2011 through February 2012. The review focused on the 3 competency domains relevant to culturally competent care: professionalism, interpersonal and communication skills, and patient care. Specialty and subspecialty requirements were assigned a score between 0 and 3 (from least specific to most specific). Given the lack of a standardized cultural competence rating system, the scoring was based on explicit mention of specific keywords. Results A majority of program requirements fell into the low- or no-specificity score (1 or 0). This included 21 core specialties (leading to primary board certification) program requirements (78%) and 101 subspecialty program requirements (79%). For all specialties, cultural competency elements did not gravitate toward any particular competency domain. Four of 5 primary care program requirements (pediatrics, obstetrics-gynecology, family medicine, and psychiatry) acquired the high-specificity score of 3, in comparison to only 1 of 22 specialty care program requirements (physical medicine and rehabilitation). Conclusions The degree of specificity, as judged by use of keywords in 3 competency domains, in ACGME requirements regarding cultural competency is highly variable across specialties and subspecialties. Greater specificity in requirements is expected to benefit the acquisition of cultural competency in residents, but this has not been empirically tested. PMID:24404264

Generic waste management requirements for a controlled ecological life support system /CELSS/

NASA Technical Reports Server (NTRS)

Hoshizaki, T.; Hansen, B. D., III

1981-01-01

Regenerative life support systems for future space missions will require closure of the waste-food loop. Each mission application will generate specific requirements for the waste management system. However, there are generic input and output requirements that can be identified when a probable scenario is chosen. This paper discusses the generic requirements when higher plants are chosen as the primary food source. Attention is focused on the quality and quantity of nutrients necessary for culturing higher plants. The types of wastes to be processed are also discussed. In addition, requirements generated by growing plants on three different substrates are presented. This work suggests that the mineral composition of waste materials may require minimal adjustment to satisfy the plant requirements.

Direct Administration of Nerve-Specific Contrast to Improve Nerve Sparing Radical Prostatectomy

PubMed Central

Barth, Connor W.; Gibbs, Summer L.

2017-01-01

Nerve damage remains a major morbidity following nerve sparing radical prostatectomy, significantly affecting quality of life post-surgery. Nerve-specific fluorescence guided surgery offers a potential solution by enhancing nerve visualization intraoperatively. However, the prostate is highly innervated and only the cavernous nerve structures require preservation to maintain continence and potency. Systemic administration of a nerve-specific fluorophore would lower nerve signal to background ratio (SBR) in vital nerve structures, making them difficult to distinguish from all nervous tissue in the pelvic region. A direct administration methodology to enable selective nerve highlighting for enhanced nerve SBR in a specific nerve structure has been developed herein. The direct administration methodology demonstrated equivalent nerve-specific contrast to systemic administration at optimal exposure times. However, the direct administration methodology provided a brighter fluorescent nerve signal, facilitating nerve-specific fluorescence imaging at video rate, which was not possible following systemic administration. Additionally, the direct administration methodology required a significantly lower fluorophore dose than systemic administration, that when scaled to a human dose falls within the microdosing range. Furthermore, a dual fluorophore tissue staining method was developed that alleviates fluorescence background signal from adipose tissue accumulation using a spectrally distinct adipose tissue specific fluorophore. These results validate the use of the direct administration methodology for specific nerve visualization with fluorescence image-guided surgery, which would improve vital nerve structure identification and visualization during nerve sparing radical prostatectomy. PMID:28255352

Direct Administration of Nerve-Specific Contrast to Improve Nerve Sparing Radical Prostatectomy.

PubMed

Barth, Connor W; Gibbs, Summer L

2017-01-01

Nerve damage remains a major morbidity following nerve sparing radical prostatectomy, significantly affecting quality of life post-surgery. Nerve-specific fluorescence guided surgery offers a potential solution by enhancing nerve visualization intraoperatively. However, the prostate is highly innervated and only the cavernous nerve structures require preservation to maintain continence and potency. Systemic administration of a nerve-specific fluorophore would lower nerve signal to background ratio (SBR) in vital nerve structures, making them difficult to distinguish from all nervous tissue in the pelvic region. A direct administration methodology to enable selective nerve highlighting for enhanced nerve SBR in a specific nerve structure has been developed herein. The direct administration methodology demonstrated equivalent nerve-specific contrast to systemic administration at optimal exposure times. However, the direct administration methodology provided a brighter fluorescent nerve signal, facilitating nerve-specific fluorescence imaging at video rate, which was not possible following systemic administration. Additionally, the direct administration methodology required a significantly lower fluorophore dose than systemic administration, that when scaled to a human dose falls within the microdosing range. Furthermore, a dual fluorophore tissue staining method was developed that alleviates fluorescence background signal from adipose tissue accumulation using a spectrally distinct adipose tissue specific fluorophore. These results validate the use of the direct administration methodology for specific nerve visualization with fluorescence image-guided surgery, which would improve vital nerve structure identification and visualization during nerve sparing radical prostatectomy.

Advanced information processing system: Inter-computer communication services

NASA Technical Reports Server (NTRS)

Burkhardt, Laura; Masotto, Tom; Sims, J. Terry; Whittredge, Roy; Alger, Linda S.

1991-01-01

The purpose is to document the functional requirements and detailed specifications for the Inter-Computer Communications Services (ICCS) of the Advanced Information Processing System (AIPS). An introductory section is provided to outline the overall architecture and functional requirements of the AIPS and to present an overview of the ICCS. An overview of the AIPS architecture as well as a brief description of the AIPS software is given. The guarantees of the ICCS are provided, and the ICCS is described as a seven-layered International Standards Organization (ISO) Model. The ICCS functional requirements, functional design, and detailed specifications as well as each layer of the ICCS are also described. A summary of results and suggestions for future work are presented.

Engineering Software Suite Validates System Design

NASA Technical Reports Server (NTRS)

2007-01-01

EDAptive Computing Inc.'s (ECI) EDAstar engineering software tool suite, created to capture and validate system design requirements, was significantly funded by NASA's Ames Research Center through five Small Business Innovation Research (SBIR) contracts. These programs specifically developed Syscape, used to capture executable specifications of multi-disciplinary systems, and VectorGen, used to automatically generate tests to ensure system implementations meet specifications. According to the company, the VectorGen tests considerably reduce the time and effort required to validate implementation of components, thereby ensuring their safe and reliable operation. EDASHIELD, an additional product offering from ECI, can be used to diagnose, predict, and correct errors after a system has been deployed using EDASTAR -created models. Initial commercialization for EDASTAR included application by a large prime contractor in a military setting, and customers include various branches within the U.S. Department of Defense, industry giants like the Lockheed Martin Corporation, Science Applications International Corporation, and Ball Aerospace and Technologies Corporation, as well as NASA's Langley and Glenn Research Centers

Siting Issues for Solar Thermal Power Plants with Small Community Applications

NASA Technical Reports Server (NTRS)

Holbeck, J. J.; Ireland, S. J.

1978-01-01

Technologies for solar thermal plants are being developed to provide energy alternatives for the future. Implementation of these plants requires consideration of siting issues as well as power system technology. While many conventional siting considerations are applicable, there is also a set of unique siting issues for solar thermal plants. Early experimental plants will have special siting considerations. The siting issues associated with small, dispersed solar thermal power plants in the 1 to 10 MWe power range for utility/small community applications are considered. Some specific requirements refer to the first 1 MWe engineering experiment for the Small Power Systems Applications (SPSA) Project. The siting issues themselves are discussed in three categories: (1) system resource requirements, (2) environmental effects on the system, and (3) potential impact of the plant on the environment. Within these categories, specific issues are discussed in a qualitative manner. Examples of limiting factors for some issues are taken from studies of other solar systems.

48 CFR 53.101 - Requirements for use of forms.

Code of Federal Regulations, 2010 CFR

2010-10-01

... matter applicable to each form is addressed. The specific location of each requirement is identified in... forms. 53.101 Section 53.101 Federal Acquisition Regulations System FEDERAL ACQUISITION REGULATION (CONTINUED) CLAUSES AND FORMS FORMS General 53.101 Requirements for use of forms. The requirements for use of...

Radiation Specifications for Fission Power Conversion Component Materials

NASA Technical Reports Server (NTRS)

Bowman, Cheryl L.; Shin, E. Eugene; Mireles, Omar R.; Radel, Ross F.; Qualls, A. Louis

2011-01-01

NASA has been supporting design studies and technology development that could provide power to an outpost on the moon, Mars, or an asteroid. One power-generation system that is independent of sunlight or power-storage limitations is a fission-based power plant. There is a wealth of terrestrial system heritage that can be transferred to the design and fabrication of a fission power system for space missions, but there are certain design aspects that require qualification. The radiation tolerance of the power conversion system requires scrutiny because the compact nature of a space power plant restricts the dose reduction methodologies compared to those used in terrestrial systems. An integrated research program has been conducted to establish the radiation tolerance of power conversion system-component materials. The radiation limit specifications proposed for a Fission Power System power convertor is 10 Mrad ionizing dose and 5 x 10(exp 14) neutron per square centimeter fluence for a convertor operating at 150 C. Specific component materials and their radiation tolerances are discussed. This assessment is for the power convertor hardware; electronic components are not covered here.

A Methodology for Writing High Quality Requirement Specifications and for Evaluating Existing Ones

NASA Technical Reports Server (NTRS)

Rosenberg, Linda; Hammer, Theodore

1999-01-01

Requirements development and management have always been critical in the implementation of software systems-engineers are unable to build what analysts can not define. It is generally accepted that the earlier in the life cycle potential risks are identified the easier it is to eliminate or manage the conditions that introduce that risk. Problems that are not found until testing are approximately 14 times more costly to fix than if the problem was found in the requirement phase. The requirements specification, as the first tangible representation of the capability to be produced, establishes the basis for all of the project's engineering management and assurance functions. If the quality of the requirements specification is poor it can give rise to risks in all areas of the project. Recently, automated tools have become available to support requirements management. The use of these tools not only provides support in the definition and tracing of requirements, but it also opens the door to effective use of metrics in characterizing and assessing the quality of the requirement specifications.

A Methodology for Writing High Quality Requirements Specification and Evaluating Existing Ones

NASA Technical Reports Server (NTRS)

Rosenberg, Linda; Hammer, Theodore

1999-01-01

Requirements development and management have always been critical in the implementation of software systems; engineers are unable to build what analysts can't define. It is generally accepted that the earlier in the life cycle potential risks are identified the easier it is to eliminate or manage the conditions that introduce that risk. Problems that are not found until testing are approximately 14 times more costly to fix than if the problem was found in the requirement phase. The requirements specification, as the first tangible representation of the capability to be produced, establishes the basis for all of the project's engineering management and assurance functions. If the quality of the requirements specification is poor it can give rise to risks in all areas of the project. Recently, automated tools have become available to support requirements management. The use of these tools not only provides support in the definition and tracing of requirements, but it also opens the door to effective use of metrics in characterizing and assessing the quality of the requirement specifications.

High Available COTS Based Computer for Space

NASA Astrophysics Data System (ADS)

Hartmann, J.; Magistrati, Giorgio

2015-09-01

The availability and reliability factors of a system are central requirements of a target application. From a simple fuel injection system used in cars up to a flight control system of an autonomous navigating spacecraft, each application defines its specific availability factor under the target application boundary conditions. Increasing quality requirements on data processing systems used in space flight applications calling for new architectures to fulfill the availability, reliability as well as the increase of the required data processing power. Contrary to the increased quality request simplification and use of COTS components to decrease costs while keeping the interface compatibility to currently used system standards are clear customer needs. Data processing system design is mostly dominated by strict fulfillment of the customer requirements and reuse of available computer systems were not always possible caused by obsolescence of EEE-Parts, insufficient IO capabilities or the fact that available data processing systems did not provide the required scalability and performance.

PIP-II Cryogenic System and the evolution of Superfluid Helium Cryogenic Plant Specifications

DOE Office of Scientific and Technical Information (OSTI.GOV)

Chakravarty, Anindya; Rane, Tejas; Klebaner, Arkadiy

2017-07-06

The PIP-II cryogenic system consists of a Superfluid Helium Cryogenic Plant (SHCP) and a Cryogenic Distribution System (CDS) connecting the SHCP to the Superconducting (SC) Linac consisting of 25 cryomodules. The dynamic heat load of the SC cavities for continuous wave (CW) as well as pulsed mode of operation has been listed out. The static heat loads of the cavities along with the CDS have also been discussed. Simulation study has been carried out to compute the supercritical helium (SHe) flow requirements for each cryomodule. Comparison between the flow requirements of the cryomodules for the CW and pulsed modes ofmore » operation have also been made. From the total computed heat load and pressure drop values in the CDS, the basic specifications for the SHCP, required for cooling the SC Linac, have evolved.« less

MASTER TELEVISION ANTENNA SYSTEM.

ERIC Educational Resources Information Center

Rhode Island State Dept. of Education, Providence.

SPECIFICATIONS FOR THE FURNISHING AND INSTALLATION OF TELEVISION MASTER ANTENNA SYSTEMS FOR SECONDARY AND ELEMENTARY SCHOOLS ARE GIVEN. CONTRACTOR REQUIREMENTS, EQUIPMENT, PERFORMANCE STANDARDS, AND FUNCTIONS ARE DESCRIBED. (MS)

[The requirements of standard and conditions of interchangeability of medical articles].

PubMed

Men'shikov, V V; Lukicheva, T I

2013-11-01

The article deals with possibility to apply specific approaches under evaluation of interchangeability of medical articles for laboratory analysis. The development of standardized analytical technologies of laboratory medicine and formulation of requirements of standards addressed to manufacturers of medical articles the clinically validated requirements are to be followed. These requirements include sensitivity and specificity of techniques, accuracy and precision of research results, stability of reagents' quality in particular conditions of their transportation and storage. The validity of requirements formulated in standards and addressed to manufacturers of medical articles can be proved using reference system, which includes master forms and standard samples, reference techniques and reference laboratories. This approach is supported by data of evaluation of testing systems for measurement of level of thyrotrophic hormone, thyroid hormones and glycated hemoglobin HB A1c. The versions of testing systems can be considered as interchangeable only in case of results corresponding to the results of reference technique and comparable with them. In case of absence of functioning reference system the possibilities of the Joined committee of traceability in laboratory medicine make it possible for manufacturers of reagent sets to apply the certified reference materials under development of manufacturing of sets for large listing of analytes.

Cost-effective technology advancement directions for electric propulsion transportation systems in earth-orbital missions

NASA Technical Reports Server (NTRS)

Regetz, J. D., Jr.; Terwilliger, C. H.

1979-01-01

The directions that electric propulsion technology should take to meet the primary propulsion requirements for earth-orbital missions in the most cost effective manner are determined. The mission set requirements, state of the art electric propulsion technology and the baseline system characterized by it, adequacy of the baseline system to meet the mission set requirements, cost optimum electric propulsion system characteristics for the mission set, and sensitivities of mission costs and design points to system level electric propulsion parameters are discussed. The impact on overall costs than specific masses or costs of propulsion and power systems is evaluated.

Manpower Systems Integration Factors for Frigate Design in the Turkish Navy

DTIC Science & Technology

2016-12-01

factors for frigate design in the Turkish Navy. The qualitative and quantitative analyses of the correlation between ship design specifications and...frigates. The correlation between the ship design characteristics and the manpower requirements is supported by the quantitative analysis. This... design in the Turkish Navy. The qualitative and quantitative analyses of the correlation between ship design specifications and manpower requirements

Slicing AADL Specifications for Model Checking

NASA Technical Reports Server (NTRS)

Odenbrett, Maximilian; Nguyen, Viet Yen; Noll, Thomas

2010-01-01

To combat the state-space explosion problem in model checking larger systems, abstraction techniques can be employed. Here, methods that operate on the system specification before constructing its state space are preferable to those that try to minimize the resulting transition system as they generally reduce peak memory requirements. We sketch a slicing algorithm for system specifications written in (a variant of) the Architecture Analysis and Design Language (AADL). Given a specification and a property to be verified, it automatically removes those parts of the specification that are irrelevant for model checking the property, thus reducing the size of the corresponding transition system. The applicability and effectiveness of our approach is demonstrated by analyzing the state-space reduction for an example, employing a translator from AADL to Promela, the input language of the SPIN model checker.

Report: EPA Could Improve Processes for Managing Contractor Systems and Reporting Incidents

EPA Pesticide Factsheets

Report #2007-P-00007, January 11, 2007. Although EPA had defined the specific requirements for contractor systems, EPA had not established procedures to ensure identification of all contractor systems.

Space Generic Open Avionics Architecture (SGOAA) reference model technical guide

NASA Technical Reports Server (NTRS)

Wray, Richard B.; Stovall, John R.

1993-01-01

This report presents a full description of the Space Generic Open Avionics Architecture (SGOAA). The SGOAA consists of a generic system architecture for the entities in spacecraft avionics, a generic processing architecture, and a six class model of interfaces in a hardware/software system. The purpose of the SGOAA is to provide an umbrella set of requirements for applying the generic architecture interface model to the design of specific avionics hardware/software systems. The SGOAA defines a generic set of system interface points to facilitate identification of critical interfaces and establishes the requirements for applying appropriate low level detailed implementation standards to those interface points. The generic core avionics system and processing architecture models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.

Facility Systems, Ground Support Systems, and Ground Support Equipment General Design Requirements

NASA Technical Reports Server (NTRS)

Thaxton, Eric A.

2014-01-01

KSC-DE-512-SM establishes overall requirements and best design practices to be used at the John F. Kennedy Space Center (KSC) for the development of ground systems (GS) in support of operations at launch, landing, and retrieval sites. These requirements apply to the design and development of hardware and software for ground support equipment (GSE), ground support systems (GSS), and facility ground support systems (F-GSS) used to support the KSC mission for transportation, receiving, handling, assembly, test, checkout, servicing, and launch of space vehicles and payloads and selected flight hardware items for retrieval. This standards manual supplements NASA-STD-5005 by including KSC-site-specific and local environment requirements. These requirements and practices are optional for equipment used at manufacturing, development, and test sites.

Orbiter data reduction complex data processing requirements for the OFT mission evaluation team (level C)

NASA Technical Reports Server (NTRS)

1979-01-01

This document addresses requirements for post-test data reduction in support of the Orbital Flight Tests (OFT) mission evaluation team, specifically those which are planned to be implemented in the ODRC (Orbiter Data Reduction Complex). Only those requirements which have been previously baselined by the Data Systems and Analysis Directorate configuration control board are included. This document serves as the control document between Institutional Data Systems Division and the Integration Division for OFT mission evaluation data processing requirements, and shall be the basis for detailed design of ODRC data processing systems.

78 FR 36369 - Heavy-Duty Engine and Vehicle, and Nonroad Technical Amendments

Federal Register 2010, 2011, 2012, 2013, 2014

2013-06-17

... reference to post-transmissions systems in the hybrid engine test requirements in 40 CFR part 1036 and 49... requirements for testing post-transmission hybrids using a vehicle test. The agencies anticipate that there... out in the regulation specify how to test post-transmission systems. Specifically, 40 CFR 1037.525, 40...

40 CFR 270.21 - Specific part B information requirements for landfills.

Code of Federal Regulations, 2010 CFR

2010-07-01

... surface water at any future time; (ii) The double liner and leak (leachate) detection, collection, and... exemption from the requirements for double liners and a leak detection, collection, and removal system or... information; (iii) If the leak detection system is located in a saturated zone, submit detailed plans and an...

Analysis of the Cost Effectiveness and Applicability of the Reliability Tasks of MIL-STD-785B.

DTIC Science & Technology

1985-09-01

M by designating specific requirements and objectives for each of the following organizations: HQ USAF/LE - Deputy Chief of Staff for Logistics IHQ ...Department of the Navy. Product Assurance Requirements Guide for Naval Ocean Systems Center Projects. NOSC TD 432. Naval Ocean Systems Center: San Diego

Cognitive Models of Scientific Work and Their Implications for the Design of Knowledge Delivery Systems.

ERIC Educational Resources Information Center

Mavor, A. S.; And Others

Part of a sustained program that has involved the design of personally tailored information systems responsive to the needs of scientists performing common research and teaching tasks, this project focuses on the procedural and content requirements for accomplishing need diagnosis and presents these requirements as specifications for an…

Countermeasure Evaluation and Validation Project (CEVP) Database Requirement Documentation

NASA Technical Reports Server (NTRS)

Shin, Sung Y.

2003-01-01

The initial focus of the project by the JSC laboratories will be to develop, test and implement a standardized complement of integrated physiological test (Integrated Testing Regimen, ITR) that will examine both system and intersystem function, and will be used to validate and certify candidate countermeasures. The ITR will consist of medical requirements (MRs) and non-MR core ITR tests, and countermeasure-specific testing. Non-MR and countermeasure-specific test data will be archived in a database specific to the CEVP. Development of a CEVP Database will be critical to documenting the progress of candidate countermeasures. The goal of this work is a fully functional software system that will integrate computer-based data collection and storage with secure, efficient, and practical distribution of that data over the Internet. This system will provide the foundation of a new level of interagency and international cooperation for scientific experimentation and research, providing intramural, international, and extramural collaboration through management and distribution of the CEVP data. The research performed this summer includes the first phase of the project. The first phase of the project is a requirements analysis. This analysis will identify the expected behavior of the system under normal conditions and abnormal conditions; that could affect the system's ability to produce this behavior; and the internal features in the system needed to reduce the risk of unexpected or unwanted behaviors. The second phase of this project have also performed in this summer. The second phase of project is the design of data entry screen and data retrieval screen for a working model of the Ground Data Database. The final report provided the requirements for the CEVP system in a variety of ways, so that both the development team and JSC technical management have a thorough understanding of how the system is expected to behave.

Feasibility study of an Integrated Program for Aerospace vehicle Design (IPAD). Volume 4: IPAD system design

NASA Technical Reports Server (NTRS)

Goldfarb, W.; Carpenter, L. C.; Redhed, D. D.; Hansen, S. D.; Anderson, L. O.; Kawaguchi, A. S.

1973-01-01

The computing system design of IPAD is described and the requirements which form the basis for the system design are discussed. The system is presented in terms of a functional design description and technical design specifications. The functional design specifications give the detailed description of the system design using top-down structured programming methodology. Human behavioral characteristics, which specify the system design at the user interface, security considerations, and standards for system design, implementation, and maintenance are also part of the technical design specifications. Detailed specifications of the two most common computing system types in use by the major aerospace companies which could support the IPAD system design are presented. The report of a study to investigate migration of IPAD software between the two candidate 3rd generation host computing systems and from these systems to a 4th generation system is included.

Multimedia-based decision support system for hazards recognition and abatement

DOEpatents

Czachowski, John B.; Zoldak, John T.

1998-01-01

A system for monitoring a site includes a portable data collection module used in the field to collect site specific data, and a processor module located at a central location. The data collection module displays choices of categories of findings, and then specific findings within each category. A selected specific finding is then displayed in report form with a citation to the specific code or statutory requirement, as well as a recommended course of action and an abatement date.

Remote sensor support requirements for planetary missions

NASA Technical Reports Server (NTRS)

Weddell, J. B.; Wheeler, A. E.

1971-01-01

The study approach, methods, results, and conclusions of remote sensor support requirements for planetary missions are summarized. Major efforts were made to (1) establish the scientific and engineering knowledge and observation requirements for planetary exploration in the 1975 to 1985 period; (2) define the state of the art and expected development of instrument systems appropriate for sensing planetary environments; (3) establish scaling laws relating performance and support requirements of candidate remote sensor systems; (4) establish fundamental remote sensor system capabilities, limitations, and support requirements during encounter and other dynamical conditions for specific missions; and (5) construct families of candidate remote sensors compatible with selected missions. It was recommended that these data be integrated with earlier results to enhance utility, and that more restrictions be placed on the system.

Propulsion element requirements using electrical power system unscheduled power

NASA Technical Reports Server (NTRS)

Zimmermann, Frank; Hodge, Kathy

1989-01-01

The suitability of using the electrical energy from the Space Station's Electrical Power System (EPS) during the periods of peak solar insolation which is currently not specifically allocated (unscheduled power) to produce propulsion propellants, gaseous hydrogen, and oxygen by electrolyzing water is investigated. Reboost propellant requirements are emphasized, but the results are more generally relevant because the balance of recurring propellant requirements are an order of magnitude smaller and the nonrecurring requirements are not significant on an average basis.

AMTD: update of engineering specifications derived from science requirements for future UVOIR space telescopes

NASA Astrophysics Data System (ADS)

Stahl, H. Philip; Postman, Marc; Mosier, Gary; Smith, W. Scott; Blaurock, Carl; Ha, Kong; Stark, Christopher C.

2014-08-01

The Advance Mirror Technology Development (AMTD) project is in Phase 2 of a multiyear effort, initiated in FY12, to mature by at least a half TRL step six critical technologies required to enable 4 meter or larger UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND provide a high-performance low-cost low-risk system. To give the science community options, we are pursuing multiple technology paths. A key task is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints. A key finding of this effort is that the science requires an 8 meter or larger aperture telescope.

AMTD: Update of Engineering Specifications Derived from Science Requirements for Future UVOIR Space Telescopes

NASA Technical Reports Server (NTRS)

Stahl, H. Philip; Postman, Marc; Mosier, Gary; Smith, W. Scott; Blaurock, Carl; Ha, Kong; Stark, Christopher C.

2014-01-01

The Advance Mirror Technology Development (AMTD) project is in Phase 2 of a multiyear effort, initiated in FY12, to mature by at least a half TRL step six critical technologies required to enable 4 meter or larger UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND provide a high-performance low-cost low-risk system. To give the science community options, we are pursuing multiple technology paths. A key task is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints. A key finding of this effort is that the science requires an 8 meter or larger aperture telescope

Proximal—distal pattern formation in Drosophila: cell autonomous requirement for Distal-less gene activity in limb development

PubMed Central

Cohen, Stephen M.; Jürgens, Gerd

1989-01-01

Limb development in the Drosophila embryo requires a pattern-forming system to organize positional information along the proximal–distal axis of the limb. This system must function in the context of the well characterized anterior–posterior and dorsal–ventral pattern-forming systems that are required to organize the body plan of the embryo. By genetic criteria the Distal-less gene appears to play a central role in limb development. Lack-of-function Distal-less mutations cause the deletion of a specific subset of embryonic peripheral sense organs that represent the evolutionary remnants of larval limbs. Distal-less activity is also required in the imaginal discs for the development of adult limbs. This requirement is cell autonomous and region specific within the developing limb primordium. Production of genetically mosaic imaginal discs, in which clones of cells lack Distal-less activity, indicates the existence of an organized proximal–distal positional information in very young imaginal disc primordia. We suggest that this graded positional information may depend on the activity of the Distal-less gene. Images PMID:16453891

Development Specification for the Feedwater Supply Assembly (FSA), FSA-431 with Integrated Auxiliary Feedwater Supply Assembly (AFSA), FSA-531

NASA Technical Reports Server (NTRS)

Anchondo, Ian; Campbell, Colin

2017-01-01

The FSA with Integrated Aux FSA Specification establishes the requirements for design, performance, and testing of the FSA-431/FSA-531 assembly in compliance with CTSD-ADV-780, Development Specification for the Advanced EMU (AEMU) Portable Life Support System (PLSS). This section contains the technical design and performance requirements for the integrated assembly of the Feedwater Supply Assembly and Auxiliary Feedwater Supply Assembly for the Advanced EVA Development Portable Life Support Subsystem (PLSS).

Plutonium Finishing Plant (PFP) HVAC System Component Index

DOE Office of Scientific and Technical Information (OSTI.GOV)

DICK, J.D.

2000-02-28

The Plutonium Finishing Plant (PFP) WAC System includes sub-systems 25A through 25K. Specific system boundaries and justifications are contained in HNF-SD-CP-SDD-005, ''Definition and Means of Maintaining the Ventilation System Confinement Portion of the PFP Safety Envelope.'' The procurement requirements associated with the system necessitates procurement of some system equipment as Commercial Grade Items in accordance with HNF-PRO-268, ''Control of Purchased Items and Services.'' This document lists safety class and safety significant components for the Heating Ventilation Air Conditioning and specifies the critical characteristics for Commercial Grade Items, as required by HNF-PRO-268 and HNF-PRO-1819. These are the minimum specifications that themore » equipment must meet in order to properly perform its safety function. There may be several manufacturers or models that meet the critical characteristics for any one item.« less

Design of agricultural product quality safety retrospective supervision system of Jiangsu province

NASA Astrophysics Data System (ADS)

Wang, Kun

2017-08-01

In store and supermarkets to consumers can trace back agricultural products through the electronic province card to query their origin, planting, processing, packaging, testing and other important information and found that the problems. Quality and safety issues can identify the responsibility of the problem. This paper designs a retroactive supervision system for the quality and safety of agricultural products in Jiangsu Province. Based on the analysis of agricultural production and business process, the goal of Jiangsu agricultural product quality safety traceability system construction is established, and the specific functional requirements and non-functioning requirements of the retroactive system are analyzed, and the target is specified for the specific construction of the retroactive system. The design of the quality and safety traceability system in Jiangsu province contains the design of the overall design, the trace code design and the system function module.

Knowledge-based approach to system integration

NASA Technical Reports Server (NTRS)

Blokland, W.; Krishnamurthy, C.; Biegl, C.; Sztipanovits, J.

1988-01-01

To solve complex problems one can often use the decomposition principle. However, a problem is seldom decomposable into completely independent subproblems. System integration deals with problem of resolving the interdependencies and the integration of the subsolutions. A natural method of decomposition is the hierarchical one. High-level specifications are broken down into lower level specifications until they can be transformed into solutions relatively easily. By automating the hierarchical decomposition and solution generation an integrated system is obtained in which the declaration of high level specifications is enough to solve the problem. We offer a knowledge-based approach to integrate the development and building of control systems. The process modeling is supported by using graphic editors. The user selects and connects icons that represent subprocesses and might refer to prewritten programs. The graphical editor assists the user in selecting parameters for each subprocess and allows the testing of a specific configuration. Next, from the definitions created by the graphical editor, the actual control program is built. Fault-diagnosis routines are generated automatically as well. Since the user is not required to write program code and knowledge about the process is present in the development system, the user is not required to have expertise in many fields.

NASA's Advanced Radioisotope Power Conversion Technology Development Status

NASA Technical Reports Server (NTRS)

Anderson, David J.; Sankovic, John; Wilt, David; Abelson, Robert D.; Fleurial, Jean-Pierre

2007-01-01

NASA's Advanced Radioisotope Power Systems (ARPS) project is developing the next generation of radioisotope power conversion technologies that will enable future missions that have requirements that cannot be met by either photovoltaic systems or by current radioisotope power systems (RPSs). Requirements of advanced RPSs include high efficiency and high specific power (watts/kilogram) in order to meet future mission requirements with less radioisotope fuel and lower mass so that these systems can meet requirements for a variety of future space applications, including continual operation surface missions, outer-planetary missions, and solar probe. These advances would enable a factor of 2 to 4 decrease in the amount of fuel required to generate electrical power. Advanced RPS development goals also include long-life, reliability, and scalability. This paper provides an update on the contractual efforts under the Radioisotope Power Conversion Technology (RPCT) NASA Research Announcement (NRA) for research and development of Stirling, thermoelectric, and thermophotovoltaic power conversion technologies. The paper summarizes the current RPCT NRA efforts with a brief description of the effort, a status and/or summary of the contractor's key accomplishments, a discussion of upcoming plans, and a discussion of relevant system-level benefits and implications. The paper also provides a general discussion of the benefits from the development of these advanced power conversion technologies and the eventual payoffs to future missions (discussing system benefits due to overall improvements in efficiency, specific power, etc.).

Content-Specific Auditing of a Large Scale Anatomy Ontology

PubMed Central

Kalet, Ira J.; Mejino, Jose L. V.; Wang, Vania; Whipple, Mark; Brinkley, James F.

2009-01-01

Biomedical ontologies are envisioned to be useable in a range of research and clinical applications. The requirements for such uses include formal consistency, adequacy of coverage, and possibly other domain specific constraints. In this report we describe a case study that illustrates how application specific requirements may be used to identify modeling problems as well as data entry errors in ontology building and evolution. We have begun a project to use the UW Foundational Model of Anatomy (FMA) in a clinical application in radiation therapy planning. This application focuses mainly (but not exclusively) on the representation of the lymphatic system in the FMA, in order to predict the spread of tumor cells to regional metastatic sites. This application requires that the downstream relations associated with lymphatic system components must only be to other lymphatic chains or vessels, must be at the appropriate level of granularity, and that every path through the lymphatic system must terminate at one of the two well known trunks of the lymphatic system. It is possible through a programmable query interface to the FMA to write small programs that systematically audit the FMA for compliance with these constraints. We report on the design of some of these programs, and the results we obtained by applying them to the lymphatic system. The algorithms and approach are generalizable to other network organ systems in the FMA such as arteries and veins. In addition to illustrating exact constraint checking methods, this work illustrates how the details of an application may reflect back a requirement to revise the design of the ontology itself. PMID:19248842

The implementation and use of Ada on distributed systems with high reliability requirements

NASA Technical Reports Server (NTRS)

Knight, J. C.

1987-01-01

A preliminary analysis of the Ada implementation of the Advanced Transport Operating System (ATOPS), an experimental computer control system developed at NASA Langley for a modified Boeing 737 aircraft, is presented. The criteria that was determined for the evaluation of this approach is described. A preliminary version of the requirements for the ATOPS is contained. This requirements specification is not a formal document, but rather a description of certain aspects of the ATOPS system at a level of detail that best suits the needs of the research. The survey of backward error recovery techniques is also presented.

Requirements for the Development of Bacillus Anthracis Spore Reference Materials Used to Test Detection Systems

PubMed Central

Almeida, Jamie L.; Wang, Lili; Morrow, Jayne B.; Cole, Kenneth D.

2006-01-01

Bacillus anthracis spores have been used as biological weapons and the possibility of their further use requires surveillance systems that can accurately and reliably detect their presence in the environment. These systems must collect samples from a variety of matrices, process the samples, and detect the spores. The processing of the sample may include removal of inhibitors, concentration of the target, and extraction of the target in a form suitable for detection. Suitable reference materials will allow the testing of each of these steps to determine the sensitivity and specificity of the detection systems. The development of uniform and well-characterized reference materials will allow the comparison of different devices and technologies as well as assure the continued performance of detection systems. This paper discusses the special requirements of reference materials for Bacillus anthracis spores that could be used for testing detection systems. The detection of Bacillus anthracis spores is based on recognition of specific characteristics (markers) on either the spore surface or in the nucleic acids (DNA). We have reviewed the specific markers and their relevance to characterization of reference materials. We have also included the approach for the characterization of candidate reference materials that we are developing at the NIST laboratories. Additional applications of spore reference materials would include testing sporicidal treatments, techniques for sampling the environment, and remediation of spore-contaminated environments. PMID:27274929

Requirements for AMLCDs in U.S. military applications

NASA Astrophysics Data System (ADS)

Hopper, Darrel G.; Desjardins, Daniel D.

1995-06-01

Flat panel displays are fast becoming a significant source of more defense for less money. Military instruments have begun to use color active matrix liquid crystal displays (AMLCDs). This is the beginning of a significant transition from electromechanical, CRT. dichroic LCD, and electroluminescent display designs to the AMLCD designs. We have the opportunity with this new technology to establish common products capable of meeting user requirements for sunlight-readable, color and grayscale capable, high-sharpness high-pixel count, flat panel displays for military applications. The Wright Laboratory is leading the development of recommended best practice, draft guidance standard, and performance specifications for this new generation, the flat panel cockpit display generation, of display modules based on requirements for U.S. military aircraft and ground combat human system interfaces. These requirements are similar in many regards to those in both the civil aviation and automotive industries; accordingly, commonality with these civil applications is incorporated where possible, against the requirements for military combat applications. The performance requirement may be achieved by two approaches: militarization of displays made to low requirements of a large volume civil products manufacturer like Sharp or integration of displays made to high requirements by a niche market commercial vendor, like Optical Imaging Systems, Litton Systems Limited, ImageQuest Inc., and Planar Advanced Inc. teamed with Xerox PARC and Standish Industries. [Note that the niche market companies listed are commercial off-the shelf vendors, albeit for high requirement low volume customers.] Given that the performance specifications can be met for a particular military product by either approach, the choice is based on life cycle cost and a thin analysis based on initial costs alone is not acceptable as it ignores the fact that military product life cycles and procurements are 20-60 years compared to 1.5 years for civil products. Thus far there is no convincing evidence that the large volume commercial product approach for combat systems will meet the combat performance specification or be cheaper from a life cycle cost perspective. National and economic security requirements require some military/avionic-grade AMLCD production domestically (i.e. in the U.S. and/or Canada). Examples of AMLCD demand and performance requirements in U.S. military systems are provided.

Architectural Implementation of NASA Space Telecommunications Radio System Specification

NASA Technical Reports Server (NTRS)

Peters, Kenneth J.; Lux, James P.; Lang, Minh; Duncan, Courtney B.

2012-01-01

This software demonstrates a working implementation of the NASA STRS (Space Telecommunications Radio System) architecture specification. This is a developing specification of software architecture and required interfaces to provide commonality among future NASA and commercial software-defined radios for space, and allow for easier mixing of software and hardware from different vendors. It provides required functions, and supports interaction with STRS-compliant simple test plug-ins ("waveforms"). All of it is programmed in "plain C," except where necessary to interact with C++ plug-ins. It offers a small footprint, suitable for use in JPL radio hardware. Future NASA work is expected to develop into fully capable software-defined radios for use on the space station, other space vehicles, and interplanetary probes.

Advanced information processing system: Local system services

NASA Technical Reports Server (NTRS)

Burkhardt, Laura; Alger, Linda; Whittredge, Roy; Stasiowski, Peter

1989-01-01

The Advanced Information Processing System (AIPS) is a multi-computer architecture composed of hardware and software building blocks that can be configured to meet a broad range of application requirements. The hardware building blocks are fault-tolerant, general-purpose computers, fault-and damage-tolerant networks (both computer and input/output), and interfaces between the networks and the computers. The software building blocks are the major software functions: local system services, input/output, system services, inter-computer system services, and the system manager. The foundation of the local system services is an operating system with the functions required for a traditional real-time multi-tasking computer, such as task scheduling, inter-task communication, memory management, interrupt handling, and time maintenance. Resting on this foundation are the redundancy management functions necessary in a redundant computer and the status reporting functions required for an operator interface. The functional requirements, functional design and detailed specifications for all the local system services are documented.

48 CFR 301.607-71 - FAC-P/PM levels and requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... GENERAL HHS ACQUISITION REGULATION SYSTEM Career Development, Contracting Authority, and Responsibilities..., systems engineering, test and evaluation, contracting, and business. (6) Specific core competencies also...

Incubator Display Software Cost Reduction Toolset Software Requirements Specification

NASA Technical Reports Server (NTRS)

Moran, Susanne; Jeffords, Ralph

2005-01-01

The Incubator Display Software Requirements Specification was initially developed by Intrinsyx Technologies Corporation (Intrinsyx) under subcontract to Lockheed Martin, Contract Number NAS2-02090, for the National Aeronautics and Space Administration (NASA) Ames Research Center (ARC) Space Station Biological Research Project (SSBRP). The Incubator Display is a User Payload Application (UPA) used to control an Incubator subrack payload for the SSBRP. The Incubator Display functions on-orbit as part of the subrack payload laptop, on the ground as part of the Communication and Data System (CDS) ground control system, and also as part of the crew training environment.

KSC Space Station Operations Language (SSOL)

NASA Technical Reports Server (NTRS)

1985-01-01

The Space Station Operations Language (SSOL) will serve a large community of diverse users dealing with the integration and checkout of Space Station modules. Kennedy Space Center's plan to achieve Level A specification of the SSOL system, encompassing both its language and its automated support environment, is presented in the format of a briefing. The SSOL concept is a collection of fundamental elements that span languages, operating systems, software development, software tools and several user classes. The approach outlines a thorough process that combines the benefits of rapid prototyping with a coordinated requirements gathering effort, yielding a Level A specification of the SSOL requirements.

The High Power Electric Propulsion (HiPEP) Ion Thruster

NASA Technical Reports Server (NTRS)

Foster, John E.; Haag, Tom; Patterson, Michael; Williams, George J., Jr.; Sovey, James S.; Carpenter, Christian; Kamhawi, Hani; Malone, Shane; Elliot, Fred

2004-01-01

Practical implementation of the proposed Jupiter Icy Moon Orbiter (JIMO) mission, which would require a total delta V of approximately 38 km/s, will require the development of a high power, high specific impulse propulsion system. Initial analyses show that high power gridded ion thrusters could satisfy JIMO mission requirements. A NASA GRC-led team is developing a large area, high specific impulse, nominally 25 kW ion thruster to satisfy both the performance and the lifetime requirements for this proposed mission. The design philosophy and development status as well as a thruster performance assessment are presented.

Effective specific impulse of external nuclear pulse propulsion systems

NASA Technical Reports Server (NTRS)

Reynolds, T. W.

1972-01-01

An investigation of a simple self-similar flow model for an external nuclear pulse propulsion system indicates that to achieve the high effective specific impulse of such a system three principal factors are required. The are (1) attaining pulses of optimum energy, (2) attaining good propellant collimation, and (3) using an ablative material for the pusher surface which has high absorptivity for radiant energy at the propellant stagnation temperature.

Assessing Weapon System Acquisition Cycle Times: Setting Program Schedules

DTIC Science & Technology

2015-06-01

additional research, focused as follows: 1 . Acquisition schedule development: How are schedules for acquisition programs actually set and how are they...the germinating requirements documents specific to systems reviewed. A clear statement was found for only one system (Air and Missile Defense Radar...AMDR) when specific threat capabilities were projected to be operational. • Program schedule setting varies in rigor: 1 Up to the interim version of

Restricted Authentication and Encryption for Cyber-physical Systems

DOE Office of Scientific and Technical Information (OSTI.GOV)

Kirkpatrick, Michael S; Bertino, Elisa; Sheldon, Frederick T

2009-01-01

Cyber-physical systems (CPS) are characterized by the close linkage of computational resources and physical devices. These systems can be deployed in a number of critical infrastructure settings. As a result, the security requirements of CPS are different than traditional computing architectures. For example, critical functions must be identified and isolated from interference by other functions. Similarly, lightweight schemes may be required, as CPS can include devices with limited computing power. One approach that offers promise for CPS security is the use of lightweight, hardware-based authentication. Specifically, we consider the use of Physically Unclonable Functions (PUFs) to bind an access requestmore » to specific hardware with device-specific keys. PUFs are implemented in hardware, such as SRAM, and can be used to uniquely identify the device. This technology could be used in CPS to ensure location-based access control and encryption, both of which would be desirable for CPS implementations.« less

Formal Specifications for an Electrical Power Grid System Stability and Reliability

DTIC Science & Technology

2015-09-01

expressed in this thesis are those of the author and do not reflect the official policy or position of the Department of Defense or the U.S. Government. IRB...analyze the power grid system requirements and express the critical runtime behavior using first-order logic. First, we identify observable...Verification System, and Type systems to name a few [5]. Theorem proving’s specification dimension is dependent on the expressive power of the formal

Semantic technologies in a decision support system

NASA Astrophysics Data System (ADS)

Wasielewska, K.; Ganzha, M.; Paprzycki, M.; Bǎdicǎ, C.; Ivanovic, M.; Lirkov, I.

2015-10-01

The aim of our work is to design a decision support system based on ontological representation of domain(s) and semantic technologies. Specifically, we consider the case when Grid / Cloud user describes his/her requirements regarding a "resource" as a class expression from an ontology, while the instances of (the same) ontology represent available resources. The goal is to help the user to find the best option with respect to his/her requirements, while remembering that user's knowledge may be "limited." In this context, we discuss multiple approaches based on semantic data processing, which involve different "forms" of user interaction with the system. Specifically, we consider: (a) ontological matchmaking based on SPARQL queries and class expression, (b) graph-based semantic closeness of instances representing user requirements (constructed from the class expression) and available resources, and (c) multicriterial analysis based on the AHP method, which utilizes expert domain knowledge (also ontologically represented).

Checkout systems: Summary report for the universal control and display console

NASA Technical Reports Server (NTRS)

1971-01-01

The development of a unified test equipment checkout concept based on a universal control and display console system is discussed. The checkout requirements are analyzed for the shuttle and space station. Capability, size, utilization requirements and specifications of the ground checkout system are made on the basis of engineering trade-off studies. Recommendations related to the attainment of overall unified test equipment conceptual goals and objectives are submitted.

An Optimization-Based Approach to Determine System Requirements Under Multiple-Domain Specific Uncertainties

DTIC Science & Technology

2016-04-30

determining the optimal design requirements of a new system, which will operate along with other existing systems to provide a set of overarching...passenger airline transportation (Mane et al., 2007; Govindaraju et al., 2015). Uncertainty in Fleet Operations The uncertainty associated with the...demand can provide the basis for a commercial passenger airline problem. The operations of the commercial air travel industry differ from military

48 CFR 432.770 - USDA specific funding limitations.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 48 Federal Acquisition Regulations System 4 2010-10-01 2010-10-01 false USDA specific funding... CONTRACTING REQUIREMENTS CONTRACT FINANCING Contract Funding 432.770 USDA specific funding limitations. (a) The USDA is authorized to subscribe for newspapers as may be necessary to carry out its authorized...

48 CFR 432.770 - USDA specific funding limitations.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 4 2011-10-01 2011-10-01 false USDA specific funding... CONTRACTING REQUIREMENTS CONTRACT FINANCING Contract Funding 432.770 USDA specific funding limitations. (a) The USDA is authorized to subscribe for newspapers as may be necessary to carry out its authorized...

48 CFR 432.770 - USDA specific funding limitations.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 48 Federal Acquisition Regulations System 4 2012-10-01 2012-10-01 false USDA specific funding... CONTRACTING REQUIREMENTS CONTRACT FINANCING Contract Funding 432.770 USDA specific funding limitations. (a) The USDA is authorized to subscribe for newspapers as may be necessary to carry out its authorized...

48 CFR 432.770 - USDA specific funding limitations.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 4 2014-10-01 2014-10-01 false USDA specific funding... CONTRACTING REQUIREMENTS CONTRACT FINANCING Contract Funding 432.770 USDA specific funding limitations. (a) The USDA is authorized to subscribe for newspapers as may be necessary to carry out its authorized...

48 CFR 432.770 - USDA specific funding limitations.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 4 2013-10-01 2013-10-01 false USDA specific funding... CONTRACTING REQUIREMENTS CONTRACT FINANCING Contract Funding 432.770 USDA specific funding limitations. (a) The USDA is authorized to subscribe for newspapers as may be necessary to carry out its authorized...

Point source detection in infrared astronomical surveys

NASA Technical Reports Server (NTRS)

Pelzmann, R. F., Jr.

1977-01-01

Data processing techniques useful for infrared astronomy data analysis systems are reported. This investigation is restricted to consideration of data from space-based telescope systems operating as survey instruments. In this report the theoretical background for specific point-source detection schemes is completed, and the development of specific algorithms and software for the broad range of requirements is begun.

Data Management System (DMS) Evolution Analysis

NASA Technical Reports Server (NTRS)

Douglas, Katherine

1990-01-01

The all encompassing goal for the Data Management System (DMS) Evolution Analysis task is to develop an advocacy for ensuring that growth and technology insertion issues are properly and adequately addressed during DMS requirements specification, design, and development. The most efficient methods of addressing those issues are via planned and graceful evolution, technology transparency, and system growth margins. It is necessary that provisions, such as those previously mentioned, are made to accommodate advanced missions requirements (e.g., Human Space Exploration Programs) in addition to evolving Space Station Freedom operations and user requirements .

Fixed Wing Project: Technologies for Advanced Air Transports

NASA Technical Reports Server (NTRS)

Del Rosario, Ruben; Koudelka, John M.; Wahls, Richard A.; Madavan, Nateri

2014-01-01

The NASA Fundamental Aeronautics Fixed Wing (FW) Project addresses the comprehensive challenge of enabling revolutionary energy efficiency improvements in subsonic transport aircraft combined with dramatic reductions in harmful emissions and perceived noise to facilitate sustained growth of the air transportation system. Advanced technologies and the development of unconventional aircraft systems offer the potential to achieve these improvements. Multidisciplinary advances are required in aerodynamic efficiency to reduce drag, structural efficiency to reduce aircraft empty weight, and propulsive and thermal efficiency to reduce thrust-specific energy consumption (TSEC) for overall system benefit. Additionally, advances are required to reduce perceived noise without adversely affecting drag, weight, or TSEC, and to reduce harmful emissions without adversely affecting energy efficiency or noise.The presentation will highlight the Fixed Wing project vision of revolutionary systems and technologies needed to achieve these challenging goals. Specifically, the primary focus of the FW Project is on the N+3 generation; that is, vehicles that are three generations beyond the current state of the art, requiring mature technology solutions in the 2025-30 timeframe.

Software as a service approach to sensor simulation software deployment

NASA Astrophysics Data System (ADS)

Webster, Steven; Miller, Gordon; Mayott, Gregory

2012-05-01

Traditionally, military simulation has been problem domain specific. Executing an exercise currently requires multiple simulation software providers to specialize, deploy, and configure their respective implementations, integrate the collection of software to achieve a specific system behavior, and then execute for the purpose at hand. This approach leads to rigid system integrations which require simulation expertise for each deployment due to changes in location, hardware, and software. Our alternative is Software as a Service (SaaS) predicated on the virtualization of Night Vision Electronic Sensors (NVESD) sensor simulations as an exemplary case. Management middleware elements layer self provisioning, configuration, and integration services onto the virtualized sensors to present a system of services at run time. Given an Infrastructure as a Service (IaaS) environment, enabled and managed system of simulations yields a durable SaaS delivery without requiring user simulation expertise. Persistent SaaS simulations would provide on demand availability to connected users, decrease integration costs and timelines, and benefit the domain community from immediate deployment of lessons learned.

Flight Control System Reliability and Maintainability Investigations

DTIC Science & Technology

1975-03-01

the left forward horn of the swash - plate . Pilot’s Cyclic Control Stick The conventional type control stick, mounted in the ... the requirement? 3. Acceptability - Is the effort/cost worth the gain in R&M7 These tests were applied to the flight control system speci- fication...quantitative R&M requirements on the specifications in Figure 1. Standard Components

Requirements and specifications of the space telescope for scientific operations

NASA Technical Reports Server (NTRS)

West, D. K.

1976-01-01

Requirements for the scientific operations of the Space Telescope and the Science Institute are used to develop operational interfaces between user scientists and the NASA ground system. General data systems are defined for observatory scheduling, daily science planning, and science data management. Hardware, software, manpower, and space are specified for several science institute locations and support options.

Elicitation of Unstated Needs

DTIC Science & Technology

2014-09-17

what you can about requirements for a next generation laptop for the Home User that • attracts new customers • leverages existing customer loyalty ...Training © 2014 Carnegie Mellon University Traditional Requirements Elicitation Approaches Interviews of customers /users to elicit problems and usage...needs Inventory of problem reporting systems harboring customer complaints Solicitation of specification from customers /users to build a system

Transit safety retrofit package development : architecture and design specifications.

DOT National Transportation Integrated Search

2014-05-01

The Architecture and Design Specifications capture the TRP system architecture and design that fulfills the technical objectives stated in the TRP requirements document. The document begins with an architectural overview that identifies and describes...

46 CFR 62.35-15 - Fire safety.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Requirements for Specific Types of Automated Vital Systems § 62.35-15 Fire safety. (a) All required fire pump remote control locations must include the controls necessary to charge the firemain and— (1) A firemain...

46 CFR 62.35-15 - Fire safety.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Requirements for Specific Types of Automated Vital Systems § 62.35-15 Fire safety. (a) All required fire pump remote control locations must include the controls necessary to charge the firemain and— (1) A firemain...

46 CFR 62.35-15 - Fire safety.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Requirements for Specific Types of Automated Vital Systems § 62.35-15 Fire safety. (a) All required fire pump remote control locations must include the controls necessary to charge the firemain and— (1) A firemain...

Review of Special Standards in Quality Management Systems Audits in Automotive Production

NASA Astrophysics Data System (ADS)

Šurinová, Yulia

2013-12-01

Quality management systems (QMS) in automotive industry generally have several differences in comparison with other industrial branches. Different customers have their own specific requirements, including requirements for quality audits. Audits are one of the coretools of quality management to make the PDCA (Plan - Do - Check - Act) cycle work. As a matter of fact, compliance with ISO/TS 16949:2009 requirements is a condition for supplying the automotive industry. However, there are some standards which co-exist together with the ISO 9001 based management systems and technical specification for QMS in automotive ISO/TS16949. Which are those specific standards in automotive industry and what standard to use and why - those are the questions to be answered in this paper. The aim of the paper is to review what standards are used for audits implementation in automotive industry in the Slovak Republic, and why the organizations keep following those "extra" standards even if certification for ISO/TS 16949 is required by all the car makers. The paper is structured as follows: after short introduction to the topic and related terms, presented is our methodology. . In the third section, the achieved results are discussed. And finally, the principal findings of the paper, limitations and conclusions are presented.

Automatic specification of reliability models for fault-tolerant computers

NASA Technical Reports Server (NTRS)

Liceaga, Carlos A.; Siewiorek, Daniel P.

1993-01-01

The calculation of reliability measures using Markov models is required for life-critical processor-memory-switch structures that have standby redundancy or that are subject to transient or intermittent faults or repair. The task of specifying these models is tedious and prone to human error because of the large number of states and transitions required in any reasonable system. Therefore, model specification is a major analysis bottleneck, and model verification is a major validation problem. The general unfamiliarity of computer architects with Markov modeling techniques further increases the necessity of automating the model specification. Automation requires a general system description language (SDL). For practicality, this SDL should also provide a high level of abstraction and be easy to learn and use. The first attempt to define and implement an SDL with those characteristics is presented. A program named Automated Reliability Modeling (ARM) was constructed as a research vehicle. The ARM program uses a graphical interface as its SDL, and it outputs a Markov reliability model specification formulated for direct use by programs that generate and evaluate the model.

Global Hawk Systems Engineering. Case Study

DTIC Science & Technology

2010-01-01

Management Core System ( TBMCS ) (complex software development) • F-111 Fighter (joint program with significant involvement by the Office of the...Software Requirements Specification TACC Tailored Airworthiness Certification Criteria TBMCS Theater Battle Management Core System TEMP Test and

Modular biowaste monitoring system conceptual design

NASA Technical Reports Server (NTRS)

Fogal, G. L.

1974-01-01

The objective of the study was to define requirements and generate a conceptual design for a Modular Biowaste Monitoring System for specifically supporting shuttle life science experimental and diagnostic programs.

The Formal Semantics of PVS

NASA Technical Reports Server (NTRS)

Owre, Sam; Shankar, Natarajan

1999-01-01

A specification language is a medium for expressing what is computed rather than how it is computed. Specification languages share some features with programming languages but are also different in several important ways. For our purpose, a specification language is a logic within which the behavior of computational systems can be formalized. Although a specification can be used to simulate the behavior of such systems, we mainly use specifications to state and prove system properties with mechanical assistance. We present the formal semantics of the specification language of SRI's Prototype Verification System (PVS). This specification language is based on the simply typed lambda calculus. The novelty in PVS is that it contains very expressive language features whose static analysis (e.g., typechecking) requires the assistance of a theorem prover. The formal semantics illuminates several of the design considerations underlying PVS, the interaction between theorem proving and typechecking.

Energy saving in data processing and communication systems.

PubMed

Iazeolla, Giuseppe; Pieroni, Alessandra

2014-01-01

The power management of ICT systems, that is, data processing (Dp) and telecommunication (Tlc) systems, is becoming a relevant problem in economical terms. Dp systems totalize millions of servers and associated subsystems (processors, monitors, storage devices, etc.) all over the world that need to be electrically powered. Dp systems are also used in the government of Tlc systems, which, besides requiring Dp electrical power, also require Tlc-specific power, both for mobile networks (with their cell-phone towers and associated subsystems: base stations, subscriber stations, switching nodes, etc.) and for wired networks (with their routers, gateways, switches, etc.). ICT research is thus expected to investigate into methods to reduce Dp- and Tlc-specific power consumption. However, saving power may turn into waste of performance, in other words, into waste of ICT quality of service (QoS). This paper investigates the Dp and Tlc power management policies that look at compromises between power saving and QoS.

Network, system, and status software enhancements for the autonomously managed electrical power system breadboard. Volume 2: Protocol specification

NASA Technical Reports Server (NTRS)

Mckee, James W.

1990-01-01

This volume (2 of 4) contains the specification, structured flow charts, and code listing for the protocol. The purpose of an autonomous power system on a spacecraft is to relieve humans from having to continuously monitor and control the generation, storage, and distribution of power in the craft. This implies that algorithms will have been developed to monitor and control the power system. The power system will contain computers on which the algorithms run. There should be one control computer system that makes the high level decisions and sends commands to and receive data from the other distributed computers. This will require a communications network and an efficient protocol by which the computers will communicate. One of the major requirements on the protocol is that it be real time because of the need to control the power elements.

Computer program for design and performance analysis of navigation-aid power systems. Program documentation. Volume 1: Software requirements document

NASA Technical Reports Server (NTRS)

Goltz, G.; Kaiser, L. M.; Weiner, H.

1977-01-01

A computer program has been developed for designing and analyzing the performance of solar array/battery power systems for the U.S. Coast Guard Navigational Aids. This program is called the Design Synthesis/Performance Analysis (DSPA) Computer Program. The basic function of the Design Synthesis portion of the DSPA program is to evaluate functional and economic criteria to provide specifications for viable solar array/battery power systems. The basic function of the Performance Analysis portion of the DSPA program is to simulate the operation of solar array/battery power systems under specific loads and environmental conditions. This document establishes the software requirements for the DSPA computer program, discusses the processing that occurs within the program, and defines the necessary interfaces for operation.

AN ULTRAVIOLET-VISIBLE SPECTROPHOTOMETER AUTOMATION SYSTEM. PART I: FUNCTIONAL SPECIFICATIONS

EPA Science Inventory

This document contains the project definition, the functional requirements, and the functional design for a proposed computer automation system for scanning spectrophotometers. The system will be implemented on a Data General computer using the BASIC language. The system is a rea...

Conceptual design of ACB-CP for ITER cryogenic system

NASA Astrophysics Data System (ADS)

Jiang, Yongcheng; Xiong, Lianyou; Peng, Nan; Tang, Jiancheng; Liu, Liqiang; Zhang, Liang

2012-06-01

ACB-CP (Auxiliary Cold Box for Cryopumps) is used to supply the cryopumps system with necessary cryogen in ITER (International Thermonuclear Experimental Reactor) cryogenic distribution system. The conceptual design of ACB-CP contains thermo-hydraulic analysis, 3D structure design and strength checking. Through the thermohydraulic analysis, the main specifications of process valves, pressure safety valves, pipes, heat exchangers can be decided. During the 3D structure design process, vacuum requirement, adiabatic requirement, assembly constraints and maintenance requirement have been considered to arrange the pipes, valves and other components. The strength checking has been performed to crosscheck if the 3D design meets the strength requirements for the ACB-CP.

System Definition Document

DOT National Transportation Integrated Search

1996-06-12

The Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center : (C-TIC) System Definition Document describes the C-TIC concept and defines the : high level processes and dataflows. The Requirements Specification together : with the Inte...

49 CFR 236.1049 - Training specific to roadway workers.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 49 Transportation 4 2011-10-01 2011-10-01 false Training specific to roadway workers. 236.1049... Train Control Systems § 236.1049 Training specific to roadway workers. (a) Roadway worker training. Training required under this subpart for a roadway worker shall be integrated into the program of...

49 CFR 236.929 - Training specific to roadway workers.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 49 Transportation 4 2011-10-01 2011-10-01 false Training specific to roadway workers. 236.929... for Processor-Based Signal and Train Control Systems § 236.929 Training specific to roadway workers. (a) How is training for roadway workers to be coordinated with part 214? Training required under this...

49 CFR 179.101-1 - Individual specification requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... HAZARDOUS MATERIALS SAFETY ADMINISTRATION, DEPARTMENT OF TRANSPORTATION (CONTINUED) SPECIFICATIONS FOR TANK CARS Specifications for Pressure Tank Car Tanks (Classes DOT-105, 109, 112, 114 and 120) § 179.101-1... than 1/2 inch. 4 Tank cars not equipped with a thermal protection or an insulation system used for the...

49 CFR 179.101-1 - Individual specification requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... HAZARDOUS MATERIALS SAFETY ADMINISTRATION, DEPARTMENT OF TRANSPORTATION (CONTINUED) SPECIFICATIONS FOR TANK CARS Specifications for Pressure Tank Car Tanks (Classes DOT-105, 109, 112, 114 and 120) § 179.101-1... than 1/2 inch. 4 Tank cars not equipped with a thermal protection or an insulation system used for the...

49 CFR 179.101-1 - Individual specification requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... HAZARDOUS MATERIALS SAFETY ADMINISTRATION, DEPARTMENT OF TRANSPORTATION (CONTINUED) SPECIFICATIONS FOR TANK CARS Specifications for Pressure Tank Car Tanks (Classes DOT-105, 109, 112, 114 and 120) § 179.101-1... than 1/2 inch. 4 Tank cars not equipped with a thermal protection or an insulation system used for the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2011 CFR

2011-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

NASA Systems Engineering Handbook

NASA Technical Reports Server (NTRS)

2007-01-01

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Hierarchical specification of the SIFT fault tolerant flight control system

NASA Technical Reports Server (NTRS)

Melliar-Smith, P. M.; Schwartz, R. L.

1981-01-01

The specification and mechanical verification of the Software Implemented Fault Tolerance (SIFT) flight control system is described. The methodology employed in the verification effort is discussed, and a description of the hierarchical models of the SIFT system is given. To meet the objective of NASA for the reliability of safety critical flight control systems, the SIFT computer must achieve a reliability well beyond the levels at which reliability can be actually measured. The methodology employed to demonstrate rigorously that the SIFT computer meets as reliability requirements is described. The hierarchy of design specifications from very abstract descriptions of system function down to the actual implementation is explained. The most abstract design specifications can be used to verify that the system functions correctly and with the desired reliability since almost all details of the realization were abstracted out. A succession of lower level models refine these specifications to the level of the actual implementation, and can be used to demonstrate that the implementation has the properties claimed of the abstract design specifications.

Data Specifications for the Landsat Data Continuity Mission

USGS Publications Warehouse

Irons, J.R.; Speciale, N.J.; Douglas, McCuistion J.; Masek, J.G.; Markham, B.L.; Storey, James C.; Lencioni, D.E.; Ryan, R.E.

2003-01-01

The National Aeronautics and Space Administration (NASA) plans to procure data from a privately-owned and commercially-operated remote sensing system for the next Landsat mission, the Landsat Data Continuity Mission (LDCM). Data requirements are documented in an LDCM Data Specification. The specifications require delivery of data covering 250 Landsat scenes on a daily basis. The data are to be acquired in a manner that affords seasonal coverage of the global land mass. Data are required for the heritage reflective Thematic Mapper (TM) spectral bands plus two new bands, a blue band for coastal zone observations and a short wave infrared band for cirrus cloud detection. The specifications do not require thermal data, representing a departure from the TM heritage. The specification also requires data providing a 30 m ground sample distance for each of the spectral bands with the exception of the new cirrus cloud band at 120 m. An absolute uncertainty of 5 percent or less is required for radiometrically corrected LDCM data and the commercial operator is required to deliver data that can be registered to a cartographic projection with an uncertainty of 65 m or less. Procuring data from a commercial operator represents a new approach for the 30-year-old Landsat Program. The LDCM Data Specification will ensure that the procured data provides continuity of the Landsat data stream and advances the mission.

Automated Ground Umbilical Systems (AGUS) Project

NASA Technical Reports Server (NTRS)

Gosselin, Armand M.

2007-01-01

All space vehicles require ground umbilical systems for servicing. Servicing requirements can include, but are not limited to, electrical power and control, propellant loading and venting, pneumatic system supply, hazard gas detection and purging as well as systems checkout capabilities. Of the various types of umbilicals, all require several common subsystems. These typically include an alignment system, mating and locking system, fluid connectors, electrical connectors and control !checkout systems. These systems have been designed to various levels of detail based on the needs for manual and/or automation requirements. The Automated Ground Umbilical Systems (AGUS) project is a multi-phase initiative to develop design performance requirements and concepts for launch system umbilicals. The automation aspect minimizes operational time and labor in ground umbilical processing while maintaining reliability. This current phase of the project reviews the design, development, testing and operations of ground umbilicals built for the Saturn, Shuttle, X-33 and Atlas V programs. Based on the design and operations lessons learned from these systems, umbilicals can be optimized for specific applications. The product of this study is a document containing details of existing systems and requirements for future automated umbilical systems with emphasis on design-for-operations (DFO).

Data Base Design Using Entity-Relationship Models.

ERIC Educational Resources Information Center

Davis, Kathi Hogshead

1983-01-01

The entity-relationship (ER) approach to database design is defined, and a specific example of an ER model (personnel-payroll) is examined. The requirements for converting ER models into specific database management systems are discussed. (Author/MSE)

The Importance of Information Requirements in Designing Acquisition to Information Systems

NASA Technical Reports Server (NTRS)

Davis, Bruce A.; Hill, Chuck; Maughan, Paul M.

1998-01-01

The partnership model used by NASA's Commercial Remote Sensing Program has been successful in better defining remote sensing functional requirements and translation to technical specifications to address environmental needs of the 21st century.

Roofing Source File.

ERIC Educational Resources Information Center

American School & University, 1998

1998-01-01

Provides guidelines for school administrators to aid in the selection of school-roofing systems, and information required to make specification and purchasing decisions. Low-slope roofing systems are examined, as are multiply systems such as modified bitumen, EPDM, thermoplastic, metal, and foam. (GR)

Rapidly Deployed Modular Telemetry System

NASA Technical Reports Server (NTRS)

Varnavas, Kosta A. (Inventor); Sims, William Herbert, III (Inventor)

2013-01-01

The present invention is a telemetry system, and more specifically is a rapidly deployed modular telemetry apparatus which utilizes of SDR technology and the FPGA programming capability to reduce the number of hardware components and programming required to deploy a telemetry system.

A systems engineering management approach to resource management applications

NASA Technical Reports Server (NTRS)

Hornstein, Rhoda Shaller

1989-01-01

The author presents a program management response to the following question: How can the traditional practice of systems engineering management, including requirements specification, be adapted, enhanced, or modified to build future planning and scheduling systems for effective operations? The systems engineering management process, as traditionally practiced, is examined. Extensible resource management systems are discussed. It is concluded that extensible systems are a partial solution to problems presented by requirements that are incomplete, partially immeasurable, and often dynamic. There are positive indications that resource management systems have been characterized and modeled sufficiently to allow their implementation as extensible systems.

Public healthcare interests require strict competition enforcement.

PubMed

Loozen, Edith M H

2015-07-01

Several countries have introduced competition in their health systems in order to maintain the supply of high quality health care in a cost-effective manner. The introduction of competition triggers competition enforcement. Since healthcare is characterized by specific market failures, many favor healthcare-specific competition enforcement in order not only to account for the competition interest, but also for the healthcare interests. The question is whether healthcare systems based on competition can succeed when competition enforcement deviates from standard practice. This paper analyzes whether healthcare-specific competition enforcement is theoretically sound and practically effective. This is exemplified by the Dutch system that is based on regulated competition and thus crucially depends on getting competition enforcement right. Governments are responsible for correcting market failures. Markets are responsible for maximizing the public healthcare interests. By securing sufficient competitive pressure, competition enforcement makes sure they do. When interpreted according to welfare-economics, competition law takes into account both costs and benefits specific market behavior may have for healthcare. Competition agencies and judiciary are not legitimized to deviate from standard evidentiary requirements. Dutch case law shows that healthcare-specific enforcement favors the healthcare undertakings concerned, but to the detriment of public health care. Healthcare-specific competition enforcement is conceptually flawed and counterproductive. In order for healthcare systems based on competition to succeed, competition enforcement should be strict. Copyright © 2015 Elsevier Ireland Ltd. All rights reserved.

Report of the facility definition team spacelab UV-Optical Telescope Facility

NASA Technical Reports Server (NTRS)

1975-01-01

Scientific requirements for the Spacelab Ultraviolet-Optical Telescope (SUOT) facility are presented. Specific programs involving high angular resolution imagery over wide fields, far ultraviolet spectroscopy, precisely calibrated spectrophotometry and spectropolarimetry over a wide wavelength range, and planetary studies, including high resolution synoptic imagery, are recommended. Specifications for the mounting configuration, instruments for the mounting configuration, instrument mounting system, optical parameters, and the pointing and stabilization system are presented. Concepts for the focal plane instruments are defined. The functional requirements of the direct imaging camera, far ultraviolet spectrograph, and the precisely calibrated spectrophotometer are detailed, and the planetary camera concept is outlined. Operational concepts described in detail are: the makeup and functions of shuttle payload crew, extravehicular activity requirements, telescope control and data management, payload operations control room, orbital constraints, and orbital interfaces (stabilization, maneuvering requirements and attitude control, contamination, utilities, and payload weight considerations).

Space shuttle configuration accounting functional design specification

NASA Technical Reports Server (NTRS)

1974-01-01

An analysis is presented of the requirements for an on-line automated system which must be capable of tracking the status of requirements and engineering changes and of providing accurate and timely records. The functional design specification provides the definition, description, and character length of the required data elements and the interrelationship of data elements to adequately track, display, and report the status of active configuration changes. As changes to the space shuttle program levels II and III configuration are proposed, evaluated, and dispositioned, it is the function of the configuration management office to maintain records regarding changes to the baseline and to track and report the status of those changes. The configuration accounting system will consist of a combination of computers, computer terminals, software, and procedures, all of which are designed to store, retrieve, display, and process information required to track proposed and proved engineering changes to maintain baseline documentation of the space shuttle program levels II and III.

Earth Observing System/Meteorological Satellite (EOS/METSAT). Advanced Microwave Sounding Unit-A (AMSU-A) Contamination Control Plan

NASA Technical Reports Server (NTRS)

Fay, M.

1998-01-01

This Contamination Control Plan is submitted in response the Contract Document requirements List (CDRL) 007 under contract NAS5-32314 for the Earth Observing System (EOS) Advanced Microwave Sounding Unit A (AMSU-A). In response to the CDRL instructions, this document defines the level of cleanliness and methods/procedures to be followed to achieve adequate cleanliness/contamination control, and defines the required approach to maintain cleanliness/contamination control through shipping, observatory integration, test, and flight. This plan is also applicable to the Meteorological Satellite (METSAT) except where requirements are identified as EOS-specific. This plan is based on two key factors: a. The EOS/METSAT AMSU-A Instruments are not highly contamination sensitive. b. Potential contamination of other EOS Instruments is a key concern as addressed in Section 9/0 of the Performance Assurance Requirements for EOS/METSAT Integrated Programs AMSU-A Instrument (MR) (NASA Specification S-480-79).

Space shuttle booster separation motor design

NASA Technical Reports Server (NTRS)

Smith, G. W.; Chase, C. A.

1976-01-01

The separation characteristics of the space shuttle solid rocket boosters (SRBs) are introduced along with the system level requirements for the booster separation motors (BSMs). These system requirements are then translated into specific motor requirements that control the design of the BSM. Each motor component is discussed including its geometry, material selection, and fabrication process. Also discussed is the propellant selection, grain design, and performance capabilities of the motor. The upcoming test program to develop and qualify the motor is outlined.

Goals Analysis Procedure Guidelines for Applying the Goals Analysis Process

NASA Technical Reports Server (NTRS)

Motley, Albert E., III

2000-01-01

One of the key elements to successful project management is the establishment of the "right set of requirements", requirements that reflect the true customer needs and are consistent with the strategic goals and objectives of the participating organizations. A viable set of requirements implies that each individual requirement is a necessary element in satisfying the stated goals and that the entire set of requirements, taken as a whole, is sufficient to satisfy the stated goals. Unfortunately, it is the author's experience that during project formulation phases' many of the Systems Engineering customers do not conduct a rigorous analysis of the goals and objectives that drive the system requirements. As a result, the Systems Engineer is often provided with requirements that are vague, incomplete, and internally inconsistent. To complicate matters, most systems development methodologies assume that the customer provides unambiguous, comprehensive and concise requirements. This paper describes the specific steps of a Goals Analysis process applied by Systems Engineers at the NASA Langley Research Center during the formulation of requirements for research projects. The objective of Goals Analysis is to identify and explore all of the influencing factors that ultimately drive the system's requirements.

Identification of specific requirements for a NASA aerospace law information system and identification of the acquisition requirements for an aerospace law collection for the NASA law library

NASA Technical Reports Server (NTRS)

Morenoff, J.; Roth, D. L.; Singleton, J. W.

1972-01-01

The study to develop, implement, and maintain a space law library and information system is summarized. The survey plan; major interviews with individuals representative of potential sources, users and producers of information related to aerospace law; and system trade-off analyses are discussed along with the NASA/RECON system capability. The NASA publications of STAR and IAA are described, and the NASA legal micro-thesaurus is included.

The challenge of developing structural materials for fusion power systems

NASA Astrophysics Data System (ADS)

Bloom, Everett E.

1998-10-01

Nuclear fusion can be one of the most attractive sources of energy from the viewpoint of safety and minimal environmental impact. Central in the goal of designing a safe, environmentally benign, and economically competitive fusion power system is the requirement for high performance, low activation materials. The general performance requirements for such materials have been defined and it is clear that materials developed for other applications (e.g. aerospace, nuclear fission, fossil energy systems) will not fully meet the needs of fusion. Advanced materials, with composition and microstructure tailored to yield properties that will satisfy the specific requirements of fusion must be developed. The international fusion programs have made significant progress towards this goal. Compositional requirements for low activation lead to a focus of development efforts on silicon carbide composites, vanadium alloys, and advanced martensitic steels as candidate structural material systems. Control of impurities will be critically important in actually achieving low activation but this appears possible. Neutron irradiation produces significant changes in the mechanical and physical properties of each of these material systems raising feasibility questions and design limitations. A focus of the research and development effort is to understand these effects, and through the development of specific compositions and microstructures, produce materials with improved and adequate performance. Other areas of research that are synergistic with the development of radiation resistant materials include fabrication, joining technology, chemical compatibility with coolants and tritium breeders and specific questions relating to the unique characteristics of a given material (e.g. coatings to reduce gas permeation in SiC composites) or design concept (e.g. electrical insulator coatings for liquid metal concepts).

Kilowatt Isotope Power System: component test report for the ground demonstration system alternator stator. 78-KIPS-17

DOE Office of Scientific and Technical Information (OSTI.GOV)

Not Available

1977-12-14

The purpose of this test was to demonstrate that the alternator stator has satisfactorily completed sufficient testing to safisfy the requirements set forth within the Kilowatt Isotope Power System (KIPS) Component Test Specification for the GDS Alternator Stator (TS 2538). The results of the acceptance tests conducted on the alternator stator, S/N 003, are presented, and show that the stator did meet specified requirements.

Software Requirements Analysis as Fault Predictor

NASA Technical Reports Server (NTRS)

Wallace, Dolores

2003-01-01

Waiting until the integration and system test phase to discover errors leads to more costly rework than resolving those same errors earlier in the lifecycle. Costs increase even more significantly once a software system has become operational. WE can assess the quality of system requirements, but do little to correlate this information either to system assurance activities or long-term reliability projections - both of which remain unclear and anecdotal. Extending earlier work on requirements accomplished by the ARM tool, measuring requirements quality information against code complexity and test data for the same system may be used to predict specific software modules containing high impact or deeply embedded faults now escaping in operational systems. Such knowledge would lead to more effective and efficient test programs. It may enable insight into whether a program should be maintained or started over.

Development of vendor evaluation criteria and post-implementation considerations for MSFC center-wide executive information system

NASA Technical Reports Server (NTRS)

Moynihan, Gary P.

1992-01-01

In June 1991, the MITRE Corporation submitted a series of recommendations as part of a Marshall Space Flight Center (MSFC) Management Information System Requirements Study, initiated by the Information Systems Office (ISO). A major recommendation of the study was to develop an Executive Information System (EIS) for MSFC executives. ISO was directed, by center management, to proceed with the development of a Center-Wide Executive Information System. Existing EIS prototypes, developed by the Space Shuttle Projects Office and the Payload Projects Office, were reviewed. These existing MSFC prototypes were considered not to encompass the required functionality needed on a center-wide basis. A follow-up study by MITRE provided top-level system requirements. These were later incorporated into a final requirements specification document by Boeing Computer Support Services.

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 4: PEP functional specification

NASA Technical Reports Server (NTRS)

1979-01-01

The functional, performance, design, and test requirements for the Orbiter power extension package and its associated ground support equipment are defined. Both government and nongovernment standards and specifications are cited for the following subsystems: electrical power, structural/mechanical, avionics, and thermal control. Quality control assurance provisions and preparation for delivery are also discussed.

The Co-Creation of Information Systems

ERIC Educational Resources Information Center

Gomillion, David

2013-01-01

In information systems development, end-users have shifted in their role: from consumers of information to informants for requirements to developers of systems. This shift in the role of users has also changed how information systems are developed. Instead of systems developers creating specifications for software or end-users creating small…

48 CFR 711.002-70 - Metric system waivers.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 5 2011-10-01 2011-10-01 false Metric system waivers. 711... ACQUISITION PLANNING DESCRIBING AGENCY NEEDS 711.002-70 Metric system waivers. (a) Criteria. The FAR 11.002(b) requirement to use the metric system of measurement for specifications and quantitative data that are...

48 CFR 711.002-70 - Metric system waivers.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 48 Federal Acquisition Regulations System 5 2012-10-01 2012-10-01 false Metric system waivers. 711... ACQUISITION PLANNING DESCRIBING AGENCY NEEDS 711.002-70 Metric system waivers. (a) Criteria. The FAR 11.002(b) requirement to use the metric system of measurement for specifications and quantitative data that are...

48 CFR 711.002-70 - Metric system waivers.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 5 2013-10-01 2013-10-01 false Metric system waivers. 711... ACQUISITION PLANNING DESCRIBING AGENCY NEEDS 711.002-70 Metric system waivers. (a) Criteria. The FAR 11.002(b) requirement to use the metric system of measurement for specifications and quantitative data that are...

48 CFR 711.002-70 - Metric system waivers.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 5 2014-10-01 2014-10-01 false Metric system waivers. 711... ACQUISITION PLANNING DESCRIBING AGENCY NEEDS 711.002-70 Metric system waivers. (a) Criteria. The FAR 11.002(b) requirement to use the metric system of measurement for specifications and quantitative data that are...

46 CFR 62.35-40 - Fuel systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Fuel systems. 62.35-40 Section 62.35-40 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-40 Fuel systems. (a) Level alarms. Where...

DOE Office of Scientific and Technical Information (OSTI.GOV)

Baker, J.E.

Many robotic operations, e.g., mapping, scanning, feature following, etc., require accurate surface following of arbitrary targets. This paper presents a versatile surface following and mapping system designed to promote hardware, software and application independence, modular development, and upward expandability. These goals are met by: a full, a priori specification of the hardware and software interfaces; a modular system architecture; and a hierarchical surface-data analysis method, permitting application specific tuning at each conceptual level of topological abstraction. This surface following system was fully designed and independently of any specific robotic host, then successfully integrated with and demonstrated on a completely amore » priori unknown, real-time robotic system. 7 refs.« less

The Determination of Navy Family Housing Requirements

DTIC Science & Technology

1992-04-01

for greater precision and responsiveness, closer scrutiny of Navy family housing programs, and internal initiatives relating to quality management ...DETERMINATION SYSTEM Overview For almost 20 years, the Navy has used a semiautomated system to project family housing requirements. This process is managed ... Family Housing Management Institute (FHMI) materials, and management specifications maintained by NAVFAC and FACSO. FINDINGS Theory We believe that the

Key Performance Parameter Driven Technology Goals for Electric Machines and Power Systems

NASA Technical Reports Server (NTRS)

Bowman, Cheryl; Jansen, Ralph; Brown, Gerald; Duffy, Kirsten; Trudell, Jeffrey

2015-01-01

Transitioning aviation to low carbon propulsion is one of the crucial strategic research thrust and is a driver in the search for alternative propulsion system for advanced aircraft configurations. This work requires multidisciplinary skills coming from multiple entities. The feasibility of scaling up various electric drive system technologies to meet the requirements of a large commercial transport is discussed in terms of key parameters. Functional requirements are identified that impact the power system design. A breakeven analysis is presented to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

46 CFR 128.420 - Keel cooler installations.

Code of Federal Regulations, 2010 CFR

2010-10-01

... ENGINEERING: EQUIPMENT AND SYSTEMS Design Requirements for Specific Systems § 128.420 Keel cooler...-metallic hose-clamps may be used at machinery connections if— (1) The clamps are of a corrosion-resistant...

Expanding the Scope of Site-Specific Recombinases for Genetic and Metabolic Engineering

PubMed Central

Gaj, Thomas; Sirk, Shannon J.; Barbas, Carlos F.

2014-01-01

Site-specific recombinases are tremendously valuable tools for basic research and genetic engineering. By promoting high-fidelity DNA modifications, site-specific recombination systems have empowered researchers with unprecedented control over diverse biological functions, enabling countless insights into cellular structure and function. The rigid target specificities of many sites-specific recombinases, however, have limited their adoption in fields that require highly flexible recognition abilities. As a result, intense effort has been directed toward altering the properties of site-specific recombination systems by protein engineering. Here, we review key developments in the rational design and directed molecular evolution of site-specific recombinases, highlighting the numerous applications of these enzymes across diverse fields of study. PMID:23982993

Methodology for the systems engineering process. Volume 3: Operational availability

NASA Technical Reports Server (NTRS)

Nelson, J. H.

1972-01-01

A detailed description and explanation of the operational availability parameter is presented. The fundamental mathematical basis for operational availability is developed, and its relationship to a system's overall performance effectiveness is illustrated within the context of identifying specific availability requirements. Thus, in attempting to provide a general methodology for treating both hypothetical and existing availability requirements, the concept of an availability state, in conjunction with the more conventional probability-time capability, is investigated. In this respect, emphasis is focused upon a balanced analytical and pragmatic treatment of operational availability within the system design process. For example, several applications of operational availability to typical aerospace systems are presented, encompassing the techniques of Monte Carlo simulation, system performance availability trade-off studies, analytical modeling of specific scenarios, as well as the determination of launch-on-time probabilities. Finally, an extensive bibliography is provided to indicate further levels of depth and detail of the operational availability parameter.

Project FIRES - Firefighters Integrated Response Equipment System. Volume 3: Protective Ensemble Design and Procurement Specification, Phase 1B

NASA Technical Reports Server (NTRS)

Abeles, F. J.

1980-01-01

Each of the subsystems comprising the protective ensemble for firefighters is described. These include: (1) the garment system which includes turnout gear, helmets, faceshields, coats, pants, gloves, and boots; (2) the self-contained breathing system; (3) the lighting system; and (4) the communication system. The design selection rationale is discussed and the drawings used to fabricate the prototype ensemble are provided. The specifications presented were developed using the requirements and test method of the protective ensemble standard. Approximate retail prices are listed.

Nucleic acid detection system and method for detecting influenza

DOEpatents

Cai, Hong; Song, Jian

2015-03-17

The invention provides a rapid, sensitive and specific nucleic acid detection system which utilizes isothermal nucleic acid amplification in combination with a lateral flow chromatographic device, or DNA dipstick, for DNA-hybridization detection. The system of the invention requires no complex instrumentation or electronic hardware, and provides a low cost nucleic acid detection system suitable for highly sensitive pathogen detection. Hybridization to single-stranded DNA amplification products using the system of the invention provides a sensitive and specific means by which assays can be multiplexed for the detection of multiple target sequences.

Comparison and selection of off-grid PV systems

NASA Astrophysics Data System (ADS)

Izmailov, Andrey Yu.; Lobachevsky, Yakov P.; Shepovalova, Olga V.

2018-05-01

This work deals with comparison, evaluation and selection of PV systems of the same type based on their technical parameters either indicated in their technical specifications or calculated ones. Stand-alone and grid backed up photoelectric systems have been considered. General requirements for photoelectric system selection and evaluation have been presented that ensure system operability and required efficiency in operation conditions. Generic principles and definition of photoelectric systems characteristics have been considered. The described method is mainly targeted at PV engineering personnel and private customers purchasing PV systems. It can be also applied in the course of project contests, tenders, etc.

Ion-Specific Nutrient Management in Closed Systems: The Necessity for Ion-Selective Sensors in Terrestrial and Space-Based Agriculture and Water Management Systems

PubMed Central

Bamsey, Matthew; Graham, Thomas; Thompson, Cody; Berinstain, Alain; Scott, Alan; Dixon, Michael

2012-01-01

The ability to monitor and control plant nutrient ions in fertigation solutions, on an ion-specific basis, is critical to the future of controlled environment agriculture crop production, be it in traditional terrestrial settings (e.g., greenhouse crop production) or as a component of bioregenerative life support systems for long duration space exploration. Several technologies are currently available that can provide the required measurement of ion-specific activities in solution. The greenhouse sector has invested in research examining the potential of a number of these technologies to meet the industry's demanding requirements, and although no ideal solution yet exists for on-line measurement, growers do utilize technologies such as high-performance liquid chromatography to provide off-line measurements. An analogous situation exists on the International Space Station where, technological solutions are sought, but currently on-orbit water quality monitoring is considerably restricted. This paper examines the specific advantages that on-line ion-selective sensors could provide to plant production systems both terrestrially and when utilized in space-based biological life support systems and how similar technologies could be applied to nominal on-orbit water quality monitoring. A historical development and technical review of the various ion-selective monitoring technologies is provided. PMID:23201999

Ion-specific nutrient management in closed systems: the necessity for ion-selective sensors in terrestrial and space-based agriculture and water management systems.

PubMed

Bamsey, Matthew; Graham, Thomas; Thompson, Cody; Berinstain, Alain; Scott, Alan; Dixon, Michael

2012-10-01

The ability to monitor and control plant nutrient ions in fertigation solutions, on an ion-specific basis, is critical to the future of controlled environment agriculture crop production, be it in traditional terrestrial settings (e.g., greenhouse crop production) or as a component of bioregenerative life support systems for long duration space exploration. Several technologies are currently available that can provide the required measurement of ion-specific activities in solution. The greenhouse sector has invested in research examining the potential of a number of these technologies to meet the industry's demanding requirements, and although no ideal solution yet exists for on-line measurement, growers do utilize technologies such as high-performance liquid chromatography to provide off-line measurements. An analogous situation exists on the International Space Station where, technological solutions are sought, but currently on-orbit water quality monitoring is considerably restricted. This paper examines the specific advantages that on-line ion-selective sensors could provide to plant production systems both terrestrially and when utilized in space-based biological life support systems and how similar technologies could be applied to nominal on-orbit water quality monitoring. A historical development and technical review of the various ion-selective monitoring technologies is provided.

HAL/S-FC compiler system functional specification

NASA Technical Reports Server (NTRS)

1974-01-01

The functional requirements to be met by the HAL/S-FC compiler, and the hardware and software compatibilities between the compiler system and the environment in which it operates are defined. Associated runtime facilities and the interface with the Software Development Laboratory are specified. The construction of the HAL/S-FC system as functionally separate units and the interfaces between those units is described. An overview of the system's capabilities is presented and the hardware/operating system requirements are specified. The computer-dependent aspects of the HAL/S-FC are also specified. Compiler directives are included.

49 CFR 232.601 - Scope.

Code of Federal Regulations, 2010 CFR

2010-10-01

... TRANSPORTATION BRAKE SYSTEM SAFETY STANDARDS FOR FREIGHT AND OTHER NON-PASSENGER TRAINS AND EQUIPMENT; END-OF-TRAIN DEVICES Electronically Controlled Pneumatic (ECP) Braking Systems § 232.601 Scope. This subpart... systems. This subpart also contains specific exceptions from various requirements contained in this part...

ATM Technology Demonstration-1 Phase II Boeing Configurable Graphical Display (CGD) Software Design Description

NASA Technical Reports Server (NTRS)

Wilber, George F.

2017-01-01

This Software Description Document (SDD) captures the design for developing the Flight Interval Management (FIM) system Configurable Graphics Display (CGD) software. Specifically this SDD describes aspects of the Boeing CGD software and the surrounding context and interfaces. It does not describe the Honeywell components of the CGD system. The SDD provides the system overview, architectural design, and detailed design with all the necessary information to implement the Boeing components of the CGD software and integrate them into the CGD subsystem within the larger FIM system. Overall system and CGD system-level requirements are derived from the CGD SRS (in turn derived from the Boeing System Requirements Design Document (SRDD)). Display and look-and-feel requirements are derived from Human Machine Interface (HMI) design documents and working group recommendations. This Boeing CGD SDD is required to support the upcoming Critical Design Review (CDR).

Lessons Learned in the Specification, Purchase, Validation and Final Installation Process of a Replacement PCM Bit Synchronizer

NASA Technical Reports Server (NTRS)

Price, Richard N.

2007-01-01

This paper intends to describe the lessons learned while specifying validating and installing a bit sync to replace the 30 year old Aydin Model 335a PCM bit sync used in the Space Shuttle Launch Control Center. The engineer had to analyze the original requirements and specifications and then create new requirements documentation that more correctly described our needs. One issue to consider was the removal of unnecessary requirements such as various data formats when only one format is used. The conversion to a system that no longer has an assortment of analog rotary switches required retraining of the operators. Finally, post-procurement corrections for undisclosed user requirements and missed design requirements required close contact with a manufacturer who was willing to accommodate the changes.

Development Requirements for Spacesuit Elbow Joint

NASA Technical Reports Server (NTRS)

Peters, Benjamin

2017-01-01

Functional Requirements for spacesuit elbow joint:1) The system is a conformal, single-axis spacesuit pressurized joint that encloses the elbow joint of the suited user and uses a defined interface to connect to the suit systems on either side of the joint.2) The system shall be designed to bear the loads incurred from the internal pressure of the system, as well as the expected loads induced by the user while enabling the user move the joint through the required range of motion. The joint torque of the system experienced by the user shall remain at or below the required specification for the entire range of motion.3) The design shall be constructed, at a minimum, as a two-layer system. The internal, air-tight layer shall be referred to as the bladder, and the layer on the unpressurized side of the bladder shall be referred to as the restraint. The design of the system may include additional features or layers, such as axial webbing, to meet the overall requirements of the design.

Preliminary Analysis of Effect of Random Segment Errors on Coronagraph Performance

NASA Technical Reports Server (NTRS)

Stahl, Mark T.; Shaklan, Stuart B.; Stahl, H. Philip

2015-01-01

Are we alone in the Universe is probably the most compelling science question of our generation. To answer it requires a large aperture telescope with extreme wavefront stability. To image and characterize Earth-like planets requires the ability to block 10(exp 10) of the host stars light with a 10(exp -11) stability. For an internal coronagraph, this requires correcting wavefront errors and keeping that correction stable to a few picometers rms for the duration of the science observation. This requirement places severe specifications upon the performance of the observatory, telescope and primary mirror. A key task of the AMTD project (initiated in FY12) is to define telescope level specifications traceable to science requirements and flow those specifications to the primary mirror. From a systems perspective, probably the most important question is: What is the telescope wavefront stability specification? Previously, we suggested this specification should be 10 picometers per 10 minutes; considered issues of how this specification relates to architecture, i.e. monolithic or segmented primary mirror; and asked whether it was better to have few or many segmented. This paper reviews the 10 picometers per 10 minutes specification; provides analysis related to the application of this specification to segmented apertures; and suggests that a 3 or 4 ring segmented aperture is more sensitive to segment rigid body motion that an aperture with fewer or more segments.

NASA-STD 3001 and the Human Integration Design Handbook (HIDH): Evolution of NASA-STD-3000

NASA Technical Reports Server (NTRS)

Pickett, Lynn; Connolly, Janis; Arch, M.; Tillman, Barry; Russo, Dane

2007-01-01

The Habitability & Environmental Factors and Space Medicine Divisions have developed the Space Flight Human System Standard (SFHSS) (NASA-STD-3001) to replace NASA-STD-3000 as a new NASA standard for all human spaceflight programs. The SFHSS is composed of 2 volumes. Volume 1, Crew Health, contains medical levels of care, permissible exposure limits, and fitness for duty criteria, and permissible outcome limits as a means of defining successful operating criteria for the human system. Volume 2, Habitability and Environmental Health, contains environmental, habitability and human factors standards. Development of the Human Integration Design Handbook (HIDH), a companion to the standard, is currently under construction and entails the update and revision of NASA-STD-3000 data. This new handbook will, in the fashion of NASA STD-3000, assist engineers and designers in appropriately applying habitability, environmental and human factors principles to spacecraft design. Organized in a chapter-module-element structure, the HIDH will provide the guidance for the development of requirements, design considerations, lessons learned, example solutions, background research, and assist in the identification of gaps and research needs in the disciplines. Subject matter experts have been and continue to be solicited to participate in the update of the chapters. The purpose is to build the HIDH with the best and latest data, and provide a broad representation from experts in industry, academia, the military and the space program. The handbook and the two standards volumes work together in a unique way to achieve the required level of human-system interface. All new NASA programs will be required to meet Volumes 1 and 2. Volume 2 presents human interface goals in broad, non-verifiable standards. Volume 2 also requires that each new development program prepare a set of program-specific human factors requirements. These program-specific human and environmental factors requirements must be verifiable and tailored to assure the new system meets the Volume 2 standards. Programs will use the HIDH to write their verifiable program-specific requirements.

Cellular projections from sensory hair cells form polarity-specific scaffolds during synaptogenesis

PubMed Central

Dow, Eliot; Siletti, Kimberly

2015-01-01

The assembly of a nervous system requires the extension of axons and dendrites to specific regions where they are matched with appropriate synaptic targets. Although the cues that guide long-range outgrowth have been characterized extensively, additional mechanisms are required to explain short-range guidance in neural development. Using a complementary combination of time-lapse imaging by fluorescence confocal microscopy and serial block-face electron microscopy, we identified a novel type of presynaptic projection that participates in the assembly of the vertebrate nervous system. Synapse formation by each hair cell of the zebrafish's lateral line occurs during a particular interval after the cell's birth. During the same period, projections emerge from the cellular soma, extending toward a specific subpopulation of mature hair cells and interacting with polarity-specific afferent nerve terminals. The terminals then extend along the projections to reach appropriately matched presynaptic sites, after which the projections recede. Our results suggest that presynaptic projections act as transient scaffolds for short-range partner matching, a mechanism that may occur elsewhere in the nervous system. PMID:25995190

Atmospheric, Magnetospheric and plasmas in Space (AMPS) spacelab payload definition study; Volume 4: Part 3, Labcraft instrument systems general specification

NASA Technical Reports Server (NTRS)

Keeley, J. T.

1976-01-01

Guidelines and general requirements applicable to the development of instrument flight hardware intended for use on the GSFC Shuttle Scientific Payloads Program are given. Criteria, guidelines, and an organized approach to specifying the appropriate level of requirements for each instrument in order to permit its development at minimum cost while still assuring crew safety, are included. It is recognized that the instruments for these payloads will encompass wide ranges of complexity, cost, development risk, and safety hazards. The flexibility required to adapt the controls, documentation, and verification requirements in accord with the specific instrument is provided.

Design of the cryogenic systems for the Near and Far LAr-TPC detectors of the Short-Baseline Neutrino program (SBN) at Fermilab

DOE Office of Scientific and Technical Information (OSTI.GOV)

Geynisman, M.; Bremer, J.; Chalifour, M.

The Short-Baseline Neutrino (SBN) physics program at Fermilab and Neutrino Platform (NP) at CERN are part of the international Neutrino Program leading to the development of Long-Baseline Neutrino Facility/Deep Underground Neutrino Experiment (LBNF/DUNE) science project. The SBN program consisting of three Liquid Argon Time Projection Chamber (LAr-TPC) detectors positioned along the Booster Neutrino Beam (BNB) at Fermilab includes an existing detector known as MicroBooNE (170-ton LAr-TPC) plus two new experiments known as SBN’s Near Detector (SBND, ~260 tons) and SBN’s Far Detector (SBN-FD, ~760 tons). All three detectors have distinctly different design of their cryostats thus defining specific requirements formore » the cryogenic systems. Fermilab has already built two new facilities to house SBND and SBN-FD detectors. The cryogenic systems for these detectors are in various stages of design and construction with CERN and Fermilab being responsible for delivery of specific sub-systems. This contribution presents specific design requirements and typical implementation solutions for each sub-system of the SBND and SBN-FD cryogenic systems.« less

Design of the cryogenic systems for the Near and Far LAr-TPC detectors of the Short-Baseline Neutrino program (SBN) at Fermilab

NASA Astrophysics Data System (ADS)

Geynisman, M.; Bremer, J.; Chalifour, M.; Delaney, M.; Dinnon, M.; Doubnik, R.; Hentschel, S.; Kim, M. J.; Montanari, C.; Montanari, D.; Nichols, T.; Norris, B.; Sarychev, M.; Schwartz, F.; Tillman, J.; Zuckerbrot, M.

2017-12-01

The Short-Baseline Neutrino (SBN) physics program at Fermilab and Neutrino Platform (NP) at CERN are part of the international Neutrino Program leading to the development of Long-Baseline Neutrino Facility/Deep Underground Neutrino Experiment (LBNF/DUNE) science project. The SBN program consisting of three Liquid Argon Time Projection Chamber (LAr-TPC) detectors positioned along the Booster Neutrino Beam (BNB) at Fermilab includes an existing detector known as MicroBooNE (170-ton LAr-TPC) plus two new experiments known as SBN’s Near Detector (SBND, ∼260 tons) and SBN’s Far Detector (SBN-FD, ∼760 tons). All three detectors have distinctly different design of their cryostats thus defining specific requirements for the cryogenic systems. Fermilab has already built two new facilities to house SBND and SBN-FD detectors. The cryogenic systems for these detectors are in various stages of design and construction with CERN and Fermilab being responsible for delivery of specific sub-systems. This contribution presents specific design requirements and typical implementation solutions for each sub-system of the SBND and SBN-FD cryogenic systems.

Space tug thermal control. [design criteria and specifications

NASA Technical Reports Server (NTRS)

1974-01-01

It was determined that space tug will require the capability to perform its mission within a broad range of thermal environments with currently planned mission durations of up to seven days, so an investigation was conducted to define a thermal design for the forward and intertank compartments and fuel cell heat rejection system that satisfies tug requirements for low inclination geosynchronous deploy and retrieve missions. Passive concepts were demonstrated analytically for both the forward and intertank compartments, and a worst case external heating environment was determined for use during the study. The thermal control system specifications and designs which resulted from the research are shown.

Roadway reference system users' manual (a.k.a. the reference post system made simple)

DOT National Transportation Integrated Search

1999-05-01

Modern roadway management requires information. The Roadway Reference System (RRS) is a means by which data can be associated to a specific location and retrieved in reference to that location. The major advantage to this system is that once in place...

48 CFR 215.407-5-70 - Disclosure, maintenance, and review requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... management systems (e.g., production control or cost accounting) with the estimating system so that the... disposition of the survey team findings. (g) Impact of estimating system deficiencies on specific proposals... DEFENSE ACQUISITION REGULATIONS SYSTEM, DEPARTMENT OF DEFENSE CONTRACTING METHODS AND CONTRACT TYPES...

46 CFR 182.458 - Portable fuel systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 7 2013-10-01 2013-10-01 false Portable fuel systems. 182.458 Section 182.458 Shipping...) MACHINERY INSTALLATION Specific Machinery Requirements § 182.458 Portable fuel systems. (a) Portable fuel systems, including portable tanks and related fuel lines and accessories, are prohibited except where used...

46 CFR 182.458 - Portable fuel systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 7 2010-10-01 2010-10-01 false Portable fuel systems. 182.458 Section 182.458 Shipping...) MACHINERY INSTALLATION Specific Machinery Requirements § 182.458 Portable fuel systems. (a) Portable fuel systems, including portable tanks and related fuel lines and accessories, are prohibited except where used...

46 CFR 182.458 - Portable fuel systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 7 2011-10-01 2011-10-01 false Portable fuel systems. 182.458 Section 182.458 Shipping...) MACHINERY INSTALLATION Specific Machinery Requirements § 182.458 Portable fuel systems. (a) Portable fuel systems, including portable tanks and related fuel lines and accessories, are prohibited except where used...

HAL/S-FC compiler system functional specification

NASA Technical Reports Server (NTRS)

1974-01-01

Compiler organization is discussed, including overall compiler structure, internal data transfer, compiler development, and code optimization. The user, system, and SDL interfaces are described, along with compiler system requirements. Run-time software support package and restrictions and dependencies are also considered of the HAL/S-FC system.

The Bartlesville System; TGISS Software Documentation.

ERIC Educational Resources Information Center

Roberts, Tommy L.; And Others

TGISS (Total Guidance Information Support System) is an information storage and retrieval system specifically designed to meet the needs and requirements of a counselor in the Bartlesville Public School environment. The system, which is a combination of man/machine capabilities, includes the hardware and software necessary to extend the…

Space-based multifunctional end effector systems functional requirements and proposed designs

NASA Technical Reports Server (NTRS)

Mishkin, A. H.; Jau, B. M.

1988-01-01

The end effector is an essential element of teleoperator and telerobot systems to be employed in space in the next decade. The report defines functional requirements for end effector systems to perform operations that are currently only feasible through Extra-Vehicular Activity (EVA). Specific tasks and functions that the end effectors must be capable of performing are delineated. Required capabilities for forces and torques, clearances, compliance, and sensing are described, using current EVA requirements as guidelines where feasible. The implications of these functional requirements on the elements of potential end effector systems are discussed. The systems issues that must be considered in the design of space-based manipulator systems are identified; including impacts on subsystems tightly coupled to the end effector, i.e., control station, information processing, manipulator arm, tool and equipment stowage. Possible end effector designs are divided into three categories: single degree-of-freedom end effectors, multiple degree of freedom end effectors, and anthropomorphic hands. Specific design alternatives are suggested and analyzed within the individual categories. Two evaluations are performed: the first considers how well the individual end effectors could substitute for EVA; the second compares how manipulator systems composed of the top performers from the first evaluation would improve the space shuttle Remote Manipulator System (RMS) capabilities. The analysis concludes that the anthropomorphic hand is best-suited for EVA tasks. A left- and right-handed anthropomorphic manipulator arm configuration is suggested as appropriate to be affixed to the RMS, but could also be used as part of the Smart Front End for the Orbital Maneuvering Vehicle (OMV). The technical feasibility of the anthropomorphic hand and its control are demonstrated. An evolutionary development approach is proposed and approximate scheduling provided for implementing the suggested manipulator systems in time for space stations operations in the early 1990s.

Space shuttle main engine definition (phase B). Volume 2: Avionics. [for space shuttle

NASA Technical Reports Server (NTRS)

1971-01-01

The advent of the space shuttle engine with its requirements for high specific impulse, long life, and low cost have dictated a combustion cycle and a closed loop control system to allow the engine components to run close to operating limits. These performance requirements, combined with the necessity for low operational costs, have placed new demands on rocket engine control, system checkout, and diagnosis technology. Based on considerations of precision environment, and compatibility with vehicle interface commands, an electronic control, makes available many functions that logically provide the information required for engine system checkout and diagnosis.

41 CFR 102-38.115 - What are the specific reporting requirements for negotiated sales?

Code of Federal Regulations, 2014 CFR

2014-01-01

... 41 Public Contracts and Property Management 3 2014-01-01 2014-01-01 false What are the specific... Management Federal Property Management Regulations System (Continued) FEDERAL MANAGEMENT REGULATION PERSONAL PROPERTY 38-SALE OF PERSONAL PROPERTY Sales Process Negotiated Sales § 102-38.115 What are the specific...

41 CFR 102-38.115 - What are the specific reporting requirements for negotiated sales?

Code of Federal Regulations, 2012 CFR

2012-01-01

... 41 Public Contracts and Property Management 3 2012-01-01 2012-01-01 false What are the specific... Management Federal Property Management Regulations System (Continued) FEDERAL MANAGEMENT REGULATION PERSONAL PROPERTY 38-SALE OF PERSONAL PROPERTY Sales Process Negotiated Sales § 102-38.115 What are the specific...

41 CFR 102-38.115 - What are the specific reporting requirements for negotiated sales?

Code of Federal Regulations, 2011 CFR

2011-01-01

... 41 Public Contracts and Property Management 3 2011-01-01 2011-01-01 false What are the specific... Management Federal Property Management Regulations System (Continued) FEDERAL MANAGEMENT REGULATION PERSONAL PROPERTY 38-SALE OF PERSONAL PROPERTY Sales Process Negotiated Sales § 102-38.115 What are the specific...

41 CFR 102-38.115 - What are the specific reporting requirements for negotiated sales?

Code of Federal Regulations, 2010 CFR

2010-07-01

... 41 Public Contracts and Property Management 3 2010-07-01 2010-07-01 false What are the specific... Management Federal Property Management Regulations System (Continued) FEDERAL MANAGEMENT REGULATION PERSONAL PROPERTY 38-SALE OF PERSONAL PROPERTY Sales Process Negotiated Sales § 102-38.115 What are the specific...

41 CFR 102-38.115 - What are the specific reporting requirements for negotiated sales?

Code of Federal Regulations, 2013 CFR

2013-07-01

... 41 Public Contracts and Property Management 3 2013-07-01 2013-07-01 false What are the specific... Management Federal Property Management Regulations System (Continued) FEDERAL MANAGEMENT REGULATION PERSONAL PROPERTY 38-SALE OF PERSONAL PROPERTY Sales Process Negotiated Sales § 102-38.115 What are the specific...

Space Tug avionics definition study. Volume 2: Avionics functional requirements

NASA Technical Reports Server (NTRS)

1975-01-01

Flight and ground operational phases of the tug/shuttle system are analyzed to determine the general avionics support functions that are needed during each of the mission phases and sub-phases. Each of these general support functions is then expanded into specific avionics system requirements, which are then allocated to the appropriate avionics subsystems. This process is then repeated at the next lower level of detail where these subsystem requirements are allocated to each of the major components that comprise a subsystem.

Developing Formal Correctness Properties from Natural Language Requirements

NASA Technical Reports Server (NTRS)

Nikora, Allen P.

2006-01-01

This viewgraph presentation reviews the rationale of the program to transform natural language specifications into formal notation.Specifically, automate generation of Linear Temporal Logic (LTL)correctness properties from natural language temporal specifications. There are several reasons for this approach (1) Model-based techniques becoming more widely accepted, (2) Analytical verification techniques (e.g., model checking, theorem proving) significantly more effective at detecting types of specification design errors (e.g., race conditions, deadlock) than manual inspection, (3) Many requirements still written in natural language, which results in a high learning curve for specification languages, associated tools and increased schedule and budget pressure on projects reduce training opportunities for engineers, and (4) Formulation of correctness properties for system models can be a difficult problem. This has relevance to NASA in that it would simplify development of formal correctness properties, lead to more widespread use of model-based specification, design techniques, assist in earlier identification of defects and reduce residual defect content for space mission software systems. The presentation also discusses: potential applications, accomplishments and/or technological transfer potential and the next steps.

40 CFR 63.7535 - How do I monitor and collect data to demonstrate continuous compliance?

Code of Federal Regulations, 2012 CFR

2012-07-01

... activities, including, as applicable, calibration checks and required zero and span adjustments. A monitoring...-control periods, or required monitoring system quality assurance or control activities in data averages... data according to this section and the site-specific monitoring plan required by § 63.7505(d). (b) You...

40 CFR 63.7535 - How do I monitor and collect data to demonstrate continuous compliance?

Code of Federal Regulations, 2011 CFR

2011-07-01

... activities, including, as applicable, calibration checks and required zero and span adjustments. A monitoring...-control periods, or required monitoring system quality assurance or control activities in data averages... data according to this section and the site-specific monitoring plan required by § 63.7505(d). (b) You...

Model-based software design

NASA Technical Reports Server (NTRS)

Iscoe, Neil; Liu, Zheng-Yang; Feng, Guohui; Yenne, Britt; Vansickle, Larry; Ballantyne, Michael

1992-01-01

Domain-specific knowledge is required to create specifications, generate code, and understand existing systems. Our approach to automating software design is based on instantiating an application domain model with industry-specific knowledge and then using that model to achieve the operational goals of specification elicitation and verification, reverse engineering, and code generation. Although many different specification models can be created from any particular domain model, each specification model is consistent and correct with respect to the domain model.

A review method for UML requirements analysis model employing system-side prototyping.

PubMed

Ogata, Shinpei; Matsuura, Saeko

2013-12-01

User interface prototyping is an effective method for users to validate the requirements defined by analysts at an early stage of a software development. However, a user interface prototype system offers weak support for the analysts to verify the consistency of the specifications about internal aspects of a system such as business logic. As the result, the inconsistency causes a lot of rework costs because the inconsistency often makes the developers impossible to actualize the system based on the specifications. For verifying such consistency, functional prototyping is an effective method for the analysts, but it needs a lot of costs and more detailed specifications. In this paper, we propose a review method so that analysts can verify the consistency among several different kinds of diagrams in UML efficiently by employing system-side prototyping without the detailed model. The system-side prototype system does not have any functions to achieve business logic, but visualizes the results of the integration among the diagrams in UML as Web pages. The usefulness of our proposal was evaluated by applying our proposal into a development of Library Management System (LMS) for a laboratory. This development was conducted by a group. As the result, our proposal was useful for discovering the serious inconsistency caused by the misunderstanding among the members of the group.

Overland Mobility of the Forces in the Canadian Environment,

DTIC Science & Technology

1977-01-14

to refer to prior kowledge and this is typified by the I examples of data bank Input In Fig 1. The data ublch Is used may be broadly classifiled as...I tics, suspension as a mobility limiting factor. k. The Enzine Compartment - selection of engines, power require- Seats, load factors, fuel...consumption, specific bulk, specific weight, cooling requirements, parasitic power losses. cooling - system design, fan types and applications, air flow in 3

Automated systems to identify relevant documents in product risk management

PubMed Central

2012-01-01

Background Product risk management involves critical assessment of the risks and benefits of health products circulating in the market. One of the important sources of safety information is the primary literature, especially for newer products which regulatory authorities have relatively little experience with. Although the primary literature provides vast and diverse information, only a small proportion of which is useful for product risk assessment work. Hence, the aim of this study is to explore the possibility of using text mining to automate the identification of useful articles, which will reduce the time taken for literature search and hence improving work efficiency. In this study, term-frequency inverse document-frequency values were computed for predictors extracted from the titles and abstracts of articles related to three tumour necrosis factors-alpha blockers. A general automated system was developed using only general predictors and was tested for its generalizability using articles related to four other drug classes. Several specific automated systems were developed using both general and specific predictors and training sets of different sizes in order to determine the minimum number of articles required for developing such systems. Results The general automated system had an area under the curve value of 0.731 and was able to rank 34.6% and 46.2% of the total number of 'useful' articles among the first 10% and 20% of the articles presented to the evaluators when tested on the generalizability set. However, its use may be limited by the subjective definition of useful articles. For the specific automated system, it was found that only 20 articles were required to develop a specific automated system with a prediction performance (AUC 0.748) that was better than that of general automated system. Conclusions Specific automated systems can be developed rapidly and avoid problems caused by subjective definition of useful articles. Thus the efficiency of product risk management can be improved with the use of specific automated systems. PMID:22380483

A computer-based specification methodology

NASA Technical Reports Server (NTRS)

Munck, Robert G.

1986-01-01

Standard practices for creating and using system specifications are inadequate for large, advanced-technology systems. A need exists to break away from paper documents in favor of documents that are stored in computers and which are read and otherwise used with the help of computers. An SADT-based system, running on the proposed Space Station data management network, could be a powerful tool for doing much of the required technical work of the Station, including creating and operating the network itself.

Workstation Segment Specification for the World-Wide Military Command and Control (WWMCCS) Information System (WIS)

DTIC Science & Technology

1989-07-01

software eventually, and which indicate the general thrust of evolution and growth capabilities required of the workstation segment. These GRAY sections...configuration control over the evolution of the system. (" - The transition from the WWMCCS Standard ADP system to WIS will be gradual and will be...has been designed to support the workstation needs required for most WIS users, and is the workstation that will support the long-term evolution of

Research and development for Onboard Navigation (ONAV) ground based expert/trainer system: ONAV entry knowledge requirements specification update

NASA Technical Reports Server (NTRS)

Bochsler, Daniel C.

1988-01-01

A revised version of expert knowledge for the onboard navigation (ONAV) entry system is given. Included is some brief background information together with information describing the knowledge that the system does contain.

LogiKit - assisting complex logic specification and implementation for embedded control systems

NASA Astrophysics Data System (ADS)

Diglio, A.; Nicolodi, B.

2002-07-01

LogiKit provides an overall lifecycle solution. LogiKit is a powerful software engineering case toolkit for requirements specification, simulation and documentation. LogiKit also provides an automatic ADA software design, code and unit test generator.

NASA software specification and evaluation system design, part 1

NASA Technical Reports Server (NTRS)

1976-01-01

The research to develop methods for reducing the effort expended in software and verification is reported. The development of a formal software requirements methodology, a formal specifications language, a programming language, a language preprocessor, and code analysis tools are discussed.

[CRISPR/Cas system for genome editing in pluripotent stem cells].

PubMed

Vasil'eva, E A; Melino, D; Barlev, N A

2015-01-01

Genome editing systems based on site-specific nucleases became very popular for genome editing in modern bioengineering. Human pluripotent stem cells provide a unique platform for genes function study, disease modeling, and drugs testing. Consequently, technology for fast, accurate and well controlled genome manipulation is required. CRISPR/Cas (clustered regularly interspaced short palindromic repeat/CRISPR-associated) system could be employed for these purposes. This system is based on site-specific programmable nuclease Cas9. Numerous advantages of the CRISPR/Cas system and its successful application to human stem cells provide wide opportunities for genome therapy and regeneration medicine. In this publication, we describe and compare the main genome editing systems based on site-specific programmable nucleases and discuss opportunities and perspectives of the CRISPR/Cas system for application to pluripotent stem cells.

Autonomous Integrated Receive System (AIRS) requirements definition. Volume 2: Design and development

NASA Technical Reports Server (NTRS)

Chie, C. M.; White, M. A.; Lindsey, W. C.; Davarian, F.; Dixon, R. C.

1984-01-01

Functional requirements and specifications are defined for an autonomous integrated receive system (AIRS) to be used as an improvement in the current tracking and data relay satellite system (TDRSS), and as a receiving system in the future tracking and data acquisition system (TDAS). The AIRS provides improved acquisition, tracking, bit error rate (BER), RFI mitigation techniques, and data operations performance compared to the current TDRSS ground segment receive system. A computer model of the AIRS is used to provide simulation results predicting the performance of AIRS. Cost and technology assessments are included.

40 CFR 62.14620 - What site-specific documentation is required?

Code of Federal Regulations, 2010 CFR

2010-07-01

... the incinerator and associated air pollution control systems within the standards established under... required? 62.14620 Section 62.14620 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED...) Procedures for receiving, handling, and charging waste. (3) Incinerator startup, shutdown, and malfunction...

Mission Operations Center (MOC) - Precipitation Processing System (PPS) Interface Software System (MPISS)

NASA Technical Reports Server (NTRS)

Ferrara, Jeffrey; Calk, William; Atwell, William; Tsui, Tina

2013-01-01

MPISS is an automatic file transfer system that implements a combination of standard and mission-unique transfer protocols required by the Global Precipitation Measurement Mission (GPM) Precipitation Processing System (PPS) to control the flow of data between the MOC and the PPS. The primary features of MPISS are file transfers (both with and without PPS specific protocols), logging of file transfer and system events to local files and a standard messaging bus, short term storage of data files to facilitate retransmissions, and generation of file transfer accounting reports. The system includes a graphical user interface (GUI) to control the system, allow manual operations, and to display events in real time. The PPS specific protocols are an enhanced version of those that were developed for the Tropical Rainfall Measuring Mission (TRMM). All file transfers between the MOC and the PPS use the SSH File Transfer Protocol (SFTP). For reports and data files generated within the MOC, no additional protocols are used when transferring files to the PPS. For observatory data files, an additional handshaking protocol of data notices and data receipts is used. MPISS generates and sends to the PPS data notices containing data start and stop times along with a checksum for the file for each observatory data file transmitted. MPISS retrieves the PPS generated data receipts that indicate the success or failure of the PPS to ingest the data file and/or notice. MPISS retransmits the appropriate files as indicated in the receipt when required. MPISS also automatically retrieves files from the PPS. The unique feature of this software is the use of both standard and PPS specific protocols in parallel. The advantage of this capability is that it supports users that require the PPS protocol as well as those that do not require it. The system is highly configurable to accommodate the needs of future users.

Generic Educational Knowledge Representation for Adaptive and Cognitive Systems

ERIC Educational Resources Information Center

Caravantes, Arturo; Galan, Ramon

2011-01-01

The interoperability of educational systems, encouraged by the development of specifications, standards and tools related to the Semantic Web is limited to the exchange of information in domain and student models. High system interoperability requires that a common framework be defined that represents the functional essence of educational systems.…

46 CFR 62.35-5 - Remote propulsion-control systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 2 2014-10-01 2014-10-01 false Remote propulsion-control systems. 62.35-5 Section 62.35... AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-5 Remote propulsion-control systems. (a) Manual propulsion control. All vessels having remote propulsion control from the navigating...

46 CFR 62.35-5 - Remote propulsion-control systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 2 2013-10-01 2013-10-01 false Remote propulsion-control systems. 62.35-5 Section 62.35... AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-5 Remote propulsion-control systems. (a) Manual propulsion control. All vessels having remote propulsion control from the navigating...

46 CFR 62.35-5 - Remote propulsion-control systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Remote propulsion-control systems. 62.35-5 Section 62.35... AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-5 Remote propulsion-control systems. (a) Manual propulsion control. All vessels having remote propulsion control from the navigating...

46 CFR 62.35-5 - Remote propulsion-control systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Remote propulsion-control systems. 62.35-5 Section 62.35... AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-5 Remote propulsion-control systems. (a) Manual propulsion control. All vessels having remote propulsion control from the navigating...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2012 CFR

2012-10-01

... of the alarm and extinguishing systems, the fire extinguishers, means of access to different... dampers and the number identifying each system. (2) Ventilation diagram including dampers and other fire control features. (3) Details of alarm systems. (4) Details of extinguishing systems, including fire mains...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2014 CFR

2014-10-01

..., the arrangement of the alarm and extinguishing systems, the fire extinguishers, means of access to... other fire control features. (3) Details of alarm systems. (4) Details of extinguishing systems, including fire mains, carbon dioxide, clean agent, foam, and sprinkling systems. (e) Marine engineering. For...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2013 CFR

2013-10-01

..., the arrangement of the alarm and extinguishing systems, the fire extinguishers, means of access to... other fire control features. (3) Details of alarm systems. (4) Details of extinguishing systems, including fire mains, carbon dioxide, clean agent, foam, and sprinkling systems. (e) Marine engineering. For...

46 CFR 127.110 - Plans and specifications required for new construction.

Code of Federal Regulations, 2011 CFR

2011-10-01

.... (v) Fluid-driven power and control systems. (vi) Through-hull penetrations and shell connections...) Steering and steering-control systems. (4) Propulsion and propulsion-control systems. (5) Piping diagrams... personnel in the control and observation of the propulsion systems and machinery spaces, or to reduce the...

36 CFR 1234.10 - What are the facility requirements for all records storage facilities?

Code of Federal Regulations, 2014 CFR

2014-07-01

... the HVAC systems, fire alarm and fire protection systems. Manual switching between sources of service... elements are protected by a properly installed, properly maintained wet-pipe automatic sprinkler system, as... must provide documentation that the facility has a fire suppression system specifically designed to...

46 CFR 62.35-5 - Remote propulsion-control systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 2 2012-10-01 2012-10-01 false Remote propulsion-control systems. 62.35-5 Section 62.35... AUTOMATION Requirements for Specific Types of Automated Vital Systems § 62.35-5 Remote propulsion-control systems. (a) Manual propulsion control. All vessels having remote propulsion control from the navigating...

[Multimag-M magnetotherapy system of the new generation].

PubMed

Borisov, A G; Grigor'ev, E M; Gurzhin, S G; Zhulev, V I; Kriakov, V G; Proshin, E M

2007-01-01

The Multimag-M microprocessor chronomagne-totherapy system of the new generation is described. The system provides on-line diagnosis of the pulse parameters and the breathing rate during a biotechnical feedback session. The requirements to the system software, as well as its specific features and design principles, are considered.

Energy Emergency Management Information System (EEMIS): Functional requirements

NASA Astrophysics Data System (ADS)

1980-10-01

These guidelines state that in order to create the widest practicable competition, the system's requirements, with few exceptions, must be expressed in functional terms without reference to specific hardware or software products, and that wherever exceptions are made a statement of justification must be provided. In addition, these guidelines set forth a recommended maximum threshold limit of annual contract value for schedule contract procurements.

40 CFR 270.16 - Specific part B information requirements for tank systems.

Code of Federal Regulations, 2010 CFR

2010-07-01

... (CONTINUED) SOLID WASTES (CONTINUED) EPA ADMINISTERED PERMIT PROGRAMS: THE HAZARDOUS WASTE PERMIT PROGRAM... systems in which ignitable, reactive, or incompatible wastes are to be stored or treated, a description of...

Procedure for Electronic Management of Rulemaking and Other Docketed Records in the Federal Docket Management System

EPA Pesticide Factsheets

This procedure identifies the specific requirements, processes and supporting documents EPA uses to electronically manage rulemaking and other docketed records in the Federal Docket Management System (FDMS).

Final report bridge design system analysis and modernization.

DOT National Transportation Integrated Search

2016-09-27

The Bridge Design System (BDS) is an in-house software program developed by the Michigan Department of Transportations : (MDOT) Bridge Design Unit. The BDS designs bridges according to the required specifications, and outputs corresponding design ...

Space shuttle visual simulation system design study

NASA Technical Reports Server (NTRS)

1973-01-01

A recommendation and a specification for the visual simulation system design for the space shuttle mission simulator are presented. A recommended visual system is described which most nearly meets the visual design requirements. The cost analysis of the recommended system covering design, development, manufacturing, and installation is reported. Four alternate systems are analyzed.

46 CFR 128.450 - Liquid-mud systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 4 2010-10-01 2010-10-01 false Liquid-mud systems. 128.450 Section 128.450 Shipping...: EQUIPMENT AND SYSTEMS Design Requirements for Specific Systems § 128.450 Liquid-mud systems. (a) Liquid-mud... this chapter. (b) Tanks for oil-based liquid mud must be fitted with tank vents equipped with flame...

Outline of Standards for Migration to Integrated Online System.

ERIC Educational Resources Information Center

Millen, Celeste; And Others

Intended to describe an ideal system for William Madison Randall Library at the University of North Carolina-Wilmington, this outline presents specific system requirements that would build on and enhance features available on the current system while moving toward a truly integrated system with built-in possibilities for expansion and improvements…

Direct Energy Conversion for Low Specific Mass In-Space Power and Propulsion

NASA Technical Reports Server (NTRS)

Scott, John H.; George, Jeffrey A.; Tarditi, Alfonso G.

2013-01-01

"Changing the game" in space exploration involves changing the paradigm for the human exploration of the Solar System, e.g, changing the human exploration of Mars from a three-year epic event to an annual expedition. For the purposes of this assessment an "annual expedition" capability is defined as an in-space power & propulsion system which, with launch mass limits as defined in NASA s Mars Architecture 5.0, enables sending a crew to Mars and returning them after a 30-day surface stay within one year, irrespective of planetary alignment. In this work the authors intend to show that obtaining this capability requires the development of an in-space power & propulsion system with an end-to-end specific mass considerably less than 3 kg/kWe. A first order energy balance analysis reveals that the technologies required to create a system with this specific mass include direct energy conversion and nuclear sources that release energy in the form of charged particle beams. This paper lays out this first order approximation and details these conclusions.

Beyond the Baseline 1991: Proceedings of the Space Station Evolution Symposium. Volume 1: Space Station Freedom, part 1

NASA Technical Reports Server (NTRS)

1991-01-01

Personnel responsible for Advanced Systems Studies and Advanced Development within the Space Station Freedom Program reported on the results of their work to date. The results of SSF Advanced Studies provide a road map for the evolution of Freedom in terms of user requirements, utilization and operations concepts, and growth options for distributed systems. Regarding these specific systems, special attention is given to: highlighting changes made during restructuring; description of growth paths thru the follow-on and evolution phases; identification of minimum impact provisions to allow flexibility in the baseline; and identification of enhancing and enabling technologies. Products of these tasks include: engineering fidelity demonstrations and evaluations of advanced technology; detailed requirements, performance specifications, and design accommodations for insertion of advanced technology.

A Sensitivity Study of the Aircraft Vortex Spacing System (AVOSS) Wake Predictor Algorithm to the Resolution of Input Meteorological Profiles

NASA Technical Reports Server (NTRS)

Rutishauser, David K.; Butler, Patrick; Riggins, Jamie

2004-01-01

The AVOSS project demonstrated the feasibility of applying aircraft wake vortex sensing and prediction technologies to safe aircraft spacing for single runway arrivals. On average, AVOSS provided spacing recommendations that were less than the current FAA prescribed spacing rules, resulting in a potential airport efficiency gain. Subsequent efforts have included quantifying the operational specifications for future Wake Vortex Advisory Systems (WakeVAS). In support of these efforts, each of the candidate subsystems for a WakeVAS must be specified. The specifications represent a consensus between the high-level requirements and the capabilities of the candidate technologies. This report documents the beginnings of an effort to quantify the capabilities of the AVOSS Prediction Algorithm (APA). Specifically, the APA horizontal position and circulation strength output sensitivity to the resolution of its wind and turbulence inputs is examined. The results of this analysis have implications for the requirements of the meteorological sensing and prediction systems comprising a WakeVAS implementation.

A usability evaluation toolkit for In-Vehicle Information Systems (IVISs).

PubMed

Harvey, Catherine; Stanton, Neville A; Pickering, Carl A; McDonald, Mike; Zheng, Pengjun

2011-05-01

Usability must be defined specifically for the context of use of the particular system under investigation. This specific context of use should also be used to guide the definition of specific usability criteria and the selection of appropriate evaluation methods. There are four principles which can guide the selection of evaluation methods, relating to the information required in the evaluation, the stage at which to apply methods, the resources required and the people involved in the evaluation. This paper presents a framework for the evaluation of usability in the context of In-Vehicle Information Systems (IVISs). This framework guides designers through defining usability criteria for an evaluation, selecting appropriate evaluation methods and applying those methods. These stages form an iterative process of design-evaluation-redesign with the overall aim of improving the usability of IVISs and enhancing the driving experience, without compromising the safety of the driver. Copyright © 2010 Elsevier Ltd and The Ergonomics Society. All rights reserved.

From user needs to system specifications: multi-disciplinary thematic seminars as a collaborative design method for development of health information systems.

PubMed

Scandurra, I; Hägglund, M; Koch, S

2008-08-01

This paper presents a new multi-disciplinary method for user needs analysis and requirements specification in the context of health information systems based on established theories from the fields of participatory design and computer supported cooperative work (CSCW). Whereas conventional methods imply a separate, sequential needs analysis for each profession, the "multi-disciplinary thematic seminar" (MdTS) method uses a collaborative design process. Application of the method in elderly homecare resulted in prototypes that were well adapted to the intended user groups. Vital information in the points of intersection between different care professions was elicited and a holistic view of the entire care process was obtained. Health informatics-usability specialists and clinical domain experts are necessary to apply the method. Although user needs acquisition can be time-consuming, MdTS was perceived to efficiently identify in-context user needs, and transformed these directly into requirements specifications. Consequently the method was perceived to expedite the entire ICT implementation process.

Formal analysis of imprecise system requirements with Event-B.

PubMed

Le, Hong Anh; Nakajima, Shin; Truong, Ninh Thuan

2016-01-01

Formal analysis of functional properties of system requirements needs precise descriptions. However, the stakeholders sometimes describe the system with ambiguous, vague or fuzzy terms, hence formal frameworks for modeling and verifying such requirements are desirable. The Fuzzy If-Then rules have been used for imprecise requirements representation, but verifying their functional properties still needs new methods. In this paper, we propose a refinement-based modeling approach for specification and verification of such requirements. First, we introduce a representation of imprecise requirements in the set theory. Then we make use of Event-B refinement providing a set of translation rules from Fuzzy If-Then rules to Event-B notations. After that, we show how to verify both safety and eventuality properties with RODIN/Event-B. Finally, we illustrate the proposed method on the example of Crane Controller.

46 CFR 128.440 - Bilge systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 4 2011-10-01 2011-10-01 false Bilge systems. 128.440 Section 128.440 Shipping COAST... AND SYSTEMS Design Requirements for Specific Systems § 128.440 Bilge systems. (a) Except as provided by this section, each bilge system must comply with §§ 56.50-50 and 56.50-55 of this chapter. (b) If...

46 CFR 128.440 - Bilge systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 4 2012-10-01 2012-10-01 false Bilge systems. 128.440 Section 128.440 Shipping COAST... AND SYSTEMS Design Requirements for Specific Systems § 128.440 Bilge systems. (a) Except as provided by this section, each bilge system must comply with §§ 56.50-50 and 56.50-55 of this chapter. (b) If...

SIMS prototype system 1: Design data brochure. [solar heating system

NASA Technical Reports Server (NTRS)

1978-01-01

A prototype solar heating and hot water system using air as the collector fluid and a pebble bed for heat storage was designed for installation into a single family dwelling. The system, subsystem, and installation requirements are described. System operation and performance are discussed, and procedures for sizing the system to a specific site are presented.

Engineering Specification for Large-aperture UVO Space Telescopes Derived from Science Requirements

NASA Technical Reports Server (NTRS)

Stahl, H. Philip; Postman, Marc; Smith, W. Scott

2013-01-01

The Advance Mirror Technology Development (AMTD) project is a three year effort initiated in FY12 to mature by at least a half TRL step six critical technologies required to enable 4 to 8 meter UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND result in a high-performance low-cost low-risk system. To provide the science community with options, we are pursuing multiple technology paths. We have assembled an outstanding team from academia, industry, and government with extensive expertise in astrophysics and exoplanet characterization, and in the design/manufacture of monolithic and segmented space telescopes. A key accomplishment is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints.

Managing Complex IT Security Processes with Value Based Measures

DOE Office of Scientific and Technical Information (OSTI.GOV)

Abercrombie, Robert K; Sheldon, Frederick T; Mili, Ali

2009-01-01

Current trends indicate that IT security measures will need to greatly expand to counter the ever increasingly sophisticated, well-funded and/or economically motivated threat space. Traditional risk management approaches provide an effective method for guiding courses of action for assessment, and mitigation investments. However, such approaches no matter how popular demand very detailed knowledge about the IT security domain and the enterprise/cyber architectural context. Typically, the critical nature and/or high stakes require careful consideration and adaptation of a balanced approach that provides reliable and consistent methods for rating vulnerabilities. As reported in earlier works, the Cyberspace Security Econometrics System provides amore » comprehensive measure of reliability, security and safety of a system that accounts for the criticality of each requirement as a function of one or more stakeholders interests in that requirement. This paper advocates a dependability measure that acknowledges the aggregate structure of complex system specifications, and accounts for variations by stakeholder, by specification components, and by verification and validation impact.« less

Advanced Platform Systems Technology study. Volume 2: Trade study and technology selection

NASA Technical Reports Server (NTRS)

1983-01-01

Three primary tasks were identified which include task 1-trade studies, task 2-trade study comparison and technology selection, and task 3-technology definition. Task 1 general objectives were to identify candidate technology trade areas, determine which areas have the highest potential payoff, define specific trades within the high payoff areas, and perform the trade studies. In order to satisfy these objectives, a structured, organized approach was employed. Candidate technology areas and specific trades were screened using consistent selection criteria and considering possible interrelationships. A data base comprising both manned and unmanned space platform documentation was used as a source of system and subsystem requirements. When requirements were not stated in the data base documentation, assumptions were made and recorded where necessary to characterize a particular spacecraft system. The requirements and assumptions were used together with the selection criteria to establish technology advancement goals and select trade studies. While both manned and unmanned platform data were used, the study was focused on the concept of an early manned space station.

Information Science Panel joint meeting with Imaging Science Panel

NASA Technical Reports Server (NTRS)

1982-01-01

Specific activity in information extraction science (taken to include data handling) is needed to: help identify the bounds of practical missions; identify potential data handling and analysis scenarios; identify the required enabling technology; and identify the requirements for a design data base to be used by the disciplines in determining potential parameters for future missions. It was defined that specific analysis topics were a function of the discipline involved, and therefore no attempt was made to define any specific analysis developments required. Rather, it was recognized that a number of generic data handling requirements exist whose solutions cannot be typically supported by the disciplines. The areas of concern were therefore defined as: data handling aspects of system design considerations; enabling technology for data handling, with specific attention to rectification and registration; and enabling technology for analysis. Within each of these areas, the following topics were addressed: state of the art (current status and contributing factors); critical issues; and recommendations for research and/or development.

Model-Drive Architecture for Agent-Based Systems

NASA Technical Reports Server (NTRS)

Gradanin, Denis; Singh, H. Lally; Bohner, Shawn A.; Hinchey, Michael G.

2004-01-01

The Model Driven Architecture (MDA) approach uses a platform-independent model to define system functionality, or requirements, using some specification language. The requirements are then translated to a platform-specific model for implementation. An agent architecture based on the human cognitive model of planning, the Cognitive Agent Architecture (Cougaar) is selected for the implementation platform. The resulting Cougaar MDA prescribes certain kinds of models to be used, how those models may be prepared and the relationships of the different kinds of models. Using the existing Cougaar architecture, the level of application composition is elevated from individual components to domain level model specifications in order to generate software artifacts. The software artifacts generation is based on a metamodel. Each component maps to a UML structured component which is then converted into multiple artifacts: Cougaar/Java code, documentation, and test cases.

System Engineering of Photonic Systems for Space Application

NASA Technical Reports Server (NTRS)

Watson, Michael D.; Pryor, Jonathan E.

2014-01-01

The application of photonics in space systems requires tight integration with the spacecraft systems to ensure accurate operation. This requires some detailed and specific system engineering to properly incorporate the photonics into the spacecraft architecture and to guide the spacecraft architecture in supporting the photonics devices. Recent research in product focused, elegant system engineering has led to a system approach which provides a robust approach to this integration. Focusing on the mission application and the integration of the spacecraft system physics incorporation of the photonics can be efficiently and effectively accomplished. This requires a clear understanding of the driving physics properties of the photonics device to ensure proper integration with no unintended consequences. The driving physics considerations in terms of optical performance will be identified for their use in system integration. Keywords: System Engineering, Optical Transfer Function, Optical Physics, Photonics, Image Jitter, Launch Vehicle, System Integration, Organizational Interaction

Comparison of Commercial Electromagnetic Interface Test Techniques to NASA Electromagnetic Interference Test Techniques

NASA Astrophysics Data System (ADS)

Smith, V.

2000-11-01

This report documents the development of analytical techniques required for interpreting and comparing space systems electromagnetic interference test data with commercial electromagnetic interference test data using NASA Specification SSP 30237A "Space Systems Electromagnetic Emission and Susceptibility Requirements for Electromagnetic Compatibility." The PSpice computer simulation results and the laboratory measurements for the test setups under study compare well. The study results, however, indicate that the transfer function required to translate test results of one setup to another is highly dependent on cables and their actual layout in the test setup. Since cables are equipment specific and are not specified in the test standards, developing a transfer function that would cover all cable types (random, twisted, or coaxial), sizes (gauge number and length), and layouts (distance from the ground plane) is not practical.

Frictionless segmented mechanics for controlled space closure

PubMed Central

Andrade, Ildeu

2017-01-01

ABSTRACT Extraction spaces may be needed to achieve specific orthodontic goals of positioning the dentition in harmony with the craniofacial complex. However, the fundamental reality that determines the occlusion final position is the control exerted by the orthodontist while closing the extraction spaces. A specific treatment objective may require the posterior teeth to remain in a constant position anteroposteriorly as well as vertically, while the anterior teeth occupy the entire extraction site. Another treatment objective may require the opposite, or any number of intentional alternatives of extraction site closure. The present case report describes a simple controlled segmented mechanic system that permitted definable and predictable force systems to be applied and allowed to predict the treatment outcome with confidence. This case was presented to the Brazilian Board of Orthodontics and Dentofacial Orthopedics (BBO) in partial fulfillment of the requirements for Diplomate certification. PMID:28444016

Comparison of Commercial Electromagnetic Interface Test Techniques to NASA Electromagnetic Interference Test Techniques

NASA Technical Reports Server (NTRS)

Smith, V.; Minor, J. L. (Technical Monitor)

2000-01-01

This report documents the development of analytical techniques required for interpreting and comparing space systems electromagnetic interference test data with commercial electromagnetic interference test data using NASA Specification SSP 30237A "Space Systems Electromagnetic Emission and Susceptibility Requirements for Electromagnetic Compatibility." The PSpice computer simulation results and the laboratory measurements for the test setups under study compare well. The study results, however, indicate that the transfer function required to translate test results of one setup to another is highly dependent on cables and their actual layout in the test setup. Since cables are equipment specific and are not specified in the test standards, developing a transfer function that would cover all cable types (random, twisted, or coaxial), sizes (gauge number and length), and layouts (distance from the ground plane) is not practical.