bluuebunny/crossref_metadata_2025 huggingface dataset:
1.6.2 An Experience with a Multiformalism Specification of an Avionics System
Authors: Traore I. , Jeffroy A. , de Chazelles P. , Romdhani M. , Sahraoui A.E.K
Published: November 2014

This paper introduces a novel approach1 in the development of systems. The approach is based on a selective use of formal/semi‐formal specification languages by using the multiparadigm/multiformalism approach. It allows to combine different specification languages in the same environment. Used methods are StateCharts, SAO, and SDL for a specific avionics system as CMWC340. We give also an extended approach based on the same framework using Statemate and VDM to derive a global formal specification for the systems. This work can be considered as an experience return with preliminary results and also in an infrastructure/exploratory study. An ongoing perspective is the use of a common format based on industrial standard as VHDL‐AMS.
7.1. Applying the Systems Engineering Process: Building Improvements to a Business Management System
Authors: Stemm Douglas J. , Ahearn Susan M.
Published: November 2014

This paper describes a practical application of the Systems Engineering (SE) process to the continuous improvement of a Business Management System (BMS) at Raytheon Systems Company, Naval and Maritime Systems (NAMS) division, which documents how an enterprise conducts its business via processes. It further explains how to improve the BMS by requirements management and an architectural structure which accommodates merging the process documentation from two or more companies. In today's business environment of merger and acquisitions, a solid process merger strategy is of increasing importance. A consolidated company wants to leverage the best practices from each company that has been merged. BMS improvements also rely on a “recipe” approach and object modeling.

This paper will describe the ongoing results from a BMS improvement activity to verify, validate, and improve a BMS for an enterprise with multiple sites and a variety of customers and programs. The paper's first pass through the SE process focuses on aligning an enterprise's BMS to its drivers, so that it only documents and performs that which is necessary. The second pass through the SE process deals with mergers, where two or more companies with separate BMSs align into a cohesive enterprise.
7.4. DEVELOPING TECHNICAL STRATEGY WITH SYSTEMS ENGINEERING
Authors: Wray Richard B.
Published: November 2014

A successful technical strategy is critical for success in the high technology industries. But defining a successful technical strategy can be difficult, in part because there is little in the literature on developing and implementing successful technical strategies in Corporate America. The basis for much of the advanced thinking on effective strategies comes out of the military environment: what an effective strategy is and how it can be implemented. This paper briefly reviews some military thinking on strategy.

The major thrust of this paper applies systems engineering to the business system development problem. It identifies key technical elements of the business strategy, technologies to be used, company practices for a successful business, and positive feedback from customers. In this context, the issue is to systems engineer a business solution and an effective technical strategy.

A second thrust of this paper is to summarize the systems engineering process thus needed to perform this front end business system development. This paper describes the systems engineering process elements needed to implement technical strategy in the commercial environment.
1.1.3 Concept Exploration into an Australian Indigenous Space Launch Capability
Authors: Rogers Anthony J. , Tragesser Steven G. , Smith E. Price
Published: November 2014

This paper endeavours to explore the possibility of establishing an Australian indigenous space launch capability. The paper examines a trade space made up of a series of requirements and alterables derived from a mission statement and a set of objectives. This trade space is then optimised in an effort to maximise the benefits of such a capability, in order to determine whether the proposal is worth pursuing at the next level of system design.
1.1.4 Developing the International Space Station Integrated Verification Measurement Program
Authors: Haskins Bill R.
Published: November 2014

The International Space Station (ISS) Program Master Integration and Verification Plan (PMI&VP) requires that the systems engineering verification team establish and implement an integrated verification measurement program. This paper captures the knowledge and experience acquired through the International Space Station systems engineering efforts to develop, implement, and report a detailed set of integrated stage verification planning and closure metrics. The information and lessons learned, contained in this paper, may provide insight, direction, and a starting point for other large engineering organizations seeking to institute a measurement program.
4.1.1 Agent Systems Architectures for Complex and distributed Product Development Systems
Authors: Wenzel Stefan , Igenbergs Eduard
Published: November 2014

In complex system development projects the agent system describes the company's organization with its structures and resources carrying out all the tasks as agents. This includes all the individuals and organizational units (e.g., departments, teams, employees) as well as important resources like installations, machinery, equipment or tools, methods, software, specific know‐how (Negele, 1998; Negele & Wenzel, 2000). But when should we use which organizational structure or tool/method? Basically an adequate architecture and design of the agents/means to conduct a system development is highly interdependent from product and process architecture.

This paper provides a methodology, which allows us to measure the degree of integration within a distributed product development environment and to specify the cost associated. Thus, cost/benefit ratios can be calculated for different scenarios. Upfront it describes a framework, how product development environments, and the process‐, product‐, and agent‐system can be structured, classified, and how they are interrelated. On the basis of the product and process architecture organizational‐ and tool‐structure decisions for complex product development systems can be made
4.1.2 The Concept of a Decision Architecture For the Systems Engineering Development Process
Authors: Buede Dennis , Powell Robert A.
Published: November 2014

The purpose of this paper is to introduce the concept of a decision architecture for a life‐cycle balanced systems engineering process that addresses not only the design of an operational system but also the qualification of that design. This paper motivates the need for such a decision architecture, namely to drive the operational architecture of the development system. Elements and uses of the decision architecture are discussed. Sample topics in a decision architecture are shown for the operational and development systems. Finally some historical case material is presented on this topic.
5.1.3 How to Organize System Engineering in a Company – A Case Report
Authors: Zonnenshain Avigdor
Published: November 2014

System Engineering (SE) is an emerging area of expertise that comprises activities essential to project success.

Defense industries around the world are searching for an effective method of incorporating SE into Project Management.

The Ordnance Division of RAFAEL has taken a radical strategic step in strengthening its SE by creating a new department – The Systems Department.

The Systems Department comprises all System Engineers dedicated to SE project activities in the division and is responsible for the development and implementation of modern SE methodologies.

The Systems Department is dedicated to fulfill the following tasks within the organization:

Support concurrent engineering in projects

Incorporate support engineering (i.e. ILS, RAMS, Quality Engineering) in the project's life cycle.

Support planning and control of projects

Initiate ideas for new systems.

Promote strategic thinking and planning within the Ordnance Systems Division:

Launch knowledge management within the division.

The Ordnance Systems Division Management is ready to meet the challenge ahead, and believes that the Systems Department will prove to be successful in the short and long range.

Ordnance Division customers will benefit from the new department's “wise” approach on a multitude of issues such as:

Requirements Definition

Concept Development

Tests and Evaluation

Design Reviews.

If successful, this Systems Department could well become the organizational model for another companies and other RAFAEL divisions.
6.1.2 Determining the Impact of Change within your Method‐ and Toolbox for System Development
Authors: Wenzel Stefan , Igenbergs Eduard , Negele Herbert
Published: November 2014

To be successful in a highly dynamic environment, with increased global competition, shorter life cycles, more demanding customers/users, and more complex products, we have to strive for an effective and efficient product development system. In order to reach this goal, the right methods and tools are an important aspect, besides the right products, processes, strategies, requirements, people, etc. There are lots of different methods and tools well known, e.g., QFD, Taguchi, CAX, PDM, Robust Design, or DFX and most of them are applied (successfully?) in daily industrial practice. But what method or tool should we use, and when?

For the right product development method/tool box, a comprehensive framework is needed, which supports the selection, coordination, and assessment according to domain‐ and company‐specific needs and constraints. Unfortunately, tools and methods often are used because it is popular to use them, but not because they ideally support the solution of specific problems. Therefore, in earlier papers a systematic approach was proposed on how methods and tools can be selected for a successful product development system, independent of the industrial sector of a company, but dependent on its problems, market constraints, and declared goals (Wenzel & Bauch 1996, Negele et al. 1998, Wenzel et al. 2000).

This paper is an extension and a more detailed workout of the derived structured model, the “House of IPD” (IPD: Integrated Product Development). It was initially derived from the analysis of different product development processes at commercial companies in Germany, England, and the US (Wenzel & Bauch 1996). Two papers have already been presented at INCOSE symposia describing the structure, goals, benefits, and usage of the House of IPD (Negele et al. 2000, Wenzel et al. 2000).

In the House of IPD, the interdependencies and relations between goals and problems, essentials/ processes, and practices can be structured. It is possible to visualize in a matrix, how and to what extent (qualitative) the practices (HOWs) contribute to the realization of certain essentials (WHATs), and which essentials support which goals or solve which problems (WHYs).

In this paper, after shortly refreshing the basic concepts of the House of IPD, we will explain a method to determine the impact of changes in an existing method‐ and toolbox for complex system development. Therefore, the qualitative relationships represented in the House of IPD will be transformed into quantitative relationships. These can then be used to study the impact of methods & tools (HOWs) on essentials/ key success (WHATs) factors.
7.1.1 SE Tool Selection: Fact or Fiction
Authors: Stemm Douglas J.
Published: November 2014

This paper will discuss case studies of different processes for the selection of tools. There will be examples of each tool selection process, what drove the final decision, and what the aftermath of that decision was for particular projects involved. Finally, there will be conclusions about these case studies for selection of System Engineering tool processes and what should drive tool selection regardless of selection process. This paper is based on experiences in support of Navy ship developments, Air Defense Systems, Sonar Development, Command Control and Communications Integration.
7.1.2 Similarity Workshops as a Project Initiation Tool
Authors: Cavanagh Michael , Wood J.R.G.
Published: November 2014

This paper discusses the theory and initial results of the application of the ideas regarding ‘similarity’ introduced by Verma (Verma 1998) as a means of improving ‘left shift’ in the Systems Engineering lifecycle at BAE SYSTEMS. In particular, it concentrates upon the practical application of these ideas in a real world environment.
7.1.3 Systems Engineering Based Analytical Tool for Pollution Prevention
Authors: Pai Sundeep V. , Doukas Louis
Published: November 2014

This paper discusses the development and scope of application of a systems engineering based tool, termed PPAS (Pollution Prevention Analytical System), for environmental management of industrial estates with a major petrochemical component. The top‐level function of PPAS is to reduce/control the generation of pollutants over the whole life‐cycle of production and to minimise wastes and risks. The PPAS being developed at RMIT, is a synthesis of the systems engineering approach, cleaner production methods, optimisation techniques, microeconomic concepts, and the casual modelling and econometric methods which are relevant to the planning, design, and management of systems.
8.1.3 Quantitative Standards: Can INCOSE Survive Without Them?
Authors: Oliver David W.
Published: November 2014

INCOSE and its individual and corporate members have participated in the development of valuable systems engineering standards like 632, 1220, and 15288, for the propagation of best practices. These standards are qualitative in that they describe the work that needs to be done or list factors to be considered throughout the life cycle in vernacular text with illustrations. The information is exceptionally useful in instruction and in establishing best practices, but it is not measurable or executable.

In contrast, our culture and civilization has been advanced over the millennia by quantitative, measurable standards like the gauge of the railroad, the metric system, or HTML, XML, and site names for the Internet. Presently there is a surge in development of quantitative standards for information transfer in both the software and hardware worlds. This paper touches on some of these developments and raises the issue of how INCOSE can survive as a world leader in systems engineering unless it becomes a recognized leader in the development of quantitative standards through individual member and corporate member application of significant manpower to quantitative standards issues.

How shall the existing qualitative standards be extended to become quantitative standards for rigorous information transfer, and

How shall INCOSE organize and focus to lead this while leveraging from other larger worldwide efforts.
8.1.4 A Project‐wide Document Review Database System
Authors: McCowan Roger
Published: November 2014

Between 1991 and 1997, the Jindalee Operational Radar Network (JORN) was being developed by Telstra Corporation, together with several major sub‐contractors, to meet the requirements laid down by the Australian Department of Defence, in a MIL and DOD Standards environment. The Project's Verification and Validation Programme was established using IEEE Std 1012–1986, to assure the integrity of the design at all stages during the development of the JORN. To fulfil its role, the Verification and Validation Section designed and developed a Document Review Database System which facilitated the review, correction, and release of documents, as well as provide traceability for all document changes. This paper outlines the problems identified with document reviews, and describes a Document Review Database System which mitigates these problems.
2.2.1 Design of A Common System Architecture For A Medical Device Application
Authors: Gardner John R.
Published: November 2014

This paper describes the process used to design a common design platform for use in a medical device application. In addition to the process, the quantitative results and the relative impact are described. We conclude herein that the development of the common platform provides positive cycle time, unit cost, quality and reliability results.
3.2.4 Modelling and Analysis of Internet Multimedia Protocols
Authors: Liu Lin , Billington Jonathan
Published: November 2014

ITU‐T recommendation H.323 is the dominant standard for multimedia communications over packet‐based networks, including the Internet. This paper firstly reviews the H.323 standard, then proposes a formal analysis methodology for H.323 using Coloured Petri Nets (CPN). Some initial CPN modelling and analysis results for H.323 are given, and further work is proposed.
5.3.1 Systems Engineering Integration of Conceptual Design and Marketing
Authors: Vollerthun Andreas , Igenbergs Eduard
Published: November 2014

Continuing the thoughts that were presented at last years international INCOSE symposium this paper aims at integrating conceptual design and marketing by using a systems engineering approach. Applying a methodology that has been successfully implemented in a software tool for conceptual design‐ and cost‐modeling the next step that is taken in the presented work establishes the basis to also include marketing methods. By bringing technical product models and cost‐models together with a market model into one integrated model, an added value is generated for systems engineers since they are enabled to analyze entire business cases. Applying the described model allows designers to easily change parameters in the design and analyze the effects of these changes e.g. on market revenues. The paper describes some of the methods that the market model consists of, shows the interfaces to conceptual design and cost modeling, and discusses the integration into the overall design process as it is performed in many companies. As a reference on how the model can be applied data from the development of the European satellite navigation system ‘Galileo’ are presented.
5.3.3 The Journey of Software Process Improvement at ADI Limited
Authors: O'Brien Shaun
Published: November 2014

Over the past three years, ADI Limited's Information Systems, Software and Services (IS3) business in Perth has undertaken an extensive journey in software process improvement. Along the way the organisation has implemented many improvements to it's project management and software engineering processes. All staff in the organisation have been involved in the improvements in some way – from developing new procedures through to adopting and following them.

To make the journey even more challenging, the organisation has chosen to move Ada based development to Java, making extensive use of Internet/Intranet technologies.

At the time of submitting this paper, ADI was preparing to undertake a full capability assessment using the new Capability Maturity Model Integrated (CMMI) and determine where exactly we are on the map. The case study will look at past highlights of our journey so far and also what the future holds for us.
5.3.4 Cost & Performance Measures in System Design
Authors: Mirchandani Chandru
Published: November 2014

This paper will describe one model for optimizing the performance and reliability of a new system. The model defines cost‐performance and cost‐reliability measures. The paper provides an overview of how a design process using re‐configurable elements is accomplished. The process highlights the cost, performance benefits of a design currently being developed against currently available alternatives. The criteria for selecting performance and reliability metrics are cost optimization. This paper will demonstrate the improvement in reliability and performance as applied to a processing application, when this optimization process is used.
7.3.2 Measurements for the Safety and Mission Assurance of the International Space Station
Authors: Wade James W.
Published: November 2014

Effective and efficient programmatic decisions are required throughout the design, development, and operation of the International Space Station (ISS), which involves sixteen countries, over one million pounds of flight hardware, and an on‐orbit assembly process spanning six years. Paramount to the success of the ISS, are the safety and mission assurance (S&MA) aspects of the program. Various S&MA products, such as critical items (CILs), safety nonconformances, and problem reports, all provide an individual assessment of the program's risk throughout the design, development, and operation phases of the ISS life cycle. However, until recently, no method existed for measuring the overall S&MA risk of NASA programs. The NASA International Space Station Program's Safety and Mission Assurance/Program Risk Office (S&MA/PR) has developed such a metric.
4.4.2 The Process to Tailor COTS to ROTS for Military Applications
Authors: Velagapudi Sunil , Bitetto Mark F. , Delgado Suzanne A.
Published: November 2014

The defense industry has shifted away from detailed design specification‐based procurement to Off‐The‐Shelf procurement to reduce cost and development time, while taking advantage of increased availability and performance.

The spectacular growth of the commercial electronic industry gives the military system developer a myriad of appealing options. However, despite the increased availability and affordability of commercial hardware, the complete solution to a given problem is often not found in supplier catalogs because of system level requirements (size, weight, power, performance, networking, and interface) and stringent environmental requirements (temperature, humidity, and vibration) levied on military hardware.

Transition from the myth of Commercial Off‐The‐Shelf (COTS) to the reality of Ruggedized Off‐The‐Shelf (ROTS) is a difficult challenge. The challenge is to understand the product, the supplier capability and environment, and in response, tailor the requirements. Tailoring refers to the entire COTS selection and modification process, including changes to product requirements and system requirements.

The focus of this paper is to define the process of tailoring a partially compliant COTS product to ROTS to meet the functional, environmental, and packaging requirements of a military application. To illustrate the process, an example of the tailoring of hardware from COTS to ROTS for the U.K. Ministry of Defence (MoD) Nimrod Maritime Reconnaissance Aircraft 4 (MRA4) project is presented.
8.5.3 A Framework for a Systems Engineering Body of Knowledge
Authors: Kasser Joseph , Massie Angus
Published: November 2014

At this time, systems engineering has no recognized body of knowledge. Without such a body of knowledge, systems engineers have difficulty agreeing on exactly what systems engineering should be and academia has difficulty in teaching it. This paper first summarizes a number of models of systems engineering and proposes a framework for a systems engineering body of knowledge (SEBOK) based on a combination of two of the models. The paper then proposes a road map for the development of the SEBOK, a way to offer a world class postgraduate degree and closes with some perspectives on systems engineering that become visible when system engineering is viewed within the framework.
8.5.4 Technological Forecasting: A Soft Systems Perspective
Authors: Stajnko Frank , Doukas Louis
Published: November 2014

The art and science of technological forecasting is the greatest weakness of strategy making. In dynamic and complex environments it is extremely difficult and perhaps even impossible. This is because the future tends to emerge from these situations in ways that defy conventional forecasting techniques. In fact systemic emergence is often considered impossible to model in this way. Most of these techniques are linear, deterministic and inflexible in nature, which is why they are often described as being hard. A soft perspective is required in order to understand the subtle complexities involved and to show how existing models them selves can change with time. This paper looks at the common forecasting techniques used, the problems encountered and how the application of Soft Systems Engineering can make a difference.
2.6.1 The Value of Adding Digital Print Technology to Existing IPDT Collaboration Systems
Authors: Brown Phillip J. , Kuchelmeister Frank R. , Lavender Jack
Published: November 2014

Timely and reliable information exchange is a hallmark of successful collaborative product development endeavors. The continuing challenge for organizations seeking to improve productivity is how to select and deploy technologies that provide the best return on their investment. This paper documents the process that LMMFC‐D (Lockheed Martin Missiles and Fire Control ‐ Dallas) followed in selecting digital print technology to improve Integrated Product Development Teams (IPDT) performance across several programs. Cost benefit results are included.
4.6.2 Systems Thinking for Joint Force Capability Planning and Management
Authors: Matthews David , Burke Martin , Collier Phil , Cook Stephen
Published: November 2014

Joint Forces are anticipated to play an increasingly important role in the Australian Defence Organisation. This paper provides a way of thinking about Joint Forces intended to support activities such as Joint Force capability planning and management. The central approach is that of systems thinking. This approach is applied to develop a set of core concepts associated with strategic planning for future capabilities. In particular the idea of a portfolio is introduced as a management tool for future capability planning. The concepts developed are presented as elements within a system of ideas designed for the activities of long term planning for Australia's Joint Force capabilities and the assessment and day‐to‐day management of these capabilities.
1.7.3 Conceptual Design of Building Automation System by Applying Systems Engineering Approach
Authors: Yoo Il Sang , Park Young Won
Published: November 2014

As the 21st century signifies an information‐oriented society, the computer integration takes place in all walks of human presence. Needs for computer and network‐integrated building present new challenges in building industry. After the first intelligent building appeared in USA in 1984, it gradually became an essential capability for the building industry requirement these days. Intelligent Building System(IBS) is very complex because there are many subsystems such as telecommunication(TC), office automation(OA), building automation(BA), construction environments, etc. During the planing phase of IBS development, therefore, systems engineering must be performed to analyze stakeholder's requirements to build an optimized system while minimizing trial‐and‐error expenses and risks. This paper presents a conceptual design of BAS by applying systems engineering methods. That is, we developed an IBS subsystem specification for building automation subsystem, which is a part of IBS, using the methodology of requirement analysis, functional analysis, synthesis, and verification where we used a computer‐aided systems engineering tool, RDD‐100, as an example s/w for system design efficiency and product design knowledge management.
5.7.2 The Data Standard AP‐233: An Invigorator for Global Systems Engineering
Authors: Johnson Julian , Herzog Erik
Published: November 2014

Contemporary systems engineering developments are frequently global in scope, and ‘distributed’ in both graphical and temporal senses, involving many different design and analysis tools, across systems engineering and various specialist engineering disciplines. Currently there is little interoperability between these suites of tools. This situation can have real stagnating effects on systems engineering activities, and considerable detrimental economic, productivity and quality consequences. Neutral data exchange is one solution to this problem. The AP‐233 systems engineering data interoperability standard will be fundamentally important, making global systems engineering in heterogeneous design environments possible. The aims, approach and results to date of the SEDRES‐2 project, the most recent AP‐233 data model, and the relationship to other areas of work, are described. Several business scenarios where AP‐233 has the potential to make a significant contribution are explained. A mature semantic‐level systems engineering interoperability standard is an essential enabler and a significant invigorator to distributed systems engineering.
3.1.4 Emergence: A Partial History of Systems Thinking
Authors: McConnell George R.
Published: November 2014

Systems Engineers require a good knowledge of both engineering and systems concepts. Inevitably, there will be few who are equally strong in both areas of knowledge. This paper offers a brief overview of the history of systems thinking, concentrating primarily on those areas which relate specifically to the understanding of emergent properties of systems. Whilst inevitably only a whistle stop tour of the subject the paper offers insight into both the depth and the breadth of systems knowledge available. It is intended as a starting point for those interested in finding out more.
9.2.8 Value of Systems Engineering – SECOE Research Project Progress Report
Authors: Honour Eric , Mar Brian
Published: November 2014

This paper is a progress report on the results of a SECOE research project to collect and analyze data that describes project cost, schedule, and quality with systems engineering cost and quality. The original hypotheses to be tested were that (a) at low levels, increasing systems engineering effort results in better project quality, and (b) there is an optimum above which further increases are detrimental. The collection of data is much more difficult than anticipated. The preliminary results are presented in an attempt to encourage more individuals to submit data. Analysis of the preliminary data (25 project submissions) supports the hypotheses. The data suggests that dimensionless ratios of actual to planned cost and actual to planned schedule correlate with an independent variable defined as an index of systems engineering effort (product of systems engineering cost and systems engineering quality divided by total project cost).
1.6.3 A Systems Decision Modeling Approach to Electrical Generation Capacity Planning
Authors: Leeprechanon N. , Moorthy S. S. , Brooks R. D. , Ellis M. , Sappakitkamjorn J.
Published: November 2014

This paper presents modeling techniques for planning electrical generation capacity where demand is uncertain. We present traditional solutions to the capacity generation problem using a deterministic programming model based on both simple and complex demand scenarios. We then present a systems approach, employing a unique two‐stage stochastic programming model that employs random parameters, which operate on deterministic model data, over the range of all possible scenarios. This systems model enables the expected cost of uncertain demand information to be calculated (ECII), and candidate stochastic solutions (VSS) to the capacity generation problem to be evaluated.
3.3.3 Assessing System Development Tool Integrity
Authors: Beland Steven C. , Dagli Cihan H.
Published: November 2014

Computing tools are often used to develop and evaluate complex systems in many industries. Use of such tools enables the increasing complexity of today's systems but introduces the potential for system problems due to potential errors introduced into the system by development tools or by misleading results from evaluation tools. The consequences of tool‐related problems may range from insignificant to catastrophic, introducing risk from both the economic and safety perspectives. This paper shows how to identify the risk of potential problems introduced by the use of such tools in an overall system development context and mitigate or eliminate these risks, building on guidance originally created for the lower system abstraction levels of software and electronic hardware for commercial aviation.
5.5.3 Predicting USMC SBIR Phase I to II Transition Success by Evaluating Use of Systems Engineering Capabilities
Authors: Petee Danny A. , Componation Paul J.
Published: November 2014

Defense research & development budget cuts, increased pressure from the acquisition community to find research funding, and a congressional directive enforced by the under secretary of defense for acquisition and technology have created a climate where the u.s. marine corps SBIR program must improve its ability to transition technology it develops into acquisition programs. One approach to accomplishing this is by applying systems engineering to the SBIR process. Though no formal systems engineering process exists for its SBIR program, the marine corps wishes to understand the relationship between the systems engineering capability of phase I SBIR projects and their likelihood of transition to phase ii. This study seeks to shed light on that question.
1.2.3 A Systems Engineering Approach to Occupant Protection System Design and Optimization through Modeling and Simulation
Authors: Zhang glu , Ma Deren
Published: November 2014

Occupant Protection Systems (OPS) have become a very important part of today's automotive systems. The extensive government regulations and consumer information programs make the design and optimization of the advanced OPS a complex and challenging task. A Systems Engineering (SE) approach is implemented throughout the OPS design and optimization process. The SE process includes customer requirements analysis, system concept design, system design, analysis and optimization and system verification and validation. To fully evaluate the performance of the OPS and ensure its compliance of government regulations, the system needs to be tested in a large number of crash scenarios. Using physical tests alone to develop the OPS is cost prohibitive. Therefore, computer modeling and simulation are utilized as one of the primary tools in the process. A frontal impact OPS design and optimization example is presented in the paper to demonstrate the process.
1.4.3 Learning Organizational Lessons
Authors: Sheard Sarah
Published: November 2014

Learning and applying lessons is one requirement for continuing to improve business processes. Too often, companies neither collect lessons nor apply them well, or else they collect lessons well but have difficulty incorporating the lessons into future work. This paper describes the phases of learning lessons, necessary cultural factors and infrastructures, and how lessons‐learned programs evolve over time. The phases of a process for learning lessons are identification and collection, analysis and description, and communication and implementation. Additionally, this paper shows many dimensions of lessons‐learned efforts, provides pointers to many examples available online, and helps the reader establish a strategy for improving the ability of the organization to learn lessons.
2.4.3 Evolving Systems Engineering Processes: Moving from “What Systems Engineers Do” to “Engineering Systems“
Authors: Sheard Sarah , Holzer Thomas H.
Published: November 2014

Companies have documented systems engineering processes for years, in order to describe what the people they call “systems engineers” do to help product development. In an era of integrated processes, however, it becomes apparent that systems engineering is by its nature an integrating process. Therefore, true engineering of systems works better with an integrated set of engineering processes, within which are systems engineering roles. This paper describes why systems engineering processes are evolving in this manner, as well as how to evolve processes that describe what systems engineers do into an integrated set of processes for engineering systems.
2.5.2 Systems Engineering in an Outsourcing Environment
Authors: Parth Frank R. , Gumz Joy
Published: November 2014

Outsourcing is the process of hiring someone else to do work that a business cannot, or does not wish to, do itself. While businesses have always done this, the entire field of outsourcing has taken on new dimensions and in the past few years has become vastly different from what it once was. Now companies are outsourcing significant portions of their core application development work overseas as well as areas such as order processing, help desks and others, justified by a lower cost per unit. As a result of overseas outsourcing, significant problems have arisen that either did not exist before or were easy to remedy when the work was done internally. Many of these problems can be traced to poor or missing requirements, a poor understanding of business processes, or to technology and security problems in the deliverables. This article discusses the role of systems engineering in avoiding or reducing the most significant problems. Rather than just gathering functional and performance requirements, systems engineers must now develop an entire requirements encyclopedia in order to provide enough information, do much more detailed business process analysis, and help develop testing and quality assurance approaches that can detect security back doors that may have been put into software products.
2.6.2 Systems Engineering Sizing in the Age of Acquisition Reform
Authors: Valerdi Ricardo , Ernstoff Michael , Mohlman Paul H. , Reifer Don , Stump Evin
Published: November 2014

As organizations develop more complex systems, increased emphasis is being placed on Systems Engineering (SE) to ensure that cost and schedule are within budget. Correspondingly, the failure to adequately plan and fund the systems engineering effort appears to have contributed to a number of cost overruns and schedule slips, especially in the development of complex ground and space systems. Government and commercial organizations have recently placed increased emphasis on accurately planning the SE function and on understanding the factors that influence the resources needed to implement and perform SE.

In an attempt to better quantify the SE activity, the DoD acquisition community has been exploring Systems Engineering Revitalization and migrating back to a reinstatement of prescribed military standards. Several models and tools have become available to aid in forecasting systems engineering resource needs, but few guidelines exist to help engineers and program managers determine which approach is best suited for estimating any particular effort.

To provide such guidelines, this paper provides an overview of eight existing cost models ‐ three of which focus on software and five on hardware. These models include SE components and employ unique approaches to sizing the SE effort. An overview of the genesis and assumptions of each model shed some light on their individual applicability. To complete the paper, future research topics are discussed along with recommendations on tasks to enhance the accuracy of SE sizing.
3.2.2 Optimal and Adaptable Reliability Test Planning Using Conditional Methods
Authors: Powell Mark A.
Published: November 2014

Developing optimal cost verification strategies for performance requirements using the analysis or test methods can be difficult, if not impossible. Developing such a strategy that is also adaptable to unexpected test results is even more difficult. The author investigates a reliability requirement verification example from the automobile industry for cost optimization and adaptability to unexpected failures using classical methods. Verification strategies for this example are then developed using conditional methods. These conditional verification strategies demonstrate significant cost efficiencies, and provide easy adaptability to unexpected failures. These strategies further provide understandable decision criteria for test success or failure. Using conditional methods for verification of performance requirements provides opportunities for cost savings, adaptability to unexpected test results data, and clear decisions for product acceptance.
3.3.1 Consumer product development: A systems engineering approach to the derivation of design requirements from stakeholder needs
Authors: Agouridas Vassilis , McKay Alison , de Pennington Alan
Published: November 2014

This paper reports results of research into the engineering design of consumer electromechanical products. The research dealt with the derivation of design requirements from stakeholder needs. An approach based on principles of systems engineering was developed, applied and evaluated through a number of case studies that were carried out in three industrial domains. The evaluation showed that the approach can significantly improve the quality of product designs. The revision of the expressed stakeholder requirements and the expression of stakeholder requirements as stakeholder needs and stakeholder attributes were found to be key factors towards the improvement of product designs. It is recognised that there are many difficulties associated with the identification of stakeholder needs for both existing and new products. However, given a need, benefits can be gained from providing information to support traceability between design parameters, design requirements, stakeholder attributes and stakeholder needs; such traceability is a key enabler to downstream integration management.
3.4.3 Genomics: Requirements Going From Art to Industry
Authors: Kosack Daniel
Published: November 2014

Genomics is a new science that is contributing significantly to our understanding of genes, life processes, and disease. Genomics endeavors to look at the entire organism – the complete DNA ‐ to study its entire gene set, observing mutations and diversity. Producing the entire DNA sequence and identifying the genes within is no easy task. As budgets are cut and cost becomes more important, the role of organized software and systems engineering becomes more pronounced.

This paper describes the systems used at the Institute for Genomic Research (TIGR) to produce the sequence of an organism. The paper begins with an overview of the overall Genomics process. It follows with a discussion of the human genome project and how lessons learned from the project regarding scale and capability have affected the Genomics view of systems design. The paper continues with discussion about the need for traceable, consistent requirements and organized system design in Genomics. Finally, the paper discusses how the Institute for Genomic Research recognizes and addresses the need for proper systems development through requirements gathering and analysis, system decomposition, and rework.
3.6.2 Successful Integration of Systems Engineering and Program Management Processes
Authors: Witte Craig S.
Published: November 2014

Since the inception of Systems Engineering as a discipline, Systems Engineers (SEs) have been providing technical leadership toward the successful completion of projects. As the science of project management has evolved, SEs and Project Managers (PMs) have grown more interdependent. In fact, there are many similarities in the skills required for Systems Engineers and Project Managers.

This paper will provide a summary of the shared skills between both SE and PM professionals. A description of the interaction between SE and PM disciplines in various organizational structures will also be presented. A comparison will be made between PMI's view of product realization and the standard “Vee Diagram” process understood by most Systems Engineering professionals. And lastly, this paper will conclude with a description of the project management process followed at the Harris Corporation. Survey results will be presented illustrating the distribution of traditional project management functions between Project Managers, Systems Engineers, and Project Engineers.
4.1.1 Benefits in Using Object‐Oriented Methodology For Architecture Modeling
Authors: Osvalds Gundars
Published: November 2014

Currently enterprise and systems architecture models being developed by Systems Engineers to describe the stakeholders' problem often use the Structured/Functional Methodology while software designers usually use the Object‐Oriented Methodology. Thus, architectures represented with Functional Representation may not be fully implemented, as designed, by the software developers who use Object‐Oriented Representation. The systems engineer should consider the benefits in utilizing an Object‐Oriented Methodology in developing the architecture design. A benefit, in the use of the same representation, is the ability to create a concordant set of engineering products that are traceable from the design to the system implementation. Another benefit is that the Object‐Oriented Methodology is that it closely matches the stakeholders' view of the world which consists of objects that perform actions and utilize information. Therefore the use of the Object‐Oriented Methodology in the design and documentation of enterprise and system architectures provides reusable design artifacts for the software developers.
4.3.1 Security Engineering: Systems Engineering of Security through the Adaptation and Application of Risk Management
Authors: Gilliam David P. , Feather Martin S.
Published: November 2014

Information Technology (IT) Security Risk Management is a critical task in the organization, which must protect its resources and data against the loss of confidentiality, integrity, and availability. As systems become more complex and diverse, and more vulnerabilities are discovered while attacks from intrusions and malicious content increase, it is becoming increasingly difficult to manage IT security. This paper describes an approach to address IT security risk through risk management and mitigation in both the institution and in the project life cycle. The application of risk management to security engineering is described. Support for this through application of a security risk algorithm and a risk management tool for risk analysis is also discussed.
4.6.1 Combining Heuristic Search, Visualization and Data Mining for Exploration of System Design Spaces
Authors: Feather Martin S. , Kiper James D. , Kalafat Selcuk
Published: November 2014

Finding a near‐optimal solution to a complex design problem is challenging. On the one hand the problem space is too large and convoluted for human comprehension, while on the other hand it is infeasible to elicit the entirety of design knowledge required for fully automatic problem solving.

We report on a practical application of information technology techniques to aid system engineers effectively explore large design spaces. We make use of heuristic search, visualization and data mining, the combination of which we have implemented within a risk management tool in use at JPL and NASA.

This approach is demonstrated on the planning for development of an advanced technology for spacecraft applications. In this context of risk‐informed design, numerous risk abatement options give rise to a huge space of potential design solutions. We show how our approach enhances the system engineers' ability to explore this design space.
5.1.1 From Stakeholder Values to Product Requirements
Authors: Weiss Stanley I.
Published: November 2014

The identification of all stakeholders, as well as their values, has become a basis, often insufficiently achieved, for understanding, prioritizing and realizing requirements for a product. Traditionally, these are gathered from a variety of sources and a widely used method for organizing, evaluating and tracking customer needs translation to design information is Quality Function Deployment (QFD).

QFD is commonly understood as a matrix tool for collecting, organizing and prioritizing data for evaluation of requirements and their translation to technical characteristics of a system or product. Since true requirements are derivatives of the values of the many stakeholders associated with complex systems or products, a sequence of identifying stakeholders with their values and prioritization, leading to the development of requirements, provides a logical path to product design characteristics. QFD provides a means that facilitates this.

The method described here has further value for data collection, reference and traceability since it is highly adaptable to changes in stakeholders and values