bluuebunny/crossref_metadata_2025_split huggingface dataset:
3 An Implementation of the Analytic Hierarchy Process (AHP) on a Large Scale Integrated Launch Vehicle Avionics Systems Engineering Architecture Trade Study
Authors: Wagner James F. 
Published: November 2014

ABSTRACTThe objective of a large scale integrated avionics architecture trade study is to consistently and fairly choose among alternative architectures. A structured process is required to accomplish this objective. The Analytic Hierarchy Process (AHP) provides a framework, and was used to quantitatively choose among four potential alternative avionics complement architectures with respect to meeting avionics design objectives and mission needs. This paper focuses on an implementation of the AHP on a large scale integrated launch vehicle avionics systems engineering architecture trade study. Several key characteristics of the four alternative architectures are identified and form the evaluation criteria for the trade study. AHP was used to carefully evaluate the relative importance of the criteria, and aide in the comparative judgements and synthesis of the criteria priorities and the selection of the alternative. The alternative avionics solution selected is a modular, federated (pseudo distributed) architecture of subsystems which results in the most efficient overall launch vehicle management.
1 Managing the Rework Cycle not the Schedule ‐ A Project Management Paradigm for the Future?
Authors: Mawby Dave 
Published: November 2014

AbstractMany projects fail to deliver against their targets because conventional project management techniques are failing to cope with the project's dynamic environment, complex interactions and the multitude of ‘soft’ / people issues. If conventional techniques do not cope with the complicated factors that affect our larger projects, are there any better methods? This paper demonstrates that better management of the rework cycle and application of dynamic project modelling technology can provide a more robust means of controlling complex projects than many of those in common use today.Combining this insight with the capability of anticipating and managing complexity through dynamic project modelling offers tomorrow's project managers the ability to build more robust programme plans. Project managers will then be better able to cope with pressures present within the project's environment and to respond more effectively to change. This understanding of the rework cycle and application of dynamic project modelling offer a new and more powerful project management paradigm for the 21st century.
1 Concept Analysis: Modeling and Organization Transformation
Authors: Oliver David W. 
Published: November 2014

ABSTRACTThis paper models the concept analysis of a new freight locomotive product as an example of modern product development and organization evolution. It combines the producer business strategy with the purchasing railroad needs and the needs of the railroad customers, (Oliver 1997), (Gale 1994). Modeling techniques are shown for requirements elicitation. The results are tied to technical engineering effectiveness measures using analytical techniques and the less formal methods of TQM and Six Sigma, (Saaty 1983), (Harry 1994). As the example progresses there is an identification and presentation of critical engineering performance calculations and trade‐off to establish system level design tied directly to customer perceived value and quality and to business strategy.As the locomotive design changes emerge, concurrent changes to the business structure, organization and motivation factors also emerge. Modeling makes Concept Analysis rigorous and provides transformation to the notations of recipients.
Starting at the Finish Line
Authors: Armstrong James R. 
Published: November 2014

AbstractThe front end of the program is given a lot attention in the world of systems engineering. For instance, requirements writing is a favorite subject. The back end activities are usually included to the extent of making sure the requirements cover them appropriately. Otherwise, the post‐design activities are often left to be addressed in a just‐in‐time fashion.The most critical activity of this period, and indeed the program, has to be customer acceptance. Waiting until the time of acceptance to address the issues is high risk. Even the standards in use and development keep the user at arms length.There are many lessons learned that substantiate this as a high risk approach and provide better approaches. This paper takes a look at the current status and brings these lessons learned together to identify early tasks that should be included in programs to reduce the risk, schedule and cost of non‐acceptance by the customer.
Pictorial Representation of Communication Satellite Resource Allocation Using STK
Authors: Shamash Micah , Wells Tyler 
Published: November 2014

ABSTRACTOver the past decade the need for communication satellites has grown dramatically, with the main consumer no longer being strictly the government cost‐effectiveness has become a main issue. Designing a communication satellite that will be cost effective, as well as, efficient for a given user community is often a daunting task; it requires analyzing many different hardware configurations to determine which will most effectively service the user community. Using a database of typical users and analyzing hardware trade‐offs is often times a preferred method of solving these types of analytical problems. More times than not this labor intensive analysis is done by hand, but to get reliable, easily reproducible results a “tool” can be developed to automate the analysis.In looking at an analytical problem as extensive as communication satellite resource allocation, simple numerical data does not always provide for the best answer. This paper describes our experience using Satellite Tool Kit (STK) a COTS product to graphically display the results of our satellite resource allocation tool. This tool is currently being used to analyze hardware trade offs for the design of a communication satellite constellation.
Concept Mapping as a Communications Tool in Systems Engineering
Authors: McCartor Mary Morgan , Simpson Joseph J. 
Published: November 2014

AbstractIn any “deep learning” situation, and in communicating in particular, understanding will be enhanced by using techniques that more closely fit the nonlinear structure of our thinking processes. This idea is particularly relevant to systems engineering, which deals with so many interrelated concepts—concepts whose parts are often handled by separate organizations with different “languages” and foci, presenting additional barriers and confusions in understanding. In the figures in this paper, we have tried to show a variety of patterns that concept mapping can be cast in, for flexibility and interest. Our experience in Boeing is that such an approach simplifies, deepens, and clarifies communications, while providing the opportunity to find ways to develop more complete and better integrated concepts.
Developing and Teaching a System Architecting Process
Authors: Cabrera Orlando J. 
Published: November 2014

AbstractThis paper will present the definition and development of a System Architecting (SA) process as well as the SA class that was subsequently developed. Under the auspices of our Total Quality Management Program (TQM) and beginning in 1995, a group of senior System Engineers at Harris Government Communication System Division (GCSD) began meeting on a regular basis. The group's goals were to define SA and its application to GCSD, establish a processes for implementing architectural development and prepare an internal SA class. The group, named the System Architecting System Improvement Project or SA SIP, successfully accomplished its goals. In addition, the SIP contracted with the University of Southern California (USC) during the spring and summer of 1996. USC developed an intensive 48‐hour short course on System Architecting for Harris. The USC material was also used in the development of the internal class. The SIP developed class has been taught to System Engineers throughout the Electronic System Sector (ESS) of Harris since the summer of 1997.
A Fully Integrated Engineering Approach For Navy Theater Wide Theater Ballistic Missile Defense
Authors: Hyer Scott A. , Meshel David C. , Kovel Maxim I. 
Published: November 2014

AbstractA cornerstone of any successful system development is in its engineering approach and planning. A concisely defined process, complete with objectives and products identified at each stage is necessary to draw multiple organizations together in working toward a common goal. This paper identifies the major parts of the engineering approach being taken on the U.S. Navy Theater Wide (NTW) Theater Ballistic Missile Defense (TBMD) Program. Guided by the general guidelines prescribed by the EIA‐632 Interim Standard (dated 1994), the authors developed a Systems Engineering Management Plan (SEMP) which defines the organizational structure and teaming arrangements, task responsibilities, engineering process, products, and schedule events.
CMMI Assessments
Authors: Ahern Dennis M. , Dunaway Donna K. 
Published: November 2014

ABSTRACTThe CMMI Product Team has created a set of assessment requirements that are to be satisfied in any full, comprehensive assessment method for use with the CMMI models. The CMMI Assessment Requirements (CAR, v. 0.1) is an extension of prior work done at the SEI on a CMM®‐Based Appraisal Framework (CAF, v. 1.0). The CAR was written to comply with the emerging ISO/IEC 15504 standard, for wider applicability. The team has also created a comprehensive CMMI assessment method, called the Standard CMMI Assessment Method for Process Improvement (SCAMPI). This method is based on the SEI's CMM‐Based Appraisal for Internal Process Improvement (CBA IPI) and the SECM Appraisal Method (EIA/IS 731, Part 2). Pilot tests for CMMI products, using SCAMPI, are planned for 1999–2000.The CMMI Product Team will also provide guidance for tailoring the CAR to address the needs of an organization that wishes a less‐than‐full or partial assessment. Such partial assessments, e.g., initial assessment or quick‐look, would provide less rigor than SCAMPI, but would also require fewer resources.
A Systems Engineering Approach to Simulation Based Acquisition (SBA)
Authors: Huang Paul , Sleder Pradip Kar Al , Kato Hiroko 
Published: November 2014

ABSTRACTModernization of defense industry has come a long way technologically. The complexity and sheer magnitude of modern weapon systems represents a major design challenge. The involved life‐cycle support of those systems is very complicated. All of those added together will make the cost of any new weapon system prohibitively high. Facing this new challenge, United States Department of Defense (U.S. DoD) proposes an initiative, namely the Simulation Based Acquisition (SBA), to reduce the acquisition cycle. This initiative has significantly impacted the manner in which new weapon systems are concepted, designed, integrated, tested, produced, and supported throughout their life cycles. This paper presents a systematic approach to this DoD initiative. It leverages past experience in research and development in system integration related technology. Combining with lessons learned from executing modern weapon systems development, this process has the potential to provide the industry with a standard SBA process.
Open Systems and the Systems Engineering Process
Authors: Hanratty J. Michael , Lightsey Robert H. , Larson Arvid G. 
Published: November 2014

AbstractThe open system approach is both a technical approach to systems engineering and a preferred business strategy that is becoming widely applied by commercial manufacturers of large complex systems. It has the attention of DoD management who have mandated its use by DoD systems developers. Why? Because without such a change in system development practice, DoD risks being unable to maintain continued superior combat capability affordably!Today, legacy weapons systems continue to be developed with their own, often unique and frequently closed, infrastructures, making upgrading or modifying them over their expected lifetimes (20 to 40 years) both problematic and expensive. Also, reduced procurement budgets and increased dominance of commercial technology cause acquisition managers to increasingly rely on commercial markets for affordable product development and support. So, as DoD's role shifts from being a technology producer to being a technology consumer, it relies more on commercial products whose design is not controlled by DoD and whose lifetimes are much shorter and more volatile than the weapons systems they support (e.g., years vs. decades). As a result, acquisition managers risk relying on unique products provided by a single supplier at high non‐competitive prices and with little opportunity for technology insertion by other suppliers.This paper discusses the need for a rigorous systems engineering process which incorporates open systems concepts and principles — where resulting system designs more readily accommodate changing technology to achieve cost, schedule, and performance benefits by promoting multiple sources of supply and technology insertion.
1 Systems Engineering ‐ a pragmatic approach
Authors: Fletcher M J 
Published: November 2014

ABSTRACTThis paper provides a personal view, built from practical experience, that considers and contrasts the approaches of developing a System from a “top down” decomposition of requirements with the historical methods of designing from the “bottom up”. The former follows the purist approach assuming an all‐new system development. The latter looks at the “traditional” approach of evolving systems out of a number of almost independently developed equipments or sub‐systems.The paper proposes a pragmatic approach that retains both these techniques in Systems Engineering. In particular, this approach is applied to the reuse of Components, Equipments or SubSystems in the design of a new system.
Establish A Baseline Assessment to Manage Risks Using Risk Matrix
Authors: Willhite Anne Marie , Norton Darcy R. 
Published: November 2014

AbstractThis document describes a baseline risk assessment process and tool that was developed for the Air Force Electronic Systems Center (ESC) and based on Risk Matrix—a structured way to identify, prioritize, evaluate, and manage the impact of key risks on acquisition and development programs. The basic principles can be used by anyone who needs to manage risks.
A Design Attribute Methodology for the Identification and Ranking of Functional Integration Risk
Authors: Vick Jeffery D. 
Published: November 2014

AbstractIt is well known that applying validation methods during product development will reduce product functionality problems. Generally, the earlier an error is found, the less it costs to resolve it. The traditional amount of validation analysis applied during the detailed design of derivative commercial airplanes is being challenged due to market pressures to cut costs. Without sufficient validation, a significant number of functional integration problems can remain undetected until discovered late in development by flight tests or during airline operations – which translates into cost overruns. A tradeoff exists between making planned investments in validation analysis and incurring unplanned costs later. Having the ability to identify where in the design to focus design validation analyses is essential for assuring a functionally integrated product and minimizing total development costs. A design‐attribute risk assessment methodology based upon search theory, technical risk analysis concepts, and systems heuristics was developed and applied for this purpose.
Application of Systems Engineering to U.S. Department of Energy Privatization Project Selection at the Hanford Nuclear Reservation
Authors: Layman John S. 
Published: November 2014

AbstractThe privatization efforts at the U.S. Department of Energy's Hanford Nuclear Reservation have been very successful primarily due to a disciplined process for project selection and execution.Early in the development of Privatization at Hanford, the Department of Energy determined that a disciplined alternatives generation and analysis (AGA) process would furnish the candidate projects with the best probability for success. Many factors had to be considered in the selection of projects. Westinghouse Hanford Company was assigned to develop this process and facilitate the selection of the first round of candidate privatization projects.Team members for the AGA process were assembled from all concerned organizations and skill groups. Among the selection criteria were legal, financial and technical considerations which had to be weighed.
SYSTEMS ENGINEERING REALISATION
Authors: Grady Jeffrey O. , Jurewicz Ben R. , Long James E. , Mar Brian W. , Morais Bernard G. 
Published: November 2014

AbstractThe systems engineering process as described in many books, however many minor variations may exist, is perceived by most members of INCOSE as an obvious way to pursue the development of solutions to complex problems. At the same time, most members are aware and concerned that few companies practice its precepts with total success. This paper makes the claim that sound system engineering knowledge exists but is not often well applied in practice as a premise of a study to seek out the reasons for this schism with the goal being an eventual closure of it. This paper, therefore, is an introduction to an extended activity planned by the authors.
Using a Common Information Model as a Methodological Basis for a Tool‐supported Requirements Management Process
Authors: John Gisela , Hoffmann Matthias , Weber Matthias , Nagel Martin , Thomas Carsten 
Published: November 2014

AbstractThe growing complexity of systems and the continuing pressure on reductions in development time and cost can only be tackled if an effective and tool‐supported requirement management process is established. In our view, requirements management is not just part of requirements engineering. Instead, in principle, it is part of all phases of the entire system life‐cycle, ranging from market analysis and top‐level customer requirements to system maintenance, final shutdown, and removal. In this paper, we report on some methodological experiences gained from introducing a tool‐supported requirements management process at DaimlerChrysler Aerospace Airbus. First, we will describe our view of the main process steps in requirements management and the typical roles that people play in a tool‐supported requirements management process. Then, we will introduce the basic parts of a common requirements management information model and discuss how a general common information model helps to support the main process steps in requirements management.
A Framework for Improving the Requirements Engineering Process Effectiveness
Authors: Williams Ddembe , Kennedy Michael 
Published: November 2014

AbstractThis paper presents “research in progress” for a proposed process simulation‐modelling framework for improving the requirements engineering process effectiveness. It presents a framework based on system dynamics model for measuring the RE process performance in terms of quality, cost resources and schedule adherence. The paper describes the factors included in an initial requirements engineering process model and proposes further work based on the main research issues derived from the model. In developing such a model, the research fills an important gap in the requirements engineering process literature and has the potential to provide practising requirements managers with a tool to support policy development and decision‐making in improving process effectiveness. The strength of the proposed model and its advantages over the existing models is its dynamic nature, and its capability to incorporate both hard and soft factors and the understanding gained from explanatory insights from the feedback structures. Preliminary results based on a pilot case study suggest that the process model‐based tool makes a useful contribution for understanding the RE process. Such a tool may be useful in attaining process effectiveness based on a learning and training environment supported by the system dynamics tools.
Case Study on the Use of Scaling Methods for Prioritising Requirements
Authors: Moisiadis Frank 
Published: November 2014

AbstractThere are often not enough resources available to build systems that can do everything the customer wants. Many times it is necessary to prioritise requirements in the face of limited resources. Budget constraints, delivery deadlines, competitor pressure, and gaining or maintaining one's market‐share are all factors that often impact on the delivery schedule for a system. Consequently, the most important requirements need to be found and implemented first. In trying to determine what requirements are most important, many methods are used in practice. All of these methods involve some kind of scaling or rating system. This paper looks into the various scaling systems that are used. A case‐study has been conducted to evaluate three different rating scales on a set of requirements for a library and for a set of car attributes. The findings are quite interesting in that they reveal weaknesses in using particular rating scales. Suggestions are made as to which rating scale to use to prioritise requirements.
ESSI Project ODE: Implementation of an object oriented software development environment
Authors: Ruiz Fernando 
Published: November 2014

AbstractThis paper presents the ODE Project developed by Casbega, a Spanish soft drink bottler and distributor (Coca‐Cola, Fanta, etc.), with the aim of implementing a new Object Oriented software development environment.ODE Project started in June 1998 and will finish at the end of June 1999. Its realisation is situated to the logistic area. The objective of this project is to prove that the application of a new style of software development is really worthwhile, before extending it to the rest of areas of the company.In this paper we provide the reader with an information on how we approached the implementation of the OO software development environment and what results we achieved up to date.
2 MIST – A Measurement Selection Tool
Authors: Farr William H. , Crigler John R. 
Published: November 2014

AbstractThis paper describes a tool that is being jointly developed by the INCOSE Measurement Working Group (MWG) and a group at the Naval Surface Warfare Center Dahlgren Division under sponsorship of the Office of Naval Research (ONR). The tool is a database of key measures to be used throughout a complex system development for that system's evaluation and assessment. The tool can be used both by program management and the technical personnel involved in doing the evaluation to identify which measures should be collected covering the project, the system development process, and the system itself.
Metrics and Processes for F‐22 Requirements Management
Authors: Meyer Al 
Published: November 2014

AbstractThe F‐22 Advanced Tactical Fighter Program has documented over 76,000 functional and design requirements in more than 231 hardware and software specifications during its Engineering and Manufacturing Development (EMD) phase of development. Because of the complex and integrated nature of the requirements, it was necessary to develop an automated relational database tool in which to store, track and analyze these requirements.Besides selecting an electronic tool to use team wide, a process had to be developed for the requirements change process, along with metrics for the tool to generate, in order to monitor the process. The process had to be acceptable and nonintrusive to procedures already established at the three primary contracting companies of Locheed Martin Aeronautical Systems, Lockheed Martin Tactical Aircraft Systems, and Boeing. The metrics needed to be easily collected and provide relevant data to the health and accuracy of the overall database.This paper documents the criteria which went into tool selection, the procedures established for tool use, and the metrics developed to monitor the process.