bluuebunny/crossref_metadata_2025_split huggingface dataset:
10.2.1 The Dual Vee – Illuminating the Management of Complexity
Authors: Mooz Hal , Forsberg Kevin 
Published: November 2014

AbstractThe Waterfall, Spiral, and Vee models are reminder models that guide us to less perilous paths when developing solutions to problems. Dr. Royce's Waterfall (Royce 1970) provides an orderly approach to software development. Dr. Boehm's Spiral (Boehm 1988) provides emphasis on solving known software risks before proceeding with Royce's Waterfall. The Forsberg/Mooz Vee Model (Forsberg 1991) embraces full systems development by including details of integration, verification, and validation and opportunity and risk management in the symmetry of the Vee development sequence. However, all of these single solution development models fail to address the necessary concurrent development of a system's architecture with the entities of that architecture. The Dual Vee Model introduced in Visualizing Project Management, 3rd Edition in 2005, does just that and illuminates the necessary interactions and sequences recommended for orderly maturation of a system and systems of systems. This paper explains the power of the Dual Vee Model when applied as a reminder model for development of complex systems.
10.2.2 IDEF0 Lessons Learned
Authors: Smith Darold K. 
Published: November 2014

AbstractThe IDEF0 methodology is becoming widely used as a tool in all types of systems. If a program is considering using IDEF0, there are serious pitfalls to avoid to assure that using IDEF0 provides as accurate and complete system definition that IDEF0 is capable of supporting.The pitfalls are illustrated with three case histories to support the lessons learned. Some lessons apply to other methodologies beyond IDEF0. Although IDEF0 has been in use for many years, it is still being applied to new programs and the lessons learned are timely.
10.3.2 An Enterprise Systems Engineering Model
Authors: DeRosa Joseph K. , Rebovich George , Swarz Robert S. 
Published: November 2014

AbstractThe INCOSE (ANSI/EIA 632) systems engineering model may not be adequate for an enterprise environment, in which environmental influences and the interaction of people, processes, and technology are not taken into account. This paper considers some “systems thinking” concepts and applies them to develop an expanded model that may be more appropriate in the enterprise environment.
10.4.1 Certification & Accreditation – The Role of Security Engineering in the Systems Development Life Cycle
Authors: Tysenn Jeff 
Published: November 2014

ABSTRACTSecurity is most effective if it is planned and managed throughout an organizations Systems Development Life Cycle (SDLC). Many security risks, analyses, and events occur during a systems or applications lifetime and these issues should be dealt with from the initial planning stages and continue through all phases of the SDLC. Many systems today must also address Certification and Accreditation (C&A) before going operational. C&A facilitates including security as an element of the SDLC assuring that a clear set of Security Requirements is developed and implemented, residual risk is minimized and clearly understood, and all security controls developed and deployed in the final operational system are documented in a System Security Plan. This paper examines the role of security engineering and their activities throughout the SDLC and the C&A process, the guidance that helps define the Security Requirements, and the roles of the people involved to provide a basic understanding of security engineering as it applies to C&A throughout the SDLC. One of the objectives of this paper is to help Program Manager's understand and take into account the C&A process into program plans and schedules.
10.4.2 Managing compatibility throughout the product life cycle of embedded systems – Definition and application of an effective process to control compatibility
Authors: Bornemann Falk , Wenzel Stefan 
Published: November 2014

AbstractDue to the fact of increasing complexity in modern embedded systems, problems associated with compatibility have become an important issue when managing product life cycles. The question of how to maintain and restore the system wide compatibility throughout the entire product life cycle is yet to be answered. So far, compatibility management has not been established as a standard procedure among the traditional and established business areas. Even the CMMI (Capability Maturity Model Integration) [Chrissis, M. B.; Konrad M. and Shrum S. “CMMI – Guidelines for Process Integration and Product Improvement” Carnegie Mellon Software Engineering Institute, (2003 by Pearson Education, Inc.)] does not classify compatibility management as a specific single process area.This paper gives a first impression of what an effective compatibility management needs to deliver and how it should be integrated into the product life cycle process.Furthermore, in the following paper process are being defined and applied of how to manage and remedy problems associated with compatibility. Procedures will be described and their functionality will be explained. With the help of that process incompatibilities can be removed and system‐wide compatibility can be maintained throughout the entire product life cycle of an embedded system. The paper also shows that without clearly defined processes that describe and help how to remove incompatibilities, maintain and restore system wide compatibility, especially during system updates and upgrades, the time, money and effort spend to secure the functionality of complex embedded systems will reach uneconomical levels.
11.1.3 An introduction to Network Centric Warfare
Authors: Gastelum Alejandro , Dagli Cihan H. , Miller Ann 
Published: November 2014

AbstractThis paper gives a short explanation of Network Centric Warfare, some background information and technology that makes this a reality. It also provides an example of how network centric solutions can be used to do a kill Chain and its advantages over platform centric scenarios. NCW faces a lot of challenges to System Engineers interoperability, increased complexity, fault tolerance, distributed computing are all needed to be understood to make NCW a reality. The nature of network centric makes us focus also on wireless networks and how they can be used, its advantages, protocols, and later on two frameworks implemented by Sun, Jini an Jxta. Each has its own set of protocols, procedures and ideology, and both are being used to create very reliable networks with changing topology.
11.2.1 Challenges in the application of systems engineering principles to the design of appealing consumer products
Authors: Agouridas Vassilis , Longstaff James , Childs Tom , McKay Alison 
Published: November 2014

AbstractThis paper reports results of research carried out in the context of a co‐ordination action funded by the European Commission that dealt with the gathering and evaluation of state of the art tools, best practice methods and techniques deployed by leading manufacturers in developing appealing consumer products. Data was gathered through questionnaires and semi‐structured interviews. Analysis of the data showed that the design of appealing products involves an intricate web of relationships amongst understanding consumer needs, determining and verifying product characteristics, and validating products that excite consumers. The need for a systems engineering approach in rationalising such an intricate web of relationships is described based on the research findings. A number of challenges associated with the implementation of such an approach are discussed.
11.2.2 The Systems Project: Life Cycle Development/Management of as Many as Four Interrelated Systems
Authors: Paul Arthur S. , Owunwanne Chinweizu 
Published: November 2014

AbstractWork presented at this Conference previously proposed the Producing System (or enabling system) as a mechanism for organizing and managing the enabling resources in the development of a Product System (Alias, required system, system‐of‐interest, intervention system, end product, operational system, etc.). It presented the producing system as separate from, but closely related to, the product system. Specifically, the relationship was equated to that of a parent: child (producing system: product system) relationship.(Paul and Yerace 2004)This paper explores current practices regarding the identification and processing of systems that interact with, or have some form of involvement in the life cycle of, the product system. The primary focus is, of course, the interrelationship between the product system and the enabling resources or producing system; however, studies have identified diverse interactions with competing systems, context systems, collaborating systems, containing systems, and others. This paper identifies the similarities and differences among the various perspectives.Finally, the paper expands on these concepts by introducing the Systems Project as a family of up to four closely related systems whose interactions are focused on the life cycle (birth to death) of the product system. Specifically, the Systems Project is a framework for packaging and conducting all of the systems engineering activities associated with developing/managing the product system, the producing system, the Existing System (if there is one in place, if applicable [I/A]), and the Maintenance and Support System through the life cycle of the product system.
11.4.2 Top 40 Systems Engineering Work Products From Phrase Lists and Self‐Organizing Maps
Authors: Beshore David G. 
Published: November 2014

AbstractA computer‐automated method using semantic web algorithms is described that ranks the best systems engineering work products on websites and corporate repositories. The process is both server‐based and PC‐based to automate the capture and ranking of knowledge from industry experts within The Aerospace Corporation. A virtual Process Assets Library system (vPALs) economically collects and self‐organizes documents through long lists of phrases (phrase vectors) using next‐generation web engines. Ranking documents implements scoring algorithms with phrase vectors in the development of 1‐D, 2‐D, and 3‐D self‐organizing maps (SOMs). vPALs is being deployed in 1) real‐time decision making during launch vehicle systems testing and day‐of‐launch at Cape Canaveral and Vandenberg, 2) proposal technical evaluations, 3) data mining and maintenance of corporate document repositories, 4) formal design reviews with customers, and 5) web‐based systems and software engineering books of knowledge. Nine websites are used in this paper to rank order the most relevant documents related to SE workproducts: NASA‐PBMA FAA‐ASD, FAA‐IPG, SEI, SEPO‐SPAWAR, SMC, DAU, STC and Aerospace's AeroLink corporate document repository.
11.4.3 Advancing the Canadian Capability Engineering Approach
Authors: Lalancette Claire , Lizotte Michel , Nécaille Christophe , Robbins Wayne , Waruszynski Barbara 
Published: November 2014

AbstractThe Collaborative Capability Definition Engineering and Management Technology Demonstration (CapDEM TD) project is investigating Capability Engineering (CE) in order to support the Capability‐Based Planning (CBP) decision‐making process. This paper presents the evaluation effort being applied to the Capability Engineering approach, a methodology based on the systems engineering paradigm and articulated around three axes: People, Process and Materiel. Originating from the laboratories of Defence R&D Canada, the CapDEM effort is now evolving from theory into practice, based on an on‐going evaluation strategy concretely realized via three validation exercises that consist of realistic simulations of people applying the process and materiel to resolve capability gaps. This paper details the evaluation strategy and includes lessons learned from the first and second validation exercises. The tenets and expectations from the final exercises will form the final part of the paper, with the intent of providing insight into the advancement of capability engineering.
Development Program Risk Assessment Based on Utility Theory
Authors: Ben‐Asher Joseph Z. 
Published: November 2014

AbstractA methodology for risk assessment is introduced based on Utility Theory. The main idea is to quantify the risk consequences by using an equivalent lottery where the probability of getting the worst possible risk outcome is taken as the value representing the risk consequences. This improves the evaluation process by making it more systematic, and justifies the use of the expected value for obtaining the risk factor. The idea is compared with other methods and is demonstrated by a case study.
Can Systems Modeling Language Impact Systems Engineering?
Authors: Orr Kevin , Ramakrishnan Sreeram , Dagli Cihan H. 
Published: November 2014

AbstractThis paper examines the System Engineering processes/applications transforming from being document‐centric to being model‐centric by examining the benefits and uses of the Systems Modeling Language (SysML). This paper will look at the concept behind SysML and provide a background on existing research to address the Unified Modeling Language (UML) Systems Engineering request for proposal to generate SysML. This paper will identify benefits of using SysML in the Systems Engineering process and makes a recommendation for its use in large scale integration projects and complex hardware and software designs.
Preparing SEBoK for Korea Defense Systems Acquisition Processes
Authors: Han Myeong‐Deok 
Published: November 2014

AbstractJust as INCOSE tried to set up G2SEBoK, Korea Council on Systems Engineering is now trying to set up its own Systems Engineering Body of Knowledge so that its members and other people related to Korea Defense Acquisition Processes can share a common perspective about what is SE, what is the core of the SE processes, How we do it, etc. Here is the report of the first draft of KCOSE SEBoK list of contents with some description of how we approach this problem.
1.2.0 Panel 1.2.0: Heading Down a New Track: Growing an SE Practice in a Big, Bureaucratic, Legacy Enterprise
Authors: Ericsson C. , Brouwer P. , Gharatya K. , Halliday B. , O'Neil A. 
Published: November 2014

AbstractAfter over 100 years of traditional design and construction, the rail industry is now tailoring Systems Engineering processes to cope with the complexities of its capital projects. This industry is attempting to accomplish in ten or fifteen years what has taken aerospace and defense 50 years to achieve—‐ that is, to embed an SE approach into the fabric of its business. Four panelists will share how their big, bureaucratic and very conservative organizations are transforming to meet today's challenges. They will describe how they are dealing with the driving forces of system interoperability and dynamic technologies and the restraining forces of severe SE competency shortages and institutional barriers to cross‐disciplinary teamwork. They will share how they are changing their contracts, design documents and procedures, and how they are adapting design tools and approaches to deliver successful projects and improve life‐cycle systems performance. These are the early chapters of an entire industry in flux.
1.3.4 Model‐Based Design and Verification of Fault‐Tolerant Systems
Authors: Sorea Maria , Ruess Harald 
Published: November 2014

AbstractThere is an increasing trend towards model‐based development (MBD) of safety‐critical systems. In an MBD approach, various development activities such as simulation, testing, code generation, and verification are based on a single formal model of the system. In this paper we show that the MBD approach can also be applied towards automating the safety analysis process. Using precise formal models of the system as the basis of the analysis helps avoiding design errors at early stages in the development lifecycle. The analysis is automated by means of model‐checking tools, which results in a more thorough analysis and reduced manual effort compared to more traditional methods. We illustrate model‐based analysis using the fault‐tolerant startup protocol for a time‐triggered middleware architecture (TTA). For a functional model of this protocol, it is verified that the specified safety requirements are satisfied in the presence of all faults within the given fault hypothesis. We demonstrate that exact, complete, and consistent safety analyses can—and in fact should—be carried out for relevant industrial designs in very early phases of the development life cycle and in an automated fashion.
1.4.2 A Model for Successful Engineering Internship: Growing Our Own Future Engineers
Authors: Malloy Mary Ann 
Published: November 2014

AbstractUCLA's Higher Education Research Institute reported there has been a 60% drop in science and engineering majors among incoming college freshmen since the year 2000. Competition for the dwindling number of graduating entry‐level engineers is fierce. At the same time, the academic experience of engineering rarely emulates what students can expect in the real world. Students need relevant work opportunities to validate their career plans while keeping them engaged in their engineering degree programs. Two years ago, we established an Internship Program to respond to both sides of this challenge. Internship expands the concept of training beyond enhancing the skills of existing staff, to include a company making a training investment in student engineers they might like to hire full‐time someday. In this paper, we provide a template for our successful Internship Program as a model for other employers who would like to “grow their own” entry‐level engineers.
3.2.2 Enabling Economics‐Driven Systems Engineering Through Reusable Software Architectures and Components
Authors: Selby Richard W. 
Published: November 2014

AbstractEconomics‐driven systems engineering integrates system design principles with measurement‐based analyses of value, options, and tradeoffs. This study helps enable economics‐driven systems engineering by describing an example of measurement‐based analysis of software reuse in large‐scale systems. Software reuse enables developers to leverage past accomplishments and facilitates significant improvements in software productivity and quality. Software reuse catalyzes gains in productivity by avoiding redevelopment and gains in quality by incorporating components whose reliability has already been established. The purpose of this study is to characterize software reuse empirically by investigating one development environment that actively reuses software. Twenty‐five software systems ranging from 3000 to 112,000 source lines have been selected for analysis from a NASA systems development environment. The amount of software either reused or modified from previous systems averages 32% per project in this environment. Non‐parametric statistical models are applied to examine numerous development variables across the software modules in the systems. This research focuses on initial results and graphical characterizations of the data. Four classes of software modules are analyzed: (a) modules reused without revision, (b) modules reused with slight revision (< 25% changes), (c) modules reused with major revision (≥ 25% changes), and (d) newly developed modules. The modules reused without revision had the fewest faults, lowest fault correction effort, and lowest fault densities. In conclusion, we outline future research directions that build on these strategies and ideas.
4.4.1 Rule‐Based Design Reviews
Authors: Gilb Tom 
Published: November 2014

AbstractDesign reviews would benefit from the support of Specification Quality Control (SQC). By the use of SQC with a set of relevant design review rules, it should be possible to ensure prior to a design review that all the relevant information for a review is present in the design specifications, and that all the minimum review criteria are met. This will ensure management time is not wasted and aid better decision‐making.In addition, this paper outlines the impact of Evolutionary Project Management (Evo) on the design review process.
4.4.2 Measurement‐Driven Systems Engineering Using Six Sigma Techniques to Improve Software Defect Detection
Authors: Selby Paige C. , Selby Richard W. 
Published: November 2014

AbstractSystem developers and managers continually strive to identify, undertake, and realize improvements in system development methods. Measurement‐driven systems engineering guides the identification of improvement opportunities and enables the quantitative evaluation of progress and benefits. Six Sigma techniques provide a structured approach for using measurement‐driven methods to decrease the variances and shift the means of user‐defined metrics such as defect densities, development cycletimes, and resource expenditures. This research investigates the effectiveness of software defection detection using peer reviews across 12 system development phases on 14 large‐scale systems. This study analyzes 3418 defects from 731 peer reviews and benchmarks the defect injection and detection performance across the 12 system development phases. Six Sigma techniques including the define‐measure‐analyze‐improve‐control (DMAIC) method, root cause analysis, and control charts helped achieve inphase detection of 95 percent of defects and realize over 50 percent improvements in defect densities and closure cycletimes for certain peer review types.
5.4.3 Usability of formal verification on EFFBD models: Applying Petri nets to Systems Engineering issues
Authors: Seidner Charlotte , Lerat Jean‐Philippe , Roux Olivier H. 
Published: November 2014

AbstractAssessing the safety and the dependability of a system is one of the systems engineer's main targets. Formal tools, however powerful they may be to meet these issues, are often too cumbersome and complex to use. In this paper, we show that efficient formal methods can be used on high‐level models used in Systems Engineering to achieve some verification and validation processes. We give an overview of ongoing work on the translation of EFFBD‐like models to time Petri nets, using model transformation and meta‐modeling. We also present some encouraging results obtained with a prototype translation tool.
6.2.1 From Foresight to Insight: A Strategic Alignment Model for New Product Development
Authors: Lee Hei‐Kuang , Liu Chih‐Ming , Lee Meng‐Hua 
Published: November 2014

AbstractThe most important roles of strategic management concern about the right “attention” and the right “execution.” Based on this idea, the research question of this study is “How to align the strategy of a company to new product development?” This paper will focus on the longitudinal deployment of strategy and try to provide a solid methodology of strategic alignment to penetrate the multiple management levels of a company. Based on Ansoff's gap analysis model of strategic management, roadmapping techniques of management of technology, Work Breakdown Structure of project management, a Strategic Alignment Model for New Product Development (SAM‐NPD) is proposed in this study. A Six‐Echelon model, including industry, market, product, technology, intellectual property and cost structure analyses, is also developed for guiding the implementation of the SAM‐NPD model. Finally, a longitudinal case study of the successful application of this methodology in Taiwan is illustrated. Keywords: strategic management; strategic alignment model for new product development; SAM‐NPD; six‐echelon model.