bluuebunny/crossref_metadata_2025 huggingface dataset:
2.4.4 Prediction of Information System Availability in Mission Critical and Business Critical Applications
Authors: Hecht Myron , Incorporated SoHaR
Published: November 2014

One of the most important attributes of on‐line computer systems that are performing mission or business critical applications is availability. System Engineers are often called upon to predict the reliability of such systems as part of proposal preparation, architecture definition, design reviews, and operation. However, traditional modeling techniques are incapable of handling integrated hardware and software systems with multiple states and redundancy. This paper describes how Markov Modeling and Reliability Block Diagrams can be used together to model a large on‐line information system and develop the answers to strategic questions on the configuration and operation of high availability computing systems. The analyses are performed using MEADEP, a reliability analysis tool capable of hierarchical modeling and integrating Markov and block diagram techniques. In the example 3‐tier architecture e‐commerce site described in this paper, it is shown that (a) the most frequently failing subsystem is not necessarily the availability bottleneck, and (b) that restoration time is often a more important parameter than availability when attempting to maximize system throughput.
2.4.5 Multistage System Integration
Authors: Tahan Meir , Ben‐Asher Joseph Z.
Published: November 2014

In large‐scale system developments, systems engineers usually divide the integration process into stages in order to facilitate the integration. Often this “divide‐and‐conquer” method, or what we call “multistage integration”, is the only way of rendering the integration of a complex system feasible. This paper proposes to consider the employment of the multistage integration methodology for large as well as for small systems. The main point is that, regardless of size, and even when a single stage integration is feasible, it may be beneficial, both time‐wise and cost‐wise, to pursue the multistage integration methodology. Two models are developed in order to analyze single stage and multistage integrations: a purely statistical model, and a robust design based model. Both models are shown to be viable and efficient as demonstrated by a simple representative example.
4.4.1 Systems Engineering Techniques in Support of Business Improvement
Authors: Kemp Duncan , Cole John
Published: November 2014

This paper discussesd the use of Systems Engineering concepts and techniques in business improvement projects being undertaken within the United Kingdom's Warship Support Agency, part of the and Defence Logistics Organisation.

System's Engineering techniques have been used to understand complex cultural, process and organisational issues that have been limiting the performance of Warship warship Supportsupport, and help design and justify elements of the WSA's successful Enterprise Integration and Shared Data Environment Project.

The paper discusses the use of failure mode analysis to identify strategic drivers for change and system dynamics modelling to link business improvement requirements to business benefits in business cases.
4.4.2 From Systems Engineering to Service Engineering
Authors: Wieser Michael
Published: November 2014

For many companies the optimisation potential in quality, process, and cost has become smaller and smaller in the last years. Systems engineering has played an important role in that process. Now, an almost untouched and in many companies often ignored domain has become the target of interest: services!

A systematic development of services is supposed to be a key factor in the future in order to diversify the own company from the competitors. As customers more and more call for integrated solutions goods will not be sold in future on their own anymore. They will have to be integrated in services. Those one, who will be able to offer new services in a shorter period of time, that meet exactly the customers' needs, will have a main advantage in a global market. To do so, methods and tools are required.

This paper describes the current situation of services, their role in the world economy and why it is so important not to ignore the services any longer. It is shown how services can be characterised and it is discussed if current systems engineering models can be transferred to the “immaterial” world of services.
4.4.4 E‐Business Infrastructure Capability Assessment
Authors: Ring Jack
Published: November 2014

A modern E‐Business infrastructure must enable enterprise collaboration, both external and internal, throughout unpredictably dynamic situations. Anyone selecting an e‐business solution should assess the capability of its infrastructure using applicable Measures of Effectiveness (MOE's). This paper expresses the MOE's in the context of a conceptual model of an E‐Business infrastructure. In addition, a checklist and a graphical notation for scoring the capability levels of candidate solutions is provided. The purpose of a capability assessment is to help protect enterprises from making commitments to solutions that lack key capabilities. The ten MOE's described in this paper will provide a useful perspective to any systems engineering practitioner involved in creating an E‐Business solution.
4.4.5 Systems Engineering Starting in the Middle of a Program
Authors: Armstrong James R.
Published: November 2014

A process for application of systems engineering in the middle of a program has been described (Bahill and Briggs) that is based on analysis of the work breakdown structure to determine the scope of the program. The process provides general guidance and recommends specific reduced activities. This paper proposes a different start in the process to more thoroughly review the situation and determine where key information is missing. It also provides specifics and examples from several such applications of systems engineering and instances where it would have been beneficial.
5.4.3 ANSI/IEEE 1471 and Systems Engineering
Authors: Maier Mark W. , Emery David , Hilliard Rich
Published: November 2014

ANSI/IEEE Standard 1471–2000 is the Recommended Practice for Architectural Description of Software Intensive Systems, developed by the IEEE's Architecture Working Group (AWG) under the sponsorship of the Software Engineering Standards Committee of IEEE. ANSI/IEEE 1471 is the first formal standard addressing the content and organization of an architecture description document. As suggested by its title, ANSI/IEEE 1471 was conceived as a software standard, but applies essentially equally to broader systems. This article reviews the concepts of ANSI/IEEE 1471, the rationale for their selection, and their application to systems engineering.
5.4.5 Web‐based Process Documentation – Getting Over the “Paper Mentality” Hurdle
Authors: Pohlmann Lawrence D.
Published: November 2014

We are in an era of extensive emphasis on process, process maturity, and process improvement. Up until only a few years also, most process documentation was paper based. Large volumes of detailed process descriptions occupied our bookshelves – and normally remained unused for long periods of time. Many companies are now using their intranets to host, manage, and distribute process documentation. Web‐based approaches can make process documentation both more accessible and more easily maintained. However, too often these process descriptions still exhibit a “paper mentality” in that they leave much of the real power of the internet largely untapped.

This paper discusses a number of process documentation concepts that are beyond this paper mentality hurdle. The basic premise is that more advanced web‐based approaches allow integration of and easy navigation among sets of highly useful systems engineering process‐related information – which in turn facilitates more effective and efficient systems engineering.
1.5.5 Grand Systems Verification
Authors: Grady Jeffrey O.
Published: November 2014

The product system development process follows a three step sequence familiar to all system engineers: (1) define the problem you are trying to solve, (2) design and manufacture a solution to that problem, and (3) verify that the solution satisfies the requirements that drove it. Therefore, verification is a process for proving that the design of an entity satisfies the requirements for that entity that were crafted prior to the design of the entity. The common mode of verification is to compare an entity with some accepted standard of excellence. The entity can be a product or a process system or some element or combination thereof. This paper explores the fusion of several concepts, some new and some old, to build an enterprise environment within which all verification work can be accomplished within the same three step context noted above. This includes product verification but also enterprise common process verification and program process verification. The paper also challenges common responsibility assignments for this work.
2.5.2 Modeling and Simulation of Military System Architectures Using CORE®
Authors: Cropley David , Kirby Brendan
Published: November 2014

This paper describes the analysis of a hypothetical command and control architecture for a proposed future land force conducting maneuver operations under various conditions. The Systems Engineering tool CORE® has been used to capture the user needs, and to develop a hierarchy of functions necessary to implement the proposed command and control system. CORE also facilitates behavioral modeling of the functional architecture. This paper shows how the tool can be used to analyze the performance of candidate physical architectures based on a common functional architecture. The models that are formed serve as valuable aids for the user to evaluate novel operational concepts, and for the system architects to determine productive areas for research into improving technological support for command and control.
3.5.3 Product Line Requirements Management
Authors: Sutherland Michael
Published: November 2014

Product development organizations use design reuse strategies to build common subsystems for the complex systems they develop and the many customers these systems are delivered to. Sub‐systems are designed with an Architecture that will allow for strategic reuse. A base design for a sub‐system is designed, with some reasonable modifications for specific Applications, to meet the requirements of the systems the subsystem will be incorporated into.

This paper provides details on a strategy for Requirement Management across Product Lines that has successfully been deployed within a large Product Development and Manufacturing organization.
5.5.1 Architectural Abstractions
Authors: Jorgensen Raymond W. , Philpott Ian W.
Published: November 2014

Architectural constructs provide the basis for effective system design. A well conceived architecture also provides a foundation for a product definition that can be effectively adapted and reused across many different project instantiations. But what makes up a complete system architecture? Is one block diagram illustrating the arrangement of physical components “the architecture“? Or are there other dimensions of a system architecture that are needed to complete the picture? This paper explores some concepts of the “complete system architecture.” Multi‐dimensional views of architecting are examined to provide insight into what makes up a system architecture.
5.5.2 A Generic Methodology for Partitioning Product Architectures
Authors: Gaso Berislav , Whitcomb Clifford , Igenbergs Eduard , Schulz Armin
Published: November 2014

Industrial companies can gain major competitive advantages if they possess the ability to bring products to market faster while at the same time fulfilling customer desire for greater variety. An effective way for achieving this advantage is to develop modular product architectures. This paper presents a repeatable methodology for designing modular products that explicitly considers multiple product attributes (as metrics) and customer preferences. Furthermore, it introduces external and internal metrics for architectures and combines them together with the functional analysis approach in an exceedingly powerful tool called Element Modeling Language (EML). Subsequently, it is shown how EML‐structures are translated into a system of binary and non‐binary matrices, called the Matrix Modularization System (MMS), which can be handled mathematically. Two type‐of clustering algorithms, based on heuristic methods and function flows as clustering parameters, are introduced.
5.5.3 Enabling Systems Architecture Tradeoffs Using a Systems Integration Framework
Authors: Kalathil Biju , Moore Douglas , Huggins Coleste
Published: November 2014

Systems integration of large information enterprises involves integrating multiple heterogeneous database systems, client‐server platforms, web application technologies, and data warehousing solutions. Lockheed Martin Management and Data Systems (M&DS) is involved in systems integration for state, local, and federal government customers. We are currently developing a Systems Integration Framework (SIF) to assist in the architecture tradeoff and selection for large information enterprises. A SIF is an environment, which will assist in the rapid prototyping and testing of architectures, and specific instantiations of the architectures using commercial tools and platforms. Over the last four years we have developed and tested architectures for client‐server applications, web applications, mobile computing applications, data warehouses, and data mining applications. Performance metrics have been collected for web application servers and client‐server applications. This paper will describe how we utilized the SIF as a rapid prototyping and tradeoff environment to support systems engineering for state government customers in domains such as law enforcement, criminal justice, and airline operations.
5.5.4 Design of the concept of a new system, using ICDM ‐ Integrated, Customer Driven, Conceptual Design Method
Authors: Weiss Menachem P. , Hari Amihud , Zonnenshain Avigdor
Published: November 2014

ICDM, a practical and effective Integrated, Customer Driven, Conceptual Design Method has been introduced recently, for the design of New Products. The method has been evaluated, tested and successfully implemented by the Israeli high‐tech industry. ICDM is claimed and shown here to be practical and highly effective also for the design of New Complex Systems and complex high‐tech products. ICDM integrates proven techniques with original additions and can be adapted to the need of any industry.
1.6.1 A Strategy for Designing Optimal Complex Systems Solutions
Authors: Shell Tony
Published: November 2014

In this paper, a strategy for the design of optimal systems solutions is developed and assessed. The main areas of investigation focus on the use of a formal approach, based on mathematical systems theory. A specific methodology for the ‘decomposition’ of system trade‐offs, for use in identification of optimal system solutions, is explored in detail. The practical difficulties of accurately identifying the best (optimal) system solution ‐ particularly for complex systems that are subject to imposed implementation constraints and are part of some extended hierarchical construct ‐ are also addressed. The paper concludes with recommendations with regard to a proposed strategy for complex systems optimisation.
2.6.5 Designing a Supply Chain Analysis Framework
Authors: Ludema Ir. Marcel W.
Published: November 2014

After a customer has stated his need and a proper solution as been found, either by starting a design/engineering process or deliver a product from a stock position, several supply chain processes have to be aligned to eventually fulfill this customers need. Coordination between all supply chain organizations on strategic, tactical and operation levels will lead to more effective supply chains. This supply chain coordination processes is complex and practitioners need a systems thinking approach and broad understanding of topics that are related to the field of supply chain management. To fulfill this task supply chain managers have to speak the same language and understand the importance of possible problems. As part of the development of a professional course in supply chain management a supply chain analysis tool has been developed and tested during four courses in a realistic case situation. This supply chain analysis tool gives support in finding possible problems that should be tackled to optimize the supply chain. This tool is based on the two phases of a structured problem solving process that resembles the first phases of Systems Engineering approaches.
3.6.2 Managing Priorities: Deadline Pressure Control
Authors: Gilb Tom
Published: November 2014

This paper discusses the means of determining the priority order for implementing system changes. It is concerned with the priority ranking of requirements.

Most papers and books describing trade‐off analysis and multi‐dimensional priority evaluation methods refer to the use of allocating subjective, fixed numeric weightings to multiple system requirements (Daniels 2001, Keeney 1992, Saaty 1990, Gilb1976). I would like to argue that it is time we threw off the shackles of subjective weightings and gave practising system engineers something more useful and realistic as a tool for determining implementation priority.

Priority determination should be:

an information‐based process, which makes full use of the available factual information and, is able to reuse this information.

a dynamic process, which uses feedback from the ongoing implementation and, is open to instigating and catering for changes in requirements and design ideas.

a resource‐focussed process, which considers Return on Investment (ROI) and takes into account resource availability.

I would like in this paper to demonstrate how Planguage, a specification language and set of methods, which I have developed over many years, has the capability to address all these above aspects.
5.6.5 Advancing Systems Engineering for Systems‐Of‐Systems Challenges
Authors: Chen Pin , Clothier Jennie
Published: November 2014

Engineering activities in future organisation development including various information‐based systems vary but all result in evolutions of an organisation and its capabilities and systems. These evolutions occur in a context of Systems‐of‐Systems (SoS). This paper presents an understanding of SoS challenges to Systems Engineering (SE) and proposes a new approach to SE process management in order to cope with high complexity of SoS evolutions and improve architecture practice
6.6.1 A Systems Engineering Approach to Filling India's Telecommunications Gap
Authors: Barkley Scott G.
Published: November 2014

The need of developing nations to increase information flow provides a commercial opportunity to extend modern telecommunications technologies and service offerings into new markets. This high‐level case study identifies the need for new systems in India to assist in filling telecommunications service gaps, with a strong emphasis on systems for rural populations. The United States is used as a basis of comparison. Existing systems and deficiencies, stakeholders, and evaluation criteria for potential alternatives are discussed. Several alternatives for local service delivery and national backbone networks are presented, drawn from current and planned offerings in India and worldwide. Application of the criteria to the candidate solutions indicates that no single one is preferable, but a combination of several would provide a suitable solution.
6.6.5 Performing Trade Studies in the CERCLA1 Environment
Authors: Borland M. , Rice P. , Jamison K.
Published: November 2014

During almost any project, situations will arise that require project management and/or engineering personnel to make choices regarding project direction or product development. Often these choices are simply a part of the normal engineering development cycle (e.g., refinement or optimization of the product design). Frequently, on Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA) and other similar projects, trade studies are initiated to address concerns or issues raised by stakeholders (e.g., EPA, local and state governments, local tribes, public). Where CERCLA projects, by definition, deal with releases or threatened releases of hazardous substances that may endanger public health or the environment, these trade studies must balance safety, risk and health issues, as well as cost and engineering viability. How these trade studies are carried out and documented/presented to the stakeholders involved can often be the difference between continued project progress and a “stalemate” leaving the project in limbo.

This document describes a basic trade study process, which has proved successful in addressing stakeholder concerns while at the same time balancing the desires of the various parties involved.
2.5.5 A System Theoretic Framework for V&V
Authors: Wymore A. Wayne
Published: November 2014

This paper begins with a discussion of the meaning of the words validation and verification in the systems engineering context; what should be validated, what should be verified and when. The system theoretic framework proposed for V&V is then described featuring the mathematical structure of the system test requirement. Finally, the specific V&V tasks are defined within the system theoretic framework.
5.1.3 Emergence : Applying the Principles ‐ using Genetic Algorithms to derive schedules
Authors: McConnell George R.
Published: November 2014

Recognising the existence of the ‘other’ perspectives of a given situation results in improved understanding of the emergent properties of a system. This paper builds on a theoretical stance outlined in a paper at the INCOSE International Symposium in 2001 by providing an example of the application of a technique, Genetic Algorithms, which can assist in avoiding some of the biases introduced and incorrect assumptions made by everyone when solving a problem. The paper does not cover the details of the technique, concentrating instead on the use of the technique to solve a scheduling problem. A full description of the prototype solution is given and a brief overview of the differences between that prototype and the final version is provided.
1.2.2 Systems Engineering Modeling Useful in Combating Terrorism
Authors: LongPresident James , Mackey William F.
Published: November 2014

Following the terrorist events of September 11, 2001, several members of INCOSE have become involved in international, regional, and local activities to respond to those events that have shaken the international community. As part of the newly formed INCOSE Anti‐Terrorism International Working Group (ATIWG) established in October 2001, efforts at the University of Maryland University College and Vitech Corporation have produced notable models and products useful to INCOSE. ATIWG meetings at the INCOSE Workshop held in Mesa, AZ, during January 2002 stimulated all who attended and generated still more useful views of the problem space. The ATIWG convened a special panel at INCOSE 2002 in Las Vegas, NV, under the theme documented in a companion paper entitled “The Role of Systems Engineering in Combating Terrorism.”

This paper's thesis is that the multidisciplinary approach of systems engineering is useful in evaluating the terrorist threats, identifying system vulnerabilities, and reducing or eradicating international terrorism. In addition, the ability to model those events may assist in determining the functional design of the terrorist threat and perhaps permit insight into the physical design as well. The functional design (or modus operandi) is frequently unchanged from one terrorist activity to another, and only physical design changes. This then offers the potential to predict future terrorist acts. The authors are in the process of examining all facets of the issue by applying the multidisciplinary approach of systems engineering to the resolution of this meaningful international issue.
3.2.3 Modelling Uncertainty in Integrated Models
Authors: Whittle Steve , Dalton John , Rajabally Eshan
Published: November 2014

One of the main aims of modelling is to ensure that customer requirements (stated in terms of property value constraints) will be met with a suitably high level of confidence. This paper introduces work ongoing jointly within BAE SYSTEMS and the University of Newcastle‐upon‐Tyne in the UK which, in part, introduces processes and techniques to enable this aim to be realised. Part of this work involves the creation of a modelling framework to represent property flow within an integrated modelling hierarchy to aid model and property traceability and to determine and propagate both subjective and quantitative model dependability (confidence we have in the output from models).

The aim of the joint research is, in part, to determine the confidence we have in the values of the top level properties, to determine the critical lower level properties and to ease trade‐off studies.
3.2.4 A Methodology for Modeling VVT Risks and Costs
Authors: Engel Avner
Published: November 2014

The cost of large systems' Verification, Validation, and Testing (VVT) is in the neighborhood of 40% of the total life cycle cost. The cost associated with systems' failures is even more dramatic, often exceeding 10% of industrial organizations turnover. There is a great potential benefit in streamlining and optimizing the VVT process. The first step in accomplishing this aim is to define a VVT strategy and then to quantify the cost and risk associated with carrying it out.

This paper provides an overview of the methodologies for risk and cost monitoring for VVT and proposes a novel approach for modeling VVT strategies as decision problems. A quantitative VVT process and risk model is proposed. Due to the non‐deterministic nature of risk, simulation is used to generate distributions of possible costs, schedules and risk outcomes. These distributions represent a probabilistic approach and are analyzed in relation to impact events. The model provides means to explore different VVT strategies for optimizing relevant decision parameters.

To demonstrate the proposed procedure the paper describes a case study depicting a planned avionics suite upgrade program for a fighter aircraft. Some simplified partial quantitative results are also presented.
4.2.1 Diagnosing reliability problems in Socio‐technical Systems: A Visualisation approach
Authors: Gregoriades Andreas , Sutcliffe Alistair
Published: November 2014

This paper presents a visualisation approach of socio‐technical system design evaluation based on human reliability. Bayesian Belief networks are used to assess human error and system failure (Sutcliffe et al. 1999) based on a variety of high‐level operational scenarios. The System Reliability Analyser tool automates the process by iteratively manipulating the BBN model, presenting the analyst with a three‐level visualisation of the results to diagnose the locus of reliability problems. A case study is presented on the evaluation of two alternative designs of the command and control room of an offshore patrol vessel.
5.2.1 Systems Engineering and the Semantic Web
Authors: Staker Roderick J.
Published: November 2014

The rapid pace of technological development, combined with the changing nature of modern society, pose novel challenges for systems engineering in the 21st century. The effect of the first of these factors is that systems development needs to be highly agile in order to exploit the latest technological developments to their greatest possible potentials. The effect of the second is that it is becoming necessary to take into account the views of a wider range of stakeholders than may once have been the case. One way in which conventional systems engineering methods might be enhanced to better cope with such challenges is by the increased adoption of knowledge‐based methods. This paper will examine the role that a particular form of logic might play in such a knowledge‐based systems engineering approach, and its relation to the “Semantic Web”, the mooted next generation of the World‐Wide Web.
5.2.2 Self Organizing Maps (SOMs) for Systems, Software, Management and CMMI Document Relevancy
Authors: Beshore David G.
Published: November 2014

The size of the systems engineering book of knowledge is unknown, but continuously expanding! The systems and software standards are quagmires of legacy and evolution. Stacks of documents (books, standards, guidebooks, handbooks, papers, process manuals) relate to the subject of systems engineering and engineering management. Developing ‘best practices‘, from systems engineering bodies of knowledge (Beshore 2001), is critical to the future engineering success of large programs. The CMMI (CMMI) represents the latest internationally driven model requirements standard for systems engineering, software engineering and integrated product development. An automated method is presented in this paper to determine document relevance to any body of knowledge or sets of process or process assessment standards. Specific examples and uses of new tools have been used to improve documentation relevancy of Raytheon's IPDS (Integrated Product Development System) to the CMMI process requirements models. With this approach there is a way out of the document and standards quagmire through more focused process planning on programs.
6.2.3 Improving the Efficiency of Improving Efficiency – Re‐engineering the R&D Organization
Authors: Blonigen Brad , Dagli Cihan H.
Published: November 2014

Systems engineering tools were first used to improve the quality and efficiency of the systems that were produced for sale to the customer. These same tools were then applied to the manufacturing systems that produced these products to allow for more efficient production. It is time to move the focus farther up the line and apply the tools to the systems that support and produce the manufacturing systems. By using a systematic approach to the organization and management of the R&D organization, increases in efficiency can be derived that can either be used to reduce near‐term costs or be leveraged to gain even greater returns through re‐investment in technology development. This paper looks at the process of re‐engineering the R&D organization using systems engineering tools.
2.3.2 Idealized Front End Process and Maturity Matrix: A Tool for Self‐Assessment of Process Maturity Leading Up to Product Launch Decisions
Authors: Wirthlin Joseph R. , Rebentisch Eric
Published: November 2014

To better characterize the processes used to generate requirements for new products (a.k.a., the “fuzzy front end” of product development), product development literature was extensively reviewed to identify best practices. An idealized front‐end process model was developed from this literature review and then through an iterative process involving empirical field research, used to create a maturity‐based assessment tool. 17 enterprises engaged in new product development provided data for case studies on the front end of product development and the processes used in requirements generation. Using these case study data, the 17 organizations were scored using the assessment tool to identify the organizations that had the most mature front‐end processes in place. The highest‐performing organizations were compared with the lowest‐performing organizations to identify specific practices that differentiated their performance.
5.3.2 Put Me in Coach; I'm Ready to Play!: A Discussion of an Evolving Curriculum in Systems Engineering
Authors: McCarthy Daniel J. , McFadden Willie J. , McGinnis Michael L.
Published: November 2014

Prior to 1999, the Introduction to Systems Engineering Design course was taught late in the sequence of courses that the typical student took in the Department of Systems Engineering at the United States Military Academy. The normal progression of courses front‐loaded students with various modeling and analysis “toolkit” courses. Much later in the program students were taught the engineering design big picture. In 1999, the academic program was overhauled. The introductory engineering design course became the first course in the academic program. In addition, the program's courses were separated into “methods” courses that fill the student's toolkit and “formulation” courses that require students to synthesize various tools in formulating and solving small‐scale engineering problems. Finally, summer academic internship experiences were linked with a yearlong capstone design experience during the student's senior year. This paper discusses these changes and highlights advantages of this improved approach to teaching systems engineering.
5.3.3 Review of Papers Concerning Engineering Teams in INCOSE Symposia 1991 to 2002
Authors: Ferris Timothy L.J.
Published: November 2014

This paper reviews the discussions of work by engineering teams, and some very closely related issues, in the INCOSE Annual Symposia to date. The purpose of this work is to identify the issues associated with teamwork in engineering teams and the strategies to address the issues with negative effects. The publications are found to address the issues at two distinct levels, the macro of how teams should operate and the overall performance of team structures, and the micro, concerning the inner functioning of the teams, and the issues associated with the human character of the participants. The majority of the literature reviewed addresses the macro level, with only a few papers about the micro dimensions of teamwork. The review is organised chronologically to investigate temporal development of the thinking of authors.
3.4.2 Supporting Object‐Oriented Analysis of Human Performance Systems
Authors: Douglas Ian
Published: November 2014

There is a move towards conceptualizing, packaging and building human performance support systems, such as e‐learning, around reusable objects. As with the software engineering domain this approach may only be successful if analysis and design also moves to an object model. There is a need for new methodological thinking and automated tools to support the change. An automated object‐oriented performance analysis system is described, which enables modeling and collaboration during human performance systems analysis. The system is based on web services and uses a repository model to support the sharing and reuse of analysis knowledge both within and between organizations.
3.4.3 Generation of Hardware Description Languages from Modelisation tools based on Meta‐modelisation
Authors: Rault Valéry
Published: November 2014

One of the main problems when creating systems lies in the different tools and methods used by the various disciplines. Even when doing calculators and computers, with the involvement of only two disciplines, hardware and software, this situation raises many problems early in the design phase and has important consequences on the result. A way to break this wall would be to standardize the efforts around a single design tool, used by the systems, software and hardware engineers as well. As an enabler for such a standardization capability, this paper presents a generator of hardware description languages that uses a meta‐model. A major benefit is to generate code such as VHDL, Verilog or System C from various modelling tools like UML, I‐Logix's Statemate or even from other sources.
2.5.3 Product Development Interrelationships
Authors: Morais Bernard G. , Mar Brian W.
Published: November 2014

Product development processes are driven by a tradeoff between customer, developer and market forces. Commercial consumer product development is very sensitive to market conditions and efforts to increase market share. Defense and aerospace product development is more sensitive to the government customer desire to manage cost, time and schedule of the development effort and to advance the technology. This paper examines the lessons learned from both the commercial and defense product development experiences and presents a unified approach that will respond to any combination of product development issues.
6.5.2 The Role of Systems Engineering in Intelligent Transportation Systems
Authors: Mackey William F. , Krueger Michael E.
Published: November 2014

This paper explores how systems engineering is being applied to meet the growing need for an Intelligent Transportation System (ITS). There are similarities between the approaches that civil engineers take to design highways and that systems engineers take to solve complex system development problems. The process of developing a highway design can be directly correlated to the system development life cycle used in systems engineering. The progression of highway development is demonstrated to be an evolution of technologies, inventions, organizational creations, and legislative acts that has supported the development of a national interstate transportation system in the United States. The ITS is a global phenomena and is being pursued in Europe, Australia, and Japan as well as the United States. Until now, highway development has been the domain of civil engineers concerned with highway structures, materials loading, traffic patterns, and supporting facilities. However, the growing need for ITS or intelligent‐vehicle highway systems (IVHSs) requires that traditional civil engineering disciplines be integrated with computers, communications, and eventually fully automated vehicles. This paper's thesis suggests that the complex highway transportation of the 21st century can benefit from the collaboration of systems engineers and civil engineers.
6.5.3 Product Model for Requirements and Design Concept Management: Representing Design Alternatives and Rationale
Authors: Andersson Fredrik , Sutinen Krister , Malmqvist Johan
Published: November 2014

Throughout the development of complex products, thousands of requirements are established, communicated, followed up, and verified. In addition, even more design solutions, at various levels of abstractions, are created, refined, evaluated, industrialised and verified during this period. Although design tools support the documentation and administration of the output of these activities, i.e. requirements and solutions, they lack the functionality to support the iterative gestation of requirements and design solutions as they are created. This paper illustrates how a product model, focusing on requirements and design concept management, can address these issues by incorporating design rationale, i.e. the reasoning and the justification underlying requirements and solutions considered, with the aim to close the gap between product models and design rationale models. The product model has been implemented in a commercial PDM software and its use is illustrated with the information from the design of a passenger car cockpit.
2.6.3 Security Engineering Awareness for Systems Engineers
Authors: Sheard Sarah A. , Moini Assad
Published: November 2014

Systems engineers generally are not trained in computer systems security, and those who are trained often have limited exposure to narrow areas of computer security. The result is that system‐wide security requirements often are not understood or addressed adequately, and delivered systems may contain hidden security flaws and vulnerabilities that are later exploited. Reactive efforts to patch or harden system security later in the system lifecycle are very costly and only can address flaws and vulnerabilities after they have been discovered. Given both the explosive growth of the Internet and our ever‐increasing reliance on critical information infrastructure, it is no longer sufficient for systems engineers to remain technically naïve about security considerations. This paper discusses some of the reasons for this new urgency; the areas where knowledge of computer systems security is important to systems engineers; and some topics that must be considered when eliciting, analyzing, and specifying system‐wide security requirements.
2.6.4 Measurement of System Safety Processes
Authors: Caseley Paul , Clark Graham , Murdoch John , Powell Antony
Published: November 2014

The ‘Measurement of Safety Processes and ALARP’ project is a UK Ministry of Defence Corporate Research Programme, managed by QinetiQ Ltd. that is developing fine‐grained, non‐invasive, measurement systems for the safety domain. The need for better measurement systems is being driven by a number of factors, principally the need to reduce risks to As Low As Reasonably Practicable (ALARP) and the achievement of higher levels of process maturity.

The Safety Process Engineering Language (SPEL) is a language‐based measurement framework for safety processes. The approach, originally developed in the software engineering domain, is described via a case study of its industrial application on an auto‐code verification project. We show how the technique enables the cost‐effective collection of fine‐grained information to help identify improvements in the technical and business management of the safety process.
4.6.2 Intelligent Agent Saves Lives
Authors: Steinberg Richard K.
Published: November 2014

Designing human computer interfaces for rapid command and control decision‐making displays has unique challenges. Displays for Air Traffic Control, Military Operations, and Emergency Management require an interface that optimizes performance while minimizing errors. In addition to performing the emergency functions, maintaining operational readiness of equipment is a task where errors and time delays could cause loss of human life. Interaction efficiency is critical to avoid operator fatigue and minimize operator error rates that could cost lives. In emerging emergency management systems and concepts, the user typically acts as a manager by exception while the majority of system activity is computer automated. While direct interaction of the user with the system is minimal, an inaccurate action by the user can have catastrophic consequences. There is clearly a need for decision aiding systems to help focus users on the most important information. This paper describes a case study that demonstrates the use of a human engineered intelligent agent. The results of this effort suggest as much as a 40% reduction in casualty risks while using the intelligent agent and strong positive preference ratings by all operators who used it.
1.7.2 An Integrated Risk Management Process
Authors: Saad Joe , Hsu John C.
Published: November 2014

When the risk management process was introduced at the Boeing Airlift And Tanker (A&T) Programs, many obstacles were encountered. It was determined to overcome these obstacles and improve the process. While the process of risk analysis and mitigation is well known, implementation is more challenging than just establishing the process and procedures. The detailed steps of implementation are presented. Visibility of critical risk to program level manager and customer is vitally important for both program management and timely and effective resolution. The company profit as well as customer budget control depend on close monitoring of project spending. The project cost risk is converted to impact assessment of Estimate At Completion (EAC) at the earlier stage of the project progress. The integration of project risk with program level risk and with business risk is discussed.
4.7.1 How to Quantify Quality: Finding Scales of Measure
Authors: Gilb Tom
Published: November 2014

‘Scales of measure’ are fundamental to the definition of all scalar system attributes; that is, to all the performance attributes (such as reliability, usability and adaptability), and to all the resource attributes (such as financial budget and time). A defined scale of measure, allows you to numerically quantify such attributes.

‘Scales of measure’ form a central part of Planguage, a specification language and set of methods, which I have developed over many years.

This paper describes how you can develop your own tailored scales of measure for the specific system attributes, which are important to your organization or system. You cannot rely on being ‘given the answer’ about how to quantify. You will lose control over your current vital system performance concerns if you cannot, or do not, quantify your critical attributes.
5.7.1 The C4ISR Architecture Framework V 2.0: Considerations for Usage
Authors: Iaquinto Joseph F
Published: November 2014

Many DoD contracts require the use of the C4ISR Architecture Framework. This framework prescribes a specific set of architectural artifacts. However it provides very little guidance on how one is to use this framework. This paper provides a brief introduction to the C4ISR Architecture Framework, version 2.0. Following this, specific usage guidance is provided to aid the C4ISR Framework user in accomplishing the objectives of the Framework.
5.7.2 Systems Engineering: a Natural Approach to C4ISR
Authors: Maley Joseph , Long James
Published: November 2014

In 1998, the United States Department of Defense mandated the C4ISR Architecture Framework for all ongoing and future contracted architectures. The goal is to ensure that future military systems are interoperable and provide the warfighter with the support and effectiveness required for successful missions.

The C4ISR Architecture Framework specifies a set of “standard” views capturing various system perspectives. As with nearly all frameworks, the outline and contents are defined, but the methodology and support aids are left to the developmental organization's discretion. Many organizations implement processes that develop and manage the various C4ISR artifacts as independent deliverables, which are often inconsistent. Removing these inconsistencies occupies much of the time and resources available at every developmental stage. Failing to recognize inconsistencies leads to actual developmental, integration, and operational problems along with expensive retrofit efforts.

This paper indicates how the use of a proven systems engineering process in concert with a comprehensive systems engineering tool significantly reduces these inefficiencies, establishes a stronger base for decision making, and allows management to mitigate strategic and developmental risks more successfully.
6.7.1 Leveraging Web Services in Product Design – Implications for System Engineering
Authors: Brunk Brett K.
Published: November 2014

The rise of the Internet has had a profound effect on application development and user interfaces. In a similar fashion, emerging web services technologies have the potential to change the way applications are assembled and re‐used. Web services provide application designers new building blocks for assembling a product that meets users' needs – at the same time, web services come with their own set of design constraints. For web services to be successfully incorporated into a product, it is important that system designers understand how web services change application design. This paper begins by exploring the main components of web services and shows how web services affect system design. In addition, web services introduce three concepts – modularity, re‐application and interface decomposition – that can be applied to general system engineering design.