bluuebunny/crossref_metadata_2025_split huggingface dataset:
SYSTEMS ENGINEERING ‐ BEYOND MIL‐STD‐499B OR THE BRILL PARADIGM OF SYSTEM ENGINEERING
Authors: Brill James H. 
Published: September 2023

AbstractThis paper goes beyond the systems engineering construct of MIL‐STD‐499B and suggests private and public enterprises would benefit from viewing systems engineering as a “system.” The suggested paradigm (model) synthesizes the author's original concepts, portions of MIL‐STD‐499B (Draft, May 1992) and proceedings of the 23–25 October 1992 NCOSE sponsored committee meeting on a systems engineering capability maturity model. The model's concentric design incorporates the system elements and system primary functions of MIL‐STD‐499B, but moves the “customer” bulls‐eye to an outer‐ring labeled “Business Environment,” and identifies people, process, and technology as the three key components of systems engineering. Each of the key components is decomposed to lower levels of detail.The paradigm presented is intended to have universal application and not be limited to defining, evaluating, and improving systems engineering efforts in defense system acquisition and technology programs. Lastly, it is hoped that the paper's content will stimulate others to take a more “systems” view of “systems engineering.”
THE NEED FOR SYSTEMS ENGINEERING EDUCATION
Authors: Samson Charles H. , Lowery Lee L. 
Published: September 2023

AbstractAs engineering specialization has increased, engineering education has also become more specialized in order to keep up with advances in technology. Likewise, engineering faculty have tended to become more specialized to keep pace with such advances, and to conduct research and publish at the leading edge of their fields. These circumstances have exacerbated the problems of melding specialized skills into a form for achieving the best designs of complex systems.The writers believe that it is essential:
To require adequate preparation in systems engineering for every engineering graduate.
To provide opportunities for generalization in systems engineering for those who wish to become “general practitioners” capable of integrating the various specialized skills needed.
The writers suggest an approach to satisfying these needs that would complement rather than compete with existing engineering disciplines.
AUTOMATED SUPPORT FOR MANAGING SYSTEM REQUIREMENTS
Authors: Kovarik Vincent J. , McGhan James N. , Myjak Annette R. 
Published: September 2023

AbstractThe development of requirements for large systems is a complex and iterative process. Adequately maintaining a requirements set for large systems with multiple configuration items quickly becomes an intractable problem. This paper presents an approach which applies object‐oriented modeling techniques to represent the interrelationships between requirements and provide traceability to subsequent, related development products. The ability to automatically compute transitive closures over user‐defined relationships provides a powerful yet simple mechanism for tracing the impact of a requirement change to potentially affected components. This model of requirements relationships is complemented by the ability to model the content and structure of specification documents. By applying the representation of the document structure, coupled with a database query capability, the system can generate a System Segment Specification, Software Requirement Specification, and a Software Design Document based on the contents of the model.
DECISION ANALYSIS TOOLS AND THEIR APPLICATION TO THE SYSTEMS ENGINEERING PROCESS
Authors: Layton Robert L. 
Published: September 2023

AbstractThis paper describes how the use of decision analysis tools can enhance the systems engineering process. Two case studies are presented showing how the tool Criterium™ was used to select a supercomputer and to select a more accurate and less expensive inspection system for 20 foot aluminum I‐beams that attach wings to airplanes.
A SYSTEMS ENGINEERING APPROACH TO IMPROVING THE PEANUT GRADING SYSTEM
Authors: Dowell Floyd E. , Konstance Richard P. , Meyer Charles R. 
Published: September 2023

AbstractSystems engineering was used to identify peanut grading system needs, establish requirements, and compare proposed solutions that meet consensus specifications established by all industry segments. Previous attempts to change the grading system were hindered by difficulty in getting all segments to agree on proposed changes. The systems engineering approach overcame this obstacle. Four conceptual designs that improve the current system are at various stages of development and implementation. These improvements are: high moisture foreign material identification; measuring moisture during sampling; measuring single kernel moisture; and grading larger samples with an automated sample cleaning, shelling, sizing, and data collection system. Each of these improvements help ensure consumer demands for quality are met while not unfairly burdening any one segment of the peanut industry.
Implementation of a Bait Adulticide Technology for Corn Rootworm in Integrated Farm Management Systems: a Systems Engineering Approach
Authors: Westbrook John K. , Steiner W.W.M. , Alessi R. Samuel 
Published: September 2023

AbstractThis paper presents a consistent approach to the development of interdisciplinary research plans and transfer of technology from Agricultural Research Service laboratories. Specifically, this case study discusses the implementation of a bait adulticide for an agronomic pest insect (corn rootworm) within an integrated farm system. Prospects for the use of systems engineering within the Agricultural Research Service for research planning, conduct and evaluation are discussed.
Mil‐Std‐499B and the Practice of Technical Reviews
Authors: Fisher Jack , Lake Jerry 
Published: September 2023

ABSTRACTAlthough technical reviews are an important part of the systems engineering process, they have not received a great deal of attention in systems engineering literature. In this paper, technical reviews are discussed for a DoD acquisition program from both the government and contractor's perspective. Requirements for technical reviews that will be included in the about to be released Mil‐Std‐499B are summarized, including descriptions of types of reviews, review sequence, and review content. Opportunities for tailoring review requirements are discussed for several types of programs. Both government and contractor review responsibilities are discussed in light of the new incremental review and integrated product team approach in Mil‐Std‐ 499B. The various steps in the contractor's process for conducting a review are described, including the content of a contractor's technical review plan and the roles of each participant in a “typical” review. Techniques for obtaining approval of a technical review by closing out action items are discussed.
IMPLEMENTATION OF A REQUIREMENTS VERIFICATION DATABASE
Authors: Brown Dean D. 
Published: September 2023

AbstractThis paper presents a case study on the implementation of a requirements verification database by the Systems Test Department on a large Westinghouse program. By selecting the appropriate requirements traceability tool, verification reports were created that provided visibility into the verification of approximately 3,000 requirements, improved the test procedure generation process, and enhanced communication. Making the database easily accessible to the test engineers ensured that all verification decisions were documented and all requirements accounted for.
SYSTEMS ENGINEERING CAPABILITY MODEL FOR STRATEGIC IMPROVEMENT
Authors: O'Neill Don 
Published: September 2023

ABSTRACTThe Systems Engineering Process Capability Maturity Model is organized around the key concepts in the Malcolm Baldrige National Quality Award Examination criteria. It introduces a model for systems engineering success and the Total Quality Management infrastructure prescription which places a premium on experience with the customer and his problems, the company's products and its solutions, and the processes for engineering and management needed to deliver operational solutions.Systems engineering capability is organized into a set of models to guide an organization towards success in several essential dimensions. Using these models, a series of assessment instruments are derived to assess systems engineering process maturity, evaluate systems engineering capability, examine systems engineering capacity, identify system risks, review systems project performance, inspect systems engineering products, and survey customer satisfaction. “Quick look” instruments identify risks to systems engineering success, and “probe” instruments pinpoint the specific weaknesses in each element. A well defined improvement process details the risk identification, confrontation, and resolution activities.
CONFIGURATION MANAGEMENT OF NONCOMMERCIAL‐USE SOFTWARE
Authors: Nisargand Arun 
Published: September 2023

AbstractA review of the Software Configuration Management (SCM) standards, both military and non‐military, shows that these satisfy the needs of large software systems developed for government agencies and other outside customers.Not all the software developed by large organizations, however, is for outside customers. Much of the PC based software developed in large organizations is never marketed to outside customers. Though used in‐house, it is subjected to the same rigorous configuration management standards that are used for large software systems. This is expensive and may not be necessary.The following paper describes essential elements of Software Configuration Management and how they can be simplified and applied selectively to increasingly smaller software development projects without sacrificing credible configuration management.
DUAL DOORS TO THE SYSTEMS SUITE
Authors: Reilly Norman B. 
Published: September 2023

ABSTRACTThere are at least two doors into the chambers of systems engineering. One is the more traditional gateway of aerospace, big government systems and high‐tech. The other is the more recent industrial portal of concurrent engineering and the quality movement. As we mix in the ‘big room’ there is often confusion among us. Has concurrent engineering replaced the older paradigms, such as the staircase (waterfall) model? Should conventional system design teams now become quality teams? What are the organizational implications? As we learn to do business differently, is there a generic structure to guide us? If so, what should we change and what should we keep? This paper examines the traditions of the past and the promise of the future and proposes a wedding that can guide our perspectives in the midst of dramatic change.
MCDONNELL DOUGLAS AEROSPACE AVIONICS ENGINEERING PROCESS HANDBOOK
Authors: Hlavaty Charles W. , Welch J. Douglas , Wolf Renard C. 
Published: September 2023

AbstractThis paper describes the McDonnell Douglas Aerospace (MDA) Avionics Engineering Process Handbook. The handbook describes MDA's processes for avionics engineering, which are based upon DoD's requirements as delineated in DoDI 5000.2, MIL‐STD‐499B, MIL‐STD‐973, MIL‐STD‐490A, and other Government documents. DoD's acquisition phase requirements, configuration baselines, and program reviews are used as a basis for the documented processes. MDA's baselines, which form the informational basis for the DoD baselines, are described. DoD's reviews are supplemented with MDA‐defined reviews to produce event‐driven program models, which are described. Key types of process documentation used in the handbook to detail the engineering process are also described.
Systems Engineering Case Study: A Software‐Driven Whole‐Farm Management Information System
Authors: Alessi R. Samuel , Vang Leng , Hjelmfelt Eric , Mayhew Michael E. , Voorhees Ward B. 
Published: September 2023

AbstractFarming involves complex interaction among natural and manmade resources. This results in high‐risk decision‐making for farm managers. A farm‐based management information system would aid the manager by providing records of past farm operations and production, in addition to forecasting possible outcomes of future management decisions. This paper presents an attempt to use systems engineering principles for the design and construction of a farm management information system. Improved understanding of farm problems and system requirements have resulted from intimate involvement with users and a prototyping process to capture requirements. Design, prior to software coding, is being implemented and has enabled clearer and more complex communications between the designer and programmer. These systems engineering principles are directly responsible for the increased functionality and usability of the software‐driven system.
6.1.4 The Telecommunication Domain ‐ a Challenge for INCOSE
Authors: Kaffenberger Ruediger 
Published: September 2023

AbstractThe telecommunication sector harbours the true giants among the artificial systems. Telecommunication systems have the largest physical size of man made systems, they have the most users and the largest commercial value. Telecommunication systems have even outpaced the automobile in respect to its impact onto society. However, despite these facts and despite humankind relies on the availability and effectiveness of telecommunication systems, one finds only few contributions from individuals or organisations of the telecommunication industries to the science of systems engineering. In this paper, the outline of an alternative systems engineering profile of the telecommunication domain will be presented. This profile will be used to illustrate why systems engineering in the telecommunication domain is different and why INCOSE should be interested in it.
8.1.2 Systems Engineering in a Public Interest Project: Providing a Web Based Communications Capability
Authors: Roberson Janet Villa , Bauknight Gerald C. 
Published: September 2023

AbstractThis paper describes an application of the systems engineering process in a public interest project. The purpose of the project was to support the Salinan Native American Nation in an unobtrusive way that was important to the nation. This goal was identified through action research discussions with a Salinan Nation leader and the tribal council. The chosen project was to develop a web based communications system for this virtual nation. The authors selected the INCOSE “How To” Guide as a process to develop this project. The project is outlined through its planned completion and lessons learned from this project are considered for similar future projects.
3.2.1 Progress towards Systems Modelling for the Extended Enterprise
Authors: Sims P.F. , Epifanie A. , Fitzgerald G. , Lott J. , Miles D. , Plastow I. , Slack C. 
Published: September 2023

AbstractThe paper will describe the Airbus Integrated Modelling Environment (AIME) developed at BAE SYSTEMS. The AIME provides the ability to produce a single integrated system simulation using a number of different specialist modelling tools. In an AIME based model for the A340–600 Aircraft, Flowmaster® is used to accurately predict the fluid mechanical behaviour of the fuel system, Simulink® to filter and process fuel probe signals and accurately gauge tank quantities, and Statemate® to simulate the control functionality. The user can interact with all of these tools at any point in time while running a dynamic simulation of overall system behaviour.The open nature of the AIME is allowing the Airbus extended enterprise to integrate a Parker Aerospace developed model of fluid mechanical behaviour with the British Aerospace developed Control and Indication models. Integration of the models allows the companies to reach a common understanding of the target system's required functionality.
4.2.2 The Perception‐Reaction Simulation Model for Enterprise Control Systems
Authors: Gibson Ralph D. 
Published: September 2023

AbstractThroughout the history of warfare, battle decisions have been made based on the perceptions of both friendly and enemy forces. Perceptions in early history were based on visual sightings and relayed back to the commander through a slow communication system of runners. Technology has changed the methods of information collection and transmission, but the concept of battle has not changed the fact that commanders make decisions based on their perception of the battlefield. What technology has done is to place so much information in front of the commander at an ever increasing pace that misunderstanding or completely missing vital information could drastically affect the outcome of the battle. The purpose of the Joint Force Air Component Commander (JFACC) Project is to revolutionize military command and control, specifically in Joint Aerospace Operations. The Joint Air Operations Enterprise will consist of three major components: a control system, a feedback system, and a plant. This paper discusses the use of a perception‐reaction simulation model to perform the physical actions of the plant. The definition and relationship of the three components are described in terms of their contribution to the Joint Air Operation Enterprise. A description of the perception‐reaction model and its relationship to the physical actions of the battlespace are given. Examples of current perception‐reaction methodology are provided. Finally, the perception‐reaction model is integrated into the Joint Air Operations Enterprise, and it is shown how the perception‐reaction model can fully support the enterprise.
6.3.4 Approaches to Certification of Reconfigurable IMA Systems
Authors: Hollow Paul , McDermid John , Nicholson Mark 
Published: September 2023

AbstractThe aerospace industry has been investigating integrated modular avionics (IMA) for some years. IMA offers greater flexibility in the use of computing resources by reconfiguring the software to employ different processors and communications, in order to recover from failure and to redistribute workload. Such reconfiguration offers benefits, but poses difficulties for certification since current certification practice requires assessment of each configuration.The approach we have adopted is to seek means of clearing a configuration of a system and to identify a number of “equivalent” configurations. This requires us to establish “safe” reconfigurations for the IMA system. Technically, we have formulated the search for a set of “equivalent” configurations as a multi‐objective optimisation problem. Pragmatically, the search produces configuration tables which could be used by the IMA operating system to make a “safe” change to an “equivalent” configuration, when necessary.
8.3.2 Risk Reduction Through Changing Success Criteria
Authors: McKinney Dorothy 
Published: September 2023

AbstractIn the 1990's the big challenge was how to streamline processes to produce systems better, faster and cheaper. In this new decade, the big challenge looming before us is how to dynamically adjust the success criteria for a project to increase its chances for success. Dynamic adjustment of success criteria is one of the most cost‐effective ways to minimize project risk in the dimensions which are most critical to our customers and our companies, such as: cost, time‐to‐market, product features, system stability and evolvability. Precisely targeting system development processes for the level of acceptable risk, while using metrics effectively to ensure that results match intentions, is a challenge best met jointly by program managers and systems engineers. This paper describes this challenge, and offers some approaches for collaboration which might make both program management and system engineering jobs more doable, while improving chances of successful program completion.
1.4.1 A Development Guide of Robust System Architecture
Authors: Yoo Il Sang , Kim Jae Chul , Park Young Won 
Published: September 2023

AbstractThe term Systems Architecting (SA) is widely used in systems engineering area, but the explicit meaning of the term varies considerably from person to person, depending on his expertise and viewpoints. In this paper, we surveyed the range of variations in definitions and presented the summary. Additionally, the definition of robust systems architecting is suggested along with the associated systems architecture guides that can be followed during architecture development. These guides are written from the viewpoints of art side, requirement specification, system view, principle, tool and environment.
4.4.3 Using A System Object Methodology in Software Intensive Systems
Authors: Wray Richard B. 
Published: September 2023

ABSTRACTSystems Engineering typically relies upon functionally oriented system definition. However, for software intensive systems that rely upon object‐oriented development, functionally oriented system definition provides insufficient input to software development. Development of object‐oriented software can be improved by providing input to the software process using an object‐oriented system methodology that merges precepts from the Fusion Methodology and the Unified Modeling Language. A hybrid system object methodology must establish at least the user/system context and the models of the key elements of a system design (including the system object model, life cycle model and operations model). Relationships between these models in the methodology include definition of the system boundary, classes and attributes of objects, events and system operations. This paper summarizes underlying object modeling precepts important to systems engineering and describes this hybrid system object methodology.
5.5.2 The Effectiveness of Multiple Software Requirements Elicitation Methods — A Case Study
Authors: White Sara , Gonzales Regina M. , Johnson Eric 
Published: September 2023

AbstractRequirements engineering methods have been developed to assist in requirements specification. Teaching these methods to college engineering students should prepare students to develop a more complete, consistent, and testable requirements specification than they would have developed if they had not used these methods. The “Software Metrics Toolset Software Requirements Specification” was developed using several requirements engineering methods and was completed in Fall 1997 EE590 Software Systems Engineering II class. This report will compare the final set of requirements from the Software Metrics Toolset (SMT) Software Requirements Specification to the developed SMT for completeness and cost impact. The software requirements elicitation methods used in the development of the Software Metric Toolset effectively limited the cost of requirement changes in the actual development and customer delivery stage to less than 3% of the budgeted cost. The results underscore the value of using multiple methodologies that look at different aspects of the requirements.