bluuebunny/crossref_metadata_2025_split huggingface dataset:
10.5.1 An MBSE Case Study and Research Challenges
Authors: Do Quoc , Cook Stephen 
Published: November 2014

AbstractModel‐Based Systems Engineering (MBSE) is an emerging practice that provides major advantages over document‐based engineering design approaches: traceability and transparency of the evolving design, improved design completeness, and improved knowledge sharing. The paper opens with an introduction to contemporary systems engineering practice, its limitations and the need for MBSE. Then the paper describes an MBSE case study on the ground‐based air missile defence system, which includes SysML model design and development, lessons learnt and insights, and a set of derived research challenges for future research and development.
11.3.1 Set‐based design – the lean tool that eludes us; Pitfalls in implementing set‐based design in Kongsberg Automotive
Authors: Hansen Elisabeth , Muller Gerrit 
Published: November 2014

AbstractThis paper is based on a five month research project performed at the company Kongsberg Automotive (KA). It describes a study of the implementation of set‐based design in project processes in KA, results from the study, and evaluations of these results. The focus has been on knowledge gaps in relation to the implementation of set‐based design. Data has been gathered through observations, discussions with and feedback from employees, interviews and surveys, as well as literature research in order to evaluate the implementation of set‐based design. A set‐based approach has also been used in this research through the development of a set of theories that were investigated in an effort to disprove them or create a basis to support the probability of the theory being correct.Through this project it has become clear that there are variations in the employees' knowledge on what set‐based design entails. Data show that there is far more agreement on potential goals and benefits of the implementation. This indicates that the employees know where they are going, but that there is some ambiguity as to how to get there. This could be resolved through clarification of the elements of the process and clarification of how the company wants to achieve its goals.
11.5.1 Early Formulation Model‐Centric Engineering on NASA's Europa Mission Concept Study
Authors: Bayer Todd , Chung Seung , Cole Bjorn , Cooke Brian , Dekens Frank , Delp Chris , Gontijo I. , Lewis Kari , Moshir Mehrdad , Rasmussen Robert , Wagner David 
Published: November 2014

AbstractBy leveraging the existing Model‐Based Systems Engineering (MBSE) infrastructure at JPL and adding a modest investment, the Europa Mission Concept Study made striking advances in mission concept capture and analysis. This effort has reaffirmed the importance of architecting and successfully harnessed the synergistic relationship of system modeling to mission architecting. It clearly demonstrated that MBSE can provide greater agility than traditional systems engineering methods. This paper will describe the successful application of MBSE in the dynamic environment of early mission formulation, the significant results produced and lessons learned in the process.
Dependency Analysis in Complex System Design using the FireSat example
Authors: Groß Johannes , Rudolph Stephan 
Published: November 2014

AbstractUsing the FireSat mission from literature (see Larson 1999), the satellite design process is analyzed. Prior to this analysis, the physical and functional properties of the satellite system are encoded in a graph‐based design language. During the automated design language compilation process several graph representations are generated. These graph representations are generated from the design constraints. From the mathematical analysis of the graphs three important interpretations can be derived. The first interpretation concerns the derivation of the exchange rates based on the analysis of the functional coupling. The second interpretation yields a feasible design sequence. Third, a generic backtracking method for resolving engineering design conflicts is presented and illustrated with an antenna example. All three interpretations are illustrated through a detailed view into the FireSat communication subsystem. Furthermore, the demonstration of the method closes with a system‐level analysis of the satellite design process to show its applicability to all levels of detail in system design.
Documents are an Essential Part of Model Based Systems Engineering
Authors: Logan Paul , Harvey David , Spencer Daniel 
Published: November 2014

AbstractModel Based Systems Engineering (MBSE) existed long before the recent emphasis on its merits compared with traditional document‐based methods. Advocates disparage documents per se, failing to recognise their importance as information artefacts essential to MBSE. While the digital data model may be the ‘source of truth’, stakeholders view, verify, and use the model via screen‐rendered artefacts, which if made permanent to any degree, constitutes ‘printing’ a document. This paper examines the nature and use of documents, both paper and electronic, in traditional and model‐based methodologies, and identifies the evidentiary qualities of paper‐based documents required for legal acceptance of electronic documents. Document templates are used to initially structure the model schema, populate the model, and progressively auto‐generate output documents as complex views on the developed system model. The essential need for documents as information artefacts in gathering, developing, maintaining and reporting the ‘truth’ in a model‐based (and model‐centric) paradigm is demonstrated.
Model‐based Interface Specification for Systems Integration in Systems of Systems Engineering
Authors: Gianni Daniele , D'Ambrogio Andrea , Simone Pierluigi De , Lisi Marco , Luglio Michele 
Published: November 2014

AbstractThe key to enable systems integration is that systems inter‐communications are accurately and unambiguously specified. In line with ongoing Model‐based Systems Engineering (MBSE) initiatives aiming to support systems engineering activities by means of formal and graphical models, we have introduced a logical model for the definition of Interface Communication Modelling Language (ICML), to enable a model‐based approach for interface specification. ICML is based on UML and can potentially be integrated with other systems models in similar forms, e.g., SySML, and with systems of systems models in UPDM or related frameworks. We have designed ICML basing on a preliminary domain analysis on radio signal specifications, with application to space systems. In the analysis, we have specifically considered simple digital and unidirectional signals, and subsequently we have included a method to use ICML for Time‐Division Multiplexed signals. We also present an excerpt of the ICML metamodel and a simple example application.
A Performance‐based Statistical Expert Judgment Model to Assess Technical Performance and Risk
Authors: Eggstaff Justin W. , Mazzuchi Thomas A. , Sarkani Shahram 
Published: November 2014

AbstractThe rapidly changing environment and asymmetric threats currently encountered on the modern battlefield requires the timely delivery of effective weapons systems. Unfortunately in fiscal year 2008, according to the US Government Accountability Office, research and development costs of the United States Department of Defense major weapons acquisition programs increased 42 percent above original estimates, and delays in initial operational capability deliveries slipped to 22 months. While there are several quantitative methods to estimate acquisition program cost and schedule performance and to identify their risks (e.g., Earned Value Management), the estimation of technical performance and technical risk identification is generally heuristic in nature and based on expert judgment because of limited quantitative data for constructive modeling. The proposed research in this paper expands upon the Technical Risk Index Distribution method developed by Lewis, Mazzuchi and Sarkani by incorporating a performance‐based method of mathematically combining quantified expert opinion for technical performance estimation and risk analysis.
A Principle Modeling Framework for Software Intensive Systems
Authors: Tomer Amir 
Published: November 2014

AbstractA systematic modeling framework for utilizing UML for effective modeling is introduced, keeping consistency and traceability among the various aspects and elements of the system. The proposed framework defines five conceptual decomposition levels for software‐intensive systems modeling, namely, the Business level, the Software‐Intensive System (SWIS) level, the Computer Software Configuration Item (CSCI) level, the Computer Software Component level (CSC) and the Computer Software Unit (CSU) level. Each system‐element at each level is considered a “system‐of‐interest” on its own, while all of them adhere to a unified common definition of the term “system”. In addition, each of the analysis and design levels is associated with integration and testing level, and a consistent modeling between the operational configurations and the testing configurations is introduced. Consideration is also given to modeling of configurations in other stages of the life cycle. The framework has been successfully deployed and proven usable in a graduate level systems engineering course as well as in an undergraduate software engineering course.
Teaching Them How to Fish: Industry‐Focused Student Projects in Systems Engineering
Authors: Valerdi Ricardo , Zonnenshain Avigdor 
Published: November 2014

AbstractThis paper provides an overview of industry‐focused systems engineering team projects for university students. The projects described are from two universities: the University of Arizona (U.S.A.) and Technion (Israel). The role of such projects in teaching and learning of systems engineering is explored, specifically in the context of constructivist learning theory. Characteristics of successful student projects are discussed together with examples of such projects and their resulting artifacts. We conclude by proposing measures of success of such projects.
Managing and understanding complex systems using traceability and open source software
Authors: Brörkens Mark , Gürsoy Ömer 
Published: November 2014

AbstractBi‐directional traceability from requirements via architecture and design to code and test and vice versa is identified as a good practice for improving the quality of system development processes. This paper provides methodological guidelines for adding traceability to existing tool chains and proposes an implementation based on open source frameworks.
Model‐Based Systems Engineering as an Enabler for Regulatory Design Compliance
Authors: Dean Jered , Henderson Cody , Gardner John 
Published: November 2014

AbstractWhether working in the FDA regulated medical field or explosive industrial environments, using model‐based systems engineering provides the confidence, traceability and structure to meet regulatory requirements. In addition, the authors propose the methodology to be a means to optimize schedule predictability and development of the most appropriate products. In this paper, the systems engineering process being employed is briefly described and two case studies are explored that make the case for MBSE as a key enabler of efficient design to complex regulations.
4.2.1 Can Systems Engineering be Agile? Development Lifecycles for Systems, Hardware, and Software
Authors: Carson Ronald S. 
Published: November 2014

Abstract“Agile” development is alluring because of the promise of shorter cycle times and improved customer satisfaction. Some characteristics of software development and systems (and hardware) development are identified as key differentiators in selecting traditional, plan‐driven vs. agile development. Additional underlying or root reasons are identified to substantiate these differences. These include gated vs. serialized processes, comprehensive vs. incremental system design, independent vs. dependent fabrication, up‐front definition vs. continuous validation, and finish‐to‐start vs. finish‐to‐finish planning and execution. Some additional programmatic and technical criteria are identified for selecting traditional, plan‐driven SE vs. agile methods. The two methods do not appear to be reconcilable when developmental hardware is involved.
Linked Lifecycle Data – Connecting Distributed Engineering Data and harvesting its inherent value
Authors: Fisher Amit , Williams Ben , Matthews Schuyler 
Published: November 2014

AbstractSystems engineers have many different ways to search, locate and analyze engineering data. However, just like in the days before the World Wide Web, this data is being stored, managed and represented in different proprietary formats and locations that make it hard to discover and analyze. In parallel, search engines and Internet style hyperlinks have been proven to be very powerful technologies that change the way we all find and consume information every day. We believe that adopting a similar technical approach can enable organizations to overcome the complexity inherent in modern product design. In this paper we will review this new approach, named Linked Lifecycle Data, and the new opportunities it presents for improving efficiency, quality and productivity in the design and development of complex products and systems.
5.6.2 A Lean Approach to Improving SE Visibility in Large Operational Systems Evolution
Authors: Turner Richard , Lane Jo Ann , Ingold Dan , Madachy Ray 
Published: November 2014

AbstractIt is often difficult to understand the status of capability development in large operational systems. Schedules are rarely stable. This is due to factors such as: the size and complexity of capabilities; unexpected changes in priorities; depth of supplier chains; variety and availability of special engineering resources; contract structure; and the inherently complex nature of such operations. Lean approaches use the concepts of work in progress (WIP) and capacity to maximize flow through a process. Under certain circumstances, these concepts can be applied to systems engineering and development processes. This paper describes an example implementation of the concept in a large health care system of systems. To enhance both visibility and flow, the approach utilizes visualization techniques, pull‐scheduling processes, and a services approach to systems engineering.
4.2.2 A Framework and Metrics for Addressing an Agile Enterprise
Authors: Harris Pritchett 
Published: November 2014

AbstractWhen attempting to design or specify agile solutions for an enterprise with long acquisition timeframes, both the solutions and the enterprise itself must be considered in the same framework to understand the value of time and money spent at one time and performance measured at another. A broad overview of techniques, artifacts, and measurements developed for, and used to, address Enterprise Agility is presented and discussed. Emphasis is placed on treating the distance between both ends of the traditional engineering ‘V’ in a common framework, and on ‘virtual’ feedback between operations and design or portfolio management spaces.
10.1.2 Call for an Effective Alignment of Program Management and Systems Engineering Risk Management Practices
Authors: Arnold Eileen P. 
Published: November 2014

AbstractSystems Engineering (SE) and Project / Program Management (pM / PM) struggle with Risk Management confusion in organizations embracing certifications of the two disciplines. Some of that confusion may remain even if an organization has standardized on their own Risk Management process if it adds yet another view and language of Risk Management (RM) process and activities. This Call is to encourage the collaboration of multiple organizations and standards committees, citing instances where alignment has been achieved and providing twelve recommendations for exploration of opportunities for improved program and systems engineering RM function. This paper is an elaboration of the RM section of last year's paper, (Arnold, 2012) based on the two certification bases. The Systems Engineering Handbook (Haskins, 2011), the Project Management Body of Knowledge (PMBoK) (PMI, 2008), and the Systems Engineering Body of Knowledge (SEBoK) (Pyster et al, 2012) are explored, with other RM contributors.
Clarifying the Context of SE for the SEBoK
Authors: Boehm Barry , Pyster Art , Olwell David 
Published: November 2014

AbstractThe Systems Engineering Body of Knowledge (SEBoK) (Pyster and Olwell 2012) (see http://www.sebokwiki.org) portion of the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) project (see http://www.bkcase.org) involved three years of extensive and intensive discussions among its 70 authors and over‐200 external reviewers worldwide. These helped the SEBoK effort better understand the implications of various candidate definitions of systems engineering (SE)‐related terms and to shape the resulting SEBoK content. This paper focuses on the resulting clarification of four key aspects of SE: (1) What is the historical context of SE? (2) What is the system boundary of SE? (3) Who are SE's users? and (4) What are the relations among SE and other disciplines?
3.5.1 Model as You Write, or Write as You Model – A Grammar‐Based Approach to Modeling and Documentation
Authors: Yamada Takahiro 
Published: November 2014

AbstractModel‐Based Systems Engineering (MBSE) is the formalized application of modeling to support activities necessary for development of systems and is expected to replace the document‐centric approach that has been practiced by systems engineers. Many models of systems are being developed by many engineers, but most engineers still write documents in addition to developing models. This is because the semantics of the models is not embedded in the models and is usually provided in documents.This paper proposes a novel approach to development of documents and models at the same time. In this approach, technical information is encoded with an artificial language. The grammar of this language specifies how the semantics of situations should be encoded into sentences. Generated sentences can be converted to other forms such as diagrams, tables, and/or text in any natural language. Generated sentences can also be converted to electronic data, which can be used by any application program. With this approach, documents can be used as models, too, because documents are written according to strict syntactic and semantic rules. At the same time, models can be used as documents, too, because the semantic information necessary for interpreting models is embedded in the model. This approach can be applied to any technical information, which includes requirement specifications, design specifications, interface specifications, development plans, test plans, test procedures, and operation procedures.
5.2.1 Systems Engineering Complexity in Context
Authors: Sheard Sarah A 
Published: November 2014

AbstractSystems engineering literature identifies many different kinds of complexity. One paper cataloging complexity for the purpose of modifying systems engineering cost estimates identified more than 30 types. The research described in this paper investigates the idea of sorting and organizing the many concepts of complexity and showing the relationships between them on a single two‐dimensional chart.The Systems Engineering Complexity Contexts (SECC) chart was developed to show how a large number of complexity concepts relate to systems engineering and to each other. All but two of the 30 types from the paper mentioned above fit on this chart. Those two appear as aspects that may apply to all other boxes on the chart instead of as orthogonal elements, which was the desired representation.
4.5.2 Model Integration – Extracting Value from MBSE
Authors: Broodney Henry , Shani Uri , Sela Aviad 
Published: November 2014

AbstractModel‐Based Systems Engineering is making its way into the design processes of many Systems builders. But as with any new concept, it must prove its worth by demonstrating significant Return‐On‐Investment. One of the benefits of having designs formalized in models is sharing information, models and data, between designers and teams, and allowing valuable analytics to be performed over that collection of information. This paper will discuss a gradually evolving approach to model integration, sharing and collaboration, from simple indexing and relationship maintenance to comprehensive frameworks for information integration based on the recent advances in ontology‐based data fusion and model transformations.
Developing an Allocation of System of Systems Requirements for Border Security
Authors: Flanigan David , Brouse Peggy 
Published: November 2014

AbstractDuring the initial concept development of a System of Systems (SoS) capability, a methodical process is required to develop the SoS requirements and then allocate them to their constituent systems. Review of existing Systems and SoS Engineering requirements literature do not identify such a process. This paper develops a process in order to create the SoS requirements, decompose and allocate them to their systems, develop a model to represent these requirements, and then assess their allocation properties.
A Semantic Framework for Systems Engineering Standards
Authors: Price David , Feeney Allison Barnard , Jones Albert 
Published: November 2014

AbstractSystems engineers and asset managers create and maintain models of components and systems associated with long‐lived, engineering assets. Component models come from many domains, disciplines and applications. System models typically require integration of these component models. This paper presents the results of an investigation into the convergence of three distinct themes: the growing numbers of standards for engineering data, the maturing of Semantic Web technology, and a framework for architecting and relating engineering vocabularies and data. This investigation sought to determine whether these themes, used together, could enable industry to make significant progress toward model‐based systems engineering in the areas of collaboration, knowledge management, data integration and timely decision making. This paper argues that semantic technologies have matured to the point where they should be the preferred choice for developing future standards and frameworks.
10.4.1 Goals for a New Paradigm of Behavior Modeling
Authors: Brown Barclay 
Published: November 2014

AbstractThe goal of this approach is to develop a new paradigm integrating the practices of business process modeling and use case modeling. These two modeling approaches describe the behavior of organizations and systems, and their interactions, but rest on different paradigms and serve different needs. An integrated approach would have advantages in efficiency, consistency and completeness of the overall behavioral model. In many cases, business process modeling is employed as a precursor to the development of a system to be used in a business organization. Developing a new paradigm and modeling approach that achieves the objectives of both business process modeling and use case modeling in an integrated form, in one analysis pass, should result in time savings, increased accuracy and improved communication. This paper presents a set of goals for the new paradigm and modeling approach.