bluuebunny/crossref_metadata_2025_split huggingface dataset:
4.3.2 An Information Model for Integrating Product Development Processes
Authors: Lykins Howard , Rose Susan , Scott Peter C. 
Published: November 2014

ABSTRACTThis paper describes some of the work products used or generated during the development of a software‐intensive system by integrated product teams (IPTs) working on the system elements. An information modeling approach represents the relationships among the information entities involved in the system‐level management, design, verification, integration, and testing activities: the model has been extended to the subsystem, configuration item, and component levels. The purpose of the information model is to provide developers with additional knowledge about the work products composing the information flows defined in a process model. This additional knowledge makes it easier to adopt the process model, tailor it for use on a project, and understand the roles of the IPTs and their members.
5.3.5 Integration of Small Satellite Cost and Design Models for Improved Conceptual Design‐to‐Cost
Authors: Mosher Todd , Barrera Mark , Lao Norman 
Published: November 2014

ABSTRACTIn the late 1980's a new paradigm, the utilization of modern small satellites, arose and opened up a new class of space applications. Since 1991, The Aerospace Corporation has been studying small satellites. Two products of this on‐going study are the Small Satellite Cost Model (SSCM) and the Small Satellite Design Model (SSDM). In an effort to better meet design‐to‐cost goals for conceptual design, The Aerospace Corporation has recently integrated the SSCM and SSDM into a single design‐to‐cost tool for use by a systems engineer either working alone or in cooperation with a design team. Several versions of the integrated tool are being developed with varying levels of fidelity.
1.4.3 Traceability for the Development and Assessment of Safe Avionic Systems
Authors: Pearson Sheena , Riddle Steve , Saeed Amer 
Published: November 2014

ABSTRACTFor complex avionic systems, evidence must be provided to demonstrate that the risk associated with the software is acceptable. It has been proposed that this evidence be obtained by conducting safety assessment in parallel with development. This increases the importance of co‐operation between teams (including development, assessment and safety authority). To facilitate this co‐operation, a traceability method is proposed, based on a set of information structures and procedures for their analysis. An application of the approach to a study based on the Slats & Flaps system for the Airbus 321 is presented.
1.4.4 Use of QFD as an Integrated Product Team Tool to Select Concepts Based Upon Requirements
Authors: Hess Don , Vance Matt , Ball Doug 
Published: November 2014

ABSTRACTThe potential for improved weapon load outs on advanced aircraft was recognized by the Wright Laboratories, Munitions Division as a key enabling technology for dramatic improvements in the system performance and affordability. The dilemma faced by the Laboratory was the plethora of enabling technologies, and design concepts. Their combinations were staggering. Given recent weapon technology investments and varying strongly held professional opinions on the best aircraft integration approach, the way ahead was not obvious. Over 1000 potentially feasible combinations of options were available.The laboratory was interested in demonstrating feasible technologies to reduce risk and increase the technical readiness of compressed weapons technologies.The overall goal was to increase the sortie effectiveness of small, F‐16 class fighters by over an order of magnitude using new smaller more accurate munitions currently in development. Resources were available for further development of a limited number of compressed weapons technologies and aircraft carriage technologies. The way we chose to rapidly and accurately identify the high payoff concepts was the use of Quality Function Deployment (QFD) as a formal systems engineering tool in an Integrated Product Team environment. The use of QFD enabled the IPT to select high payoff technologies based upon “system requirements” and a high degree of professional knowledge and experience. The QFD process enabled us to eliminate biases built in from the different organizational views of the team which was made up of government/industry, weapon/aircraft, primes and suppliers and to identify synergistic concepts worthy of additional design and development.
4.4.2 Designing Client‐Server Systems for the Intensive Care Unit: An Application of Performance‐Driven Design
Authors: Zaleski John R. , Binder Ernst , Silliman Keith 
Published: November 2014

ABSTRACTWe present a method of computer system performance analysis. As an example of the method's utility, we apply it to the process of designing and modeling a database management system to aid physicians and staff in the process of monitoring and analyzing patient cardiovascular and respiratory data in a typical hospital intensive care unit (ICU). This example application is based on work in critical care data analysis performed by the first author as part of the Ph.D. dissertation requirement at the University of Pennsylvania. The critical data needs of ICU staff are analyzed and a client‐server based database processing system is presented which is robust enough to sustain the data recording needs of 20 patients within the ICU with sufficient bandwidth to permit concurrent data retrieval on patients.
2.5.4 How Maturity Modeling Saved My Softball Team
Authors: Armstrong James R 
Published: November 2014

ABSTRACTThe general acceptance and success of the Software CMM has led to a proliferation of copycat models. There are reportedly about four dozen in some stage of creation. Systems engineering is now deeply involved in this movement. These models can have great benefit to a systems engineering program. However, there is also risk of overemphasis on the institutionalization of processes rather than the value or effectiveness of the effort. This paper looks at the traps one can fall into and how to avoid them.
3.5.3 A Device to Measure Systems Engineering Process Maturity, Effectiveness and Product Quality
Authors: Topf Philip A. , Bellagamba Laurence 
Published: November 2014

ABSTRACTThis paper describes a device to enable project teams to measure how well they are performing systems engineering with respect to both process maturity and effectiveness and to determine the most important process areas to improve. The development and rationale for the systems assessment device and its application at the Rockwell Collins Avionics & Communications Division is described. Key features used to implement the device and to report project findings are illustrated. Lessons learned from application to 27 projects are reported.
4.5.1 An Application of the Analytic Hierarchy Process to Systems Engineering and Project Management
Authors: Fisher Gerard H. 
Published: November 2014

ABSTRACTDeclining federal budgets and pressures from other companies are causing an increase in the competition for a decreasing number of government contracts. The world is exploding with new applications for desktop workstations, even in the military environment. The information technology field emerged with little discipline in either hardware or software development. Improvement was encouraged through the introduction of government quality initiatives and a 1995 U.S. congressional mandate limiting awards of new government contracts to those companies with a record of good past performance. Poor performance on a single contract can take a company out of competition for up to five years! This adds urgency to improving a company's performance on existing contracts.To ensure customer satisfaction, high quality products, and a profitable relationship, a company needs to make an early identification of potential problems and take corrective actions before they impact the customer. To this end, the author developed an Analytic Hierarchy Process (AHP) model which identifies project problems early enough to take corrective action. AHP permits multiattribute evaluation of economic data, other numeric factors and subjective factors and yields a single figure of merit.This project applied the systems engineering process to the development and implementation of this AHP model. The model synthesized the expert knowledge of five experienced systems engineers and project managers to develop the weighting of the various elements of the model. The model was built to use the existing executive information system being used by a moderately‐sized corporation's executive officers and is easily transferable to other organizations. It is a new way to interpret the data. The results, based on nine months of data collection and analysis for 152 projects, indicate that project performance can be predicted based on current data collected.
4.5.3 A Comparison Study in Software Requirements Negotiation
Authors: Egyed Alexander , Boehm Barry 
Published: November 2014

ABSTRACTIn a period of two years, two rather independent experiments were conducted at the University of Southern California. In 1995, 23 three‐person teams negotiated the requirements for a hypothetical library system. Then in 1996, 14 six‐person teams negotiated the requirements for real multimedia related library systems.A number of hypotheses were created to test how real software projects differ from hypothetical ones. Other hypotheses address differences in uniformity and repeatability.The results indicate that repeatability in 1996 was even harder to achieve then in 1995 (Egyed‐Boehm, 1996). Nevertheless, this paper presents some surprising commonalties between both years that indicate some areas of uniformity.In both years, the same overall development process (spiral model) was followed, the same negotiation tools (WinWin System) were used, and the same people were doing the analysis of the findings. Thus, the comparison is less blurred by fundamental differences like terminology, process, etc.
5.5.1 Re‐engineering the Prime Contract Office
Authors: Mawby Dave , Brooks Barry 
Published: November 2014

ABSTRACTConcurrent engineering (CE) is reasonably well understood in a product design and build environment and can yield significant benefits in terms of shorter lead time, lower costs and reduced rework.Large complex projects typically use some form of prime contract office (PCO) to manage and coordinate the delivery of a product/project against a set of customer requirements. This PCO environment is characterised by the management of multiple subcontractors through the disciplines of systems engineering (SE) and project management. A traditional SE approach (as typified by the waterfall diagram) tends to imply sequential activities rather than the concurrency associated with design/build activities. So, does the more complex environment of a PCO still offer opportunities for significant improvements from CE?Evidence suggests that these improvements can be made in the PCO environment. This paper demonstrates how the ‘process’, ‘people’ and 'systems' changes that deliver CE can be applied in the PCO context and outlines a framework for successful PCO operation.
5.6.1 The Aerospace Corporation's Concept Design Center
Authors: Aguilar Joseph A. , Dawdy Andrew B. , Law Glenn W. 
Published: November 2014

ABSTRACTThe Concept Design Center (CDC) developed by The Aerospace Corporation has enhanced support to its customers by providing a process for bringing together the conceptual design capabilities and experts throughout The Aerospace Corporation. The members meet as a group on an as‐needed basis in a computer laboratory to create and evaluate conceptual designs in a synergistic and concurrent manner.The CDC consists of a number of teams, each of which focuses on a different segment of the mission. This paper will focus on the general characteristics of the CDC and on the Space Segment Team (SST) whose primary function is the conceptual design of the spacecraft.
7.6. Implementing An Acquisition Information Systems Architecture
Authors: Gopalakrishna Srikumar V , Little Patrick 
Published: November 2014

ABSTRACTUpper level management increasingly find the need to align any development efforts with business needs, organizational mission, goals and strategies. While there is an increased demand for greater value from the acquisition programs at reduced costs, there are limited resources to achieve this goal. Improved program management of IT is key to increasing acquisition program effectiveness and reducing costs. Most organizations today find an immediate need for an enterprise wide architecture framework that describes work processes, information flows, information technology (IT) and standards to meet its mission‐critical acquisition programs.While many information architecture models such as the Zachman framework “(Zachman 1987, 1992)” for information systems architecture and the three‐schema architecture exist in industry, none have gained sufficient acceptance to be considered a standard.The Acquisition Information Systems Architecture (AISA) was developed to assist our clients, especially those in the Government, comply with legislative and executive agency guidance and to facilitate a framework that guides towards understanding the present and helps plan a migration strategy to a proposed architecture.
7.8. An Integrated Methodology for Developing Interface Documentation (A Method to Maximize Information Reuse)
Authors: Rhoads Russell P. , Harrison Larry 
Published: November 2014

ABSTRACTThis paper addresses the complexity of updating and maintaining interface documentation in a document driven world. This process integrates all activities both vertically and horizontally in order to produce a low maintenance cost set of consistent documentation. The process uses a peel the onion methodology or cookbook approach to interface development. Start with an interface and what comprises it and work down.What are the “Peel the Onion” Interface Development process benefits?
Maximizes the reuse of information
Optimizes time spent in interface development
A logical process flow for the development of an interface
Ensures consistency throughout the interface specifications and Interface Control Documents
Integrates behavior with requirements
Full traceability of behavior to requirements
Provides a mechanism for simulation development
Behavioral information becomes integral part of specification.Using this methodology as the basis of behavioral, simulation and documentation saves time, reduces cost and shortens schedule. The results of this methodology are that significant cost savings can be realized by maximizing information reuse for all interfaces.
7.16. Successful Development of Commercial Infrastructure Projects with Systems Engineering
Authors: Rochecouste Hervé 
Published: November 2014

ABSTRACTAs the International Council On Systems Engineering (INCOSE) internationalises its mission, there is a need to address the advancement of the Systems Engineering practice in all environments where improvement opportunities are achievable. This paper is a bilingual English/French analysis of the application of Systems Engineering disciplines for commercial infrastructure systems development. The analysis addresses areas where Systems Engineering Science can be translated from a military context to assist sister projects on the commercial side of the industry. The paper also encourages INCOSE to consider the external side of its mission, and to find a language that will assist those who need to know, instead of internally preaching to those who already know.SOMMAIREL'apparition du Conseil International de l'Ingénierie des Systèmes (INCOSE) sur la scène internationale permet de promouvoir les avancées de l'Ingénierie des Systèmes dans tous les domaines où une amélioration est souhaitable. Cet exposé est une analyse bilingue Français/Anglais de l'application de l'Ingénierie des Systèmes au développement des systèmes d'infrastructures civiles. L'analyse porte sur les domaines où la Science de l'Ingénierie des Systèmes peut être transposée du contexte militaire vers les projets civils. L'exposé encourage aussi INCOSE à extérioriser sa mission, et à trouver un langage pour aider ceux qui sont encore dans l'inconnu, plutôt que les experts en la matière.
1.1.1 Architecting Space Systems
Authors: Warmkessel Joyce , Kaliardos William N. 
Published: November 2014

AbstractThis paper describes current research in a new process for architecting space systems. It has been observed that traditional systems architecting processes tend not to be followed in practice. Research shows that a single point solution is determined very early, long before the implications of this decision are fully discovered, and the solution is only abandoned when it becomes impossible to implement.This research sets forth an alternative process that provides designers with sets of potentially novel, optimised architectures on which to focus. The process emphasises placing team effort on problem understanding and formulation, versus brainstorming designs within a prematurely constrained architecture. An important step involves representing space architectures as major functions rather than specific forms, allowing brainstorming of the “whats” versus the “hows.”This paper presents the major steps in the process, applied to a distributed satellite swarm for measuring the ionosphere. Simulation results are also presented.
5.1.1 Keeping the Focus During Requirements Analysis
Authors: Carson R. S. 
Published: November 2014

AbstractThe requirements analysis process can have difficulties and diversions which work against success using the standard flow processes. This paper examines seven key problem areas and shows how they can be treated in a disciplined manner to ensure more success during the requirements analysis process. The treatment herein is intended to serve as a reminder of things generally known to practicing systems engineers but often overlooked or neglected in the rush to complete projects. Attention to these items helps catch problems before the design or fabrication is finished, helping to reduce costs of rework. This set of tools can be easily used as review criteria for those needing to develop, manage, design to or verify requirements.
2.2.4 A System Approach to Evaluate Mission Based Flight Performance of Air Ambulance Helicopters
Authors: Kachab D. , Kusumo R. , Sinha A. K. , Hoffmann P. H. , Scott M. L. , Hogan P. , Laycock K. 
Published: November 2014

AbstractThe type of mission systems and the number of crew on board “air ambulance helicopters”, are mission dependent. To evaluate the system effectiveness of the helicopter, with systems and crew on board, requires a holistic study of the mission capability, flight performance, reliability, maintainability and cost. A set of system methodologies are required to evaluate and integrate these parameters to study the mission effectiveness. In this paper a methodology is developed to evaluate the flight performance from a system perspective. The methodology is demonstrated by considering an example helicopter in an air ambulance role on an “incident medical response mission“.
6.2.2 “Shoot the Modelers & Begin Design”; Focusing Analysis on Design Using a System Model
Authors: Steiner Rick 
Published: November 2014

AbstractOne of the principal pitfalls of model driven system development is the establishment and enforcement of appropriate stopping criteria. Without it, good system modelers will continue to add unnecessary detail, and bad system modelers will gloss over important issues. Establishing the boundaries of system analysis activities has frequently been ad‐hoc, or vaguely documented in planning documents.Model driven system design promotes the use of a system model, instead of paper specifications, to describe system static and dynamic relationships. This paper explores the use of this system model approach as a framework for specifying and aggregating analysis activities, and as a mechanism for assessing completeness and consistency of the resulting system concept over time.
8.2.3 A Joint Government & Industry Initiative for Smart Acquisition
Authors: Haysman Peter , Hall Simon 
Published: November 2014

AbstractThis paper gives an overview of a study conducted on behalf of the Future Artillery Weapons Systems (FAWS) Integrated Project Team (IPT) of the UK Ministry of Defence, Defence Procurement Agency (DPA), with BAE SYSTEMS.The initial aim of the study was to provide an insight into the interactions amongst the FAWS programmes & projects, and their respective links to external programmes & projects to provide an understanding of the overall systems architecture of the FAWS IPT.A background to the investigation is given from the stimulus of the UK MoD Smart Procurement Initiative (SPI) together with the approach adopted for the study, the data collection process and the tools & methods applied and a selective overview of the issues.As a result of the study activity a number of observations were drawn by the authors on potential implications for the “bigger picture” of capabilities acquisition, including critical inputs and outputs required of acquisition stakeholders and models of Incremental vs Mid Life Improvement (MLI) acquisition and these are presented in overview.
2.3.2 Towards a Knowledge Based Soft Systems Engineering Method for Systems of Systems
Authors: Staker Rod 
Published: November 2014

AbstractA knowledge based soft systems engineering method for systems of systems investigations is described. The method is based on a combination of the positive features of existing methods from the systems engineering, management science and knowledge engineering literature. The methods on which it is based include Conventional Systems Engineering, Personal Construct Psychology, Quality Function Deployment, Soft Systems Methodology, Distributed Knowledge Engineering and Critical Systems Heuristics. It seeks to enable geographically dispersed participants to collaborate fairly to make joint knowledge about their collective needs and preferences explicit, and to capture these in a structured form in an electronic knowledge repository. Once such problem knowledge has been captured in a structured electronic form, automated reasoning techniques may be used to support decision‐making concerning actions to take to resolve problems and take advantage of opportunities. These reasoning techniques might include artificial intelligence based techniques such as rule‐based reasoning, probabilistic reasoning and constraint logic programming, as well as multi‐objective mathematical programming under uncertainty techniques.
3.3.4 A Systems Engineering Based Tool For Municipal Solid Waste Management In Hochiminh City
Authors: Tu Nguyen Viet , Doukas Louis 
Published: November 2014

AbstractTraditionally, waste management planning has been put into the technical, environmental and economic context only, and solid waste management (SWM) focused largely on technology. Under increasing pressures on resources (of land, energy, finance, and environmental quality), legislation, living standards, public response to ecoenvironmental pollution, it is clear that SWM is becoming increasingly an social‐technical profession, and should be examined in a broader context rather than that of traditional approaches.For the first time in Vietnam, the paper indicated using systems approaches and methodologies to engineer an integrated conceptual systems model. It found that twelve areas should be changed systematically in order to improve the whole municipal solid waste management (MSWM) operations for meeting future challenges and needs in terms of management, organisation, technology, ecoenvironment, economics, urban planning, and legislation.It concluded that systems engineering (SE), when combined with other social approaches, could help managers in their decision making and strategic management planning processes related to topics such as administration structure reforms, policy making, financial structure establishment, service development and performance enhancement, technology selection, processes and procedures innovation in MSWM.