bluuebunny/crossref_metadata_2025 huggingface dataset:
SYSTEM INTEGRATION LABORATORY ‐ A NEW APPROACH TO SOFTWARE/ELECTRONICS SYSTEM INTEGRATION
Authors: Huang Paul , Kar Pradip , Kennedy Alan , Kato Hiroko
Published: November 2014

This paper describes the system definition and integration approach adopted for the Bradley Fighting Vehicle (BFV) M2A3 Engineering and Manufacturing Development (EMD) program at United Defense LP. The BFV A3 Upgrade program incorporates lessons learned in the Desert Storm Operation. Upgrades are primarily in the area of fire control, electronics and software.

Modern electronics and software systems are relatively complex. Subsystems have to be integrated so that they perform cohesively to implement sophisticated system functions with minimal supervision from human operators. This cohesive implementation, or system integration, requires special discipline, knowhow, facility, and organization. This paper describes a systems engineering approach that allows an understanding of the system early in the program, identifies problem areas and generates candidate solutions before commencement of system design. It also describes the advantages of this approach.

The approach described was used on the BFV A3 program. A System Integration Laboratory (SIL) was constructed and a rapid prototyping methodology was adopted to generate a simulation, emulation, and stimulation (SES) early in the program to allow for a better understanding of the overall system. The SIL also created an incremental integration environment that allowed the system to be integrated using the philosophy of “build‐a‐little, test‐a‐little, and integrate‐a‐little” to simplify the integration tasks and reduce program risk.
FOUNDATIONS OF SYSTEMS ENGINEERING ETHICS
Authors: Alessi R. Sam , Gokey John R. , Mayhew Michael E. , Walden David D.
Published: November 2014

INCOSE has stated the need to develop standards for the integrity of Systems Engineering. Part of what defines this integrity will involve ethics. This paper provides background information to support a search for ethics peculiar to Systems Engineering. Presented are a rationale for considering ethics, the role and responsibility of professional societies to state ethical standards, a historical and theoretical perspective and requirements for development of a Systems Engineering ethics code. An ethics discussion within INCOSE will likely produce tools, such as a code, which distinguish Systems Engineering's role and responsibilities for ethical design and management of complex systems that minimize unintended harmful behavior.
INTERNATIONAL SPACE STATION PERFORMANCE METRICS
Authors: Rice Alvin F.
Published: November 2014

Boeing, as the Prime Contractor for the International Space Station (ISS), has a system of Metrics to manage the Prime Contractor portion of the program. The system of metrics and processes provide programmatic and technical type parameters to measure the status and progress of the Prime Contract and provide early warning indicators of performance problems.

The metrics are generated and used as a management tool by the Prime Contractor and Product Group Integrated Product Teams (IPTs) and Analysis Integration Teams (AITs) for all phases of the program. The system of metrics are applicable to program hardware, software, firmware, support equipment and supporting services. The Space Station IPTs and AITs are made up of NASA and Prime Contractor participants. The metrics are an integrated part of the Management Control System and are used for reporting at weekly, monthly, quarterly and special event reviews. These metrics provide a means to assess and display the health of the program at various IPT and AIT levels.
A COST OF OWNERSHIP METRIC AND ITS USE ‐ A PLACE TO START
Authors: Stark George E.
Published: November 2014

At a time when Government budget cuts are in vogue and increased military readiness is the goal, knowledge of system cost of ownership is essential for decision‐makers and system engineers. As with many aspects of our economy, costs associated with operating and maintaining our C4I systems continue to climb. Understanding and correctly using a cost of ownership metric can direct attention to problem areas, help prioritize changes to the system, and track the impact of system improvements over time. This paper introduces the reader to the rationale and intended use for one approach to measuring the cost of ownership for a space surveillance radar system. The intent is to provide a starting point for learning more about the subject. By using such a metric, it will become possible to achieve the goal of increasing mission success for less cost.
PROJECT MANAGEMENT AND SYSTEMS ENGINEERING IN AN IPD ENVIRONMENT
Authors: Roe Charles L.
Published: November 2014

Integrated Product Development is a creative new way to produce quality products in a predetermined time within a set cost. The focus is on multifunctional teams working together and total integration of all products and processes (people, tools, and techniques). Within the team structure several potential pitfalls exist that can threaten the process. This paper suggests that two of the critical pitfalls involve (1) the project manager effectively executing new responsibilities that fall to him or her in the process and (2) the organization overcoming the difficulties of applying the systems engineering methodology to the products being developed by these concurrent teams.
EXPERIENCE WITH THE SYSTEMS SECURITY ENGINEERING CAPABILITY MATURITY MODEL
Authors: Hefner Rick , Monroe Warren , Hsiao David
Published: November 2014

The Systems Security Engineering Capability Maturity Model (SSE‐CMM) is a tool for appraising and improving an organization's security engineering practices, and for augmenting existing assurance methods. The SSE‐CMM was developed through a government‐industry collaboration involving the nation's leading providers of security systems, products, and services. It does not specify how a particular process should be performed, but identifies practices generally accepted by industry. The SSE‐CMM can also be used to examine the practice of security engineering within the context of systems engineering.

This paper describes the principles upon which the SSE‐CMM is based, the structure of the model, and its use in appraisals. Issues in model development, application, and adoption are presented.
Quantitative QFD for System Engineering
Authors: Maier Mark W.
Published: November 2014

Quantitative QFD (Q2FD) is an extension of conventional Quality Function Deployment (QFD). Q2FD incorporates quantitative requirements decomposition models into the QFD framework. It also rearranges conventional QFD matrices to facilitate quantitative capture and both forward and backward chaining of performance values. The rearranged matrices also allows full representation of QFD matrices with standard spreadsheets instead of only with special purpose software. Q2FD can serve as a bridge between quality, system, and disciplinary engineering personnel and act as an organizing formalism for all performance aspects of system design.
Measuring Systems Engineering Process Maturity
Authors: Pierson Harold
Published: November 2014

Many Systems Engineering organizations are beginning to examine their engineering processes as a means of improving their competitiveness. There are now process maturity models which serve as process frameworks and provide a yardstick for measuring Systems Engineering process maturity. These models define what activities must be performed and a scale for judging how well they are performed. Appraisal methods are available for evaluating an organization's process maturity. This paper discusses the importance of measuring Systems Engineering process maturity and gives an overview of two Systems Engineering process maturity models.
PROVIDING A FRAMEWORK FOR EFFECTIVE SOFTWARE QUALITY MEASUREMENT: MAKING A SCIENCE OF RISK ASSESSMENT
Authors: Martin Robert A. , Shafer Lawrence H.
Published: November 2014

Software quality assessment is a field that is coming into greater focus as the global drive for systemic quality assurance continues to gather momentum. Many forces are at play, from the pressures of consolidations, mergers, and downsizing, to the emergence of new technologies which are sparking renewed looks at re‐engineering in business and government, particularly the advances in user interface capabilities endemic to the PC and distributed processing economic explosions. These developments and forces have led to our creation of a quality assessment methodology which harnesses the results of program analysis techniques to generate a timely analysis that can be productively used to focus management attention on the fundamental quality issues within their software systems. This approach has been used successfully for more than 75 system evaluations as part of source selection or project management studies.
NAVY LEGACY SYSTEMS REENGINEERING
Authors: Wilson Mark L.
Published: November 2014

Legacy systems abound in the Navy. In many cases it is infeasible or ill advised to develop new systems from scratch. Yet due to new system requirements, increasing maintenance costs, or other reasons it is desirable to somehow replace or upgrade these systems. There is also a desire to capture some of the capabilities inherent in these systems and somehow reuse them. This paper looks at some of the issues involved reengineering, and in particular those that tend to be unique to or more pronounced in Navy systems. It also briefly describes some progress that has been made using language translation to facilitate reengineering of Navy systems to open architectures.
Discovery & The Change Control Process
Authors: Oliver David W.
Published: November 2014

This paper describes the change control process that is essential for engineering projects to cope with requirements changes imposed from outside the program and to cope with the internal discovery of issues that require the engineering work be altered.

The engineering life cycle has been described in the literature by a waterfall model, which emphasizes top down development, and a spiral model, which emphasizes prototyping. Engineering developments in the real world follow neither of these models. In the real applications world the engineering work follows a nominal forward process which can be described rigorously with models, (Oliver 1994a).

One step of that rigorous process considers multiple product releases, risk remediation, and partial builds for early validation testing. Prototypes are built to a schedule to meet these project needs

In real applications the forward process is never followed without interruption. Customers discover that requirements must change, engineers discover technical problems, and management discovers need for funding and schedule changes. These changes can cause the engineering work to be interrupted at any step of the forward process and to be resumed at any other step of the forward process. Since the work is interrupted at any step and may resume at any other step, these impacts cannot be described in a work flow diagram because it would show recursion from every point back to every other point.

The real engineering work conditions can be rigorously described with a forward process combined with a change process, (Oliver 1994b). The change process provides for identification of the need for change, change impact assessment, change authorization, change planning, change execution, and process improvement based on analysis of change causes.
1 EVALUATION IN THE SEDRES PROJECT: Measuring the Effectiveness of Model Data Exchange between System Engineering Tools: Ninth Annual International Symposium of the International Council On Systems Engineering (INCOSE) June 6–10, 1999
Authors: Harris David , Candy Linda
Published: November 2014

The System Engineering Data Representation and Exchange Standardisation (SEDRES) Project is a European initiative towards the development of a standardised data exchange capability for use between the different tools used in System Engineering. A significant issue arising from the Project is the usability of such a data transfer capability, and its effectiveness in the System Engineering process, especially in its application in the support of Integrated Product Teams. This paper addresses the Test & Evaluation programme within SEDRES and its focus on the Usability issues for tool data transfer. It concludes with a comparison of the SEDRES capability with a proposed Integrated System Engineering Environment (ISEE) Model set out in a 1996 INCOSE report (INCOSE 1996).
1 A Plug‐and‐Play Early Validation Module
Authors: Larsen Bob , Buede Dennis
Published: November 2014

In the complex world of developing requirements and eliciting user needs, engineers build billions of dollars of products that are wrong on delivery, because they solved the wrong problem. All technical people need specialized techniques and processes to increase the probability of developing the right products in the future. Everyone discusses the importance of getting the stakeholder involved, but the present techniques do little to address this problem. Presently, validation is the stakeholder's only mechanism to test that the developer is building the right product. Validation is the process of testing for technical appropriateness and adequacy near the end of the system life cycle process. An Early Validation (EaVa) module will stablize the problem statement, which will enhance the probability of technical appropriateness and adequacy. EaVa can be used continuously, developing requirements, or for the preliminary design phase depending on the system and the stakeholder's needs. EaVa tries to ensure the engineers are solving the right problem prior to the majority of the resources being committed late in the design phase. A critical piece is getting user feedback, based on this EV step, from independent agents or engineers within the process.
2 Design Integration “Testing” from Concept to Support
Authors: Blake A. T.
Published: November 2014

The value of modelling and design prototyping in the early phases of the systems engineering life cycle is well understood, as is the use of specialist test facilities for design verification during development and to confirm system behaviour and performance prior to delivery. This paper identifies that significant business advantage can be gained through the integration of these various design evaluation activities. The use of an integrated test and evaluation strategy, supported by a model integration environment, is proposed as a means of achieving this objective. The key concept discussed is that of a “virtual” rig.
2 An Integrated Model for Characterizing & Managing System Architectures
Authors: Steiner Rick
Published: November 2014

The term “architecture” is widely used in systems engineering circles, but the explicit meaning of the term varies considerably from person to person, depending on expertise and viewpoint. A previous paper (Steiner '98) defined the term with respect to system evolvability. This paper attempts to clarify architectural characteristics by defining three orthogonal axes:

Expression (form/function),

Permanence (enduring/transitory), and

Abstraction (abstract/concrete).

Segregating a given architectural concept into these three key areas of concern facilitates a balanced approach to managing system architectural models. It can also logically be extended as a mechanism for clear communication among stakeholders.
3 From research to development: specifying a future command and control system
Authors: Lamers Jessy , Streng Martin
Published: November 2014

We present some experiences obtained with the definition and preliminary design of a new generation command and control system for military applications. We will concentrate on the transfer of research results to development. During this phase, requirements have to be specified for the new system for which it is still hard to envision in detail the desired tasks that it should support. At the same time, the new technologies that are to enable these new capabilities are not known well enough to completely understand their possibilities. We will outline some approaches that, in our project, helped to be creative at the right time and specific and decisive when needed. These are storyboard, natural language and formal methods. We will indicate for each of them at what moment they can be best applied.

Finally, we indicate why any such approach used within a project does not guarantee widespread acceptance of its results by the remaining R&D population.
1 Embedded Systems, The Forgotten Y2K Problem
Authors: Fisher Gerard H.
Published: November 2014

The shortcut of early programmers has become one of the world's worst nightmares. Year 2000 (Y2K) problems exist in the most improbable places, from medical equipment like defibrillators and EEGs to building equipment that determines when it is time for maintenance. The Y2K problem in mainframe software is well known. The problems dealing with the microprocessors embedded in virtually all of our smart equipment is less apparent. This paper discusses the problem, the systems engineering process for identifying and remediating the problems, and some ways to use this remediation to add value to your systems.
2 A Systems Approach to the Year 2000 (Y2k) Issue
Authors: Moore Patrick D R , Fairbairn Allen G
Published: November 2014

Widespread disruption has been predicted for businesses as the sins of programmers in the not too distant past are found out. The long term consequences of using only two digits for the year in date codes and other memory saving techniques are soon to be unavoidably upon us all. PC's and other electronic devices are relatively easy to check out and fix, although many people are still failing to do so. Less easy to track down and deal effectively with are the myriad types and numbers of embedded chips built into the equipment, machinery and control systems that have been installed and used world‐wide over the last twenty years or so. The real Y2k issue for businesses turns out to be contending with the unpredictable consequences of a widespread, common mode failure both within and outside of a company's legal boundaries. The paper describes simple means by which any business can be better prepared in order to withstand the effects of the millennium changeover. Basic systems engineering principles are described that produce the basis for understanding core business processes. A useful technique of dependency modelling can be used to prepare contingency plans and countermeasures. More importantly, the paper shows how vital it is to view a business as part of the greater business “system” of commercial activity – the extended enterprise concept or “system of systems” to which all businesses belong and which is the true focus for the Millennium bug problem.
3 Assessing Emergencies and Making Disaster Recovery Decisions
Authors: Riggs Donald A. , Botten LeRoy H.
Published: November 2014

Emergency situations almost always present unforeseen situations and problems. Thus, effective mobilisation of business continuity and recovery (BC&R) resources surviving an adverse event requires assessment and analysis of the emergency situation to aid in crisis management.

Costs associated with transition to BC&R operations and subsequent return to normal operations are often significant. Use of backup facilities, personnel, and data; and non‐standard operational procedures (including the transition process itself) increases the risk of operational error. Assumption of such risks and costs may be necessary following an adverse event; however, a decision to invoke BC&R operations should be an informed decision made by a designated senior manager.

This paper offers systems engineering‐based methods and practices for facilitating rapid, accurate assessment following an emergency. The decision support tool described facilitates such assessment, provides recommendations for recovery action; and aids in planning, implementing, and approving transition to BC&R operations or restoration of normal operations.
1 R&D in Systems Engineering perspective
Authors: Bol Derk
Published: November 2014

Systems Engineering is a structured and integral approach for the development of complex products and processes. Obtaining the knowledge and mastering new technologies necessary for the development of these products and processes is the subject of Research & Development (R&D).

This article discusses the relationship between the various phases of product life cycle and the different types of R&D activities from a Systems Engineering point of view. It is shown that Systems Engineering helps to:

Clearly position R&D activities in the product life cycle

Make the goals of R&D activities clear for both the customer and the R&D team

Make the development of a new technology an integral part of the overall system development.
2 Whole Life Systems Engineering Research in Academia – a Position Report
Authors: Sydenham Peter H
Published: November 2014

This paper addresses a need for improved research support within the ‘Whole of Life’ aspect of Systems Engineering. A key element in the full profile of a mature Systems Engineering sector is the presence of a suitably supportive academic research activity. By surveying the current global scholarly contributions it is shown that much needs to be done to bring research for this area up to the baseline normally experienced in mature sectors. A short summary of the main Systems Engineering academic research programs that have been reported in USA UK and Australia show that some corrective actions are in place. It is also of interest to learn of the different approaches being used to address this need. Finally, generic recommendations are given that are considered to be needed to assist Whole Life Systems Engineering research support reach the normally expected performance available from academia.
3 Systems Engineering applied to a Research Management Process
Authors: Burdett Stuart , Rawlins Richard
Published: November 2014

This paper describes a process, based on systems engineering principles, that is being used by the UK MoD to select research to meet the changing needs of its existing land combat vehicle fleets and its future combat vehicle‐system procurements. This selection process addresses operational uncertainty, system complexity, international collaboration, changing procurement approaches and yet remains flexible enough to exploit technology opportunities as they arise. The research being managed encompasses system integration, technology development and ‘pure’ technology research.
1 Function Based Design Of Complex, Complicated Systems
Authors: Shell A D
Published: November 2014

The ‘top‐down’ system design process of functional decomposition is increasingly being criticised as simplistic, outmoded, and (in particular) too ‘reductionist’. Its use on large, complex systems is frequently portrayed as naive and impractical. There is much comment on the need to concentrate, instead, on the ‘emergent behaviours’ of systems, and to adopt a ‘holistic’ design approach in which a system solution is ‘evolved’ through a process of system design synthesis.

This paper presents a counter‐argument that top‐down design decomposition can, in fact, be a highly efficient way to produce good (optimal) system solutions .

Many of the fundamentals of function based system design are addressed: the central role of system function in the design process; the characterisation of system complexity and complication; the identification and specification of component requirements; and the determination of optimal design solutions.

An established mathematical theory of systems design, using formal constructs and set‐theory notation, is used as the basis for the presentation of ideas.
2 SYSTEM THEORETIC PORTENTS OF PREDISPOSITION TO SYSTEM FAILURE
Authors: Wymore A. Wayne
Published: November 2014

This paper is the first in what will be a series of papers concerned with system failure traceable to decisions taken at a level of specification above that of bioware/hardware/software components, failure ascribable to faulty requirements and architecture. The style of discourse is informal but the results are based on research in the mathematical, system theoretic foundations of systems engineering wherein rigorous mathematical structures for system requirements and designs have been established: input/output, functional, technology, performance, cost, tradeoff and system test requirements and functional, buildable and implementable system designs generated by these requirements. The results in this paper have been deduced from examples and counterexamples representing instances of the general structure of requirements and system designs. Discussed herein, is predisposition to system failure from the following sources:

Completeness of problem statements.

Simplification of system requirements.

System functional analysis.

Coupling of implementable system designs.
1 A Method for Design and Analysis of Next Generation Aircraft Computer Systems
Authors: Grigg Alan , Audsley Neil , Fletcher Martyn , Wake Allan
Published: November 2014

Next generation aircraft computer systems require a major advance in system design practice and associated methods of analysis compared to even the most modern aircraft systems now in service. As well as the ongoing need to demonstrate predictable, real‐time behaviour for a wide range of safety critical and mission critical applications, a significant improvement in flexibility is required in order to support cost‐effective design‐time and in‐service modifications to the system. The system design and analysis problem is further complicated by a trend towards increasing functional and physical integration. In this paper, we address the temporal aspects of the problem and propose a design/analysis approach based on resource reservation. This supports top‐down development by incorporating only appropriate timing information at each stage of development and defering the use of implementation details until absolutely necessary. At each stage of refinement, the system model supports localised changes with minimal re‐analysis, thus minimising the impact (and associated cost) of such changes.
2 A new approach to marine programmable systems assessment
Authors: Earthy Jonathan , Register Lloyd's
Published: November 2014

Increasing reliance on complex, computer‐assisted systems presents a problem for most maritime stakeholders. The combination of complexity, use of computer hardware and software, and sector practice in the purchase and operation of computer‐based systems leads to a wide range of potential defects which cannot be guarded against by prescriptive standards.

The EC ATOMOS II research project has developed a total system, human‐centred, risk‐based, through life approach to the specification, design, introduction and use of operationally effective and commercially efficient marine systems, including the use of programmable electronic systems (PES). This is presented in a new standard from ISO which will have a far‐reaching effect on the design and operation of marine transport.

The rationale for a new approach to the development, use and assessment of marine PES and a new ISO standard which embodies this rationale are presented. The industrial impact is outlined.
4 The Importance of Animation with UML
Authors: Dockerill Kevin
Published: November 2014

In order to understand the diverse requirements for large complex and highly integrated real time embedded systems, System Engineers have recognised the benefits of representing requirements using graphical notations with animation.

Animation has been used for different aspects of systems, which include control, moding, mechanical, fluid mechanics and algorithms.

Tools have been developed to support each type of system. However, if we wish to fully exploit model based tool notations as part of the System and Software Development then we need an overall design framework for the System.

UML has the potential to describe such a framework using a common notation for both Systems and Software Engineering. The notation supports architecture, behaviour and functional views of the system.

However, experience with animated tools has led to view that UML tools must also be developed to support animation of the design in order to maximise the benefits in adopting UML for the systems and software development of real time embedded systems.

This paper aims to identify the need for animation, through experience within BAe, the need for UML and the role of animation with UML tools.
2 Multinational Requirements Handling
Authors: Smith Craig N. , Dynamics Matra BAe
Published: November 2014

This paper discusses an approach to requirements handling that is based on seeking flexibility and adaptability. It is particularly suitable for multinational programmes which are characterised by differences in requirements.

Several aspects must be considered coherently within a systems engineering approach to provide a solution with sufficient flexibility and adaptability. Firstly, the correct environment is required to remove preconceptions about the solution and discover the underlying need. A joint requirement management process between customer and industry can achieve this, provided requirements are set at the correct level. In turn, this requires that the boundaries of the problem are challenged, particularly the interaction of the system characteristics and the concept of employment. Finally, the whole process will fail without the correct team principles and enlightened communications.
1 Systems Engineering and Information Management ‐ a Local Need in a Global Perspective
Authors: Fossnes Terje
Published: November 2014

This paper addresses several concurrent initiatives within the Royal Norwegian Navy Materiel Command, and how information available world‐wide have been utilised. This includes use of the Systems Engineering tool RDD‐100®, IEEE STD 1220–1994, results from NATO CALS, the SE‐CMM and SWOT analysis. The activities performed affect the Norwegian Navy's New Frigates project as a pilot for new processes and information management. The paper culminates in an integration of the initiatives into an overall interdisciplinary process‐model for future implementation of identified needs with respect to information handling in an Enterprise Resource Planning (ERP) system. Finally some lessons learned from the initiatives are addressed.
2 Integrating Human Factors within Systems Engineering
Authors: Ward George , Harmer Steve
Published: November 2014

The need to re‐focus attention on Human Factors issues in Systems Engineering has recently taken fresh impetus in the UK, as the cost‐effectiveness of the human element in defence system procurement has been reconfirmed as a critical component in achieving fielded system success.

British Aerospace Military Aircraft and Aerostructures (MA&A), in conjunction with the BAe Sowerby Research Centre, has for the past five years been engaged in activities aimed at ensuring that their Systems Engineering process improvement plans take full account of customer driven Human Factors Integration (HFI) requirements. These include the need to identify and manage all aspects of human involvement in the system lifecycle in order to ensure a balanced application of human and machine resources. The overriding aim being to optimise total system cost‐effectiveness.

This paper reports the status of these activities and describes the background to this work, the goals of HFI, the BAe initiatives undertaken and gives a personal view of the way forward to the successful integration of HFI principles into systems engineering.
3 Collaborative Software Process Data Collection: BAe and Roll‐Royce's Experience of Sharing a Measurement Philosophy
Authors: Clark Graham D. , Powell Antony L.
Published: November 2014

As the Aerospace Industry increasingly moves to an environment where the development of its processes and products take place across company boundaries, the need for an understanding of how they will share process and product data is vital. BAe and Rolls‐Royce are collaborating on such an enterprise and this paper reports on a pilot collaboration from an engineering perspective. As a result of exchanging best practice in Software Metrics between BAe MA&A and Rolls‐Royce, a decision was made to begin to use the Process Engineering Language (PEL) across the two companies to gather metrics in a consistent format. The goal was to find out if the same measurement philosophy could be used to assess differing Real Time High Integrity Software development strategies and to see if different working practices produce similar costs and results.
2 Cost effectiveness of formal methods in the development of avionics systems at AEROSPATIALE
Authors: PILARSKI François
Published: November 2014

AEROSPATIALE has been using formal methods since the early 80's to develop part of the embedded systems, and more specifically most of the avionics systems. During the last two decades, such an approach has demonstrated significant cost savings. This paper presents some aspects of this approach and focuses more precisely on the way it has helped in reducing embedded system development and maintenance costs.

This first section of this paper is devoted to a general description of the overall context and it gives some elements of history.

The second section summarizes the benefits AEROSPATIALE has found in using SAO first, and now SCADE, and constitutes an attempt to synthesize the properties and characteristics that make a formal method efficient (at AEROSPATIALE).

The third section summarizes some aspects of formal methods, which have not been extensively used yet but which are likely to induce extra cost reduction, namely proof techniques.
1 Collaborative Methods Applied to the Development And Certification of Complex Aircraft Systems
Authors: Langton Roy , O'Connor Steve , Jones George , DiBella Paul
Published: November 2014

Described are new methods of procurement, development and certification for complex aircraft systems and how these new methods have evolved over the past 15 years.

The traditional methods of system design and equipment procurement that were used in the 1980's by aircraft manufacturers and that had been in place for decades, have undergone major changes following the aerospace recession of the late 80's and early 90's. Almost all of today's primes are procuring equipment at the system level and are requiring a more direct involvement by the supplier community in the design, development, integration, testing and certification of the aircraft as part of the system procurement contract. Furthermore, suppliers are being made accountable for the performance of the system in the field in terms of maintenance cost, equipment removal rates, and dispatchability.

This paper describes the evolution process and some of the different approaches used by the prime community in the procurement of major aircraft systems. Comparisons are made using specific examples of fuel system procurement adopted by different aircraft manufacturers.

Issues and benefits of these new methodologies are discussed and opportunities for improvements for the future are suggested.
3 Developing a Simulator for the Aerospace Extended Enterprise Product Introduction Process
Authors: Mason‐Jones Rachel , Wingrove Stuart , Naim Mohamed , Alexander Ian
Published: November 2014

Industries are keenly aware of the importance of speedy response in ensuring market share not only in the Product Delivery Process but also in the Product Introduction Process (PIP). Even those industries with traditionally long PIP's recognise the need to drive down time to market launch of new products in order to remain competitive. One such industry is aerospace which not only has a very competitive environment but also traditionally long PIP lead‐times. The sheer number of components, and hence companies, involved within the aerospace supply chain adds to complexity of the PIP and subsequent initiative to improve performance. While there is a recognised need to drive down current PIP lead‐times due to the time spans involved there is an increased risk when experimenting with new initiatives and approaches. It is in situations such as these where a business game can be an important supply chain redesign tool. So companies are free to experiment with a variety of new strategies while limiting online risks.

This paper addresses the issue of business games as a media for raising awareness of the systems approach in Supply Chain Management and their subsequent use as design tools for Supply Chain strategies. The paper specifically focuses on the development of a Management Fight Simulator of an aerospace Product Introduction Process within an Extended Enterprise.
2 Lessons Learned in Transitioning to EIA/IS 731 from INCOSE SECAM
Authors: Barber Don E.
Published: November 2014

In 1995, Honeywell's Air Transport Systems division began using the INCOSE Systems Engineering Capability Assessment Model (SECAM) as a tool for facilitating Systems Engineering process improvement. The Key Focus Areas of the SECAM were used as a template for organizing the division's standard Systems Engineering process and Systems Engineering Capability Assessments were conducted to measure the completeness and effectiveness of this process. In 1998, the Electronic Industry Alliance released EIA/IS 731, the Systems Engineering Capability Model (SECM). Honeywell made the decision to transition to this new standard and conducted a Systems Engineering Capability Assessment using EIA/IS 731. This paper describes the similarities and differences between the two models from the perspective of the user, as well as, the lessons learned in executing the transition.
3 CMMI and Systems Engineering
Authors: Clouse Aaron , Schoening William W. , Graffius Joseph , Wells Curt
Published: November 2014

In late 1999 the systems engineering community will be presented with a new process maturity model produced by the Capability Maturity Model Integration (CMMI) project. The immediate significance to systems engineers is that the new model offers, for the first time, strong integration and consistency with the Software CMM (SW‐CMM v2). Organizations can choose to use one or more of several highly integrated models – a Systems Engineering CMM, a Software CMM and a Systems + Software CMM.

Organizations can further choose to use a continuous or a staged version of each model and be assured of equivalent content. This paper describes the relationship of the new CMMI models to the recently completed EIA/IS 731, Systems Engineering Capability Model, and the potential impacts to systems engineering process appraisal and improvement. An overview of the CMMI models and terminology is provided as a basis for describing the relation to the EIA/IS 731
2 Introducing and Maintaining Systems Engineering in a Medium Sized Company
Authors: Hamann Robbert J. , van Leeuwen Wim
Published: November 2014

This paper describes the introduction of Systems Engineering at a medium sized company and the organisation set up to maintain this capability afterwards. The paper explains the context leading to the introduction and describes the steps taken to formally introduce Systems Engineering. It shows the relation between the organisation of the company and the way elements of the Systems Engineering process are formalised. The paper stresses the necessity that any change in the engineering practices should be shown to fit into the engineering process that is in place and to improve it, and needs a firm backing from senior engineers to be applied. Also, continuous training and review is necessary to keep application of the processes alive.
1 RAMSAAT – Systems Engineering Modeling and Simulation Aid
Authors: Newland Ronald K. , Conroy Joseph L.
Published: November 2014

RAMSAAT (Rapid Airspace Management Siting and Analysis Tool) is a systems engineering design and analysis tool for air space management systems (AMS). It provides a highly mobile, laptop based means for AMS Systems Engineers to work with customers (acquirers) to evolve system specific requirements and characteristics. The Systems Engineer can work with any customer and Program Managers to geographically site the AMS system per customer description. This enables analysis of the customers up front requirements for the sensors and associated communications. Within this paper insight is provided into the use of RAMSAAT to enhance the engineering process in regards to requirements analysis and validation. It is also shown how RAMSAAT assists with meeting the standards for requirements definition as outlined in EIA 632, “Process for Engineering a System”.
2 Model Driven Development: Practices and Tools
Authors: Haskins Cecilia
Published: November 2014

Model‐based software engineering is a reality whose time has come. This paper points out ways in which automated software generation from models can be accomplished and yield superior results to traditional methods without taking the human out of the cycle. This paper illustrates the importance of integrating tools with practice.
3 Team Efficiencies Within a Model‐Driven Design Process
Authors: Koenig Lynda J. , Smith David B. , Wall Stephen D.
Published: November 2014

(Smith & Koenig 1998) formulated a model‐based design process describing a triad of people, process, and technology (PPT) within an aerospace culture. It suggested that the time required for an organization to change to a new approach is a function of a minimum development time and powerful forces acting in tension (Lewin 1951).

(Wall et al. 1999) described the object model‐based system, addressed the team dynamics involved in developing the products of the process, and proposed metrics to assess productivity of each team.

This paper examines the PPT triad at the lowest level, the minimum product cycle time. It shows that team interventions, above and beyond team productivity considerations, can produce even lower product cycle times.

A model shows the effect of the three components of the triad acting together. The lower cycle times possible are a product of team effects and technology advances in producing an individual object.
2 System Issues Related to Implementing on the Internet
Authors: Mackey William , Bagg Thomas C.
Published: November 2014

Implementing capabilities on the World Wide Web should never be taken lightly. A good systems engineer is able to examine such implementations from all points of view, including political, legal, security, access, technical deployment, and quality.

The evaluation discussed in this paper was conducted to ensure that the National Aeronautics and Space Administration (NASA) was proceeding in a correct direction by implementing RECALL a Lessons Learned System on the Web and, subsequently, did so successfully. The systems approach extended well beyond technical implementation to several issues that are not often addressed by an implementation team. The resulting evaluation increased the team's sensitivity to such issues and, in fact, the authors believe that the evaluation provided as much benefit as the system itself.
1 Process Assessment Framework – An Integral Part of Safety Assessment
Authors: Burke M.
Published: November 2014

This paper examines the importance of the processes used to produce engineered artifacts for safety critical computing systems.

The integration of direct evidence about the system with supporting process related evidence is the basis of all safety cases. The process of assessing the acceptability of such cases is based on Engineering Judgement. Engineering Judgement is inherently conservative and appeals to precedent systems or analogous systems where possible. Faced with genuinely new technology or new uses of existing technology the Engineering Judgement can appear to be totally subjective.

This paper examines the underlying approaches taken by Engineers to define exactly what level of risk is “tolerable” in the absence of historical precedent.

A general approach is common across a wide range of engineering disciplines. The adaptation of lessons learnt from mature disciplines (e.g. mechanical engineering) to relatively new and immature disciplines (e.g. Computing Systems Engineering) are of particular interest.

This paper considers how general engineering principles can be applied to support the integration of Commercial Off The Shelf (COTS) components and systems for modern aerospace related products
3 Software Engineering and Systems Engineering in DoD
Authors: Zettervall Brenda T.
Published: November 2014

As the Department of Defense (DoD) moves toward acquisition without rigid DoD standards, acquisition is becoming less an issue of hardware vs. software or software engineering vs. systems engineering – it is becoming an integrated whole. New DoD directives, an integrated Capability Maturity Model, highly trained acquisition personnel, and a partnership with industry to manage risk will help us meet the challenges of acquisition in the next century.
1 Enterprise‐wide Requirements & Decision Management
Authors: DeGregorio Gary
Published: November 2014

Decision‐making is one of the most fundamental processes contributing to a corporation's success, yet in many companies, decisions are often characterized as ad‐hoc events without a clear linkage to supporting information, tradeoff studies, or clearly stated rationale. Furthermore, the “information” used to support these decisions is often in the form of complex, unstructured documents which lack clear linkages between their content. As a result, future decision‐makers are often not able to benefit from the collective experiences of their predecessors. Consequently, there are no cycles of learning and the same mistakes are often repeated each time that a similar decision is made. It is clear that the most successful companies in the future will be those who can effectively manage and leverage the “intellectual capital” generated by the decision making process (the thinking engine of systems engineering) and the linkage of that process to essential supporting information. This paper describes an approach to address the deficiencies in the prevailing methods for requirements and decision management by proposing an enterprise‐wide approach which provides for a true “learning organization” capability in the form of reusable decisions frameworks.
2 Effective Decision Making in the Product Introduction Process: A Supply Chain View
Authors: Naylor Ben , Naim Mohamed
Published: November 2014

Many enterprises are currently considering the total supply chain in their product delivery process. If an enterprise is to view the product delivery process as part of a supply chain then it must also consider the product introduction process (PIP). The PIP can account for a considerable proportion of an enterprise's total costs. This paper presents the development of a supply chain view of a steel industry PIP so as to establish a framework for a software based Decision Support System (DSS) via a systems engineering approach. The systems engineering approach is used to ensure optimisation of the whole. The paper shows that there is limited evidence of a framework for considering the PIP from a supply chain perspective using IT or otherwise.