bluuebunny/crossref_metadata_2025_split huggingface dataset:
1 Systems Engineering On‐Time Deliveries
Authors: Warmkessel Joyce M. 
Published: November 2014

AbstractThe typical systems engineering application focuses on developing and delivering products which meet an acquirer's specified requirements, with emphasis on performance requirements. As currently practiced, however, systems engineering is not considered as a mechanism for identifying and reducing the amount of development rework – a major cause of project delays and cost overruns. Yet two elements of the systems engineering process, in conjunction with system dynamics analyses, can be used to reduce both the amount of rework required and the time required to identify the need for such rework.
2 Systems Engineering and the Joint Strike Fighter: The “Flagship” Program for Acquisition Reform
Authors: Struth Robert G. 
Published: November 2014

ABSTRACTThe Joint Strike Fighter (JSF) program represents the largest potential aircraft contract for the U.S. Department of Defense (DoD) in the foreseeable future. It will provide replacement strike fighters for the U.S. Air Force, the U.S. Navy, and the U.S. Marine Corps, as well as for the United Kingdom and probably many other non‐U.S. services. The objective of meeting the different needs of many services with variants of a single airplane is a very difficult challenge, especially when the number one consideration is affordability.As part of the plan to achieve an affordable solution, the JSF program will be conducted under the DoD's acquisition reform initiatives begun in 1994. These initiatives mandate a new and innovative way of doing business, canceling many government military
2 Designing an Optimal Product Introduction Process for an Extended Enterprise in the Aerospace Sector
Authors: Clegg Ben , Boardman John , Boardman Alison , Mason‐Jones Rachel 
Published: November 2014

AbstractThe process of introducing complex new aerospace products is such that a single company can rarely claim to possess the entire technical expertise, resource base, or investment capital required to fully accomplish it. Therefore, it is a growing trend for aerospace companies to require a provisional understanding between their suppliers, partners, or customers before engaging in the development of any substantially new products. Such a group of companies forms the embryonic ‘extended enterprise’ (EE) which may be thought of as a 'system of systems' where each of the sub‐systems is an individual company. This extended enterprise may continue to work together and become cohesively bound by contractual obligation into a fully fledged EE; which should be capable of sustainable competitive product realisation. The benefits of shared new product development means that system engineering expertise and commercial risk is shared. However, the main disadvantage is that project management complexity increases, which lengthens product lead‐time and raises costs. The question that must asked is, when and how do the individual systems become effectively bound to make up a single system?
1 Development of a Skills and Knowledge Taxonomy Aligned with the EIA/IS 731–1 Systems Engineering Capability Model
Authors: Widmann E. R. , Hudak G. J. , Hudak T. A. , Anderson G. E. 
Published: November 2014

AbstractThe INCOSE Corporate Advisory Board has set a high priority on the generation of a skills and knowledge taxonomy aligned with the EIA/IS 731–1 Systems Engineering Capability Model (SECM). For an organization to grow in systems engineering capability when implementing the EIA/IS 731‐1 SECM, individuals within that organization must also grow in increasing levels of competency. This paper describes the establishment within the INCOSE Technical Board of a special team to generate the needed taxonomy and presents preliminary results of their efforts. A brief account is provided on the general importance of capability models, which establishes a background for this high priority task. Key features of the EIA/IS 731‐1 SECM, to which the taxonomy is to be aligned, are summarized. The development approach for the taxonomy is described. A foundation is presented for the taxonomy's architecture, which is comprised of three highly congruent models. The paper closely ties the taxonomy to elements of the EIA/IS 731‐1 SECM. An example demonstrates the application of the taxonomy to the development of a set of enabling skills for the conduct of risk management per the EIA/IS 731‐1 SECM. The paper concludes with a description of future activities. The completed document will be entitled The Taxonomy Of Systems Engineering Competency, with subtitle Enabling Growth In Systems Engineering Capability Aligned With The EIA/IS 731‐1 Systems Engineering Capability Model.
1 Development of Internet in Latin America: The role of Academic Network Systems and their future
Authors: Aguilar Santiago R. 
Published: November 2014

AbstractThe role of academic network systems was pivotal for the development and expansion of Internet in Latin America. Most of the first Internet points‐of‐presence (POPs) in the region were implemented within the academic and scientific community. Today, deregulation is fostering a wave of competition and privatization through the region. The academic networks are facing a more competitive regulatory environment on the one hand, but also facing strong monopolies of basic telecom services on the other hand. It is necessary for regulatory agencies to establish and enforce clear and open regulations to help the survival of the academic networks. However, it is also necessary for the academic Internet providers to implement creative and aggressive strategies to continue providing communications services to universities, high schools and research and scientific institutions.
3 The Sociological Impact of Computers and The Internet on The Elderly
Authors: Ward Edward E. 
Published: November 2014

ABSTRACTThis paper explores the growth of the use of computers and the Internet by the elderly. For the purpose of this paper, elderly is defined as someone 60 years or older. This paper begins with a short history of the environment in which this segment of the population has developed. It also includes an introduction to the Internet and computers and their effect on society. It discusses how the elderly receive information and education on computers and the Internet. It also explores the different uses that the elderly use the Internet for and compare them with society in general. The paper discusses how government agencies offer their services to the elderly on line. It demonstrates the impact that the Internet is having on the lifestyle, quality of life and day to day life of the elderly. Included also is a look at the expansion of the utilization of the Internet by the elderly. This paper presents a conclusion and a look into the future as the “Baby Boomers” reach retirement age.
2 Risk‐based Decision Support
Authors: Roberts Barney B. , Fussell Louis 
Published: November 2014

ABSTRACTRisk Management is often accomplished in a segmented and incomplete process. The engineering design team will worry technical risks, the mission planning team will worry mission success, and the program management team will worry about cost and schedule risks. None of these issues are independent. Schedule reductions or cost reductions will cause technical risks which may compromise mission success. Likewise a solution to a mission risk will create technical risks which directly impacts cost and schedule performance.Risk‐based decision support is a process of examining the entire risk environment of a decision issue and presenting not just a point value to a decision maker, but the risk impacts, uncertainty, and the risk drivers for the solution options.Current hot topics such as DoD's CAIV (Cost as an independent variable) and NASA's “Faster, Better Cheaper” (FBC) approach to projects and programs are concepts that beg for an integrated approach to risk management. The previous culture was to approach risk as “reduce all risk at any cost”. The current environment demands that risk be a traded resource along with cost, schedule and mission performance. Decisions must be made such that an acceptable mix is achieved.Our approach is designed to integrate these risks into a common framework. It is designed to be a part of the program manager's decision‐making process. All decisions are made within a context of understanding the total integrated risk to the project.
3 Sources of Performance Risk in Complex System Development1
Authors: Browning Tyson R. 
Published: November 2014

AbstractDeveloping complex systems is an exercise in uncertainty reduction and risk management. This article continues a previous paper, synthesizing research findings from literature and interviews with experienced product development managers and system engineers at a major aerospace company regarding the sources of uncertainty underlying one category of risk, product performance risk. Relationships between sources of performance uncertainty are shown using a causal framework. Consequences of performance uncertainty and shortfalls are also discussed. The goal of this preliminary work is to highlight areas for increased attention in planning and management processes, while providing a systems view of the effects of certain actions.
1 Structured Engagement
Authors: Boardman John , Fairbairn Allen 
Published: November 2014

AbstractWe discuss the management of the large product development process which necessarily involves a web of firms. Optimisation at the level of the firm means sub‐optimisation at the web level or the extended enterprise. Reductions in costs and lead times, for product development in the large, is only possible by recognising that effort is distributed across a market value chain. In this paper we describe a framework for ‘structured engagement’. This will support key decision‐makers in performing concurrent design of the architectures for the product, the processes, and the chain that delivers the required competencies (skills and technologies.
2 Integrating Government and Commercial Requirements – Serving Two Masters
Authors: Bayer Steve , Boese Gary , Hart Dan , Bonniksen Chris 
Published: November 2014

ABSTRACTThe world market for launching satellites increased dramatically during the Preliminary Engineering and Manufacturing Development Phase of the United States Government's Evolved Expendable Launch Vehicle procurement program. This coincided with the U.S. Government's increased emphasis on acquisition reform ‐ insight versus oversight. These events brought about the following issues:
Development funds could only support a single design for both government and commercial customers,
Government and commercial requirements needed to be merged,
The government needed assurance that its requirements would be preserved, and
Government insight requirements had to be satisfied.
The Boeing Company integrated and managed the Government Evolved Expendable Launch Vehicle (EELV) System Performance Requirements (SPR) and the Boeing commercial customer launch requirements into the Boeing Delta IV launch system development program. This paper describes the organization of the specification tree, the integration and flow‐down of requirements, requirements change management, the requirements verification, and the lessons learned from these activities.
4 Risk Management in the Department of Defense
Authors: Schaeffer Mark D. 
Published: November 2014

AbstractSince 1995, the Department of Defense (DoD) has increased its emphasis on risk management and changed the approach to its implementation. This presentation briefly summarizes the relationship between risk management and the DoD acquisition reform initiatives instituted by the Department in 1994–95, the evolution of risk management within DoD to its current state, and the contributions of the DTSE&E‐chaired Risk Management Working Group.Despite progress, there is still considerable work to be done to improve the effectiveness of risk management in DoD. This presentation discusses the following future and ongoing initiatives to achieve that end:
Institutionalizing risk management as a normal management function in DoD acquisition programs,
Implementing risk management,
Sharing information,
Improving risk management training.
4 Technology Assessment Tool (A Systems Engineering Approach to Assessing U.S. Department of Energy Technology Proposals)
Authors: Rynearson Michael A. , Nonte John , Richardson John G. , Sebo Donald E. , Cooper W. Brooks , Theriault Rudy J. 
Published: November 2014

AbstractThis paper discusses the system design of a Technology Assessment (TA) tool that can be used to quantitatively evaluate new and advanced technologies, products, or processes. Key features of the tool include organization of information in an indentured hierarchy; questions and categories derived from the decomposition of technology performance; segregation of life‐cycle issues into six assessment categories; and scoring, relative impact, and sensitivity analysis capability.An advantage of the tool's use is its ability to provide decision analysis data, based on incomplete or complete data.
1 Systems Engineering Through Stages
Authors: Stevens R. J. , Brook P. 
Published: November 2014

AbstractSystems engineering demands repeated exploration of requirements and practicality through all parts of the development and operational life cycle. Development and usage must proceed in a series of stages, in which systems engineering processes interact with the organisational decision‐making. This paper defines a systems engineering approach based on established concepts from the innovation, product management and systems engineering literature. This model suggests that a unified systems engineering approach can be applied to all of development, including innovation, prototyping and evolutionary development.
2 System Engineering and Marketing
Authors: Paul David J. , Kenley C. Robert 
Published: November 2014

AbstractUsing models to capture requirements and to initialize operations concepts for new product development has received attention in the Eighth Annual INCOSE Symposium in Vancouver, with the result that the requirements handling process itself is more efficient. The document‐driven design methodology is replaced with models that state subsystem‐level requirements in executable form. However, most “models” are product‐focused and do not incorporate a methodology to clarify and quantify customer needs in relation to that product. This paper outlines a method that has been used by the authors in projects varying in size from church building programs to large satellite programs and involves both marketing and system engineering disciplines.
3 The Common Denominator
Authors: Karas Len , Rhodes Donna H. 
Published: November 2014

AbstractThis paper presents the systems engineering methodology in use at Lockheed Martin Federal Systems (LMFS) in Owego, New York. This LMFS‐Owego methodology has evolved over a fifteen‐year period, through evaluation, selection, and synthesis of many successful techniques used for systems analysis and design. The most recent enhancement to the methodology is theOperational Description Template, which serves as acommon denominatorfor optimal systems development. We discuss the problem that the methodology addresses, overview the process to which the methodology is applied, describe the methodology, and discuss initial results of the application of this method.
4 A Framework for Early Evaluation of Functional Product Structures
Authors: Harzenetter Florian , Thomé Bernhard , Igenbergs Eduard 
Published: November 2014

AbstractThis paper proposes a framework which supports the assessment and optimisation of the quality of products in very early phases of product development. First, an introduction is given to the notion of architecture and its establishment during the lifecycle process. Then a set of metrics is presented which is used to evaluate structural properties of a product architecture. This evaluation mechanism also serves to optimise a product structure towards an optimal representation of these properties. Finally we will show that structural properties support quality aspects that can be used to determine desirable product structures for a given design problem.
4 System Flowdown Using Enhanced QFD
Authors: Clausing Don , Cohen Lou 
Published: November 2014

AbstractIn defense/aerospace systems engineering the requirements are usually flowed down to lower, more detailed system levels directly as a self‐contained process. Commercial systems engineering takes a more eclectic view of the flowdown process. Here we set forth the complete commercial system flowdown process, which has two primary features: (A) a zigzag path through requirements, concepts, and improvement at system level N, which is then repeated at level N+1, and (B) three sources for requirements at level N: (1) higher‐level requirements from level N‐1, (2) the voices of external stakeholders (VOES) at level N, and (3) amplifications of the functions at level N. Thus, this approach expands on the narrow flowdown of requirements by integrating it with the VOES and functional analysis, and integrating all of requirements with concept selection and improvement. This is done by utilizing QFD, functional analysis and amplification, and Pugh concept selection. This process when implemented effectively provides competitive advantage in the global commercial competitive markets.
3 Software Reusable Artifacts Evolution: A Three Levels of Abstraction Framework
Authors: Toffolon Claudine , Dakhli Salem 
Published: November 2014

AbstractThe software crisis is still going on but is nowadays, more critical than ever as organizations cannot exist without operational software. Ramifications of the software crisis are both economic and social. In that context, software reuse is a key technology which permits organization to cope with many aspects of the software crisis (maintenance costs and development cycle times reduction, software systems quality increase). However, despite the potential benefits of software reuse, current reuse methods, techniques and tools fail to improve the software development process productivity and the software products quality. In particular, existing software technology doesn't take into account the organizational aspects of the software reuse process complexity. In this paper, we propose a three‐ levels of abstraction (conceptual, organizational, technical) framework to describe the reusable artifacts evolution activity. The conceptual level lists the main tasks of the evolution activity and the data flows they exchange. The organizational level describes the actors contributing to the evolution activity and the evolution tasks carried out by each actor. The technical level emphasizes the version control problems resulting from reusable artifacts evolution and defines a set of basic rules to cope with these problems.
4 SPARTAN: an approach to software and systems engineering process assessment
Authors: Holt Jon , Patel Dipesh 
Published: November 2014

AbstractThis paper, initially, describes a SPICE (ISO 15504) compatible software process assessment tool for safety‐critical systems for use in the rail industry. This assessment tool and methodology, known as SPARTAN, is then extended to take into account systems engineering, rather than just software engineering.
1 Towards a Standardised Systems Engineering Information Model
Authors: Herzog Erik , Törne Anders 
Published: November 2014

AbstractData exchange capabilities of contemporary systems engineering tools are, on the whole, limited. The main reason for this is the effort required for implementing tool to tool data exchange ‘bridges’, and the large number of tools available on the market.This paper is one in a suite of three papers presenting the results of the Esprit 20496 ‐ SEDRES. The objective of the project has been to provide the groundwork for a systems engineering information exchange standard within the ISO 10303 (STEP) framework. The companion paper by Johnson et al. (Johnson et al., 1999] provides an overview of the project and a report on the results of SEDRES. In this paper, the focus is on presenting the structure, scope and plans for future extensions of the SEDRES information model.The SEDRES information model has been specifically developed to facilitate data exchange between systems engineering tools. It has also been put forward as input for the standardisation work, that in due time will result in a STEP Application protocol for systems engineering – Application protocol 233.
2 Function Analysis and Decomposistion using Function Analysis Systems Technique
Authors: Wixson James R. 
Published: November 2014

ABSTRACTThe “Father of Value Analysis”, Lawrence D. Miles, was a design engineer for General Electric in Schenectady, New York. Miles developed the concept of function analysis to address difficulties in satisfying the requirements to fill shortages of high demand manufactured parts and electrical components during World War II. His concept of function analysis was further developed in the 1960s by Charles W. Bytheway, a design engineer at Sperry Univac in Salt Lake City, Utah.Charles Bytheway extended Mile's function analysis concepts and introduced the methodology called Function Analysis Systems Technique (FAST) to the Society of American Value Engineers (SAVE) at their International Convention in 1965 (Bytheway 1965). FAST uses intuitive logic to decompose a high level, or objective function into secondary and lower level functions that are displayed in a logic diagram called a FAST model.
1 Tailoring Quality Function Deployment for Use in Systems Engineering
Authors: Plowman Catherine 
Published: November 2014

AbstractThis paper describes and illustrates a tailored version of the Quality Function Deployment (QFD) methodology referred to as the “House of Quality”. The tailoring has been accomplished to facilitate the use of QFD by systems engineers—especially in the early project phases. All steps are completely documented as are the augmentations to the standard QFD approach. These augmentations include project initiation; requirements normalization; customer, opportunity, and integration impact scoring; system concept scoring; and system concept synthesis and selection. The closing section describes a NASA project in which this tailored approached produced significant and quantifiable cost savings.
2 A Solution to the Architecture/Software Design Bind ‐ The Mission Object View
Authors: Frank Rodger F. 
Published: November 2014

AbstractTwo powerful approaches to system modeling, each of which addresses important issues in the system development process, are currently available for use: architecture view sets and domain level object modeling. Each of these techniques is insufficient to architect complex, software intensive systems when used alone – object modeling does not address important physical and low‐level architectural concerns and an architecture depiction may violate a smooth object development unintentionally. Additionally, the two approaches are interdependent and interact in conflicting, confusing ways. This is the central nature of the architecture/software design bind. This paper suggests a solution to the architecture/software design bind by including the domain object model in the architecture view set as a full fledged, participating view – the Mission Object View. This allows a controlled and complete relationship between object constructs and architecture entities.
3 Methodology for Measuring Requirements' Impact on Software Size
Authors: Stewart Ron , Donat Michael R. 
Published: November 2014

AbstractAccurate estimation of the size of the software needed to implement a set of requirements allows for more efficient planning. Preliminary results at Raytheon System Canada Ltd. indicate that objective analysis of requirements can increase the precision of software size forecasts. This paper defines a methodology for measuring the impact of requirements on software size.