bluuebunny/crossref_metadata_2025_split huggingface dataset:
Soil Strength Degradation Due to SCRs Vertical Motion at Touchdown Zone
Authors: Hu H.J.E. , Leung C.F. , Chow Y.K. , Palmer A.C. , Chan H.C.N. 
Published: February 2015

Steel catenary risers (SCR) connect seabed pipelines and flow lines to floating structures used for oil and gas production in deep waters. Waves and currents induce motions of the structure and the risers. The repeated motions of the risers at the touchdown zone in turn induce loads on the seabed soil and might eventually cause fatigue damage to the risers. The analysis of riser fatigue damage is heavily dependent on the soil model. Soil behaviour at touchdown zone such as soil remolding, stiffness degradation and deformation of the seabed at the touchdown zone further complicate the accurate assessment of riser fatigue damage, which is currently not appropriately quantified in existing design methods.
This paper presents centrifuge model tests simulating the repeated vertical movement of a length of riser on clay seabed. During the tests, the pipe was subjected to cyclic motion of constant vertical displacement amplitude. Particle Image Velocimetry (PIV) analyses are performed to investigate the soil failure mechanism during the penetration and uplift of the length of riser, including cavity formation, transition from shallow and deep failure mechanism, and evolution of failure mechanism as the load cycle increases.
The test results show a significant progressive degradation of penetration and uplift resistances upon the onset of riser cycling which is due to the remoulding of the soil. Furthermore, formation of weakened zone confines the development of failure mechanism as the number of load cycles increases. These results could provide further insight into the touchdown zone modelling as SCR present as an economical solution as oil exploration and production carried out in greater water depth.
Coupling Between Lateral and Torsional Vibrations: A New Insight into PDC Bit Drilling Inefficiencies
Authors: Makkar Navish , Sullivan Eric , Habernal Jason 
Published: February 2015

Drilling performance and durability of polycrystalline diamond compact (PDC) bits can be degraded by the vibrations associated with drilling. In particular, two types of vibrations are of interest, torsional oscillation and backward whirl. Torsional oscillation ("stick / slip") is characterized by fluctuations in bit angular velocity. In extreme cases, the angular velocity can fall to zero or even reverse (CCW) direction, and reverse rotation is known to be detrimental to laminated cutters. In addition, backward whirl (lateral vibration), which refers to the counter-clockwise orbiting of bit center-of-rotation around the hole centerline, causes inefficient off-normal cutter movement and can lead to excessive cutter wear and fracture.
In the current paper, the authors examine torsional oscillation data representing field and laboratory drilling events, and provide an alternative explanation for the observed reductions in drilling efficiency and durability. More specifically, the authors suggest that the likelihood of backward whirl with variations in angular velocity. At first, the hypothesis is evaluated by dynamic simulations and then validated through a series of torsional oscillation tests performed in the laboratory.
To further substantiate the effect, the authors demonstrate how mechanical specific energy MSE and temperature rises when loading on PDC cutters varies from normal. This information is easily correlated with the dull conditions and damage to PDC cutters.
The insight that stick / slip may include a backward whirl component can be used to guide the optimization of drilling parameters. This can be achieved in the field, either during operations if real-time in-bit sensing data are available or for offset well planning purposes if data are available in memory mode only. In either case, the likelihood of achieving performance objectives such as completing an interval (minimizing early terminations) and achieving target penetration rates are significantly improved.
Coiled Tubing Downhole Communication System Helps Solve Complex Intervention Challenges
Authors: Acorda Edgar Paul , Sundramurthy Deenadayalan , Stanley Frederick , Terry Adrian , Dean Gregory 
Published: February 2015

Well completion in deepwater operations are particularly challenging from an engineering perspective. With the high cost and high risk associated with deepwater interventions it's critical to reduce the number coiled tubing runs and maximize the number of operations that can be performed during one run into a well.
Coiled tubing perforation jobs have historically required multiple runs to correlate depth, perforate and sometimes stimulate or gas lift a well. Recent advancement in this field has resulted in a suite of solutions based on a realtime downhole communication system comprising a non-intrusive electrical conductor, surface hardware and software, and a combination bottomhole assembly (BHA). The combination BHA incorporates the motorhead assembly, conductor and BHA release function, and a pressure, temperature, and casing collar locator sensor package for accurate depth correlation with high-resolution pressure and temperature data. The design also enables the use of ball-activated tools.
A particular offshore Philippines deepwater project recently benefited from this technology. The coiled tubing downhole communication system obtained realtime data using a small-diameter conductor wire pre-installed inside the coiled tubing. The data was used to optimize conventional coiled tubing interventions and expand the use of wireline logging tools. The conductor has minimal effect on the flow area of the coiled tubing or on the overall weight of the reel. The logging BHA was attached with mechanical and electrical quick connects and was rigged up offshore in minutes.
This paper reviews how the new downhole communication system extended the capabilities of coiled tubing during two deepwater well interventions. It will further discuss the system's operational flexibility by illustrating the case study of running the system.
Numerical Studies of Vortex Induced Vibration of a Circular Cylinder at High Reynolds Number
Authors: Tofa M. Mobassher , Maimun Adi , Ahmed Yasser M. , Jamei Saeed , Khairuddin N.M. 
Published: February 2015

Study of vibrations due to vortex shedding(VIV) in the wake of a cylinder that is exposed to a current is very important, especially for marine risers which are used to extract oil and gas from sea bed. The phenomenon of vortex induced vibration(VIV) has been one of the major concerns for hydrodynamic researchers due to its potential ability to cause severe fatigue damage, the hydrodynamics of VIV is a very complex subject to be dealt with. Though there are numbers of research papers about VIV simulation of a circular cylinder, most of them were related to 2D flow and lower Reynolds number. 3D numerical simulation of vortex induced vibration at high Reynolds number can be very challenging.
Successful 3D simulation can be useful for designing effective VIV suppression devices.
Suitable mesh and turbulence model are important to get desired results, analyzing computational time and resources are crucial before starting such projects. In this paper turbulence model such as DES and LES are used at three dimensional VIV simulation for a Reynolds number Re=104, results from CFD are compared with existing experimental results. A comparison was drawn between these two turbulence models in terms of result accuracy and computation time.
Hopefully discussion of this paper can be helpful for any future project that would deal with VIV simulation.
A Human Rights Approach to Localising The MDGs Through Gender-Equitable Local Development
Authors: McGill Ron 
Published: February 2015

Until now, the United Nations Capital Development Fund’s (UNCDF) Gender Equitable Local Development (GELD) programme has not been presented within an explicit human rights framework. This is strange given that the human rights based approach to development (HRBAD) aims to ensure that all human beings can live their lives fully and with dignity. HRBAD is fundamentally about the healthy and full development of individuals and communities. In addition, one of human rights’ central concerns is that people have equal access to the benefits of society. Initiatives to realize human rights therefore give priority to the most marginalized - the poorest - in a society. It is those individuals who have most difficulty in securing the basics that are essential to living their lives with dignity. Women in all communities are disproportionately represented among the poor. Thus, human rights have gender equity as a central focus. Put another way, we are dealing with the feminization of poverty. We are dealing with the concept of equal access (to development). In short, we are dealing with those who need (and deserve) greater priority in access to infrastructure and supporting services in order to reach a point of equality.
The Capacity and Institution Building (CIB) Working Group of United Cities and Local Governments: Towards Improving Aid Effectiveness in the Local Government Sector
Authors: Kehoe Tim 
Published: February 2015

The United Cities and Local Governments (UCLG) Capacity and Institution Building (CIB) Working Group gather together professional practitioners of local government associations (LGAs) and individual local governments active in international cooperation, with the overall objective to improve the quality, coordination and alignment of their development cooperation interventions.The Working Group is the successor of the CIB Platform, which existed for many years within the former International Union of Local Authorities (IULA) as an informal gathering of staff members of local government associations (LGAs) involved in the field of municipal international cooperation (MIC) and association capacity building (ACB). In addition to information exchange, the CIB Platform undertook specific initiatives such as a World Bank-funded program supporting ACB in several countries. In May 2004, the CIB was integrated into the structures of the newly-founded UCLG organisation, and its membership was expanded to also include staff members of international departments of cities active in international cooperation.
Recent trends in Gender Mainstreaming and Poverty Alleviation: The Kudumbashree Initiative
Authors: Tiwari Nupur 
Published: February 2015

Kudumbashree was officially launched in 1998 in the State of Kerala, India, with the objective of eradicating absolute poverty in 10 years through community action. It is a comprehensive women-based poverty eradication programme jointly initiated by Government of Kerala and National Bank for Agriculture and Rural Development (NABARD), scaled up from earlier UNICEF-assisted initiatives in Alappuzha Municipality and Malappuram district. The programme is implemented by community-based organizations (CBOs) of poor women in co-operation with local governments (Panchayats).Kudumbashree focuses on empowerment of women through its CBOs and activities such as service coordination, encouraging thrift and internal lending, and start-up of micro enterprises. There are success stories of enterprises such as catering and canteen services at bus stands and offices in several places across the state. Handling of solid waste in municipalities is another emerging area of activity.
The Contrapuntal Humanisms of Edward Said
Authors: BARTINE DAVID 
Published: February 2015

Abstract
In Culture and Imperialism Said proposes (and discusses elsewhere) counterpoint in music as a model for a different kind of critical reading. The article examines ambiguities in his concepts of counterpoint and provides a study of ways in which Said's ideas about counterpoint in music bear on his somewhat problematic discussions of a humanism critical of humanism in his final book project, Humanism and Democratic Criticism.
Bijstand als schadepost
Authors: Oude Hergelink A.S. , Vermaat M.F. 
Published: February 2015

Bijstand als schadepost
Schadevergoedingen en de bijstandswet vormen geen gelukkig paar. Immers, voordat iemand een beroep op de bijstand zoals geregeld in de Participatiewet kan doen, moet er geen sprake meer zijn van vermogen boven de vrijlatingsgrens. Waarom schade vergoeden als de gemeente vervolgens de bijstand beëindigt? In deze bijdrage wordt aan de hand van wetgeving, gemeentelijke regelgeving en jurisprudentie besproken wat de gevolgen voor het recht op bijstand (kunnen) zijn wanneer een bijstandsgerechtigde een letselschadevergoeding ontvangt. Op 16 april 2014 heeft de Rechtbank Zeeland-West-Brabant geoordeeld dat indien het onderhavige letselschadeslachtoffer haar aanspraak op een bijstandsuitkering (deels) zou verliezen, dat aangemerkt diende te worden als schade en die schade voor vergoeding door de aansprakelijke partij in aanmerking komt. Deze uitspraak werpt een nieuw licht op de problematiek.
Abstraction
Authors: Dye Dick 
Published: February 2015

AbstractThe wordabstractionis used as a noun, “to build an abstraction.” Its root form,abstract, is used as a verb, “to abstract the requirements to perform a domain analysis” or as an adjective, “a linked list is an abstract concept.” From the software engineering perspective, all of these uses refer to the concept of identifying essential properties while simultaneously eliminating nonessential properties. An abstraction intentionally ignores some qualities, attributes, or functions to focus attention on others. It is a summary; it covers the high points and leaves out the details. An abstraction omits all the pieces of the system that are not necessary for understanding the system at a given level of detail. The abstraction includes only the relevant aspects of the object. The selection of what to include and what to exclude in a good abstraction is based on knowledge of the problem, the needs of the moment, and experience. A proper combination of these considerations leads to a good abstraction.The purpose of creating abstractions is to concentrate on one aspect of the problem and to preclude distraction by other parts of the problem. Level of abstraction is a quality that deals with the amount of detail in this view of a system. The process of abstraction has also been referred to as chunking. In this context, one abstraction represents one chunk of information. Encapsulation is the process of separating and hiding the external (user's) view of an abstraction from the internal (implementer's) view of the abstraction. There are three fundamental abstractions in terms of which all software can be described. A complete design must include all three. They are data, function, and process. These are discussed.
Acceptance Testing
Authors: Marciniak John J. , Shumskas Anthony 
Published: February 2015

Abstract
Acceptance testing (AT) is a testing process that is applied to ascertain whether the software products under development have met the requirements specified by agreement, e.g., contract. It helps validate, typically through functional testing, that the software items fulfill the requirements and specifications appropriate for the life cycle of the software product, AT can be performed in phases, and either on the interim or final software products for both new and modified software systems. It is conducted under controlled conditions using documented procedures to generate, acquire, and record data that accurately measure the software product against predefined criteria for functionality, performance, interface quality, and identified quality attributes (e.g., safety, security, reliability, interoperability). This activity may involve all or some of the following: instrumentation, test software, simulation software, and/or special test equipment; and includes the evaluation of the acquired data to verify compliance with specified performance requirements.
Ada Programming Language
Authors: Feldman Michael B. , Brosgol Benjamin M. 
Published: February 2015

AbstractAda is a Pascal‐like programming language whose original development and later enhancement was sponsored by the U.S. Department of Defense (DOD). Today Ada is alive and well, and software developed in it can be found not only in defense applications worldwide, but also in trains, planes, and automobiles, not to mention commercial satellites, steel mills, cable television, and “smart cards”.The current Ada standard is Ada 95; the language of the original Ada standard is now referred to as Ada 83. Where necessary to full understanding the determation between Ada 83 and Ada 95 is made. but we keep this distinction to a minimum.DOD sponsored Ada as a means to address two fundamental cost problems typical of embedded systems. Ada 95 adds a coherent set of smooth extensions that were designed in direct response to experience with Ada 83 and other languages and environments, and also to the spectacular improvements in hardware and operating systems during the 1980s and 1990s.Ada has sometimes been described as a manager's language rather than a programmer's language. There is some validity to this description, since the language encourages the software developer to plan ahead, and since its philosophy is oriented around ease of program readability rather than conciseness of notation. In the defense industry, and especially outside it, most programs are written only once, then debugged, maintained, added to, and subtracted from, repeatedly, over many years. Basing the language facilities on the needs of system maintenance and enhancement was a key insight in the initial design, and the relevance of this principle has not diminished over time.
Analogical Models/Expert Judgment
Authors: Hughes Robert T. 
Published: February 2015

AbstractAlthough expert judgment and the use of analogy have many applications in software engineering—for example, in the selection of reusable components and the identification of design patterns—the terms are most closely associated with the process of estimating software development effort. An estimate of development effort is a prediction, based on available information, of the effort needed to develop a software application. A true prediction should not itself influence actual effort as that would transform it into a performance goal. Thus managers of the software development process are interested in prediction as an intermediate step on the way to identifying reasonable performance goals for those participating in a development project.Analogy and case‐based reasoning would appear to be key methods used by expert estimators. A systematic approach to using analogy suggested by Cowderoy defined the six steps: Assessing the problem; finding the Case History; identifying the differences; quantifying the differences; analyzing the uncertainty; and communicating results. The attempts to automate these processes are discussed.
Software Architecture
Authors: Garlan David 
Published: February 2015

AbstractAs the size and complexity of software systems increase, the design, specification, and analysis of overall system structure becomes a critical issue. Structural issues include the organization of a system as a composition of components; global control structures, the protocols for communication, synchronization, and data access; the assignment of functionality to design elements; the composition of design elements; physical distribution; scaling and performance; and dimensions of evolution. This is thesoftware architecturelevel of design.Over the past decade architectural design has emerged as an important subfield of software engineering. Practitioners have come to realize that having a good architectural design is a critical success factor for complex system development. A good architecture can help ensure that a system will satisfy key requirements in such areas as performance, reliability, portability, scalability, and interoperability. A bad architecture can be disastrous.Practitioners have also begun to recognize the value of making explicit architectural choices, and leveraging past architectural designs in the development of new products. Today there are numerous books on architectural design, regular conferences and workshops devoted specifically to software architecture, a growing number of commercial tools to aid in aspects of architectural design, courses in software architecture, major government and industrial research projects centered on software architecture, and an increasing number of formal architectural standards. Codification of architectural principles, methods, and practices has begun to lead to repeatable processes of architectural design, criteria for making principled tradeoffs among architectures, and standards for documenting, reviewing, and implementing architectures. The role of the architecture, description language and tools are discussed.
Artificial Intelligence in Software Engineering
Authors: Partridge Derek 
Published: February 2015

AbstractArtificial intelligence (AI) and software engineering (SE) have, to a large extent, developed and matured independently, but recent years (at the time of writing) have brought significant cross‐fertilisation and the consequent developments exhibit the expected hybrid vigor. These two fields have a lot in cornmon—both aim to implement software systems as the prime goal. They also have many differences, especially when viewed historically. AI was, and perhaps still is, a domain of researchers whose aims were to reproduce aspects of human intelligence on computers and thereby learn something about the nature of computational intelligence per se, or about the embodiment of this intriguing phenomenon in humans. Software engineers, on the other hand, were preoccupied with developing a science and technology for efficiently instantiating quite well‐defined problems, robustly and reliably, in computer systems. The activities of both groups centered around programs and programming, but there the similarity ended. A successful outcome was measured rather differently within these two fields: (1) a reliable (perhaps verified) implementation of a well‐defined function for the software engineer and (2) a selection of “intelligent” behaviors from a concrete instantiation of a complex, incomplete, and ill‐defined theory for the AI researcher. So it is not too surprising that these two fields developed somewhat independently of each other.It is useful to outline a framework within which one can consider the full spectrum of impacts of AI on software engineering. There are three (or possibly four) major classes of interaction of AI and SE: software support environments, AI tools and techniques in conventional software, and use of conventional software technology in AI systems. The fourth area is methodological considerations. The impact of AI on software engineering, from a methodological perspective, has been to promote recognition of the inadequacies of a linearized specify‐and‐verify approach to software production. Instead of AI workers learning to “do things properly,” to specify their problems completely before designing solutions (although this has happened to some extent as well), the impact has been that software engineers recognize that interative software development can be a legitimate approach.