bluuebunny/crossref_metadata_2025_split huggingface dataset:
Mild chronic kidney disease is associated with cognitive function in patients presenting at a memory clinic
Authors: Romijn Marloes D.M. , van Marum Rob J. , Emmelot‐Vonk Mariëlle H. , Verhaar Harald J.J. , Koek Huiberdina L. 
Published: November 2014

ObjectiveIn dialysis‐dependent and severe chronic kidney disease (CKD) patients, cognitive impairment is found in 16–29%. In community‐dwelling population without dementia mixed results have been observed. We investigated the relationship between renal function and cognition in patients from a memory clinic.MethodsWe performed a cross‐sectional study of consecutive patients from a memory clinic between 2005 and 2009. Renal function was estimated with the Modification of Diet in Renal Diseases (MDRD) and Cockcroft‐Gault (CG) formulas, and categorized into ordinal groups: reference ≥60 ml/min/1.73 m2, mild CKD 45–59 ml/min/1.73 m2 and moderate CKD <45 ml/min/1.73 m2. Cognitive function was dichotomized (Mini‐Mental State Examination (MMSE) ≥24 vs. <24). We performed multiple logistic regression analyses with adjustment for potential confounders.ResultsThe cohort comprised 581 patients (mean age 77 ± 10 years). With the MDRD, there were 74 (12%) cases with moderate CKD and 108 (18%) with mild CKD. With the CG, these prevalences were 144 (30%) and 130 (27%). In mild CKD patients, a significant relationship was found between cognitive function and CKD according to the MDRD‐formula [adjusted OR 2.10; 95%CI 1.09–4.05]. In moderate CKD patients, no significant adjusted associations were found. In patients without dementia, significant adjusted associations were found between CKD and MMSE (MDRD: mild CKD [OR 5.09; 95%CI 1.17–22.14] and moderate CKD [OR 5.03; 95%CI 1.10–22.98]; CG: mild CKD [OR 6.16; 95%CI 1.17–32.50] and moderate CKD [OR 5.60; 95%CI 1.01–30.91]).ConclusionThis study showed a significant association between mild CKD and impaired cognitive function in patients from a memory clinic, especially in patients without dementia. Copyright © 2014 John Wiley & Sons, Ltd.
Encoding and retrieval along the long axis of the hippocampus and their relationships with dorsal attention and default mode networks: The HERNET model
Authors: Kim Hongkeun 
Published: November 2014

ABSTRACTThe encoding of sensory input is intertwined with external attention, whereas retrieval is intrinsically related to internal attention. This study proposes a model in which the encoding of sensory input involves mainly the anterior hippocampus and the external attention network, whereas retrieval, the posterior hippocampus and the internal attention network. This model is referred to as the HERNET (hippocampal encoding/retrieval and network) model. Functional neuroimaging studies have identified two intrinsic large‐scale networks closely associated with external and internal attention, respectively. The dorsal attention network activates during any externally oriented mental activity, whereas the default mode network shows increased activity during internally oriented mental activity. Therefore, the HERNET model may predict the activation of the anterior hippocampus and the dorsal attention network during the encoding and activation of the posterior hippocampus and the default mode network during retrieval. To test this prediction, this study provides a meta‐analysis of three memory‐imaging paradigms: subsequent memory, laboratory‐based recollection, and autobiographical memory retrieval. The meta‐analysis included 167 individual studies and 2,856 participants. The results provide support for the HERNET model and suggest that the anterior–posterior gradient of encoding and retrieval includes amygdala regions. More broadly, humans continuously oscillate between external and internal attention and thus between encoding and retrieval processes. These oscillations may involve repetitive and spontaneous activity switching between the anterior hippocampus/dorsal attention network and the posterior hippocampus/default mode network. © 2014 Wiley Periodicals, Inc.
Fundamentals of Systems Engineering at NASA
Authors: Chamberlain Robert G. , Shishko Robert 
Published: November 2014

AbstractThe fundamental concepts and process of systems engineering as they apply in the context of the National Aeronautics and Space Administration are described. In particular: Systems and systems engineering are defined, and the objectives of systems engineering are discussed. The doctrine of successive refinement is presented, and the associated spiral model of the systems engineering process is described. The various phases of the project cycle for major systems acquired by NASA are examined.This paper is based on material being prepared for the first draft of the NASA Systems Engineering Handbook. Consequently, the authors are seeking constructive criticism.
THE NASA SYSTEMS ENGINEERING TRAINING PROGRAM
Authors: Pivirotto Donna 
Published: November 2014

AbstractNASA has instituted a Systems Engineering Training Program as part of its Program and Project Management Training Initiative (PPMI). The PPMI has several elements, including Project Management, Program Control, Human Development and Systems Engineering. PPMI also includes special training such as Source Evaluation Boards, SRM&QA, TQM, and Program/Project Management shared experience workshops. The Systems Engineering Training Program develops and delivers systems engineering courses NASA‐wide. In addition, the program includes an intercenter working group which holds monthly videocons to exchange information on system engineering techniques and practices NASA‐wide. A NASA Systems Engineering Handbook is being developed which will:
Represent a basic NASA‐tailored systems engineering process.
Provide reference pointers to material on systems engineering techniques, technologies and practices.
Provide documentation of material which will be used in the courses offered by NASA.
SPECIFICATION OF A SYSTEMS ENGINEERING FRAMEWORK FOR A SEAMLESS SYSTEMS ENGINEERING PROCESS
Authors: Krimm Ronald C. 
Published: November 2014

AbstractIn putting a Systems Engineering methodology and associated processes in place, it was determined that computer automation was essential as manual techniques were complicated, time consuming and generally not feasible. A project has been established to define, prototype and demonstrate a viable concept to specify a Systems Engineering environment. A core capability, the requirements management process, was selected as the starting point with provisions for integration of the other Systems Engineering elements. An evolutionary development approach is planned based on a successful proof‐of‐concept prototype demonstration. Special attention will be given to the integration of software management within a Systems Engineering structure.
SYSTEMS ENGINEERING ROLE IN PROCESS MANAGEMENT
Authors: Sarris Anthony K. 
Published: November 2014

AbstractTo improve the efficiency of American industry, it is necessary to create an environment to manage and control the processes that enable the creation, deployment, operation, support and disposal of complex systems. Steps toward realizing that environment include: process definition, organizational development, assignment of responsibility, and personnel training. Automated support tools are essential to assist with the definition and management of the environment, as well as with personnel training. The tools must include: a broad range of modeling elements, a 3‐schema representation system, stored content (e.g. database) and application logic acquisition tools, and a commonsense knowledgebase for product definition. This paper will provide a background regarding these requirements and will describe efforts to meet the requirements through the development and application of advanced information system technologies.
MAPPING SYSTEMS ENGINEERING PRINCIPLES AND PRACTICES TO COMMERCIAL SECTOR ACTIVITY
Authors: Iliff Randall C. 
Published: November 2014

AbstractThe Systems Engineering (SE) process provides a valuable mechanism for management of complex developmental programs but application has been almost exclusively limited to the Defense sector. One of the key challenges facing the SE community is to extend these capabilities to applications in the Commercial sector. There are many fundamental differences in the conduct of operations between these two sectors.However much we believe in the basic systems engineering process, these differences must be considered when we speak of “exporting” techniques. Individual elements of the SE process must be packaged in such a way that they can be selectively applied, and must clearly be seen as providing a positive return on investment.This paper offers a basic framework with which to identify the elements of SE in the Defense sector, a general comparison with the equivalent activity in various portions of the Commercial sector, and observations regarding implementation strategy and opportunities.
A CASE STUDY: THE PRACTICE OF SYSTEMS ENGINEERING ON THE E‐3 AWACS RADAR SYSTEM IMPROVEMENT PROGRAM
Authors: Hyer Scott A. 
Published: November 2014

ABSTRACTA program currently being conducted to upgrade the radar within the United States Air Force (USAF) E‐3 Airborne Warning and Control System (AWACS) serves to illustrate examples in modern day systems engineering practices. Of particular interest are efforts in the traceability and interpretation of requirements, the design and verification of interfaces, the reduction of risk with a brassboard flight program, the design review process, the integration of the system, and the leadership and coordination applied to the many engineering and management disciplines which were involved. This paper will examine approaches taken to solve problems in these areas and why these approaches were effective. Examples are presented to bridge the gap between ideals and reality and to reinforce the main objectives of each approach.
RELIABILITY MODELING OF HARDWARE/SOFTWARE SYSTEMS TO SUPPORT ARCHITECTURAL TRADE‐OFFs
Authors: Goddard Peter L. , Friedman Michael A. 
Published: November 2014

ABSTRACTDeveloping complex systems to meet the demands of the current military and commercial marketplaces requires careful architectural design to ensure optimal robustness within the expected use environment. Modeling the reliability of systems that combine hardware and software elements to achieve needed system functionality has been difficult or impossible due to the paucity of techniques for including software and the effects of software failures into system reliability models.This paper reports on and extends the research into system and software modeling techniques which was recently completed by the authors for Hughes Aircraft Company under contract to the U. S. Air Force, Rome Laboratory. An overview of the reliability model development process for combined hardware/software systems which focuses on creating a model which accurately includes the impact of software is provided. A brief discussion of how to use the results of the modeling to assess alternative design approaches is included.
DEVELOPMENT AND IMPLEMENTATION OF AN INTEGRATED SYSTEMS ENGINEERING ENVIRONMENT
Authors: Harwell R.M. 
Published: November 2014

AbstractIn 1989, Lockheed established a plan to develop an Integrated Systems Engineering Environment which would help us integrate and manage the requirements development process through fluid interfaces among advance design, operations analysis, and design management tools. The ultimate goal is to enable systems engineering (SE) to better meet its objective – To assure the fully integrated development of a product (under controlled cost/schedule constraints) which meets the customer's needs. A System Specification, including system architecture has been developed and feasibility proofing of concepts completed. Several software houses have expressed interest in coding and marketing the system as a commercial systems engineering tool.
CATALYST: AUTOMATING SYSTEMS ENGINEERING IN THE 21ST CENTURY
Authors: Comer Edward R. 
Published: November 2014

AbstractThis paper describes the concept for a future automated environment supporting systems engineering, named Catalyst. Catalyst will enhance the effectiveness of the systems engineering process to produce more successful, higher quality systems. Sponsored by the Air Force Rome Laboratory, the Systems Engineering Concept Demonstration Program researched the needs and defined the requirements and conceptual design of Catalyst. The paper discusses the operational concept, architecture, and important features and characteristics for Catalyst.
SYSTEM ENGINEERING CONCEPT DEMONSTRATION (SECD) PROCESS MODEL
Authors: Ortiz Alberto 
Published: November 2014

AbstractThis technical paper will present a summary of the SECD Process Model Task sponsored by Rome Laboratory at Griffiss Air Force Base, New York. An introduction to the SECD Program is presented in the “SECD ‐ Overview” [LaMonica 1992]. The SECD Process Model is a system acquisition and development model with emphasis on system engineering activities over the entire system life cycle. The Process Model is a graphical and textual representation of the system engineering life cycle activities, agents, flows, feedbacks, and work products. This interactive Process Model provides a multidimensional view of government acquisition and contractor development activities. In the context of the SECD Program, the Process Model validates the System /Segment Specification (SSS) requirements and demonstrates coverage and completeness of the system engineering process.
COMPUTER‐AIDED SYSTEM ENGINEERING TOOLS —THE DESIGN SRATM FAMILY OF TOOLS
Authors: Elliott Michael W. , Vickers Archie D. 
Published: November 2014

AbstractThe authors and others at PRC have developed a family of computer‐automated system engineering (CASE) tools which support system requirements analysis, automatic specification preparation, requirements traceability, and rapid access to system engineering reference data. The tools include the following:
Design SRATM (requirements analysis tool)
Spec WriterTM (automatic specification tool)
SpecREFTM (digital image library access)*
SpecTRACETM (requirement traceability)*
SpecEditorTM (specification editing tool)*
These tools have been developed specifically to support the DOD system requirements analysis (SRA) process. They are also used in commercial systems engineering applications.Elements of the SRA process and their specific implementation in PRC CASE tools described in this paper include the following:
Functional analysis and decomposition
Requirements allocation
Design constraint analysis
Automatic specification preparation
Requirements verification support
Requirements traceability
* Currently in development.
INCORPORATING ACTIVE ADVICE AND GUIDANCE IN HUMAN‐COMPUTER INTERACTION
Authors: Ramparany Fano , Minor Earl 
Published: November 2014

AbstractComputer systems supporting complex human activities or complex processes require user interfaces that can build and maintain explicit models of the user, the process, and the system itself.Such interfaces could adapt to the user, and could provide focused advice and guidance support at any point during the process. We qualify such adaptive user interfaces as “intelligent”.Benefits which are expected from intelligent interfaces include a drastic reduction in the learning time required to efficiently use the environment, and efficient teaching of how to conduct the process for novice users.In this article, we propose a generic architecture for designing intelligent user interfaces1The main components of this architecture are:
a task scheduler
an activity selector
an activity configurer
a process context modeler
the interface with the domain process specific modules and functions.
These components and their organization are described.An implementation of an intelligent user interface using this architecture will be presented. This user interface was built for the Knowledge Engineering Workbench (KEW), developed within the Esprit project ACKnowledge [MSW89]. KEW is a workbench that integrates complementary tools and techniques dedicated to knowledge acquisition.
THE EVOLUTION OF SYSTEMS ENGINEERING
Authors: Reilly Norman B. 
Published: November 2014

ABSTRACTOver the past forty years, systems engineering has methodically evolved through the Staircase, Early Prototype, Spiral and Rapid Development models. The evolution is characterized by successively deeper penetrations of prototyping concepts into the traditional staircase paradigm. Early prototyping penetrates to the requirements level. The spiral model penetrates to the design level. Rapid Development, the newest innovation, engulfs the entire process resulting in repeated operational deliveries. Each paradigm continues to have its useful niche, but selection of the wrong model for a given task invariably enhances the probability of failure. There is a need for continued education and acceptance of the newer approaches within the technical management and systems engineering communities.
Special Training Needs of system Engineers
Authors: Brinn Derek E. Mc 
Published: November 2014

AbstractThe objectives of this paper are to (1) show that Systems Engineering embraces two distinct disciplines, that each has distinct training needs, that the training needs of the system architect/optimizer are not currently being satisfied, and that both industry and academia would benefit from rectifying the situation and (2) describe the nature of the training needs and how they might be supplied.
SYSTEMS ENGINEERING AT THE U.S. MILITARY ACADEMY
Authors: Kays James L. 
Published: November 2014

AbstractThis paper describes the rationale, structure and operational concept for implementing an undergraduate systems engineering program at the U.S. Military Academy. The rationale for the program derives from the purpose and vision of the Academy and from the needs of tomorrow's Army. The structure of the program is influenced by leading systems engineering programs in the nation and the constraints of the Academy curriculum. The implementation of the program serves the needs of cadet education, faculty development and linking the Academy to the industry it serves – the U.S. Army.
THE PROJECT AS AN INTEGRATING ELEMENT OF A MASTER PROGRAM IN SYSTEMS ENGINEERING
Authors: Brown Ian T , Chia David T H , Doukas Louis 
Published: November 2014

AbstractsAt the Royal Melbourne Institute of Technology graduate engineers from all engineering disciplines undertake a Master Degree program in systems engineering which introduces these experienced engineers to the concepts and processes used in systems engineering practice. The integration of these concepts and processes into the real world of technology systems and in particular into the world of the individual course participant depends heavily on the successful completion of a minor thesis project. Our experience in the management of 105 systems engineering projects has identified a number of problems and success factors and has led to the development of a procedure for the successful management of these projects.
Structured Techniques: Where's the Payoff?
Authors: Silves Michael 
Published: November 2014

AbstractMuch discussion and hand wringing has gone on about formal approaches to software development. Over the years a number of apparently disparate approaches to software development have appeared on the scene. This paper attempts to make some sense out of the whole thing by looking at the history of software development methods from the perspective of methods as partitioning tools. It traces the history from structured programming through data modeling focusing on advantages and foibles of the various approaches. The underlying theme is that an organized methodology is neither good nor bad; it is merely necessary.
777 OPERATIONAL REQUIREMENTS DEVELOPMENT METHODOLOGY
Authors: Underwood Hubert H. 
Published: November 2014

ABSTRACTThis paper addresses a formal methodology for the 777 Airplane operational requirements development. The advantages of a formal model are explored and the tool set utilized is discussed. The extensions in definition of the operational requirements and the traceability and interdependence of the functional and performance requirements are shown.Layered state and transition diagrams showing operational sequences and related requirements illustrates the methodology.
1.5.1 TEAM WORKSHOPS: A SYSTEM ANSWER TO IPT ISSUES
Authors: Sheard Sarah A. , Popick Paul R. , Van Scoyoc Thomas G. 
Published: November 2014

AbstractIn an Integrated Product Team environment, the systems engineering focus can be diluted unless specific steps are taken to focus the key people working on each team, and to improve their understanding and teamwork. Team Launches and Team Workshops have been created to educate teams just coming under contract and ongoing teams, respectively. The workshops teach team techniques in a structured, facilitated setting, over a two‐ to four‐day period, during which teams concentrate on establishing system and project goals, roles, responsibilities, and plans. This paper describes the agendas and processes involved in producing Team Launches and Team Workshops.
1.5.3 MULTIMEDIA DOCUMENTATION FOR THE SOFTWARE MAINTAINER
Authors: Garthwaite Jean D. , Huff George A. 
Published: November 2014

AbstractIn the DOD, eighty percent of the life‐cycle cost of a software‐intensive system is for maintenance, and the cost of fixing software increases by an order of magnitude as it is passed from developer to maintainer. Much of the requisite knowledge about the system's mission, software structure, and maintenance tool set and procedures resides with the developers of a software‐intensive system. While some of this knowledge may actually be documented, it is seldom readily accessible and software maintainers must painstakingly rediscover it. To reduce the learning curve among software maintainers and the associated life‐cycle costs for specific systems, new software documentation approaches must be developed.This paper describes the HAC/RMPE Software Maintenance Tutor, a multimedia prototype which has proved effective in capturing system‐specific developer knowledge in a form that is useful to the maintainers. The tutor was built for the Higher Authority Communication/Rapid Message Processing Element (HAC/RMPE) and has been in use since September 1993 as a means of familiarizing new personnel with the HAC/RMPE software. New materials are continually being added. The tutor combines elements of a training system and an on‐line performance aid, and represents a unique approach for supplementing the software maintenance training process.The HAC/RMPE Tutor shows promise for filling a critical gap in the training of software maintainers and thereby reducing the overall system life‐cycle cost. It also represents a generic form of multimedia documentation which has applications in many other domains.