6 research outputs found

    Devising magnetism : concepts and investigative practices

    Get PDF

    Arctic Frontiers 2016

    Get PDF

    Arctic Human Development Report : Regional Processes and Global Linkages

    Get PDF
    The goals of the second volume of the AHDR – Arctic Human Development Report: Regional Processes and Global Linkages – are to provide an update to the first AHDR (2004) in terms of an assessment of the state of Arctic human development; to highlight the major trends and changes unfolding related to the various issues and thematic areas of human development in the Arctic over the past decade; and, based on this assessment, to identify policy relevant conclusions and key gaps in knowledge, new and emerging Arctic success stories. The production of AHDR-II on the tenth anniversary of the first AHDR makes it possible to move beyond the baseline assessment to make valuable comparisons and contrasts across a decade of persistent and rapid change in the North. It addresses critical issues and emerging challenges in Arctic living conditions, quality of life in the North, global change impacts and adaptation, and Indigenous livelihoods. The assessment contributes to our understanding of the interplay and consequences of physical and social change processes affecting Arctic residents’ quality of life, at both the regional and global scales. It shows that the Arctic is not a homogenous region. Impacts of globalization and environmental change differ within and between regions, between Indigenous and non-Indigenous northerners, between genders and along other axes

    Addressing Common Crosscutting Problems with Arcum

    No full text
    Crosscutting is an inherent part of software development and can typically be managed through modularization: A module’s stable properties are defined in an interface while its likely-to-change properties are encapsulated within the module [19]. The crosscutting of the stable properties, such as class and method names, can be mitigated with automated refactoring tools that allow, for example, the interface’s elements to be renamed [9, 18]. However, often the crosscutting from design idioms (such as design patterns and coding styles) are so specific to the program’s domain that their crosscutting would not likely have been anticipated by the developers of an automated refactoring system. The Arcum plug-in for Eclipse enables programmers to describe the implementation of a crosscutting design idiom as a set of syntactic patterns and semantic constraints. Arcum can process declarations of related implementations and infer the refactoring steps necessary to transform a program from using one implementation to its alternatives. As a result, automating refactoring for domainspecific crosscutting design idioms can be easy and practical. This paper presents a case study of how Arcum was used to mitigate four classic software engineering problems that are exacerbated by crosscutting: library migration, debugging, programmer-defined semantic checking, and architectural enforcement
    corecore