bluuebunny/crossref_metadata_2025 huggingface dataset:
6.5.4 SafeAir ‐ An Integrated Development Environment and Methodology
Authors: Goshen‐Meskin ora , Gafni Vered , Winokur Michael
Published: November 2014

SafeAir (http://www.safeair.org) is a European Commission project that has been submitted under the 5th framework program. Within the framework of SafeAir an Avionic System Development Environment (ASDE) will be developed and evaluated. ASDE will implement technologies, methods and tools that meet the high dependability needs of real time embedded systems. Once natural language requirements are in place, ASDE will support system and software property specifications on the basis of formal, readable, graphical notations. Notation will be based on block‐diagrams, activity‐charts and state‐charts, both at the analysis and design phase. ASDE will integrate defacto standard modelling tools (Statemate, MATLAB, Sildex, and SCADE) for complex embedded system applications. Thus, ASDE will provide a seamless process path from system‐level modelling tools to an automatic code generation tool in compliance with the DO‐178B certification standard [1] for critical airborne embedded systems. ASDE will significantly raise the degree of early error detection and reduce the validation effort during system integration time utilizing formal verification techniques for the verification of system critical properties.

The key concepts for these improvements are a model based design process, formal verification, automatic code generation and automatic code validation.
7.5.1 Appraisal using the Federal Aviation Administration's Integrated Capability Maturity Model® (FAA‐iCMM®)
Authors: LaBruyere Larry
Published: November 2014

The Federal Aviation Administration (FAA) has been improving its processes for several years. As part of this process improvement effort they recently completed an appraisal of eleven programs representing the full systems engineering and acquisition lifecycle, against the FAA's Integrated Capability Maturity Model® (FAA‐iCMM®). This paper describes the method used and identifies lessons learned.
7.5.3 Capability Assessments – Worth the Trouble?
Authors: Olesnicky Roman
Published: November 2014

Formal capability assessment is increasingly viewed by many as an essential element of a structured business improvement program, but many organisations are reluctant to take that first step because of perceptions of expense and complexity, and uncertainty of the value of the overall process. This paper recounts the experiences of the Author's organisation in its first foray into the world of formal Capability Assessment as part of the CMMI1 pilot program. It recounts the process, records the resources applied, lessons learned, and “even better ifs” with a view to aiding that decision process for organisations that may be contemplating embarking on such a path.
1.6.1 Object Modelling for the Management of Narrow Passageways in Transportation Systems
Authors: Lagakos Vasilios , Kaisar Evangelos I. , Austin Mark
Published: November 2014

Within the transportation network arena, narrow passageways occur where the width of a transportation link is insufficient to permit operation of two‐way traffic at normal speeds of operation. As a result, traffic congestion, accidents, and costly delays are common problems. The effective management of these systems is needed to mitigate the undesirable impact of these bottlenecks on system safety, performance and cost. In an effort to address the significant challenges associated with the analysis, design, and implementation of appropriate management operations for narrow passageways, this paper attempts to develop an object‐based model for the management of narrow passageway problems in transportation systems. The object model is formulated in two steps. First, we identify high‐level management functionality, objects, and associated data/information sources that are common to all narrow passageway applications. In the second step, functionality of the object model is customized to the specific needs of the narrow passageway application domain (e.g., waterways).
2.6.2 A Family of Systems Collaborative Engineering Environment
Authors: Crisp Harry , Lake Jerome G.
Published: November 2014

This paper describes the Naval Collaborative Engineering Environment (CEE) being developed to facilitate data/information exchange and collaboration among engineers, scientists, users, and managers at multiple distributed geographic locations for the purpose of family‐of‐systems interoperability engineering. A description of the envisioned open systems, standards based infrastructure of communications, data processing and resource management services is included, as well as how the Naval CEE will be used within the US Naval Force Systems Engineering Process.
2.6.3 The Next Venue for Systems Engineering
Authors: Ring Jack
Published: November 2014

In the hypercompetitive era customers will not want to buy your products. However, they will pay extra for improvements to their existing system(s). The purpose of this paper is to explain this difference in customer behavior and what it signals regarding expanded career opportunities for systems engineering practitioners. This paper describes hypercompetition, identifies the major stimuli that system engineering practitioners must honor and identifies the resultant capabilities and behaviors required for success. Customers include government, business and civil sector. Capability improvements include ten fold gains in intelligence, cycle times, quality and return on resources. Participation is voluntary but anyone not learning to practice these new types of relationships and behaviors likely will be relegated to the hypocompetition pile.
6.6.2 Market Survey ‐ Commercial Reliability, Availability and Maintainability Engineering Software
Authors: Filliol Nathalie , Stäritz Joachim
Published: November 2014

In aerospace projects increased reliability, availability and maintainability (RAM) is an important contribution to the reduction of the technical and financial risks. So called RAM Engineering software makes it easier to perform such analyses, particularly in early development phases.

The objective of this work is the investigation of commercially available tools (e.g. AvSim+, OpSSim, RAPTOR, Relex, …) for the application at the European Aeronautic Defence and Space Company. The tool should be adapted to the specific requirement of future users.

The requirements for a RAM Engineering Tool are expressed in KO‐Criteria, Criteria and their corresponding weighting factors Altogether 13 RAM Engineering software, which are available on the market, were analyzed. Information about the products was collected, in order to conduct a qualitative comparison of their abilities. After a preselection nine products were tested on the basis of an example system and afterwards evaluated regarding the determined criteria and their weighting factors.

The investigation suggests that the market does not offer an optimal tool for all applications at EADS, but each tool has its strengths and weaknesses. The result of the evaluation determines the software, which offers the best compromise for the calculation of the reliability and the inherent and achieved availability. However different tools are recommended for special applications like the calculation of the mission reliability or the operational availability.
6.6.3 The Application of the Learning Cycle in the Royal Australian Navy Class Logistics Offices
Authors: Tyndall Moya , Whitehouse Tom , Woolley Anthony , Turner Ben
Published: November 2014

An overview of the research and development task established to demonstrate the feasibility of applying numerical tools (based on modelling and simulation) to Royal Australian Navy (RAN) capability management is given. Our focus in this task is on the materiel support aspects of the capability management process that are the responsibility of the RAN Class Logistics Offices in the Defence Materiel Organisation. For example, assistance is required in making decisions in resources allocation, maintenance scheduling, spares optimisation and obsolescence management. A learning cycle, which has its foundation in systems thinking and systems engineering, is introduced in this paper as a mechanism for continuous improvement and informed decision making. Tools and techniques that can be used to assist the activities in the learning cycle are described with appropriate examples. These tools and techniques include statistical analysis, knowledge discovery in databases, decision‐making techniques, systems modelling and risk assessment. Also, some conclusions and future directions for this research program are presented.
7.6.3 The Importance of the Business Context to System Boundary Definition – A Case Study or Two
Authors: Jeffrey
Published: November 2014

This paper provides two illustrations of recent projects where an appreciation of the true impact of a new and expensive integrated system upon the wider organisation was not considered until well into system design and in one case at prototype delivery. The case studies provide an operational context and support for investment in development of the operational concept prior to system design. Furthermore, the case studies emphasize that a developed operational concept in the form of mission scenarios or use cases provide an invaluable tool for design validation in an agreed operational/user context.
5.7.3 Impact of Shared Data Environment – Enterprise Integration (SDE‐EI) on Systems Engineering
Authors: Meakin Brian , Kemp Duncan
Published: November 2014

This paper describes the impact that improved Enterprise Integration (EI) through the use of Shared Data Environments (SDE) can bring to Systems Engineering (SE).

Picking up on the Symposium theme of ‘Innovate, Integrate and Invigorate’ the paper decribes the areas where EI will enable and strengthen SE during the Product Life Cycle and across the Supply Chain.

It focusses on the organisational and cultural impacts of EI initiatives currently taking place in ‘live’ Pilot projects across major UK MOD/Industry Programmes and how this both enables and enhances ‘Best Practice’ Systems Engineering.

In addition to the benefits EI can bring to SE the authors have been successful in applying a Systems Engineering approach to implementing their respective EI projects. The paper records their key findings.
6.7.1 Program to Identify Potential Ambiguities in Requirements Written in English
Authors: Bellagamba Laurence
Published: November 2014

Methods to find ambiguities in requirements written in English are discussed. The most effective methods involve conversations between the system recipient and provider. A program written in Mathematica to facilitate initiating such conversations is described. Example outputs from the program are shown.
6.7.2 Innovation and Soft Systems Engineering
Authors: Stajnko Frank , Doukas* Louis
Published: November 2014

Innovation is the way that a business system turns its vision and foresight into reality. Unfortunately it can also be complex and limitless in its application and scope. This means that there is a great risk that you can charge off in the wrong direction, hence wasting considerable resources on the way and quite possibly causing significant and terminal failure. Strategy making and Soft Systems Engineering are critical in helping to aim the innovation effort in the right direction, such that resource deployment is optimised and the chances of success greatly improved. It must be noted that effective strategy making depends on the accurate forecasting and anticipation of change, which is difficult at the best of times. Be that as it may, it still remains the only way to tackle long range, significant and radical innovation. Tactical approaches are really only appropriate for minor and incremental innovation.
6.7.4 XMInt: An XML Mediated Integration Model
Authors: Mukviboonchai Suvimol , Chirathamjaree Chaiyaporn
Published: November 2014

To interoperate data sources that differ structurally and semantically particular problems occur, for example, problems of changing schema in data sources will affect the integrated schema. In this paper, conflict between heterogeneous systems is investigated and existing approaches to integration are reviewed. We propose XMInt, an XML Mediated Integration model which employs mediation and wrapping techniques as the main components for the integration of databases and legacy systems. With XMInt, a mediator acts as an intermediate medium transforming queries to sub‐queries, integrating result data and resolving conflicts. Wrappers then transform sub‐queries to specific local queries so that each local system is able to understand the queries. This framework is currently being developed to make the integration process more widely accessible by using standard tools. An initial prototype is included to demonstrate the model.
7.7.3 Integrating COTS products into a Maritime Reconnaissance System
Authors: Velagapudi Sunil , Chapman Tim T. , Voytko Mary , McMahon John A.
Published: November 2014

Military programs are increasingly procuring Commercial Off‐The‐Shelf (COTS)‐based products to decrease the program costs and time to delivery by leveraging on integration of mature, Research and Development (R&D) products.

Some of the assumptions are: 1) one doesn't have to pay for R&D, 2) COTS products plug and play and 3) products are easily adapted to different platforms.

Whilst savings with respect to R&D costs are not addressed in this paper, the plug & play and adaptation aspects merit discussion, especially when integrating smart and complex COTS products. COTS products do not eliminate systems engineering effort; they can increase the amount of effort required.

This technical paper will present some of the challenges, the solutions, and lessons learned in integrating COTS products on United Kingdom (UK) Ministry of Defence (MoD) Nimrod Maritime Reconnaissance Aircraft 4 (MRA4) program. In addition, strategies are proposed that may be used by other COTS‐based programs.
9.1.3 Q‐Analysis: A possible addition to the SE Toolbox
Authors: Hansell Alex , Vance Kim
Published: November 2014

A key problem of systems engineering is how to break down a system into its principal subsystems or components and their interfaces. The traditional approach relies on intuition & past experience, both are heavily influenced by the conventional taxonomy of academic disciplines (mechanics, aerodynamics, electronics, economics, etc). This intuitive approach is being supplemented by emerging disciplines (risk analysis, environmental concerns, ergonomics, etc). Increasingly it is being found that traditional approaches no longer satisfy modern holistic aspirations. The problems are too diverse whilst being increasingly tightly coupled. An effective multidisciplinary approach is required. This paper discusses the application of Q‐analysis to the problem of identifying subsystems & interfaces.
9.1.5 Using distributed database queries and composable mediators to support requirements analysis
Authors: Sutinen Krister , Katchaounov Timour , Malmqvist Johan
Published: November 2014

Requirements analysis in a modern development environment needs to take into account product information at all stages of development. An integrated product model is used to describe the data used through the development process in form of different kinds of models and to capture the relationships between them. Due to its diverse nature, this information is usually stored in distributed and heterogeneous information systems. To support the task of requirements analysis, a distributed data integration architecture called composable mediators is proposed. Composable mediators are a multidatabase system consisting of distributed autonomous object oriented (OO) mediator servers defined in terms of other mediator servers. The complexity of the information model describing requirements data is addressed by the use of OO queries. The distribution and diversity of the data involved is addressed by accessing it through a distributed mediator system. This approach allows not only all related distributed data to be accessible in a timely manner without any changes to existing systems, but also for new information to be extracted from the available product requirements related data.
1.1.4 The ‘Learn from Experience’ (LfE) journey in Systems Engineering
Authors: Meakin Brian , Wilkinson Brian
Published: November 2014

This paper describes how ‘Learning from Experience’ (LfE) encompasses and pervades the popular domain of interest ‘Knowledge Management’ (KM) throughout the life cycle of a project. This paper is NOT about KM. It is about the development, retention and re‐use of tacit knowledge or wisdom. If KM captures the explicit Knowledge that can be captured and extracted from databases, then LfE adds to this the tacit knowledge [or wisdom] of those who have ‘been there and done it‘. By combining explicit and tacit knowledge we have the better of two worlds coexisting together in a self‐learning and self‐sustaining process.

As Systems Engineering can be expressed as a Socio‐Technical activity it is appropriate that Systems Engineers utilise LfE to inform the Enterprise, project and the personal knowledge base as early as possible in the project life to ensure the chosen system solutions are those with the best opportunity for success. LfE is generic and is just as appropriate for a non‐engineering enterprises, for example a Banking Institution.
2.1.1 Systems Engineering Realization of a Market Model
Authors: Genz Bodo
Published: November 2014

This 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

This 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

At 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

RAFAEL 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

Implementing 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

Maintenance 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

While 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

This 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

SE (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

This 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

The 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

Recently, 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

Who 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

A 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

The 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

Risk 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

Software 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

This 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

Many 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

To 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

This 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

This 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

The 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

Lockheed 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.
2.3.3 Measurement For Small Projects
Authors: Baxter Donald F.
Published: November 2014

After several years of leading successful systems projects, you are now tasked to assemble a small team to address a design problem with a component of the major weapon system developed by your company and to report your findings and recommendations in two months. This is a classic assignment for a small project … limited duration, small group, and specific task. While you might think this is an opportunity to fall under the radar of the corporate reporting and measurement program, you're missing out if you don't take advantage of the unique opportunity to experience and explore the possibilities available to you through working on a small project and the opportunities for understanding measurement in ways that just aren't possible on larger programs. This paper explores the world of measurement in small projects.
2.3.4 Experience with Extending CMMISM for Safety Related Applications
Authors: Bofinger Mark , Robinson Neil , Lindsay Peter , Spiers Mick , Ashford Matt , Pitman Adrian
Published: November 2014

+SAFE, a safety extension to the Capability Maturity Model ‐ Integrated (CMMI) has been developed and trialed in Australia, for use in assessing suppliers of safety‐related systems. This paper describes the latest version of the safety extension and also reports on the results of seven trials.
3.3.4 Requirements Variability Management
Authors: Jorgensen Raymond W.
Published: November 2014

When a project is “reused” from an initial project to subsequent reapplications of the original project, the question of management of the intellectual property between projects becomes a significant maintenance issue. When intellectual property is copied from one project space and pasted into the next project space, the intellectual property (IP) between the two projects is no longer directly shared (it's rather salvaged), and the IP between the two projects will tend to diverge. Enhancements or variations that are introduced into that IP will not be managed as a product family, but rather be managed as project specific IP. Any global updates needed across all projects then become difficult and costly to understand and apply. One change must be re‐created in each project sharing the same product definition. True sharing or reuse of IP between the projects becomes difficult.

To truly share IP between two or more projects, the IP material must come from the same source (not different copies). Sharing IP between projects encourages a product family approach to engineering. The fear, though, of shared IP is a perception that the project will no longer be able to preserve their project's unique definition or unique needs. They are “different from the original project”, thus they must maintain their own IP. And sharing other project data with their unique customer bias is out of the question.
4.3.5 A Question of Context – Why Manufacturing Cultures Don't Understand Systems Engineering
Authors: Iliff Randall C.
Published: November 2014

Effective management of Systems Engineering requires expertise not only within the discipline, but expertise in explaining the discipline as well. This is particularly critical in the commercial sector, whose management is overwhelmingly rooted in manufacturing process and culture. Manufacturing is an important and essential skill set, but it is fundamentally different than the creative process of Systems Engineering. Bridging the communication gap is essential to establishing even an opportunity to perform effective Systems Engineering. This paper equips the reader with a clear understanding of the challenge, and the insight needed to become an informed and effective Systems Engineering advocate.
1.4.1 Application of Systems Engineering Principles In The Creation of a New Master of Science In Systems Engineering Degree Program
Authors: Harwell Richard M.
Published: November 2014

A university accepts the challenge to create a new Master of Science curriculum needed by industry. Industry declares a major shortfall in knowledgeable systems engineers and an inability to knowingly identify the capabilities of those practitioners that are available. Add to that mixture, a professional base that is still debating how to define itself and the boundaries that govern its practice. These are just some of the elements faced by Southern Polytechnic State University and Lockheed Martin Aeronautics Company (both based in Marietta, Georgia) in developing a joint Certificate Program and a Master of Science in Systems Engineering Degree Program. And these concerns do not take into account other issues that every new curriculum faces.
1.4.4 Combined Research and Curriculum Development in Information‐Centric Systems Engineering
Authors: Austin Mark A. , Baras John S. , Kositsyna Natalya I.
Published: November 2014

This paper describes a multidisciplinary program of research and curriculum development in Information‐Centric Systems Engineering currently underway at the Institute for Systems Research, University of Maryland, College Park. This work is supported by a significant grant from the National Science Foundation and industrial funds from US industry. After motivating the need for an information‐centric approach to systems engineering education, this paper describes the research methodology, pathway from research to curriculum development and teaching, and architecture for web‐based project deliverables.
2.4.2 New Approach to Generic Attributes
Authors: Wells Curt , Ibrahim Linda , LaBruyere Larry
Published: November 2014

Generic Attributes (GAs) are measures of process performance introduced by the systems engineering capability model, EIA/IS 731. The systems model defines two GAs – Effectiveness and Value. While the concept of GAs is generally accepted as valid, they have been used very little, due to difficulties in interpretation and appraisal.

Revised definitions and a new approach for appraising and using GAs have been developed for the Federal Aviation Administration Integrated Capability Maturity Model® v2.0 (FAA‐iCMM®). The improved approach to Generic Attributes provides the needed clarity and measurement objectivity. Definitions of the iCMM GAs and their relationship to process model concepts are described, along with a practical approach to appraising GAs.
2.4.3 Verification “Auditability” can be “Free”
Authors: Jones James H.
Published: November 2014

When simple audit support standards are applied to developing project requirements verification documentation in the current new product development environment, several benefits accrue. Data then made available from the verification documentation supports technical test reviews and an effective project status metric, as well as rigorously proving that verification is complete for specified requirements. Essential to verify requirements for systems affecting human safety, audit support standards enabled rigor could be useful during planning and testing to assure quality under ISO 9001 parameters claimed as met by many companies. When methods described in this paper virtually automate the resulting auditability, it essentially becomes “free“.