bluuebunny/crossref_metadata_2025_split huggingface dataset:
2.2.2 A Decision Support Framework for the Software Systems Engineer
Authors: Knapper Robert J. , Brouse Peggy S. 
Published: November 2014

AbstractDecision Support Systems have been developed to aid the decision maker by providing ranked alternatives to consider. The ranking criteria may be resource‐based, schedule‐based or performance‐based. When considering decisions that affect the overall architecture of a software system and the integration of its subsystems/components, the software systems engineer may have some unique challenges when legacy software is part of the system. For the software systems engineer, reengineering legacy systems or integrating legacy systems with new development and/or off‐the‐shelf software are areas where effective software system analysis is critical. When analyzing a software system, a range of system artifacts may be used. These artifacts include a description of the system in natural language, program design language descriptions, flow charts, object diagrams, as well as the system code. All of these artifact types can contain equivalent information at their specific level of abstraction. However, deriving information that is needed from each of these types of artifacts for reengineering or integrating a legacy system may present varying levels of difficulty. For example, analyzing a poorly structured system with little or no design documentation is a particularly challenging problem. Software modelling using an abstract architecture representation as a common description vehicle can “level the playing field” by creating representations of disparate systems at the same level of abstraction. This is of importance to reengineering efforts; it shows promise for supporting and facilitating integration efforts between legacy and other systems. It also allows the definition and development of a framework for a decision support system to aid the software system engineer. This paper is a follow on to previous work by the authors and presents a proposed decision support system framework that makes the use of the technical analyses and techniques presented.
3.6.1 Rapid prototyping and validation of Human factors model in a Model Based Naval Systems Engineering Application
Authors: Gopinathan H. , Tocci A. , Ciambra F. , Frisoni D. 
Published: November 2014

AbstractThe Model Based System Engineering (MBSE) approach focuses on building an architecture model which is portable to different platforms, re‐usable and interoperable among different domain models. This allows integrating the Human Machine Interface (HMI) model or the Human Factors domain model with the System architecture model seamlessly.MBSE ensures the separation of user specifications from the way the system utilises the capabilities/technologies of the target application platform. Thus a Platform Independent Model (PIM) of the HMI is developed, mapping the end‐user/operator specifications. This model is then transformed to Platform Specific Model (PSM) meeting the requirements/technologies of the specific platform using rapid prototyping.This paper discusses the generation of HMI Prototype from a PIM for a Naval Combat Management System (CMS) using the application codenamed ModVis. It also addresses the advantages of an early Verification and Validation (V&V) of the system model and visualisation of a preliminary prototype of the system early in the project life cycle.
6.5.1 A collaborative process based on systems engineering and mechatronics methods
Authors: Caron Françoise 
Published: November 2014

AbstractThe laws of physics bring into play geometric dimensions and directions. Consequently, systems engineering can in no way ignore the reciprocal effects of choices concerning the system's geometry and architecture on expected performance (electromagnetic phenomena, heat propagation and pressure loss, for example, are recurring issues in systems engineering projects).Such challenges elicit the need to define which processes and methods would permit to concurrently design a system's architecture, its geometry, and the three‐dimensional layout of its constituent parts.The purpose of this report is to present elements of an answer to this need. They were provided by a systems engineering methodology based on system architecture and three‐dimensional models as well as functional models. Based on modeling and simulation techniques, this methodology was developed and applied as part of the O2M research project sponsored by the competitiveness clusters System@tic and Moveo (two French agencies promoting applied research projects that bring together research laboratories, large industrial groups, and small and medium‐sized organizations).
7.2.2 An Introduction to Applying Systems Engineering to In‐Service Systems
Authors: Ven Marcel Van De , Talik Joe , Hulse Jon 
Published: November 2014

AbstractThere is emerging consensus within the Systems Engineering (SE) community that, while the principles underpinning SE remain the same across the lifecycle:
Some of the issues concerned with sustaining existing systems are more problematic than when realizing new systems; and
The existing SE Body of Knowledge and the competences of SE practitioners tend to focus on the issues that are more important when realizing new systems than on the issues that are more important when changing existing systems.A UK working group on Applying SE to In‐Service Systems looked into difficulties in this area and produced a report containing draft guidance and recommendations for further action. These recommendations were recognized by INCOSE and consequently the International In‐Service Systems Working Group (“the ISSWG”) was set up in 2009 with the following objectives:
To consider the work of the UK Working Group and extend and adjust it as necessary in order to provide improved advice on the difficulties encountered in practice in applying authoritative guidance on SE, including the INCOSE SE Handbook, to systems which are in service and best current practice in adapting SE guidance to overcome these difficulties; and
To consider the current channels by which INCOSE promulgates advice on good SE practice, including the SE Handbook and the SE Book of Knowledge and make recommendations on how additional guidance on performing SE on in‐service systems should be integrated into these channels.
7.2.3 FasTracks Transit Program Oversight using Systems Engineering Principles
Authors: Stokes Timothy 
Published: November 2014

AbstractThe Regional Transportation District (RTD) FasTracks Program is a multi‐billion dollar transit expansion plan to build 122 miles of new commuter rail and Light Rail Transit (LRT) lines, and 18 miles of Bus Rapid Transit (BRT) in the Denver region.RTD recognized that programmatic risk, inherent in the cost, schedule, and quality aspects of such a complex program, needed to be mitigated through a comprehensive Oversight Program. A systematic requirements based oversight approach was developed based on the principles of Systems Engineering to manage complexity. This Oversight Program is modeled on a Systems Engineering V‐framework.Utilizing risk management to focus oversight efforts, requirements are verified by RTD's oversight staff throughout a project's life cycle. A web‐enabled database application is utilized to collect oversight data, which helps to ensure that requirements are verified at the system, subsystem, and component levels of the work breakdown structure. Useful information derived from the Oversight Program is fed‐back to program participants to enable continuous improvement of the program's management systems, thus reducing programmatic risk.This paper discusses the application of RTD's tools and techniques used to oversee the FasTracks program and how Systems Engineering principles can be used to reduce programmatic risk for large transit programs.
7.4.3 Understanding Airlines' Value Perceptions for Value‐Based Requirements Engineering Of Commercial Aircraft
Authors: Zhang Xinwei , Auriol Guillaume , Eres Hakki , Baron Claude , Kossmann Mario 
Published: November 2014

AbstractAlthough Systems Engineering (SE) processes and standards are widely used in aircraft development programs, traditional requirements engineering practice for commercial aircraft does not explicitly address value perceptions and related, relevant information. In this paper, a novel approach is proposed to promote a better understanding of customer value perceptions for value‐based requirements engineering. The approach is a four‐step process leading from initial customer statements to component value models. A set of theories and methods is introduced in order to resolve the different concerns regarding the appropriate understanding of customer value perceptions, and based on these, the establishment of the requirements. A case study is used that shows the transformation of airlines' initial expectation statements into a corresponding group value model, which supports the first two steps of the approach. The benefits of this approach are that perceived customer value can be explicitly qualified and quantified; and subsequently used reactively for design evaluation, and proactively for value‐driven design.
7.5.3 Common Sense – Uncommon Practice? Capability engineering examples from Rail and Defence
Authors: Kemp Duncan , Mollett Jennifer 
Published: November 2014

AbstractWhilst there is a significant amount of information available on systems engineering of products, there is significantly less information available on how to systems engineer operational capabilities1.In some respects this is surprising – it is the operational capability that the sponsor requires –whether it is the ability to move large numbers of people into and out of central London, or to establish and sustain a bridgehead in enemy held territory.The paper describes an approach to developing operational capabilities. It describes how capability engineering can be viewed from several perspectives, including:
An enquiry based perspective describing the seven key questions that all capability engineering programmes need to address if they are to be successful
A structural perspective describing the relationship between purpose, operation concept, capability design and individual components of capability
A process perspective describing the activities that need to be undertaken from realising there is a capability gap through to demonstrating that the new/changed capability has improved the situation
The paper describes the interrelationships between the three perspectives, when to use them as part of Capability Engineering activities and why they are necessary and probably sufficient. The discussion topics in this paper are illustrated with two case studies from the Defence and Rail industries.Finally the paper suggests that the effectiveness of using the different perspectives will vary with the maturity of the organisations' capability engineering. Where capability engineering maturity is low the enquiry based perspective will be most useful, where it is more defined the structural and process perspectives will be more effective.
9.4.1 Synergies between INCOSE SE Handbook, CMMI and DO‐178B
Authors: Monzon Antonio 
Published: November 2014

AbstractOne of the biggest challenges in multi‐normative organizations, in the field of industrial areas like aerospace and defense, is to make all technical regulations compatible. A huge amount of effort is spent by these organizations to maintain their accreditations periodically. Although each standard has its own purpose and appraisal procedure, it seems to be useful to know about the commonalities among norms, as well as extracting best practices from the application of its requirements to the accomplishment of the others. Particularly the INCOSE Systems Engineering Handbook can be considered as general lifecycle framework for systems, the Capability Maturity Model for Integration (CMMI) is a reference model to assess the process efficiency and RTCA DO‐178B can be used as basis for software certification. In literature very few contributions can be found to explain how these standards interrelate and how they can work together to achieve more efficient organizations. This experience paper aims to shed some light on the common aspects of these three standards applicable for the production of on‐board software. The combination proposal included in this paper is the result of the experience of the author in the application of these standards (and others) in the military avionics domain. Conclusions could be useful for their application to other domains or even for future potential combined accreditations.
10.2.1 A Framework to Institutionalize Systems Engineering Skill‐Set
Authors: Jahangir Ebad 
Published: November 2014

AbstractSystems Engineering (SE) has been variously defined as an approach, discipline, process, practice, or similar other terms. Each of these terms presents issues especially when compared to other traditional engineering specializations. It is best to think of SE as a skill‐set that can be promoted among the engineering population in general but, more importantly, in a smaller group whose members lead multidisciplinary groups (e.g. chief engineers). A specific skill‐set is derived from INCOSE and NASA competency models using a design structure matrix type approach. This framework uses commonly understood terms in the industry to encourage adoption by a company's engineering leadership. It is recommended that large engineering companies encourage the SE skill‐set by including key SE experts in technical career ladders. The formation of an SE tools and methods group is also recommended that can drive and harmonize SE practice in all technical areas of a large engineering company.
10.3.2 Systems Engineering Lite
Authors: Kolozs James , Henderson Cody , Gardner John 
Published: November 2014

AbstractAn approach is presented (termed Systems Engineering Lite) in which systems engineering is adapted to address small to medium sized projects by combining the roles of project manager and systems engineer and by utilizing a simplified set of systems engineering tools. This approach brings the systems engineering benefits of managing complexity and increasing communication and understanding of the system to a wider range of companies, industries, and project sizes than is traditionally the domain of systems engineering. Our experience has been that this approach results in reduced project costs, happy customers, and more successful projects.
10.5.2 Three years of MBSE for a large scientific programme: Report from the Trenches of Telescope Modeling
Authors: Karban Robert , Zamparelli Michele , Bauvir Bertrand , Chiozzi Gianluca 
Published: November 2014

AbstractThe most ambitious projects of the European Southern Observatory's (ESO) is the construction of the European Extremely Large Telescope (E‐ELT) which will be by far the world's largest optical and near‐infrared telescope, and. will provide images 15 times sharper than those from the Hubble Space Telescope. Such a project poses continuous challenges to systems engineering due to its complexity in terms of requirements, operational modes, long operational lifetime, interfaces, and number of components. Since 2008 the Telescope Control System (TCS) team has adopted a number of Model Based Systems Engineering (MBSE) practices in order to cope with the various challenges ahead. This paper provides an overview of the different approaches we took during this time ‐ which ones worked, and which did not.
11.1.1 Agent‐Based Modeling for Smart Grid: Application to Consumer Reaction to Demand Response
Authors: Lewe Jung‐Ho , Miller Michael Z. , Kelly Kristin M. 
Published: November 2014

AbstractThe Smart Grid is a large‐scale endeavour to accommodate future electric power needs. It plans to deploy innovative technologies for higher level of system efficiency and sustainability. A solid understanding on multitude facets of this challenge is vital hence a system‐of‐systems perspective was adopted. The resulting model was created to capture dynamics between the supply and the demand aspects, underpinned by agent‐based modeling and simulation techniques. After defining the consumer agent and the environment that includes the external and internal factors with which the agent interacts, a baseline simulation run was performed to verify the correct interactions between the agents and their environment. A sample Demand Response scheme was implemented to demonstrate the model and the results were compared with the baseline at the individual agent and the aggregate levels. This model demonstrates the capability and the insights that systems engineering techniques, such as agent‐based modeling, can bring to Demand Response evaluation for a Smart Grid system.
11.4.3 Impact of Agile Process in Systems Engineering
Authors: Pamujula Suresh , Thoppay Rajesh , Kelly Kristin , Fish Rusty 
Published: November 2014

AbstractThis paper explores how Agile techniques can be adopted in the structured system engineering process in delivering System of Systems (SoS). In doing so, the impact of following Agile processes and how priorities are handled in a corporation that is more product centric and profit‐loss driven will be discussed. The paper addresses the lessons learned from the integrating various products that make the SoS. Effects on the overall delivery of the SoS will be discussed including factors like system‐level knowledge, tools, organization structure and global teams. Finally, the paper will highlight some the recommendations that would be applicable for program management in system engineering who want to adopt Agile based techniques for software development and overall delivery of SoS. This paper is intended to provide a case study for applying Agile processes in a SoS context in a commercial environment.
Agile Collaborative Systems Engineering ‐Motivation for a Novel Approach to Systems Engineering
Authors: Asan Emrah , Bilgen Semih 
Published: November 2014

AbstractWell‐established systems engineering approaches are becoming more inadequate as today's systems are becoming more complex, more global, more software intensive, more COTS/re‐use based and more evolving. The changes in the organization and management of such systems of systems projects make it even more difficult for traditional systems engineering approaches. Increased level of outsourcing, significant amount of subcontractors, more integration than development, reduced project cycles, ecosystem like collaborative developments, software product lines and global development are some of the changes in the project life cycle approaches. In this paper, we gather and synthesize the current literature to highlight the need for an agile systems engineering approach and to characterize its agile properties in order to support our motivation for a novel systems engineering approach for large scale software intensive systems of systems projects.
Developing the Modeling Recommendation Matrix: Model‐Assisted Communication at Volvo Aero
Authors: Rypdal Rasmus Wibe , Muller Gerrit , Pennotti Michael 
Published: November 2014

AbstractVolvo Aero Norway (VAN) is a manufacturing company specializing in the production of high precision aerospace components for both commercial and military jet engines. VAN has, as a high‐end production company, a highly diverse set of stakeholders in their employees, customers and suppliers. It is therefore a definite need for VAN to have personnel that can communicate efficiently between stakeholders to be able to complete projects and optimize production in order to sustain their competitive position.Using systems modeling is a known technique to aid communication, raise understanding and create debate surrounding any given system of interest. By measuring the value, in regards to the aforementioned effects of modeling, of the work being performed at VAN we can discuss the usefulness of modeling‐based communication. We will examine the connection between a stakeholder's distance to a given system and the optimal level of modeling detail and novelty.In this paper, we will discuss model effectiveness based on balancing impact factors based on stakeholder's system proximity. We will classify and evaluate models in a 2D‐Matrix and present recorded trends at VAN.
Estimation: A Paradigm Shift towards Dynamic Design‐to‐Cost and Radical Management
Authors: GILB TOM 
Published: November 2014

AbstractAccurate estimation is impossible for complex technical projects, but keeping to agreed budgets, and deadlines is achievable by using feedback and change. In other words, rather than trying to improve the initial project estimates, the budgets and deadlines must be set, based on the value of delivery (not the cost), and then iterative re‐engineering of product and process must be used to stay within acceptable resource bounds. Or at least iteration must be used to get most of the expected value delivered, within the acceptable budgets and deadlines. This paper explains the background to this approach and discusses its use providing several examples.
Managing Concurrency in Systems Engineering
Authors: Scheithauer Dieter 
Published: November 2014

AbstractThe engineering of complex products and services cannot be performed without iterations. Products and services with a multi‐level system architecture and a reasonable number of system elements usually show development activities on individual system elements performed in parallel. The development of each system element is widely managed independently. This paper is concerned with managing concurrency resulting from both, the iterative nature of systems engineering per se, and the multiple projects for developing all the system elements.Lean systems engineering is promising improvements to the systems engineering process in general. However, lean systems engineering is still evolving. Particularly, the integration with all other system life cycle processes needs to be progressed without compromising the lean paradigm. In this paper, amendments to the current state of lean systems engineering are proposed in order to close some of the gaps.
Systems thinking in the planning of military operations
Authors: Greeff A.P. 
Published: November 2014

AbstractThe execution of a Military operation has an analogy to a development project which has the objective to develop a complex product system (victory). This product Performance (victory) must be delivered within a certain time, cost and operational context. Vital to any successful development project is planning, and for complex development projects, good planning is imperative.The result of a complex product development planning cycle, results usually in projects with tasks which resembles a systems life cycle approach. Similarly a complex military operation has the characteristics of delivering a product within time cost in an operational context. Just as a complex product is developed by means of a systems approach, planning could be performed by means of the application of systems thinking.
Using the Guide to the Systems Engineering Body of Knowledge (SEBoK version 0.5) for Undergraduate System Engineering Program Assessment
Authors: Parnell Gregory S. , McCarthy Daniel J. , Hardman Nicholas , Yale Gary E. 
Published: November 2014

AbstractThe draft of the Guide to the Systems Engineering Body of Knowledge (SEBoK version 0.5) was released in a wiki format on September 19, 2011. This paper uses SEBoK to assess the undergraduate systems engineering programs at the United States Military Academy at West Point and the United States Air Force Academy. Both ABET accredited engineering programs educate cadets in to be future leaders of character in their respective military services. We first review the rationale for undergraduate SE programs at the academies. Next, we compare the two programs including their program objectives, student outcomes, curricula, enrolments, and graduate assignments for each program. Then, we compare each of the SE programs to the SEBoK knowledge areas. We conclude with ideas on how undergraduate SE programs can use the SEBoK in planning and execution of their academic programs.