bluuebunny/crossref_metadata_2025_split huggingface dataset:
6.3.2 A Frame‐Based Approach to Requirements Engineering
Authors: Cook Stephen C. , Kasser Joseph , Asenstorfer John 
Published: November 2014

AbstractRequirements engineering is justifiably receiving increased attention at present as deficiencies in this endeavour are often cited as being responsible for poor project outcomes. The paper opens by identifying the goals for the next generation of requirements engineering support tools and postulates that requirements engineering practice and tools will require more than an incremental improvement to achieve these goals. The approach proffered is to apply expert system techniques to the problem. Through an examination of previous research we propose that a highly capable requirements engineering tool can be built based on intelligent agents operating on a bespoke frame‐based knowledge representation architecture. Evidence is presented that the approach has the representational richness and reasoning power to undertake the functionality identified as being necessary to assist requirements engineering.
8.3.3 A Second Application of the CEaVa Method
Authors: Larsen Bob , Buede Dennis 
Published: November 2014

AbstractIn the complex world of developing requirements and eliciting user needs, engineers build billions of dollars of products that are wrong on delivery, because they solved the wrong problem. The problem statement does change, because the environment (i.e., schedule, technology, people, or politics) changes. The Continuous Early Validation (CEaVa) refinement method will stabilize the problem statement (i.e., critical requirements or KPPs), which will enhance the probability of building the right product. We will highlight the second application on a billion dollar Army Information Technology system case study that utilized the CEaVa method.
4.4.1 Modeling the Customer Value of Product Development Processes
Authors: Browning Tyson R. 
Published: November 2014

Abstract1Lean is not minimizing cost, cycle time, or waste. Lean is maximizing value. In product development (PD)—a process where the systems engineering (SE) of products plays a significant role—sometimes getting lean requires doing more, not less. Providing a preferred combination of technical performance, affordability, and lead time requires a flexible and lean PD process. Value is affected not only by the presence of necessary (value‐adding) activities in the PD process but also by the way those activities work together (as a system) to ensure that they use and produce right information. Lean PD requires the right information in the right place at the right time.The kernel of the idea is based on systems thinking. The value of a system is more than the value of its individual components. Similarly, the value of a process is more than the value of its individual activities. How well the components or activities work together (or fail to do so) makes the difference in value. If all the activities add value, how can we ensure that they work together in such a way that the overall process maximizes its potential value? Lean PD requires the systems engineering of processes.
4.4.3 A Visual Explanation of Development Methods and Strategies including the Waterfall, Spiral, Vee, Vee+, and Vee++ Models
Authors: Mooz Hal , Forsberg Kevin 
Published: November 2014

AbstractConsiderable confusion continues relative to development methods, development strategies, and delivery strategies. This confusion is prevalent in routine engineering discussions and in recent textbooks. Method models such as the Waterfall, Spiral, Vee, Vee+, and Vee++ offer a variety of software and system development approaches each with a specific emphasis. Each of these models can be applied to an incremental or evolutionary strategy according to the nature of the project and each of these in turn can be produced in single or multiple deliveries.This paper addresses the choosing of a technical development strategy, which consists of selecting and implementing a combination of the most appropriate development method, a development strategy, and a delivery strategy.
8.4.2 A Case Study in the Application of UML and OOA/D in an Information Management Program
Authors: Gibbons Paul J. 
Published: November 2014

AbstractDuring the past few years, Object Oriented (OO) techniques have begun to expand from what had traditionally been a software development focus. Specifically, the expansion of these techniques has not only been extended on the programmatic time line, but also expanded in applicability to other disciplines including Systems Engineering. As the time‐line applicability of these techniques has grown, early‐on program phases which particularly address Systems Engineering are gaining emphasis. As a result of this, OO techniques are becoming a key tool set in the current‐day Systems Engineering discipline.This paper provides a Case Study of an ongoing competitively won Information Warehouse and human‐system information access program. An overview of the Unified Modeling Language (UML) and related OOA/D techniques are explored. A particular emphasis is placed on insights and lessons learned from the System Engineering perspective.
6.5.1 Using COTS tools in the development of a Model Based Avionics Architecture Tool
Authors: Chau Savio , Hall Ronald , Traylor Marcus , Whitfield Adrian 
Published: November 2014

AbstractInformation and discussion of the development of an Avionics Architecture Tool that is model‐based using commercial off the shelf (COTS) products will be provided. Statemate Magnum from I‐Logix Inc. was used in this work. A number of areas of interest will be discussed, including the user and institutional needs affecting tool design, development, and deliverables, how plug‐and‐play general component models is used for avionics architecture rapid prototyping, the basic architecture of a general component model, and preliminary results of utilising the tool to develop a “straw man” avionics architecture.
6.5.3 An Approach to Generalising the State Space of a Distributed Missile Simulator
Authors: Gordon Steven , Kristensen Lars , Billington Jonathan 
Published: November 2014

AbstractFormal methods can be used to verify refinements made in the design stages of systems. For example, the state space of a detailed design model can be compared with that of an abstract design model to see if it preserves sequences of events. Problems with state space analysis (state explosion, fixed initial states) make this difficult for real applications. In this paper we outline an approach for obtaining a generalised state space of a distributed missile simulator. The original state space has a repetitive structure. Our aim is to prove that for any initial state, the system will eventually halt, after which we can define a compact graphical representation of the state space, that is independent of the initial state.
6.5.4 SafeAir ‐ An Integrated Development Environment and Methodology
Authors: Goshen‐Meskin ora , Gafni Vered , Winokur Michael 
Published: November 2014

AbstractSafeAir (http://www.safeair.org) is a European Commission project that has been submitted under the 5th framework program. Within the framework of SafeAir an Avionic System Development Environment (ASDE) will be developed and evaluated. ASDE will implement technologies, methods and tools that meet the high dependability needs of real time embedded systems. Once natural language requirements are in place, ASDE will support system and software property specifications on the basis of formal, readable, graphical notations. Notation will be based on block‐diagrams, activity‐charts and state‐charts, both at the analysis and design phase. ASDE will integrate defacto standard modelling tools (Statemate, MATLAB, Sildex, and SCADE) for complex embedded system applications. Thus, ASDE will provide a seamless process path from system‐level modelling tools to an automatic code generation tool in compliance with the DO‐178B certification standard [1] for critical airborne embedded systems. ASDE will significantly raise the degree of early error detection and reduce the validation effort during system integration time utilizing formal verification techniques for the verification of system critical properties.The key concepts for these improvements are a model based design process, formal verification, automatic code generation and automatic code validation.
7.5.1 Appraisal using the Federal Aviation Administration's Integrated Capability Maturity Model® (FAA‐iCMM®)
Authors: LaBruyere Larry 
Published: November 2014

AbstractThe Federal Aviation Administration (FAA) has been improving its processes for several years. As part of this process improvement effort they recently completed an appraisal of eleven programs representing the full systems engineering and acquisition lifecycle, against the FAA's Integrated Capability Maturity Model® (FAA‐iCMM®). This paper describes the method used and identifies lessons learned.
7.5.3 Capability Assessments – Worth the Trouble?
Authors: Olesnicky Roman 
Published: November 2014

AbstractFormal capability assessment is increasingly viewed by many as an essential element of a structured business improvement program, but many organisations are reluctant to take that first step because of perceptions of expense and complexity, and uncertainty of the value of the overall process. This paper recounts the experiences of the Author's organisation in its first foray into the world of formal Capability Assessment as part of the CMMI1 pilot program. It recounts the process, records the resources applied, lessons learned, and “even better ifs” with a view to aiding that decision process for organisations that may be contemplating embarking on such a path.
1.6.1 Object Modelling for the Management of Narrow Passageways in Transportation Systems
Authors: Lagakos Vasilios , Kaisar Evangelos I. , Austin Mark 
Published: November 2014

AbstractWithin the transportation network arena, narrow passageways occur where the width of a transportation link is insufficient to permit operation of two‐way traffic at normal speeds of operation. As a result, traffic congestion, accidents, and costly delays are common problems. The effective management of these systems is needed to mitigate the undesirable impact of these bottlenecks on system safety, performance and cost. In an effort to address the significant challenges associated with the analysis, design, and implementation of appropriate management operations for narrow passageways, this paper attempts to develop an object‐based model for the management of narrow passageway problems in transportation systems. The object model is formulated in two steps. First, we identify high‐level management functionality, objects, and associated data/information sources that are common to all narrow passageway applications. In the second step, functionality of the object model is customized to the specific needs of the narrow passageway application domain (e.g., waterways).
2.6.2 A Family of Systems Collaborative Engineering Environment
Authors: Crisp Harry , Lake Jerome G. 
Published: November 2014

AbstractThis paper describes the Naval Collaborative Engineering Environment (CEE) being developed to facilitate data/information exchange and collaboration among engineers, scientists, users, and managers at multiple distributed geographic locations for the purpose of family‐of‐systems interoperability engineering. A description of the envisioned open systems, standards based infrastructure of communications, data processing and resource management services is included, as well as how the Naval CEE will be used within the US Naval Force Systems Engineering Process.
2.6.3 The Next Venue for Systems Engineering
Authors: Ring Jack 
Published: November 2014

AbstractIn the hypercompetitive era customers will not want to buy your products. However, they will pay extra for improvements to their existing system(s). The purpose of this paper is to explain this difference in customer behavior and what it signals regarding expanded career opportunities for systems engineering practitioners. This paper describes hypercompetition, identifies the major stimuli that system engineering practitioners must honor and identifies the resultant capabilities and behaviors required for success. Customers include government, business and civil sector. Capability improvements include ten fold gains in intelligence, cycle times, quality and return on resources. Participation is voluntary but anyone not learning to practice these new types of relationships and behaviors likely will be relegated to the hypocompetition pile.
6.6.2 Market Survey ‐ Commercial Reliability, Availability and Maintainability Engineering Software
Authors: Filliol Nathalie , Stäritz Joachim 
Published: November 2014

AbstractIn aerospace projects increased reliability, availability and maintainability (RAM) is an important contribution to the reduction of the technical and financial risks. So called RAM Engineering software makes it easier to perform such analyses, particularly in early development phases.The objective of this work is the investigation of commercially available tools (e.g. AvSim+, OpSSim, RAPTOR, Relex, …) for the application at the European Aeronautic Defence and Space Company. The tool should be adapted to the specific requirement of future users.The requirements for a RAM Engineering Tool are expressed in KO‐Criteria, Criteria and their corresponding weighting factors Altogether 13 RAM Engineering software, which are available on the market, were analyzed. Information about the products was collected, in order to conduct a qualitative comparison of their abilities. After a preselection nine products were tested on the basis of an example system and afterwards evaluated regarding the determined criteria and their weighting factors.The investigation suggests that the market does not offer an optimal tool for all applications at EADS, but each tool has its strengths and weaknesses. The result of the evaluation determines the software, which offers the best compromise for the calculation of the reliability and the inherent and achieved availability. However different tools are recommended for special applications like the calculation of the mission reliability or the operational availability.
6.6.3 The Application of the Learning Cycle in the Royal Australian Navy Class Logistics Offices
Authors: Tyndall Moya , Whitehouse Tom , Woolley Anthony , Turner Ben 
Published: November 2014

AbstractAn overview of the research and development task established to demonstrate the feasibility of applying numerical tools (based on modelling and simulation) to Royal Australian Navy (RAN) capability management is given. Our focus in this task is on the materiel support aspects of the capability management process that are the responsibility of the RAN Class Logistics Offices in the Defence Materiel Organisation. For example, assistance is required in making decisions in resources allocation, maintenance scheduling, spares optimisation and obsolescence management. A learning cycle, which has its foundation in systems thinking and systems engineering, is introduced in this paper as a mechanism for continuous improvement and informed decision making. Tools and techniques that can be used to assist the activities in the learning cycle are described with appropriate examples. These tools and techniques include statistical analysis, knowledge discovery in databases, decision‐making techniques, systems modelling and risk assessment. Also, some conclusions and future directions for this research program are presented.
7.6.3 The Importance of the Business Context to System Boundary Definition – A Case Study or Two
Authors: Jeffrey  
Published: November 2014

AbstractThis paper provides two illustrations of recent projects where an appreciation of the true impact of a new and expensive integrated system upon the wider organisation was not considered until well into system design and in one case at prototype delivery. The case studies provide an operational context and support for investment in development of the operational concept prior to system design. Furthermore, the case studies emphasize that a developed operational concept in the form of mission scenarios or use cases provide an invaluable tool for design validation in an agreed operational/user context.
5.7.3 Impact of Shared Data Environment – Enterprise Integration (SDE‐EI) on Systems Engineering
Authors: Meakin Brian , Kemp Duncan 
Published: November 2014

AbstractThis paper describes the impact that improved Enterprise Integration (EI) through the use of Shared Data Environments (SDE) can bring to Systems Engineering (SE).Picking up on the Symposium theme of ‘Innovate, Integrate and Invigorate’ the paper decribes the areas where EI will enable and strengthen SE during the Product Life Cycle and across the Supply Chain.It focusses on the organisational and cultural impacts of EI initiatives currently taking place in ‘live’ Pilot projects across major UK MOD/Industry Programmes and how this both enables and enhances ‘Best Practice’ Systems Engineering.In addition to the benefits EI can bring to SE the authors have been successful in applying a Systems Engineering approach to implementing their respective EI projects. The paper records their key findings.
6.7.2 Innovation and Soft Systems Engineering
Authors: Stajnko Frank , Doukas* Louis 
Published: November 2014

AbstractInnovation is the way that a business system turns its vision and foresight into reality. Unfortunately it can also be complex and limitless in its application and scope. This means that there is a great risk that you can charge off in the wrong direction, hence wasting considerable resources on the way and quite possibly causing significant and terminal failure. Strategy making and Soft Systems Engineering are critical in helping to aim the innovation effort in the right direction, such that resource deployment is optimised and the chances of success greatly improved. It must be noted that effective strategy making depends on the accurate forecasting and anticipation of change, which is difficult at the best of times. Be that as it may, it still remains the only way to tackle long range, significant and radical innovation. Tactical approaches are really only appropriate for minor and incremental innovation.
6.7.4 XMInt: An XML Mediated Integration Model
Authors: Mukviboonchai Suvimol , Chirathamjaree Chaiyaporn 
Published: November 2014

AbstractTo interoperate data sources that differ structurally and semantically particular problems occur, for example, problems of changing schema in data sources will affect the integrated schema. In this paper, conflict between heterogeneous systems is investigated and existing approaches to integration are reviewed. We propose XMInt, an XML Mediated Integration model which employs mediation and wrapping techniques as the main components for the integration of databases and legacy systems. With XMInt, a mediator acts as an intermediate medium transforming queries to sub‐queries, integrating result data and resolving conflicts. Wrappers then transform sub‐queries to specific local queries so that each local system is able to understand the queries. This framework is currently being developed to make the integration process more widely accessible by using standard tools. An initial prototype is included to demonstrate the model.
7.7.3 Integrating COTS products into a Maritime Reconnaissance System
Authors: Velagapudi Sunil , Chapman Tim T. , Voytko Mary , McMahon John A. 
Published: November 2014

AbstractMilitary programs are increasingly procuring Commercial Off‐The‐Shelf (COTS)‐based products to decrease the program costs and time to delivery by leveraging on integration of mature, Research and Development (R&D) products.Some of the assumptions are: 1) one doesn't have to pay for R&D, 2) COTS products plug and play and 3) products are easily adapted to different platforms.Whilst savings with respect to R&D costs are not addressed in this paper, the plug & play and adaptation aspects merit discussion, especially when integrating smart and complex COTS products. COTS products do not eliminate systems engineering effort; they can increase the amount of effort required.This technical paper will present some of the challenges, the solutions, and lessons learned in integrating COTS products on United Kingdom (UK) Ministry of Defence (MoD) Nimrod Maritime Reconnaissance Aircraft 4 (MRA4) program. In addition, strategies are proposed that may be used by other COTS‐based programs.
9.1.3 Q‐Analysis: A possible addition to the SE Toolbox
Authors: Hansell Alex , Vance Kim 
Published: November 2014

AbstractA key problem of systems engineering is how to break down a system into its principal subsystems or components and their interfaces. The traditional approach relies on intuition & past experience, both are heavily influenced by the conventional taxonomy of academic disciplines (mechanics, aerodynamics, electronics, economics, etc). This intuitive approach is being supplemented by emerging disciplines (risk analysis, environmental concerns, ergonomics, etc). Increasingly it is being found that traditional approaches no longer satisfy modern holistic aspirations. The problems are too diverse whilst being increasingly tightly coupled. An effective multidisciplinary approach is required. This paper discusses the application of Q‐analysis to the problem of identifying subsystems & interfaces.
9.1.5 Using distributed database queries and composable mediators to support requirements analysis
Authors: Sutinen Krister , Katchaounov Timour , Malmqvist Johan 
Published: November 2014

AbstractRequirements analysis in a modern development environment needs to take into account product information at all stages of development. An integrated product model is used to describe the data used through the development process in form of different kinds of models and to capture the relationships between them. Due to its diverse nature, this information is usually stored in distributed and heterogeneous information systems. To support the task of requirements analysis, a distributed data integration architecture called composable mediators is proposed. Composable mediators are a multidatabase system consisting of distributed autonomous object oriented (OO) mediator servers defined in terms of other mediator servers. The complexity of the information model describing requirements data is addressed by the use of OO queries. The distribution and diversity of the data involved is addressed by accessing it through a distributed mediator system. This approach allows not only all related distributed data to be accessible in a timely manner without any changes to existing systems, but also for new information to be extracted from the available product requirements related data.
1.1.4 The ‘Learn from Experience’ (LfE) journey in Systems Engineering
Authors: Meakin Brian , Wilkinson Brian 
Published: November 2014

AbstractThis paper describes how ‘Learning from Experience’ (LfE) encompasses and pervades the popular domain of interest ‘Knowledge Management’ (KM) throughout the life cycle of a project. This paper is NOT about KM. It is about the development, retention and re‐use of tacit knowledge or wisdom. If KM captures the explicit Knowledge that can be captured and extracted from databases, then LfE adds to this the tacit knowledge [or wisdom] of those who have ‘been there and done it‘. By combining explicit and tacit knowledge we have the better of two worlds coexisting together in a self‐learning and self‐sustaining process.As Systems Engineering can be expressed as a Socio‐Technical activity it is appropriate that Systems Engineers utilise LfE to inform the Enterprise, project and the personal knowledge base as early as possible in the project life to ensure the chosen system solutions are those with the best opportunity for success. LfE is generic and is just as appropriate for a non‐engineering enterprises, for example a Banking Institution.