bluuebunny/crossref_metadata_2025_split huggingface dataset:
Altered integrity of the right arcuate fasciculus as a trait marker of schizophrenia: A sibling study using tractography‐based analysis of the whole brain
Authors: Wu Chen‐Hao , Hwang Tzung‐Jeng , Chen Yu‐Jen , Hsu Yun‐Chin , Lo Yu‐Chun , Liu Chih‐Min , Hwu Hai‐Gwo , Liu Chen‐Chung , Hsieh Ming H. , Chien Yi Ling , Chen Chung‐Ming , Isaac Tseng Wen‐Yih 
Published: November 2014

AbstractTrait markers of schizophrenia aid the dissection of the heterogeneous phenotypes into distinct subtypes and facilitate the genetic underpinning of the disease. The microstructural integrity of the white matter tracts could serve as a trait marker of schizophrenia, and tractography‐based analysis (TBA) is the current method of choice. Manual tractography is time‐consuming and limits the analysis to preselected fiber tracts. Here, we sought to identify a trait marker of schizophrenia from among 74 fiber tracts across the whole brain using a novel automatic TBA method. Thirty‐one patients with schizophrenia, 31 unaffected siblings and 31 healthy controls were recruited to undergo diffusion spectrum magnetic resonance imaging at 3T. Generalized fractional anisotropy (GFA), an index reflecting tract integrity, was computed for each tract and compared among the three groups. Ten tracts were found to exhibit significant differences between the groups with a linear, stepwise order from controls to siblings to patients; they included the right arcuate fasciculus, bilateral fornices, bilateral auditory tracts, left optic radiation, the genu of the corpus callosum, and the corpus callosum to the bilateral dorsolateral prefrontal cortices, bilateral temporal poles, and bilateral hippocampi. Posthoc between‐group analyses revealed that the GFA of the right arcuate fasciculus was significantly decreased in both the patients and unaffected siblings compared to the controls. Furthermore, the GFA of the right arcuate fasciculus exhibited a trend toward positive symptom scores. In conclusion, the right arcuate fasciculus may be a candidate trait marker and deserves further study to verify any genetic association.Hum Brain Mapp 36:1065–1076, 2015.© 2014 Wiley Periodicals, Inc.
SYSTEMS ENGINEERING RE‐ENERGIZED: Impacts of the Revised DoD Acquisition Process
Authors: Lake Jerry 
Published: November 2014

AbstractThe Department of Defense acquisition process has gone through a decade of change intended to improve war fighting capabilities, to field products with a shorter cycle time, and to lower system life cycle costs. The intensity of change has increased during 1991 in response to the short comings of prior changes to correct acquisition problems and to deal with declining budgets, changing threats, and reduced manpower. The focus of this paper is on the major changes taken to re‐energize systems engineering. In addition, issues are highlighted that have resulted from several technical documents under revision at the same time without a formal integration or lead effort. This paper calls for someone in authority to take the lead to ensure that conflicting signals are not given to industry by the several different standards under revision. Harmonization is imperative if the rising expectations of defense and public leaders are to be realized in an environment of shrinking manpower and fiscal resources.
LOCAL SYSTEM ENGINEERING EDUCATION PROGRAM IGNITION AND SUSTENANCE
Authors: Grady Jeffrey O. 
Published: November 2014

ABSTRACTAcademic institutions, industry, and other components of our society are continuing a long standing trend toward fragmenting and specializing the arts and sciences related to the development of complex systems. The absence of an effective countervailing force encouraging generalism poses serious problems for American industry. Several examples exist illustrating how this trend can be turned around.
RESPONSIBLE SYSTEM DEVELOPMENT
Authors: Hemsley David L. 
Published: November 2014

AbstractDeveloping systems which meet all the requirements of system specifications is a difficult task. Hardware and software design engineers take responsibility for only a portion of the system specification when developing hardware or software components. Often, no one is responsible for making sure that all of the system requirements are accounted for during the development of a system. The result of mismatches between system requirements and system components is a prolonged system integration and delivery schedule as errors are often not detected until a system is being integrated or tested against the system specification. Every requirement in a system specification should be accounted for during the development of a system. System development methodology and software tools have been developed to ensure that system components accurately reflect the system specification.
Extending RDD‐100 to Meet Project Demands
Authors: Osaki Herb , Pampe >Mark 
Published: November 2014

AbstractRDD‐100 is a commercial off the shelf (COTS) automation tool used for systems engineering applications. It is based on a rigorous approach using an Element, Relationship, Attribute (ERA) database, graphical input and output formats, and built‐in engineering data consistency checks. It also includes the capability to expand the definition (schema) of the ERA database and to create reports to manipulate, format, and print the database contents. The following describes the process which establishes a new ERA schema and data extraction reports that are used with the inherent capabilities of RDD‐100 to produce deliverable, military compliant specifications from a systems engineering database.
Improved System Understanding by Similarities and Analogies
Authors: Asbiomsen O. Andreas 
Published: November 2014

AbstractA set of definitions of system engineering concepts is the point of departure of this paper. Those definitions are generic and cover system and its life cycle, the system engineering discipline and the system engineering process.A system engineer must be able to analyze and understand systems, first on a conceptual level that is independent of technology, i.e., a technology free functional analysis. More detailed knowledge and deeper insight into a concrete technology are required later. The system engineer must be able to move from one system project to another, sometimes with entirely different technologies and requirements.The paper points to a need for greater flexibility and easier adaptability on the part of the system engineer. This means that the knowledge base and professional tool box of the system engineer must meet this requirement also. A way this requirement can be met is by system similarity and the principle of analogy between functional principles.
Systems Engineering for Commercial Space Programs
Authors: Fisher Jack 
Published: November 2014

AbstractA systems engineering approach has been developed at the Space and Communications Group (SCG) of Hughes Aircraft Company which has proven highly successful for commercial space programs. Success is defined by the profit‐making delivery and operation of advanced communications satellites. The key elements of the approach include:
Assignment of a team of highly motivated individuals with knowledge in each of the key technical areas of the program.
Co‐location of the team with the satellite program office.
Use of the same team from the beginning of the program through system test and onorbit check‐out.
Assignment to the team of the lead role as the program technical conscience and problem solvers.
A well understood systems engineering process.
The process includes maintenance of estimates of system performance throughout the development and test phases, careful management of design resources and interfaces, and a strong linkage between system requirements and verification planning and implementation. MIL‐STD‐499A requirements were not considered in the development of the process. Nevertheless, comparison with MIL‐STD‐499A reveals a number of similarities which are noted.
Systems Engineering with the Right Requirements: An Approach for Assessing User Needs
Authors: Borden Chester S. , Smith Jeffrey H. , Griesel Ann 
Published: November 2014

AbstractThis paper presents a methodology for assessing diverse user requirements in a rapidly changing technological environment. The purpose is to provide a more accurate assessment of user needs at the first point of entry for the customer into the systems engineering process. Applying a customer/provider orientation to the traditional user/developer environment, a product oriented approach is adopted to link the process to a Total Quality Management (TQM) philosophy. The approach is designed to elicit user needs directly from interested parties and using the analysis process described, map the user needs to a set of prioritized common functional requirements. The methodology has been applied within a publicly funded research and development institution in an information technology context and has received broad organizational support and positive feedback. The approach is illustrated with a case study from the information technology arena.
NEEDS, RATIONALE AND CONCEPTUAL ALTERNATIVES FOR COMBATTING AIRCRAFT POLLUTIONS
Authors: Asbjornsen O. Andreas , Paragiri Neil R. 
Published: November 2014

AbstractDepletion of the ozone layer in the upper atmosphere has the potential to change its chemistry and the Earth's environment. Various pollutants affect this depletion, which started as early as in the 1930's. High altitude aircraft bring pollution to a fairly quiet range of the atmosphere, closer to the ozone layer than ground pollution. The aircraft pollution problem represents a large scale integrated system engineering problem where many requirements conflict and must be traded off. The system engineering principles have been applied to a conceptual study of the aircraft transportation system, its interface with the global environment and the social structures in the society and to the analysis and conceptual design of plans to combat the pollution effects from civil jet aircraft.
REQUIREMENTS MANAGEMENT/TRACEABILITY: A CASE STUDY ‐ NASA'S NATIONAL LAUNCH SYSTEM
Authors: Pinkerton Mary Beth , Fogle Frank R. 
Published: November 2014

AbstractPoorly defined and poorly managed system requirements result in increased programmatic costs. To stay within the bounds of cost and schedule and to ensure a quality end product, concise, well managed and traceable systems requirements are a necessity. This paper will discuss the implementation of the requirements management tool, Document Director, at the National Aeronautics and Space Administration (NASA) Marshall Space Flight Center (MSFC) as related to the definition and management of the launch vehicle system level requirements for the National Launch System (NLS). In addition, the set‐up process, immediate and projected benefits to systems engineers, and lessons learned from implementing a systems engineering based requirements management tool on a major aerospace program will be described.
REQUIREMENTS MANAGEMENT: A CASE STUDY ‐ NASA'S ASSURED CREW RETURN VEHICLE
Authors: Hooks Ivy , Stone Dennis 
Published: November 2014

AbstractThis paper describes how the system requirements were developed for the Assured Crew Return Vehicle (ACRV) and analyzes the changes to those requirements over the past three years. The project manager took decisive steps to ensure good initial system requirements. The “goodness” of the requirements can be assessed by the character and amount of changes that have occurred.
SPECIALTY ENGINEERING INNOVATIONS ON THE U.S. ARMY JOINT STARS GSM BLOCK I UPGRADE CONTRACT
Authors: Iliff Randall C. , Rewinkel Cindy J. 
Published: November 2014

AbstractThe Joint Surveillance Target Attack Radar System (Joint STARS) proved highly successful during Operation Desert Storm. Although unique circumstances in Operation Desert Storm permitted onequipment contractor support of the system, the U.S. Army is committed to operation and maintenance by the soldier.The new Joint STARS Block I Ground Station Module (GSM) is produced by Motorola Government Electronics Group, and must satisfy a formidable mix of requirements. The system must substantially exceed the complexity and performance levels of the Interim Ground Station Module (IGSM) sent to the Gulf, yet be operable and maintainable by soldiers rather than contractor engineers and technicians. This paper documents the unique interactions and degree of integration associated with the specialty engineering functions on the Joint STARS Block I GSM program, and illustrates the success that can be achieved.
SYSTEM ENGINEERING IN THE REGULATORY ENVIRONMENT
Authors: Romine D. Ted 
Published: November 2014

AbstractIn October 1987, the Nuclear Regulatory Commission (NRC) established the Center for Nuclear Waste Regulatory Analyses (the Center) at Southwest Research Institute in San Antonio, Texas, to provide sustained high‐quality research and technical assistance in support of NRC regulatory responsibilities under the Nuclear Waste Policy Act (the Act), as amended. A key role of the Center is to assist the NRC in the development and implementation of the Systematic Regulatory Analysis (SRA) process – a systems approach to defining and implementing the regulatory program for a deep geologic repository for the permanent disposal of high‐level radioactive waste.This paper identifies the major regulatory challenges that led to the NRC recognition of the need for a systems approach. It then describes the adaptations of classic system design techniques to the definition of the “streamlined” regulatory process “system.” This is followed by a summary description of the resulting SRA process. In addition, there is a brief discussion of potential adaptations of the process that would produce significant additional efficiencies if applied at the start of a regulatory program.
FLOWING REQUIREMENTS TO SUBCONTRACTS
Authors: Knaggs Howard J 
Published: November 2014

AbstractDuring the past 40 years, the defense industry has experienced phenomenal growth in the amount of work subcontracted by prime defense contractors. Industry wide, subcontracted work has risen from 9 percent in the 1950s to over 53 percent today. Along with the rise in subcontracted work, has come an increase in problems associated with purchased products. More products are being received which do not perform as expected, or are delivered late because the design or testing took much longer than anticipated. The source of these problems, however, can quite often be traced back to poor requirements descriptions initially given to the subcontractors. This paper describes a preferred process for flowing technical requirements from prime contract sources to a subcontract, to create an adequate definition of the products being procured. This process has been developed by a multi‐discipline team from the Boeing Defense & Space Group, sponsored by the Subcontracts Management organization, and is applicable to all subcontract procurements involving requirements which have been flowed from a prime contract.
The Supertool: QFD, Structured Analysis & Concurrent Engineering Combined
Authors: Dick Michael J. 
Published: November 2014

ABSTRACTTo be competitive, companies must efficiently develop products that meet their customers' needs. Three established methodologies, Quality Function Deployment, Structured Analysis, and Concurrent Engineering combine to form a superpowerful technique to help companies be competitive.Quality Function Deployment (QFD) is a universally‐used, powerful tool for relating the customer requirements to detailed engineering requirements. It is frequently referred to as “the voice of the customer”. Structured Analysis is a technique of systematically decomposing a system into progressively more detailed parts. A “picture oriented” method, this technique has a history of providing visibility into large systems. It is useful on small systems as well. Concurrent Engineering simultaneously deals with marketing, design and production concerns; traditional approaches treat each of these concerns separately. Concurrent Engineering emphasizes design for cost, design for manufacturing and assembly, design for serviceability, design for reliability, design for maintainability… in short, design for “X”. This emphasis on design for “X” begins at the very conception of the product.This paper describes how these three methods, QFD, Structured Analysis, and QFD interrelate and then describes a unique way to combine them into a supertool for assuring product competitiveness.
UTILIZATION OF QUALITY FUNCTION DEPLOYMENT AS A TOOL FOR THE SYSTEMS ENGINEER
Authors: Adams Tamara J. , Amos Richard W. , Wyskida Alan R. , Maddux Gary A. 
Published: November 2014

ABSTRACTThis paper presents an overview of the utilization of QFD as a tool for the systems engineer. QFD can be used in the systems engineering process for both requirements definition/allocation and resource allocation management. Relevant examples of the application of QFD in the development of U.S. Army missile systems and in a program management role will be used to illustrate the benefit of this tool in the systems engineering process.
INDIRECT EXPERIMENTATION FOR SYSTEM OPTIMIZATION: A PARADIGM BASED ON DESIGN DEPENDENT PARAMETERS
Authors: Fabrycky Wolter J. 
Published: November 2014

AbstractA large gap exists between the commitment to technology, system configuration, life‐cycle cost and available knowledge about the impact of these commitments during system operation. This gap is particularly acute during conceptual and preliminary system design. More powerful approaches are needed to narrow the gap. This paper presents a paradigm for indirect experimentation based on normative models form the field of operations research. The paradigm proceeds from the identification of design dependent parameters which link design characteristics and operational outcomes. When applied during conceptual and preliminary design, this linkage helps to reduce the gap between knowledge and commitment. The normative models provide a basis for system optimization early in the life cycle.
Distributed Communication Network Systems Performance Modeling
Authors: Basta Robert A. , Kraemer Bruce P. , Bond Walter P. , Billhartz Thomas J. 
Published: November 2014

AbstractThis paper will describe the use of system performance modeling and simulation in designing large, complex distributed communication network systems. These systems include both local and wide area configurations, utilizing a variety of protocols, hardware, communication media, etc. This paper will show how Harris was able to apply the information obtained from the modeling activity to understand the behavior of the systems being architected and to verify that specific system performance requirements are met.
SYSTEM ENGINEERING CONCEPT DEMONSTRATION ‐ AN OVERVIEW
Authors: LaMonica Frank S. 
Published: November 2014

AbstractThis technical paper provides an overview of Rome Laboratory's Research & Development Program in the area of System Engineering. In particular, it describes the objectives of an exploratory development effort entitled “System Engineering Concept Demonstration” (SECD), the activities that were pursued under the effort, and its results. It serves as an introduction to other papers [Comer 1992], [Ortiz 1992], and [Pariseau & Stuebing 1992], which provide further detail on the technology and demonstrations that resulted. Rome Laboratory's future plans to develop Systems Engineering technology are also identified.
RAPID PROTOTYPING VIA AUTOMATIC SOFTWARE CODE GENERATION FROM FORMAL SPECIFICATIONS: A CASE STUDY
Authors: Rahmani S. , Stone A.G. , Luk W.S. , Sweet S.M. 
Published: November 2014

AbstractThis paper describes an approach for defining system and software requirements and validating them through rapid prototyping. It provides the results of a case study for generating prototype software (representing the total system hardware and software) directly and automatically from the requirements. The paper addresses system/software definitions, which include the requirements and design (architecture). The approach consists of modeling and prototyping. The case study described here applied this approach to selected systems of Boeing 747‐400 aircraft. A formal model of system specification was generated. The rapid prototyping task automatically generated thousands of Ada source lines of code from the specification model. The tool used on the project was Statemate. The software was executed successfully the first time. The functions and behavior of the system were demonstrated and validated by its users. This study indicated that early execution and validation of system requirements, through the use of formal modeling and rapid prototyping with direct user involvement, can be accomplished.
System Modeling for V&V
Authors: Clark B. E. , Frank G. A. 
Published: November 2014

AbstractSimulation and formal models are becoming an accepted part of the early stages of system design. This paper discusses the use of executable system models during system design and implementation.RTI recently developed an abstract executable model of the operating system developed for an avionics test bed based on the PAVE PILLAR architecture.The target hardware consisted of two processing clusters, each with five VHSIC 1750A modules connected by a parallel bus and a system mass memory. The three components are connected by two optical high‐speed data busses. The modeling was done while both the hardware and software were under development. The process of developing and validating the models produced a significant V&V payoff for the design teams. Formal modeling forced early consideration of hardware/software, inter‐module, and inter‐application interfaces that were overlooked during the system design process. This led to forecasting system problems that normally would not have been discovered until system integration. This paper will review the modeling effort and show, in a systems engineering context, how abstract modeling can serve as a powerful method for early discovery of interface errors normally not found until integration.
SYSTEMS ENGINEERING IN THE AUTOMOTIVE INDUSTRY
Authors: Percivall George S. 
Published: November 2014

AbstractDue to recent changes, automobile engineering has reached a critical point requiring more formal methods. This situation is familiar to the aerospace industry where increasing complexity resulted in the formalization of systems engineering. The principles of aerospace systems engineering are the basis for automotive systems engineering. Several aspects must be changed to meet the automotive environment. Change agents must be identified and placed in strategic positions to implement systems engineering. A key ingredient to automotive systems engineering is the development of the automotive engineers with systems engineering capabilities.