bluuebunny/crossref_metadata_2025_split huggingface dataset:
MANAGING REQUIREMENTS EFFECTIVELY IN THE CONCURRENT ENGINEERING ENVIRONMENT
Authors: Bukwa Russell , Rhodes Donna 
Published: November 2014

AbstractThe concurrent engineering environment can be characterized by three key factors: (1) a structured systems engineering approach employed by a cross‐functional development team; (2) the use of quality engineering techniques; and (3) an integrated development environment which facilitates and integrates systems analysis, development, and design. This paper will introduce the RMat Requirements Baseline Management System, developed and used by IBM Federal Systems Company (FSC) in Owego, New York. RMat's role in facilitating concurrent engineering will be discussed in the context of these key characteristics.
The Next Step: The Industrialization of Systems Engineering Tools
Authors: Young Arnie 
Published: November 2014

AbstractThis paper discusses the current trend of system engineering tools to focus on production‐oriented solutions rather than feature‐oriented products. This trend is spearheaded by engineers demanding more than a drawing and thinking aide ‐but rather tools that unify the product delivery life cycle and provide unambiguous communication between system engineers and designers ‐ tools that guarantee that the developed system reflects the one specified. This paper draws as a parallel, the industrialization of the CAD/CAM industry during the 1970s. Also, a correlation is shown between today's electronic CAE industry and how its set of tools are forcing systems engineers to rethink their definition of deliverables.
A SYSTEMS ENGINEERING CAPSTONE DESIGN EXPERIENCE
Authors: Scherer William T. , White Douglas J. 
Published: November 2014

AbstractWe describe the senior capstone design course in Systems Engineering at the University of Virginia. The capstone course is a major design experience for the students that involves the students in real design problems while working with real clients in order to expose the students to the practice of systems engineering. Working in groups with five or six members, the students apply the systems engineering aspects of systems and decision science, systems management and systems methodology toward open‐ended design problems. Our experience with the program for the first three years has led to considerable success, with numerous capstone groups receiving commendations from clients and the Department of Systems Engineering receiving ABET's first Award for Educational Innovation.
SYSTEMS ENGINEERING TOOL INTEGRATION STANDARDS: THEIR IMPACT ON SYSTEM QUALITY AND PRODUCTIVITY
Authors: Sharon David 
Published: November 2014

Abstract‐ CASE, Computer‐Aided Systems Engineering, is an excellent acronym to be applied to all the managerial, technical, maintenance and support activities in building new systems and enhancing existing systems. This paper will describe the key software engineering standards and technology trends affecting our ability to develop higher quality software more productively. The components of a complete CASE environment will be described along with the major technical and organizational issues in implementing CASE along with a reference model and description of each major CASE standards effort.
SAFETY AND RELIABILITY ISSUES IN SAFETY‐RELATED SYSTEMS
Authors: Zucconi Lin 
Published: November 2014

ABSTRACTThe increasing number of accidents attributed to computer‐based systems is causing increased public awareness of the risk associated with these systems' use in safety‐related applications. Examples include the Therac‐25 medical LINAC deaths, the growing number of Airbus A320 crashes, the AT&T Long‐Lines disaster on Martin Luther King Day in 1990, the spate of regional telephone outages of the summer of 1991, and many more. How do safety and reliability sometimes conflict? What practical computer system and software development technologies and processes can be applied to increase the safety and reliability of computer systems? What are the technical and managerial issues contributing to the construction of less‐than‐safe computer‐based systems? How can systems engineers and software engineers work together to address the issues related safety and reliability of computer systems? This paper will address these topics and include an assessment of the best current state‐of‐the‐practice and of upcoming technologies that will carry us into the 21st century.
3.1.3 NEW CONCEPTS OF SYSTEMS ENGINEERING AT THE AEROSPACE CORPORATION AND THE SPACE AND MISSILE SYSTEMS CENTER (SMC)
Authors: Rountree Richard C. , Castro Robert P. , Guillen Andrew T. 
Published: November 2014

AbstractThe Aerospace Corporation sponsors in‐house research to enhance and extend the corporation's core competencies. The objective of one Aerospace Sponsored Research (ASR) was to develop new concepts for systems engineering, consistent with Integrated Weapon System Management (IWSM)/ Integrated Product Development (IPD) environments, by addressing methodology, guidance and training, and computer‐aided tools. The ASR had five primary objectives including defining an Systems engineering/ Configuration Management (SE/CM) methodology, developing guidance and training, investigating computer‐aided SE/CM tools, maintaining Aerospace role introducing SE/CM concepts to the Space and Missile Systems Center (SMC), and ensuring cross‐information flow of lessons learned between SMC System Program Offices (SPOs) and external customers. Significant accomplishments were made toward satisfying each of the stated objectives, especially achieving the opening of an operational SMC IPD Center.
6.3.1 The Use of Systems Engineering Tools in the Classroom
Authors: Buede Dennis M. 
Published: November 2014

AbstractThis paper clarifies the value of using state‐of‐the‐art systems engineering tools (SETs) in the classroom, both at the undergraduate and graduate level. The goals for using SETs in the classroom as well as the lessons I have learned from trial and error experiences while trying to use them effectively. These lessons learned are based upon my experiences using DesignIDEF (Meta Software), RDD‐100 (Ascent Logic), and CORE (Vitech Corporation) over the past four years in the classroom and on research projects with students. I conclude that the benefits of this activity far exceed the costs (which are not inconsiderable) and that each SET must be approached uniquely in designing classroom activities.
1.1.1 SYSTEMS ENGINEERING IN WILDERNESS AREAS MANAGEMENT
Authors: Dolton Theodore A. , Hoy John P. , Martin Frederick 
Published: November 2014

AbstractWe describe how Systems Engineering (SE) can support our National Forests by applying SE methodology to creating a management plan for wilderness areas. We posit that a wilderness area is a large and complex system, and we are transferring a technology for engineering large complex systems to this new domain.The National Forest Service (NFS) has developed its own planning process, known as the Limits of Acceptable Change (LAC), for developing or upgrading wilderness areas management plans. We analyze the LAC process as a planning and management tool for the NFS and compare it to a tailored SE process.The key features in our SE are: (1) treating the wilderness as a system; (2) considering human use (recreational, business and educational) in balance with the natural characteristics, by incorporating a dual path process with one path for each; and (3) allowing a series of tradeoffs among alternates for the wilderness system management plan.
1.1.2 MAINTENANCE BUDGET ALLOCATIONS IN FISCALLY CONSTRAINED ENVIRONMENTS USING RISK CONSTRAINED OPTIMIZED MAINTENANCE PLANNING (RCOMP)
Authors: Douglas Freddie , Fogle Frank R. , Mog Robert A. , Williamson A. Sean , Riggs Jeffrey L. 
Published: November 2014

AbstractBudgetary considerations are forcing organizations to become more cost‐effective entities. Selected operations research techniques have been integrated into the Risk Constrained Optimized Maintenance Planning (RCOMP) tool to provide decision support for this process. The RCOMP tool allows for the exploration of tradeoffs between life cycle cost and total maintenance time and between net investment and total maintenance time for a system. The tool also facilitates the selection of the optimal mix of preventive and corrective maintenance as well as the most cost‐effective maintenance acquisition strategy.
2.1.4 DEVELOPING A SYSTEMS ENGINEERING APPROACH FOR THE HANFORD RETRIEVAL, TREATMENT AND IMMOBILIZATION DIVISION BASED ON DOD STANDARDS
Authors: Saladin Vincent L. 
Published: November 2014

AbstractThe DOE Systems Engineering effort is in the “Hot Seat” at the Hanford Nuclear Site. Hanford has been designated as the site at which the Systems Engineering approach for all DOE will be developed. Conditions are excellent for a major success or failure. Given that DOE does not have a standard in place defining Systems Engineering, and that the number of people with knowledge of Systems Engineering is limited, an overwhelming success will be difficult to come by.This paper describes the approach taken by the DOE Retrieval, Treatment and Immobilization (RTI) Division Systems Engineering group to overcome the odds against success and implement Systems Engineering at the Hanford facility.
1.2.3 THE USE OF AN AUTOMATED SYSTEM ENGINEERING TOOL TO SUPPORT THE RISK MANAGEMENT PROCESS
Authors: Sadler Gerald G. , Baker Loyd 
Published: November 2014

AbstractA technical risk management system (TRMS) has been developed for the Fluids and Combustion Facility project which is a facility designed to support microgravity combustion and fluids experimentation aboard the International Space Station Alpha (ISSA). The TRMS incorporates Vitech Corporation's system engineering tool set, CORE, to capture and manage the evolving system design and risk identification, assessment, and abatement activities.
3.2.4 A PROCESS DRIVEN APPROACH TO INTEGRATED ENVIRONMENTS
Authors: Malcolm Nadine E. , McKennon Jane 
Published: November 2014

AbstractA process driven approach allows construction of integrated concurrent engineering tool environments based on the tool requirements of the tasks to be performed on a program. Tool capabilities can be matched to task requirements and the semantics of tool to tool bridges can be derived from process semantics. Finally, the process can be tuned to take optimal advantage of the integration capabilities of the tools. Two examples show how very different bridges are needed between the same two tools in the context of two different processes.
4.2.1 Tailoring the Military Systems Engineering Methodology for the Commercial Market: A Case Study of the Westinghouse StreetLINK SYSTEM
Authors: Holub Brian L. , Phillips Paul A. 
Published: November 2014

AbstractMilitary design methodologies produce systems that meet requirements, work reliably, and are maintainable. These military engineering and management practices have applicability to commercial markets for ensuring system quality, but cost and schedule constraints require the commercial developer to tailor them. Westinghouse Electronic Systems is an example of a defense contractor moving into the commercial marketplace. Their StreetLINK police mobile computing system is a new law enforcement data communications software tool. To develop StreetLINK, Westinghouse applied its knowledge of military systems engineering practices to the evolution of a commercial product. This paper describes the StreetLINK design process, covering mission requirements and functional analysis, requirements allocation and documentation, design synthesis and production, design reviews and meetings, product testing, and lessons learned. This experience provided insight into the differences and similarities between the established military engineering process and the newly explored commercial development process. For Westinghouse, this project developed a new commercial systems engineering paradigm.
2.3.1 Risk Management on the Advanced Tomahawk Weapon Control System: A Practical Application of Risk Management in Today's Defense Environment
Authors: Ford William C. 
Published: November 2014

AbstractRisk management is formally recognized by the government's acquisition system as providing value added to major defense programs. Actually implementing such a process, however, must be done within both programmatic and cultural constraints. This paper will examine the risk management process used on the ATWCS program, its evolution, and some of the practical considerations that have affected its implementation and continued functioning.
3.3.1 Systems Engineering Process Standardization: A Road Map for Concurrent Engineering
Authors: Wade James 
Published: November 2014

AbstractIntegrated product development (IPD) and concurrent engineering (CE) have been utilized by numerous companies to quickly and efficiently develop products. IPD makes use of analysis and product teams to address specific aspects of a product's design. Each team is allocated a portion of the overall budget, and in return is completely responsible for that aspect of the product, including cost, schedule, staffing, and product deliveries. However, simply forming and empowering a team will not necessarily produce quick and efficient product development. A “road map”, established top‐down from management, and worked bottom‐up by the teams is required to provide coordination during the design and development of the product. This “road map” is contained in the results of a NASA‐wide activity to establish common processes, products, and terminology in the management of technical programs and projects.
4.1.2 CULTURAL CHANGES AND LESSONS LEARNED IN SYSTEMS ENGINEERING AT THE SPACE AND MISSILE SYSTEMS CENTER (SMC)
Authors: Rountree Richard C. 
Published: November 2014

AbstractSubstantial changes in the acquisition and associated systems engineering cultures have occurred in recent years at the Space and Missile System Center (SMC) and The Aerospace Corporation in El Segundo, California. Sources of these changes have mainly derived out of directives from the Department of Defense (DoD) and Air Force Materiel Command (AFMC). These changes and directives have rejuvenated practice of a structured and disciplined systems engineering approach and introduced enhanced program management practices. Such practices have evolved from a blend of cultures associated with MIL‐STD‐499b (Draft), MIL‐HDBK‐499‐3 (Draft), Integrated Product Development (IPD), and Integrated Weapon System Management (IWSM). The 499b “Engine” and IPD guidance were implemented to various stages on several SMC programs. Emphasis was on conducting System Requirements Analysis (SRA), ensuring compatibility between requirements and tasking, and working in system acquisition teams according to IPD philosophy. Lessons learned from these early years of adopting to cultural changes represent mainly favorable results; i.e., cultural changes in business (government, industry) have proven to be efficient, systems engineering methodologies applied early provide program dividends. However, program “stove piping” (i.e., inward looking IPD team) is a dominant consideration and must be reckoned with.
2.2.2 Lessons Learned from Benchmarking and Planned Process Improvements
Authors: Fisher Gerard H. , Dobry Michael , Fisher Jack , Friedenthal Sanford 
Published: November 2014

AbstractThe NCOSE Benchmarking Working Group conducted a nationwide blind benchmarking of systems engineering processes and presented the results at the 1994 Symposium. Developing a comprehensive survey is far more difficult than one would expect. In the spirit of continuous improvement, the Benchmarking Working Group asked all 40 participants in the original survey to help us improve the process. This effort is sponsored by the Benchmarking Working Group to assist NCOSE members in future benchmarking efforts.
6.2.3 Industrial Collaboration Systems Engineering Capability Maturity Model Description and Overview of Hughes Pilot Appraisal
Authors: Cusick Kerinia , Minnich Ilene 
Published: November 2014

ABSTRACTThis paper describes the architecture and characteristics of the Industrial Collaboration Systems Engineering Capability Maturity Model (IC SE‐CMM), and the application of the model to an organization in a pilot appraisal performed at Hughes Aircraft Company. The appraisal methodology is discussed both in general terms and the Hughes specific application. Findings from the appraisal are reviewed in general terms, as well as the lessons that were learned from performing the appraisal.
DEVELOPING A SINGLE PERFORMANCE INDICATOR FROM HIERARCHICAL METRICS
Authors: Jones James H. 
Published: November 2014

AbstractA contemporary System Engineering task is development of process performance metrics. Executive management desires a single performance indicator that combines subsidiary metrics into a meaningful summary representation of organization health with respect to its mission. A purely mathematical approach can produce such an indicator, but when constituent metrics also contain subsidiary metrics, a multiple stage method is required. Because not all metric result customers are fully competent to audit the result, this paper sets forth a generally understandable method that “presells” the output to all involved parties through their approval of each model base before alternatives performance data are entered. The eminent decision support capability inherent in this method suits it for complex tradeoff analyses and System Engineering Maturity Modeling.
CONDUCTING A SYSTEMS ENGINEERING PROCESS ASSESSMENT
Authors: Mackey William 
Published: November 2014

AbstractOne way to improve the practice of systems engineering is to baseline the best practices and assess organizations against the baseline. Computer Sciences Corporation (CSC) is one of the nation's leaders in both developing baseline models and conducting assessments. During March through June 1994, the CSC Central Engineering Board (CEB) initiated the first systems engineering process self assessment (SEPA) using the National Council on Systems Engineering (NCOSE) Capability Assessment Working Group (CAWG) Systems Engineering Capability Assessment Model (SECAM). This paper summarizes those SEPA activities.
3.4.2 An Early Start for Integrated Spiral Development
Authors: Terry William S. 
Published: November 2014

AbstractThe application of integrated system/product development approaches and the use of spiral development models is becoming more prevalent in practice today. However, generally these methods are applied to programs as the program is starting development. Loral Federal Systems‐Owego (LFS‐O) recently used the concept of Integrated System Development/Integrated Product Development (ISD/IPD) along with a spiral development approach starting in initial idea exploration and through the proposal phase of a major new program. This experience is described along with a summary of lessons learned from early in the development.
4.4.3 Development of an Approach to Alternative System Solution Capture and Evaluation
Authors: Baxter Michael J. 
Published: November 2014

AbstractThis document details the research and development effort entitled “Development of an Approach to Alternative System Solution Capture and Evaluation.” This research discribes the development of a computer aided systems engineering capability for integrated development and evaluation of alternative system concepts. The described elements of this procedure include the following: development and capture of system evaluation measures, requirements and performance models; utility function development; architectural element modeling, system alternative assembly; and alternative system evaluation and selection. The document consists of a number of sections which address the problem, the value of solving the problem, the approach, a background survey, a developmental prototype, the preliminary results, and process and software illustration figures.
4.5.3 ETHICS IN SYSTEMS ENGINEERING
Authors: Kasser Joe 
Published: November 2014

AbstractSystems are growing larger and larger and are taking over the running of many facets of modern society, such as Automated Traffic Handling Systems, Intelligent Vehicle Highway Systems, and Air Traffic Control Systems. A failure in one of these systems can cause economic damage, as well as loss of life. An engineer who discovers such a problem or even the probability of such a problem faces an ethical dilemma concerning what to about the discovery. This paper discusses personal and corporate ethics in systems engineering; the ethical dilemma faced by a systems engineer and the possible consequences of abiding by one's principles.
4.5.4 Essential Systems Engineering: A Lifecycle Process
Authors: Azzolini John 
Published: November 2014

AbstractA systems engineering process is presented which supports the project lifecycle with improved rigor. The incorporation of specific structure and discipline results in a process which is requirements based, with added value in the planning, execution and reporting of design, implementation, integration, verification, and validation activities.The concept of the validation basis is introduced and discussed. It is a key concept in the development of this process.
5.5.1 Applying Systems Tools & Methods to the Development of a Quality Program Implementing Quality Standards such as ISO 9000
Authors: Bodi Robert F. 
Published: November 2014

AbstractTools and methods developed for the field of systems engineering can be used to provide effective support to a wide‐ranging set of manufacturing needs. One area that shows great potential application for these systems tools and methods is the development of a quality system to meet the requirements of quality standards such as ISO 9000. This paper briefly explores this potential application.
7.5.3 “If I Could Do That, Then I Could…” System Engineering in a Research and Development Environment ‐ As Illustrated by the Evolution of the Space Shuttle Tiles
Authors: Forsberg Kevin 
Published: November 2014

AbstractResearchers and Project Managers in a research and development environment often resist the notion that a structured process such as System Engineering can be applied to their environment. While it is impossible to invent to a schedule, it is certainly possible and necessary to use good engineering practices in the research and development process. System Engineering is one of these necessary engineering disciplines.To illustrate the use of System Engineering in its applications in R&D, this paper will follow the development of a new ceramic material from its origin in the research laboratories in the early 1960s through its application to the Space Shuttle thermal protection studies in the late 1960s and its production scale‐up as the Space Shuttle tile material in the 1970s, to its ultimate potential in the current exploratory studies as a matrix for repair of human bone in the 1990s.The author was closely associated with the material throughout much of its history. In the mid‐ to late 1960s the author was deputy director of the Materials and Structures Laboratory (where the material was invented by Robert Beasley) in the Lockheed Palo Alto, California, Research Facility. The author later became program manager of the Space Shuttle Tile Program.
Designing Budget‐Tolerant Systems
Authors: Denzler David W. R. , Kasser Joe 
Published: November 2014

AbstractIn today's systems engineering environment, budgets are decreasing while needs are remaining constant or even increasing. This paper discusses the concept of designing systems so that in the event of budget reductions, there is no need to cancel the project and restart the development of a system with lower capability. Instead, the least‐important requirements are easily eliminated.