bluuebunny/crossref_metadata_2025 huggingface dataset:
1.7.3 Incorporating Risk In the Programmatic Decision‐Making Process – A Case Study
Authors: Kepchar Ken , Stack Toni , Newnam Bill
Published: November 2014

While the need for good risk management as part of project and program management is well established, risk management practice has often lagged its potential to assist the management team in identifying the need for decisions, framing courses of action, and providing objective evaluation of alternative courses of action. This paper provides an analysis of the role that risk management plays in supporting programmatic decision‐making. Specifically, it looks at how risk management supports the intelligence, design, choice, and review functions of decision‐making as formulated by Herbert Simon. It includes a case study that illustrates the application of risk management to an on‐going program at the Federal Aviation Administration (FAA). The paper also discusses the application of available analytical tools to support the programmatic decision‐making process.
3.7.2 Exploiting Inspection: Some New Practices and Some Reminders
Authors: Gilb Tom
Published: November 2014

Inspection, a proven technique for achieving quality and identifying process improvements, should be applied to technical specifications throughout systems engineering. The greatest value from inspection can be gained through a proper understanding of its purposes and benefits. Newer practices, such as sampling, should be incorporated into the more traditional application of this technique.
4.7.3 Multi‐Criteria Decision Analysis: Limitations, Pitfalls, and Practical Difficulties
Authors: Kujawski Edouard
Published: November 2014

The 2002 Winter Olympics women's figure skating competition is used as a case study to illustrate some of the limitations, pitfalls, and practical difficulties of Multi‐Criteria Decision Analysis (MCDA). The paper compares several widely used models for synthesizing the multiple attributes into a single aggregate value. The various MCDA models can provide conflicting rankings of the alternatives for a common set of information even under states of certainty. Analysts involved in MCDA need to deal with the following challenging tasks: (1) selecting an appropriate analysis method, and (2) properly interpreting the results. An additional trap is the availability of software tools that implement specific MCDA models that can beguile the user with quantitative scores. These conclusions are independent of the decision domain and they should help foster better MCDA practices in many fields including systems engineering trade studies.
1.8.1 Risk Management: Observations and Lessons Learned
Authors: Robinette G. Jeffrey
Published: November 2014

This paper describes some observations and lessons learned from over ten years of doing risk management at the Air Force Aeronautical Systems Center (ASC), Wright‐Patterson Air Force Base, Ohio. This work is based on implementing the ASC Integrated Risk Management (IRM) process at Wright‐Patterson and other government and industry facilities. It also provides an overview of the Aeronautical Systems Center's Integrated Risk Assessment (IRA) approach.

This paper discusses lessons learned from performing the three parts of an integrated risk assessment: the Technical Assessment, the Schedule Assessment and the Cost Estimate. It covers their interaction and interrelationship when accomplishing each of the three parts. It also presents lessons learned from the other major tasks required of a healthy risk management process. The highlights of this paper come from approximately thirty different risk assessments performed by the author, visits to many government program offices, visits to contractor facilities, and annual surveys accomplished at ASC.
2.8.3 Tri‐Cities Chapter Community Project
Authors: Baynes Patrick A. , deLamare Michael A. , Hendel Brian J.
Published: November 2014

In an effort to revitalize the Tri‐Cities Chapter of INCOSE, our Chapter took on a project to analyze the facility needs for the Tri‐Cities Chaplaincy, a local non‐profit organization. The Project examined existing and future space requirements to support the Chaplaincy's expanding services and organizational growth. In addition to active chapter members, the Project attracted the participation of both inactive chapter members and some non‐chapter members. The Project succeeded in energizing the Chapter and in helping the Chaplaincy understand the increasing demands for its valuable community services. This paper discusses how the Project proceeded, some lessons learned from the process, and the benefits it provided the Chapter.
4.8.1 Visualization of Multi‐Attribute Utility Models
Authors: Fishenden J.C. , Singleton G.R. , Maier M.W.
Published: November 2014

Multi‐attribute utility models are usually thought of as direct quantifications of stakeholder preferences. A system alternative that receives the highest utility score is the preferred solution. However, in practice users often attempt to use multi‐attribute models for complex forms of decision making, such as new alternative synthesis or investment selection. Since more complex decision‐making requires more insight into the multi‐attribute data than a single number, we have investigated methods for visualizing high‐dimensionality utility data, especially for utility‐over‐time applications. This paper discusses the visualization techniques and presents examples.
1.1.1 Applying Systems Engineering to Warship Topside Design
Authors: Montigiani Marco , Manzini Mauro
Published: November 2014

This paper presents a high level warship topside design process. All the aspects involved such as Human Factors, Electromagnetic Engineering, the Platform, the Combat System and so on, are taken into account. To manage, plan and coordinate all the activities, a Systems Engineering approach is applied. Starting from requirements definition and their analysis, through an iterative optimization loop, the whole Systems Engineering process is described. To assist supervision, graphic tools such as risk matrices are introduced. These matrices allow a global vision of the whole process in a very simple way. So we provide an effective path towards an efficient topside configuration that minimizes the risks which would otherwise occur in a non‐interdisciplinary approach. Finally a way to “measure” the process is given.
1.2.2 A Specification Format for Reducing the Cost of Change in Safety‐Critical Systems
Authors: Howard Jeffrey
Published: November 2014

Safety‐critical systems are costly to change. In all systems, changes must be examined for their impact on existing designs. Conflicts must be resolved and trade‐offs evaluated to ensure that the system still accomplishes its goals. In safety‐critical systems, the additional concerns of system safety must be satisfied: the change must not introduce new hazardous behaviors, be they incorrect actions or correct actions taken at an incorrect time. An improved format for system specifications, called intent specifications, and a component requirements modeling language, called SpecTRM‐RL (SpecTRM Requirements Language) can reduce the cost of evaluating the safety of changes to complex safety‐critical systems. Intent specifications, the SpecTRM‐RL requirements modeling language, and supporting tool automation have been applied in the aerospace, automotive, and medical device industries.
1.3.1 Conflict Oriented Design
Authors: Lochow Tim
Published: November 2014

Due to the increasing competition on the transport aircraft market the aircraft manufacturers have to make effective strategic decisions during the product development phase in order to avoid false investments and resultant costs. A central position takes the preliminary design phase. This study of the EADS Corporate Research Center contributes to an increase of effectiveness of the design and technology validation process by integrating core elements of innovative design and quality management methods like TRIZ and FMEA. That way a conflict oriented design concept is formed, which allows the user to analyse interdependencies of conflicts that arise during the design process. Additionally a typology of emerging conflicts and contradictions in the preliminary design process is developed, supported by research results in the field of conflict management and concurrent engineering. For the demonstration of the concept, a prototype of a parametric aircraft configuration tool is used. It supplies functionalities that help focusing on detecting conflicts and contradictions within the concept design or technology validation process.
1.3.3 Deployment of System Engineering to Structural Design Teams within Airbus
Authors: Bourne Matthew
Published: November 2014

System Engineering though well established in the development of Aircraft Systems and Software within Airbus has not been widely used in structural design. On the A380 project it was decided to deploy System Engineering methodology across both disciplines to add rigor to the design, benefit from exchange of data and try to ensure Maturity at EIS. This paper describes how System engineering principles were simplified as far as possible to allow deployment to teams unaccustomed to their use and how the cascade of requirements has led to a large proportion of non‐functional requirements at the lowest levels.
1.4.1 Teaching Old Dogs New Tricks
Authors: Bardo Robert A. , Brown Phillip J.
Published: November 2014

Downsizing, and consolidation of previously independent companies, has produced a clash of cultures in many companies. The problem is exacerbated by “home‐grown” product development cultures that have been around for decades and often fail to adequately integrate new disciplines such as software engineering and systems engineering.

Over the years, the pace and complexity of technological development has increased. Mergers have brought together more companies with differing processes. New standards like the Software‐Capability Maturity Model® (SW‐CMM®) and Capability Maturity Model Integration® (CMMI®) have been introduced. All these changes have increased the need for developing and instituting new, integrated, and more repeatable engineering processes. Methods of introducing, and gaining acceptance of, these new processes are becoming very important to the continued competitiveness of many companies.

At issue is how best to get a diverse workforce to work together to achieve extraordinary goals.

Lockheed Martin Missiles and Fire Control (LMMFC), faced with integrating two former competitors, embarked in 1999 on a course to develop a common product development culture. A primary forcing function was the use of Carnegie Mellon University's Capability Maturity Model‐Integration (CMMI®) standard. The resulting new processes are enabling employees to achieve higher goals – by increasing productivity, maximizing use of information, using proven simplified processes, increasing re‐use, and decreasing re‐work. Results to date indicate a “One Company, One Team” mentality is rapidly becoming the norm at LMMFC.
1.5.2 Factors Influencing SE Practices by 2010
Authors: Ring Jack
Published: November 2014

This paper describes current and probable stochastic shocks that may shape the practice of systems engineering in the near future. This is not about predicting the future but about considering possibilities, ramifications and probabilities. The purpose of this paper is to encourage the reader to add, change, or delete entries that are more pertinent to their respective situations and viewpoints, then to think deeply about the interrelationships of these change factors thus the key alternative scenarios for the reader's future. One general conclusion seems clear – the SE practitioner of 2003 will be largely obsolete in five to seven to ten years unless he/she vigorously engages in multidisciplinary learning both across engineering disciplines and especially outside of engineering.
2.1.2 Predicting the Reliability of a Complex System Using an Artificial Neural Network
Authors: Breitler Alan L. , Sloan Crystal D.
Published: November 2014

The capability to predict the reliability of complex systems that must be deployed without overly prolonged or expensive testing is of increasing importance to the military test and evaluation community. The presentation of subsystem reliability data to an artificial neural network is a critical factor in the capability of such networks to produce accurate system predictions. By producing a matrix of values corresponding to subsystem reliabilities, using a zero (0) for a nonexistent parallel resource and a one (1) for a nonexistent series subsystem, it was possible to train an artificial neural network to accurately predict the overall system reliability.
2.2.1 Model‐based Safety Analysis of a Flap Control System
Authors: Bretschneider Matthias , Holberg Hans‐Jürgen , Böde Eckard , Brückner Ingo , Peikenkamp Thomas , Spenke Harriet
Published: November 2014

Fault tree analysis is a widely adopted technique to systematically analyze causes for a given failure of a complex system. Traditionally, a fault tree is constructed top‐down based on knowledge about the structure of the system and the interaction of subsystems. With the increasing system complexity and the accompanying introduction of model‐based development techniques in the industrial process, a substantial amount of this knowledge is laid down in the system models. The main focus of the presented techniques and tools is to automatically exploit this knowledge by extracting a fault tree suitable for FaulTree+ directly from a given design modeled in Statemate. The resulting fault tree is complete wrt. the specified failure, i.e. the analysis considers every possible causal failure combination which is guaranteed by applying model checking techniques. Using an aircraft Flap control system this paper shows how to smoothly integrate the technique into an existing model‐based process.
2.2.2 Complexity and change in the subsea oil production industry
Authors: Piciaccia Luca Abele , Faanes Tore , Lindland Hans Jørgen
Published: November 2014

Sweeping changes have been experienced throughout the whole of the subsea oil production industry.

Space technology has gone subsea, and with it comes the need to properly address the relevant issues.

The traditional oil industry, used to measure its tools in multiple of tons and its performance in barrels, has been faced by the challenge of distributed system interfaces and their metrics.

This paper describes of how the challenge is being tackled at FMC Kongsberg Subsea (FKS), the Subsea Production System manufacturer with the largest number of system installed in the world.
2.2.3 Towards the Integration of Safety Assessment and Systems Engineering Methods for Rail Transport Systems Development
Authors: Duurland Erwin , Ransijn Gert ‐Jan , Verhoeven Maarten , van Duyne Reinier
Published: November 2014

This paper describes an improved, scenario‐based method for identifying hazards of complex safety‐critical systems and its application to the safety management of a high‐speed rail transportation system.

The identifications of hazards is the foundation of safety assessment. If a hazard – any situation that can contribute to an accident ‐ is not identified, one can not take action to eliminate it or to reduce the risks related to it. Organizations creating or introducing changes to safety‐critical systems should make systematic and vigorous attempts to identify any possible hazard.

Traditional approaches for systematic identification of hazards include emperical methods like the use of checklists and structured walktroughs as well as creative methods like brainstorming and HAZOPS studies. While emperical methods rely heavily upon knowledge of the past and tend to be less effective for novel systems, creative methods tend to lack systematic rigour. Both categories fail at addressing the hazards associated with functional failure of complex integrated systems.

The scenario‐based method introduced in this paper combines the systematic, analytical derivation of hazards from behavior models that specify the operational scenarios for the system of interest with creative team‐based sessions that are structured around the same behavior models of the operational scenarios.

An major benefit of this approach is that through the behavior models of the operational scenarios the safety assessment process is directly linked to systems engineering work products. This provides a sound basis for integrated design iteration cycles and reuse of information and thus for improving the quality, lead times and cost of the overall development process.
2.3.2 Tailoring Systems Engineering for UAV platform development
Authors: Doornbos Jaap , Jesse Evert , Wijnhoven Ilze
Published: November 2014

This paper describes how Systems Engineering methods have been applied in the conceptual design study for an Unmanned Aerial Vehicle (UAV), and the lessons that were learned in this experience. In comparison with traditional aerospace and defense industry, the UAV market is different because of the seemingly endless possibilities of UAV technology, the lack of existing standards and the entrance of new players, which are not traditionally active in aerospace or defense. This makes the application of Systems Engineering for UAV platform developments differ from traditional practice.

In the UAV conceptual design study, which is the focus of this paper, all partners had a strong background in aerospace and defense development. The case is discussed as an example, aimed at illustrating the principles of tailoring Systems Engineering for UAV platform development.
3.3.2 Design Concept Evaluation Using System Throughput Model
Authors: Sequeira Gary , Nutt W. Mark
Published: November 2014

The U.S. Department of Energy (DOE) Office of Civilian Radioactive Waste Management (OCRWM) is currently developing the technical bases to support the submittal of a license application for construction of a geologic repository at Yucca Mountain, Nevada to the U.S. Nuclear Regulatory Commission. The Office of Repository Development (ORD) is responsible for developing the design of the repository surface facilities for the handling of spent nuclear fuel and high level nuclear waste. Preliminary design activities are underway to sufficiently develop the repository surface facilities design for inclusion in the license application. The design continues to evolve to meet mission needs and to satisfy both regulatory and program requirements.

A system engineering approach is being used in the design process since the repository facilities are dynamically linked by a series of sub‐systems and complex operations. In addition, the repository facility is a major system element of the overall waste management process being developed by the OCRWM. Such an approach includes iterative probabilistic dynamic simulation as an integral part of the design evolution process. A dynamic simulation tool helps to determine if:

the mission and design requirements are complete, robust, and well integrated;

the design solutions under development meets the design requirements and mission goals;

opportunities exist where the system can be improved and/or optimized;

proposed changes to the mission and design requirements have a positive or negative impact on overall system performance and if the design changes may be necessary to satisfy these changes.

This paper will discuss the type of simulation employed to model the waste handling operations. It will then discuss the process being used to develop the Yucca Mountain surface facilities model. The latest simulation model and the results of the simulation and how the data was used in the design evolution process will also be discussed. Since the use of dynamic simulation is iterative and integral to the design effort, future activities will also be summarized. The paper will close discussing lessons learned from applying dynamic simulation to designing complex systems, and will discuss what pitfalls to avoid and recommendations for developing flexibility in system model development.
3.4.1 CENTER FOR SYSTEMS ENGINEERING
Authors: Bausman Karen , Wilson Mark
Published: November 2014

The “Systems Engineering” Discipline seems to have has lost its focus within the Air Force. Comments by high level USAF leaders have pointed out that the front end of the Systems Engineering Process has broken down. This has resulted in systems that have high requirements volatility and acquisition failures. In a combined effort, the Air Force Institute of Technology, the Air Force Material Command and the Air Force Space Command have joined forces to establish a Center for Systems Engineering.

It has become evident over the last ten years, with Acquisition Reform, the government gave away the “Keeper” role that assured a consistent application of Systems Engineering and no one from industry has stepped up to accept full responsibility. Systems Engineering (SE) is an interdisciplinary engineering management process that evolves and verifies an integrated, life cycle balanced set of system solutions that satisfy customer needs. It is a comprehensive, iterative, multi‐functional, technical management process that includes translating operational requirements into configured systems. It is responsible for integrating the technical inputs of the entire design team, managing interfaces, characterizing and managing technical risk, transitioning technology from the technology base into program specific efforts, and verifying that designs meet operational needs. It is a life cycle activity that demands a concurrent approach to both product and process development. Systems Engineering/Management touches every aspect of our acquisition, operational, sustainment and retirement processes.

A national forum on SE identified the need to ensure that a quality systems engineering capability exists. The Center for Systems Engineering (CSE) has been established to do just this job. This CSE serves as the nucleus for the development and accumulation of academic, government and industry SE best practices, processes, metrics and training. It is collaborating with other members of the SE community to develop, publish, continuously refine and advocate systems engineering processes and implementation. The CSE provides consulting and analysis services on SE to all Air Force commands and programs and publish findings as necessary. The CSE manages the identification and collaboration of education and training for all Air Force personnel associated with the systems engineering process. Ultimately we hope to rebuild the systems engineering expertise across all Department of Defense areas.

This paper identifies some of the current systems engineering issues/initiatives and challenges with which the CSE is engaged. The approach in this paper provides a logical method of correcting current systems engineering shortfalls and posturing the Air Force, and potentially the Department of Defense, for future success in the management of our weapon/space systems toward meeting the war‐fighters needs.
3.4.2 Deployment of Systems Engineering at PSA Peugeot Citroën
Authors: Lamothe Pascal , Fanmuy Gauthier
Published: November 2014

Automobile product has become today a complex system. Not only does it seek for an optimal trade‐off between many domains such as style, human factors, mechanical, electronic, body structure, software, economy and production products but automobile has also taken advantage of control and information management functions that represent a third of the car price.

Automobile is now both the result of the application of existing solutions (re‐use of processes) and the integration of innovating solutions.

Moreover while automobile product is becoming more complex, customers move from a demand market to an offer market. Automobile industry offer now creates client needs. This competitive challenge involves obviously the necessity to reduce costs and deadlines while functional and performance requirements are increasing.

Resolution of this set of antagonistic requirements can be obtained only by using the most appropriate methodologies. Engineering methodologies now converge towards a large concept called: Systems Engineering.

This paper introduces fundamental considerations associated with the deployment of systems engineering in PSA Peugeot Citroën: (1) tailoring a referential of processes for engineering an automobile product based on EIA 632 standard (2) building a training cycle (3) setting up systems engineering tools focused on the engineering requirements processes with DOORS (4) assisting the engineering teams to use methods and tools.

We hope this experience about the still ongoing deployment of system engineering in PSA Peugeot Citroën will inspire firms that wish to set up the systems engineering methodology.
3.5.3 Trans‐national distributed Systems Engineering in A400M
Authors: Schulze Sven‐Olaf
Published: November 2014

This paper briefly gives an overview about the Systems Engineering application in a multi‐national and multi‐lingual project. At least 6 nations, Airbus and other companies, are developing in one partnership this new military transport aircraft. Based on the contractual, cost, quality and time constraints the engineers have to design the best possible solution for this aircraft. The aim is to give an overview about the practical experience developing a system in an IPT (integrated project team), a multi cultural environment, different historical experience and knowledge of each partner and to show the added value to work with a defined and agreed view of developing a complex system.
3.6.1 Experience in Teaching the Seamless Integration of Systems Engineering and Project Management
Authors: Mooz Hal , Forsberg Kevin
Published: November 2014

Project management and systems engineering are two inseparable disciplines. Yet they are very frequently taught separately and they are usually implemented separately within organizations. PMI and INCOSE usually operate independently, further accentuating the separateness. This leads to a lack of teamwork and collaboration and often causes competition and tension among those that should be working and cooperating seamlessly. To overcome this undesired result in a US Government Agency's technology‐intensive project environment, a training program has been in place for fifteen years that serves as the basis for high‐level project manager certification and presents the disciplines of project management and systems engineering as a single inseparable process. The training has resulted in improved project performance and reduced cost and schedule overruns. Over the years the content has continually been upgraded to remain at the state of the art and to improve the effectiveness of the information transfer. This paper describes the motivation, concept, formulation, execution, and management of this highly effective program.
3.6.3 Towards a shared process for system design and project management
Authors: BARON Claude , Esteve Daniel
Published: November 2014

This paper explores the interest to join system design and project management methods and tools. Our motivation is to prevent the obvious incompatibilities between technical objectives and socio‐economical requirements in the enterprise. What we recommend is to work on a generic unique model based on the classical top down design steps, to which costs models and non‐functional requirements are associated. Project management thus appears as an activity of diagnosis and optimisation, allowing to choose certain realisations between the different possible scenarios and to optimise the management by an allocation of tolerances, which is calculated for each supplier on the base of a global objective. This analysis concludes on the interest of two complementary tools : the evolutionary algorithms to arbitrate the scenarios, and the Monte‐Carlo methods for the allocation of tolerances.
4.4.2 Net‐Centric Dynamic System Model Architecture
Authors: LaCerte Yves
Published: November 2014

Net‐Centric weapon systems interoperate on the Global Information Grid to achieve information superiority. In a sensor‐to‐shooter scenario, the chain of events that connect the initiation of a control event to its result is not within a closed space. The chain may incorporate information gathering devices and weapons a thousand miles apart, or any of a myriad of devices in a more local confederated environment. Net‐Centric systems need to consider determinism not only on the control side, but the communications side as well. This paper investigates a Net‐Centric Dynamic System Model architecture in the context of interoperability.
4.5.2 Preparing the World for Complexity: A Systematic Approach
Authors: Klingler Ronald D. , Plowman Catherine M. , Soto Rafael , Turk Robert J.
Published: November 2014

The increasing level of complexity in most aspects of today's world requires that government, industry, and society, in general, produce integrated systems and products more fully capable of addressing that complexity. Unfortunately, the high degree of fragmentation in our current educational system does not adequately provide graduates with the knowledge and skills necessary to produce integrated systems. This demand for integration has created professional opportunities in the way of new careers, such as systems engineering, but has not yet driven the broader application of systems principles by other professionals. Even today's interdisciplinary teams must possess the ability to visualize the entire system they are working on prior to applying their individual skills toward developing and producing integrated solutions.

This paper highlights proposed interventions at all educational levels (i.e., elementary, secondary, and college educational settings, as well as in the workplace) to introduce systems thinking as a more desirable way of performing any professional activity. In particular, the college freshman level has been selected to conduct an initial intervention to test this hypothesis. Systems approaches and principles will be presented and discussed in a formal classroom setting between issuance and evaluation of pre‐ and post‐presentation questionnaire. It is expected that this intervention will result in increased knowledge of system principles and concepts, and an increased understanding of how these principles can be applied by this target audience.
3 Panel: How Do Requirements Relate to Objects?
Authors: Kaindl Hermann , Glinz Martin , Kasser Joseph E. , Kasser Joseph E.
Published: November 2014

This position paper discusses arguments in favor and against regarding requirements as objects. As there are good arguments for both standpoints, a partial synthesis is developed. The synthesis is based on the idea of not treating requirements as objects, but using objects for organizing and understanding requirements.

Object‐oriented systems engineering contains a broad chasm. On one side is object‐oriented systems engineering and on the other are the systems and sub‐systems that are objects by definition. The chasm is the domain of requirements. Whiles conventional systems and software requirements engineering have ignored the chasm, Total Quality Management (TQM) can be used to bridge the chasm and reduce cost and schedule overruns. This approach is based on a starting assumption that since requirements drive the work of implementing the system, object‐oriented requirements have both the traditional properties describing the product but also have properties than can assist in ensuring a cost‐effective production process. Several candidate properties that have been identified and their usefulness are discussed. Some concept demonstration tools that have been developed are summarised, and the presentation concludes by pointing out that the object‐oriented properties can be used to provide views of a proposed system at the System Requirements Review that would be difficult to observe in the current paradigm.
5.2.1 Can Systems Engineering be taught at Undergraduate Level?
Authors: Goodlass Sue
Published: November 2014

Everyone knows that Systems Engineering is complicated and difficult. It takes a long time to become sufficiently experienced to be a good practitioner and people need to make mistakes in order to learn from them. How successfully then, can such a difficult topic be taught at undergraduate level? In the early 1990's, BAE SYSTEMS engaged Loughborough University to develop and deliver an undergraduate systems engineering programme and has recruited engineers from it since the first cohort graduated in 1997. This paper describes how the programme was designed and developed and compares systems engineers graduating from this programme with other engineers in BAE SYSTEMS.
5.3.3 The Need for Observable States Affects the Make‐Reuse‐Buy Decision
Authors: Botta Rick , Wuersch Bill , Bahill Terry
Published: November 2014

Today, systems are supposed to be designed so that they are better, faster and cheaper. The mantra for doing this seems to be the reuse of available components. This paper presents a process to help select and reuse existing components in new system designs. An important part of this process is identifying observable states.
5.5.1 The Analysis and Evaluation of Customer Satisfaction and Service Management
Authors: Trappey Amy J.C. , Hsu Fu‐Chiang , Kuo J. , Trappey Charles V. , Chao Charles L.J. , Lu Tony T. H.
Published: November 2014

Adaptation of information technology in business applications enables enterprises to understand customer behaviors and use customer‐related knowledge to increase competitiveness, adjust product market position, and build customer loyalty. The Internet and computer telephony integrated (CTI) applications, in particular, enhance the communication channels among members of extended enterprises (e.g., customers and suppliers). Thus, Customer Relationship Management (CRM) has become a key focus of modern enterprise operations with the help of modern Internet and CTI techniques. A company can achieve the customer‐centric business model and the one‐to‐one marketing strategy by using contact center applications and data mining methodologies. With the increasing number of communication channels, telephone‐based contact centers are no longer sufficient to build and maintain good customer relations. Multi‐channel contact centers that integrate phone, fax, e‐mail, web, and PDAs enable managers to respond to customer queries, complaints and service requests. An improved CRM program not only provides greater access but also provides the means to analyze customer interaction data. Corporations gain benefits such as enhanced customer loyalty and brand enhancement by transforming data collected through multiple communication channels into meaningful knowledge. This research uses a multi‐channel contact center (CC) as a basis to model customer interaction processes, define key performance indicators (KPIs) of CC, and develop CC evaluation methods to measure customer satisfaction and service quality of a contact center based on the set KPIs.
5.5.2 Application of SSM and Architecture Frameworks as a Method of Enquiry for Organisational Behaviour
Authors: Vencel Les , Sweetman Elizabeth
Published: November 2014

Systems engineering is traditionally used as a method of design. In this study, it has been used as a method of enquiry into organisational behaviour in a sociotechnical system. A mix of methodologies from both the functionalist and interpretative social paradigms has been adopted. The methodology mix comprises Checkland's Soft Systems Methodology (SSM) and Structured Analysis and Design Techniques. This hybrid methodology allowed the use of rich pictures and architectural models to analyse organisational behaviour from two representative views: the human activity system and the operational architecture.

The paper relates the goals of developing an understanding of the current organisational operational behaviour and then discusses the use of methodological pluralism, its rationale and the use of a revised Total Systems Intervention (TSI) model by Jackson based on contemporary critical systems thinking as a checklist for pluralism. The hybrid methodology using both soft and hard methods employed rich pictures and Defence Architecture Framework (DAF) compliant architecture models (AS‐IS views) to enquire into organisational behaviour. The DAF models represented both the perceived and actual state of operations. Comparison of the DAF models correlated with the SSM derived rich pictures and issues log were used to develop an understanding of the organisational behaviour as well as produce an updated operational architecture. Recommendations for change were made to senior management. We finish the paper with a 12‐point lessons learnt discussion of our experiences in doing this study. We conclude that the use of a pluralist systems engineering approach as a method of enquiry into sociotechnical organisational behaviour can provide a richer understanding of operational behaviour as it complements the human activity systems view with the operational architecture views. The pluralist approach is methodologically sound and Jackson's modified TSI provides an evaluation checklist.
5.6.1 The Application of Complexity Theory in the Development of Large‐scale ICT Systems
Authors: du Preez Lukas Johannes , Smith Abraham Johannes
Published: November 2014

The elements of complexity theory (chaos theory) found application in many diverse disciplines, including the social and management sciences. It became a means to address some of the vexing problems that could not be solved through direct causal analysis. Complexity theory contradicts many of the existing views of conventional management and requires a cognitive change from a rational Newtonian paradigm to a non‐linear, dynamic and complex systems paradigm. This paper unites the principles of complexity theory with Information and Communications Technology (ICT) project management by considering any large‐scale ICT development project as a non‐linear, dynamic and complex system within the context of a larger complex environment. The interactions between the different complex dimensions of the project state space are discussed. ICT project‐ and risk management are described within the context of the elements of complexity theory such as sensitive variables, attractors and fractals.
5.6.2 User Requirements for a Technical Risk Assessment Technique
Authors: Bijl Maarten G.H. , Hamann Robbert J.
Published: November 2014

This paper addresses the results of a study identifying the user requirements for a technical risk assessment technique, specifically for use by small to medium sized enterprises active in space engineering. By means of a questionnaire Systems Engineers and Project Managers of four companies where interviewed in order to collect data on the companies' business, the experience of the personnel with risk management, constraints on the technique's implementation and the content of the technique.

Major result of the study is that the view on risk and the factors composing it varies widely and that a technique or tool will likely not be applied if it does not agree with the view of the assessor. As a consequence a technique must enable the modelling of the assessor's perception of the structure of the risk (that is: the factors determining the probability of occurrence of a risk and their mutual interaction). A basic set of risk models (Risk Spaces) is proposed and the constraints on technique and tool are summarized.

The paper presents the main elements of the User Requirements for a technical risk assessment technique for the specific target group: they address both a technique and tool to construct the risk model (Model Tool Kit) and the risk assessment technique and tool itself.
6.1.2 Interactive Metamodel‐Compliance Checking of Requirements in a Semiformal Representation
Authors: Kaindl Hermann , Kramer Stefan , Hailing Mario , Harput Vahan
Published: November 2014

Checking requirements is highly desirable but hard to achieve in practice, where only word processors are used in most projects. While in this case reviews are more or less the only means, formal representations allow for a variety of automated checks. Unfortunately, formal representations of requirements are rarely available in real‐world projects.

Semiformal representations are easier to obtain and still offer some possibilities for automated checks. Based on an object‐oriented hypertext representation, we present an implemented approach for compliance checks against a metamodel, which resembles some kind of completeness checking. In addition to allowing checks to be invoked by a human user of the tool, the checks are periodically and automatically invoked by taking into account the already existing information on the requirements. In summary, we propose an interactive approach with shared initiative between the tool and its user for compliance checking of requirements against a metamodel in a semiformal representation.
6.3.2 Goal / Strategy Maps Methods, Techniques and Tools to Specify Requirements in Different Evolutionary Contexts
Authors: Salinesi Camille , Etien Anne , Zoukar Iyad
Published: November 2014

this paper reports the status of a research program that deals with the issues specifically raised by Requirements Engineering (RE) in the context of Information System (IS) evolution projects. This research program was triggered by the ‘Chaos’ report by the Standish Group, which explains that the lack of adequate RE methods techniques and tools is a major cause of failure of IS projects, and on the other hand, by Bohem's report, which says that most of IS projects are set in an evolutionary context rather than for developing new IS. Our goal was three‐fold: (i) to identify the methodological frameworks for doing RE in IS evolution projects, (ii) to build adequate modeling techniques that match the need of these frameworks, and (iii) to propose adequate methods and tools to deal with IS evolution requirements. This paper reports on each of these aspects.
7.1.1 Assessing the Impact of Requirements Volatility on the SE Process using Bayesian Analysis
Authors: Russell Michael S.
Published: November 2014

There are many factors that affect the level of requirements volatility a system experiences over its lifecycle. Improper requirements generation, undocumented user expectations, conflicting design decisions, and anticipated / unanticipated world states are representative of these volatility factors. Combined, these volatility factors adversely affect successful system development. This paper proposes that a Bayesian Network can be used to support reasonable judgments concerning the most likely sources and types of requirements volatility a developing system will experience prior to starting development; and by doing so it is possible to predict the level of requirements volatility the system will experience over its lifecycle. This assessment offers valuable insight to the system's developers, particularly by providing a starting point for risk mitigation planning and execution.
7.2.3 Too Hard, Too Soft, Just Right … Goldilocks and Three Research Paradigms in SE
Authors: Cropley David H , Harris Michael B
Published: November 2014

This paper examines the spectrum of methodologies that can be utilized in research in general. The two primary categories, quantitative and qualitative, traditionally find use in particular discipline areas. This paper will examine the characteristics of common quantitative and qualitative methodologies and discuss how these can be applied to research in systems engineering. The result is a wide choice of methodologies covering both the functionalist (hard) and interpretive (soft) paradigms. The broad focus of systems engineering, covering both hard (technical) and soft (socio‐technical) approaches, will be shown to benefit from a broad appreciation of the full range of research methods. The paper discusses the predisposition to quantitative methods that dominates engineering thinking and argues for the inclusion of qualitative research methods in the toolkit of systems engineering researchers.
7.3.3 The Applications of Systems Engineering for the Development of RFID in e‐Logistic Service
Authors: Wang T.J. , Tsen Y.J. , Chang Larry
Published: November 2014

Current paper will apply system engineering to Radio Frequency Identification (RFID) system that is developed for the purpose to improve Taiwanese logistic industry competitiveness. Based on the development strategy for systems engineering in the e‐environment, the production line and warehouse management e‐logistic RFID system program integrate both domain knowledge and systems engineering. The methodologies, tools, procedures, templates and management system of systems engineering have been applied in this program. Using systems engineering technology, such as requirement analysis, risk management and others will help to solve the complex and changing environment of present logistic service industry in Taiwan.
7.4.1 An Architecture Description Language for Developing Automotive ECU‐Software
Authors: Freund Ulrich , Gurrieri Orazio , Küster Jochen , Lonn Henrik , Migge Jörn , Reiser Mark‐Oliver , Wierczoch Thomas , Weber Matthias
Published: November 2014

The significance of embedded software systems in the automotive domain has increased dramatically during the last ten years. In contrast, today's development methods and tools applied in the automotive industry are limited in many ways. They are each restricted to certain stages of development and therefore several approaches need to be used simultaneously, they are not interoperable and most of them are not tailored to the specific needs of the automotive domain. In this paper we present an Architecture Description Language called EAST ADL that seeks to capture all information needed during development, from early analysis to implementation and evolution and meets specific automotive requirements such as support for automatic code generation in the context of common automotive hardware.
7.4.2 Europe's First System of Systems
Authors: Brown Phillip J.
Published: November 2014

Systems thinking is as old as civilization. The question is can today's systems engineers benefit from examining the accomplishments of early system builders? This thought is examined in the context of roman engineering achievements.

The birth of the Roman republic around 500 B.C. led to the building of an unprecedented array of remarkable systems. The needs of the republic, followed by those of the empire, produced important advances in building construction, water supply, mining and the building of bridges, roads, harbors, ships. Many complex systems such as the aqueducts supplying Rome's water were created.

This paper postulates that the Romans developed Europe's first system of systems. The backbone of the system, a network of roads radiating out from Rome, began as a strategic initiative to maintain government control throughout the empire. Over time, this super system evolved into the means for Romanizing the many different cultures dragged into Rome's dominion. The resulting cultural harmonization left a lasting imprint on the world.
7.5.1 Recommendations for Automated Test Requirements Management
Authors: Houser Jody B.
Published: November 2014

In the aerospace community, requirements data has a way of living beyond the end of product validation when it might be expected that it has fulfilled its purpose. Not only are these requirements then used to develop test strategies and acceptance limits for the production line, but certain aerospace standards and product support agreements demand a transmittal of test requirements to the airlines and their representatives. The management of requirements data as it progresses from the interface control document, to test equipment engineering and ultimately to the airframer's customer is explored. Specifically, a set of recommendations for a tool to support production test requirement management is proposed.