Institute of Right to Build in Czech and German Law The thesis deals with the topic of the institute of right to build in Czech and German law. The elementary aim of the thesis is to describe the legal institute of right to build, not only in the Czech legal system, but also in the German legal system. The right to build is an absolute property right with effect erga omnes. It belongs into a group of rights, which privileges one to use a thing of someone else. The statute declares the right to build to be real property. On the ground of the right to build arises the right of the builder to have a building on the surface or under the surface of the encumbered piece of land. The right to build is always limited through a set period of time, it should not be created for longer than 99 years. The typical features of the right to build are alienability and inheritability. The content of this thesis is divided into four chapters. The nature of right to build, as a right, which privileges one to use the thing of someone else, is described in the first chapter. There are also descriptions of the basic legal terms associated with the right to build. The chapter describes the terms 'building' and 'builder' as well as the principle of superficies solo cedit. The second chapter is dedicated to the history of...

The thesis is focused on institute called right to build and other possibilities to build on somebody else's land in accordance with Civil Code effective since 1. 1. 2014. It also defines important terms connected to the right to build, its history on Czech territory and its foreign form which can be used as source of inspiration for future practice. Part of the thesis deals with unauthorized structures on somebody else's land which are built on the land without a legal reason.

Continues Integration has been a vital part of software development process in order to make the development process fast and reliable. There are number of actors which play an important role with support of third party tools that helps the development process to be effective and productive in nature. The CI- toolchain is capable of doing much more than the compilation of the software project which covers the daily life tasks of the developers like testing, documentation etc. The important part of automated toolchain is the conversion of source code artifacts into executables with the help of the build system. The selection of proper build system is a matter of subjective in nature and it depends upon the number of factors that should be analyzed before proceeding forward towards the selection mechanism. This thesis focuses on software rebuilding and proves practically with experiments that could help developers and managers to decide between two important software build systems SCons and CMake. It has been experimentally proved that what are the conditions and situations where SCons performs better and what are the moments where it is wise to select CMake as a build tool. At first, individual build tools are evaluated in terms of scalability, conveniency, consistency, correctness, performance (in terms of speed and targets) and later, the build systems are experimented by automating the workflow by increasing the source code artifacts to evaluate the performance when there is limited user interaction. The behavior of the build systems are also tried with other third party tools like Tessy for testing purposes, Jenkins as CI server, and Polarion as requirement engineering tool to show how much effort is required to integrate third party tools with the build system in order to increase the functionality. The evaluation of the build systems is important because that will highlights the areas where potential candidates are better and where there is lack of functional specifications. Generally speaking, SCons has an advantage of being Pythonic in nature and provides the developer ease of use to specify the build configurations using programmatic skills. CMake on other hand are on top of shelves where there is no need to understanding and caring about the underlying platform and where developers want to generate the native build tool solutions which are readily available for exporting them into IDEs. Though both of the build systems has different goals, for example SCons is ready to sacrifices the performance while providing user correctness of the build while CMake focuses on generating native build tools by understanding the underlying platform. All of these types of situations are discussed with experiments in this thesis and serves as the practical guides for high level managers to decide the build tools among others. After evaluation, this thesis firstly suggests the general techniques where the bottlenecks could be covered and then build tool specific optimizations and recommendations are discussed to speed-up the development process.

This research takes a social constructivist approach to investigate the relationship between people’s perceptions of disaster risk and their responses in disaster-prone cities of the Global South. This is important because the effects of risk perceptions on the ways that people respond to disaster risk remains unclear and has been labelled ‘weak’ within the disaster studies literature. Furthermore, this lack of clarity has contributed to the marginalisation of people at risk from contributing to interventions that address disaster risk, which this research finds problematic. Therefore, a better understanding of how people perceive their risk and how this shapes their responses would help inform more effective and multi-scalar interventions to address disaster risk. The research takes place in three adjacent neighbourhoods of Cochabamba city, Bolivia. Within this ‘case site’, the house is used as a methodological tool to investigate how people’s risk perceptions shape their responses to disaster risk. In particular, the research explores how risk perceptions influence the way people design and construct self-build houses in order to reduce their risk of a disaster. The focus on housing construction represents a novel way of exploring the relationship between risk perceptions and disaster risk-reduction behaviour. The research takes place in the context of persistent, low-intensity natural hazards that are linked to disaster risk which incrementally increases over time. This marks a shift away from the many studies that investigate rapid-onset, extreme hazards that quickly overwhelm people’s capabilities and which are associated with crisis and urgency. Additionally, the research is concerned with small-scale disasters, which again marks a shift away from the disaster studies literature which principally focuses on large-scale disasters that result in many casualties, large economic loss and which affect a large geographical area. The research ultimately shows that whether a risk perception is high or low is not the most important factor; rather, it is an individual’s awareness and understanding of disaster risk that encourages long-term and anticipatory strategies that require significant investments in the house. Furthermore, the research argues that research which describes the relationship between risk perceptions and responses as ‘weak’ forecloses the nuances and complexity of human behaviour in disaster-prone contexts because it does not capture the subtle yet important ways that risk perceptions shape responses.

As the product-release cycle in the tech industry speeds up, there is more pressure on manufacturers to bring new products to market faster than ever. This puts a great deal of pressure on the suppliers of capital equipment used to manufacture these tech products. The supply chain agility of these suppliers is increasingly important. The purpose of this study is three-fold (1) to develop a methodology that can be used by any firm for measuring and ranking the agility of suppliers and finding the root causes of supplier agility, (2) to develop the first-ever fully quantitative measure of supply chain agility, and (3) to test if the supply chain management practices that are associated with agility in the academic literature are truly correlated with supply chain agility. Using the outlined methodology in this paper, the data suggest that the customer's current system and processes adequately met the need for short-notice, expedited build times. However, many processes and communications between the suppliers and customer have a lot of room for improvement that may positively impact the supply chain agility of suppliers. Since most every firm captures this same data, such as PO create dates and supplier ship dates, any firm can and should replicate this analysis to discover their suppliers' unique drivers of supply chain agility. Each supplier's historical agility was measured and ranked using historical order performance data. This agility score is the first of its kind to measure agility without the use of qualitative factors or self-reported measures of agility. Only three of the supply chain survey questions developed from or borrowed from the academic literature were correlated with supply chain agility in this study. Survey responses regarding the frequency of communication and information sharing are two examples of variables that were not associated with supplier supply chain agility. The only survey question response that was found to be positively correlated with supply chain agility involves the agile practice of delayed product differentiation. Contrary to the literature, two questions involving supplier-customer communication and the linking of order management system were found to be negatively correlated with supply chain agility. In regards to the non-survey, historical data, the independent variables that were correlated with agility highlighted the need for improved systems and processes between the suppliers and customer. Two examples of processes and systems that need improvement are expedited build time requests and PO swaps.

Tato diplomová práce popisuje úpravu průběžné integrace pro Platform tým ve společnosti Red Hat. Výsledkem práce je nástroj Metamorph, který umožní sjednocení ostatních nástrojů průběžné integrace pod týmem Platform. Teoretická část popisuje vznik, popis a přidané hodnoty průběžné integrace. Následně jsou blíže přiblíženy existující nástroje na trhu. Dále je zde popsáno použití průběžné integrace v nástroji Jenkins. V práci jsou také dopodrobna popsány existující řešení průběžné integrace ve společnosti Red Hat. Dále je zde popsán návrh a implementace výše zmíněného nástroje. V závěru jsou výsledky práce otestovány týmem z firmy Red Hat a nastíněny možnosti rozšíření.

Continuous software engineering is a rapidly growing discipline in software engineering. Among its many reported benefits is increased development velocity, faster feedback for developers, and better software quality. It also comes with its own share of challenges, most of which are centered on making automated builds more efficient or detecting problems with build configuration. However, the majority of literature in this area does not take into account software developers, which are arguably the cornerstone of software development. Software development is still a human-driven endeavour. It is a developer who writes the code, tests it, makes the final decision while factoring in the build results, and so on. Furthermore, software development does not happen in a vacuum. Development takes place within the context of practices dictating how it should be done, and perceived benefits that drive practice adoption and implementation. Software development, and by extension continuous software development, is a socio-technical endeavour that features interactions between human aspects (developers, testers, etc.), technical aspects (automation), and environmental aspects (process, project-specific characteristics, infrastructure, etc.). While the software engineering field has its share of theories, frameworks, and models, or borrows them from other fields, we still do not have a human-centric framework for software engineering that takes into account other socio-technical aspects (technical and environmental). My dissertation addresses this need for a socio-technical framework by illustrating a series of studies that ultimately resulted in the creation of a socio-technical theory of continuous software engineering that focuses on phenomena involving both humans and automation. In particular, I focus on the role of continuous software engineering tools (automation) in the software development process and how they displace existing tools, disrupt existing workflows, and feature in software developer decision making. This theory will enable further research in this area as well as allow researchers to make more grounded recommendations for industrial applications. / Graduate

This thesis is organized in three different parts. In the first part Ericsson’s methods fordeveloping and deploying the existing knowledge are analyzed. In the second part we analyzethe competence build-up for consultants within a technical domain that is constantly evolving.The third part is an evaluation, on an overview level, of a new organizational concept thatEricsson launched. The concept is a way to globally manage knowledge and competencewithin different technical domains. The concept is called Global Competence Center.The method applied was interviews, as a first step to learn about the subject and also forourselves to get to know the organization in which we conducted our research. Interviewswere also used in order to answer our research questions. The employees gave their view onwhat makes learning more efficient. Examples are hands-on, reality based and problemoriented tasks. This was combined with studies of literature and our own experiences oflearning.Our study shows that a combination of different methods for developing and deployingknowledge and building competence seems to be most suitable. This is based on theinterviewees’ experiences and the principles of a theory about adult learning called andragogy.From the interviews, we also received suggestions about work improvements for theconsultants’ work roles. A competence program was developed for the building ofcompetence amongst consultants. The program uses case studies and mentorship as two of themethods, which both apply to the theory of andragogy. / Den här rapporten är uppdelad i tre olika delar. I den första delen analyseras Ericssonsmetoder för att utveckla och sprida existerande kunskap. I den andra delen analyserar vikompetensuppbyggnaden för konsulter inom en teknisk domän som ständigt förändras. Dentredje delen är en utvärdering, på en översiktlig nivå, av ett nytt organisatoriskt koncept somEricsson har startat. Konceptet är ett sätt att hantera kunskap och kompetens inom olikatekniska domäner. Konceptet kallas för Global Competence Center.Metoden vi använde var intervjuer, som ett första steg för att lära oss ämnet men också för attlära oss organisationen som vi utförde vår studie i. Intervjuer användes också för att kunnabesvara våra frågeställningar. De anställda gav sin syn på vad som gör lärande mer effektivt.Exempel är hands-on, verklighetsbaserade och problembaserade uppgifter. Arbetetkombinerades med litteraturstudier och våra egna erfarenheter av lärande.Vår studie visar att en kombination av olika metoder, för att utveckla och sprida kunskap ochbygga kompetens, verkar vara mest lämplig. Detta är baserat på de intervjuades erfarenheteroch principerna av en teori om vuxnas lärande, kallad andragogik. Från intervjuerna fick viockså förslag på förbättringar för konsulternas arbetsroller. Ett kompetensprogramutvecklades för att bygga kompetens bland konsulter. Programmet använder case-studier ochmentorskap som två av metoderna, vilka båda drar nytta av hur teorierna om andragogiktillämpas.

Den här rapporten är uppdelad i tre olika delar. I den första delen analyseras Ericssonsmetoder för att utveckla och sprida existerande kunskap. I den andra delen analyserar vikompetensuppbyggnaden för konsulter inom en teknisk domän som ständigt förändras. Dentredje delen är en utvärdering, på en översiktlig nivå, av ett nytt organisatoriskt koncept somEricsson har startat. Konceptet är ett sätt att hantera kunskap och kompetens inom olikatekniska domäner. Konceptet kallas för Global Competence Center.Metoden vi använde var intervjuer, som ett första steg för att lära oss ämnet men också för attlära oss organisationen som vi utförde vår studie i. Intervjuer användes också för att kunnabesvara våra frågeställningar. De anställda gav sin syn på vad som gör lärande mer effektivt.Exempel är hands-on, verklighetsbaserade och problembaserade uppgifter. Arbetetkombinerades med litteraturstudier och våra egna erfarenheter av lärande.Vår studie visar att en kombination av olika metoder, för att utveckla och sprida kunskap ochbygga kompetens, verkar vara mest lämplig. Detta är baserat på de intervjuades erfarenheteroch principerna av en teori om vuxnas lärande, kallad andragogik. Från intervjuerna fick viockså förslag på förbättringar för konsulternas arbetsroller. Ett kompetensprogramutvecklades för att bygga kompetens bland konsulter. Programmet använder case-studier ochmentorskap som två av metoderna, vilka båda drar nytta av hur teorierna om andragogiktillämpas. / This thesis is organized in three different parts. In the first part Ericsson’s methods fordeveloping and deploying the existing knowledge are analyzed. In the second part we analyzethe competence build-up for consultants within a technical domain that is constantly evolving.The third part is an evaluation, on an overview level, of a new organizational concept thatEricsson launched. The concept is a way to globally manage knowledge and competencewithin different technical domains. The concept is called Global Competence Center.The method applied was interviews, as a first step to learn about the subject and also forourselves to get to know the organization in which we conducted our research. Interviewswere also used in order to answer our research questions. The employees gave their view onwhat makes learning more efficient. Examples are hands-on, reality based and problemoriented tasks. This was combined with studies of literature and our own experiences oflearning.Our study shows that a combination of different methods for developing and deployingknowledge and building competence seems to be most suitable. This is based on theinterviewees’ experiences and the principles of a theory about adult learning called andragogy.From the interviews, we also received suggestions about work improvements for theconsultants’ work roles. A competence program was developed for the building ofcompetence amongst consultants. The program uses case studies and mentorship as two of themethods, which both apply to the theory of andragogy.

京都大学 / 0048 / 新制・課程博士 / 博士(工学) / 甲第21724号 / 工博第4541号 / 新制||工||1708(附属図書館) / 京都大学大学院工学研究科社会基盤工学専攻 / (主査)教授 中川 一, 教授 平石 哲也, 准教授 川池 健司 / 学位規則第4条第1項該当 / Doctor of Philosophy (Engineering) / Kyoto University / DFAM