bluuebunny/crossref_metadata_2025_split huggingface dataset:
A SYSTEM CONCEPT FOR AN ADVANCED VEHICLE CONTROL SYSTEM
Authors: Mackey David E. , Mackey William F. , Mackey William F. 
Published: November 2014

AbstractThis paper explores a system concept for an Advanced Vehicle Control System (AVCS). The progression of highway design and construction has resulted from an evolution of technologies, inventions, organizational creations, and legislative acts supporting the development of a national interstate transportation system (Mackey, 1994). Until now, highway design and construction has been the domain of civil engineers concerned with highway structures, materials loading, traffic patterns, and supporting facilities. However, the growing need for intelligent vehicle‐highway systems (IVHS) requires that traditional civil engineering disciplines be integrated with computers, communications, and eventually fully automated vehicles. This paper's thesis suggests that the complex highway transportation of the late 20th century and the 21st century can benefit from the collaboration of systems engineers and civil engineers. This paper identifies and prototypes an AVCS concept with roadside computers controlling the lateral and longitudinal movements of a vehicle.
REENGINEERING PROCESS OF A CORPORATE FINANCIAL SYSTEM: A SYSTEMS ENGINEERING SOLUTION
Authors: Ghahramani Bahador 
Published: November 2014

AbstractThis paper analyzes, evaluates, and recommends Reengineering of a Corporate Financial System (CFS) that is currently in operation in a leading global communication company. The analysis highlights the problem areas in the CFS regulatory financial statements of the Fortune 500 Company. As a result of this Reengineering process, a new state‐of‐the‐art system will be proposed that will eliminate the existing bottlenecks.The initial purpose of the CFS was to serve the regulatory requirements inherent in the communication services line of the business. Over time, however, the system has evolved to support multiple business units. Today, the CFS General Ledger process serves the financial community of the corporate Communications, Communications Products, Information Management Services and Corporate Headquarters business units and divisions. The purpose of the CFS General Ledger System is to receive, on‐line, detailed financial data from various feeder systems, perform validations and balancing, allocations, update the General Ledger data base, and provide financial data for downstream systems in order to satisfy legal, regulatory, accounting and management decision making requirements. These functions are supported by numerous systems referred to as the “CFS Family of Systems”. They include the Corporate Financial Input System (CFIS), CFS Daily, Individual Allocation Systems, Corporate Financial Inquiry and Reporting System (CFIRS), and the Financial Reporting System. The on‐line interaction among these systems is analyzed in this paper.
USE OF INTERNET RETRIEVAL AND ACCESS TOOLS IN SUPPORT OF THE GODDARD SPACE FLIGHT CENTER
Authors: Nguyen Diem V. , Mackey William 
Published: November 2014

AbstractOften in the past, standards and new technology information have been available only in hardcopy form, with reproduction and mailing costs proving rather significant. In light of current budget constraints and in the interest of efficient communications, the Mission Operations and Data Systems Directorate (MO&DSD) New Technology and Data Standards Office recognizes the need for an online information server (OLIS). This server would allow
Dissemination of standards and new technology information throughout MO&DSD more quickly and economically
Online browsing and retrieval of documents that have been published for and by MO&DSD
Access to the Electronic Publishing System (EPS) of the International SpaceOps Symposium Organization (All NASA papers presented during the SpaceOps 96 Symposium will be retrievable through this EPS following the symposium.)
Setting up a semi‐permanent Internet Protocol (IP) multicast testbed to carry audio and video between two or more sitesThis paper explores a variety of available information servers and searching tools, their current capabilities and limitations, and the application of these tools to MO&DSD. Most importantly, the discussion focuses on the way this concept is being applied toward improving dissemination of documentation and improving documentation review processes.
PROVIDING AND SUPPORTING SYSTEMS ENGINEERING TOOLS FOR A LARGE ORGANIZATION
Authors: Jones David A. , Zeek David 
Published: November 2014

AbstractThe Texas Instruments Systems Group has developed a comprehensive infrastructure containing some unique features for providing and supporting systems engineering (SE) tools. This group has about 700 systems engineers in four cities connected by data networks.An SE design automation group acquires and provides standard software tools under a single budget.Software is provided on PC's from servers and on UNIX workstations. An arrangement allowing access to either PC or UNIX programs from a single desktop machine is under way. Current standard tools are CAE Soft radar programs, Designer, Foresight, Framemaker, Maple V, Mathcad Plus, MATLAB, LabVIEW, PV‐WAVE, QFD Designer, SLATE, and SPW.Software manuals are loaned through libraries or directly. About 600 volumes are in four libraries. Some unique problems arose and were overcome.On‐site SE‐specific support is provided, and over a half dozen methods are used to communicate with SE's.Current issues include interoperability and interfaces and standard tool methods.
A SYSTEM SYNTHESIS ENVIRONMENT FOR ENGINEERING OF COMPLEX NAVAL SYSTEMS
Authors: Salinas José , Harrison Steve 
Published: November 2014

AbstractThis paper presents research currently being conducted at the Naval Undersea Warfare Center (NUWC) on a system synthesis tool for the design and Engineering of Complex Naval Systems. The main purpose of this tool is to unify under a single information base all the domain specific engineering requirements necessary for the correct implementation of large engineering systems. In addition, the tool will provide the capacity for interfacing system design with current analysis and design programs. A hierarchical design implementation is adopted for the structure of the design based on either the physical or functional specification of the different architecture components. A demonstration of the tool which implements performance, RMA, and PM/FL information is discussed.
EXPLOITING THE TURNPIKE EFFECT IN ENGINEERING PROCESS SUPPORT
Authors: Jennings Larry E. , Tauber Stephen J. 
Published: November 2014

AbstractThe unavailability of a suitable commercial requirements management package led Sanders to develop such a tool in house. Use of the prototype Requirements Information Manager (RIM) on four active company projects identified desirable design modifications and additional capabilities which were required. These have been incorporated, making RIM a powerful, versatile tool. RIM is steadily being adopted within the Company's engineering community. Some culture shock occurs, but in general engineers are receptive to use of RIM. The ever increasing usage of RIM by engineers with urgent requirements‐related information needs has led to the pragmatic introduction of new features just in time for immediate use. Overall RIM's evolution (which still continues) demonstrates a beneficial application of the normally counterproductive turnpike effect. Availability of the tool has facilitated adherence to good engineering practice.
THE RASSP INTEGRATED SYSTEMS TOOL SET PROVIDES BETTER SYSTEM TRADE‐OFF STUDIES
Authors: Fry Charles 
Published: November 2014

AbstractThe goal of the ARPA/Tri‐Service‐sponsored Rapid Prototyping of Application Specific Signal Processors (RASSP) program is to reduce development and manufacturing time and cost of signal processors by a factor of four. Lockheed Martin's Advanced Technology Laboratories (ATL) RASSP team has developed an integrated systems engineering tool set. This tool set integrates Ascent Logic's RDD‐100, PRICE Systems parametric cost estimation models, and Management Sciences RAM‐ILS tools. This tool set provides systems engineers with cost and reliability estimation data within a systems engineering tool. This tool set is described and an example of the tool usage provided. The example demonstrates the value of the tool integration. This tool set enables systems engineers to estimate the life‐cycle costs and reliability early in the design process.
INTEGRATED OFFICE SUITE SOFTWARE, AND THE DEVELOPMENT OF AD HOC TOOLS
Authors: Jernigan Stephen S. 
Published: November 2014

Abstractad hoc: formed or used for specific or immediate problems or needs; fashioned from whatever is immediately available. Quite often we are faced with the need for an ad hoc computer‐based tool to eliminate the drudgery of boring, tedious, repetitious tasks. It could be something as simple as writing a macro in your current software application, or as difficult as the need to merge several different software applications. Other reasons for such tools could be: limited budgets, impending deadlines, resistance to change, unique processes/procedures, or a constant and rapidly evolving environment.Although there are advantages to procuring COTS software (eliminates development time, reduces internal maintenance, and assures technical support is readily available), there are times when it is necessary to develop an ad hoc tool. This paper describes an example of such a tool, developed from a very well integrated office suite software package.
TOP LEVEL REQUIREMENTS FOR AN ADVANCED SYSTEMS ENGINEERING INFORMATION REPOSITORY
Authors: Karangelen Nicholas E. , Hoang NgocDung T. , Howell Steven 
Published: November 2014

AbstractThe collection and management of data associated with the design and development of large complex systems is a critical activity supporting the systems engineering process. This paper describes the top level requirements for an advanced data repository supporting systems engineering activities in the development of large, complex, computer‐based systems. The repository requirements are addressed in three categories: repository functional requirements, non‐functional requirements (e.g., performance, dependability, scalability), and implementation standards.
ASSESSING INTEROPERABILITY USING A TOOL'S ARCHITECTURE
Authors: McCay Brian M. 
Published: November 2014

AbstractThis paper investigates the usefulness of examining the architecture of a tool to understand its ability to support interoperability. The purpose is to see if such assessments are useful and to suggest next steps. An information system architecture is defined, along with architecture technical performance criteria to help assess interoperability. The architectures of three well‐known commercial systems engineering tools (DOORS, RDD‐100, and SLATE) are then described. Each architecture is then subjectively scored against the interoperability performance criteria. The paper concludes that this approach is worth further investigation, and offers suggestions regarding refinements for such assessments.
ANALYZING PROCESSES WITH HANQ
Authors: Neimeier Hank , McGowan Clem 
Published: November 2014

AbstractWe view a process as a network of activity nodes that each take time and consume resources. Products and information flow between the nodes. Hands‐on Analytic Network Queuing (HANQ) is an approach and a computational tool to analyze the performance of such processes. Currently HANQ is a set of computational blocks implemented as a library for the Extend™ simulation language product. HANQ is based on a new computational paradigm (analytic risk evaluation and analytic queuing) that overcomes several of the limitations of discrete event simulation. Using HANQ one can compute the risk of an overall process's time, resource utilization, and costs (expressed as probability distributions) given the risks of the individual activities. Deterministic solutions simplify sensitivity and uncertainty analyses. HANQ supports activity based costing (ABC) and can handle time varying workloads and service rates. HANQ integrates performance, cost, and risk in a single model.
THE INTEGRATION OF COMMERCIAL OFF THE SHELF (COTS) MODELING AND SIMULATION TOOLS TO DESIGN AND OPTIMIZE WIDE AREA NETWORKS (WANs)
Authors: Plichta Eugene J. 
Published: November 2014

AbstractCommercial Off The Shelf (COTS) modeling and simulation tools are now available that are capable of automating many of the time‐consuming systems engineering processes employed to design and optimize Wide Area Networks (WANs). Because WANs continue to evolve and increase in complexity, automated modeling and simulation tools are now required to effectively perform design and optimization analyses. Through the use of modeling and simulation tools, systems engineers can generate WAN designs with lower costs, greater accuracy, and in a shorter amount of time than was previously possible. Ideally, one engineering tool would be utilized to solve all network design problems for all types of communications networks. Unfortunately, such a tool does not currently exist. Thus, the most pragmatic approach is for systems engineering organizations to select and integrate a multitude of COTS WAN modeling and simulation products that can interface and work harmoniously together.
Sharing Corporate Experience Through Electronic Repositories
Authors: Tavan Steven W. , Clapp Judith A. , Garvey Paul R. , Sateriale Alan 
Published: November 2014

AbstractWith the increase in scope and complexity of major system developments, project managers and systems engineers need to access timely information to make cost‐effective decisions. To share best practices and lessons‐learned, many companies have decided to capture their corporate memory and disseminate it through electronic repositories. This paper describes four repositories that are helping achieve these goals at The MITRE Corporation.
Trade‐off Analysis in Model Based Systems Engineering
Authors: Oliver David W. 
Published: November 2014

AbstractThis paper considers model based systems engineering which produces executable requirements and specifications. It describes the trade‐off step of the systems engineering technical process. It treats the inputs to the trade‐off step. It defines a behavior for systems engineers to follow in performing trade‐off analysis. That behavior is described as an executable meta‐process rather than as a methodology to make it independent of the plethora of methodologies.A meta‐process describes the steps to be taken in the process, the ordering of the steps and the inputs and outputs to each step. This is a behavioral picture. It also describes the information handled at each step and the relationships among the pieces of information. This is a static structural picture sometimes called an object model or an information model. The meta‐process defines the possible views of the information that will be handled.A methodology, in contrast, selects particular orderings of the engineering steps and particular views of information in particular notations for use by an engineering team.
Successful Vendor Collaboration Deployinga Requirements Management Tool
Authors: Rader Jock 
Published: November 2014

AbstractThe paper describes a successful partnership between Hughes Aircraft Company and the tool vendor, QSS, to transition a requirements management tool into operational use within the company. We provide an overview of the Hughes objective to migrate to common processes and tools across a range of engineering disciplines. A discussion of the difficulties in achieving wide spread use of new processes and tools sets the stage for a description of the Hughes approach for adopting a requirements management process supported by the vendor's tool, DOORS. We validate our approach with examples of Hughes accomplishments to date. Based on our experience, we emphasize the importance of a positive relationship with tool vendors. Transition achievements allow us to provide illustrations of customer‐vendor cooperation to achieve mutually desirable goals.
An Analysis of the Model Based Systems Engineering Process
Authors: Oliver David W. 
Published: November 2014

AbstractMuch of systems engineering has been performed by writing requirements and specifications primarily in text. An alternative approach preserves the proven best practices of systems engineering, but adds rigorous computer executable models to capture and record the information which describes the system. The requirements and specifications are executable and transformable. Text descriptions are joined to the models so that the proven best practices are not replaced; they are augmented.This paper analyzes the systems engineering process using executable models of behavior and executable models of structure. The structure models are compatible with the traditions of mechanical engineering, electrical engineering and modern object‐oriented software.A major goal of this work is to provide a convenient separation of the concerns of the systems engineer and to use abstraction to make the sub‐processes as simple as possible.
COMMON MODELS FOR CONFIGURATION MANAGEMENT AND AUTHORIZATION MANAGEMENT IN SYSTEMS ENGINEERING ENVIRONMENTS
Authors: Kalathil Biju , Welsh John , Tuck Mary Catherine , Bailey Mark , Zielhke Auti 
Published: November 2014

AbstractIn an integrated product development environment that includes several vendor tools, diverse and incompatible configuration management mechanisms and authorization management mechanisms across tools can lead to inefficiencies in the design process. We describe in this document a common model of configuration management and authorization that may be adopted for an integrated product development environment. We specified a common minimal set of configuration management mechanisms and authoriza‐tion management mechanisms that must be provided by the tools to support the proposed configuration and authorization models. We implemented a pilot program of the configuration management and authorization management models using Intergraph Corporation's Document Manager 2.0 (DM2) software system. This pilot implementation proves the plausability and usability of the model.
ALFS A REQUIREMENTS MANAGEMENT SUCCESS USING DOCUMENT DIRECTOR
Authors: Webb Buddy F 
Published: November 2014

AbstractThe Airborne Low Frequency Sonar System (ALFS), is the next generation of dipping sonar system being developed for the U.S. Navy Helicopters. ALFS is being built by the Naval And Maritime System Engineering Center, which is part of the Hughes Aircraft Company located in Fullerton, CA. This project is in the Engineering Developmental Model (EDM) Phase and will be conducting its Operational Developmental Testing in 1996. The ALFS project is a Military Standard 2167A program requiring requirements tracking throughout the programs life cycle. This paper will focus on how, the Requirements Management task was accomplished and the lessons learned.
ARTICULATED CONFIGURATION MANAGEMENT
Authors: Dyer Gary M. 
Published: November 2014

AbstractArticulated Configuration Management is a system that provides a backplane for status accounting, source code control, embedded processes, and project management. It does this by automating and linking the processes that previously were manual evolutions.The implementation, and indeed the definition, of Configuration Management varies widely among both Department of Defense and civilian activities. Some possible scenarios are presented in the hope that new technology may provide a better solution and definition for all concerned.This paper discusses the evolution of Configuration Management systems of the past into new technology that fully automates and articulates the Software Engineering Environment. It is presented and demonstrated in partnership with SQL Software Inc. of Vienna, VirginiaIn its purest form, Configuration Management has always been viewed as the process of tracking change. The change vehicle itself goes by many names within the industry. It may be called a bug report, trouble report, change proposal or a multitude of other names. For the purpose of this paper, I will refer to the change vehicle as a change document.Historically, Configuration Management and its associated change documents have been paper forms or manually updated forms within a database. This traditional Configuration Management very rarely had a meaningful connection to the source code modification it was supposed to track. The advent of state of the art Configuration Management systems now provides us with the capability to join or articulate the change document with the modified code and its outputs.Configuration Management systems are usually predicated on the development, baseline, and release philosophy of an organization. This philosophy generally is implemented in one or more of the following three scenarios.
SPACE MISSION OPERATIONS CONCEPT
Authors: Squibb Gael F. 
Published: November 2014

AbstractDeveloping a Mission Operations Concept for a space mission is a system engineering process. It involves multiple disciplines working together to describe the operational attributes of the flight and ground elements of the mission. This is done in the terms of the operators and the users (recipients of the data from the mission). A space mission operations concept emphasizes the way the mission will be operated and used (operational characteristic). Again, this is done in terms that are understood by the operators of the system and the users (the recipients of the data from the system). The Operational Attributes of a Mission are described by considering nine mission characteristics. These characteristics may be traded for cost and performance attributes of the mission. Developing a Mission Operations Concept is the process through which changes to mission requirements and/or design that will lower the Mission Life Cycle Cost can be identified. The inputs to the Mission Operations Concept include flight, ground and management functions.Mission Operations Concepts are typically generated for nearly all space missions. It is a requirement in many project plans and RFPs that are generated. However, there is not a definition of what is included in a mission operations concept; of what should be considered when generating this operations concept; what the process is or what the products are. This paper will discuss the process of developing a space mission operations concept; the benefits of starting this system engineering task early; the necessary inputs to the process; and the products which are generated. This paper is based on a chapter in a text book that will be published in March 1996 ‐ prior to the NCSC Conference. In addition this process has just started going through an international review which will result in an ISO Standard for a Space Mission Operations Concept checklist. This checklist will describe the inputs, and outputs required to conform to the ISO standard for a space mission operations concept. The paper will include that latest draft of the international standard checklist, and explain the system engineering processes and benefits of generating an operations concept early in the life‐cycle of the project, during the study phase, and then maintaining the operations concept throughout the life‐cycle of the project.