bluuebunny/crossref_metadata_2025_split huggingface dataset:
SYNERGE: A Tool for Managing System Engineering Information
Authors: Neely Michael C. , Hartley Jonathan 
Published: September 2023

AbstractThis paper describes the development of an information management tool, called SYNERGE, to provide a low‐cost, desktop‐based, generalized user interface to a project information base. SYNERGE enables the management and analysis of interrelated requirements, tests, system elements, organizations, activities, resources, and other types of system engineering information, thus integrating a variety of activities and facilitating analysis of impacts of changes to the baseline. By making the project information base accessible to all process participants, SYNERGE will encourage an institutional transition to the more extensive use of automation, including high‐capability COTS products.
REQUIREMENTS TRACEABILITY ON THE F‐22 PROGRAM
Authors: Reed Michael A. 
Published: September 2023

AbstractThis paper presents the requirements traceability approach taken on the Engineering Manufacturing and Development (EMD) phase of the F‐22 Program, formerly known as the Advanced Tactical Fighter Program (ATF). Traceability was implemented through the incorporation of an automated CASE tool to track hierarchial requirements, vertically and laterally, to individual requirement verifications and test plans. Limitations in CASE tool integration and team incorporation of new technologies are discussed.
TOWARDS A NEW GENERATION EDUCATION: AN APPLICATION OF SYSTEMS ENGINEERING PRINCIPLES
Authors: Ottenberg Mark A. , Asbjornsen O. Andreas 
Published: September 2023

AbstractAs the world's technical development proceeds with increasing speed, and the society becomes ever more complex, it seems that our education system lags further and further behind with its old traditions and cultures. This paper shows that a proper application of Systems Engineering Principles in the design and development of education offers interesting and radical suggestions for changing the way education is traditionally structured and practised. “The Fifth Discipline” by Senge (Senge, 1990), which is the ability to continuously learn and develop from experience, experiments, and observations while working as part of a multi‐disciplinary team, when combined with knowledge in different fields, is really systems engineering at its best.
STRATEGIES FOR PREVENTING FUTURE “REQUIREMENTS CREEP”
Authors: Manos Kerry L. 
Published: September 2023

ABSTRACT“Requirements Creep,” the gradual increase in the average number of requirements specified for a given type of system, poses a formidable challenge to the future of systems engineering efforts. In such cases where the number of system‐level requirements reaches into the hundreds (or even thousands), the tasks of identifying, decomposing, allocating, documenting and providing traceability of requirements quickly becomes a bookkeeping nightmare. Moreover, the critical tasks of identifying alternative system architectures, synthesizing design concepts and performing trade‐offs against an overwhelming array of criteria are becoming so complex as to confound and confuse even the most capable of systems engineers. And equally insidious is the impact of large numbers of requirements on system cost– since the term “requirement” has traditionally referred to a need that must be satisfied despite cost.In this paper, the author proposes that, in addition to developing the means to work effectively with large sets of requirements (e.g., computer data bases, modeling and simulation tools, etc.) systems engineering methodology should encompass strategies for limiting the number of requirements specified in the first place. The author then discusses a number of possible approaches, including elements of Quality Function Deployment, Analytic Hierarchy Processing and the so‐called “Eighty‐Twenty Rule,” and proposes how these might be applied collectively to determine the appropriate domain of requirements for a particular system. Although most readily applicable to non‐contract commercial or consumer system developments, such strategies could form a basis for future requirements definition efforts for government contract programs.
Development of a System Engineering Process Model Template
Authors: Tronstad Y.D. , Peterson J. , Shreve S. 
Published: September 2023

AbstractThe main problem facing the development of any large system today is complexity. The generalized process guidelines in the current MilStd life cycle specifications are based to a large extent on document production which falls short of capturing the system design data necessary to accommodate later upgrades. An executable model based approach to system engineering with one underlying formal representation for development of both system and process description is a better means for understanding the system and ultimately fulfilling the operational objectives within budget and schedule constraints.
SYSTEMS ENGINEERING IN A TECHNOLOGY DEVELOPMENT EFFORT: A CASE STUDY
Authors: Carlson Stephen O. , Matich Nicholas T. 
Published: September 2023

AbstractThis study discusses the System Engineering approach used to transition a medium‐sized (75 people) U.S. Government Research & Development (R&D) project from Concept Exploration (CE) to Demonstration and Validation (Dem/Val). The study presents a brief history of the project and discusses the Systems Engineering processes and techniques used to formalize system requirements, integrate the components, ensure proper testing, and produce complete documentation. Human factors issues observed in implementing formal Systems Engineering are discussed and lessons learned are presented. The use of a CASE tool is discussed.
CASE STUDIES: APPLICATIONS OF QUALITY FUNCTION DEPLOYMENT IN ACCORD WITH MILITARY STANDARD 499B
Authors: Bellagamba Laurence , Gernand Joseph , Tribble Alan 
Published: September 2023

AbstractQuality function deployment is a methodology to relate what needs to be done to how to do it. The methodology is used to implement the requirements for the systems engineering process established in Military Standard 499B in conjunction with Integrated Product Development teams. Examples are presented for two divergent applications: payload design for an upper atmosphere research satellite and investment strategy design for a division's research and technology program.
Risk Expectation Management for Building Secure Information Systems
Authors: Howe Donald M. 
Published: September 2023

AbstractThis paper describes the process of building Information Systems that integrate security mechanisms to protect from unauthorized access and mistreatment Risk expectation management for information systems is associated with security requirements‐policy‐architecture‐risk analysis and synthesis. Cognizance of threat is the most important part of developing secure information systems. The paper organizes the complexity of information security principles into a structured approach intended to minimize the expected security risk. An example is presented in the appendix.
DISTRIBUTED DESIGN OF COMPUTER‐BASED SYSTEMS: TRACEABILITY
Authors: White Stephanie 
Published: September 2023

AbstractDistributed computer‐based systems are complex due to their size, heterogeneous nature, and the dynamic interdependency of their components. Hardware and software are usually developed by a number of companies which the prime contractor and customer must rigorously monitor and control. Engineers and managers need traceability for control. They must trace requirements and design decision dependencies to create a complete and consistent design, to understand the impact of change, and to perform re‐engineering without introducing errors. Automatic compilation of software and silicon may eventually eliminate the need for traceability between formal specification and end‐product, but traceability will still be needed for tracing textual requirements and design decisions to formal specifications and test cases. This paper discusses the need for traceability, current practice and feasibility.
SYSTEM DEVELOPMENT PROCESS PLANNING AND MANAGEMENT
Authors: Beck John W. , Hudak George J. 
Published: September 2023

AbstractThis paper describes the planning and management approach used by AT&T Bell Laboratories to systematically establish and manage development processes for diverse types of projects. The approach is based on knowledge of all practices, tools, and training and an efficient method for selecting and tailoring these elements for projects. Planning is supported by a knowledge system that helps them select and tailor the “mosaic” of development tools and aids to produce a project specific development process plan. New projects benefit from the “experience” as other projects complete and update the knowledge system. All projects benefit from plans that are developed better, faster, and cheaper and the subsequent uniform development environment facilitates staff mobility.
THE WORK BREAKDOWN STRUCTURE: Its Much More Than a Cost Reporting Structure
Authors: Lake Jerry 
Published: September 2023

ABSTRACTFor the past 25 years of defense system acquisitions, the business side of government programs has controlled the underlying structure of the product‐oriented work breakdown structure (WBS). As such, little interest has been shown by engineers in discussing or using a WBS to assist system development. In the past year, both Mil‐Std‐881 on work breakdown structures and Mil‐Std‐499 on systems engineering have undergone revision. The revised systems engineering standard creates new purposes and uses for an “engineering” work breakdown structure (EWBS) consistent with concurrent engineering implementation. These purposes and uses expand the historical role of a WBS for establishing, tracking and comparing cost accounts to satisfy management's need to have visibility into program costs. As a result, the structure of an EWBS differs in several aspects from the time honored structure of Mil‐Std‐881.This paper discusses the central role the engineering WBS takes in accomplishing world class systems engineering. The focus, therefore, is (1) on the major role the EWBS plays in systems engineering and (2) on the differences of the EWBS with the WBS generated to satisfy business needs. The EWBS is explained with respect to its specific roles in structuring the statement of work, assigning integrated product and process teams, and conducting incremental technical reviews. A proposed resolution is recommended for resolving perceived differences between business and engineering work breakdown structures.
3.1.2 Intelligent Agent Technology in the Health Care Environment
Authors: Simons Desiree. J. 
Published: September 2023

AbstractMost people think of intelligent agent technology and the Internet as being connected because of the awareness brought to search engines by the public's use of the Internet. However, agent technology has always been in existence, as for example in the banking environment where an agent might be the alert agent for detecting when a stock price reaches a certain point. Unfortunately, many of today's Internet agents are not considered “intelligent” mainly because they are incapable of defining their area of search and as such, their applications are somewhat limited. Efforts to make agents work more efficiently have led to the emergence of a new technology called “filtering” which makes use of the speed of computers and the ability of networks to communicate. This paper examines the factors that are driving the development of filtering as well as the role of agent technology in the ever‐changing landscape of computer systems development. Finally, the impact that this kind of technology will have on medical professionals and patients in our future health care environment is illustrated by a description of the Patient Advocate system being developed by Stanford University.
3.1.3 The Application of Systems Engineering to Telemedicine
Authors: Chorley Stephen J. 
Published: September 2023

AbstractA case study is presented of the application of the systems engineering process of BAE SYSTEMS to a telemedicine project for South Africa. It is an example of the successful transfer of technology from the defence to the civilian sector and shows how the company's systems engineering practices were effectively applied in this field. The conclusion reached is that a good systems engineering process should be adaptable and effective and that technology transfer is an ideal benchmark test for any such process.
3.1.4 Predictive Performance Analysis and System/Software Architecture
Authors: Lacerte Yves 
Published: September 2023

AbstractThe development of long‐lived real‐time embedded software‐intensive systems face unique challenges. It is critical that sound architectural principles be applied toward the development of such complex systems. An essential architectural element in a real‐time system is performance.Predictive evaluation techniques can be effectively applied as part of the architecture design process. These techniques enable the estimation of performance of a given implementation on a given hardware configuration without having to actually execute it. In addition, it allows the architect to evaluate individual application modules during development instead of waiting for the application to be completely developed before assessing its performance.
7.1.3 Radioactive Material Transportation Requirements for the Department of Energy
Authors: Bolander Thane W. , John Mark E. , Fawcett Rick L. 
Published: September 2023

AbstractThe Department of Energy (DOE) created the National Transportation Program (NTP) whose goal is to ensure the availability of safe, efficient, and timely transportation of DOE materials. The Integration and Planning Group of the NTP, assisted by Global Technologies Incorporated (GTI), was tasked to identify requirements associated with the transport of DOE Environmental Management (EM) radiological waste/material. A systems engineering approach was used to identify source documents, extract requirements, perform a functional analysis, and set up a transportation requirements management database in RDD‐100. Functions and requirements for transporting the following DOE radioactive waste/material are contained in the database: high level radioactive waste (HLW), low‐level radioactive waste (LLW), mixed low‐level radioactive waste (MLLW), nuclear materials (NM), spent nuclear fuel (SNF), and transuranic waste (TRU waste). The requirements will be used in the development of standard transportation protocols for DOE shipping. The protocols will then be combined into a DOE Transportation Program Management Guide, which will be used to standardize DOE transportation processes.
8.1.3 Applying Engineering Principles to Human Components in Complex Systems
Authors: Kurstedt Harold 
Published: September 2023

AbstractSystems engineers must understand the workings within and the relationships among human as well as non‐human subsystems in the larger systems they're engineering. To be systems thinkers, we must easily and comfortably integrate human subsystems into complex systems. A key to approaching the human subsystems is to incorporate solution‐focused thinking that is based on circular and mutual causality rather than cause and effect. However, systems engineers can quite well apply their engineer's laws of physical science to human subsystems. The fundamental building block for systems that include humans is the dyad (two people). When anxiety rises in a dyad, the two people will attract a third human or non‐human subsystem to form a triangle. We can diagram dyads and triangles to better analyze, design, and implement complex systems containing human subsystems.
3.2.2 System Design and Validation Through Modeling and Simulation
Authors: Garrett D.G. , Wolff Jeffrey , Johnson T.F. 
Published: September 2023

ABSTRACTThis paper will discuss the methods and techniques required to successfully model and simulate modern avionics systems. Emphasis is placed on techniques to separate hardware and software models. The use of system model and simulations throughout the life cycle of a system is discussed. Several examples from the S‐3B Ada program are cited.
1.3.4 Three Types of Systems Engineering Implementation
Authors: Sheard Sarah A. 
Published: September 2023

AbstractINCOSE has been bedeviled by arguments about the definition of systems engineering. Many definitions have appeared, but the only one that is widely accepted is so broad as to be almost a tautology. As a result, INCOSE has been unable to answer many questions in a way that most members can accept.This paper claims that systems engineering can be defined in a way that leads to clean answers to many questions. This definition claims that what people have been calling “systems engineering” can be split into three basic implementations or types of systems engineering: Discovery, a discipline or specialist type that involves significant analysis, particularly of the problem space; Program Systems Engineering, a coordination or generalist type that emphasizes the solution space and technical and human interfaces; and Approach, a process type that can (and should) be performed by any engineer. Such a breakout resolves controversies and has implications on systems engineering training, research, processes, standards, and promulgation.
5.4.3 A Case Study in Modeling Company Policy Documents as a Source of Requirments
Authors: Crumpton Kathleen Marie , Gonzales Regina M. , Trauth Sharon 
Published: September 2023

AbstractThis paper describes an approach that was developed to produce structured models that graphically reflect the requirements contained within a text document. The document used in this research is a draft policy document governing business in a research and development environment. In this paper, we present a basic understanding of why this approach is needed, the techniques developed, lessons learned during modeling and analysis, and recommendations for future investigation.The modeling method applied on the policy document was developed as an extension to entity relationship (ER) diagrams, which built in some structural information typically associated with object oriented techniques. This approach afforded some structure as an analysis tool, while remaining flexible enough to be used with the text document. It provided a visual representation that allowed further analysis and layering of the model to be done.
7.4.2 The Systems Engineering Started in the Middle Process
Authors: Bahill Terry , Briggs Clark 
Published: September 2023

AbstractThe systems engineering process often begins somewhere in the middle of a project. Naturally, the systems engineering process should be different for a project where systems engineering starts in the middle versus a project where it starts at the beginning of the project. This paper presents a consensus of senior systems engineers at the Idaho National Engineering and Environmental Laboratory about how systems engineering should be done when it starts in the middle.
8.4.1 One Engineering Process – Integrated!
Authors: Denny Barbara , Bennett Richard 
Published: September 2023

AbstractProcess definition is not new at Rockwell Collins. Processes have been documented and repeatedly updated throughout the Rockwell Collins history. Process variations have existed due to the number of disciplines, Business Units, degree of adherence, level of senior management support, customer influence, etc. During the past two years Rockwell Collins has documented an enterprise level standard engineering process framework. The resulting Engineering Technical Consistent Process (ETCP) addresses the disciplines of Systems Engineering, Software Engineering, Hardware Engineering and Application Specific Integrated Circuits (ASIC) Engineering and is one of a suite of enterprise level processes that encompass the full business lifecycle.
5.5.1 The Shangri‐La of ROI
Authors: Sheard Sarah A. , Miller Christopher L. 
Published: September 2023

AbstractMany INCOSE members are dismayed that there are no hard numbers to justify implementation of systems engineering process improvement. This paper shows that: 1) There are no “hard numbers.” 2) There will be no hard numbers in the foreseeable future. 3) If there were hard numbers, there wouldn't be a way to apply them to your situation, and 4) if you did use such numbers, no one would believe you anyway.We have to get past fantasy and find out how to make the case for implementing systems engineering process improvement without these elusive hard numbers. This paper concludes with suggestions on how to build a case for process improvement that does not rely on hard numbers.
6.6.4 Case Study in Effective Government‐Contractor Partnering
Authors: Thornton John A. , Kinsinger Heide A. , Luczak Michael A. 
Published: September 2023

AbstractAny Department of Defense (DoD) acquisition program manager would argue for more funding and more schedule as a rationale for successful program execution, claiming his or her program is on a “fast track”. At the same time, the days of having relief provided due to cost overruns and schedule delays are becoming history, and such perils unquestionably increase the risk of unwanted scrutiny of programs. These realities have challenged program managers to seek new and innovative ways to manage their programs. The government and contractor program managers for the Space and Naval Warfare System Command's Advanced Deployable System (ADS) Program have responded to this challenge by developing an effective government‐laboratory‐contractor partnership, and utilizing this efficient relationship in virtually every facet of program planning and execution. The case study presented in this paper discusses how the ADS Underwater Segment (UWS) has used this partnership in planning and executing its 42 month program, which was completed on time and under budget. It provides lessons learned from this management experience for consideration by other program managers interested on embarking on such a path.
8.6.2 Systems Engineering – Consumer and Infrastructure Approaches
Authors: Kayton Myron , Ogan Ron 
Published: September 2023

AbstractSystems Engineering processes increase in complexity for infrastructure applications compared with consumer. The level of testing documentation, subassembly qualification and verification of simulation tools are important for infrastructure systems but are of minimal value for consumer systems. Requirements tracking and flow‐down from the customer performance specifications are more detailed and costly for infrastructure systems. Infrastructure systems that are based upon stable technologies, such as buildings or utilities usually do not use Systems Engineering processes.
9.1 Extending EIA‐731 Systems Engineering Capability Model Appraisal Method for Safety and Tailoring the Method to Yellowstone National Park
Authors: Alessi Sam , Johnesee James A. , Plowman Catherine M. , Siler Nelson 
Published: September 2023

AbstractIntegrated safety management requires that safety be integrated with basic management and engineering practices. The objective of this work was to add safety to the EIA‐731 Systems Engineering Capability Model Appraisal Method and thereby gain simultaneous and integrated findings. Safety appraisal information was gleaned from the Department of Energy, the Department of Interior, the Private Sector, the Occupational Safety and Health Administration, and other sources. This information was cast as a series of maturity‐oriented questions and added to EIA‐731. The integrated questionnaire was then tailored for application at Yellowstone National Park and the Idaho National Engineering and Environmental Laboratory. Results are not available at this writing due to delays in the scheduling of the appraisal, but will be included in a follow‐up paper. The integrated Safety Systems Engineering Capability Model Appraisal incorporates general safety principles that are applicable to any industry interested in project management, systems engineering and safety.