bluuebunny/crossref_metadata_2025 huggingface dataset:
Different Effects of a By‐product From Olive Oil Extraction on S‐Metolachlor and Bentazone Soil Fate
Authors: Cañero Ana I. , Cox Lucía , Cabrera Alegría , Cornejo Juan
Published: November 2014

Bentazone and S‐metolachlor are herbicides widely used for the control of broad leaf weeds in crops such as corn and soybean. The effect of the addition to soils with different texture and organic matter content of an organic waste (OW) from oil olive production (alperujo) on different processes affecting behaviour of both herbicides was evaluated. Sorption of S‐metolachlor increased upon amendment. A six‐fold increase could be observed for Kd values on the sandy soil amended at 10% rate and a five‐fold increase on the soil with higher content on clay (48%) and same rate of OW (10%). The results revealed that although an increase in soil total pore volume was found upon amendment (from 210 to 266 mm3 g−1 in sandy (S) soil, from 215 to 251 in clayey (19% silt) (T) soil, and from 240 to 289 in clayey (50% silt) (E) soil), leaching of the herbicide S‐metolachlor was greatly reduced (from 61 to 3.5% in the S‐soil and from 37 to <1% in the clayey T‐soil) since its behaviour in soils is strongly affected by sorption processes. Bentazone leaching was only slightly delayed upon amendment. Half‐life of both herbicides also increased upon amendment. The greatest increase was observed with the higher rate of OW (10%) in the soils with higher content of clay (48% in T‐soil and 31% in E‐soil). A 17‐fold increase was observed for S‐metolachlor half‐life in T‐soil and a four‐fold increase for bentazone in E‐soil. Thus, the use of the by‐product from olive oil extraction can be a good strategy to reduce the off‐site movement of S‐metolachlor by increasing its soil sorption, and therefore the risk of water pollution can be diminished. However, the higher persistence of both herbicides in organic amended soils should be taken into account.
Health‐related quality of life in older adult survivors of selected cancers: Data from the SEER‐MHOS linkage
Authors: Kent Erin E. , Ambs Anita , Mitchell Sandra A. , Clauser Steven B. , Smith Ashley Wilder , Hays Ron D.
Published: November 2014

BACKGROUND

Research on health‐related quality of life (HRQOL) among older adult cancer survivors is mostly confined to breast cancer, prostate cancer, colorectal cancer, and lung cancer, which account for 63% of all prevalent cancers. Much less is known about HRQOL in the context of less common cancer sites.

METHODS

HRQOL was examined with the 36‐Item Short Form Health Survey, version 1, and the Veterans RAND 12‐Item Health Survey in patients with selected cancers (kidney cancer, bladder cancer, pancreatic cancer, upper gastrointestinal cancer, cancer of the oral cavity and pharynx, uterine cancer, cervical cancer, thyroid cancer, melanoma, chronic leukemia, non‐Hodgkin lymphoma, and multiple myeloma) and in individuals without cancer on the basis of data linked from the Surveillance, Epidemiology, and End Results cancer registry system and the Medicare Health Outcomes Survey. Scale scores, Physical Component Summary (PCS) and Mental Component Summary (MCS) scores, and a utility metric (Short Form 6D/Veterans RAND 6D), adjusted for sociodemographic characteristics and other chronic conditions, were calculated. A 3‐point difference in the scale scores and a 2‐point difference in the PCS and MCS scores were considered to be minimally important differences.

RESULTS

Data from 16,095 cancer survivors and 1,224,549 individuals without a history of cancer were included. The results indicated noteworthy deficits in physical health status. Mental health was comparable, although scores for the Role–Emotional and Social Functioning scales were worse for patients with most types of cancer versus those without cancer. Survivors of multiple myeloma and pancreatic malignancies reported the lowest scores, with their PCS/MCS scores less than those of individuals without cancer by 3 or more points.

CONCLUSIONS

HRQOL surveillance efforts revealed poor health outcomes among many older adults and specifically among survivors of multiple myeloma and pancreatic cancer. Cancer 2015;121:758–765. © 2014 American Cancer Society.
Multiphasic modelling of bone‐cement injection into vertebral cancellous bone
Authors: Bleiler Christian , Wagner Arndt , Stadelmann Vincent A. , Windolf Markus , Köstler Harald , Boger Andreas , Gueorguiev‐Rüegg Boyko , Ehlers Wolfgang , Röhrle Oliver
Published: November 2014

Percutaneous vertebroplasty represents a current procedure to effectively reinforce osteoporotic bone via the injection of bone cement. This contribution considers a continuum‐mechanically based modelling approach and simulation techniques to predict the cement distributions within a vertebra during injection. To do so, experimental investigations, imaging data and image processing techniques are combined and exploited to extract necessary data from high‐resolution μCT image data. The multiphasic model is based on the Theory of Porous Media, providing the theoretical basis to describe within one set of coupled equations the interaction of an elastically deformable solid skeleton, of liquid bone cement and the displacement of liquid bone marrow. The simulation results are validated against an experiment, in which bone cement was injected into a human vertebra under realistic conditions. The major advantage of this comprehensive modelling approach is the fact that one can not only predict the complex cement flow within an entire vertebra but is also capable of taking into account solid deformations in a fully coupled manner. The presented work is the first step towards the ultimate and future goal of extending this framework to a clinical tool allowing for pre‐operative cement distribution predictions by means of numerical simulations. Copyright © 2015 John Wiley & Sons, Ltd.
A Microwave Synthesis of Mesoporous NiCo2O4 Nanosheets as Electrode Materials for Lithium‐Ion Batteries and Supercapacitors
Authors: Mondal Anjon Kumar , Su Dawei , Chen Shuangqiang , Kretschmer Katja , Xie Xiuqiang , Ahn Hyo‐Jun , Wang Guoxiu
Published: November 2014

A facile microwave method was employed to synthesize NiCo2O4 nanosheets as electrode materials for lithium‐ion batteries and supercapacitors. The structure and morphology of the materials were characterized by X‐ray diffraction, field‐emission scanning electron microscopy, transmission electron microscopy and Brunauer–Emmett–Teller methods. Owing to the porous nanosheet structure, the NiCo2O4 electrodes exhibited a high reversible capacity of 891 mA h g−1 at a current density of 100 mA g−1, good rate capability and stable cycling performance. When used as electrode materials for supercapacitors, NiCo2O4 nanosheets demonstrated a specific capacitance of 400 F g−1 at a current density of 20 A g−1 and superior cycling stability over 5000 cycles. The excellent electrochemical performance could be ascribed to the thin porous structure of the nanosheets, which provides a high specific surface area to increase the electrode–electrolyte contact area and facilitate rapid ion transport.
Genetic dissection of Gata2 selective functions during specification of V2 interneurons in the developing spinal cord
Authors: Francius Cédric , Ravassard Philippe , Hidalgo‐Figueroa María , Mallet Jacques , Clotman Frédéric , Nardelli Jeannette
Published: November 2014

Motor activities are controlled by neural networks in the ventral spinal cord and consist in motor neurons and a set of distinct cardinal classes of spinal interneurons. These interneurons arise from distinct progenitor domains (p0–p3) delineated according to a transcriptional code. Neural progenitors of each domain express a unique combination of transcription factors (TFs) that largely contribute to determine the fate of four classes of interneurons (V0–V3) and motor neurons. In p2 domain, at least four subtypes of interneurons namely V2a, V2b, V2c, and Pax6+ V2 are generated. Although genetic and molecular mechanisms that specify V2a and V2b are dependent on complex interplay between several TFs including Nkx6.1, Irx3, Gata2, Foxn4, and Ascl1, and signaling pathways such as Notch and TGF‐β, the sequence order of the activation of these regulators and their respective contribution are not completely elucidated yet. Here, we provide evidence by loss‐ or gain‐of‐function experiments that Gata2 is necessary for the normal development of both V2a and V2b neurons. We demonstrate that Nkx6.1 and Dll4 positively regulate the activation of Gata2 and Foxn4 in p2 progenitors. Gata2 also participates in the maintenance of p2 domain by repressing motor neuron differentiation and exerting a feedback control on patterning genes. Finally, Gata2 promotes the selective activation of V2b program at the expense of V2a fate. Thus our results provide new insights on the hierarchy and complex interactions between regulators of V2 genetic program. © 2014 Wiley Periodicals, Inc. Develop Neurobiol 75: 721–737, 2015
Does pain severity guide selection to multimodal pain rehabilitation across gender?
Authors: Haukenes I. , Hensing G. , Stålnacke B.M. , Hammarström A.
Published: November 2014

Background

Studies have addressed the effect of multimodal pain rehabilitation (MMR), whereas criteria for selection are sparse. This study examines whether higher scores on musculoskeletal pain measures are associated with selection to MMR, and whether this differs across gender.

Method

A clinical population of 262 male and 589 female patients was recruited consecutively during 3 years, 2007–2010. The patients were referred from primary care to a pain rehabilitation clinic in Northern Sweden for assessment and selection to MMR. Register‐based data on self‐reported pain were linked to patients' records where outcome (MMR or not) was stated. We modelled odds ratios for selection to MMR by higher scores on validated pain measures (pain severity, interference with daily life, pain sites and localized pain vs. varying pain location). Covariates were age, educational level and multiple pain measures. Anxiety and depression (Hospital, Anxiety and Depression Scale) and working status were used in sensitivity tests.

Results

Higher scores of self‐reported pain were not associated with selection to MMR in multivariate models. Among women, higher scores on pain severity, pain sites and varying pain location (localized pain = reference) were negatively associated with selection to MMR. After adjustment for multiple pain measures, the negative odds ratio for varying location persisted (OR = 0.59, 95% CI = 0.39–0.89).

Conclusion

Higher scores on self‐reported pain did not guide selection to MMR and a negative trend was found among women. Studies of referral patterns and decision processes may contribute to a better understanding of the clinical practice that decides selection to MMR.
Watch What You Say: Job Applicants’ Justice Perceptions From Initial Organizational Correspondence
Authors: Walker H. Jack , Helmuth Catherine A. , Feild Hubert S. , Bauer Talya N.
Published: November 2014

Although it is a common practice for organizations to communicate with job seekers following application submission, little is known about how applicants react to this correspondence. Drawing from recruitment and organizational justice theories, we explore the possibility that specific correspondence content influences job seekers’ fairness perceptions. Data collected from 119 actual job applicants indicated that providing relevant information about the recruitment process (information adequacy) positively related to informational and interpersonal justice perceptions. However, delivering this information in an interpersonally sensitive manner (information sensitivity) had a stronger impact on interpersonal justice perceptions. Finally, post hoc analyses suggested that incorporating specific content delivered in initial job applicant correspondence could allow recruiting organizations to develop practical, cost‐effective strategies for enhancing job seekers’ fairness perceptions following their application submission. © 2014 Wiley Periodicals, Inc.
The Relationship of System Engineering to the Project Cycle
Authors: Forsberg Kevin , Mooz Harold
Published: November 2014

A new way of portraying the technical aspect of the project cycle clarifies the role and responsibility of system engineering to a project. This new three dimensional graphic illustrates the end‐to‐end involvement of system engineering in the project cycle, clarifies the relationship of system engineering and design engineering, and encourages the implementation of concurrent engineering.
7.1.3 PRINCIPLES OF COMMERCIAL SYSTEMS ENGINEERING
Authors: Honour Eric C.
Published: November 2014

This work presents basic principles currently used in commercial systems engineering. The principles were identified through correlative research into the practices of a wide variety of projects and companies. Sources include personal interviews, benchmark research into active companies and projects, and papers from the first four NCOSE symposia. The basic defining characteristic of commercial projects is considered to be amortized system development for production marketing. This characteristic results in customer focus, severe time and cost constraints, initially undefined requirements, marketability constraints, and management push for profitability.
4.2.3 Tools and Fools and Aphorisms
Authors: Crocker Don
Published: November 2014

It's time for a sanity check on the use of tools for Systems Engineering. This paper is based on the authors experiences on both sides of the SE tools equation. On one side is the tool builder, on another side is the tool user, and also on some side (often the outside) is the manager or owner that has to pay for the tool only to discover that the tool purchase was the proverbial tip of the iceberg. This common sense treatment of such weighty issues as: “Tools! We don't need no stinking tools”, “What comes first‐the method or the tool?”, “Can I afford this tool if you give it to me free?”,“ Will you show me your F‐Net if I show you my STD?”, and “Who does the Systems Engineering for Systems Engineering tools?” may actually have a point.
5.2.2 A CASE‐BASED REASONING APPROACH FOR THE ACCESS AND REUSE OF LESSONS LEARNED
Authors: Sary Charisse , Mackey William
Published: November 2014

This paper discusses the activities of an ongoing project to develop and demonstrate a prototype for capturing and reusing lessons learned at the Mission Operations and Data Systems Directorate (MO&DSD) of the National Aeronautics and Space Administration's (NASA's) Goddard Space Flight Center (GSFC). Primarily, systems and software engineering lessons learned are captured. Lessons learned describe difficulties and problems faced and ways to avoid them in the future. It is believed that lessons learned would be reused more often if others confronted with similar problems could locate them quickly and easily.

Therefore, the case‐based reasoning (CBR) approach, as an alternative to more conventional or other intelligent software methods, is being tried. A proof‐of‐concept prototype has been developed to evaluate the applicability of CBR to this problem. Because the system will be available to a diverse set of users, a process for incorporating lessons into the database has been defined.
4.1.1 TEAM STRUCTURES FOR SYSTEMS ENGINEERING IN AN IPT ENVIRONMENT
Authors: Sheard Sarah A. , Margolis M. Elliot
Published: November 2014

Integrated product teams (IPTs) are becoming popular structures for large projects. When a project proposes an IPT structure, either because the customer required it or because of contractor preferences, the specific organization must be defined. In this paper, the structures used by four IPT projects are outlined. These structures use Product Teams, Working Groups, System Teams, Architecture Teams, Team Leads Teams, and Management Teams to varying degrees. Overall lessons are presented along with lessons pertinent to each type of team. It is hoped that future projects will be able to use these case studies as a starting point for creating their own IPT structures.
5.1.1 THE ROLE OF THE PROJECT MANAGER IN SYSTEMS ENGINEERING
Authors: Roe Charles L.
Published: November 2014

Some engineers regard the project manager as an obstacle to overcome in the systems engineering process. Their view is that the manager's obsession with program costs, concerns about making timely delivery, and interpretations of customer nuances work against the process. This paper suggests that, far from being an impedance, the project manager can be a facilitator of a balanced systems engineering approach. At the same time, engineers must appreciate and understand the project manager's role and work with him to avoid adversarial relationships. This paper reviews the role of the project manager in the systems engineering process and explores ways that he and the project engineers can work together to ensure application of good systems engineering practices in the development of the product while giving attention to the project manager's concerns.
ZOPH – A Systemic Approach to the Modeling of Product Development Systems
Authors: Negele Herbert , Fricke Ernst , Igenbergs Eduard
Published: November 2014

In this paper, a comprehensive systems modeling approach is introduced, that is intended to embrace, structure, model, and interrelate information that is considered to be essential for product development systems. In order to achieve an integrated development of products, processes, organizations, and goals, the use of the ZOPH method is proposed. It applies one consistent modeling language to the entire development system (and its environment). Therefore, the resulting ZOPH‐Model supports an easy generation and handling of interfaces and interrelationships, which is crucial for the successful management of increasingly complex systems.
The Requirements Discovery Process
Authors: Bahill A. Terry , Dean Frank F.
Published: November 2014

Of course no two systems are the same and the process of discovering and documenting the requirements will be different for every system. However, the following steps should be appropriate for developing requirements in most systems: identify customers and stakeholders, understand the customer's needs, define and state the problem, write system requirements, review requirements with the customer, define performance and cost figures of merit, validate system requirements, describe the verification process, define technical performance measures, and mitigate risk.
What Do You Mean, You Can't Tell Me How Much of My Project Has Been Completed?
Authors: Kasser Joe
Published: November 2014

All the measurements made during the Systems Development Life Cycle do not provide an accurate answer to the question. This paper describes the development of a tool that can provide an answer to the question. In addition, when used with conventional budgetary data may be used to identify management and technical problems in their early stages.
4.1.3 System Architectures and Evolvability: Definitions and Perspective
Authors: Steiner Rick
Published: November 2014

The term “System Architecture” has been widely used in the systems engineering community for at least three decades. Even today, however, the use of this term often elicits more confusion than understanding! In particular, “System Architecture” has been used to describe, at various times, both the evolutionary system framework (Rechtin 91) (Rechtin/Maier 97), and the specific physical design or component interrelationship (Hatley 88). Even when it is agreed that the “System Architecture” represents a framework in which detailed design is performed, it is not generally agreed what aspects of behavior and structure should be captured in such a framework, how it should be represented, and how it relates to the specifics of system design. This paper examines current definitions of “systems architecture”, and proposes a taxonomy of terms to distinguish “single use” from “enduring” applications of architecture. Particular attention is paid to enduring architectures and their relationship to systems engineering.
2.3.4 A Systems Engineering Pattern Language
Authors: Barter Robert H.
Published: November 2014

Pattern languages were first developed in the 1970s as a way to tie together the wide range of design elements found in the field of civil architecture. In the early 1990's pattern languages began to appear in the field of software development. Patterns, pattern languages and pattern maps are an effective means of capturing large, complex bodies of knowledge. It is proposed that a Systems Engineering Pattern Language be developed for the purpose of capturing the Systems Engineering Body of Knowledge.
1.6.4 Requirements Completeness: A Deterministic Approach
Authors: Carson Ronald S.
Published: November 2014

A process for determining requirements completeness is developed. The method is comprised of three steps: (1) defining the problem to be solved by identifying and quantifying all system interfaces associated with the system development, operational, and maintenance concepts, (2) producing the requirements by analyzing the system interfaces to determine requirements under all conditions, and (3) verifying requirements completeness using the method of complementary antecedents (Carson 1995). The process allows one to demonstrate that requirements are complete for the associated mission (problem) statement(s).
6.2.3 Guiding Principals for Systems Engineering Tool Deployment
Authors: Sampson Mark
Published: November 2014

As Systems Engineers, we realize there is more to just about any problem then just putting a product in place. It's the same with systems engineering tools we use to solve our problems. We know that just putting tools in front of systems engineers (and consumers of systems engineering information) will not make the tools “stick“; environmental and cultural issues must be addressed for the tools to have a permanent place in how we do business.

Follows is an attempt to define issues and approaches for shifting development cultures so systems engineering tools can take root and make a real difference to the bottom line across whole enterprises–it focuses in on environmental issues needed for successful wide scale tool deployment–management and cultural roadblocks are discussed along with suggestions on dealing with the road blocks and getting systems engineering buy in to using the tools.
7.3.4 Optimising the Value of Systems Engineering
Authors: Honour Eric C.
Published: November 2014

Heuristic, intuitive wisdom holds that the practices of systems engineering have high value in the development of complex systems, yet no accepted methods exist to measure that value. In this theoretical paper, the quantitative value of systems engineering is proposed as measurable in several definitive and objective ways. The scope of systems engineering in this context is defined in the broadest terms, matching the perceived value held by those who hire systems engineers. Major components of systems engineering are described in two dimensions: task categories and development system attributes. Measurable value of these components is proposed using three product‐level measures: technical quality, risk avoidance, and problem discovery. Finally, a useable program is proposed that can lead to the information necessary to optimise the use of the systems engineering components.
3.5.2 Virtual Collaboration, e‐SE, and Team Sports Metaphors –Opportunities to Innovate, Integrate, and Invigorate
Authors: Pohlmann Lawrence D. , Myers Kenneth N. , Eilers Richard L.
Published: November 2014

Participation in virtual teams performing systems engineering‐related activities is a part of our collective destiny. While many of the functions of systems engineering (SE) are already difficult, they may be even more challenging in virtual team settings. As we transition to an electronic‐systems engineering (e‐SE), our success will depend in part on whether the environment, training, culture, infrastructure, and processes provide the appropriate support for various types of virtual collaboration that will occur within a project or enterprise.

This paper characterizes several models of collaboration and virtual collaboration – some of them based on team sports metaphors. We identify and describe different kinds of web‐based support that may be advantageous to these variations on the collaboration theme. In the process, we identify a variety of opportunities for innovation and integration – all with the aspiration of helping to invigorate SE‐related virtual team processes and activities.
1.6.2 Application of Computer‐Aided Systems Engineering to Develop Automated Guided Transit(AGT) System Architecture
Authors: Park Joong Yong , Lee Joong Yoon , Mok Jai Kyun , Park Young Won , Ahn Jang Keun , Lee Woo Dong
Published: November 2014

Automated Guided Transit (AGT) system is a complex and large system in which there are many subsystems, interfaces, functions and demanding performance requirements. Because many contractors participate in the development, it is necessary to apply methods of sharing common objectives and communicating effectively among all of the stakeholders. This paper shows not only the methodology and the results of computer‐aided systems engineering including requirement management, functional analysis and architecting the AGT system, but also an application of the tool to help manage a project by linking WBS (Work Breakdown Structure), work organization and PBS (Product Breakdown Structure). The application of computer‐aided tool, RDD‐100, provides the capability to model product design knowledge and decisions about important issues such as the architecting rationale of the top‐level system. The product design knowledge will be essential in integrating the follow‐on life‐cycle phase activities over the life of the AGT system. Additionally, when a new generation train system is required, the reuse of the database can increase the system design productivity and effectiveness significantly.
5.7.4 Support for Object‐Orientation in AP‐233
Authors: Pandikow Asmus , Törne Anders
Published: November 2014

This paper is motivated by the need to bridge the gap between the engineering methods used in software engineering and those used in systems engineering. Different alternatives attacking the problem are presented and evaluated. An implementation of one of the alternatives is described, namely the inclusion of the most important object‐oriented concepts from the OMG Unified Modeling Language (UML) into the working draft 5 of the ISO‐10303‐233 (AP‐233) systems engineering standard proposal. These concepts have also been integrated into the AP‐233 structures for version and configuration management and hence, allow now for the traceability of design elements between systems and software specifications. The extensions allow to include UML conformant tools in AP‐233 controlled system designs and on the other hand, the use of AP‐233 management capabilities for designing software.
7.7.1 Knowledge Management in Collaborative Product Development
Authors: Fagerström Björn , Olsson Lars‐Erik
Published: November 2014

An increasing amount of main suppliers are using sub‐suppliers to perform different tasks in the product development process. As a result, the knowledge needed for developing a new product will be distributed throughout many actors. Knowledge management is a comprehensive term for providing the right piece of knowledge to the right persons at the right time. This paper deals mainly with the question for how knowledge is managed in the collaborative product development between main and sub‐suppliers (system level). The result is based on a case study with one main supplier and ten of their sub‐suppliers, in which the main suppler develops, assembles, and delivers a whole, complex product to the customer. The study shows that the sub‐suppliers' knowledge and experiences are not fully utilized in the relationship with the main supplier. Some different ways of working are discussed in the paper's conclusions section, to improve the knowledge exchange between main and sub‐suppliers.
1.2.2 Better Systems Engineering with Dialogue
Authors: Backlund Göran , Sjunnesson Jan , Johansson Ingemar
Published: November 2014

Managing knowledge involves having the ability to establish intersubjectivity between a group of individuals. This paper describes two case studies where an advanced and highly structured dialogue is used as the key instrument for generating new ideas, and for establishing a common understanding of a new subject. Together with Prof. Bo Göranzon at the Department of Skill and Technology at Sweden's Royal Institute of Technology (KTH), Combitech Systems AB spent four years developing Dialogue Seminar method. After a period of thorough testing at Combitech Systems, the method has been in use at a number of other development organisations. The method is based on a view of knowledge developed by philosophers such as Aristotle, Descartes, Diderot and Wittgenstein, where tacit knowledge—or experience‐based knowledge—is central. The purpose of the concept is to give a wider understanding of knowledge, and the basic procedure involves training people to change perspective in order to stimulate new thinking. The three different cases clearly demonstrate that the Dialogue Seminar method can be successful in different situations, for example, gathering experience from a completed project, establishing a common language in a newly formed team or helping to specify a new product.
2.2.4 Operational Concepts and the Case for Use Cases: Unifying UML with Systems Engineering
Authors: Jorgensen Raymond
Published: November 2014

Operational Concepts have been used in varying degrees for many years by government acquisition agencies and contractors to help understand the operational nature of systems. Seldom, however, have the concepts been used at subcontractor levels or been encouraged by subsystem developers. Nor has there been much formality in the use and structure of the operational concept document (OCD). The typical content of the OCD remains highly textual with verbose description and little discipline in the thought process. The Unified Modelling Language (UML) has, however, introduced the notion of the Use Case, which, when examined as to purpose and focus, may provide an excellent basis for formalising the OCD content and providing a tool to help capture more effective operational scenarios at all levels of system composition. This paper explores the use of the UML Use Case as an essential part of the system Operational Concept.
4.2.2 Organizational Safety: A Systems Engineering Perspective
Authors: Jackson Scott
Published: November 2014

Numerous studies have shown that organizational factors are contributors to major accidents, in particular, catastrophes, such as Chernobyl and Challenger. Organizational safety, as distinguished from industrial and system safety, can be viewed in a systems engineering context. Case histories of these and other disasters are reviewed with a focus on the organizational aspects. First, the systems engineering concept of the development and support systems, that is, the engineering and support organizations, as categories of enabling systems dictates that these systems be considered concurrently with the operational system in establishing the total system requirements. Secondly, the systems engineering processes of requirements development and synthesis enable the creation of an organizational system which meets the total system requirements for safety. Finally, systems of verification are addressed, both externally mandated systems as well as internally conducted audits.
4.2.3 Systems Engineering Approach for Modeling An Organizational Structure
Authors: Rushton Gary , Zakarian Armen , Grigoryan Tigran
Published: November 2014

An organization is just another type of system. Why not use systems engineering techniques for modeling and development of the organizational structure. Within every organization there are required tasks/functions that interact with each other. Therefore, one may use system engineering techniques to define what the organization is required to do and then develop an organizational structure using some basic design principals, e.g., integration analysis technique to minimize coupling and maximize cohesion between various organizational tasks and functions. In this paper, we illustrate how systems engineering design principles can be used for modeling and analysis of an organization structure.
3.5.5 Integrated Cost / Schedule Risk Analysis
Authors: Hulett David T. , Campbell Bill
Published: November 2014

Project costs often exceed their estimates because those estimates do not take into consideration the actual duration of project activities. Cost risk will also be underestimated if it does not take into consideration schedule risk. This paper presents a method of incorporating the uncertainty in activities' durations into the assessment of cost risk. In this method, a Monte Carlo simulation of the schedule provides uncertainty in time. Incorporating the schedule risk results into the cost risk model provides the linkage between schedule and cost risk. Then equivalence must be established between the schedule and network concepts. Uncertainty in costs is then represented by uncertainty in “independent costs” (costs that do not depend on time) and “variable costs” (costs that depend on uncertain time and cost per unit time or “burn rate” and rate of labor compensation.) Simulation of the cost model combines the results from the schedule risk analysis with the uncertainty in the cost assumptions. The results include the probability distribution of total project costs and sensitivity of that distribution to the different inputs. Issues are discussed and simplified examples are provided.
5.5.5 Systems Engineering with ICDM – A Case Study
Authors: Herscovitz Jacob , Hari Amihud
Published: November 2014

This paper presents and demonstrates the design of a new system using the ICDM method.

ICDM is an Integrated, Customer Driven, Conceptual Design Method that encompasses the entire process of conceptual design, starting from customer needs up to the selection of the best solution to that need.

In an engineering design process, the most critical phase is the initial conceptualization of the needed system or product, where about 75% of its life cycle cost is committed (Blanchard 1978). Therefore, using efficient methodologies and practices during this phase is essential to the whole effort success (Pahl 1984).

ICDM, demonstrated in this paper, is a flexible 10 step method, tailorable to multifaceted project needs and organization's requirements.

The case study describes the stages of a system definition and conceptual design of a Personal Identification of Friend or Foe system ‐ PIFF. The problem behind this need is defined as the difficulty of friend or foe identification in terror fighting or infantry arena.

As a result, the case study showed the ability of ICDM to enable quick and efficient team decisions upon the customer needs and produced an optimal conceptual design that scored the best in terms of Customer Satisfaction Rating (CSR).
2.6.4 An Initial Application of AP‐233
Authors: Scott William , Cook Stephen C , Harris David , Smith John , Johnson Julian
Published: November 2014

The System Engineering Design Methodologies (SEDM) project is concerned with potential avenues to exploit the AP‐233 system engineering data exchange standard. The project is a joint venture between the System Engineering and Evaluation Centre of the University of South Australia and BAE SYSTEMS Australia. The work described in this paper covers the design and implementation of an import interface from the AP‐233 data model to DOORS. The project showed that AP‐233 is an effective medium for tool independent transfer of systems engineering information.
5.6.2 Decision Making in Modular Product Platform Development
Authors: Ofer Christian M. , Otto Kevin N. , Whitcomb Clifford , Igenbergs Eduard , Schulz Armin P.
Published: November 2014

In order to achieve larger market share and address individual customer needs, firms are challenged to manage the seemingly contradictory existence of internally low variety and a maximum external variety. One very powerful approach is to use modular product architectures (PA). This permits one to establish product families based on platforms.

Using platforms is a common strategy in diverse industries. For development of platform architectures, there are almost infinite possible configurations. There is a need for a framework for evaluation and selection of possible concepts. By evaluating design concepts one is faced with decision‐making. To do this, one must make choices over a distinct evaluation method and effective metrics. In this choice, the quality of information is the limiting and determining factor, it is the differentiating characteristic among methods. To show this, diverse methods will be presented and their characteristics and benefits will be discussed.
6.6.3 Safety Systems Intervention Plan for Yellowstone National Park
Authors: Plowman Catherine , Alessi Sam
Published: November 2014

Managers of Yellowstone National Park are interested in improving both the safety performance and the systems design and project management capability of the Park's personnel. The objective of our research was to address this need by constructing a safety enhanced Capability Maturity Model that will simultaneously assess systems design and safety. This approach advances the integration safety into business decisions and identification of ‘leading’ indicators of safety performance. We modified the EIA 731 Capability Maturity Model to include a focus on safety management systems. This model was used to assess the safety culture at Yellowstone National Park (YNP) in the spring of 2001. Using the standard assessment approach, results from the safety‐augmented survey were used to target specific areas of investigation. Results from the interviews and focus groups led to a collection of information and potential improvement opportunities that were subsequently used to develop a five‐year safety system intervention plan for the Park. This paper deals with the intervention plan development that occurred after the standard CMM assessment activities were completed.
3.1.1 COSYSMO: A Constructive Systems Engineering Cost Model Coming of Age
Authors: Valerdi Ricardo , Boehm Barry W. , Reifer Donald J.
Published: November 2014

Building on the synergy between Systems Engineering and Software Engineering, the Center for Software Engineering (CSE) at the University of Southern California (USC), is in the process of developing a parametric model to estimate Systems Engineering costs. The goal of this model, called COSYSMO (Constructive Systems Engineering Cost Model), is to more accurately estimate the time and effort associated with performing the system engineering tasks defined by ISO/IEC 15288.

This paper outlines the work accomplished thus far by USC, in collaboration with its Corporate Affiliates and the INCOSE Measurement Working Group, to develop the initial version of COSYSMO. This paper describes the development of the model, explains both its size and cost drivers, and outlines future steps that need to be taken to guarantee COSYSMO's successful adoption by the Systems Engineering community.
1.2.1 The Role of Systems Engineering in Combating Terrorism
Authors: Mackey William F. , Crisp Harry , Cropley David , LongPresident James , Mayian Stephen , Raza Shabaz
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. A charter for the INCOSE Systems Engineering Initiatives Technical Committee (SEITC) and an Anti‐Terrorism International Working Group (ATIWG) were established in October 2001. INCOSE ATIWG members are applying the multidisciplinary approach of systems engineering to understanding all facets of terrorism. The ATIWG convened a special panel at INCOSE 2002 in Las Vegas, NV, using the same name as the title of this paper. Rather than lose the information conveyed during that session, many of the panelists agreed to join their efforts to coauthor this paper and document much of what was said.

This paper's thesis is that the multidisciplinary approach of systems engineering is useful in evaluating terrorist threats, identifying potential target vulnerabilities, and reducing or eradicating international terrorism.
4.2.2 Trust Lubricates the Organizational System: The System Dynamics Approach
Authors: Kurstedt Harold , Tech Virginia
Published: November 2014

To be systems thinkers, we must easily and comfortably integrate human subsystems into complex systems. We can diagram dyadic and triadic human relationships to better analyze, design, and implement complex systems containing human subsystems. Trust and distrust are separate but linked state variables. Trust is fragile and distrust is robust because they fit differently into the system structure of the dyadic relationship. Key considerations for trust in the organization include risk and experience. From a systems perspective, we must design into the organization and our dyadic relationships the structure needed to increase trusting and trustworthy behaviors and to reduce opportunistic behaviors. These behaviors are bound together in feedback loops that define the structure of our relationships. We determine that structure using system dynamics tools. These tools provide the needed understanding of trust to identify steps for changing the relationship or organizational system structure that leads to changed behavior.
4.2.3 Mentoring Technical and Professional People in Today's ‘Demented’ Environment
Authors: Haskins Bill R.
Published: November 2014

Today, organizations increasingly place value on individuals who not only can adapt, but also can learn quickly—indeed, who can ‘learn how to learn‘. The recognition of mentoring as an important transfer mechanism for knowledge within organizations has grown significantly in the past couple of decades. Mentoring has become a prime tool for individual survival and professional development. As a professional development strategy, mentoring is a process whereby a more experienced employee (mentor) serves as a role model, provides support, direction, and feedback to the less experienced employee (mentee) regarding career plans and interpersonal development, helps develop specific skills and knowledge that will enhance the mentee's professional and personal growth; and increases the visibility of the mentee to decision makers in the organization who may influence career opportunities. Today, mentoring is being used by many organizations to seek a competitive advantage in a global marketplace.
6.2.4 Evolutionary Project Management (Evo): How to Manage Project Benefits and Costs
Authors: Gilb Tom
Published: November 2014

Evolutionary project management is one of many non‐waterfall (Iterative, Incremental, Spiral, Evolutionary Acquisition) project management methods used in industry today. The variation described here is the current view of the author, who has applied Evo since 1960 on real projects, both personally and through clients and students. The central distinctive characteristic of this version of Evo is its focus on quantified specification and tracking of multiple performance and cost requirements during early and frequent Evo steps of result delivery to stakeholders.
3.3.2 Object Oriented Architecture for Collaborative Web‐Centric Configuration Management of Military Rotorcraft
Authors: Stanilka Stanley P. , Dagli Cihan H.
Published: November 2014

Rotorcraft configuration management is a process, which documents performance, functionality and physical attributes of a military helicopter. This process applies technical and administrative surveillance against a certified design baseline and controls change incorporation throughout the life cycle of the aircraft. The United States Department of Defense (DOD) provides guidance on configuration management through military handbook MIL‐HDBK‐61A and EIA Standard 649. The data governed by configuration management processes can be viewed as a colossal mixture of design drawings, technical service manuals, change documents, material & process specifications, test plans, maintenance & repair records and many other forms of accountability. This paper describes how a collaborative network can be modeled around this configuration management requirement. It will partition and decompose rotorcraft‐engineering data into independent configuration management items and explain how Object Oriented (OO) design philosophies and Unified Modeling Language (UML) methods can maximize an architect's ability to integrate disparate data into a collaborative network.
6.3.3 Cost Effective Systems Engineering for Companies that Build‐on‐Speculation
Authors: Lentz V. A. , Lerner Bruce
Published: November 2014

The System Engineering community has long been looking for a Systems Engineering solution for ‘Commercial’ Systems Engineering. Our recent initiatives in the cost effective practice of System Engineering for one commercial enterprise leads us to believe that the differentiation between the two types of System Engineering might be in the business strategy. Does the company build‐to‐specification (BTS) or build‐on‐speculation (BOS)? That is the question. The answer is still evolving. However, the insight from more than 5 years of trying to apply the Mil‐Aero SE Process to engineering for a commercial enterprise that enters new product development on speculation, leads us to believe there are indeed differences. Continuing to focus on making the case for the value of Mil‐Aero style system engineering to the ‘commercial’ enterprise doesn't get us to the cost effective solution build‐on‐speculation businesses need. We offer some thoughts about the differences, and the allowances that need to be made. We provide some directions for organizing the SE methods to cost effectively provide the advantages of Systems Engineering to an organization that builds‐on‐speculation. Note: We borrowed the term ‘Build on Speculation’ from the construction industry. We are using it to identify a company that brings new product to market without a specific buyer or contract.
4.4.2 The Mission Analysis Discipline: Bringing focus to the fuzziness about Attaining Good Architectures
Authors: Shupp Jeffrey K.
Published: November 2014

The systems and software engineering communities have experienced a veritable explosion of activity surrounding architectures and their role in developing complex systems. This activity has moved forward on two fundamental fronts: the ability to document an architecture, and the ability to evaluate one. Both of these themes have as their foundation the need for well articulated requirements. The architecture is the highest level design of a system, and as such is a response to the requirements. This paper addresses a third, largely overlooked, segment of the early systems development cycle called Mission Analysis, and the focus on the solution trade space through the generation of Technical Business Strategies. Making this topic a recognized discipline in its own right will help to focus early system development work in a way that hopefully makes the overall process less reliant on super system architects to produce good solutions for the long run.