bluuebunny/crossref_metadata_2025_split huggingface dataset:
1 System Simulation ‐ Examples using Smalltalk as a Modeling Tool
Authors: Kaffenberger Rüdiger 
Published: November 2014

AbstractThe behavior of a system in its environment is not easy to describe or to verify. Executable models are a natural solution to this problem. They give the engineer a way to explore and visualize the temporal progress of the system's state. Because Smalltalk is uniformly object oriented, it shows its virtues as a tool for modeling the behavior of systems particularly in conjunction with object oriented system analysis and system design techniques. The two examples will give a first impression of the power of Smalltalk as a modeling tool. We will show the essential components of a simulation framework, that allows an easy implementation of behavior models. Additionally we will present how Smalltalk models can be employed in the requirements phase of a project. A comparison between Smalltalk and C++ will show that Smalltalk as a system modeling tool has many advantages and only few drawbacks.
1 Embedded Systems Development Integration
Authors: STIL Guy , RAWNSLEY Brian 
Published: November 2014

ABSTRACTMost European aircraft development programmes are undertaken by consortia of geographically distributed and culturally diverse industrial organisations. Specification of avionic systems, and their realisation, is undertaken by multiple system specifiers (airframe manufacturers) and multiple avionic system suppliers, using their own methods, standards and tools. The key objective of the SPIDERS project is to reduce the cost and timescale of this distributed specification process. The SPIDERS consortium includes four aircraft manufacturers: Aerospatiale, Eurocopter France, Daimler‐Benz Aerospace Airbus, and British Aerospace Airbus. SPIDERS also includes two avionic systems suppliers, Smiths Industries Aerospace and Sextant Avionique. The programme has a central workpackage involving all of the partners, working towards definition of the New System Development Model. During the project, many improvements in processes, methods and tools were identified and evaluated. The “Current System Development Model” was first captured for each partner as a baseline. This was then harmonised and improvements incorporated to give a “New System Development Model”.
2 Incorporating Contingency Risk into Project Cost and Benefit Baselines: A Way to Enhance Realism
Authors: Fenton Robert E. , Cox Richard A. , Carlock Paul G. 
Published: November 2014

AbstractBecause of their one‐time nature, most capital investment projects are characterized by substantial uncertainty in economic analysis. Virtually all of the underlying data are best‐estimate assumptions (e.g., unit prices, sales volume, production costs, etc.) that cannot be known accurately or validated easily. Nevertheless, decision‐makers frequently tend to minimize or misunderstand cost and benefit risks when approving investment decisions. This paper discusses a methodology being used in the U.S. Federal Aviation Administration (FAA) systems engineering process for improving the quality of capital investment decisions, as well as the subsequent performance during project execution, by explicitly incorporating contingency risk into the project baselines and the investment decision criterion. It is adapted from and draws heavily on the ideas of Dr Steven Book and his colleagues of the Aerospace Corporation, who originally developed many of these concepts for the U.S. Air Force.
3 MUSSAT – A TOOL FOR MODEL‐BASED SYSTEM ENGINEERING OF COMMERCIAL SATELLITE SYSTEMS
Authors: Wilke M. , Quirmbach O. , Negele H. , Fricke E. , Igenbergs E. 
Published: November 2014

AbstractThis paper describes an approach to improve data quality and to reduce the development times for commercial satellites by introducing a software‐tool for the model based design of satellite systems. This tool is called MuSSat – Modelling and Simulation of Satellite Systems. It is being developed to support the early phases of satellite development similar to the Project Design Center (PDC) of NASA's Jet Propulsion Laboratory (Shishko 1997).Basis of the approach and the supporting software tool is a modelling methodology developed at the Institute of Astronautics at the Technical University of Munich.The tool MuSSat provides the user with the means to easily and quickly model all components – and the various interdependencies between them – of a satellite system and to compare various alternative designs. Thus MuSSat enables a company to improve its performance and agility in the new market segment of commercial satellite applications by supporting integrated concurrent engineering.
1 Controlling Rapid Change through Systems Engineering the Organization
Authors: Hihn Jairus , Wheeler Rebecca , Zak Haya 
Published: November 2014

AbstractA new approach to change management has been developed and applied at the Jet Propulsion Laboratory (JPL). It's main focus is on aligning the organization with the strategic plan; and understanding the internal organizational relationships that impact change, which ultimately determine an organizations ability to be transformed and renewed. The new approach regards the strategic plan of a company as the standard by which progress and achievement are measured. Purposeful interventions should generate a company movement along a strategic course, and tracking that movement is essential for managing change. This paper presents an overview of DYNOMO, or the DYNamic Organizational Model which was developed to assist in the measurement and analysis of organizational state. The paper concludes with summaries of two applications.
2 Systems Methodology for Real‐Time Information Systems
Authors: Cropley David H , Cook Stephen C 
Published: November 2014

AbstractThis paper describes the application of novel systems concepts and methodologies to the design and implementation, or more generally the acquisition, of complex real‐time information systems. A hybrid methodology is proposed that combines contemporary ‘soft’ systems thinking with traditional hard systems engineering methodology, to result in an acquisition life cycle appropriate to such systems. This approach acknowledges the difficulties faced when applying hard systems engineering practice to real‐time information system projects with barely definable goals, significant human interaction and where implementation technology is evolving faster than the “system solution” can be designed and developed. The paper outlines the basic concepts of systems thinking that underpin the design of complex systems. Essential elements of traditional hard systems engineering, along with their failings, are described. Soft systems concepts are described and related to the problem of real time information systems. A novel systems methodology for real‐time information systems is proposed. This methodology is then examined in the context of the development of innovative combat system architectures for future naval surface combatants.
3 Architecture for a Process Meta‐System
Authors: Gundrum Valerie 
Published: November 2014

AbstractThis paper discusses using a four‐view architecture description, namely the physical, functional, behavioral, and product views to describe a site's “process system.” Defining this architecture will allow better understanding and usage of the process elements.To understand what a process meta‐system is, we can start with the definition of system as the compilation of hardware, software, and operator/user actions, designed in a configuration that will meet user needs and produce the desired products. For this paper, a process meta‐system refers to the infrastructure that is used by its stakeholders, in order to select, tailor, implement and assure a process that will create the right system.The impetus for this formulation was the realization that many companies, including my own, had a support structure for defining, documenting, instructing, and deploying process and methods, but there was confusion about the activity sequence, roles, responsibilities, approvals, tailoring, and compliance. The approach of this paper is that a process infrastructure is comprised of physical components on which functions are performed, in a time‐sequenced manner, resulting in the necessary work products. These include: a clear understanding of the sequence of activities, an understanding of the inter‐relationship of the program personnel and process owners, timely tailoring and utilization of process assets, and cross‐discipline understanding of roles and responsibilities.
4 Estimating Risk Adjusted Cost or Schedule Using Fuzzy Logic
Authors: Bellagamba Laurence 
Published: November 2014

AbstractA method is presented to quickly and inexpensively obtain risk adjusted cost or schedule estimates so many system implementation options can be compared to find the best performer for a given cost. Cost or schedule consequences are modeled as a function of technical maturity and proposal risk. Technical maturity assesses how much of the system already exists. Proposal risk assess the uncertainty of of the cost and schedule estimates. Fuzzy logic is used as an alternative to probability to estimate the risk adjusted cost and schedule. Using fuzzy logic reduces the time required to interview and interpret domain expert's assessments of risk sources and consequences, while still capturing any uncertainty in the expert's opinion. Using fuzzy logic provides a single number for risk adjusted cost or schedule that does not require interpreting a cumulative probability density function.
3 Parametric Cost Modeling of Space Missions Using the Develop New Projects (DNP) Implementation Process
Authors: Rosenberg Leigh , Hihn Jairus , Roust Kevin , Warfield Keith 
Published: November 2014

AbstractThis paper presents an overview of a parametric cost model that has been built at JPL to estimate costs of future, deep space, robotic science missions. Due to the recent dramatic changes in JPL business practices brought about by an internal re‐engineering effort known as develop new products (DNP), high‐level historic cost data is no longer considered analogous to future missions. Therefore, the historic data is of little value in forecasting costs for projects developed using the DNP process. This has lead to the development of an approach for obtaining expert opinion and also for combining actual data with expert opinion to provide a cost database for future missions. In addition, the DNP cost model has a maximum of objective cost drivers which reduces the likelihood of model input error. Version 2 is now under development which expands the model capabilities, links it more tightly with key design technical parameters, and is grounded in more rigorous statistical techniques. The challenges faced in building this model will be discussed, as well as it's background, development approach, status, validation, and future plans.
4 The Safety Processes of a Prime Contractor
Authors: Irvine R A 
Published: November 2014

AbstractThis paper is a précis of a study commissioned by the Director of Engineering at BAe Systems and Services. It takes the study of Safety Management Systems from other mature industries and decomposes the task into a series of steps based on the nature of the risks to a system. It describes the safety management of a system using an approach that is not prescriptive about the system and its environment but recognises that an assessment of the risk posed by the system should be assessed qualitatively.It addresses the development of the assessment of risk posed by this system over a Systems Lifecycle and application to a flexible living safety case that is more true to the real risks than a prescriptive testing regime at the outset of the project. The changing nature of a system throughout its lifecycle is addressed, right up to disposal in an environmentally friendly and ultimately safe manner.
2 Lessons Learned Teaching Systems Engineering to Practicing Engineers with Mixed Backgrounds
Authors: Boppe Charles W. 
Published: November 2014

AbstractA Systems Engineering subject was taught to a group of 60 practicing engineers within the context of MIT's Systems Design & Management Program during the Summer Session of 1998. Several MIT graduate students were also attending with engineers whose experience ranged between 3 and 24‐years. Industries represented included aerospace, software, office equipment, telecommunications, computers, automotive, and machine tools. This paper describes the content and implementation of the course. Particular attention is devoted to the feedback that was provided by the students and the lessons learned that could benefit similar subjects taught to both graduate students and experienced engineers with different backgrounds, needs, and expectations.
3 Simulation Based Acquisition An Ongoing Look
Authors: Frost Robin , Thomen Dave 
Published: November 2014

AbstractSimulation Based Acquisition (SBA) is a joint Industry and Department of Defense initiative to define an acquisition process that employs a robust, collaborative use of simulation technology to integrate the process across acquisition phases and programs. The intent of the initiative is to reduce the time, resources and risk associated with acquisition while enabling the Integrated Product and Process Development (IPPD) and the quality of the product. In 1998, a Joint SBA Task Force developed an SBA Road Map. This document presented an approach to bring about SBA. This paper will review the background and concept of SBA, and summarize the SBA Road Map that forms the basis for any Implementation Plan.
4 A Human Centered Design Environment for Complex Systems
Authors: Crisp Harry E. , Hoang Ngocdung T. , Schmidt Richard 
Published: November 2014

ABSTRACTAn integrated engineering environment is described wherein capabilities are provided for addressing the role of human operators and decision makers in complex systems. The manner in which the environment supports the implementation of a human engineering process as an integral part of a standard systems engineering process is described. The capabilities of a prototype Human Centered Design Environment currently under development are discussed.
1 The Development of Engineering Processes for a Diverse Engineering Enterprise
Authors: Gates P J , Fearon E A 
Published: November 2014

AbstractThe development of a robust engineering process for a diverse engineering enterprise must not only accommodate a wide range of engineering activity but must also take into account other business functions as part of an overall business process. The development of a robust approach to the engineering aspects of the business process, based on existing practice but drawing upon advances in Systems Engineering, is described. This approach draws heavily on the interrelationships of process, milestones and baselines.
2 Triority: The Advantages of Simultaneous Deployment of Integrated Product Teams, Object Oriented Analysis/Design and Formal Inspections
Authors: Rosser Larri Ann 
Published: November 2014

AbstractAs systems engineers, we tend to take a focused, sequential approach to getting things done. We list the tasks that must be performed, determine which one to begin with, implement it, and move on to the next. We call this establishing priority, and accept this as the right way to achieve our goals. My experience with Integrated Product Development, Object Oriented Engineering and Formal Inspections suggests that sometimes you need a little something more – I call it triority, because making all three of these initiatives your top priority is the key to success.
3 Capturing and Leveraging Essential Organizational Knowledge via Dynamic Roadmaps
Authors: Hansell Todd , DeGregorio Gary 
Published: November 2014

AbstractIn many companies today, technology, capability, and product planning information is maintained in a haphazard collection of overhead slides, spreadsheets, and private databases by a set of disconnected “experts” and updated sporadically (usually just in time for the next review!). This information is often quite sparse and poorly supported by knowledge and supporting data, often being held only in the heads of the “experts.” Therefore, it is often difficult to leverage as external technology and market forces continue to change. In an attempt to improve the technology planning process and to provide the basis from which a company can develop its roadmap planning as a competitive asset, a set of methods, tools, and workshop‐based training have been developed. These assist the technology strategists, systems engineers, marketing professionals, and product development managers in creating, leveraging, and maintaining an organization's critical knowledge in a dynamic fashion.
4 Customer in the Loop (CIL) ‐ The Product Development Cycle Model‐
Authors: Wenzel Stefan , Negele Herbert 
Published: November 2014

AbstractProduct development is a business process where a great number of different functionalities and internal and external interests are intertwined. Involvement of human beings, traditional development structures, specific external conditions and internal resources let almost every development process appear as one of a kind.The modeling and documentation of processes is a prerequisite for reengineering and continuous improvement of development systems. International case studies conducted by the Institute of Astronautics revealed the usefulness of a method which fits to all product development systems in general and provides a principal classification of the different processes involved. In addition, this method should be flexible enough to derive the particular profile of a product development system analyzed. This paper describes the Product Development Cycle Model (PDCM), a new and robust approach which meets these requirements. Starting and ending with customers' requirements, the PDC‐Model especially highlights the importance and impact of strongly interconnected loops and control cycles within a product development system.First we explain typical characteristics that can be used to describe development processes. Then we explain the Product Development Cycle and its distinct sub‐cycles. Finally, we show a current example from a case study.
1 Fifty Ways to Save Your Budget Reduced Cost Systems Engineering Process Improvement
Authors: Sheard Sarah 
Published: November 2014

AbstractAlthough assessments using systems engineering (SE) capability models are being performed for more organizations than ever before, few organizations want to fund a 5‐ to 7‐day “standard” appraisal1. Because of budget pressures, and because assessment expertise is growing within the industry, methods for reducing costs are receiving increasing attention. This paper prioritizes fifty ways to reduce the cost of performing systems engineering process improvement, including assessments. Many of these methods are based on experiences and materials of the Software Productivity Consortium, and others are collected from INCOSE papers.
2 A CMM For All Disciplines
Authors: Cusick Kerinia , Bruce Jim 
Published: November 2014

AbstractNot all disciplines have the benefit of a Capability Maturity Model (CMM) that they can use to focus and guide their improvement activities. Honeywell Space Systems Operations, in cooperation with SECAT LLC, developed a “generic Capability Maturity Model” which included only project and organizational management topic areas, and was designed to be applicable to all disciplines. The model, called the IPDP CMM, was developed in early 1998. The first assessment was performed in the Fall of 1998 for 8 individual disciplines. A rating profile was developed for each discipline, and strengths and weaknesses both common across the organization and unique to each discipline were identified. A few lessons learned for improving the model and the assessment method were found during the assessment which are discussed in this paper, but generally all of the teams found the results applicable and particularly helpful in focusing their improvement efforts. The goal of this paper is to present what was done, the rationale for the decisions, the lessons learned and the benefits of developing and using a generic CMM.
4 Overcoming Barriers to Systems Engineering Process Improvement
Authors: Sheard Sarah A. , Lykins Howard , Armstrong James R. 
Published: November 2014

AbstractNeither systems engineering nor process improvement is new. Since 1992, INCOSE papers and others have been reporting success in documenting and improving processes. A considerable body of process improvement literature is available, particularly related to improvement of software development processes. Even systems engineering process improvement is gaining in popularity, judging from the increasing number of INCOSE papers detailing various efforts. Yet the nature of systems engineering poses challenges over and above those seen in other process improvement efforts. This paper focuses on identifying and resolving typical barriers to improving the systems engineering process.
1 Summary of Results from the Risk Management Program for the Mars Microrover Flight Experiment
Authors: Shishko Robert , Matijevic Jacob R. 
Published: November 2014

AbstractOn 4 July 1997, the Mars Pathfinder landed on the surface of Mars carrying the first planetary rover, known as the Sojourner. Formally known as the Microrover Flight Experiment (MFEX), the Sojourner was a low cost, high‐risk technology demonstration, in which new risk management techniques were tried. This paper summarizes the activities and results of the effort to conduct a low‐cost, yet meaningful risk management program for the MFEX. The specific activities focused on cost, performance, schedule, and operations risks. Just as the systems engineering process was iterative and produced successive refinements of requirements, designs, etc., so was the risk management process. Qualitative risk assessments were performed first to gain some insights for refining the microrover design and operations concept. These then evolved into more quantitative analyses. Risk management lessons from the manager's perspective is presented for other low‐cost, high‐risk space missions.
2 Optimizing Systems Engineering for a Commercial Product Line: A Case Study in International Air Traffic Control
Authors: McGuire Kathleen 
Published: November 2014

AbstractThe development of the ASR‐12 international air traffic control (ATC) radar offers a case study in a shift from the more formal processes and products of the 1980's U.S. government contracts to a commercial product line environment. Both the radar development team and the product had to transition to new approaches. By effectively optimizing the SE process for this new environment, it is the key cost‐effective framework to optimize the product.
4 Incorporating Cost into the Front End of the Radar Systems Engineering Process
Authors: Church Douglas G. 
Published: November 2014

AbstractThis paper describes an initiative to incorporate cost into the initial stages of the design process to get the best cost‐performance value in radar systems design. Tools were developed at Northrop Grumman to provide the design community visibility as to how performance requirements affect the hardware cost. Detailed hardware cost and systems performance models have been developed and applied to ongoing radar development programs at Northrop Grumman giving systems engineers and hardware designers tools they need to optimize their designs. This paper provides a summary of the approach, describes the tools that were developed, addresses lessons learned in implementing the process and gives examples of the type of trades that can be performed using the tools. The approach is easily extended to non‐radar system designs. The process described reduces the possibility of overlooking a better design solution and avoids major changes late in the development cycle.