bluuebunny/crossref_metadata_2025_split huggingface dataset:
Bias Amelioration in Tradeoff Studies
Authors: Smith Eric D. 
Published: November 2014

AbstractBuilding large and complex systems continues to be a significant challenge for today's systems engineers and integrators. This tutorial sets forth new ways of thinking that could lead to improvements in how systems engineering and integration are carried out. In particular, nine new perspectives are suggested for “thinking outside the box”. Examples are provided for each, along with a discussion of their potential benefits. In addition, thinking in groups as well as historical thinking suggestions are examined. A summary provides an overview of notions that represent departures from current mainstream approaches.
Synergistic Model‐Based Systems Engineering with SysML and OPM
Authors: Dori Dov 
Published: November 2014

AbstractModel‐Based Systems Engineering (MBSE) is emerging as a pivotal paradigm, placing modeling as the underlying activity of systems' and products' lifecycle management. SysML is the OMG standard for MBSE, while Object‐Process Methodology (OPM), one of the six leading INCOSE MBSE methodologies, is in the process of becoming ISO standard and the basis for model‐based standards authoring. OPM and SysML complement each other, as each is especially suited for different lifecycle stages: OPM, which is simple and holistic, is most fit for the early conceptual stages, whereas SysML, which provides for expressing details, is good for later design stages. The tutorial introduces the principles, syntax, and semantics of OPM and SysML, highlighting their commonalities and differences, and showing how to use both in ways that promote synergy and improve critical system features, notably clarity, consistency, and completeness. The resulting model is an indispensible blueprint that puts all the stakeholders on the same page across the system lifecycle span.
Establishing and Using a Risk Management Program Effectively
Authors: Powell Mark A. 
Published: November 2014

AbstractWe manage risk every day of our lives. You would think all good SE's would be good risk managers. Yet many enterprises fail because some unidentified or un‐handled risk materializes. Many enterprises fail to take advantage of positive risks (opportunities) that could all but ensure success. Risk Management is not as easy as it seems it should be.This tutorial reveals to both the new SE and the seasoned veteran looking for a refresher the secrets of Risk Management and how to make it work. We will review the basic concepts of formal Risk Management and how it is executed in Systems Engineering. We will cover in depth all seven areas of Risk Management: Identification, Analysis, Assessment, Mitigation, Accounting, Planning, and Communication. Each of these areas will be approached with a specific emphasis on how they work together to make an enterprise successful. Further, we will set up a framework for introducing Risk Management within Systems Engineering, to work synergistically by integrating it with Project Management. And as icing on the cake, we will introduce some new methods for risk assessment that make the practice much more effective.
Defining Operational Concepts using SysML: System Definition from the Human Perspective
Authors: Jorgensen Raymond 
Published: November 2014

AbstractUses cases & scenarios are an effective means of assessing system operation from the user's perspective. Rather than focus on obscure “functional requirements”, which are oftentimes elusive to grasp and difficult for the end‐user to understand, this tutorial explores how an operational concept based on use cases & scenarios can be used to focus on the user's perspective of the system, with subsequent improvements in the completeness and understanding of the functional requirements. This tutorial explores why an Operational Concept document is written, what the Operational Concept is, and how it can be effectively applied on your project through use case & scenario descriptions and SysML diagramming. Tutorial includes a workshop format to apply lessons learned and discuss strategies. SysML concepts explored include use case diagrams and activity diagrams to express main use case scenarios, alternate courses, exception cases, and extension use cases.
1.1.1 Development of Patrolling Schemes for Improved Border Security Performance through an Evolutionary Approach
Authors: Muaafa Mohammed , Ramirez‐Marquez José Emmanuel 
Published: November 2014

AbstractThe potential danger of unauthorized cross‐border activities is a considerable national and trasnational security threat that has raised international concern over enhanced border control. In many cases, the vast size and geographical diversity of international borders increase the complexity of border security missions. Such situations require an optimal surveillance strategy to help prevent and deter suspicious activities along borders. This paper focuses on developing patrolling schemes that deploy personnel to patrol designated areas previously suspected for having unauthorized cross‐border attempts. A multi‐objective optimization model is proposed to design patrolling schemes that minimize vulnerability and cost. An evolutionary algorithm is used to generate a Pareto set of optimal solutions, which are characterized by the routes of patrol units. Illustrative examples are provided to discuss the effectiveness of the model.
1.2.3 Designing a Knowledge Management System (KMS) for a complex engineering environment
Authors: Saraf Neha , Siemieniuch Carys 
Published: November 2014

AbstractThis paper forms a part of the Engineering Doctorate (EngD) project sponsored by EPSRC and Thales UK. The aim of this project is to design a knowledge management system (KMS) to be applied in a complex engineering environment in the military electronics domain, by identifying and addressing issues in the sponsor organisation, Thales UK. This paper discusses the systems engineering approach taken during the requirement analysis phase and describes the key issues emerging which will impact on the design of the KMS. After giving a brief introduction of the project and methodology used in the project, the paper presents a creation of a theoretical baseline built to understand the questions involved in creating KMS (section 3), an investigation carried out in the company environment to explore existing KM issues (Section 4 and 5), and a dual case study approach undertaken to further investigate KM (section 6). The paper is concluded by summarising the key achievements of the research and outlining the approach for future steps for formal requirement generation.
1.3.1 How to use systems architecture to specify the operational perimeter of an innovative product line
Authors: BERREBI Johanna , Krob Daniel 
Published: November 2014

AbstractIn industrial companies, it can be observed that research and development departments encounter difficulties during the innovation phase. Indeed, searchers have a tendency to optimize technologies in an unorganized way. As a result, they often end up with products that do not fit with the industrial needs and are stored on shelves. The emergence of new products in an industrial perimeter should be the result of a careful study of the context, environment constrains, and stakeholder's needs which have to be translated into requirements building a frame for innovation. This article's aim is to propose a suitable methodology (system architecture) to manage and supervise innovation in order to create or improve a product. We will apply this methodology to a wireless sensor network system which is an innovative product research field launch by the rising aeronautic need to lighten aircrafts. As this system's final purpose is to be installed on aircrafts, we will try to build a family of modular systems with common basic module and specific compatible modules.
1.6.1 xFFBD: towards a formal yet functional modeling language for system designers
Authors: AIZIER Bruno , LIZY‐DESTREZ Stéphanie , SEIDNER Charlotte , CHAPURLAT Vincent , PRUN Daniel , WIPPLER Jean‐Luc 
Published: November 2014

AbstractAlthough the eFFBD formalism dates back to the 1990s (or even, in a simplified form, the 1950s), it seems that it is still not as much used by the Systems Engineering community as it could. Indeed, eFFBD is a modeling language focusing on functional paradigm i.e. allowing functional and behavioral modeling and reasoning about a system. Currently, it is often confronted or compared to other languages such as SysML for activity modeling (activity diagrams) based on object paradigm. This paper aims to demonstrate the interest and the potential advantages for systems designers, like most of the discipline‐oriented designers to dispose of an enriched (conceptually and semantically) eFFBD modeling language called here xFFBD. This has to be a credible framework for modeling, communicating and reasoning about complex systems. After shortly recalling the history, the key concepts and capabilities of eFFBD, this paper compares eFFBD with other formalisms considered here as relevant for the study, Petri nets and SysML. Several leads are then identified and discussed in order to improve the eFFBD language and to provide a first draft version of xFFBD specification.
2.2.1 Decision Management (DM) as the engine for scalable cross domain Systems Engineering (SE)
Authors: Mendonza Pradeep , Fitch John A. 
Published: November 2014

AbstractDecisions create the future in any industry or human endeavor. A robust Decision Management (DM) capability is the key enabler for accelerating the benefits of Systems Engineering (SE) discipline to new domains. Effective Decision Management is comprised of three elements: 1) decision patterns; 2) DM methods engine; 3) decision‐centric information model.INCOSE can leverage DM as an engine for SE outreach to new industries and domains. DM is highly scalable and integrates knowledge from many processes and stakeholders. A “decisions‐first” outreach strategy offers a clear value proposition to the primary stakeholders who must be convinced of the benefits of SE discipline. Existing decision‐makers gain a new set of techniques that improve decision quality, speed and execution. Subject matter experts gain a method for influencing designs with their unique knowledge and preserving their knowledge in the form of decision patterns. Project managers gain the ability to proactively identify and prioritize decisions and manage their impact on project cost/schedule baselines. Solution developers gain a better understanding of the upstream decisions that drive their requirements.Most of the cross‐domain benefits of DM can be demonstrated through rapid‐payback pilots without commitment to wholesale adoption of more comprehensive, complex and costly SE frameworks. The authors propose to engage INCOSE's Decision Analysis working group as the forum for investigating the cross‐domain applicability of DM.
2.6.2 Sociotechnical systems resilience
Authors: Ruault Jean‐René , Vanderhaegen Frédéric , Luzeaux Dominique 
Published: November 2014

AbstractSystems engineering deals with artificial systems conceived by human beings. These systems are combinations of elements aiming at one or more definite goals. Sociotechnical systems consist in technical parts, concerning systems engineering issues, and in human and organizational parts, concerning medical and social sciences issues. Resilience reports to the capacity of sociotechnical systems to adjust faced with disturbing events, to adapt and learn the adequate rules of adaptation, when the disturbances are out of the specified perimeter of the system's adaptation mechanisms. After having characterized resilience, the article highlights its relevance to the field of the sociotechnical systems. Then, sociotechnical systems' resilience is articulated with systems engineering and architecture in order to evolve systems engineering processes, engineering models, system architecture and enabling systems. Lastly, the article underlines the fact that systems engineering is necessary and owes being supplemented of good practices of management which contribute to the of sociotechnical systems resilience.
3.1.2 Machine Learning technologies for the Requirements Analysis in Complex Systems
Authors: Nardini M. , Ciambra F. , Garzoli F. , Croce D. , Cao D. De , Basili R. 
Published: November 2014

AbstractRequirement Analysis is a relevant application area for a variety of Semantic Technologies related to the extraction, disambiguation and exploitation of the knowledge derived from technical requirement documents. Most methods rely on shallow language processing technologies for the automatic extraction of core concepts (e.g. components/devices, their parts and functionalities) and norms (e.g. constraints on the use of components). Few works have been devoted to study paraphrasing (i.e. textual equivalence between requirement definitions) for consistency checking and redundancy elimination. We propose here a distributional method to train a kernel‐based learning algorithm (i.e. SVM), as a cost‐effective approach to validate requirements from text in support of Requirement Analysis in the design of a Complex Systems, i.e. Naval Combat Systems. These latter are complex systems based on software components able to manage all the Combat System Equipment in different mission scenarios. We will describe the application of Recognition of Textual Entailment (RTE) techniques based on data‐driven learning methods to this scenario. While modeling the asymmetric logical relation of entailment between two textual descriptions (i.e. an hypothesis and its thesis), RTE can be here applied to the validation step of compositions between system functionalities described in the requirement specification texts. Early evidences are here discussed, as a proof of the strong applicability of the method to the general case and to other realistic scenarios in System Engineering.
3.4.2 Putting the System Back Into Systems Engineering
Authors: Eng Bernhard Meyer M 
Published: November 2014

AbstractThis paper opens with some observations that underline the confusion regarding systems engineering, even amongst its fraternity. It proposes a “return to the roots” to revisit the definition and understanding of systems and systems engineering. A three‐dimensional Systems Engineering Space (SE‐Space) is introduced that combines system, engineering, and time. These “dimensions” are described to gain an understanding of their importance and relevance in systems engineering. Emphasis is placed on the generic nature of a system and its attributes or characteristics, as they apply to the realisation stage of systems. Concepts of this proposed Generic Systems Engineering (Generic‐SE) approach are illustrated with reference to a sample rotorcraft environment, emphasising a hierarchical structuring. It concludes with an appraisal and mapping of ISO/IEC 15288 processes against this proposed Generic‐SE approach. This demonstrates the versatility of a generic systems engineering approach, which encourages this back to the roots appeal.
4.2.1 Platforms for Engineering Experimental Biomedical Systems
Authors: Mosteller Matthew , Ghodssi Reza , Austin Mark , Yang Shah‐An 
Published: November 2014

AbstractThe systematic design, validation, and verification of systems for biomedical experiments in laboratory and clinical applications are complex activities due to the highly stochastic nature of biological systems. This paper presents a platform framework for the modeling of these biological components in the context of system‐level analysis, facilitating early validation and verification of biomedical devices. Looking forward, the capabilities of this platform enable the development of more efficient and effective experimental biomedical systems.
4.4.2 MBSE Feasibility Study to improve PLM Business Solution System Specification and Design
Authors: Marco Alemanni , Angelo Corallo , Elena Latino Maria , Scarl Dhitech , Elena Valfrè 
Published: November 2014

AbstractAmbiguous requirements are the main cause of failure in PLM business solution applications development. SysML used in a Model‐Based Systems Engineering (MBSE) development process can mitigate this primary source of error. MBSE moves system engineering practices from document‐centric to model‐centric approach in which the model becomes the primary systems engineering artefact to represent system specification and design. The adoption of this new approach requires careful consideration of the cultural change, adequate training, and a new methodology.This paper describes the feasibility study, results and lesson learned on the MBSE maturity acquired in Alenia Aermacchi Information System and Engineering departments applying MBSE to Product Life‐Cycle Management (PLM) and Document Management. It is based on the University of Salento expertise about modelling languages and on the Alenia Aermacchi experience on System Engineering. SysML has been used as standard language, IBM Harmony Methodology as system engineering methodology and IBM Rhapsody as modelling tool.
5.1.2 Entering a Brave New World: Applying Systems Engineering to American Infrastructure Projects
Authors: Hoehne Oliver M. 
Published: November 2014

AbstractSystems Engineering is a well accepted engineering discipline in most industries, including information technology, defense, aerospace, automobile, and medicine, across the globe. When it comes to railroad infrastructure projects in the United States, however, these projects inevitably rely on the Plans, Specifications and Estimate (PS&E) process used in the construction industry. Large scale conventional rail projects are highly complex. Large scale high‐speed rail systems are even more so. Systems Engineering inevitably has a fundamental impact on the traditional engineering approach of railroad infrastructure projects, perhaps not unlike what the introduction of electrification did during the steam locomotive era, as depicted in Figure 1.This technical paper presents a case study illustrating how Systems Engineering is being combined with the established Plans, Specifications and Estimate approach, and how the $65 billion California High Speed Train Project (full Phase 1 in 2010 dollars) is benefitting from the values of Systems Engineering [1].This paper provides a brief overview of the California High‐Speed Train Project, describes the Systems Engineering (SE) objectives, discusses how SE was planned and implemented, and demonstrates how Systems Engineering is benefitting the design of the California High‐Speed Train Project (CHSTP).
5.3.2 Information Technology (IT) Project Management Failures: Historical and Evolutionary Walk through from a Social Dynamic Perspective – A Primer to “Preemptive and Adaptive Project Management”
Authors: Stoica Rosana , Brouse Peggy 
Published: November 2014

AbstractDespite the evolution and sophistication of project management, a great percentage of IT projects are still failing. For centuries projects have experienced complex social interdependencies. This paper treats projects within a social context and proposes the investigation of projects management challenges by applying the “social” lens. This construct serves as a primer to introduce system dynamics principles to project management applications to further the current understanding of project “soft” factors and their interdependencies. The authors conclude that a systems dynamic approach using social lens provides the appropriate construct for a new paradigm in IT project management: “Preemptive and Adaptive”. Intangible Soft Factors (ISF's) concept is introduced. The authors hypothesize that this construct provides the appropriate balance to further investigate the ability to successfully manage IT project outcomes by means of understanding the disguised yet bonding and exceedingly influential “social” forces overlooked as a dominant project agent.
6.5.2 MBSE Supports Manufacturing System Design
Authors: Batarseh Ola , McGinnis Leon , Lorenz Jim 
Published: November 2014

AbstractTo date, Model Based Systems Engineering (MBSE) has been deployed primarily in the product design domain. However, manufacturing system design problems are equally challenging, but there are many fewer design support tools in the hands of system designers. This paper describes how MBSE principles and methods can be used to make a powerful analysis tool readily accessible to manufacturing systems engineers. The MagicDraw™ SysML tool was used to create a domain specific language for electronics assembly, and the tool itself was customized to present an interface that was relatively easy for the manufacturing domain experts to use to create descriptions of products, resources, and processes. The domain specific language was mapped to a metamodel of the Arena™ discrete event simulation language, and the ATL© model transformation tool was used to automate the generation of the an instance of a simulation model from an instance of the electronics assembly system. The use of this kind of analysis automation can reduce by up to a factor of ten the time required to develop such simulation models.
7.7.1 Getting the right requirements right
Authors: Kasser Joseph 
Published: November 2014

AbstractResearch has shown that there is an on‐going consensus that:
good requirements are critical to the success of a project
the current requirements paradigm produces poorly written requirements and
ways of producing better requirements have been around for more than 20 years.
So, instead of producing yet another paper on how to write better requirements, this paper begins by posing the following question: why do systems and software engineers continue to produce poor requirements when ways to write good requirements have been documented in conference papers and textbooks? The paper then documents findings from research into the problem via the systems thinking perspectives and hypothesises that there are two requirements paradigms; the original A paradigm and the current B paradigm which is inherently flawed. The paper then dissolves the problem of poor requirements by applying technology to reduce the need for most of the requirements written today.
8.4.1 Assessing Uncertain Benefits: a Valuation Approach for Strategic Changeability (VASC)
Authors: Fitzgerald Matthew E. , Ross Adam M. , Rhodes Donna H. 
Published: November 2014

AbstractThis paper describes a new technique for investigating the value of changeability in complex engineering systems early in the design process. The work is an extension of Epoch‐Era Analysis, a framework that models contextual uncertainties over a system's lifecycle as a sequence of finite‐duration periods of time. Strategies, defined as statements of intended change mechanism usage, are used to identify executed change mechanisms across the various contexts. Changeability is then evaluated in both time‐independent (multi‐epoch) and time‐dependent (era) domains, using a proposed set of metrics designed to explore different dimensions of value. A case study demonstrates the application of the technique to a conceptual space system.