bluuebunny/crossref_metadata_2025_split huggingface dataset:
2.4.3 A COHERENT ENGINEERING PROCESS FOR COTS ACQUISITION AND INTEGRATION
Authors: Nolte Jerry , TASC David Newbern 
Published: November 2014

AbstractOne of the major problems facing the federal agencies today is how to rapidly acquire COTS‐based systems within the contractual framework of the Defense Federal Acquisition Regulations (DFAR). TASC has developed a preliminary description of a process to solve this problem. We have identified modifications to the standard acquisition process which are needed to meet the contracting and legal requirements embodied in the DFAR while effectively attaining the desired technical benefits from building a system around commercially available software packages. The process emphasizes a small team approach to coordinate technical requirements, program schedule and budget constraints, and the acquisition process.
2.4.4 A Picture's Worth: Use of Models to Facilitate Knowledge Transfer During the System Life Cycle
Authors: Schuster Cecilia H. 
Published: November 2014

ABSTRACTIncreasingly practitioners of Systems Engineering are recognizing the challenges of creating consensus understanding on a program. For years, members of NCOSE have been clamoring for a more robust and unambiguous way of expressing their requirements and subsequent designs. Model‐based systems engineering is a reality whose time has come. This paper points out ways in which these techniques are superior in the realm of knowledge transfer. In light of the symposium theme Systems Engineering in the Global Market Place, these concepts suggest that models are the way to cross not only the boundaries of life‐cycle phases, but also the linguistic boundaries of the global community.
3.5.3 OBJECT‐ORIENTED SYSTEMS ENGINEERING
Authors: Bharathan K. , Poe Georgia L. , Bahill A. Terry 
Published: November 2014

AbstractObject‐Oriented methodology has developed to the point where it has the potential for being a powerful tool in the arsenal of the systems engineer. This paper suggests that such assimilation will require modifications in the method to make it generalizable outside the software design environment. This paper uses the lessons learned from (i) a text‐book example and (ii) a systems engineering project where the object‐oriented method is being applied to explore the scope and possibility of such assimilation.
6.4.2 FAILURE MANAGEMENT AND THE DESIGN OF COMPLEX SYSTEMS
Authors: Fisher Jack 
Published: November 2014

AbstractWhen we undertake to design a complex system, consideration must be given to how the system and its components might fail and how these potential failures may be circumvented or avoided. Current aerospace design practice for the consideration of failure is described and its weaknesses recognized. It is proposed that failure design considerations become a featured element in the systems engineering process and that a centralized approach under the banner of risk management would provide a number of significant advantages.
7.4.1 A NEW LOOK AT THE SYSTEM ENGINEERING PROCESS: A DETAILED ALGORITHM
Authors: Adamsen Paul B. 
Published: November 2014

AbstractThis paper describes a system engineering process or algorithm upon which a database for requirements, design, and decision traceability can be structured. Once in place, this database provides a powerful tool for performing change impact analyses, cycle‐time reduction analyses, cost reduction analyses, anomaly analyses, risk assessment, etc. It also assists in the development of meaningful metrics that give real technical, cost, and schedule performance visibility to program management. This in turn provides a tool for controlling the system development in terms of identifying risk areas and determining where resources should be focused to mitigate them. In short, such a database describing the system provides understanding of the system. A system understood is cost‐manageable. A system understood is schedule‐manageable. A system understood is technical‐performance‐manageable. Risk understood is manageable risk.
Systems Process for Public Policy Application
Authors: Cutler William H. 
Published: November 2014

ABSTRACTThe Systems Process, emphasizing the Functional View, is an effective organizing principle for creation of public policy actions. It has two features that counter the adversarial mindset typical of politics:
All stakeholders are included as members of a collaborative team.
It is a structured, disciplined process that addresses the inherent complexity of the problem.Complex systems are encountered everywhere in public policy. The Systems Process with its fundamentally collaborative nature is superior, perhaps indispensable, for resolving controversy and organizing an effective response. A 12‐step process framework is described, which is applied throughout the life cycle of an issue as it moves through Initiating, Planning, and Operational stages. Experience showing the benefit of this process is cited.
Systems Engineering and the Architectural Design of Buildings
Authors: Langston Dale Glyn 
Published: November 2014

ABSTRACTThis paper presents a case study of the architectural design of a custom building. In this case study, a church is investing in the conceptual design phase of a new facility. This paper summarizes the activities performed to develop the conceptual drawing of the new building and the deficiencies associated with that approach. A systems engineering approach is proposed in this paper that will lead to comparable drawings at a reduced costs.
Object levels and categories in O4S™ (Objects For Systems) for engineering of dependable systems
Authors: Ögren Ingmar 
Published: November 2014

ABSTRACTThe general O4S™ object concept is introduced with objects having offered/required interfaces and internal behavior.To support efficient system engineering objects are identified on Project, Configuration Item and Ordinary level.Object categories are introduced to model how objects of categories Operator, Software and Hardware cooperate to complete Missions.As a formal notation, the design language Odel, based on the programming language Ada95 is introduced. It is also shown how Odel gives a basis to use the traditional techniques of FTA and FMEA to analyze system dependability.
Driving Test and Verification From SLATE
Authors: Sampson Mark E. 
Published: November 2014

ABSTRACTTest and verification always seem to end up on the critical path as we come down to the finish line on our product launch efforts. These, usually separate, test organizations often have more people working test then worked product design. This paper suggests an “integrated” approach to pulling test into the systems engineering requirements management environment and shows how SLATE can be used to actually drive system test sets and monitor and report on results–after all, test exists to verify and document that the product meets the requirements.
Challenges in Designing Open Systems
Authors: Dargan P. A. , Hermes Michael A. 
Published: November 2014

ABSTRACTOpen systems offer a building block approach to development that follows sound software engineering principles: well‐defined interfaces, information hiding, weak coupling, and layers of abstraction. Open system standards define the basic system building blocks, providing a foundation for reuse, interoperability, and evolution.But there are new challenges to address with this approach: where do standards belong in an architecture? Which standards are the right ones to use? Are there commercial products that implement the standards? This paper provides some insights based on experiences in developing a standards‐based architecture for migrating a large, complex legacy system to an open system.
How to Properly Specify and Control Essential Project Data
Authors: Chevalier Jean , Marshall Richard M. 
Published: November 2014

ABSTRACTThe relationships between need, function, requirements, and verification define a systems engineering process. The documents containing this information define the product which the project will produce. Drawing up requirements compatible with user needs, the project's mission and the available technologies is a major task for the project team and subcontractors. Similarly, exercising control over changes to the documentation and appraising their consequences is of constant concern to project managers, and is another keystone of the systems engineering approach. This paper presents the result of using the DOORS tool to apply rigorous systems engineering discipline to a trial project at the French Space Agency.
Prophet™ ‐ The Engine for Integrated Risk Management
Authors: Huff Deborah S. 
Published: November 2014

ABSTRACTHughes has developed a powerful risk management toolset, named Prophet™, which has proven highly successful in managing several programs, and is now being deployed throughout Hughes. This paper describes Prophet™ features, the processes it supports, and the concepts behind them. Features include user‐friendly input screens, roll‐up risk factors, automated risk reduction charts, expected cost impact analysis, assessment history and rationale tracking, process productivity aides, tailorability features to suit a broad assortment of programs, integration with master planning and scheduling, tracking of technical performance measures, risk metrics for technical trade studies, and strategic technology maturation planning.
Implementing the Systems Engineering Process for Tool Selection
Authors: Christopher Janet 
Published: November 2014

ABSTRACTThe Lockheed Martin Systems Engineering Process is utilized by the Engineering Process Improvement (EPI) Program for selection of CAE tools for automating engineering tasks. Expanding the focus of Systems Engineering to include engineering process and practices provides a framework for defining a systematic approach to selecting and implementing processes and practices, i.e., tool selection and usage. The Systems Engineering approach for selecting EPI tools at Lockheed Martin Corporation is described, including the tasks associated with each step. The steps described follow the elemental tasks of planning, analysis, candidate selection, validation, evaluating alternatives and managing risk, and selecting the solution.
BACK TO BASICS AGAIN – A SCIENTIFIC DEFINITION OF SYSTEMS ENGINEERING
Authors: Mar Brian W. 
Published: November 2014

ABSTRACTThe major confusion with the understanding of systems engineering and improving its scientific basis is the failure to define the system of interest. Given a clear definition of the system of interest, engineered functions of that system can be identified, and applications of systems engineering concepts to those activities can be examined.A systems framework is suggested to classify basic engineering and systems engineering activities. This framework allows a better definition and search for scientific foundations of systems engineering.
Business Strategy Implementation with Systems Engineering
Authors: Oliver David W. 
Published: November 2014

ABSTRACTSuccess in the marketplace requires a business strategy implemented with engineered product or service. The product or service must provide users, operators and owners with what they want and value with more convenience and better price than offered by competitors. Management makes the business strategy and resource allocation decisions. Systems engineering defines the product and services in accord with these decisions.It is critical that needed information pass across the management/systems engineering interface without ambiguity. This often requires a translation of information into the form understood by and useful to the recipients.This paper analyzes the basic abstractions used by organizations on both sides of the interface. It establishes the basic abstractions that are common to both business strategy development and systems engineering. This set of abstractions define the information which must be communicated between the business development experts and the systems experts who may be organized together in a single team or assigned to separate organizations. The techniques for engineering systems with models, usually applied to products and services, are applied here to the interface between business strategy and systems engineering
Integrated Modeling for Launch System Architecture Optimization
Authors: Hickman Robert A. 
Published: November 2014

ABSTRACTIn a world of increasing competition and declining government space budgets, the emphasis in new launch system design has shifted from performance optimization to cost reduction. Architects making complex launch system design decisions are handicapped by the unavailability of analytical tools that provide an integrated life cycle cost analysis that quantifies the impact of design decisions. Vehicle performance, operational efficiency, reliability and ground system design all have a major effect on cost. This paper focuses on a research effort to integrate 6 separate models developed at The Aerospace Corporation to provide an integrated launch system assessment capability. The impact on the system architecting process will be discussed as well as the ability to identify and prioritize necessary design enhancements or new technologies.
A Systems Vision for INCOSE
Authors: Evans Richard , Park Sooyong 
Published: November 2014

ABSTRACTINCOSE has become great by dedicated and inspired leadership. It has also become great because it holds the promise to be a means to address a great worldwide challenge:systems. The call for INCOSE in addressing that challenge and truly fulfilling that promise is to lift and enlarge our vision to meet our responsibility for systems, not just something called systems engineering, or for systems engineers. Two options toward an elevated systems vision are presented: (1), move directly to a “systems” level and be the International Council on Systems (INCOS), or (2), take a two‐step approach, transitioning initially to an intermediate‐level vision as the International Council on the Engineering of Systems (INCOES).The intent of this paper is not at all to make a final case for an immediate change in INCOSE, rather it is to initiate further consideration of the issues and ideas offered, with a goal of helping, by citing these perspectives, to assure a great INCOSE [INCOS] now and in the future.
Development and Integration of Engineering Processes at Oerlikon Aerospace
Authors: Laporte Claude Y. , Papiccio Nicola R. 
Published: November 2014

ABSTRACTIn order to reduce cycle time, increase customer satisfaction and lower costs, Oerlikon Aerospace has initiated, in 1992, a project to define and implement software and systems engineering processes. The initiative started by performing a formal assessment of current software engineering practices. An action plan was developed and multi‐functional working groups were tasked to define and facilitate the implementation of software processes. A second initiative was started, in 1995, with the objective of defining and implementing a systems engineering process, and integrating to the systems engineering process the software engineering process already in use.
Systems Engineering and Management of Multinational Cooperative Development Programs
Authors: Roe Charles L. 
Published: November 2014

ABSTRACTInternational research and development programs present unique challenges in relation to business mobilization and in how organizations must deal with outside technology, financing, program planning, joint program management, and engineering issues. The systems engineer must address technical issues set against multinational parochial interests, while the program manager holds the industrial team together and works with a sponsor that is often a consortium of nations.
MECHANISMS FOR INTERTEAM INTEGRATION: FINDINGS FROM FIVE CASE STUDIES
Authors: Browning Tyson R. 
Published: November 2014

ABSTRACTMany product development programs consist of multiple integrated product teams (IPTs) and functional groups. Interteam information dependencies greatly affect program success. Program integration has thus become an issue of increasing interest. This paper summarizes findings from five case studies of integrative mechanisms (IMs) in complex system product development projects at Chrysler, General Electric Aircraft Engines, McDonnell Douglas, Sundstrand, and Texas Instruments. Two types of IMs are investigated in this paper: (1) Systems engineering and interface optimization and (2) Improved information and communication technologies. As the appropriateness of a given IM varies as a function of many parameters—such as program stage, size, complexity, risk, etc.—the goal of this research was not to formulate a universal template for IM application. Rather, it is hoped that the lessons learned by these five programs will help others determine the appropriateness of particular IMs in their situations. Also, the continued development of an IM categorization scheme will hopefully prove useful to those developing an integration “tool kit.”
A Simplified and Evolutionary Hypermediacy Model For Project Management
Authors: Worden Gregory 
Published: November 2014

ABSTRACTThe electronic revolution held the promise of fast and efficient communications, seamlessly integrating different platforms, regardless of a user's location, in an easy to use and inexpensive package. However, for most organizations the electronic workplace has been expensive, inflexible, difficult to learn, and incapable of working with other systems. Yet the rapid expansion of the Internet and its hypermedia interface has given project management a new tool. Hypermedia, multimedia, and associated technologies, collectively termed hypermediacy, provide an efficient, simple, flexible, and powerful method for maintaining and distributing project information. This paper presents a project information system, built on the Internet paradigm of low cost, distributed networks, using existing desktop hardware and software. Starting with a simple implementation, project management can quickly and inexpensively realize information processing requirements without expensive procurements or learning overhead. The base model is then expanded incrementally over time as project needs evolve.
An Improved Set of Products for Measuring Systems Engineering
Authors: Widmann E. R. 
Published: November 2014

AbstractThis paper provides information on the INCOSE Measurement Technical Committee and its three working groups. The charter and goals are presented along with objectives for development and support of measurement products. Significant milestone events for both products and product support services are provided – the only products to receive approval, or interim approval, of the INCOSE Technical Board were developed within the Measurement Technical Committee. A brief description is provided of each of the measurement products developed to date. A synopsis of the past year's activities is provided along with planned future activities. An integrated approach to development of measurement products is being pursued to permit more effective measurement and improvement of systems engineering activities. The products developed by the Measurement Technical Committee are available to become an integral part of the strategic planning activities of both industry and government.
A Preliminary Description of the EIA Systems Engineering Capability Model
Authors: Widmann E. R. 
Published: November 2014

ABSTRACTTwo systems engineering capability models have gained a great deal of attention: the INCOSE SECAM and the EPIC SE‐CMM. This paper provides a preliminary description of the results to date of merging the two models and application methods into a single model and assessment method under the auspices of the Electronic Industries Association (EIA). The EIA Working Group, which is responsible for accomplishing the merger, has representation from the EIA, INCOSE, and EPIC. The INCOSE representation is provided by the INCOSE Measurement Technical Committee. As such, the “merged” products may be regarded as part of the set of measurement products that the INCOSE Measurement Technical Committee is developing, both internally within INCOSE and jointly with external organizations, to measure and improve systems engineering activities. The paper provides a synopsis of the current versions of both models in order to assist in understanding the merging effort and provide a background to the resulting merged model, designated the EIA Systems Engineering Capability Model (SECM).
INCOSE Tools Database Working Group Report
Authors: Case Randy , Findley Beth , McMullen Bill , Sampson Mark 
Published: November 2014

ABSTRACTThe Tools Database Working Group (TDWG) is delivering a third release of the Systems Engineering Tools Database at the 1997 INCOSE Symposium. An update of the Requirements Management Tools, an update of the Systems Architecting Tools and a list (by both vendor and tool name) of general tools (including the requirement and architecting tools) make up this third installment. The information contained within the database comes directly and unedited from the tool suppliers. It is our wish that this information will save INCOSE members (those looking for information and those providing it) time as well as provide a common framework of reference for these important tools for Systems Engineers.
1.1.3 Systems Engineering in the Small
Authors: Sloan Crystal D. , McCumber William H. 
Published: November 2014

ABSTRACTThis paper illustrates how systems engineering is conducted at the lower end of the business, where the customer usually will not pay for the design of a system unless the costs are integrated into the price of the delivered product. Many low‐end customers do not have a clear concept of what they want a practitioner to provide. This paper presents the practitioner's view of engineering in the small, and demonstrates a strategy for finding out what the customer really wants.
5.1.3 Converting Your Systems Engineering Organization To ISO 9001 Compliance
Authors: Kasser Joseph E. , Williams Victoria R. 
Published: November 2014

ABSTRACTQuality control is evolving from only being present during final inspection, into becoming an integral part of the systems engineering process. This evolution is being helped by the International Organization of Standards (ISO) 9000 series of standards that provides a checklist for documenting processes and assessing their performance. The standards do not apply to systems engineering at this time. They are however taking the place of similar Department of Defense (DoD) standards, so there is an excellent probability that they or an equivalent standard will apply to systems engineering in the future. This paper describes one proposed way to transform an organization toward compliance with the ISO 9001 Standard, and make an organization's systems engineering process more cost effective.
1.2.1 Self‐Directed Teams for Systems Engineering
Authors: Brezinski Lawrence J. 
Published: November 2014

ABSTRACTA systems engineering functional group within a matrix organization provides technical skills to system development projects. Effective systems engineering requires a balanced emphasis on people, technology, and process activities. This balance can be achieved through the use of self‐directed teams in place of the traditional hierarchical organization. Using defined team tasks, clear interfaces, and a metrics program, self‐directed systems engineering teams were piloted. Results were measured in project performance, team performance, and involvement by systems engineers in developing and improving the technology skills and processes necessary for future company growth.