bluuebunny/crossref_metadata_2025_split huggingface dataset:
2.1.1 Systems Engineering Realization of a Market Model
Authors: Genz Bodo 
Published: November 2014

AbstractThis paper describes the development process of a market model and the model itself. This market model enables the user to simulate the market success of future products on future markets with regard to many influences like competitors and information about the consumer. It is implemented as a software tool. The challenge of this project was to find a structure of the market, which is quantifiable and connectable in a proper way. To achieve this, a special method of developing the model was used. This method is described within the first chapter of this paper. The results of this method are quantified and connectable models. The way how these models were designed and the way they work together with their meaning in the context of the market is shown by some examples, which are related to common problems in business. To demonstrate the strength of the model, some results of the produced software tool are presented in the “Output” chapter.This market model is able to improve the process of product development and the whole means which are connected to the product. But the efficient use of the model requires an integration in the product development and marketing process.
2.1.5 Does Object‐Oriented System Engineering Eliminate the Need for Requirements?
Authors: Kasser Joseph 
Published: November 2014

AbstractThis paper examines system engineering (SE) and object‐oriented (OO) methodologies and then shows both that SE is inherently OO and that OO languages such as the Unified Modeling Language (UML) may be used to document the user's needs in a manner that can be used by developers. The paper also suggests a next generation tool concept that can be used to hold both user and developer representation of the user's needs as an alternative to, and an improvement on, text mode “requirements”, hence increasing the reliability of the shared meaning of the user's needs amongst all stakeholders.
3.1.1 The Case for Systems Management
Authors: Mooz Hal , Forsberg Kevin 
Published: November 2014

AbstractAt the INCOSE 2001 International Conference we were awarded the INCOSE Pioneer Award for “tirelessly working to integrate project management and systems engineering.” In the environment of project management and system engineering, especially in aerospace, this concept is often referred to as Systems Management and there are a few Masters Degrees in Systems Management available from U.S. Universities. However, Systems Management is often viewed as the integration of computer systems, which is not our intent.This paper addresses the definition, need, heritage, evolvement, application, realization, benefits, and visualization of Systems Management. The concept is rooted in the seamless integration of business and technical management such that all technical decisions are business and customer driven to ensure the right system is being built, right.
3.1.3 How To Nurture Systems Engineers In‐House ‐ A Case Study
Authors: Katz Shelley , Lake Jerome , Zonnenshain Avigdor , Mizrahi Haim 
Published: November 2014

AbstractRAFAEL is a company at the leading edge of weapon system development. RAFAEL develops, manufactures and supports products for every branch of the Israel Defense Forces (IDF) and for defense forces of foreign governments worldwide.In 1998, RAFAEL identified the need to improve systems engineering competencies of the engineering workforce. With the absence of systems engineering programs within Israeli universities or through Israeli industries, RAFAEL developed its own in‐house training program.This paper describes the manner in which systems engineering program needs were determined and the initial program design created. The method and results of course evaluations are discussed with a summary of lessons learned and continuous improvements planned.
4.1.3 Selection Process for System Design Using Field Programmable Gate Arrays
Authors: Mirchandani Chandru 
Published: November 2014

AbstractImplementing image extraction algorithms for MODIS has shown the advantage of using Field Programmable Devices to implement CPU intensive functionality very clearly. The technology is not without its disadvantages. The task of translating the processing algorithm into VHDL code for synthesizing the design is complex. Very fast devices led to the belief that the disadvantages are well worth the minor disadvantages of labor‐intensive translation phase. However, this is not so. Analysis of the prototype effort in the implementation of FPGAs to perform image extraction showed a ten‐fold improvement in the actual process and extract function. However, the total labor effort to develop and provide the process, system and hardware to perform the processing took almost as long and cost just as much.Albeit, the replication and reuse of the system was two magnitudes lower in cost. The idea pursued in this paper investigates the use of FPGAs in the postprocessing of telemetry data (or other) data by selectively optimizing the design solution. The criteria for system selection are based on complexity, design time and data availability. The paper will describe the process by which the criteria are selected, rank ordered and evaluated for comparison. A simple design exercise will be illustrated as a demonstration.
4.1.4 Applications of Conditional Inferential Methods for Operational Cost Savings for US Coast Guard C130 Aircraft Maintenance
Authors: Powell Mark A. , Sheppard Edward B. 
Published: November 2014

AbstractMaintenance costs play a significant role in the overall operational cost of the US Coast Guard (USCG) fleet of C130 aircraft. Selection of the preventative maintenance interval for the C130 1500 Series Flight Deck Cooling Turbine provides an opportunity for considerable maintenance cost savings. If this turbine fails in service, it may be damaged beyond repair and cost $30,000 to replace. If overhauled before failure, the cost is typically $500. The USCG currently allows this turbine to fail in service, and is considering a preventative maintenance schedule of periodic overhauls. Failure data for this turbine is relatively scarce however. This paucity of data magnifies the perceived impact of uncertainties in the data, which all but paralyzes USCG decision makers charged with selecting an overhaul interval. The authors process failure and replacement cost data for this turbine using conditional inferential methods. Statistical distributions of Expected Costs Savings per Flight Hour are parameterized as a function of overhaul interval. These distributions and related estimates allow USCG decision makers to confidently select an overhaul interval that minimizes maintenance costs and is commensurate with existing maintenance schedules.
4.1.5 Development of a Systems Verification, Validation & Testing‐Methodology
Authors: Vollerthun Andreas , Engel Avner , Haskins Cecilia 
Published: November 2014

AbstractWhile many are aware of the Rule‐of‐Ten, describing the effects of late changes in the product development process; system verification, validation and testing are activities that are often regarded as tasks to be done at the very end of the development. This perception causes a number of problems (in terms of time‐to‐market, expenses, etc.) for many enterprises. Being aware of this situation a consortium of eight European companies, research institutes and organizations (see Figure 1) has formed to develop a methodology for system Verification, Validation and Testing (VVT). The project was launched in March 2002 and will continue for three years. It will be carried out with funding from the European Community under the 5th Framework Program (Project G1RD‐CT‐2002‐00683). This Paper gives an overview of the objectives, structure and the contents of the project. The paper is a first in a series that will report on the progress of VVT methodology development.
5.1.4 Thales Naval Nederland B.V
Authors: Langenberg Ir. Ilse , Gieskes Jose F.B. 
Published: November 2014

AbstractThis paper describes the path towards continuous and integrated process improvement within Thales Naval Nederland B.V, and more particular within it's Business Unit Combat Systems. The paper's Leitmotiv is formed by the individual concepts: Continuous, Integrated, Process, and Improvement.A major internal reorganisation of the company late '99 together with external trends in the process improvement domain (e.g. CMMI), created a momentum for the regrouping and re‐orientation of process improvement activities within the company.The company's experience with and lessons learned from several process improvement projects, and the unit's reorganisation activities and results are reflected upon by the Leitmotiv and used to identify challenges for the future with regard to process improvement. These challenges are captured in specific goals by senior management, enabling the Business Unit to focus its future efforts on the path towards continuous and integrated process improvement.
6.1.4 Implementing SE and ODM in Railway Projects: Innovating a Conservative Line of Business
Authors: van der Ploeg Menno 
Published: November 2014

AbstractSE (Systems Engineering) is a well‐known and frequently used methodology in the Aerospace and Defense industry. The problems associated with the Civil Engineering industry are comparable to that of Aerospace and Defense industry when it comes to the characteristics of processes, products, and efficiency. However, the Civil Engineering industry does not resemble other industries on how to deal with the problems. One of the reasons is that it is a very conservative line of business. Ever since Railinfrabeheer, which is one of the major companies in the Netherlands, started implementing SE and Object Data Management (ODM) methods. This article describes the characteristics and problems in the Civil Engineering industry, and also expounds on the models, methods, and tools Railinfrabeheer uses. These methods, derived from SE and ODM, are used in the successful development of railway systems. Finally it points out the necessary conditions for succesfull implementation and mentions several benefits experienced by the use of these methods and models.
1.2.4 Let's Just Think About That For A Minute …
Authors: Gilmour Graeme 
Published: November 2014

AbstractThis paper contends that there is a strong relationship between disciplined thought by the individual and the system engineering process. The paper explores this relationship by discussing ideas on how people think and illustrating by analogy the closeness of this activity to that of system engineering. The significance of this is that if individuals perform disciplined reflective thinking in a systematic manner then as a collective whole they are more naturally inclined to follow the general principles of good system engineering practice.
1.2.5 Capstone Design in Education: Systems Engineering and the West Point Way
Authors: Kwinn LTC Michael J. , Pohl Lt Col Edward A. , McGinnis COL Michael L. , Carlton William B. 
Published: November 2014

AbstractThe United States Military Academy, the nation's first engineering institution, is celebrating its 200th birthday. The Department of Systems Engineering, established in 1989, offers a successful, accredited undergraduate degree in Systems Engineering. Although young by Academy standards, the program has become one of the most popular engineering disciplines at the Academy.Each year, approximately 40 cadets major in Systems Engineering and another 30 cadets choose it as a Field of Study (FOS). Cadets are introduced to the different tools and techniques of systems engineering in their course work. The program culminates with a year long group design experience that allows the cadets to put the various tools and techniques into practice on a real world problem. This paper will focus on how the year‐long design study is integrated into our curriculum and has become what we believe is an outstanding experience for our cadets which enables them to enter the Army as confident leaders and engineers.
2.2.5 Analysis of the Rational Unified Process
Authors: Martin James N , Bedocs Jozsef 
Published: November 2014

AbstractRecently, Rational wrote a white paper that introduces a derivative of the Rational Unified Process (RUP) that addresses the problem of system specification, analysis, design, and development. This paper describes an analysis of suitability of the extended RUP for use in the engineering of systems. A comparative analysis is performed between RUP and two systems engineering standards—ANSI/EIA 632 and the C4ISR Architecture Framework.
3.2.4 A Project Managers User's Guide to Risk‐based Decision Support Products
Authors: Roberts Barney B. , Frost David 
Published: November 2014

AbstractWho will find this paper useful? This paper is designed for the mature project management professional who intends to make risk‐based decision making a fundamental, integrating principle of the project's operating processes. This is in contrast to the more common approach of having a separate, standalone process for risk management in which its contribution of information into other decision‐making activities is arbitrary. The paper presents advanced integrated quantitative thecniques and tools that have been proven to have high utility to decision‐makers.This paper presents the following tools and techniques and their utility:

Cumulative Distribution Functions (CDF's) for project completion date
CDF's for cost estimate at completion
Double Pareto boxes
Stochastic Critical Path Analysis
6.2.2 Application of Computer Aided Systems Engineering Processes for Korea Next‐Generation High Speed Railway Train
Authors: Yoo Il Sang , Park Young Won 
Published: November 2014

AbstractA high‐speed rail system represents a typical example of large‐scale multi‐disciplinary systems, consisting of subsystems such as train, electrical hardware, electronics, control, information, communication, civil technology etc. The system design and acquisition data of the large‐scale system must be the subject under strict configuration control and management. Not only the requirements dictate the contracts with the suppliers but also become the basis for the development process, project execution, system integration, and testing. The requirements database provide the system design specification of all development activities. Using the RDD‐100, a systems engineering tool, the korea next‐generation high‐speed rail program can establish requirements traceability and development process management in performing the enabling train technology development projects. This paper presents results from a computer‐aided systems engineering application to the Korea next‐generation high‐ speed railway project. Especially, the focus of the study was on requirement management, PBS management, verfication management and project management.
6.2.4 Design Centers – Transferring Experience from Astronautics to Aeronautics
Authors: Finkel Stephan , Wilke Martin , Metzger Helmut , Wahnfried Markus 
Published: November 2014

AbstractThe paper describes the introduction of the Customer Demand Center (CDC) at Fairchild Dornier Oberpfaffenhofen, Germany. The CDC is a Concept Design Center‐approach dedicated to the preparation and procession of customer related aircraft modifications. After describing the development of the Concept Design Center‐approach, the principal idea and set‐up of a Concept Design Center is presented. The paper highlights some of the differences between the traditional application of Concept Design Centers and the specific purpose at Fairchild Dornier. Based on those differences, the adaptation of the three building blocks within a CDC is presented. Finally lessons learned are discussed.
9.1.5 Risk Management: A practical toolkit for identifying, analyzing and coping with project risks
Authors: Gilb Tom 
Published: November 2014

AbstractRisk management must be fully integrated into all the development and maintenance processes for systems. It involves more than applying risk assessment methods to identify and evaluate system risks. To explain this broad approach to risk management, this paper discusses the way in which ‘Planguage’ (a planning language) and, the ‘Competitive Engineering (CE)’ methods contribute to handling risks.
9.1.6 Ten Powerful Principles for Quality in Systems Engineering and Software
Authors: Gilb Tom 
Published: November 2014

AbstractSoftware projects know they have a problem. Solutions abound. But which solutions work? What are the most fundamental underlying principles we can observe in successful projects? This paper presents ten powerful principles, many of which are not widely taught or appreciated. They are based on ideas of quantification, measurement and feedback. Our maturity level with respect to ‘numbers’ is known to be poor. Hopefully, as we move to higher maturity levels, we will also begin to appreciate numeric expression of idea and the power of measurement.
9.1.8 Collaboration: Government Process Improvement and Methodologies in a Collaborative Environment
Authors: Grubbs Faye , Holzer Thomas H. 
Published: November 2014

AbstractThis paper addresses how one government organization is making strides in its quest for CMM Level 2 through the collaborative strategies of its managers, workforce, contractors, and private industry and other government organizations. The last two years' efforts have yielded an environment that has helped ease the painful climb up the CMM ladder and produced some notable results. The accounts given are both descriptive and prescriptive. Methodologies for proper coordination, strategies for accomplishing buy‐in and accountability, and measures to achieve integration of processes are just some of the discussion points of this paper.
9.2.1 Synergizing Workplace Research and Postgraduate Degrees
Authors: Kasser Joseph 
Published: November 2014

AbstractMany mature age students are taking courses in postgraduate degree programs to acquire a degree needed for promotion. In these circumstances, the students may already have as much, if not more, knowledge about the subject as the instructor. A number of these degree candidates are also working in an environment whereby their work is of a research nature. Workplace research, however, is only one aspect of ongoing research. Important research is also being performed by working groups (WG) in professional organizations such as the INCOSE. In many instances such research can be incorporated into postgraduate degrees at the Masters and Doctoral levels. This paper discusses types of research that are appropriate, the benefits of applying workplace research for the employee and other stakeholders, and concludes with a step by step process for synergizing workplace research into a postgraduate degree.
9.2.2 Additional Systems Engineering Roles
Authors: Kyler Kenneth R. , McCumber William H. , Sloan Crystal D. 
Published: November 2014

AbstractTo date, the systems engineering roles described focus on those within an engineering firm and ignore the need for a systems engineer who advises, and acts in behalf of, the client separate from the organization building the system. The software systems engineering community has failed the customers by not providing a process for bridging the gulf between the contractor and the customer in an objective manner. The additional systems engineering roles described, that of the Contracting Officer's Technical Representative and the Client's System Engineer, bridge that gulf and improve the integrity of the process. The focus of this paper is on Department of Defense contracts but the prinicple is true for major software systems efforts.
9.2.3 A Sublayer Generation of System Architecture Using the Model Based Systems Engineering Tool
Authors: Lee Joong Yoon , Park Young Won 
Published: November 2014

AbstractThis paper describes a set of practical methods and templates developed to practice the Model Based Systems Engineering (MBSE), a computer‐aided systems engineering, in an efficient manner. It also shows the steps to build more credible data model. The scope of the work includes the systems engineering engine process which represents the requirements analysis, functional analysis/allocation, and synthesis. This work focuses on the functional architecture generation. The SE engine process is tailored to accommodate the specific needs encountered from practical applications of the MBSE. The outcome of the work includes the templates for requirement and scenario description methods essential to construct MBSE database. To ensure the model credibility, the study presents the use of belief criteria.
9.3.2 Vajra Logic and Mathematical Meta‐models for Meta‐systems Engineering
Authors: Palmer Kent D. 
Published: November 2014

AbstractThis paper explains at a high level of abstraction the meaning of the term Vajra Logic as it relates to Diamond Logic and Matrix Logic. It also explains the concept of Meta‐models as an extension related to the concept of Mathematical Model Theory. These ideas were mentioned in the paper “Anti‐terror Meta‐systems Engineering” and this paper seeks to fill in more background as to what is meant by these terms. These ideas are related to Set and Mass mathematical and logical categories and Syllogistic and Pervasion logics. Finally, there is discussion concerning the use of the Gurevich Abstract State Machine Method for the purpose of modeling Turing machines and Universal Turing machines as a way to represent Systems and Meta‐systems for Engineering Design. The foundations of Systems Design Languages are briefly discussed. This is a conceptual working paper of research still in progress and does not represent final results.
9.3.4 Development of the Evolved Seasparrow Missile Under IPD Methodology
Authors: Roe Charles L. 
Published: November 2014

AbstractThe Evolved Seasparrow Missile (ESSM) development has proceeded through engineering and manufacturing development and is now undergoing operational testing prior to being approved for service use. This effort, supported by a consortium of the United States and allied nations, will provide a significant improvement to the existing Sparrow Missile. It will give the fleets of these nations an antimissile capability against existing and projected threats that possess low‐altitude, high velocity, and radical maneuver capabilities that stress present systems. This paper traces the ESSM's development under DOD‐mandated Integrated Product Development (IPD) from early definition efforts through engineering and manufacturing development and into the present operational test and evaluation trials that will prove its capabilities to support consortium fleet missions.
2.3.2 Lessons Learned for Systems Engineering Capability Assessments
Authors: Wray Richard B. 
Published: November 2014

AbstractLockheed Martin Naval Electronics & Surveillance Systems‐Akron (NE&SS) has completed a continuous assessment against the Systems Engineering Capability Model (SECM), EIA/IS‐731. This assessment was conducted in three stages: Quick Look, Incremental and Final. The Quick Look took several days to conduct. The two year Incremental assessment established the processes to assure compliance with them in the organization. The one week Final assessment validated the Level 3+ capability of the organization. Lessons learned at each assessment stage are applicable to all engineering assessments when evaluated against any type of assessment model. This paper summarizes our assessment process and discusses our lessons learned.Setting out to conduct an assessment and improvement process can be confusing, especially for an organization at lower levels of capability maturity. This paper is focused on planning future assessments by organizations with limited prior assessment experience.