Este trabalho se propõe a remontar a dissolução ocorrida no tempo em que a Economia Política buscava limitar seu campo de estudo, particularmente no que se refere a percepção sobre a conduta humana e a assunção de que os homens são intrinsecamente egoístas. Para tanto, é desenvolvida a visão do homem moralmente condicionado em Adam Smith e também as modificações subsequentes originadas nas diferentes concepções dos autores da escola clássica e da neoclássica. Sendo que estas mudanças enfatizam o egoísmo do agente econômico. Neste intento, é retraçado o caminho da consolidação do postulado do egoísmo, assim como os percalços, controvérsias e conflitos desta caracterização. São explorados os elementos que auxiliaram na transformação do homem smithiano em homo economicus, tais como a leitura descontextualizada de Smith, o individualismo, o utilitarismo, o individualismo metodológico, o positivismo e a própria necessidade de abstração teórica. Adicionalmente, é verificado que a confusão de conceitos presente nesta construção metodológica traz a referência de que a ciência econômica faz apologia ao egoísmo. Esta percepção é um subproduto do desenlace da economia com as questões morais. / This research is proposed to reassemble the dissolution occurred when the Political Economy sought to limit their field of study, particularly in the perception of humann behavior and the assumption that men are inherently selfish. To do that, it is developed the perception of Adam Smith about human behavior, and the subsequent changes resulting from different conceptions of classical and the neoclassical authors. These changes emphasize the selfishness of the economic agent. In this attempt, is showed the way of the consolidating of self-interest premise, the mishaps and controversies of this path. It explores the the elements that collaborated in the transformation of Smithian man in homo economicus, such as decontextualized reading of Smith, individualism, utilitarianism, methodological individualism, positivism and the very necessity of theoretical abstraction. Additionally, it is observed that the confusion of concepts present in this methodological construction suggests that economics salutes the egoism. This is a result of the distinction between moral and economic aspects.

Este trabalho se propõe a remontar a dissolução ocorrida no tempo em que a Economia Política buscava limitar seu campo de estudo, particularmente no que se refere a percepção sobre a conduta humana e a assunção de que os homens são intrinsecamente egoístas. Para tanto, é desenvolvida a visão do homem moralmente condicionado em Adam Smith e também as modificações subsequentes originadas nas diferentes concepções dos autores da escola clássica e da neoclássica. Sendo que estas mudanças enfatizam o egoísmo do agente econômico. Neste intento, é retraçado o caminho da consolidação do postulado do egoísmo, assim como os percalços, controvérsias e conflitos desta caracterização. São explorados os elementos que auxiliaram na transformação do homem smithiano em homo economicus, tais como a leitura descontextualizada de Smith, o individualismo, o utilitarismo, o individualismo metodológico, o positivismo e a própria necessidade de abstração teórica. Adicionalmente, é verificado que a confusão de conceitos presente nesta construção metodológica traz a referência de que a ciência econômica faz apologia ao egoísmo. Esta percepção é um subproduto do desenlace da economia com as questões morais. / This research is proposed to reassemble the dissolution occurred when the Political Economy sought to limit their field of study, particularly in the perception of humann behavior and the assumption that men are inherently selfish. To do that, it is developed the perception of Adam Smith about human behavior, and the subsequent changes resulting from different conceptions of classical and the neoclassical authors. These changes emphasize the selfishness of the economic agent. In this attempt, is showed the way of the consolidating of self-interest premise, the mishaps and controversies of this path. It explores the the elements that collaborated in the transformation of Smithian man in homo economicus, such as decontextualized reading of Smith, individualism, utilitarianism, methodological individualism, positivism and the very necessity of theoretical abstraction. Additionally, it is observed that the confusion of concepts present in this methodological construction suggests that economics salutes the egoism. This is a result of the distinction between moral and economic aspects.

This thesis is focused on analyzing the current state of SaaS (Software as a Service) and impact of SaaS on corporate's ICT as a whole. The aim is to explain the concepts and implications of modern forms of providing services, to describe and to evaluate their benefits and risks and to assess future developments in this area. The attention will be paid on specifics of the environment of Czech companies. The first part of this work deals with the current SaaS solutions and related technologies. Emphasis is placed on acquainting the reader with currently available (or introduced by mid-2011) technologies and their mutual relationships. This section also summarizes the current level of knowledge of the field and on this basis provides definitions of areas and technologies. The next part of the thesis focuses on a particular cloud and SaaS solutions available on nowadays market. The next part of this section is based on a specific case study of a small company, which considers the move to SaaS solutions. This section is focused on the practical application of the preceding conclusions. Last section aims at the prediction of development of ICT business in the upcoming years, with an emphasis on SaaS and related technologies. The second part is trying to find answers to the questions "Whether," "When" and "How" will SaaS affect the market of information technologies, their deployment and business models of future anticipated expansion model of Software as a Service. SaaS maturity model is also discussed as well as specificity of the Czech market.

No description available.

DevOps is a cultural idea rather than a firm way to do software development, with the aim of reducing software lead times by bringing operations and development closer via principles that mainly deal with automation. This paper provides a potential DevOps solution for Wexnet, an internet service provider company. A requirements list is created by interviewing which is then used to evaluate existing web-based git solutions. Two viable candidates were selected, GitHub and GitLab which were compared against each other. GitLab was chosen because of its comparably low resource usage and lower overall setup complexity.

The development of AI application on the edge devices require integrated data, algorithms, and tools. Big companies like Google and Apple have integrated data, algorithms, and tools for building end to end systems with optimized and dedicated hardware for deep learning applications. The Bonseyes [2] EU H2020 collaborative project is an open and expandable AI platform. Bonsey's provides access to advanced tools and services that can be obtained from the data market place and eco-system of collaborative leading academic and industrial partners for adding AI to embedded products. Bonseyes AI Marketplace proposed an end to end AI pipeline to overcome these requirements for the development and deployment of AI solutions on edge devices. In Bonseyes, a Secure virtual premise (SVP) is a secure and protected area for the collaborative and systematic development of AI using Machine Learning AI Pipelines. The centralized SVP has limitations like scalability, reliability, and load balancing. This thesis work focuses on the enhancement of SVP and its mechanisms to adopt a distributed and federated architecture for better performance and fast development of AI applications. It investigates various federation mechanisms and implements a distributed and federated SVP. A Marketplace rendezvous host is designed and implemented from where multiple distributed compute resources can be started, controlled, and stopped by a user. Users and distributed locations related data are stored in an SQLite relational database. Communication between entities of distributed and federated SVP is enabled using HTTPs protocol and PKI Infrastructure is used for authentication and authorization of users. We evaluate the performance of our implementation by calculating the start-up time of multiple resources until a user can perform AI Engineering. The results show that time is directly proportional to the number of nodes started.

No description available.

Multinivåarkitekturer, eller N-nivåarkitekturer där 'N' refererar till antalet nivåer som börjar med 1, är ett sätt att strukturera nätverk och applikationer, antingen i '”on-premises”-infrastrukturer eller på molnplattformar, liksom inom infrastrukturer som kod (IaC). Dessa arkitekturer innebär att man delar upp nätverket eller applikationen i separata lager och nivåer. Varje lager har ett specifikt ansvarsområde och de högre lagren kan använda tjänster i de lägre lagren, men inte tvärtom. 'Nivåer' avser en fysisk separation av nätverket och applikationerna, där de olika nivåerna kan kommunicera med varandra via nätverkskommunikationspunkter där särskilda regler gäller. En nivå kan innehålla ett eller flera lager. Denna arkitektur kan ge hög säkerhet, flexibilitet, skalbarhet, enkelhet och stabilitet till en rimlig kostnad. Den här uppsatsen har tre huvuddelar. Den första delen fokuserar på en analys av multinivåarkitekturer, deras uppbyggnad och de för- och nackdelar de innebär. Dessutom jämför och diskuterar vi skillnaderna mellan N-tier-arkitektur och andra arkitekturer. I uppsatsens andra del granskar vi de miljöer, säkerhetsaspekter, kostnader, verktyg och plattformar där denna arkitektur kan implementeras. Den tredje och sista delen innefattar ett praktiskt arbete, där vi planerar, designar, implementerar och automatiserar en nätverksinfrastruktur för ett nyetablerat företag baserat på N-tier-arkitektur i en testsituation som skapas för detta ändamål. Uppsatsen avslutas med en redovisning av de praktiska resultaten, en diskussion om metoderna och samhällsaspekterna, samt rekommendationer och förslag till framtida arbete. Uppsatsen har resulterat i två huvudsakliga utfall: en detaljerad teoretisk förklaring och jämförelse av olika nätverksarkitekturer och deras tillämpningsområden, samt en mall för genomförandet av liknande projekt från idéstadiet till en automatiserad infrastruktur som kan integreras på vilken plattform som helst. / Multi-tier architectures, or N-tier architectures where “N” refers to the number of levels starting with 1, is a way to structure networks and applications, either in “on-premises” infrastructures or on cloud platforms, as well as in Infrastructure as Code (IaC). These architectures involve dividing the network or application into separate layers and levels. Each layer has a specific area of responsibility, and the higher layers can use services in the lower layers, but not vice versa. “Levels” refers to a physical separation of the network and applications, where the different levels can communicate with each other via network communication points where specific rules apply. A level can contain one or more layers. This architecture can provide high security, flexibility, scalability, simplicity, and stability at a reasonable cost. This thesis has three main parts. The first part focuses on an analysis of multi-tier architectures, their structure, and the advantages and disadvantages they offer. In addition, we compare and discuss the differences between N-tier architecture and other architectures. In the second part of the thesis, we examine the environments, security aspects, costs, tools, and platforms where this architecture can be implemented. The third and final part includes a practical work, where we plan, design, implement, and automate a network infrastructure for a newly established company based on an N-tier architecture in a test situation created for this purpose. The thesis concludes with a presentation of the practical results, a discussion of the methods and societal aspects, as well as recommendations and suggestions for future work. The thesis has resulted in two main outcomes: a detailed theoretical explanation and comparison of different network architectures and their areas of application, and a template for carrying out similar projects from the idea stage to an automated infrastructure that can be integrated on any platform

There has been a substantial growth in the usage of data in the past decade, cloud technologies and big data platforms have gained popularity as they help in processing such data on a large scale. Hopsworks is such a managed plat- form for scale out data science. It is an open-source platform for the develop- ment and operation of Machine Learning models, available on-premise and as a managed platform in the cloud. As most of these platforms provide data sci- ence environments to collate the required libraries to work with, Hopsworks provides users with Anaconda environments.Hopsworks provides multi-tenancy, ensuring a secure model to manage sen- sitive data in the shared platform. Most of the Hopsworks features are built around projects, each project includes an Anaconda environment that provides users with a number of libraries capable of processing data. Each project cre- ation triggers a creation of a base Anaconda environment and each added li- brary updates this environment. For an on-premise application, as data science teams are diverse and work towards building repeatable and scalable models, it becomes increasingly important to manage these environments in a central location locally.The purpose of the thesis is to provide a secure storage for these Anaconda en- vironments. As Hopsworks uses a Kubernetes cluster to serve models, these environments can be containerized and stored on a secure container registry on the Kubernetes Cluster. The provided solution also aims to extend the multi- tenancy feature of Hopsworks onto the hosted local storage. The implemen- tation comprises of two parts; First one, is to host a compatible open source container registry to store the container images on a local Kubernetes cluster with fault tolerance and by avoiding a single point of failure. Second one, is to leverage the multi-tenancy feature in Hopsworks by storing the images on the self sufficient secure registry with project level isolation. / Det har skett en betydande tillväxt i dataanvändningen under det senaste decen- niet, molnteknologier och big data-plattformar har vunnit popularitet eftersom de hjälper till att bearbeta sådan data i stor skala. Hopsworks är en sådan hante- rad plattform för att skala ut datavetenskap. Det är en öppen källkodsplattform för utveckling och drift av Machine Learning-modeller, tillgänglig på plats och som en hanterad plattform i molnet. Eftersom de flesta av dessa plattformar tillhandahåller datavetenskapsmiljöer för att samla in de bibliotek som krävs för att arbeta med, ger Hopsworks användare Anaconda-miljöer.Hopsworks tillhandahåller multi-tenancy, vilket säkerställer en säker modell för att hantera känslig data i den delade plattformen. De flesta av Hopsworks- funktionerna är uppbyggda kring projekt, varje projekt innehåller en Anaconda- miljö som ger användarna ett antal bibliotek som kan bearbeta data. Varje projektskapning utlöser skapandet av en basanacondamiljö och varje tillagt bibliotek uppdaterar denna miljö. För en lokal applikation, eftersom datave- tenskapsteam är olika och arbetar för att bygga repeterbara och skalbara mo- deller, blir det allt viktigare att hantera dessa miljöer på en central plats lokalt. Syftet med avhandlingen är att tillhandahålla en säker lagring för dessa Anaconda- miljöer. Eftersom Hopsworks använder ett Kubernetes-kluster för att betjäna modeller kan dessa miljöer containeriseras och lagras i ett säkert container- register i Kubernetes-klustret. Den medföljande lösningen syftar också till att utvidga Hopsworks-funktionen för flera hyresgäster till det lokala lagrade vär- det. Implementeringen består av två delar; Den första är att vara värd för ett kompatibelt register med öppen källkod för att lagra behållaravbildningarna iett lokalt Kubernetes-kluster med feltolerans och genom att undvika en enda felpunkt. Den andra är att utnyttja multihyresfunktionen i Hopsworks genom att lagra bilderna i det självförsörjande säkra registret med projektnivåisole- ring.

No description available.