bluuebunny/crossref_metadata_2025_split huggingface dataset:
A SYSTEMS ENGINEERING FRAMEWORK BASED ON CARTESIAN ARRAYS OF SETS
Authors: Haines David E. 
Published: November 2014

ABSTRACTIncreasingly, the system engineer's primary function is to facilitate knowledge capture from a concurrent product team. This role increases the need for the systems engineer to architect a data environment that meets strict criteria for a structurally valid schema. An encompassing theoretical base for creating such data structures is currently unavailable to the practicing systems engineer. Starting with the “three view” schema of MIL‐STD‐499B, a data array paradigm based on elementary theories of sets and arrays is developed as a generally applicable structure. This paradigm is then demonstrated with several examples of structured systems engineering practice. These are compared with current practices and usage to test for errors. Conclusions reached are 1) That even at the level presented, this paradigm can assist systems engineers in improving their real‐world practices; 2) Structured analysis should receive more attention in academic curricula for systems engineers; 3) Individuals knowledgeable in mathematical array and structural theories as well as systems engineering should contribute to a more complete body of formal theory; and, 4) Structural validity of the project schema should be regarded as a “first principle” for world‐class systems engineering. Recommendations include suggestions for “best practices” groundrules that could be defined now, and speculation as to where expanded theoretical development should take place for maximum benefit to the industry.
IMPLANTING EDUCATION IN SYSTEMS ENGINEERING IN A UNIVERSITY
Authors: Thomé Bernhard 
Published: November 2014

AbstractThis paper reports on a course on Systems Engineering of Computer‐Based Systems being given at a university. This particular course has the goal of laying a seed for a change in culture in universities. The cultural change targeted is for universities to offer their customers, its student body, a more systems engineering oriented educational opportunity. From this, it is felt, not only the companies in the systems business will benefit, but the students concerned as well, and ultimately also the universities courageous enough to venture in this direction.
The Systems Engineering Network at Hughes Aircraft Company
Authors: Miller Gary D. 
Published: November 2014

AbstractThis paper is an introduction to and an explanation of the Systems Engineering Network at Hughes Aircraft Company. The Systems Engineering Network (SEN) was established by the Executives of the Company, having determined that in the rapidly changing environment in which Hughes does business, a robust, modern, effective and efficient Systems Engineering capability was crucial to our competitive edge. To establish and maintain such capability the Systems Engineering Network was tasked to address all aspects of systems engineering for the corporation, cutting across all organizational boundaries. This paper will examine all aspects of the Systems Engineering Network at Hughes, including its history, its goals and objectives and its organization and structure. How the network goes about its business will be discussed, and the mechanisms for creating and sustaining improvements in the business of the Company will be explained.
ASEM ‐ A Simple Engineering Training and Personal Automation Tool
Authors: Whitten Carolyn , Keizur Alan , Mar Brian W. 
Published: November 2014

ABSTRACTThis paper describes a simple systems engineering training and support tool called ASEM. Experiences in using ASEM to teach more than 300 students in formal university and professional training courses are described.The purpose of ASEM is to support (1) the functional analysis, (2) the requirements analysis and allocation, (3) the recording of architectural decisions, test requirements and results and (3) the hierarchical development of any system description. The systems engineering process was used to create, test, and apply this tool. The tool has been well received in a teaching environment.
DESIGN OF A SYSTEM‐OF‐SYSTEMS ARCHITECTURE MODEL AND ITS USE TO IDENTIFY CROSS‐SYSTEM IMPACTS
Authors: McCay Brian M. 
Published: November 2014

AbstractThis paper describes the techniques used to build and extract information from an architecture model of an as‐built system‐of‐systems. The purpose of this paper is to describe the technical and procedural challenges in building the model using the commercially available systems engineering tool, RDD‐100. The paper also discusses how architecture model information is being used to identify potential cross‐system impacts due to proposed changes. The overall goal is to provide guidance to systems engineers to enable them to successfully develop useful models that support the controlled evolution of a system‐of‐systems architecture.
ADVANCED SYSTEM ENGINEERING AUTOMATION (ASEA)
Authors: LaMonica Frank S. , Comer Edward R. 
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 results of an exploratory development effort which specified the system level requirements and operational concept for system engineering automation known as Catalyst, and focuses on an advanced development effort entitled “Advanced System Engineering Automation (ASEA)” which is implementing the automation concept.
INTEGRATING SYSTEM ENGINEERING INTO THE SOFTWARE AND HARDWARE DESIGN PROCESS
Authors: Mori Daniel J. 
Published: November 2014

AbstractA decline in the defense budget has driven contractors to search for the “panacea tool” which will solve all of its productivity and manpower problems. Companies purchase tools to perform Object Oriented Analysis, Computer Aided Engineering, Requirements Traceability, and System Synthesis with little thought as to how they will be integrated.The process by which a company performs its engineering tasks must be considered when contemplating tool purchases. The tool must not only perform its required task in a satisfactory method, but also be easily integrated into other engineers' efforts. There should be a logical mapping between system engineering and hardware/software design tasks to ensure all engineers are cognizant of what is required, and that the design satisfies those requirements. When defining this integrated process, it is important that the handover of system engineering requirements to design be provided in a recognizable and usable form.This paper describes a possible approach that can be used to integrate the outputs of the system engineering process into inputs of the software and hardware design process. This “integrated approach” is based upon the author's knowledge of existing tools and methodologies. The use of specific tools is included not to promote these tools or approaches, but to show feasibility of one approach with existing tools.
SPACE SYSTEMS PRELIMINARY DESIGN
Authors: GORY Jean‐François 
Published: November 2014

AbstractAs in all other industries, the space industry is evolving in three primary areas: technology, costs and socio‐organisational approaches.A project conducted in CNES aims to revise the definition of future space systems with the introduction of global methods and computer‐aided tools. One of the main goals is the definition and the development of a cooperative workbench for missions and space systems design. It will be composed of a certain number of design and simulation tools dealing with unique and coherent information shared between different view points. Operated in CNES, this computer‐based workbench will focus on the early stages of projects but will also treat first order or “simplified” models which are managed daily during the projects' life span, in accordance with the detailed models from industry.
DATA QUALITY ENGINEERING: A SYSTEMS ENGINEERING “ENABLER”
Authors: Lehman Joseph R. 
Published: November 2014

AbstractThis paper briefly describes the circumstances that led to “legacy” automated data systems and characterizes the problems faced by today's large organizations as they grapple with escalating system maintenance costs, redundancy in data collection and maintenance efforts, and inadequate data quality. Some have developed a legacy system migration strategy that specifies, among other things, a requirement for integrated systems, common data standards, and a data repository system. However, most have had limited success at best in implementing practical, affordable solutions. This paper describes a successful approach out of the legacy morass—a rigorous methodology called “data quality engineering” (DQE). The DQE methodology provides a proven means for designing and implementing a workable migration strategy that features incremental improvement in system operations, implementation of a working data repository, and, most important, restored quality in the data values maintained in database files.
USE OF PERFORMANCE EVALUATION TOOLS IN SYSTEMS ENGINEERING
Authors: Vallone Antonio 
Published: November 2014

AbstractSystems engineers define system operations concepts, analyze system requirements, allocate the requirements to system architectural components (hardware, software, and operations), design the system configuration (hardware selection and sizing), and support system implementation. System performance is a major area of concern during the system development life cycle. System performance evaluation tools make life easier for the systems engineering team.
DIFFERENT PHILOSOPHIES / DIFFERENT METHODS: RDD AND IDEF
Authors: Griffith Patricia B. 
Published: November 2014

AbstractThe Requirements Driven Development (RDD1) method and the Integrated Computer Aided Manufacturing (ICAM) DEEinition language (IDEF) methods are frequently considered competitively for use on a systems engineering project. The purpose of this paper is to clarify some of the ways in which the two method families are vastly different in modeling purpose, method philosophy, usage styles, underlying concepts and history. The first section describes basic needs for SE methods and sources of confusion in method selection. The second section discusses major differences between RDD and the IDEF family. Two lessons in terms of method and tool selection are offered.
MANAGING A SYSTEMS ENGINEERING TOOL IN A PROJECT ENVIRONMENT
Authors: York Donald M. 
Published: November 2014

AbstractRather than understanding the detailed mechanics of a Systems Engineering tool, the customer wants to be assured that an integrated systems engineering approach is being implemented on his project. The customer also wants the assurance that the design engineers are working with and talking to the Systems Engineers on an ongoing basis. Effective management of a Systems Engineering tool can provide these assurances.However, many obstacles arise in managing the tool. This paper discusses these obstacles and presents lessons learned from managing Systems Engineering tools during several projects. Recommendations are provided for effectively managing any System Engineering tool such that an integrated Systems Engineering approach is realized and demonstrated to the customer.
PAYLOAD COST MINIMIZATION USING SEAT
Authors: Autio Gordon W. 
Published: November 2014

AbstractThis paper discusses the application of a methodology to arrive at a minimum cost solution to a given set of systems requirements for any electro‐optical (E‐O) payload. The Systems Engineering Analysis Tool (SEAT) is a powerful tool for the parametric analysis and cost‐effective design of E‐0 payloads. Cost estimating relationships (CERs) as a function of cost driving parameters for each subsystem along with design/performance parameters are input as analytical expressions into an existing tool called Multisensor Analysis Tool to perform the payload cost minimization. The quality function deployment (QFD) matrix or house of quality is used as an aid in deriving the system cost drivers. Various parametric trades and graphic plots in both 3‐D and 2‐D that show relative payload cost and signal‐to‐noise ratio (SNR) performance are presented. The goal is to integrate the disciplines of systems engineering and cost estimating into a cohesive, interactive process early in the system life cycle.
ISSUE DRIVEN DESIGN: PLANNING AND MANAGING DESIGN ITERATIONS
Authors: Alford Mack 
Published: November 2014

AbstractThe general recognition that the design process is iterative in nature presents the manager with a problem: how does one manage an iterative process? On the one hand, the manager would like to see a sequence of well defined tasks with well defined outputs. On the other hand, the design process may more strongly resemble a “search” process, in which the territory is unknown. This paper addresses this problem by providing techniques for defining and characterizing a sequence of partial designs.
Design Methods And Heuristics For A New High‐Volume Production System
Authors: Cavola Ray G. 
Published: November 2014

AbstractThis paper assesses two key elements of systems architecting: methodologies and heuristics, as they are applied to the concept design of a new high‐volume, discrete part assembly production system. A description of the system is provided, and then attention is focused on four major areas in the design: human factors design, system structure development, assembly scope definition, and system operating principles. In addition to descibing the use of existing heurisics, this paper presents and supports new heuristics developed in the course of architecting this system. These methods and heuristics have enabled forward progress in an evolution toward world‐class manufacturing.
Systems Engineering Practices in Generic Architecture Development and Tailoring
Authors: Wray Richard B. 
Published: November 2014

AbstractA common practice in systems engineering is the reuse of successful approaches, techniques and templates from previous programs or similar development efforts. Very rarely in present systems development do we successfully use and document a generic approach or template for development which can be reused for specific programs and missions. Under National Aeronautics and Space Administration (NASA) contract, a Space Generic Open Avionics Architecture (SGOAA) was developed for application to new space systems development. A case example of applying “tried and true” systems engineering principles in tailoring the architecture to a planned spacecraft for new lunar missions is described. Included is a summary of the principles applied, the methodology used, the key development process elements, the interface definition process, and lessons learned. This example demonstrates that a formal systems engineering methodology is needed, a generic architecture can provide a means for verifying all key interfaces, functional interfaces addressing user requirements should lead to logical and derived direct interface requirements, and interfaces should be simulated and rigorously tested to validate needs satisfied and performance acceptability.
DRIVING THE FIRST STAKE IN THE GROUND
Authors: McClinton David F. 
Published: November 2014

AbstractThe paper describes a technique for making those difficult first system architectural decisions in a major engineering project. A few key decisions set the overall architecture and allow the lower level analyses and trade studies to progress. Three examples are given from early initial system studies on two major aerospace study programs. Requirement dependencies and parameter space constraints are shown. The step by step process is explained. The approach is applicable to any system architecture.
SYSTEM ENGINEERING FOR ALL ENGINEERS
Authors: Bailey Michelle , Butterworth Jay , Fortune Mitzi , Kibbe Jim , Kaspersen Janice , Smith Bob , Stringham Mike 
Published: November 2014

AbstractThis paper describes a plan to increase the capability of general engineers in the area of system engineering and to increase the number of system engineers within an organization. Key features are emphasis on a hierarchy of system engineering capability, experience and demonstrated skills, involvement of the first‐line supervisor, facilitating early responsibility, and the ability to tailor the training and experience to the needs of the individual. Included are the preliminary measures of effectiveness.
AN APPROACH FOR IMPROVING SYSTEMS ENGINEERING COST ESTIMATION
Authors: Tilton Catherine J. , Triantis Konstantinos P. 
Published: November 2014

AbstractA critical part of a proposal for the development of a complex system is cost. One important element of this cost is the effort to perform the systems engineering function. The prevalent method for estimating these costs is a “bottom up” engineering estimate based on the experience and judgement of the estimator. In some cases, analogy to actual costs of previous, similar programs is employed. As practiced, neither of these methods provide the accuracy, consistency, or defensibility needed.This paper summarizes current practices and problems, identifies systems engineering cost drivers, and presents an approach for improving the ability to estimate systems engineering costs. The primary conclusion derived is a confirmation of the need for improvement in this area and the role of a comparable database of costs and cost drivers, as well as management commitment, in this process.
Process Based System Engineering
Authors: Tronstad Yngvar , Earley Robert , Shreve Sue 
Published: November 2014

AbstractThis paper provides a description of a Life Cycle Process Base that combines system engineering techniques and tools for modeling the product to be built with the process for building it. The process template described here provides a means for formally defining the system development process, and then identifying the methods and tools that support the design process. With the adoption and allocation to a specific organization, the template becomes a process. Through simulation and enactment of the process description, an organization is empowered to engineer and evolve the process over time and effectively manage and control the complexity of today's large scale programs.
THE AMAZINGLY INVARIANT SYSTEMS ENGINEERING PROCESS–A 30 YEAR LOOK
Authors: Kuhn Dorothy A. 
Published: November 2014

AbstractFrom time to time, systems engineers find themselves debating the subject of the systems engineering process. These debaters are commonly experienced systems engineers that may not, at the time, realize the limitations of arguing from experience. It is the trap of generalizing from a specific.The systems engineering process is well established in the systems engineering literature; it is a pragmatic engineering process that has at its basis the practices of scientific inquiry. The systems engineering literature shows that the fundamentals of this process have changed very little over the past 30 years.This paper will describe the fundamental systems engineering process, as shared by businesses as diverse as telecommunications, agriculture and defense, and will give an example of how that process is practiced in the 1990s at Texas Instruments Incorporated.
PARTITIONING COMPLEX SYSTEM DESIGN INTO FIVE VIEWS
Authors: Karangelen Nicholas E. , Hoang NgocDung T. 
Published: November 2014

AbstractThe complexity and sheer magnitude of modern computer based systems require a structured approach for their development. The principal objective of system development is to establish a design which satisfies the system requirements while optimizing the key trade‐offs associated with system functionality, behavior, and implementation. A methodology is presented in this paper for a multi‐domain system design capture approach. The methodology employs five views of the system which address the system design in separate but related domains. The basis for creating an integrated, automated environment for addressing design, capture and analysis of a complex system is discussed by: (1) defining each of the five views and organizing those views into three models of the system, (2) defining the relationships and dependencies between the models of a given system, and (3) identifying opportunities for application of advanced modeling and decision support techniques in the design, capture, and analysis of complex systems.
Automating Best Practices: The Challenge of Process Enactment
Authors: Masselle Eric , Rhodes Donna H. 
Published: November 2014

ABSTRACTProcess Enactment, or Workflow Management as it is sometimes called, provides a new technology approach which captures a well‐defined, optimized process and encodes it in an executable form. The encoded process is then enacted, providing for automated execution of tasks and activities and the controlled management of all information and data associated with the process. Enactment can be expected to influence both the way we do business and solutions we develop for customers. This paper focuses on the many challenges of process enactment, from both a technical and a cultural perspective. Also discussed will be a pilot project that has provided a test bed for demonstration and evaluation of enactment in our systems engineering environment.
Information System Security Engineering, MIL‐STD‐499B, and Trusted Development Methodology
Authors: Howe Donald M. 
Published: November 2014

AbstractThis paper provides an introduction to Information System Security Engineering in conjunction with the draft MEL‐STD‐499B for Systems Engineering. The generic system security engineering activities are identified with respect to each phase in the life cycle, and security documents are listed. The paper also discusses the trusted‐software‐development‐process as a method for achieving high assurance.
A Process for Systems Engineering Planning
Authors: Martin James N. 
Published: November 2014

AbstractThis paper describes the Systems Engineering Planning process used in AT&T Advanced Technology Systems. A process diagram is shown with 19 specific process tasks. Each of these process tasks are defined. In addition, inputs and outputs from each process task are defined. This process is intended to be used at the beginning of each project and the major output is a Systems Engineering Management Plan (SEMP). Other outputs are the Systems Engineering Master Schedule (SEMS), Systems Engineering Detailed Schedule (SEDS), and a Systems Engineering Development Environment (SEDE) Plan.
Systems Engineering Metrics ++
Authors: Miller William D. 
Published: November 2014

AbstractThis paper describes the internal AT&T Advanced Technology Systems (ATS) concerns with the current high level systems engineering metrics and the ongoing work to improve their definition to better reflect systems engineering's value to the R&D process. The current high level productivity and cost metrics are based on page counts that do not give any indication of the quality of the content on the pages. The systems engineering organization is considering a redefinition of the high level productivity and cost metrics based on function/feature points similar to their definition in software engineering. A constraint is that the revised high level metrics be derivable from the existing detailed systems engineering metrics. These feature/function point based metrics are calibrated to the project mix within AT&T ATS.