bluuebunny/crossref_metadata_2025_split huggingface dataset:
A SYSTEMS ENGINEERING APPROACH TO HIGHWAY DESIGN
Authors: Mackey William F. , Mackey William F. 
Published: November 2014

AbstractThis paper explores some of the similarities between the approaches that civil engineers take to design highways and that systems engineers take to solve complex system development problems. The process of developing a highway design can be directly correlated to the system development life cycle used in systems engineering. The progression of highway design is demonstrated to be an evolution of technologies, inventions, organizational creations, and legislative acts supporting the development of a national interstate transportation system. Until now, highway design 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 (IVHSs) 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.
SYSTEMS ENGINEERING SUPPORT METHODOLOGY
Authors: Kingsland Richard 
Published: November 2014

AbstractA computer based Systems Engineering Support Methodology has been developed which interprets specified requirements to determine the specific concerns generated by each requirement at each level of the program structure and systematically identify all activities that are necessary to evaluate the identified concerns. The process continues by identifying and accumulating the necessary information, such as design detail and data bases; and the analytical tools, computer codes and experimental results, required to perform each evaluation. Documentation is added as the evaluation program is implemented. The aggregate of defined activities and resources required for these evaluations provide management with data regarding the full scope of the program and resources required for implementation. Correlated schedule data support the development of an efficient profile for program conduct.
Improving the System Software Requirements Development Process
Authors: Brown Phillip J. , Iwach Alexander E. , Williams Donald R. 
Published: November 2014

AbstractOne of the most significant challenges currently facing the system engineering profession is devising procedures for improving the system software requirements development process. While many practitioners promote a variety of automated tools and mechanistic templates as the means to improved productivity, experience suggests the highest leverage lies in harnessing thecognitiveprocesses required to produce a stable set of well defined system software requirements. System complexity and schedule constraints necessitate the use of teams of specialists working together to produce the desired software requirements database. System engineering's primary responsibilities are to foster team acceptance of a shared vision through the identification of intermediate and final products supporting the software requirements development process. This paper describes a framework for accomplishing the above, illustrates key points with actual examples, and identifies three approaches for improving management understanding of the requirements and software development processes.
Performance Sigma and the Systems Engineering Process
Authors: Kinard John Brent 
Published: November 2014

AbstractThe paper presents a method for the integration of Six Sigma producibility, statistical analysis, and risk management techniques into the requirements specification sub‐process of the systems engineering process. Application of the proposed method will identify performance and producibility risks early in the program life cycle. The method requires concurrent engineering and produces metrics intended to compel corrective action. Tools and training to support the method are also discussed.
A Conceptual Framework for Defining an Enactable Systems Engineering Process
Authors: Adhikari Sam B. 
Published: November 2014

AbstractThis article presents a conceptual framework for defining an enactable System Engineering process. The framework is based on the three primary entity types in a systems engineering process: Activities, Agents and Artifacts (AAA). AAA entity classes possess relationship within and between them. When process behavior is added to entities and relationships, dynamic systems engineering processes are created. Process definition of enactable system engineering processes can be defined via textual descriptions, IDEF/SADT or ETVX type notations, AAA or APPL/A type of process programming languages. This eventually results in the virtual machine that enacts the process code.
THE SYSTEMS ENGINEERING PROCESS AS A NEURAL NETWORK AND ITS IMPACT ON INTEGRATED PRODUCT DEVELOPMENT
Authors: Armstrong James R. 
Published: November 2014

AbstractVarious models have been proposed for the systems engineering process. Each one serves a particular purpose, yet none are accepted as definitive. The goal of a definitive yet simple model of the types proposed to date may be intrinsically unachievable. A neural network of interactive parts is proposed as a more accurate description of the process. This view explains the difficulty in developing a perfect and simple process model. Perhaps more importantly, it impacts the implementation of the process, particularly in an Integrated Product Development environment.
A Life Cycle for Commercial and Aerospace Systems Discovery
Authors: Oliver David W. 
Published: November 2014

AbstractThis paper defines a life cycle that is tailorable to either commercial or aerospace system developments. The tailorability is accomplished by separately describing the product life cycle, the acquisition cycles, and the technical steps used in performing the systems engineering. In addition this life cycle is based on the discovery of issues.The life cycle described here differs from both the Waterfall Model, (Royce 1987), and the Spiral Model, (Boehm 1986), in significant ways that make it applicable to the work that occurs on time and cost sensitive projects.The waterfall model defines a set of phases through which the project passes, but does not describe the manner in which actual projects loop back to prior phases when issues are discovered which require revisiting prior work. The spiral model defines progress through a series of prototypes, but does not root the prototypes in particular engineering goals.In the discovery life cycle a set of normal forward phases is defined. The process for handling issues is described as a separate Change Management process which may be initiated at any step of engineering and may lead to any other step of engineering for resolution. In the discovery life cycle prototyping is associated with particular activities:
Rapid prototyping to define and demonstrate product function to operators and users to verify and refine requirements
Early prototyping to remediate risk by demonstrating feasibility.
Sequential release of products in a product line.
Sequential build designed to facilitate early stimulus/response thread validation through the system as it is integrated.
IMPROVING SYSTEM ENGINEERING EFFECTIVENESS >>> THE POSSIBILITIES >>>
Authors: Ring Jack 
Published: November 2014

AbstractAddresses the extent to which system engineering effectiveness might be improved. These data come from subjective judgments by seminar attendees but reflect a reasonable level of “expert opinion.”Results to date from this on‐going survey indicate that significant improvement is possible relative to prevailing system engineering roles and practices.
A majority felt that the results of their total development effort could be improved as much as 2:1 depending on the content and process of their systems engineering activity.
A majority felt that the achievement level of their current organizations might be increased by over 1.5:1 simply by improving the behavior in and of the process.
These factors are multiplicative. An advanced, systems‐level business might perform as much as 3:1 over many contemporary businesses.
THE SYSTEMS ENGINEERING PROCESS UNDER THE RAPID DEVELOPMENT METHOD
Authors: Reilly Norman B. , Spuck William H. 
Published: November 2014

AbstractManagement and systems engineering processes for system development have undergone a number of significant modifications over the past forty years in a constant effort to improve the probability of success. The lessons have been hard won. The traditional staircase process works best, and perhaps only, when requirements are well understood and needed technologies are in place. Following several successes and many failures, early prototyping and spiral models were devised to reduce risk in system developments where requirements and design issues were more fuzzy [BOEHM, 1988]. The latest management innovation, the rapid development method (RDM), has been successfully used to implement systems whose final requirements and designs are largely unknown at the outset [SPUCK, 1991]. It is important that the appropriate development process be selected for a given system development, and that the impact on the systems engineering process be well understood.
Requirements For Systems Engineering Metrics
Authors: Vinopal Timothy J. , Mar Brian W. 
Published: November 2014

AbstractA systems engineering approach to the development of metrics for systems engineering is presented. Metrics are needed to indicate the “health” of an ongoing systems engineering process and the likely “quality” of the product of that process. A literature review of existing quality metrics identified four eras (1) inspection, (2) statistical quality control, (3) quality assurance, and (4) strategic quality management. The specific application of quality concepts to “white collar quality”, “engineering management quality”, and “system engineering quality” provided increasingly detailed and specialized product and process metrics. A survey of 28 agency/companies practicing systems engineering was made to determine whether the current solutions satisfied the functions and requirements of metrics identified in the literature. A set of 30 process and product metrics were analyzed in function, requirement and solution format. Collection, analysis, reporting and management operational functions were found to be as important as the choice of specific metrics.
DEVELOPING A TECHNICAL PERFORMANCE MEASUREMENT TOOL
Authors: Brown Dean D. 
Published: November 2014

AbstractThis paper discusses the development of a Technical Performance Measurement (TPM) tool by Westinghouse Electric Corporation. The tool is being developed to define and standardize the TPM process, streamline the data entry and reporting process, collect TPM data for analysis, and encourage the use of TPM within Westinghouse. The tool provides several capabilities, including a friendly user interface, network capability, configuration control, report generation, variance reporting, and metrics collection. The tool is implemented using Paradox for Windows, a commercial relational database product. By developing the tool and establishing a TPM library, we are hoping to reduce our process cycle time while also improving the quality of our TPM data.
USING CONTROL CHARTS TO MEASURE SYSTEMS ENGINEERING EFFECTIVENESS
Authors: Bellagamba Laurence 
Published: November 2014

AbstractA methodology for selecting metrics to measure the long term performance of a systems engineering organization is outlined. When appropriate, control charts are used to enable the organization to perform plan, do, study, act cycles to determine if changes to operations improved the mean and variation in performance. Illustrative examples are presented using data from an aerospace firm's systems engineering department.
LIFE CYCLE SYSTEMS ENGINEERING: A GLOBAL ENVIRONMENTAL IMPERATIVE
Authors: Fiksel Joseph , Brill James H. (Jim) 
Published: November 2014

AbstractThe scope of systems engineering has rapidly expanded to encompass the full life cycle of system development, deployment and support. A number of important issues arise during the latter stages of this cycle related to the impact of a deployed system upon the biosphere. Such issues include health, safety, and environmental protection as well as recycling and resource conservation. This paper describes how the practice of Design for Environment can be incorporated into systems engineering, assuring that downstream environmental quality factors are incorporated into design trade‐off decisions.
AGUAS: Design of an Agricultural Water Quality System
Authors: Wymore Wayne , Onstad Charles , Lane Leonard 
Published: November 2014

AbstractThis paper discusses the design of AGUAS, an agricultural water quality system, for the United States Department of Agriculture (USDA). The top level function of AGUAS is to ameliorate the impact of agriculture on water quality in a designated region of the USA.In the requirements development phase the problem of the design of AGUAS was stated in terms of I/O, technology, performance, cost, tradeoff and system test requirements. USDA policy restricts AGUAS from employing coercive technologies to carry out its top level function. Therefore, the system design requirements characterize AGUAS as an information system that outputs activities to collect data about water quality in the designated region and responses to inputted demands for information from users to persuade them to adopt less polluting farm management systems.In the concept development phase, a system design concept was chosen. Subsequently, gaps in the technology required for the implementation of AGUAS have been identified through the processes of system functional analysis and physical synthesis.Currently, the project is in a research and development phase.
APPLICATION OF SYSTEMS ENGINEERING INTO AN ONGOING OPERATION
Authors: Morais Bernard G. , Grygiel Michael 
Published: November 2014

AbstractThis paper presents an approach to introducing the Systems Engineering Paradigm into a culture that was previously oriented to production. The Westinghouse Hanford Company, the Operations and Management Contractor for the Hanford Site of the Department of Energy (DOE), was directed by the Department to change from a mission of supporting the nuclear weapons production program to one that would eliminate the threats to the environment and hazards to the public that have resulted from this production. Because of the requirement for continuing management of stored wastes, a strong Stakeholder involvement, and the objective to use the cleanup of the Hanford site as a model for the cleanup of other hazardous and toxic waste sites, the DOE strongly emphasized that systems engineering should be used to develop the cleanup program.This paper will also make recommendations based upon the Hanford experience that may be applied to other instances where changing the organizational culture is necessary to support a change in the mission.
SYSTEMS ENGINEERING IN A SOCIAL APPLICATION: DESIGNING AN EVOLVED SYSTEM OF EDUCATION
Authors: Ottenberg Mark A. 
Published: November 2014

AbstractThere are many alternative areas where the benefits of systems engineering can be applied. One of the premier emerging areas of structured design today is in the design or redesign of social systems. The redesign of the education system, as a social system, is a prime candidate for the application of systems engineering. New Generation Education (NGE) is a systems engineering project to simultaneously redesign and evolve education. The unique balances this project requires within the processes and procedures of systems engineering can do much to teach us how to tailor our profession to other emerging applications.
APPLYING OBJECT ORIENTED METHODOLOGY TO COMMERCIAL SYSTEMS ENGINEERING
Authors: Lukaszewski Matthew S. 
Published: November 2014

AbstractObject oriented methodologies have traditionally been applied to software analysis and design and have been successfully implemented in languages such as C++. This paper addresses the approach, benefits and lessons learned in the application of an object oriented methodology to a highly complex, commercial‐based product development. Utilization of the methodology was effective in providing an environment for capturing all system requirements and performing an orderly analysis. This effort has led to the concept of “Reusable Requirements”.
APPLIED SYSTEMS ENGINEERING: A VIEW FROM THE TRENCHES
Authors: Terry William S. 
Published: November 2014

AbstractSystems Engineering (SE) continues to evolve as a critical part of major systems development. This evolution takes place on two fronts, the first is in the development of new processes, procedures, and tools in support of systems engineering, the second is the increased application of systems engineering in development projects. This paper will describe the application of systems engineering processes and tools to a major development program for the US Navy (USN). It will illustrate some of the pitfalls which were encountered in actual applications of systems engineering and point out some of the short‐term and long‐term benefits to both the development organization and the customer.
Revitalizing Product Development at the Edelbrock Corp.
Authors: Ring Jack 
Published: November 2014

AbstractThe author evolved a new system that revitalized product development at the Edelbrock Corporation. It integrates activities across a product life cycle, is responsive to external and internal “customers” and involves its participants in continuous improvement.Relative to the previous norm, the new system produced over three times more new products per year at about 20% less gestation time on each – all at less than 6% of company revenue. Production and warranty costs dropped and customer satisfaction increased.Whether the new system is concurrent engineering, integrated product development, or systems engineering; it works. Because it embodies and was evolved by systems principles, the experience should be transferable to other enterprises.This paper describes the system and its evolution, summarizes its performance level after 18 months and reviews the underlying principles. Also, it indicates why a company cannot do concurrent engineering until it starts doing engineering.
Applied Systems Engineering Management ‐The JORN Engineering Process Model.
Authors: Rochecouste G. Hervé 
Published: November 2014

AbstractUse of the JORN Engineering Process Model (JEPM) improves work process effectiveness throughout the JORN (Jindalee Operational Radar Network) Project. A set of integrated courses introduce the JEPM to staff. Subsequent process examination provides more than simplistic (and short‐term) process improvement.Education in the JEPM is aimed at quickly building an effective, productive engineering culture. The JEPM is utilised to understand processes and interrelationships. Effective processes can then be established, which implement project plans in a synergistic manner. Efficiency in work processes can then be raised, but only with an effective process.The JEPM is composed of four layers, which hierarchically decompose all project engineering tasks into smaller “process descriptions”. These identify required work, and entry/exit criteria, for each process. The JEPM creates a large integrated workflow diagram which could be used to monitor process effectiveness and generate performance metrics.This management tool enhances visibility of existing plans, and establishes context for plans & procedures. From a Systems Engineering viewpoint, this provides more effective direction, understanding of process interaction, and greater control over outcomes.
THE NEXT FRONTIER: A CASE STUDY OF THE INTEGRATED MANAGEMENT SYSTEM (IMS) OR EXECUTION OF IMS IN THE REAL WORLD
Authors: Lester Capt. Andrew W. , Palmer Thomas M. 
Published: November 2014

AbstractThe concepts of Mil‐Std‐499B and the Integrated Management System (IMS) have evolved over the last four years. IMS, in particular, was developed as a reflection of the U.S. Air Forces efforts in Total Quality Management (TQM) and Initiatives in Trust and Teamwork (ITT). Based on the IMS concept, beginning with the early states, contractors must have a detailed program and a plan which meets US Government requirements. In addition, it assists the Government in choosing contractor that best understands the requirements and risks, applies sound, but innovative management principles, and demonstrates a capability to manage and execute the program, via defined processes, which meet all defined system level requirements. This paper describes the similarities of Mil‐Std‐499B and IMS processes, and then discusses how one contractor implementing IMS for the first time, views this system. We have structured this paper to reflect on both the contractor's and Government's experience in developing a Request for Proposal (RFP) Package and a Proposal which meets the intent of the IMS. In the name of continuous improvement, the paper will also describe some lessons learned from the perspective of first‐time implementors of the IMS process.
APPLICATION OF DESIGN OF EXPERIMENTS TO A SYSTEM ENGINEERING TASK A PERFORMANCE TRADEOFF CASE STUDY
Authors: Davis Ronald L. , Fisk David M. 
Published: November 2014

AbstractThere are a variety of methodologies available to the system engineer to assist him in the execution of the processes of the system development cycle. Emerging software tools are making these methodologies increasingly accessible to the system engineer. Design of Experiments (DOE) is a powerful statistical methodology described by (Schmidt 1992) that has recently become more accessible to the statistics layman because of software that handles the complicated statistical computations and allows the user to focus on the planning of the experiment and the interpretation of the experimental results.DOE has been used extensively in the optimization of manufacturing processes, parts and system components. It also has potential for significantly enhancing the system concept development process in the Concept Exploration phase. We will describe how DOE methodology has been used in the execution of a conceptual design configuration trade study.
EVALUATING PROJECT RISK WITH LINGUISTIC VARIABLES
Authors: Jones James H. 
Published: November 2014

AbstractA simple, reliable method for assessing the project technical risks, schedule risks, and cost risks, usable by virtually anyone with moderate arithmetic skill, is set forth. It provides an aggregate risk figure of merit range for system risk by the tailoring project work breakdown structure hierarchy and incorporating relative importance weighting in the risk model. It extends the linguistic variable quantification based on one fuzzy logic hedge operator with a utility graph. It takes an individual's or corporate psychological attitude toward risk aspects into account. It can assess uncertainty as well as event likelihood and severity. Uncertainty is retained, to provide a qualitative expression for the overall risk range as well as the expected value.
IMPROVING REQUIREMENTS PROCESSING, A CASE STUDY
Authors: Kefer Marvin 
Published: November 2014

AbstractThis paper is a case study of AIL's effort to improve its Systems Engineering (SE) Requirement Process. Improving the engineering process is a common company goal. Determining which subprocesses to improve first, and getting program and departmental engineering support can make the difference between acceptance and nonacceptance of change. An approach to achieving these goals is described, step by step, in this paper.