bluuebunny/crossref_metadata_2025_split huggingface dataset:
A Practical Guide to Statistical Verification
Authors: Kolozs James , Black Carissa 
Published: September 2016

AbstractStatistical techniques are required for medical devices and can be used to make verification more meaningful in any industry. Sometimes, a company needs to predict how their total population of devices will perform. Other times, teams simply need stronger justifications than ‘that's how many we had’ or ‘we always test 5’ for test plans and sample sizes. However, there are an overwhelming number of statistical methods and references available. We have identified three tests that can be used to verify many types of device requirements: pass/fail (binomial), tests on the population (tolerance interval), and tests on the mean (t‐tests). This paper provides the information needed to choose a test, pick the right statistical claim and related parameters, determine the sample size needed to pass, and write acceptance criteria that makes it easy to determine a pass or fail.
The Best of Both Worlds: Agile Development Meets Product Line Engineering at Lockheed Martin
Authors: Gregg Susan P. , Scharadin Rick , Clements Paul C. 
Published: September 2016

AbstractAgile development has long been touted as way to optimize software development team efficiency and improve project success. Product line engineering (PLE) brings large‐scale improvements in cost, time to market, product quality, and more. Can these two paradigms work in concert with each other? This paper details the experience of Lockheed Martin as it introduced large‐scale agile development practices on one of its largest and most successful product line engineering efforts.
Agile Systems Engineering Process Features Collective Culture, Consciousness, and Conscience at SSC Pacific Unmanned Systems Group
Authors: Dove Rick , Schindel Bill , Scrapper Chris 
Published: September 2016

AbstractSPAWAR System Center Pacific (SSC‐Pac) in San Diego has established an Unmanned System Integration, Test, and Experimentation (UxSITE) capability to facilitate agile development of unmanned systems. This capability utilizes a unique agile systems engineering process with 6‐month overlapping “waves” consisting of four phases: development by multiple‐subcontractors, and operational management of systems architecture evolution, capability integration, and validation testing. The UxSITE capability supports a portfolio of projects, and has three years of respected and effective results. Most notably, the process puts a prime emphasis on enabling and facilitating team effectiveness: creating an embraced culture of engagement, a collective consciousness emerging from comprehensive real‐time information support, and a team conscience on a mission for the end users.
Architectural Technical Debt in Embedded Systems
Authors: Martini Antonio , Bosch Jan 
Published: September 2016

AbstractThe introduction of Agile Software Development in large companies developing embedded systems aims at shortening the time‐to‐market for new business value for the customers. However, evidences show how system engineering needs to be integrated in the process in order to avoid the degradation of architectural system qualities. Such phenomenon has recently been identified with a financial metaphor, Architectural Technical Debt, which maps sub‐optimal architectural solutions to taking a debt, and its costly impact into an interest to be paid in the long term. Through a multiple case study in 5 companies, we show what are the current practical challenges related to the long‐term accumulation of Architectural Technical Debt, and how system engineers need to track and manage such phenomenon in order to avoid costly impact such as development crises and costly re‐design.
Emergent Failure Modes and What to Do about Them
Authors: Harris Steven D. , Narkevicius Jennifer M. 
Published: September 2016

AbstractThis paper sets out to identify a means to mitigate the effects of unpredictable failures in complex systems. It outlines a formal analysis of complex systems that focuses on emergent system dynamics, some of which may be failure modes that are impossible to predict. The mathematical basis for the analysis, and some real‐world implications of the mathematics are introduced. From that same formal analysis, the paper identifies specific characteristics of system architecture to mitigate the risk of emergent failure modes. The paper concludes with an approach to mitigating the effects of EFM predicated on a principle‐based process architecture called intelligent control theory.
Graphical Modelling of a Meta‐Model of CAD Models for Deep Drawing Tools
Authors: Scheffler Robert , Murugan Vishnu Prashanth , Wrobel Gregor , Pleßow Matthias , Koch Sergej , Buse Christian , Behrens Bernd‐Arno 
Published: September 2016

AbstractFully parametric 3D CAD models of deep drawing tools require an enormous amount of temporal and financial effort which makes design engineers shy away from it. The Institute of Forming Technology and Machines (IFUM) and the Society for the Advancement of Applied Computer Science (GFaI) are currently developing a new method for the model driven design of deep drawing tools. The core of this method is a graphical modelling language for this domain that is based on and compatible with SysML but improves several diagram types. The new language aims to make the modelling of parametric relations and dependencies easier and less error‐prone.
Experience from integrating Domain Driven Software System Design into a Systems Engineering Organization
Authors: Hammarström Pär , Herzog Erik 
Published: September 2016

AbstractDeveloping software intensive safety critical systems is a challenge, even when Model Based Systems and Software engineering methods and tools are applied. This paper recounts the challenges encountered when combining the traditional Systems Engineering approach with that of software Domain Driven Design in the development of the Gripen E fighter aircraft. Systems Engineering and Domain Driven Design are compared to identify similarities and differences. Areas where special attention is required are identified. The main issue identified is that the System structure identified, will not conform to the domain structure identified using the Domain Driven Design approach. Moreover, to accommodate for proper domain analysis the Systems Engineering Architecture design process must be augmented with an Analyze and Generalize step in order to capitalize on the benefits of Domain Driven Design.
A Systematic Process for Functional Decomposition in the Absence of Formal Requirements
Authors: Brimhall Erika , Wise Richard , Simko Ryan , Huggins John , Matteson Whit 
Published: September 2016

AbstractA systematic approach is needed for developing implementation‐agnostic functional decompositions in the absence of formal requirements. This paper introduces a process for producing robust functional decompositions that provide full coverage of system functionality, enable consistency throughout the system architecture, and promote reusability of functions. The process uses activity diagrams to provide precise semantics, and defines concepts that support the development of robust implementation‐agnostic functional decompositions. The process has been successfully demonstrated through the functional decomposition of avionics software.
MBSE for Engineering Students
Authors: Fernández José L. , Moreno Guillermo 
Published: September 2016

AbstractThe demand of new complex products shifts development from largely mechanical engineering to the interdisciplinary systems engineering. So, a systems‐driven approach is critical to success in engineering complex products that consist of interdependent mechanical, electrical/electronic parts, and software modules. The paper presents a Model Based Systems Engineering learning approach where the main emphasis is on applying a modeling process rather than using complex notations or expensive tools. The results are illustrated with the final degree work of a student dealing with the preliminary design using SysML notation of a robotic system for the reconnaissance of victim bodies in natural or man‐made disaster areas. The combination of a MBSE process with the knowledge of some engineering technical specialities related to the solution is a key factor of the students’ projects success.
A New Resilience Taxonomy
Authors: Thompson Marcus A. , Ryan Michael J. , Slay Jill , McLucas Alan C. 
Published: September 2016

AbstractSince security is an enduring high‐priority consideration for both individuals and communities, many security methodologies have been proposed. Yet none of these methodologies has achieved a lasting impact on the current security and resilience issues faced in modern society. Methodologies use terminology that is inconsistent, overlapping, contradictory, or contains language that is specific to the domains of physical, electronic, and personnel security. Further, the majority of modern terms focus almost exclusively on electronic or cyber security. Consequently, the current set of security terms and definitions provide little assistance to stakeholders when articulating requirements, nor to systems designers when defining system architectures. Current security‐related resilience terminology is similarly confused, with a lack of commonality, domain‐specific language, and terms used synonymously to blur the distinction between security and security‐related resilience. This paper builds on previous work to present a cohesive taxonomy of security‐related resilience that is applicable across the physical, electronic, and personnel domains.
Independently Developed Systems Engineering of China's Aerospace Industry
Authors: Xue Huifeng , Zheng Xinhua 
Published: September 2016

AbstractChina's aerospace industry has gained great achievements in past years, systems engineering (SE) is an important contribution for the success. China's aerospace industry developed independently and continually refined SE according to the circumstances and situations, the China aerospace SE has distinct characteristics and suitable for Chinese society, economy and technology. China Academy of Aerospace Systems Science and Engineering (CASE) has done a lot of work to explore the origin, development process and content of China aerospace SE, and to spread the approach to society and economy areas. This work offers beneficial references for other countries to develop their native SE for the aerospace industry.
Systems Engineering Process for the OSIRIS‐REx Camera Suite (OCAMS)
Authors: Merrill Catherine , Williams Bradley 
Published: September 2016

AbstractThe OSIRIS‐REx Camera Suite (OCAMS), built at the University of Arizona, is a mission‐critical suite of cameras for the OSIRIS‐REx asteroid sample‐return mission. It is comprised of three cameras used together to support the threshold mission objectives. The OCAMS systems engineering team developed a process to prepare verifiable requirements and create the associated test program. This process ensures the instrument performs all required functions for the mission operation and science requirements. The process was dynamic and sufficiently flexible to conform to the development process and mission schedule. The structure of the requirements, as well as the integration and test program, allowed the OCAMS team to adapt to changing circumstances and recover schedule to support an on‐time delivery following hardware delays. The OCAMS process has been incorporated into other OSIRIS‐REx payload elements. This paper discusses the process used by the systems engineering team. Italicized texts denotes case study.
The future of systems integration within civil infrastructure: A review and directions for research
Authors: Whyte Jennifer 
Published: September 2016

AbstractWhat is the future of systems integration within civil infrastructure? This paper provides a background to systems integration; articulates the challenges of civil infrastructure in the mid‐21st century; and reviews the state‐of‐the‐art in research on systems integration in the delivery and operation of civil infrastructure. Building on the literature review it highlights opportunities that arise through reframing from projects to systems (and systems of systems), and using the potential of new forms of data analytics. It sets out a research agenda for next generation tools to visualize and understand civil infrastructure as a complex product system.
Improve Medical Device Development by Expanding Systems Engineering
Authors: Black Carissa J. 
Published: September 2016

AbstractMost members of the medical device design community are familiar with the term systems engineering, but their definition is often too narrow in scope. To maximize value, each team should have a systems engineer that serves as technical lead for the project and has overall ownership of the design and its full traceability. When a systems engineer has ownership of all traceability, it will lead to stronger regulatory submissions. When they have responsibility for identifying requirements issues or gaps throughout the design process, design changes will be identified earlier. By understanding the big picture of how all of the medical device deliverables relate (trace) to each other, the systems engineer will empower each function to consistently focus effort in high‐impact areas. When a systems engineer is the technical lead, they ensure that decisions and changes are communicated and reflected in the design documentation. It also means that they can remain neutral with stakeholders on key decisions, and allow the project manager to maintain the team balance by advocating for cost and time to market control.
The Reference Designation System (RDS) A common naming convention for systems and their elements
Authors: Balslev Henrik 
Published: September 2016

AbstractThis paper introduces the Reference Designation System (RDS) as defined in the ISO/IEC 81346 standard series. The 81346 standard is a horizontal standard within ISO and IEC, and thereby a reference document for all other international standards. RDS identifies systems and their elements. A reference designation (a TAG number) is the output of RDS. The TAG numbers act as labels for the system and the system elements, and are used for instant and unambiguous recognition across different kinds of documentation and labelling of tangible products as well as non‐ tangible products such as different models in a software tool. RDS is an international “naming convention” designed for systems and their elements and a practical technique to underpin a common understanding among different disciplines. The use of RDS as a fundamental system naming convention is not widely known within the INCOSE environment. By this paper, the author wishes to reach out to INCOSE and systems engineering in general, so the principles of RDS is to be better understood and recognized as a basic part of systems engineering tool box. RDS provides generic principles and are applicable in more or less all technical disciplines; among these are civil engineering, mechanical engineering, electrical engineering and software engineering. Application examples are provided and a case example showing the economic benefit is presented.
Making Smart Cities Smarter – MBSE Driven IoT
Authors: Hause Matthew , Hummell James 
Published: September 2016

AbstractThe Internet of Things (IoT) is a system of systems (SoS) in every sense of the definition. A.P. Sage and others list five common SoS characteristics: operational independence of the individual systems, managerial independence, geographical distribution, emergent behavior and evolutionary development or independent life cycles. Typical examples include smart houses, the electric grid, complex military systems and so‐called smart cities. The future of IoT success, including technology advancements and revenue generating potential across the business spectrum, is dependent on the application of solid Systems Engineering and Model Based Systems Engineering (MBSE) principals. Without MBSE, the complexity involved in the design, development, and deployment of IoT systems would consume both system and operational providers. Absent of any industry standards, IoT systems cannot be built in a vacuum and their success will only be realized through application of modern day systems engineering processes, methods, and tools. With the potential of 28 billion “things” connected to the Internet by 2020, it's not too difficult for anyone paying attention to this emerging technology trend to envision the massive scale of social, economic, and technological changes that will need to occur to realize this prediction. Technology advancements in consumer products will continue to evolve to facilitate connection to larger and larger IoT networks. This will be the catalyst that will drive entire infrastructures changes to: Federal, State, City, and local governments; product development companies; utility and service providers; and even to consumers and their homes in order to support the growing demand for connected products. The infrastructure and management will need to be established prior to, or in conjunction with, the smart systems that support them. This paper will show a traffic management system and connected systems in a large city and how an MBSE and SoS approach will help guide development.
The Value of Systems Engineering in Project Management: Case Study: Developing a Power Control System ConOps
Authors: Turner Steven , Mididaddi Vijay , Hoehne Oliver 
Published: September 2016

AbstractThis paper presents a case study on an innovative Project Management (PM) and Systems Engineering (SE) approach that utilized elements of Agile and Lean principles. The scope of work required the development of a Concept of Operations (ConOps) for the upgrade of a power control system (PCS). The ConOps was delivered within a demanding 14 week timeline with a team geographically distributed across 8 time‐zones, within a fixed scope and budget.The ConOps document was treated as a system and delivered in increments similar to how the methodology ‘Scrum’ is used as the Agile Product Development Framework and the Lean Product Development Flow (LPDF) method for projects. The ConOps ‘system’ was delivered early and over a number of ‘sprints’, providing each time a valuable and ‘shippable’ product (the ConOps document) to the Client.
Applying INCOSE Rules for writing high‐quality requirements in Industry
Authors: Fuentes Jose , Fraga Anabel , Génova Gonzalo , Parra Eugenio , Alvarez Jose María , Llorens Juan 
Published: September 2016

AbstractThe present paper introduces an implementation of some INCOSE guidelines for writing high‐quality requirements in industry, it presents the benefits of applying techniques, methods and tools in order to improve the Systems Engineering Process. It is also proposed an evaluation of the impact in the quality of requirements.
Systems Architecting for a Retrofittable Subsea System Application
Authors: Baker Jason , Ferraioli Patrick , Pereira Luis R. , Hudson Abram 
Published: September 2016

AbstractThis paper highlights a model‐based systems engineering (MBSE) approach tailored to the unique complexities of developing a consistent functional and physical architecture for retrofittable subsea equipment used in offshore deepwater operations. A new architecture in this application must satisfy demanding requirements in safety, reliability, availability, maintainability, retrofittability, deployment timelines, and interface compatibility. Additionally, the new architecture must be defendable against the industry's decades‐long established regulatory, cultural and technological legacies. To objectively design within these constraints, a system model was developed iteratively using both bottom‐up and top‐down analysis to define a complete functional and physical architecture. Inconsistencies between the functional and physical models encountered are resolved through detailed functional analysis and product realization process. The hybrid bottom‐up, top‐down approach employed, supports continuous stakeholder validation and requirements verification. The tailored MBSE approach and conceptual functional and physical models are presented.
Using systems thinking to improve natural resource governance and strengthen weak networks
Authors: Malan Suzi 
Published: September 2016

AbstractThis paper reports on the decision‐making processes in international conservation as found in two southern African case studies, the Greater Limpopo Transfrontier Conservation Area, and the Greater Mapungubwe Transfrontier Conservation Area. Using systems thinking to approach the model of cross‐border natural resource governance and management provided insights at the landscape scale, particularly regarding the absence of a physical institution that can be evaluated and consequently improved. The overall objective of the research project was to consult with all layers of decision and policy makers involved in order to synthesize the current state of knowledge, identify the range of potential incremental effects of management responses on natural and human systems, and determine the range of values that drive decision‐making processes. The methodology involved analyses of semi‐structured interviews with stakeholders involved in the TFCAs, as well as relevant policies and treaty documents. The findings in the governance and decision making sphere were analysed using Capability Maturity Model theory and the NATO Network Enabling Capability Model theory. The main recommendations suggest improving involvement in decision‐making processes from the grass‐roots or community level, developing communities of practice between the different countries and core protected areas, prioritizing policy harmonization, and establishing a physical TFCA unit with dedicated, longer term staff instead of the current brief rotational cycle. The same Capability Maturity Model theory was then applied to a different type of network; the Regional Inter‐Agency Standing Committee, an informal network of humanitarian aid agencies and organizations. The latter research is an ongoing project, but preliminary results show that strengthening a central platform or institution can greatly improve the connections between entities within a system of systems, as well as the performance within each individual entity.