In larger developments, a use of configuration management is crucial; the company UIQ Technology is no exception. The configuration management method controls how the flow within a software developer should go, so the configuration management method and code complexity is something that works affects each other. Therefore, you might be able to combine multiple configuration methods to try to use the best from each method to decrease code complexity. That is the goal of this thesis, to see if the COTS, Single repository or Component Based could combine with the UIQ method to decrease code complexity. This have been tested through theoretical use cases for each method and the conclusion of the study is that, Single repository and Component Based works best in the UIQ method. However, COTS is not suited for the UIQ method because of the need of secrecy for large parts of the UIQ platform. UIQ wants to do as much as possible in-house, rather than give it out to other third-party companies that they are not in absolute need of. Some improvements have been achieved throughout Single repository, that the other third-parties companies needs to be upto- date before starting development, that is something that have not been valued before.

Att hantera förändringar av mjukvara via pappersdokument är långt ifrån effektivt. CMDB, Configuration Management Database, är ett mindre känt verktyg som på ett mycket enkelt sätt kan hantera hela företagets IT-miljö. Trots att det anses fördelaktigt enligt referenslitteraturen är det väldigt få företag som väljer att införa det. Syftet med studien är att studera vilka effekter som uppstår hos en driftavdelning efter införande av en CMDB. Studien är en fallstudie. För att få med ett så brett perspektiv som möjligt påbörjades studien innan det fanns en CMDB på fallföretaget, för att sedan fortsätta med införande och driftsättning av CMDB och till sist utvärderingen av effekter efter driftsättning. Studien är en kvalitativ undersökning som med hjälp av enkäter som främsta datainsamlingsmetod utrett vilka effekter som drifttekniker noterar efter införandet. Studien har kommit fram till att förutsättningarna för införandet var tillräckliga. Införandet enligt rekommendationer i ITIL, Information Technology Infrastructure Library, var enkelt att genomföra och resultatet blev positivt. Det senare visar sig genom följande effekter som belagts 1-3 månader efter driftsättningen att alla respondenter märkt av effekterna kostnadskontroll, informationskällor, spårbarhet, komponentbaserat arbetssätt, riskbedömning och arbetsprocesser. Respondenterna fick inte alla sina förväntningar uppfyllda, men däremot underlättade CMDB hanteringen av incidents, changes och problems.

Change is inevitable when software is built and deployed. It’s not particularly problematic to manage change if there is just one system. But in a large global IT organization, with several systems and people who develop, problems may arise. If organizations don’t control change, change will control the organization. Software Configuration Management (SCM) is a set of activities to manage change by identifying objects that are likely to change, establishing relationships among them, managing different versions of the objects, controlling the changes imposed and reporting on the changes made. A way to support the work of SCM is to follow standards. A standard can be compared to a type of rule, but also a directive. In this study we examined how a multinational organization applies standards within SCM. We examined the challenges with applying standards. We also examined whether there are deviations from standards, and in such cases why did the deviations arise and what are the following consequences? The study is based on a qualitative case study that employed interviews with developers, IT architects, operations manager and solution leader. The result of this study shows that some of the challenges in applying standards within SCM are: legacy systems, globalization, CMDB and ITSM-related tools (and their processes). The study also shows that standardization within maintenance is complex and that it’s easily breach and forgotten. The study shows that the consequence of this is that the developers must constantly compromise with standards. The result of this compromise is that it’s possible to carry out the business, but the solutions may not meet standards. In this study we concluded that the organization need to direct more attention towards maintenance, and less on new development.

My thesis is aimed at the problems of Configuration Management. Configuration Management is part of managing of information science management. Being part of it, it is very well described in different methodologies aimed at management of information science. Configuration Management is concerned with monitoring of company assets. In information technology it means mainly hardware and software equipment which is being used by the company. Knowledge of exact configurations of all these assets is very important mainly for providing user support, deploying new implementations or running audits. Situation in companies dealing with IT is, that many of such companies do not use Configuration Management at all, on a limited scale or are using some substitute method. Management of these companies usually realizes that it would be good to somehow align problems aligned with using of larger quantities of hardware and software. Often it is a situation when company does not use any methodologies for IT management and thus does not know that something like Configuration Management even exists. Goal of my thesis is to help future users of Configuration Management. I am trying to achieve this goal by analyzing particular components of Configuration Management complemented by my work experiences - I have been engaged in Configuration and Change Management during the majority of the last three years.

The transfer of information between the different phases of construction projects is limited, which complicates the quality assurance of configurations. Functional requirements on the building configuration are often ambiguous and lack measurable acceptance criteria. Vaguely described criteria provide an insufficient basis for the design and verification acceptance values. The contractor is often the first to consider the feasibility just before or during the production phase. However, feasibility including production methods should be considered with the establishment of each design solutions. Costs or time consequences are often the basis for change decisions, while the investigations of the impact on the building configuration and functionality are insufficient. A continuous flow of information with functional requirements as a controlling factor is required to control configurations. Functionality that ensure high quality patient care are essential in health care facilities, therefore the control of the configurations are particularly important. This licentiate thesis shows how configuration information in healthcare construction projects can ensure necessary building functionality. The following information areas are identified as necessary for control of configurations: function, verification, design solution, production and change control. All information is related and changes in one area affect the others, directly or indirectly during construction projects. The studies that are the basis of this licentiate thesis show that the management of configuration information was deficient in healthcare construction projects, especially regarding availability and interconnectivity. In addition, the information was not available at the right time during the construction process, which impaired configuration control. For example, verification methods were not available until the end of production. This precluded verification of intended functionality through large parts of the construction project. Detailed change information from digital models of buildings can significantly improve control of configurations, but this requires standardisation of input data. In the manufacturing industry, configuration management is practised to ensure that products fulfil the required functions throughout their entire lifecycle. Development of new technologies, such as digital processes and industrialised construction, require that construction projects develop working processes similar to those of the manufacturing industry. The risk of unnecessary rework with subsequent cost increases, delays and environmental impact decrease with increased control of the configuration. In construction projects, systematic management of configuration information can ensure delivery of healthcare facilities with intended functionality. / Överföringen av information mellan de olika faserna i byggprojekt är ofta begränsad, vilket försvårar kvalitetssäkring av utformningen. De funktionella kraven på byggnadens utformning är ofta tvetydiga och saknar mätbara acceptanskriterier. Det ger en otillräcklig grund för projekteringslösningarnas och verifieringsmetodernas acceptansvärden. Möjligheten att färdigställa en utformning övervägs ofta av entreprenören precis före eller under produktionsfasen, men bör säkerställas för varje projekteringslösning. Beslut gällande ändringar baseras ofta på kostnads- eller tidskonsekvenser, medan utredningar av hur byggnaders utformning och påverkas är otillräcklig. Ett kontinuerligt informationsflöde med funktionella krav som styrande faktor krävs för att kontrollera utformning. Kvaliteten på patientvården måste säkerställas i vårdbyggnader, därför blir kontroll av utformningen är särskilt viktig. Denna licentiatuppsats visar hur utformningsinformation i vårdbyggnadsprojekt kan säkerställa anläggningens funktionalitet. Följande informationsområden identifieras som nödvändiga för kontroll av utformningen: funktion, verifiering, designlösning, produktion och ändringskontroll. Information gällande utformningen av en byggnadsdel är relaterad och ändringar inom ett område påverkar de andra, direkt eller indirekt under ett byggprojekt. Studierna som ligger till grund för denna licentiatuppsats visar att det finns brister inom alla områden av utformningsinformation, speciellt gällande tillgänglighet och sammankoppling. Kontroll av utformningen försvårades dessutom av att informationen inte var tillgänglig vid rätt tidpunkt under byggprocessen. Verifieringsmetoder fanns till exempel inte tillgängliga förrän i slutet av produktionen. Det försvårar säkerställandet av avsedda utformning genom stora delar av projektet. Detaljerad information från digitala byggnadsmodeller kan förbättra kontrollen av vårdbyggnaders utformning, men det kräver standardisering av indata. Tillverkningsindustrin utövar konfigurationsledning för att säkerställa att produkters utformning motsvarar kravställda funktioner genom hela deras livscykel. Utvecklingen av nya tekniker, såsom digitala processer och industriell produktion, kräver att byggprojekt utvecklar arbetsprocesser som liknar de i tillverkningsindustrin. Risken för onödiga omarbetningar med efterföljande kostnadsökningar, förseningar och miljöpåverkan minskar med ökad utformningskontroll. Systematisk hantering av utformningsinformation i vårdbyggnadsprojekt kan säkerställa att leveransen uppfyller avsedd funktionalitet. / <p>QC 20201002</p>

DevOps is a collaborative effort based on a set of practices and cultural values developed in order to improve software quality and release cycle while operating at the lowest cost possible. To enable DevOps principles such as automation, collaboration, and knowledge sharing, Continuous Delivery and Deployment, as well as Infrastructure as Code are heavily employed throughout the whole process of software development. One of the main building blocks of this process is a development environment where the application code is being developed and tested before it is released into production. This research investigates with the help of a systematic literature review the DevOps perspective regarding provisioning and deployment of a development environment in a controlled, automated way, specifically the benefits and challenges of this process.

No description available.

Doctor of Philosophy / Department of Computing and Information Sciences / Xinming (Simon) Ou / Enterprise network security management is a vitally important task, more so now than ever before. Networks grow ever larger and more complex, and corporations, universities, government agencies, etc. rely heavily on the availability of these networks. Security in enterprise networks is constantly threatened by thousands of known software vulnerabilities, with thousands more discovered annually in a wide variety of applications. An overwhelming amount of data is relevant to the ongoing protection of an enterprise network. Previous works have addressed the identification of vulnerabilities in a given network and the aggregated collection of these vulnerabilities in an attack graph, clearly showing how an attacker might gain access to or control over network resources. These works, however, do little to address how to evaluate or properly utilize this information. I have developed a comprehensive approach to enterprise network security management. Compared with previous methods, my approach realizes these issues as a uniform desire for provable mitigation of risk within an enterprise network. Attack graph simplification is used to improve user comprehension of the graph data and to enable more efficient use of the data in risk assessment. A sound and effective quantification of risk within the network produces values that can form a basis for valuation policies necessary for the application of a SAT solving technique. SAT solving resolves policy conflicts and produces an optimal reconfiguration, based on the provided values, which can be verified by a knowledgeable human user for accuracy and applicability within the context of the enterprise network. Empirical study shows the effectiveness and efficiency of these approaches, and also indicates promising directions for improvements to be explored in future works. Overall, this research comprises an important step toward a more automated security management initiative.

Este trabalho investiga a integração entre a gestão de itens da WBS de projetos e os itens da configuração de produtos, visando um acompanhamento mais eficiente de projetos de desenvolvimento de produto. Trata-se de uma pesquisa-ação na qual se propôs um modelo de interface entre sistemas de gestão de projetos e sistemas de gestão de configuração e empreendeu-se uma análise de sua aplicação em uma empresa de desenvolvimento de software. A interface define um mecanismo para apurar o trabalho desenvolvido, a partir das alterações dos itens da configuração e, através do relacionamento entre estes itens e os pacotes de trabalho da WBS, exportar as informações sobre início, término e trabalho realizado para as respectivas atividades do projeto. O seu objetivo é auxiliar o acompanhamento em projetos complexos, seja com um grande número de atividades, ou aqueles realizados por consórcios de empresas. São apresentados os conceitos básicos sobre gerenciamento de projetos e gerenciamento da configuração do produto; além dos processos, atividades relacionadas e análise comparativa entre os sistemas de gerenciamento existentes. Os resultados obtidos foram: um levantamento dos principais problemas relacionados com a relação entre sistemas de gestão de projetos e de gestão de configuração, uma lista de requisitos para a integração destes sistemas, a definição e modelagem de uma interface que apóie esta integração e um exemplo prático de aplicação da interface proposta. / This work performs an investigation about the WBS and product configuration items, aiming to improve the tracking activity during the project management effort. It is an action research in witch was proposed a model to integrate project management and configuration management systems and was analyzed this model through the application in a specific software development company. The interface defines a way to identify the project work from the configuration item changes at change management application and review information about start, finish and performed work at project management ones. In challenger project’s, involving to much activities or complex enterprise clusters, tracking is a complex activity because it is dependent to the capacity to measure all project results. This work presents the basic concepts about project management and configuration management, the activities related to these topics, and project management software evaluations. The results are: an study of the problems and requirements related with the WBS and configuration items integration; requirements for this kind of application; the design of an interface to support the integration of the traditional and simple project management and configuration management applications; and a practical example to the use of this interface.

As atividades de controle de versões são consideradas essenciais para a manutenção de sistemas de computador. Elas começaram a ser realizadas na década de 1950 de forma manual. As primeiras ferramentas de controle de versões, que surgiram nos anos setenta, não evoluíram significativamente desde sua criação e, até hoje, o controle de versões de arquivos é geralmente realizado em arquivos ou mesmo módulos completos, utilizando os conceitos que foram lançados há mais de três décadas. Com a popularização da utilização de sistemas computacionais, ocorreu um sensível aumento no número de sistemas existentes e, também, na complexidade dos mesmos. Além disso, muitas alterações ocorreram nos ambientes de desenvolvimento de software, e existe demanda por sistemas que permitam aos desenvolvedores ter cada vez mais controle automatizado sobre o que está sendo desenvolvido. Para isso, algumas abordagens de controle de versões refinados para artefatos de software foram propostas, mas, muitas vezes, não oferecem a exibilidade de utilização exigida pelos ambientes de desenvolvimento de software. Neste trabalho, é apresentado um sistema que visa a fornecer suporte ao controle de versões refinado e flexível para artefatos de software, tendo por base um modelo bem definido para representação das informações da estrutura dos arquivos que compõem determinado projeto de software, sejam eles código-fonte dos programas de computador, documentação criada em Latex, arquivos XML, entre outros. O sistema apresentado foi projetado para ser integrado com outras soluções utilizadas em ambientes de desenvolvimento de software / Version control tasks are considered essential for the maintenance of computers systems. They have been done since beginning of 50\'s in a by hand manner. First tools, which were released in 70\'s, didn\'t evolve significantly since its creation, and, in general, version control systems still work with entire files or even modules of software, having the same concepts that were launched more than three decades ago. With the popularization of computers systems there had been a sensible increase in the number of existing systems and also in the complexity of these systems. Besides that many changes have taken place in the software development environments, and there is demand for systems which allow developers to have more automated control about what is being developed. Regard to this demand some approaches of fine-grained version control have been proposed, but they usually do not provide the required exibility for its use in the real software development environments. In this work its presented a system which aims at providing support for exible and fine-grained version control of software artifacts, using a well defined model to represent the logical structure of the files which compose a software project, independently of its type - they can be XML files, source-code files, Latex files and others. The system has been designed to be integrated with other software solutions used in software development environments