bluuebunny/crossref_metadata_2025_split huggingface dataset:
MANUFACTURING SYSTEMS ENGINEERING PROGRAMS IN THE UNIVERSITY
Authors: Mizdail Barbara E. 
Published: November 2014

AbstractThe systems engineer is the integrator in the process of design and manufacturing of products and services. The wealth generated by the manufacturing systems operating within a society is directly related to the quality of life. It is essential that the infrastructure underlying the wealth generating systems be capable of meeting the demands of our entire society. We are in an era of accelerating change. The education and training of future work forces, as well as the retraining of the present workers, must include interdisciplinary programs producing engineers capable of imparting knowledge integrated from a holistic view, and applying a systems approach to practical solutions. Students of such programs should be a mix of young graduate engineers in classes with seasoned industry experienced engineers sent by their companies for reeducation. Teamwork projects for this diverse group can prepare engineers to think in terms of the principle of concurrent engineering, and for work on project teams which gain strength through the combined talents of the group. Industrial leaders are actively changing traditional hierarchical management styles, and supporting retraining efforts. Meantime, academia must embrace interdisciplinary programs that teach engineering, manufacturing and business concurrently. This approach differs from traditional departmental programs which often focus on specific research. By industry and academia working together the ability to adapt to change will be taught; for change is inevitable and necessary for the future quality of life for our global society.
COMPUTER‐BASED COURSEWARE FOR SYSTEMS ENGINEERING EDUCATION AND TRAINING
Authors: Verma Dinesh , Sols Alberto , Fabrycky Wolter J. , Blanchard Benjamin S. 
Published: November 2014

AbstractSystems engineering is an integration activity which is difficult to teach by conventional means alone. Education and training efforts should be supported with computer‐based courseware to augment textbooks, technical articles, case studies, and other written materials. The purpose of this paper is twofold: to describe the approach adopted at Virginia Tech in the instruction of systems engineering courses and to describe the development and utilization of computer‐based courseware in these courses. While this courseware is applicable in teaching systems engineering generally, three academic courses and their continuing education counterparts will be featured as examples. These courses are: The Systems Engineering Process, Logistics Engineering, and Economic Evaluation of Projects.
SYSTEMS ENGINEERING EDUCATION AT DEFENSE SYSTEMS MANAGEMENT COLLEGE
Authors: Lightsey Robert H. 
Published: November 2014

AbstractThis paper discusses the role of Defense Systems Management College (DSMC) as one of the primary sources of engineering management education for future DoD program managers. The focus is on that portion of the curriculum at DSMC which is related to systems engineering. Specifically, the systems engineering curriculum content is examined in the context of other technically related courses offered at DSMC. Two courses in which system engineering instruction is at the heart of the material offered, the Program Management Course and the System Engineering Management Course, are described. A description of a hands‐on project modeled after similar engineering projects at MIT and other top engineering schools is also provided. The focus is on the systems engineering process as well as on system performance as the model evolves from concept to final production model. Finally, summary conclusions are drawn regarding the role of DSMC as a source of system engineering management education in DoD and the need for vision and team work with industry in the environment immediately confronting the defense industry.
BUILDING SYSTEMS ENGINEERING TRAINING IN INDUSTRY
Authors: Mengot Roy 
Published: November 2014

AbstractThis paper reviews the steps, trials, and pitfalls in designing and delivering a Systems Engineering training course in a company the size (about 5,000 engineers) of Texas Instruments' Defense Systems and Electronics Group (DSEG). The paper is a case study of our efforts in TI DSEG to field and deliver a Systems Engineering Workshop, over a four year period, that is now considered successful. The training initiation, development, reviews, and delivery aspects are highlighted.
DEFINITION OF AND TRAINING IN THE SYSTEMS ENGINEERING PROCESS – A NASA PERSPECTIVE
Authors: Fogle Frank R. , Woodruff L. Don 
Published: November 2014

AbstractThe need to capture the systems engineering knowledge base at NASA's Marshall Space Flight Center (MSFC) and make it available to the next generation of systems engineers gave rise to the development of a systems engineering handbook to help foster the systems engineering philosophy in MSFC's numerous young engineers. This paper will detail the development of the MSFC handbook, its history, and of special interest, will be a detailed discussion of the lessons‐learned while developing the handbook. In addition, MSFC has included this handbook as a training tool in conjunction with organized, formal, on‐site systems engineering training. The methodology and approach to this training effort will be delivered. The paper will also describe the updating and eventual integration of the MSFC systems engineering process into the NASA‐wide standard for systems engineering.
APPLICATIONS OF MODERN SYSTEMS ANALYSIS PARADIGMS TO THE DEVELOPMENT OF COMPLEX SYSTEMS
Authors: Biernacki J. , Bodi R. , Wagner R. , Juhasz J. 
Published: November 2014

AbstractThe overwhelming volume of requirements and specifications associated with large complex multi‐disciplinary system development projects pose exceptional challenges to project engineers in their efforts to track and manage the hardware design response to the requirements and specifications. Previous systems engineering approaches using available methodologies and automated computer tools have been increasingly difficult to apply as the project complexity grows. Without effective methodologies and tools ensuring that system functional requirements are accurately interpreted and flowed down to the specification level has been difficult. Likewise, the allocation of functions to the architectural components, assemblies, and software including the interfaces among interacting systems has been hampered by inadequacy of conventional tools. This traceability extends to the identification of verification requirements associated with all elements of the system.The demand for increasingly complex systems, coupled by the ever‐increasing sophistication of available supporting engineering and management tools, has spawned a variety of modern methodologies for addressing complex development tasks. These new paradigms, aided by powerful computer‐based software tools, provide a structured development framework to:
Instill a disciplined focus on system engineering based on requirements
Establish a comprehensive, unambiguous path of trace‐ability from top‐level requirements to detailed design
Provide a common means for communicating complex system behavior to all program participants via graphical depictions
Develop a platform for the systematic support of the verification and test planning activities
Analyze the failure propagation behavior of the system for assessment of multiple failure modes and effects, safety and hazards analyses, redundancy management and failure tolerance
Create a simulation environment to study system behavior for analysis of performance, interfaces, and anomalies given a variety of hypothetical operational scenarios.
This paper discusses the application of such a methodology, known as Enhanced Modern Structured Analysis (EMSA), which is being used in the analysis of the Space Station Freedom. The EMSA method has been derived from the methodologies of leading experts in the field of systems analysis, with suitable enhancements which were found necessary to accommodate the Space Station Program needs. The software to support this particular analysis is the RDD‐100 (TM) package from Ascent Logic Corporation, as well as the Failure Environment Analysis Tool (FEAT) developed by Lockheed Engineering and Sciences Company. The hardware platform is an Apple Mactinosh IIfx(TM).Due to the prolific nature of general systems analysis, coupled with the power of a sophisticated computer platform and the flexibility of the methodology, this paradigm is recognized as having a wide applicability for analysis.
Enhanced System Engineering Efficiency in the 21st Century
Authors: Zajac Blair 
Published: November 2014

AbstractThe trend has been to increased system complexity. It is anticipated that the trend will continue into the 21st century. This paper addresses the issues of how to accomplish system design (trade) and performance analyses in this environment. In particular, we examine an analysis technique that relates to both implementation methods and task partitioning.Recent advances in graphical programming computer technology have opened a new vista to enhancing the system engineering process. We start out with an introduction to this new technology. A general approach to using this methodology is then presented. This is followed by a specific application example using LabVIEW, a graphical programming language available on Macintosh computers.This paper is closed with a discussion of a technique where a target computer could be automatically programmed directly by the system engineer.
1.5.4 ROADMAP FOR SUSTAINED COMPETITIVE ADVANTAGE
Authors: Rhodes Donna H. 
Published: November 2014

AbstractSustaining a competitive advantage in the global marketplace is a continuous challenge. Fast paced changes in technology, re‐engineered processes, revolutionary acquisition reforms, and highly sophisticated enabling techniques and toolsets are impacting our business. Without a proactive approach, it is easy to fall behind or “get off track”. Well‐defined roadmaps are needed to guide growth and change. While many businesses today develop business and technology strategies, these are not enough. A Systems Engineering Core Competency Strategy is equally essential to engineering organizations who will remain competitive in the next decade. This paper presents the key elements of this strategy, including recommendations for its development and use, and lessons learned based on a decade of experience.
3.1.1 SYSTEM ENGINEERING THE PEOPLE SYSTEM
Authors: Minds Kevin S. 
Published: November 2014

AbstractThis paper describes an architecture study for a system with the objective of developing a corporation's core competence in Systems Engineering. The study focuses on people as the key resource to be leveraged upon in order to achieve this objective. A system called the People System is postulated and defined by applying a tailored version of the Systems Engineering process.
3.2.1 Matching Tools to the Systems Engineering Process
Authors: Oliver David W. 
Published: November 2014

AbstractThe goal of this paper is to map the steps of the systems engineering process to classes of tools. This is an application of systems engineering with models and objects. It results in a rigorous definition of the functions performed by each tool class, the information captured by each tool, where in the engineering process the tool is used, and the interfaces between the tools. This paper utilizes the tools taxonomy described previously, [Oliver, Steiner 1994].The tools automate the systems engineering process. Each kind of tool performs particular functions and captures particular sets of information. In this paper the tools are mapped to a meta‐model for the systems engineering process. That meta‐model describes the core systems engineering steps and gives an information model for each step, [Oliver 1994a]. The meta‐model of the systems engineering process describes the engineering steps that have emerged over the years as best practices. It describes the sequences that are imposed by reality and defines as concurrencies those steps that may be performed either concurrently or in several different sequences. The mapping then establishes the interfaces between tool types; how the tools should integrate.This paper focuses on the tools used in association with requirements engineering and management as a specific example. An NCOSE survey of member priorities for tools disclosed that tools for requirements engineering and management were a top concern and the Tools Technical Committee elected to focus 1994 and 1995 efforts on this topic. This approach, using models and objects is rigorous and readily altered as new tools classes or engineering steps are identified through engineering experience.
3.2.3 COTS Integration and Support Model
Authors: Waund Carolyn K. 
Published: November 2014

AbstractPrograms requiring system development with high content of Commercial off the Shelf (COTS) hardware and software are becoming more prevalent in the federal marketplace. Much of the emphasis on COTS solutions is driven by the need to lower the cost and deployment time of new systems to meet reduced budgets. Another factor is the availability of powerful COTS information systems technology to facilitate government processes.Loral Federal Systems (LFS) has in recent years moved to address this important systems integration market. Individual projects achieved varying degrees of success in adapting traditional system development processes and management practices in the high‐COTS environment. This project experience is a key resource. This paper highlights the results of an LFS initiative to use lessons learned on recent COTS‐based projects to define a COTS integration and support model for guiding future projects. This initial model will be refined and matured by the LFS organization in the future. This paper provides: (1) observations about the current state of COTS integration, (2) description of a model for a COTS integration and support process, and (3) discussion of COTS project lessons learned and their incorporation in the COTS process.
7.2.1 A REQUIREMENT AND VERIFICATION TRACEABILITY TOOL
Authors: Elmore Donald C. , Cabrera Orlando J. 
Published: November 2014

AbstractThis paper will present the background, development, and use of a requirement and verification traceability (RVT) tool for Systems Engineering. Beginning in the late 1980's, System Engineers in the Government Communication Systems Division of Harris Corporation began to develop an automated tool to support RVT. Working within the framework of our Total Quality Management (TQM) initiative, a team of System Engineers developed a tool that has been used on a multitude of programs. The RVT information is embedded in the program's documentation (specification, statement of work, interface control documents, etc.) and then a parser is used to populate a database. Once in the database, requirement and verification reports and matrices are generated using Structured Query Language (SQL). For several years, this tool has served the needs of our System Engineering staff and has received accolades from our customers.
AUTOMATING THE MANAGEMENT OF INTERFACE DATA
Authors: Niedermuller Bob 
Published: November 2014

AbstractGeneration and maintenance of interface data are a significant part of the Systems Engineering effort on most programs. Typically the control is accomplished through Interface Control Documents (ICD's). The data used to generate the ICD has many other applications, such as wire lists, loads analysis, weights reports, etc. In most applications the ICD is actually a subset of the available interface data, and control and maintenance of this data is a multifarious task. Using an electronic database to record all interface data and generate the ICD and other required data from the resulting database cannot only save a significant amount of effort, but can improve the quality and data consistency. This process can enhance the Systems Engineering effort throughout all phases of the program from inclusion of initial interface Requirements, through Functional Allocation, Design Synthesis, Interface Management, and Verification.This approach was used to generate interface documentation for an Unmanned Air Vehicle to Automatic Test Equipment (ATE) interface. The process has proven to be less labor intensive than previous methods, and has shown significant savings in updates and generating related documents from the same database. When maintained on a network, it allowed the systems engineers working the interfaces access to the latest data, without having to generate and control printed copies. This paper will discuss the factors that must be considered in implementing an interface management database, such as selection of a DBMS program, data formats, control of the database, and will discuss the experience gained from this application, and will provide examples of the results.
SYSTEMS PERSPECTIVE TO DESIGN OPTIMIZATION
Authors: Hines Jim , Abbatine Michael S. , Fry Keith 
Published: November 2014

AbstractRockwell Space Systems Division has been undergoing dramatic changes in the last three years to embrace the Integrated Product Team (IPT) development concept. The architecture of the design system operates is critical to our mission in becoming cheaper, faster, better. Our design architecture is evolving from one that is a byproduct of the design to one of driving good design. A key element in the design process is the interconnectivity of systems and design engineering.This paper discusses the changes that are occurring in people, processes and technologies which are evolving to produce cost effective, designed products by Rockwell Space Systems Division. A modification product design case study involving tool integration known as Enterprise Process and Data Management (EPDM) will be examined in more detail.
3.3.2 LOCKHEED'S SYSTEM ENGINEERING COUNCIL
Authors: Jaggers Jerry , Khouri Jennifer 
Published: November 2014

AbstractLockheed Missiles & Space Co., Inc.'s (LMSC's) Space Systems Division (SSD) has long had a system engineering council, where senior system engineers from all the division's lines of business meet to guide the division's system engineering activities. After a temporary cessation due to a division reorganization, the council has again resumed activity, with a new charter, concrete goals, and renewed interest in preserving and strengthening our core system engineering capability. This paper addresses the history of the council, the required resources, the lessons learned, and the future plans for the council.
4.1.3 A RIGOROUS METHOD FOR FORMAL REQUIREMENTS DEFINITION
Authors: LaPlue Larry , Garcia Ruth A. , Rhodes Robert 
Published: November 2014

AbstractThe authors propose a formal method for writing behavioral requirements usable by a broad spectrum of system engineers. The method includes a requirement template with specific syntax to include all relevant aspects of a behavioral requirement, a “black box” approach to system analysis and a unique organization for requirements specification. The method addresses the most commonly encountered problems that engineers face when writing and maintaining requirements. The paper describes these problems, provides details of the method, and justifies the unique features of the method. Directions for future research to improve the method are also provided.
6.1.3 REQUIREMENTS MANAGEMENT: CONTRASTING TRADITIONAL SYSTEMS AND SOFTWARE ENGINEERING METHODS
Authors: LaBudde Edward V. 
Published: November 2014

AbstractTraditional system engineering has been the source of most of the requirements' decomposition and management techniques. Requirements' decom‐ position and flow down concentrate on a top‐down mission oriented view. The emphasis is on functional flow (input/output), black box performance allocation, and system interaction. However, it is weak in areas like operating logic, behavior, and timeline requirements.We contrast and compare the requirements' process and management techniques for the traditional system engineering and modern software approaches. We can indicate at least one gap in the area of operating logic and timeline analysis as well as numerous important under laps.Consequently, the design of many computer‐ based systems suffers from a substantial risk at the interface between system and software design engineering. The gap, created by a failure to address operational logic, sequencing, performance and timeline requirements in both disciplines, can have a major impact on program cost, schedule, and performance. Potentially, major safety related risks may result from the gap in logic and timeline requirements' tracking and allocation. In addition, significant under laps occur in operational analysis, interface control, performance, human factors, risk analysis, trade‐off studies, reviews, and planning. Therefore, these can create a risk if the software engineering effort is weak in traditional system engineering discipline. Suggestions for reducing the gap and under lap are offered.
A Formalism for the Specification of Operationally Embedded Reactive Systems
Authors: Sherry Lance 
Published: November 2014

AbstractThe Operational Procedure Information Model, presented in this paper, provides a formalism for the specification of the behavior of operationally embedded reactive systems found in aircraft guidance and navigation systems. The information model assigns semantic interpretations of the operational procedure construct to the elements of a finite state machine. The operational procedure construct captures the embedded operational behavior of the system over all the missions in the life‐cycle. The finite state machine captures the reactive behavior of the system.The information model, captured in a database and interrogated through a graphical user‐interface, can be used for simulation, analysis, and the generation of code and documentation.
2.2.3 PEOPLE CAPABILITY MATURITY MODEL (P‐ CMM): INCORPORATING HUMAN RESOURCES INTO PROCESS IMPROVEMENT PROGRAMS
Authors: Hefley William E. , Curtis Bill , Miller Sally , Konrad Michael 
Published: November 2014

AbstractThe People Capability Maturity Model (P‐ CMM) is an adaptation of the Capability Maturity Model SM for Software (CMM SM) focused on developing the organization's talent. The motivation for the P‐ CMM is to radically improve the ability of software organizations to attract, develop, motivate, organize, and retain the talent needed to steadily improve software development capability. Although being initially developed with a focus on software and information systems development, the principles and many practices of the P‐ CMM apply equally to systems engineering. There is thus on the horizon a family of capability maturity models to help organizations improve their development capability: the CMM for Software, the Systems Engineering CMM (SE‐CMM), and the P‐CMM.
6.2.4 A Methodology for Capturing An Organization's Systems Engineering Best Practices
Authors: Walden David D. 
Published: November 2014

AbstractAs part of Computing Devices International's journey to become a Six Sigma company and a World Class Systems Engineering organization, numerous process improvement teams have been formed. One such team is the Systems Engineering Best Practices Team, whose charter is to determine and document the best Systems Engineering practices currently being used in the organization.This paper describes the methodology that was used by the Systems Engineering Best Practices Team. The methodology is based on a survey followed by an iterative elaboration of each process in priority order. In addition to defining the process used for each of the best practices, Six Sigma and Systems Engineering metrics were also included. The paper also shares some of the lessons learned through application of this methodology.