The programming languages that describe hardware circuits are important for circuit designers to assist them to design and develop the hardware circuits. In this master’s project, the Lava hardware description language is used to design and develop hardware components for a baseband processing API. Lava is a language embedded in the general purpose language Haskell. The function for checking transmission errors in the baseband processing chain, Cyclic Redundancy Check (CRC) is implemented in different ways and tested. Linear Feedback Shift Registers (LFSRs) circuits for a particular polynomial generator are developed, implemented and simulated by using Lava code to calculate the CRC. A generalized function of CRC is developed as a circuit generator for any given polynomial generator. The circuit is tested by automatic test program.

The modern oil and gas industry of America has seen most of the high quality, easily obtainable resources, already produced, thus causing wells to be drilled deeper in search for unconventional resources. This means Oil Country Tubular Goods (OCTG) must improve in order to withstand harsher conditions; especially the ability of connections to effectively create leak tight seals. This study investigates the use of thread connections in tight gas fields; therefore, an insight into their potential to contribute to fulfilling the energy demands is necessary. Also, a survey of completed projects done in tight gas fields can provide vital information that will establish the minimum requirements thread connection must meet to perform its functions. To make suitable adjustments to ensure safe and efficient operations we must thoroughly understand the many aspects of thread connections. To have this understanding, a review of previous works was carried out that highlights the capabilities and imitations of thread connections. In addition to reviewing previous work done on thread connections; this study measured the viscosity of thread compounds under variable conditions. It was found that viscosity of thread compound falls in the range of 285,667 cP and 47,758 cP when measured between 32.9 degrees F and 121.5 degrees F. This can be very important because thread compound is essential to the function of thread connections. The knowledge of its viscosity can help choose the most suitable compound. By knowing the value of the viscosity of a thread compound it can also be used to form an analytical assessment of the grooved plate method by providing a means to calculate a pressure gradient which impacts the leakage.

A database with 217 cases of load tests on shallow foundations, mostly in/on granular soils, was compiled. With this information, the comparison of predicted bearing capacity using different design methods, the American Petroleum Institute Recommended Practice 2A-LRFD (API RP2A-LRFD,1989), the American Petroleum Recommended Practice 2GEO (API RP2GEO, 2011), and International Standard Organization (ISO, 2003) is carried out. The answer to which standard makes a good prediction varies with the way to define failure load from load-displacement curve. Overall, ISO has a higher prediction compared with API RP2A and API RP2GEO. For the cases with vertical concentric loading conditions, if the capacity at plastic region and is defined as failure load, then the prediction by API RP2A is closest to measured capacity. If the capacity corresponding with 10% of footing width is considered as failure load, then the API RP2A and API RP2GEO underestimate the capacity, while ISO is in a good agreement with capacity corresponding with 10% of footing width. The prediction by API RP2GEO generally has a good agreement with capacity at tangent intersection region. In most of the cases with vertical eccentric loading, all three standard underestimate the measured capacities no matter which interpreted capacities is considered as failure load, while ISO makes slightly overprediction at the lower range of eccentricities and underprediction at higher range of eccentricities for some cases. In the inclined loading condition, the prediction by API RP2GEO is minimum among the three standards, while ISO proposed the highest prediction. All three prediction underestimate the capacity under inclined loading condition. From this study, it is found that small scale load laboratory test reveals a qualitative understanding with impact of vertical eccentric and concentric inclined loading on ultimate capacities. However, it is hard to detect a clear best prediction based on small scaled laboratory load test results. The well-controlled field test results, especially the field tests with vertical eccentric and concentric inclined loading condition, are valuable to evaluate the consistency of predicted capacity by three standards. / text

Ever had an experience of forgetting to do something very important on a place you just past?. Remembering, on arrival at your destination afterward, requires an action to return to the task location. This can be unproductive and perhaps result to frustration. The purpose of this thesis is to develop a “Location Task-To-Do manager” an android mobile application that will efficiently organizes task-to-do list and remind an individual to perform a task at a pre-defined location through notification and alert messages. The methods used includes,  investigation of pre-existing systems, requirement elicitation survey technique, three-tier architecture design pattern, iterative development life-cycle model, acceptance test plan and a sets of other technology such as  Java SDK, Android APIs, TCP/IP protocol, object oriented programing techniques and MySql relational database. The result showed that, installed “Location Task-To-Do manager” application on individual mobile devices/smartphones were capable of creating task, adding task, editing task, deleting task, sharing task and setting task location through its user friendly graphical interfaces. Users are able to receive notification to perform a task within a minimum distance of 1km to the exact task location.

Diss. no. 15372 techn. sc. SFIT Zurich. / Im Buchh.: Aachen : Shaker. Literaturverz.

Techn. University, Diss., 2002--Berlin.

No description available.

Made available in DSpace on 2018-08-01T23:40:33Z (GMT). No. of bitstreams: 1 tese_6823_Finanças Comportamentais Um Estudo Sobre o Perfil do Investidor2013.pdf: 1832085 bytes, checksum: d0e659b02801917799cad972b20eacc2 (MD5) Previous issue date: 2013-08-29 / Nas mais diversas áreas de negócios, é comum que um gestor busque conhecer o perfil de seus clientes para oferecer produtos e serviços mais adequados às necessidades desses clientes. Os gestores que atuam no mercado financeiro utilizam um instrumento para identificar o perfil do investidor e ao mesmo tempo adequar a oferta de produtos e serviços financeiros em conformidade com a capacidade e a propensão de assumir riscos desse investidor, sobretudo daquele inserido no contexto do mercado de ações. Esse instrumento, apesar de não ser padrão, segue recomendações de órgãos reguladores e de associações de entidades do mercado de capitais (no Brasil, a Anbima - Associação Brasileira das Entidades dos Mercados Financeiro e de Capitais). Esses instrumentos utilizam, para a avaliação do perfil de risco, fatores como situação financeira do investidor, objetivo do investimento, horizonte de tempo para obtenção de resultados, tolerância ao risco e experiência em investimentos de risco. Não consideram fatores comportamentais que segundo a teoria, podem afetar a propensão a assumir riscos. Dentre esses fatores estão o senso de autocontrole, que ocasiona uma percepção distorcida de controle sobre os resultados esperados, e o grau de autoconfiança que no extremo pode levar ao excesso de confiança ou excesso de otimismo quanto a resultados esperados. Sendo assim, por meio de uma pesquisa realizada com 59 clientes de uma corretora de ações, o presente estudo se propôs a avaliar se o perfil de risco do investidor calculado segundo recomendações de órgãos reguladores do mercado financeiro, afeta o senso de autocontrole e o grau de confiança dos investidores em suas decisões de investimentos no mercado de ações. E avaliar se é possível segmentar os investidores de acordo com características pessoais e fatores que compõem o seu perfil de risco de forma a mais bem caracterizá-los quanto a riscos assumidos e retornos obtidos em seus investimentos em mercados de risco. Buscou identificar quais fatores que compõem a avaliação do perfil de risco são mais relevantes para discriminar os investidores segundo suas características pessoais e sua propensão a assumir riscos. A partir de uma análise de conglomerados (cluster analysis) o estudo identificou três grupos distintos de investidores com diferentes níveis de conhecimento e experiência de investimentos no mercado de ações e relacionou esses grupos a riscos assumidos e retornos alcançados em seus investimentos.

Context. The approach of developing software systems with the use of third partycomponents i.e. COTS or OSS has increased globally. In this study API product refers toeither a software component or a software service or both packaged together, that can beaccessed through an API. Developers are faced with plethora of alternative choices to selectan API product. With this increase in components adoption, API product providers are facedwith challenge of designing their product to be more attractive than others. This needs theproviders to be educated about the developer behavior when they choose an API product.Understanding the selection practices of developers can help providers to improve thepackaging of API products, making them more suitable for selection. Objectives. The objectives of this study is to investigate the criteria that developers usewhen reasoning about acceptability of a software component. Methods. A background study is performed to identify the evaluation criteria proposed inthe literature. An empirical study using Qualitative content analysis is performed. In the study the 480 reviews of different API products are analyzed to understand the criteria frompractitioners’ perspective. Results. 9 relevant criteria that developer use to reason about accepting or rejecting an APIProduct are identified. 30 sub criteria related to the 9 criteria are described in the study. Conclusions. This study concludes that the identified 9 criteria play an important role indeveloper assessment of the API product. It is also found that the criteria have significantimpact on the ratings of API product. These criteria could guide API product providers tomake better choices when developing the product.

Att skicka rätt agent till rätt uppdrag är fundamentalt för förmedlingsbolag. För att garantera att detta sker på ett effektivt sätt utvecklade Fasbros IT tjänsten ARUBA som rangordnar en uppsättning agenter efter deras restid till ett uppdrag. Detta genomfördes med hjälp av Google Maps- och GraphHopper Directions API:er. ARUBA är ett back-end system. Systemet tar emot ett JSON-objekt som innehåller ett uppdrag och en lista agenter, dessa agenter sorteras efter kortast restid till uppdraget. Resultatet sparas i en lista som returneras som ett JSON-objekt. Systemet klarar av att hantera tusentals agenter och är robust så att den klarar av att fortsätta arbeta även ifall en av dess två API:er blir otillgängligt. Koden är väldokumenterad och har en god grund för att kunna vidareutvecklas av intressenten. Det är simpelt att utöka mängden API:er som används och samtidigt behålla robustheten i applikationen. ARUBA skapades i syfte att visa intressenten att deras nuvarande system kan förbättras i funktionalitet, effektivitet och precision. / Sending the best agent to the most fitting mission is fundamental for any company. To guarantee that this is done efficiently, Fasbros IT have created the ARUBA service that ranks a group of agents based on their respective traveltimes to a mission. This was done by the means of existing Google Maps and GraphHopper API:s. ARUBA operates as a back-end service that communicates with a separate interface that sends and receives information from it in form of JSON-objects. A mission and a list of agents are received and a ranked list of the agents based on their traveltimes to the mission is the output of ARUBA. The service is able to handle thousands of agents and is robust in the sense that it is able to switch between API:s in order to keep running in case one of the them isn’t responding. The code is thoroughly documented and stands on a solid base that is easily developable by the stakeholder. It is easy to increase the amount of API:s that are used and still maintain the robust ability of the system. ARUBA was created in order to prove to the stakeholder that their current system could be improved in its functionality, efficiency and precision.