bluuebunny/crossref_metadata_2025_split huggingface dataset:
Systems Engineering Management in Research and Development Valley of Death
Authors: DiMario Michael , Hodges Ann 
Published: September 2023

ABSTRACTA failure of a great many early research and development programs is the result of encountering the traditional valley of death that shadows early research and technology development. The elements that create the valley of death leads to research and technology development high risk and poor return on investment for a great many research and development organizations. This leads eventually to avoiding research and technology development all together because the organizations cannot viably manage the outcome of their early‐stage research and development (ESR&D) efforts. Unfortunately, there are few established frameworks and processes for enabling smooth transitions to avoid failure and manage risk across fundamental research, applied research, development, and productization. Many leaders, program managers, and scientists are unwilling to involve systems engineering because of the perception that systems engineering is heavily process oriented, adds unnecessary costs, and should be applied only to mature technologies. The value of systems engineering as applied to ESR&D is unclear to these key individuals. The unfortunate result is that systems engineering is not applied to ESR&D. This article discusses the potential of application of systems engineering to ESR&D to improve return on investment and decrease risk.
Systems Engineering in Technology Development
Authors: Sly Jaime , Crowne David 
Published: September 2023

ABSTRACTTechnology development is the crucial first step in designing new products and systems. It is a unique phase of product development in that it incorporates both scientific exploration and reduction to an engineered result. Too often, systems thinking and systems engineering principles aren't applied at this stage, leading to technologies that solve the wrong problems, inability to progress to higher maturity levels, and unworkable implementation architectures. In practice, this means higher development costs, extended timelines, and failed technology development projects. This article presents a framework for and provides guidance on systems engineering activities that add value and improve outcomes if applied during early stages of product development.
Acute Effects of Spinal Cord Injury on the Pituitary‐Testicular Hormone Axis and Sertoli Cell Functions: A Time Course Study
Authors: HUANG H. F. S. , LINSENMEYER T. A. , LI M. T. , GIGLIO W. , ANESETTI R. , VON HAGEN J. , OTTENWELLER J. E. , SERENAS C. , POGACH L. 
Published: September 2023

ABSTRACT: The present study investigated the time course of the onset of the abnormalities in spermatogenesis following spinal cord injury, and their relationship to changes in the pituitary testicular hormonal axis and Sertoli cell function.These results suggest that spinal cord injury will result in a temporary, but profound, effect on the pituitary‐testicular hormone axis. These changes may impair certain aspects of Sertoli cell function that could render these cells incapable of supporting normal spermatogenesis. However, the seventy of spermatogenic lesions and the disparate responses of the two major Sertoli cell proteins make it unlikely that hormone deficiency is the only mechanism responsible for the impaired spermatogenesis following spinal cord injury.Spinal cord injury (SCI) was induced in adult male rats by surgical transection of the spinal cord at the level of T9 and L1 vertebrae. Animals were killed 3, 7, and 14 days after the operation. As early as 3 days following SCI, abnormalities in spermatogenesis, including delayed spermiation and vacuolization of the nucleus of spermatids, were noted in both the T9 and L1 animals. By 14 days, other lesions, including phagocytosis of mature spermatids, incomplete cellular associations, and total regression of seminiferous epithelium, became apparent. Concurrently a transient but significant (P < 0.05) suppression of serum follicle‐stimulating hormone (FSH) occurred in the T9 animals, and a suppression of serum luteinizing hormone (LH) occurred in both the T9 and the L1 animals 3 days after the surgery. This was accompanied by a suppression of testicular and serum testosterone levels (P < 0.05, P < 0.01, respectively). Most of the hormonal parameters had recovered and were not different from those of sham‐operated animals by 14 days (P > 0.10). Northern blot analysis of testicular poty(A)+ RNA revealed a transient but significant reduction in the steady‐state level of the 2.7‐kilobase (kb) Sertoli cell transferrin mRNA transcript in both the T9 and the L1 animals 3 days after the operation (P < 0.05). On the other hand, the 1.7‐kb androgen binding protein (ABP) mRNA remained unaffected during the 2‐week study period. The steady‐state level of mRNA transcripts for spermatogenic cell‐specific hemiferrin and spermatid specific transition protein 2 and protamine 1 also remained unchanged.
State of the Practice–Automation and Tools: Report from NCOSE Tools Working Group
Authors: Holtzman Julian 
Published: September 2023

AbstractThis paper will present the goals, objectives, and near‐term working plan for the Tools Working Group, a subcommittee of the NCOSE Practices Group. Since the Working Group has only been reactivated in the last nine months, this paper will not be able to include the major results; the most productive period has been that since the January meeting in Melbourne, Florida. A separate paper will be available to NCOSE 1993 meeting attendees at the end of the plenary session.
OBJECT ORIENTED ANALYSIS: AN INTRODUCTIONAND COMPARISONTO TRADITIONAL SYSTEMS ENGINEERING ANALYSIS METHODS
Authors: Wirth John M. , Joseph Daniel S. 
Published: September 2023

AbstractObject oriented analysis (OOA) is an analysis method that “examines requirements from the perspective of the classes and objects found in the … problem domain” (Korncoff, 1993). OOA allows systems engineers to analyze increasingly complex problem domains. Its methodology improves the communication between the system analyst, the problem domain experts, the managers, and the customers. Analysis results are more internally consistent through OOA methods, and commonalty of objects and functions are explicitly represented through the use of inheritance. Requirements specifications can be built that are more resilient to change, and analysis methods and results are structured for reuse. Finally, when products of the systems analysis and design processes includes software written in Ada (or another object oriented language), OOA provides a consistent underlying representation that minimizes the transition/translation problems often encountered between software and systems engineering efforts.This paper provides an introduction to OOA methods and its utility for systems engineering. A comparison between OOA and more traditional functions‐requirements‐allocations (FRA) analysis methods is discussed. A simple case study is presented to contrast traditional FRA and OOA methods.
EXPERIENCE WITH THE APPLICATION OF SYSTEMS ENGINEERING TOOLS
Authors: Cox John E. 
Published: September 2023

AbstractSystems engineering is one of the last engineering disciplines to be automated. Now that system design automation (SDA) tools are finally becoming available, they are expected to be a “silver bullet” that offer a miraculous solution to the complex process of building large systems. However, experience. has shown that the addition of computer‐based tools to the systems engineering activity in fact adds an additional layer of concern to an already complex situation. Getting measurable benefits from the application of automated systems engineering tools has proven to require close management attention due to many factors.This paper addresses the above and other issues, citing lessons learned in the deployment of RDD‐100(r) System Designer on several large programs and discussing the strategies that may be employed to maximize success in automating systems engineering processes.
SYSTEMS ENGINEERING: PROCESS VERSUS MANAGEMENT
Authors: Bell James D. , Grellmann Hans W. 
Published: September 2023

ABSTRACTThis paper presents practical considerations in applying systems engineering in the development of complex systems that have natural conflicts with management processes. Many efforts focus on the elements, program phases and tools of systems engineering, but generally do not address practical steps for applying systems engineering, while integrating the “human element” into the process. This paper addresses: a) the current environment, b) the distinction between systems engineering processes and elements of management, c) profiles of a good systems engineering manager vs. a good systems engineer, and d) the relationship of processes to organizational structure. The paper concludes with some thoughts on a management philosophy that supports systems engineering.
INTEGRATED MASTER PLAN / INTEGRATED MASTER SCHEDULE
Authors: Lagaly Donald J. 
Published: September 2023

AbstractThe Advanced Tactical Fighter (ATF) Engineering and Manufacturing Development (EMD) Request For Proposals called for several dramatic changes in the acquisition process along the guidelines proposed by the Packard Commission. The ATF EMD Program was to truly be an event‐based program, as opposed to being driven predominantly by a schedule produced before the proposals were submitted. How can a major aircraft EMD program be managed apart from a schedule? Of course, it cannot. For the F‐22 EMD Program, an Integrated Master Plan (IMP) was developed, defining all essential tasks in a hierarchial and Integrated Product Team format. The IMP describes the Events, Significant Accomplishments, and Accomplishment Criteria to be completed to the satisfaction of the SPO/Contractor team throughout the nine year EMD Program. The IMP indicates which Work Breakdown Structure element is primarily tasked with each Accomplishment Criteria, the multiple Accomplishment Criteria under a specific Significant Accomplishment, and the multiple Significant Accomplishments necessary to successfully demonstrate satisfactory Event closure. The IMP is a contractual document, without calendar dates. An associated Integrated Master Schedule expands the contractual IMP by adding an expected schedule to every Event, Significant Accomplishment, and Accomplishment Criteria. The IMS also adds sub‐criteria Tasks to some Accomplishment Criteria. In the early stages of the EMD Program, the IMP has already demonstrated its value by instilling a discipline to the concurrent engineering nature of the F‐22 Program that might otherwise have been very difficult to achieve.
A SYSTEMS ORIENTED DEVELOPMENT APPROACH FOR COMMERCIAL ENTERPRISES
Authors: Stone Arthur G. 
Published: September 2023

AbstractIn the commercial market sector, (non‐DoD) systems engineering is usually not required by customers. The decision to use it has to be based on what's good for business. However, very little information is available on how to develop a strategy for employing systems engineering in the commercial market sector. This paper proposes a strategy based on a hierarchy of systems engineering processes, with the systems approach at the top of the hierarchy. The systems approach identifies; (1) the basic systems engineering activities and their purpose, (2) a standard system life cycle model that integrates the basic systems engineering activities over time, and (3) guidelines on tailoring the systems approach into a systems engineering process that will work for any industry and product unique considerations.
Life Cycle and Production Unit Cost Analysis Techniques for System Configuration Selection in the Norwegian Offshore Oil and Gas Industry
Authors: Plummer David F. 
Published: September 2023

AbstractThe constituent elements, hierarchical relationship, and design, construction, commissioning, startup, production and decommissioning life cycle of oil and gas production systems (e.g., offshore drilling/production platforms, onshore petroleum processing facility, offshore gas production platforms) in the Norwegian offshore petroleum/gas industry are described.Economic and financial considerations (currency conversion, escalation/inflation rates, rate of return) which affect life‐cycle and production unit cost analyses are summarized. Risk and uncertainty in the analyses are discussed.The structure and estimation of life cycle costs for complex petroleum/gas production facilities is discussed. A model is presented for calculating unit costs for production‐facility output, e.g., $/bbl, $/sm3; definitions of terms are given in an appendix. The use of life‐cycle and production unit cost estimates to select a preferred system configuration is discussed.A numerical example is provided to illustrate the production unit cost estimation procedure. Cost information for the example is based on an actual Norwegian offshore oil/gas production system.
SYSTEMS ENGINEERING THE FAULT ANALYSIS PROCESS FOR COMMERCIAL AVIONICS APPLICATION
Authors: Spangler C. Steven 
Published: September 2023

AbstractThis paper provides an overview of a fault analysis methodology and process that integrates Failure Mode and Effect Analysis (FMEA) with Built‐in Test Equipment (BITE) Coverage Analysis. This integrated process has been given the title FMEA/BITE Analysis. The Systems Engineering methods and tools used to develop this integrated process are discussed and applied to the problem statement. Decomposition of requirements for industry standards and the new Boeing Commercial Airplane Group (BCAG) 777 Cabin Management System were used to identify what the analysis process must do and what the analysis results must contain. A trade study was performed to select the process architecture based on the multiple objectives of both the FMEA and the BITE Coverage analyses. An overview of the FMEA/BITE Analysis process is provided that specifies the analysis tasks, data items, and product deliverables. Finally, concepts are identified in which computer assistance can be applied to achieve a high‐quality, measurable fault analysis.
EXPERIENCES IN TRAINING SOFTWARE ENGINEERS TO PERFORM SYSTEMS ENGINEERING
Authors: Harbaugh Sam 
Published: September 2023

AbstractThis paper presents the experiences in designing and delivering a systems engineering course for a project team consisting of software engineers who have, for the first time, total systems responsibility for a new computer system. The training objectives support the training mission which is to help assure project success.The training scope includes the systems engineering process, its management and its products beginning with needs analysis and continuing through system requirements specification, system design and producing software requirements and a software development plan.The course described here includes analysis of various aspects of computer systems; workload, functionality, man‐machine interface, security, and the “ilities” (reliability, maintainability, etc.). The course covers system design techniques and process models. The course covers how the results of analysis and design are qualified and how they are used in the construction of Government documents.
REQUIREMENTS: A PRACTICAL, TESTED APPROACH FOR BREAK‐THROUGH SYSTEMS
Authors: Frantz W. Forrest 
Published: September 2023

AbstractRequirements are often described in free‐flowing text, interspersed throughout a document, difficult to locate, qualitative versus quantitative, incomplete, and hence, not a means to base final customer acceptance. But, when requirements are uniquely specified and quantified via standard requirement attributes, requirements can be analyzed and clearly communicated. This allows a process to occur between the customer and project team that concisely defines the requirements and acceptance criteria of the system. The approach sets the basis for systems development ‐ from architectonics through customer acceptance.Prior to implementing a practical approach to requirements definition and analysis, project teams found the requirements process too difficult to implement and did without. Customer ownership was weak. Few breakthrough projects succeeded. As a result, several approaches to requirements definition and analysis were tested.This paper presents a synthesis of the best of these approaches. Projects now move into final phases with well‐defined acceptance criteria and customer ownership. Presented in this paper are guidelines and standards used to develop requirements, requirement attributes, the Ten Commandments of requirements, the process of developing requirements, formats, acceptance criteria, and how requirements feed other project disciplines.
7.1.4 Identifying and Modeling Safety Hazards
Authors: Daniels Jesse , Bahill A. Terry , Werner Paul W. 
Published: September 2023

AbstractThe Hazard Model described in this paper is a risk management tool that is intended to aid in tracking and evaluating risks. The model is a new application of old systems engineering tools, i.e., tradeoff studies. However, the model is not intended to be directly integrated into the SE process. Rather, it should be implemented as an ongoing evaluator of key attributes as required by the system under study. The Hazard Model is designed to accept data from distributed databases, evaluate the data, and provide as output a numerical representation of the system's state, called the Hazard Index. The Hazard Index may be interpreted as a traveler's advisory. A Hazard Object template is used to ensure that all necessary descriptors for each condition that may potentially contribute to hazardous circumstances are collected in a standardized format. Three methods for combining hazard data are presented and compared. These three methods serve as the “engine” for our Hazard Model. Interactions among hazard stimuli are also investigated. Three methods are presented for handling three different types of interactions between the Hazard Objects.
8.1.4 Military and civil logistic support of humanitarian relief operations
Authors: Ludema M. W. , Roos H.B. 
Published: September 2023

AbstractAs a result of a higher frequency of crisis situations, and due to the fact that societies become more and more vulnerable, the expenditures for humanitarian relief operations are growing. The currently available knowledge concerning humanitarian relief operations and relief logistics can be used more effective. Much knowledge is available in the humanitarian relief society and in military organizations involved in relief operations in crisis situations. The current base of knowledge is not interrelated or evaluated enough in respect to relief system effectiveness. If knowledge concerning humanitarian relief operations would be reengineered following a systems engineering, system logistics, and a more coordinative approach, humanitarian relief operations might be more effective for the same or even less money. One solutions that could benefit from integrated civil and military relief logistics knowledge and coordination of civil and military relief operations is the establishment of several relief‐hubs for one the Netherlands might prove a good location.
2.3.2 Implementing Systems Engineering
Authors: Armstrong James R. 
Published: September 2023

AbstractThe task of implementing systems engineering is always a challenge. Many times, the task is given to a technical expert with little training in people skills. Further, even the social scientists struggle with getting people to change. Much has been written about change management. However, recent research in this area has developed a process for change that provides more structure to this activity and has application to systems engineering. This paper provides a translation from the social environment to the technical.
4.3.3 Exploring Concepts during Pre‐System Definition
Authors: Schoening William W. 
Published: September 2023

AbstractDespite the fact that Pre‐System Definition (PSD) is a precursor to the later life‐cycle phases, organizations continue to perform this phase poorly. PSD projects (also called Concept Exploration or Feasibility Studies) can be characterized as being of relatively short duration with rapid transitions in focus. Since PSD is before design, the issues and approaches are different from the later design phases. This paper describes many of the causes for poor PSD execution and discusses techniques for helping a poorly executing PSD project recover. Brief diagnostic questions are posed to help readers implement the approaches proposed in this paper.
4.3.4 Role of Design, Design Validation, and Verification Activities in Development of Software Systems
Authors: Kaslow David , Martin Lockheed 
Published: September 2023

ABSTRACTOften on a large program, the management structure focuses on the management of the work and monitors the development and approval of the program baseline but does not provide the day‐to‐day design direction. At best, program management has knowledge of the high‐level portion of the baseline. Integrated Process and Product Teams (IPPTs) are one mechanism for providing day‐to‐day direction. This paper recommends establishing Design, Design Validation, and Verification Activities for the day‐to‐day coodination of the design. These Activities can be used very effectively in the traditional management structure or as an integrating force among IPPTs.
6.3.1 Properties of a High Quality Informal Requirements Document
Authors: Schneider Richard E. , Buede Dennis M. 
Published: September 2023

AbstractOne way to improve the quality of a system level informal requirements document is to check it for goodness properties and fix any checking errors. Several lists of goodness properties are available but they differ by author. And a sound basis for selecting goodness properties is seldom provided. We propose a set of goodness properties which were developed from a larger list of properties using selection criteria as this sound basis.In previous work we established a set of criteria for selecting which properties represent high quality in an informal requirements document. This paper extends that work by applying the selection criteria to a large set of candidate properties. Through a process of refining, combining, splitting, and discarding of candidate properties using the selection criteria, we arrived at the limited set of high quality properties. This paper describes that process.
6.3.2 End User Involvement in Establishing Software Requirements for Aerospace Software Systems
Authors: Ippolito Brian , Murman Earll 
Published: September 2023

ABSTRACTRequirement practitioners often cite end user involvement as an important element of an effective requirement derivation process. The research reported in this paper provides quantitative data of end user involvement in the software requirement derivation process. The paper includes information on the identity of the end user versus the customer, end user involvement, frequency of end user and customer changes, value added by the end user, enablers, and end user satisfaction. The findings presented were part of a larger two‐year research effort involving over one hundred and seventy requirement practitioners from the Aerospace industry, United States Air Force, and MIT. The goal of the research effort was to identify effective practices for deriving software requirements.
1.4.4 Rapid Architecting Based on Systems Engineering Principles
Authors: Harzenetter Florian , Thomé Bernhard , Igenbergs Eduard 
Published: September 2023

AbstractThis paper provides an approach to Rapid Architecting based on systems engineering principles. After an introduction to the problem area, the notion of “Rapid Architecting” is explained: First a description of a generic process model for Rapid Architecting is proposed. This description is not tied to any specific method for architecting. Then we describe a method that implements this generic process model as well as the models needed for carrying out the process. While explaining the process and the models, we outline the underlying systems engineering principles that have been the basis for the definition of the process and the method.