bluuebunny/crossref_metadata_2025_split huggingface dataset:
A Systems Engineering Approach for Computer Based Systems Outline and First Results of a Program
Authors: Schweizer Gerhard , Thomé Bernhard , Voss Markus 
Published: November 2014

AbstractThis paper argues for the necessity of an engineering discipline for computer based systems and outlines its beginnings. It is based on results obtained and directions mapped out for such a discipline by the IEEE Technical Committee on Engineering of Computer Based Systems (ECBS).Computer Based Systems are seen as the technical artifacts of a dedicated engineering discipline. Experience and heuristics of such a discipline need to be grounded in a practical theory. On top of such a theory, a systems engineering approach has to be defined that allows the professional practice of the discipline and the safeguarding of the entire life cycle of all its artifacts. Such a systematization of a discipline inevitably leads to guidelines and to reference standards. Those reference standards reflect the systems engineering approach and regulate the engineering process. The different classes those reference standards fall into are discussed and some consequences are proposed.
Application of a System Architecture Standard to a Federated Information System
Authors: Percivall George S. 
Published: November 2014

ABSTRACTThis paper describes the results of applying a system architecture standard during the development of a federated information system. A description of the system and the application of the standard to describe the architecture of the system are provided. Observations concerning the application of the standard are made, including description of the modifications in applying the standard in a federated environment, as well as, general comments about the necessity of using architectural styles and views.
Balancing Requirements and the Product A Process and Tools Case Study
Authors: Scheurer Robert P. , Kepchar Kenneth J. 
Published: November 2014

AbstractA vast number of requirements are involved in the development of complex systems. Because the systems themselves contain many subsystems with a large numbers of parts, it is a formidable task to ensure that the final product is a complete and accurate reflection of the requirements contained in the customer specification. However, integrated teams now have new and better tools in their arsenal which can simplify their jobs. The following case study examines an improved process using integrated tools on the McDonnell Douglas F/A‐18E/F program for producing higher quality aircraft while still meeting exacting specifications.
An Architectural Model for System‐Level Design
Authors: Calvez J.P. , Peckol J. K. 
Published: November 2014

ABSTRACTThe increasing complexity in the specification and design of electronic and computer based applications, demands that designers begin to think more and more at higher levels of abstraction. To reduce the gap between the specification level and the physical architecture, we propose to add an intermediate level called the functional architectural level. The proposed model has a well‐formalized, semantics and notation, satisfies most of the required properties for an architectural model and is fully integrated into the MCSE methodology. The generality of the inherent concepts permits the model and method to be used at various levels of abstraction and in a wide range of problem domains.
Optimization and Evaluation of Single‐Staged Transportation Systems Example for the Solution of Highly Complex Technical Problems
Authors: Kesselmann Michael 
Published: November 2014

ABSTRACTSpace transportation vehicles are an example for highly complex technical systems. The optimization of these systems is very difficult due to the high degree of complexity and connectivity between the system elements and between the vehicle and its environment. Single Stage to Orbit (SSTO) vehicles as potential transportation systems for future space activities have not yet been investigated in sufficient depth to get an entirely consistent overview of potential fields of operation.A systems engineering approach has been considered to systematically examine the influence of system variations on the overall performance and cost of the vehicle. To speak more generally, in the early pre‐design phase of a new system it seems to be reasonable to first elaborate some alternative concepts. In a second step qualitative sensitivity analyses based upon slight variations of certain vehicle components are investigated.The proposed process has proven to be a very useful and reasonable approach for relatively detailed and reliable evaluation and optimization of complex systems in the pre‐design phase.
Program Maturity and Red‐Team Findings
Authors: Kaslow David E. 
Published: November 2014

ABSTRACTAlmost all programs are established with the components needed to be successful. Those components are: a management process consisting of structures, schedules, and reviews; an engineering process; and a development process. However, a program, especially a large program, can discover too late that the design does not close. Then a red‐team is brought in to assess program maturity and to recommend modifications to design, as well as to the management, engineering, and development processes. This paper characterizes typical red‐team findings and provides recommendations for the review process, decision mechanisms, and review checklists that will address the typical red‐team findings.
A Collection of Integrated Product Development Lessons Learned
Authors: Cusick Kerinia 
Published: November 2014

ABSTRACTAs part of the development process for the Integrated Product Development Capability Maturity (IPD‐CMM) model, the model authors interviewed a series of people from a variety of companies, gathering information on what they believed to be the important aspects of Integrated Product Development, and what they had learned in the process. This paper is a summary of the key points gathered from those interviews, as well as a collection of the primary characteristics that we believe distinguish good Integrated Product Development.
Management of the Systems Engineering Discipline
Authors: Bruno Michelle E. , Mar Brian W. 
Published: November 2014

ABSTRACTFor a company to remain competitive in the market place it is important for the company to utilize their systems engineering workforce effectively. To do this, a company must collect information about their workforce and manipulate this information to the companies' benefit. This paper explores the management of the systems engineering discipline across companies that perform systems engineering activities by: (1) summarizing the current literature, (2) reporting the results of an industry survey, and (3) identifying additional areas for research. Literature is limited when discussing the management and monitoring of individual systems engineering capabilities, the survey data provides insight on how companies manage and track their systems engineering workforce.
The Leverage of Leadership
Authors: Ortberg Natalie Jaramillo 
Published: November 2014

ABSTRACTThe Aerospace Industry has been reeling from all the changes it has seen in the last five years. U.S. Defense budgets have been declining since 1990 from approximately $300 billion to under $250 billion in 1995 (Economist, 1995) and the trend has led to the largest downsizing and consolidation the industry has ever seen. International defense and aerospace companies from all political spheres are also affected, because competition is no longer only based on national, regional or political boundaries as in the past. This paper will study the relationship as leadership style leverages the ability of a systems engineering organization to implement change initiatives that are necessary to sustain a Competitive Advantage in the Aerospace Industry. The challenges of consolidating operations within Aerospace companies is used to illustrate the thesis that leadership styles at all levels of the company affects the ability of an organization to change.
ACHIEVING MORE SCIENTIFIC SYSTEMS ENGINEERING PRACTICES: PRC'S EXPERIENCE IN APPLYING THE SE CMM
Authors: Young Ralph R. , Mosier Steve 
Published: November 2014

ABSTRACTA criticism that could be levied on the systems engineering profession is that while we have been working hard at it for a long time, the improvements in achieving a more scientific approach could be better than they have been. PRC is applying the Systems Engineering Capability Maturity Model (SE‐CMM) to facilitate a more scientific systems engineering (SE) approach. This article reports on the approach used and evaluates our progress to date. It provides insights for other organizations which are believed will facilitate more scientific advances in SE practices elsewhere.
Metrics and Teams: A Winning Combination
Authors: Brown Phillip J. 
Published: November 2014

ABSTRACTTeam performance goals, in combination with process measurements, are essential in getting a group of people to produce extraordinary results. This premise was tested with a group of high school students preparing for the annual Academic Decathlon (AD) competition. Results speak for themselves. Previous team best was a 18th place finish at the state finals. The 1996 AD team finished fourth in Texas. This paper recounts the story of how metrics helped transform a disparate mix of high school students into a high performing team. Lessons learned are reviewed with an eye towards extending them into a business environment.
A Reliable Approach To Systems Engineering Process Maturity
Authors: Brezinski Lawrence J. 
Published: November 2014

ABSTRACTA reliable approach to achieving each stage of process maturity is needed to provide the foundation for continuing process improvement. When properly selected, systems engineering work products tie together standards, policies, and project activities as the basis for implementing a process improvement program. The overall organizational result is improved process maturity and a solid base for accelerating future process improvements.
A Quantitative Metric of System Development Complexity
Authors: Thomas L. Dale , Mog Robert A. 
Published: November 2014

ABSTRACTEach day, engineers cope with the challenges of building complex systems –challenges which threaten the project cost, schedule, and technical performance. Complex physical systems abound in nature – can engineers gain any insight on dealing with complexity from nature? Furthermore, how can these insights be applied? The discussion which follows suggests two fundamental lessons offered by nature in dealing with complexity: (1) system complexity is a function of component interaction and (2) complexity is a means which must be employed prudently. Subsequently, a complexity metric for the engineering application of these insights is presented.
Internal Development of Systems Engineers
Authors: Kaufman Mark S. 
Published: November 2014

ABSTRACTIn the mid 1980's our division president was fond of repeating the statement that management often said, “Systems engineers are born and not made”. Apparently they were not being born fast enough to respond to an increasing need for experienced systems engineers available to be assigned to a wide variety of tasks. Also, as our systems engineering work force became more senior they were promoted to higher salary without the experience base necessary to move into the role of lead systems engineer or system architect. To rectify this problem, a program was put in place with the goal of developing senior level systems engineers. This program includes a documented systems engineering methodology, a set of supporting process documents, a personnel development process, training and mentoring.
Graduate Systems Engineering Education at the Air Force Institute of Technology
Authors: Kramer Stuart , Pohl Edward 
Published: November 2014

ABSTRACTThe Air Force Institute of Technology offers a successful, accredited graduate degree in systems engineering. The program is based on the view that systems engineering is a design discipline. Students with undergraduate engineering degrees are given course work covering essential tools and techniques of systems engineering and are required to demonstrate mastery in a group design study. The program philosophy and curriculum are described and a recent design study is summarized. Although created to meet Air Force needs, the program and experience are relevant to others.
1.1.1 Classifying Systems
Authors: Paul Arthur S. 
Published: November 2014

ABSTRACTIn response to concerns within the field of systems engineering about the overuse and possible misuse of the term ‘systems‘, this paper presents an in‐depth analysis of current schemes for classifying systems and proposes a scheme of nine classes that is simple, intuitive, and focuses on man‐made systems. The author's expectation is that individuals who are interested in the field of systems will communicate more effectively by qualifying systems and speaking of specific types of systems instead of speaking of systems in general. This can also be a first step in a process of developing methodologies and tools that are targeted to the different types of systems.
2.1.3 A Systems Approach towards Design for RAMS/LCC Lessons learned from cases within aerospace, chemical process, and automotive industry
Authors: van Baaren Ron J. , Smit K. 
Published: November 2014

ABSTRACTThis paper presents the preliminary results of a Ph.D. project aimed to develop and implement a framework for the incorporation of reliability, availability, maintainability, supportability and life‐cycle cost (RAMS/LCC) aspects in the design and development process of large‐scale, complex technical systems. Within a systems engineering approach this shall lead to faster, more affordable design, production or manufacturing, operation and support of high‐quality systems that satisfy all customer requirements.Three main activities of research are identified; need analysis, model development and application and validation. This paper centers on the results of several case studies conducted as part of the need analysis phase. These cases, conducted in Europe within three branches of industry (aerospace, chemical process, and automotive industry), identified the need for an integrated systems engineering approach towards design for RAMS/LCC. Additionally these cases provided an overview of current practices, lessons learned and area's of improvement related to design for RAMS/LCC.
3.1.4 A Hierarchical Method for Analyzing Candidate Solutions and Selecting the Best Option
Authors: Stokrp Mark C. , Birns Leonard 
Published: November 2014

ABSTRACTIn this paper the authors describe a case study which used a Systems Engineering Capability Maturity Model (SE‐CMM)‐compliant process for Analyzing Candidate Solutions to evaluate computer system performance modeling tools and recommend one for company‐wide use. As part of the paper, the authors describe the background and objectives of the effort and the details of the technical approach employed. While evaluating competing vendors or commercial‐off‐the‐shelf (COTS) products may be the most common use, trade studies are also useful for analyzing requirements trade‐offs, system or network architecture alternatives, make‐buy decisions, schedule changes, and other decisions faced by engineers and managers.
4.1.1 System Architecture ‐ A View Perspective
Authors: Frank Rodger F. 
Published: November 2014

AbstractDevelopment and deployment of large software systems are among the riskiest of business ventures. Lack of ability to depict, communicate and evaluate the overall architecture of the system ‐ to describe how the system works ‐ is the central issue to this risk. This paper proposes a solution to the system architecture problem. By considering the needed architecture views and view relationships first, then identifying the models needed to implement the views and relationships between them. The concept of architecture views is developed, an example of a necessary and sufficient architecture view set for a large software‐intensive system is provided and architecture relationships to specification and object design are also described.
5.1.1 Overview of the EIA 632 Standard: Processes for Engineering a System
Authors: Martin James N. 
Published: November 2014

ABSTRACTThe EIA 632 standard has been developed that describes the “processes for engineering a system.” This standard evolved from EIA/IS 632—the interim standard that described a systems engineering process. This paper will describe the structure of the standard, elements of the process, and key concepts such as stakeholder requirements, enabling products, building blocks, and development layers.
5.1.2 Evolution of EIA 632 from an Interim Standard to a Full Standard
Authors: Martin James N. 
Published: November 2014

ABSTRACTThe EIA 632 standard has been developed that describes the “processes for engineering a system.” This standard evolved from EIA/IS 632—the interim standard that describes a systems engineering process. This paper will describe the heritage of this standard, reasons for this particular evolutionary step, and the approach in converting from the interim standard to the full standard.
2.2.2 Sources of Schedule Risk in Complex System Development
Authors: Browning Tyson R. 
Published: November 2014

ABSTRACTFrom one perspective, developing complex systems is an exercise in uncertainty reduction and risk management. In this article I first organize the principle sources of risk in product development into five categories: market risk, product performance risk, technology risk, development cost risk, and schedule risk. Second, I synthesize 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 of these categories, schedule risk. Relationships between these sources of schedule uncertainty are shown using a causal framework. 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.
4.2.2 Untangling the Twists in Requirements Analysis
Authors: Jorgensen Raymond W. 
Published: November 2014

ABSTRACTThis paper is a description of requirement analysis techniques that can be used to effectively describe a complex system, using concepts of abstraction and decomposition to layer the system definition into easily understood subsystem components. By using abstracted layers of the system, documents describing the system are more easily understood by reader's who may be unfamiliar or only somewhat familiar with the system description. Also, appropriate abstraction can help the system designers and developers organize and find critical information more readily than the brute force attack of system definition. After all, the entire purpose of systems engineering techniques is to create information that is readily understood and communicable to developers and users of a system. Effective communication with a diverse community of people is the focus of systems engineering practice.
3.3.2 Formalisation of an order processing soft systems model using Petri nets
Authors: Sagoo Jaspal , Boardman John 
Published: November 2014

ABSTRACTSoft systems methodologies are known for investigating the problems occurring in the management of organisations using conceptual models. These models are informal and thus they are easily used and understood by a non‐specialist. However, such models cannot be subjected to formal analysis, and problems can occur in verifying their correctness. This paper addresses this issue by combining Petri net theory with the conceptual models of a methodology known as the Boardman Soft Systems Methodology (BSSM). Specifically, a systematic approach is presented that allows the systemigrams of the BSSM to be translated into Petri net models. This translation allows a systemigram to be checked for the integrity of its data, and Petri net theory can be used to analyse the resulting Petri net models. It is the intention that this type of analysis would be used by a target audience to verify and validate the systemigram models. Application of this approach is illustrated by an industrial case study that involves the Order Intake phase of a product's life cycle.
3.3.3 VERDICT: A Distributed Virtual Environment for System Engineering
Authors: Kuchinski Michael J. 
Published: November 2014

Abstract1This paper proposes a framework for the development of a distributed virtual interface (called VERDICT) for a system engineering development environment that (1) focuses on the role of the human in the system being designed, (2) focuses on the cognitive needs of the engineers using the development environment, and (3) facilitates the intended universality of the environment by relying on technologies that allow architecture independence. VERDICT stands for Virtual Environment for Remote Design Integration and Configuration Testing. Its purpose is to provide a distributed virtual interface to a system engineering environment for the design of complex systems. Principal among its goals is the organization of information through the development of a taxonomy of the types of knowledge representations, or cognitive media, used in system design. Related to this goal is the determination of how these cognitive media are best represented by physical media (text, graphics, animation, sound, etc.). Another goal is implementation transparency, through the utilization of enabling technologies such as Java and CORBA.
3.3.4 Practical Experience Applying Formal Methods to Air Traffic Management Software
Authors: Yates Richard , Andrews Jamie , Gray Phil 
Published: November 2014

ABSTRACTThis paper relates experiences with formal methods that are relevant to the systems engineering activities of requirements specification, design documentation, and test case generation. Specifically, this paper reviews the lessons learned from the application of formal methods to selected components of an air traffic management system. This project used experimental tools developed at the University of British Columbia: S, a formal specification tool; HPP, an HTML documentation tool; and TCG, a test case generation tool. The components experimented on are from a recently fielded system written in C++ using unimplemented pre‐ and post‐conditions on components. The purpose of the experiment was to evaluate the usefulness of these formal methods to uncover design or logic errors in the system components and to assist in designing test cases. This experience identified some ambiguities in the original specification, evaluated the feasibility of the experimental tools we used, and identified areas in which the tools could be improved.
4.3.1 The SEDRES Project (Systems Engineering Data Representation And Exchange Standardisation); Producing A Data Exchange Standard Supporting Integrated Systems Engineering
Authors: Johnson JFE 
Published: November 2014

ABSTRACTIntegrated Product Development frequently involves multi‐company and multi‐national teams, using heterogeneous design tool sets. Systems Engineering (SE) must be able to operate in this environment. SEDRES is producing a neutral data exchange standard based on STEP (ISO‐10303), that will embrace product definition aspects crucial to successful SE: product requirements, systems architectures, product functionality, allocation, traceability and configuration management information. The standard will enable SE tools to exchange such information, and should be applicable to many industries.SEDRES is a three‐year European Commission‐funded ESPRIT project, running 1996–1998, which was initiated by Aerospatiale, Alenia, British Aerospace, DASA and Saab. Also contributing are the Universities of Loughborough, Linkoping, and the Australian Centre for Test & Evaluation.This paper describes the emerging standard, reports on early exchanges and on the successful vote for an ISO standardisation activity. It explains how the draft standard is being extended in the second project phase, and future intentions.