Legal Challenges and Market Rewards to the Use and Acceptance of Remote Sensing and Digital Information as Evidence

Bakgrund I den nutida forskningen är det essentiellt att företag tar hänsyn till medarbetarnas motivation så att de gynnas av det arbetssätt som tillämpas. En arbetsmetod som blivit allt vanligare är konceptet Lean som ursprungligen kommer från den japanska bilindustrin. Lean har idag utvecklats till ett allmängiltigt koncept som tillämpas i flertalet branscher världen över. Trots att konceptet innebär flertalet positiva aspekter har det fått utstå stark kritik när det kommer till de mänskliga aspekterna och forskare har ställt sig frågan om Lean är "Mean". Kritiken härleds främst till medarbetares arbetsmiljö i form av stress och brist på variation, självbestämmande, hälsa och välmående. Få empiriska studier har däremot genomförts som undersöker konsekvenserna som Lean får på medarbetares upplevda motivation. Syfte Vårt syfte är att undersöka och öka förståelsen för medarbetares upplevelser av motivationen i företag som tillämpar Lean. Vidare har studien för avsikt att utreda om det föreligger en paradox mellan Lean och vad som motiverar medarbetare på en arbetsplats. Metod Studien har utgått från en kvalitativ metod via intervjuer. För att göra en djupare undersökning och analysera hur vårt fenomen, motivation, upplevs i en kontext med Lean tillämpade vi Små-N-studier. Vi har även haft en iterativ forskningsansats som förenat den deduktiva och induktiva ansatsen där studien pendlat mellan teorier och empiriska observationer fram tills det slutgiltiga resultatet. Slutsatser Utefter medarbetarnas upplevelser har vi identifierat att det inte föreligger någon paradox mellan Lean och motivation eftersom övervägande antal medarbetare upplevde att de är motiverade även om företaget tillämpar Lean. Dock har studien kunnat urskilja både stödjande och motverkande faktorer när det kommer till medarbetarnas upplevda arbetsförhållanden som i sin tur inverkar på motivationen. De motverkande faktorerna menar vi främst beror på att arbetsförhållandena i somliga fall innehåller höga prestationskrav, målstyrning samt standardiseringar. Vidare upplevs motivationen överlag som mer positiv när företagen använder en mjukare form av Lean där samtliga medlemmars intressen beaktas.Background In modern research, it is essential that companies consider employees’ motivation so that they benefit from the applied practices. A working method that has become increasingly common is the concept Lean, which has its origin in the Japanese automotive industry. Today, Lean has evolved into a universal concept that is applied in many industries worldwide. Although the concept involves numerous positive aspects it has endured strong criticism when it comes to the human aspects and researchers have raised the question if Lean is "Mean". Criticism is derived primarily to employees’ working conditions in terms of stress and lack, variation, autonomy, health and wellbeing. However, few empirical studies have been carried out that examines the impact that Lean has on employees’ experienced motivation. Aim The aim is to increase the understanding of employees’ experienced motivation in companies that practice Lean. Further on the study has the intention to investigate if there is a paradox between Lean and what motivates employees on work. Methodology The study has been conducted through a qualitative method by interviews and to be able to do a deeper examination and analyze how our phenomenon, motivation, is experienced in a Lean context we applied small-N-studies. Our strategy has been iterative, combining both a deductive and inductive approach, where the study has varied between theories and empirical observations until the final result. Conclusions We have identified that there is no paradox between Lean and motivation since the majority of employees’ experienced that they are motivated even though the company practice Lean. Nevertheless the study shows that there are both supportive and counteractive factors when it comes to the employees’ experienced working conditions. The counteractive factors consists foremost of high performance standards, goal steering and standardizations, and have in some cases a negative influence on the working conditions. Furthermore the experienced motivation is more positive overall when the companies use a softer form of Lean where all the members’ interests are taken into account

Lessons Learned and Next Steps in Energy Efficiency Measurement and Attribution: Energy Savings, Net to Gross, Non-Energy Benefits, and Persistence of Energy Efficiency Behavior

This white paper examines four topics addressing evaluation, measurement, and attribution of direct and indirect effects to energy efficiency and behavioral programs: Estimates of program savings (gross); Net savings derivation through free ridership / net to gross analyses; Indirect non-energy benefits / impacts (e.g., comfort, convenience, emissions, jobs); and, Persistence of savings

Water Funds: Conserving Green Infrastructure

This manual is an effort by TNC to compile, analyze and synthesize its own experience, together with that of the water funds already in existence and under creation, in order to provide operational guidelines to people and organizations interested in establishing a water fund or similar mechanism. Each location has different ecological, social, economic, legal and institutional features and, therefore, each water fund will have its own characteristics, phases and projections. This manual presents general guidelines and logical steps that must be followed to boost the opportunities and benefits of a water fund and to minimize possible obstacles for its creation. It is not intended to be an in-depth look at every aspect of water funds. Although TNC participates in several other initiatives and similar approaches to watershed management, such as the water producers program in Brazil, this document will not address those initiatives and will only focus on the water funds scheme, placing greater emphasis on experiences in the Andean region

An Assessment of PIER Electric Grid Research 2003-2014 White Paper

This white paper describes the circumstances in California around the turn of the 21st century that led the California Energy Commission (CEC) to direct additional Public Interest Energy Research funds to address critical electric grid issues, especially those arising from integrating high penetrations of variable renewable generation with the electric grid. It contains an assessment of the beneficial science and technology advances of the resultant portfolio of electric grid research projects administered under the direction of the CEC by a competitively selected contractor, the University of California’s California Institute for Energy and the Environment, from 2003-2014

Traceability of Requirements and Software Architecture for Change Management

At the present day, software systems get more and more complex. The requirements of software systems change continuously and new requirements emerge frequently. New and/or modified requirements are integrated with the existing ones, and adaptations to the architecture and source code of the system are made. The process of integration of the new/modified requirements and adaptations to the software system is called change management. The size and complexity of software systems make change management costly and time consuming. To reduce the cost of changes, it is important to apply change management as early as possible in the software development cycle. Requirements traceability is considered crucial in change management for establishing and maintaining consistency between software development artifacts. It is the ability to link requirements back to stakeholders’ rationales and forward to corresponding design artifacts, code, and test cases. When changes for the requirements of the software system are proposed, the impact of these changes on other requirements, design elements and source code should be traced in order to determine parts of the software system to be changed. Determining the impact of changes on the parts of development artifacts is called change impact analysis. Change impact analysis is applicable to many development artifacts like requirements documents, detailed design, source code and test cases. Our focus is change impact analysis in requirements and software architecture. The need for change impact analysis is observed in both requirements and software architecture. When a change is introduced to a requirement, the requirements engineer needs to find out if any other requirement related to the changed requirement is impacted. After determining the impacted requirements, the software architect needs to identify the impacted architectural elements by tracing the changed requirements to software architecture. It is hard, expensive and error prone to manually trace impacted requirements and architectural elements from the changed requirements. There are tools and approaches that automate change impact analysis like IBM Rational RequisitePro and DOORS. In most of these tools, traces are just simple relations and their semantics is not considered. Due to the lack of semantics of traces in these tools, all requirements and architectural elements directly or indirectly traced from the changed requirement are candidate impacted. The requirements engineer has to inspect all these candidate impacted requirements and architectural elements to identify changes if there are any. In this thesis we address the following problems which arise in performing change impact analysis for requirements and software architecture. Explosion of impacts in requirements after a change in requirements. In practice, requirements documents are often textual artifacts with implicit structure. Most of the relations among requirements are not given explicitly. There is a lack of precise definition of relations among requirements in most tools and approaches. Due to the lack of semantics of requirements relations, change impact analysis may produce high number of false positive and false negative impacted requirements. A requirements engineer may have to analyze all requirements in the requirements document for a single change. This may result in neglecting the actual impact of a change. Manual, expensive and error prone trace establishment. Considerable research has been devoted to relating requirements and design artifacts with source code. Less attention has been paid to relating Requirements (R) with Architecture (A) by using well-defined semantics of traces. Designing architecture based on requirements is a problem solving process that relies on human experience and creativity, and is mainly manual. The software architect may need to manually assign traces between R&A. Manual trace assignment is time-consuming, expensive and error prone. The assigned traces might be incomplete and invalid. Explosion of impacts in software architecture after a change in requirements. Due to the lack of semantics of traces between R&A, change impact analysis may produce high number of false positive and false negative impacted architectural elements. A software architect may have to analyze all architectural elements in the architecture for a single requirements change. In this thesis we propose an approach that reduces the explosion of impacts in R&A. The approach employs semantic information of traces and is supported by tools. We consider that every relation between software development artifacts or between elements in these artifacts can play the role of a trace for a certain traceability purpose like change impact analysis. We choose Model Driven Engineering (MDE) as a solution platform for our approach. MDE provides a uniform treatment of software artifacts (e.g. requirements documents, software design and test documents) as models. It also enables using different formalisms to reason about development artifacts described as models. To give an explicit structure to requirements documents and treat requirements, architecture and traces in a uniform way, we use metamodels and models with formally defined semantics. The thesis provides the following contributions: A modeling language for definition of requirements models with formal semantics. The language is defined according to the MDE principles by defining a metamodel. It is based on a survey about the most commonly found requirements types and relation types. With this language, the requirements engineer can explicitly specify the requirements and the relations among them. The semantics of these entities is given in First Order Logic (FOL) and allows two activities. First, new relations among requirements can be inferred from the initial set of relations. Second, requirements models can be automatically checked for consistency of the relations. Tool for Requirements Inferencing and Consistency Checking (TRIC) is developed to support both activities. The defined semantics is used in a technique for change impact analysis in requirements models. A change impact analysis technique for requirements using semantics of requirements relations and requirements change types. The technique aims at solving the problem of explosion of impacts in requirements when semantics of requirements relations is missing. The technique uses formal semantics of requirements relations and requirements change types. A classification of requirements changes based on the structure of a textual requirement is given and formalized. The semantics of requirements change types is based on FOL. We support three activities for impact analysis. First, the requirements engineer proposes changes according to the change classification before implementing the actual changes. Second, the requirements engineer indentifies the propagation of the changes to related requirements. The change alternatives in the propagation are determined based on the semantics of change types and requirements relations. Third, possible contradicting changes are identified. We extend TRIC with a support for these activities. The tool automatically determines the change propagation paths, checks the consistency of the changes, and suggests alternatives for implementing the change. A technique that provides trace establishment between R&A by using architecture verification and semantics of traces. It is hard, expensive and error prone to manually establish traces between R&A. We present an approach that provides trace establishment by using architecture verification together with semantics of requirements relations and traces. We use a trace metamodel with commonly used trace types. The semantics of traces is formalized in FOL. Software architectures are expressed in the Architecture Analysis and Design Language (AADL). AADL is provided with a formal semantics expressed in Maude. The Maude tool set allows simulation and verification of architectures. The first way to establish traces is to use architecture verification techniques. A given requirement is reformulated as a property in terms of the architecture. The architecture is executed and a state space is produced. This execution simulates the behavior of the system on the architectural level. The property derived from the requirement is checked by the Maude model checker. Traces are generated between the requirement and the architectural components used in the verification of the property. The second way to establish traces is to use the requirements relations together with the semantics of traces. Requirements relations are reflected in the connections among the traced architectural elements based on the semantics of traces. Therefore, new traces are inferred from existing traces by using requirements relations. We use semantics of requirements relations and traces to both generate/validate traces and generate/validate requirements relations. There is a tool support for our approach. The tool provides the following: (1) generation/validation of traces by using requirements relations and/or verification of architecture, (2) generation/validation of requirements relations by using traces. A change impact analysis technique for software architecture using architecture verification and semantics of traces between R&A. The software architect needs to identify the impacted architectural elements after requirements change. We present a change impact analysis technique for software architecture using architecture verification and semantics of traces. The technique is semi-automatic and requires participation of the software architect. Our technique has two parts. The first part is to identify the architectural elements that implement the system properties to which proposed requirements changes are introduced. By having the formal semantics of requirements relations and traces, we identify which parts of software architecture are impacted by a proposed change in requirements. We have extended TRIC for determining candidate impacted architectural elements. The second part of our technique is to propose possible changes for software architecture when the software architecture does not satisfy the new and/or changed requirements. The technique is based on architecture verification. The output of verification is a counter example if the requirements are not satisfied. The counter example is used with a classification of architectural changes in order to propose changes in the software architecture. These changes produce a new version of the architecture that possibly satisfies the new or the changed requirements

Flight deck engine advisor

The focus of this project is on alerting pilots to impending events in such a way as to provide the additional time required for the crew to make critical decisions concerning non-normal operations. The project addresses pilots' need for support in diagnosis and trend monitoring of faults as they affect decisions that must be made within the context of the current flight. Monitoring and diagnostic modules developed under the NASA Faultfinder program were restructured and enhanced using input data from an engine model and real engine fault data. Fault scenarios were prepared to support knowledge base development activities on the MONITAUR and DRAPhyS modules of Faultfinder. An analysis of the information requirements for fault management was included in each scenario. A conceptual framework was developed for systematic evaluation of the impact of context variables on pilot action alternatives as a function of event/fault combinations

Spatial Dynamic Modeling and Urban Land Use Transformation:

Assessing the economic impacts of urban land use transformation has become complex and acrimonious. Although community planners are beginning to comprehend the economic trade-offs inherent in transforming the urban fringe, they find it increasingly difficult to analyze and assess the trade-offs expediently and in ways that can influence local decisionmaking. New and sophisticated spatial modeling techniques are now being applied to urban systems that can quickly assess the probable spatial outcomes of given communal policies. Applying an economic impact assessment to the probable spatial patterns can provide to planners the tools needed to quickly assess scenarios for policy formation that will ultimately help inform decision makers. This paper focuses on the theoretical underpinnings and practical application of an economic impact analysis submodel developed within the Land use Evolution and Impact Assessment Modeling (LEAM) environment. The conceptual framework of LEAM is described, followed by an application of the model to the assessment of the cost of urban sprawl in Kane County, Illinois. The results show the effectiveness of spatially explicit modeling from a theoretical and a practical point of view. The agent-based approach of spatial dynamic modeling with a high spatial resolution allows for discerning the macro-level implications of micro-level behaviors. These phenomena are highlighted in the economic submodel in the discussion of the implications of land use change decisions on individual and communal costs; low-density development patterns favoring individual behaviors at the expense of the broader community.

Environmental hazard identification, assessment and control for a sustainable maritime transportation system

A demand exists to contribute towards the widening awareness of the need for sustainable maritime development and for coordinated maritime policies worldwide. Maritime shipping is considered the most eco-efficient mean of transportation and yet, is responsible for negative environmental impacts. This dissertation focuses on developing data-driven decision support tools to evaluate the sustainable performance of MTS by focusing on the elements of the MTS that place stress on the environment. The first research contribution is a System Dynamics simulation model that examines the MTS resiliency after an extreme event and determines the sequence needed to restore the ocean-going port to its pre-event state. The second is a Decision-Making in Complex Environments (DMCE) tool developed by integrating fuzzy logic with a combination of Analytic Hierarchy Process (FAHP) and Techniques for Order Performance by Similarity to Ideal Solution (FTOPSIS) to quantify and rank preferred environmental impact indicators within MTS. The third is an extension to this DMCE tool by the integration of a Monte Carlo simulation in order to have a better understanding of the risks associated with the resulting rankings of those preferred environmental indicators. And, the fourth is a predictive model for the monitoring of vegetation changes near-port areas and to understand the long-term impacts that maritime activity has towards the environment. The developed models address the impacts MTS has on the natural environment and help achieve environmental sustainability of this complex system by evaluating the sustainability performance of the MTS --Abstract, page iv

ABSTRACTS, PAPERS PRESENTED, ANNUAL MEETING, SAEA, LITTLE ROCK, ARKANSAS, FEBRUARY 1990

Teaching/Communication/Extension/Profession,