<p>Det finns ett problem med att filbaserade databaser inte klarar av att hantera konsistens i form av de beroenden som existerar i databasen. Här har detta problem undersökts utifrån de uppdateringar som sker när indata och datadefinitioner på nytt, efter eventuell uppdatering, genereras in i databasen.</p><p>Olika typer av beroenden har identifierats i databasen och testexempel har valts ut bland befintliga datadefinitioner och indatafiler i det system som används som exempelsystem. Möjligheten att använda en wrapper för att hantera konsistensen har undersökts och denna wrapper har placerats in i arkitekturen för exempelsystemet. Tester har genomförts för främmande nycklar och funktionaliteten add, lägga till ny data. Vid tester kan konstateras att de flesta främmande nycklar antingen identifieras av programmet eller de kan identifieras via ytterligare implementation.</p>

Det finns ett problem med att filbaserade databaser inte klarar av att hantera konsistens i form av de beroenden som existerar i databasen. Här har detta problem undersökts utifrån de uppdateringar som sker när indata och datadefinitioner på nytt, efter eventuell uppdatering, genereras in i databasen. Olika typer av beroenden har identifierats i databasen och testexempel har valts ut bland befintliga datadefinitioner och indatafiler i det system som används som exempelsystem. Möjligheten att använda en wrapper för att hantera konsistensen har undersökts och denna wrapper har placerats in i arkitekturen för exempelsystemet. Tester har genomförts för främmande nycklar och funktionaliteten add, lägga till ny data. Vid tester kan konstateras att de flesta främmande nycklar antingen identifieras av programmet eller de kan identifieras via ytterligare implementation.

Information Technology has taken a larger focus in today’s society and become a more centralized part of IT-organizations and other businesses. The traditional management models for manufacturing and production has become harder to apply in the software lifecycle. This is since the software no longer is produced and launched with no follow-up. Today’s IT- organization needs to continuously handle, operate and maintain their software. In recent years a new philosophy has emerged within the IT community, DevOps. DevOps aims to erase the silos built-in to the business to become a more efficient and optimized organization regarding their software delivery. This exploratory case study has been conducted at the Swedish Governmental Employment Services IT-department. It aims to expand the existing knowledge base regarding DevOps and the aspects of the organizational culture the philosophy claims. This study aims to investigate how organizations work while trying to introduce a DevOps culture. The potential difficulties an organization could face in relation the organizational culture described for DevOps, seen as a management model, will also be a focus of this study. In-depth interviews and observations have been conducted with the employees at the named IT-department in order to analyze and create an overview of the current culture in the department. The study has shown new angles regarding financial and resource management, dependencies between teams and the importance of an existing leadership. New perspectives have also been provided towards organizational change. Key Words: DevOps, Organizational Culture, Organizational Change, Leadership, Dependencies, IT-organizations, Communication, Information, Team, Silos, Self-Leadership

Genom arkeologins historia har skepp studerats som symboler för makt, status och krig. Även om skeppen studerats väldigt mycket inom dessa aspekter har relationerna och nätverken runt skeppens produktion och underhåll fallit i skymundan. Målet med uppsatsen är därför att studera dessa relationer ur ett holistiskt perspektiv, och att försöka tolka hur dessa relationer i sin tur påverkat skeppets roll i gravsammanhang genom att använda Osebergsskeppet som grund för studien. Tidsramen som satts är yngre järnålder, detta för att kunna tolka skeppens symboliska värde effektivt. För att göra det immateriella greppbart används entanglement-teori, och kvantitativa uträkningar för naturliga- och mänskliga resurser används som hjälpmedel för detta. Studien visar att allt rörande skeppet är intrasslade med varandra, och att en kollektiv agens av samhället var nödvändig för produktion och senare underhåll av skeppen. Skeppens symboliska värde är också format av dessa relationer, och det är möjligt att det är dessa relationer som lett till skeppens roll i gravseden under perioden. / For much of the history of archaeology ships have been studied as symbols for power, wealth, and warfare. Even though viking-age ships have been studied immensely in these regards the relationships and the network of organization around the construction and maintenance have not received as much attention from archaeologists. The aim of this essay is therefore to study these relationships in a holistic view, and to try to interpret how these relationships affected the ships’ place in the funerary sphere using the Oseberg ship as the basis for this study. The timeframe for the study is set to late iron-age since the study of symbolism needs a longer timeframe to be interpreted effectively. To get the intangible to become tangible the entanglement theory is applied, and quantitative estimations on natural- and human resources are used as support to do so. The study shows that everything surrounding the ship is entangled, and that a collective agency of the communities was necessary for the production and maintenance of the ships. The symbolic meaning of the ship is also formed by these relationships, and that it might be these relationships that gave the ships a place in the funerary sphere during the period.

I varje projekt finns det brister i kommunikation som kan leda till att kostnad, tid och kvalitét påverkas. Varje projekt är en tillfällig organisation med olika företag och olika personer med varierande erfarenheter inom projektering. Detta medför att varje projekt är i sig unikt och hur alla ska kommunicera med varandra kan vara stora frågetecken under projekteringens förlopp. Denna rapport tittar närmare på vilka brister och svårigheter som kan uppkomma i projekteringskedet.

Companies are constantly challenged to maintain but also to expand their market position. According to a study it’s problematic to carry out successful IT-projects. Dependencies, coordination and long term planning are three factors which has shown are difficult to master in bigger projects. The aim with the study is to in- vestigate how these aspects work in one case, through a case study on an IT com- pany. The goal is to contribute with research to the subject of long term planning in IT-projects where agile methods usually is used today. Previous research and theories as project management, agile project management, planning methods, scaling methods, coordination methods and change management are used as a base for the study. An exploratory qualitative study has been performed at the case company, the generated result composes of interviews with personnel from the company. The result showed how the methods and theories where used in the case company mainly focusing on long-term planning and workflows. Generally, the same thoughts where shared among the personnel, but because of the open questions the responder got encouraged to elaborate and explain their opinion leading to new information and aspects even when they agreed on the topic. When analyzing the result, I show that a clear framework, implementing of sim- ple work methods and the project management were all important to be able to conduct long-term planning and handle dependencies in projects. The conclusion was to implement the scaling method SAFe but also to use coordination methods. An important aspect is to include change management processes and theories when implementing or changing something. Further studies suggest that research in this article should be carried out on more companies and studies if the imple- mentation of the agila scaling method SAFe has a positive effect in a company. / Varje dag utmanas företag för att bibehålla men även utöka deras marknadspo- sition. Enligt en studie så är det problematiskt att genomföra lyckade IT-projekt. Beroenden, koordinering och långsiktig planering är tre faktorer som det visat sig vara svårt med i större projekt. Syftet med studien är att undersöka hur dessa aspekter fungerar på ett visst fall, genom en fallstudie på ett IT-företag. Målet är att kunna bidra med forskning till ämnet gällande långsiktig planering i IT-pro- jekt där agila metoder vanligtvis idag används. Tidigare forskning och teorier som projektledning, agil projektledning, planeringsmetoder, skalningsmetoder, koordineringsmetoder samt förändringsledning ligger till grund för studien. En explorativ kvalitativ studie har genomförts på fallföretaget. Det genererade re- sultatet baseras på intervjuer med personal på företaget. Resultatet visade hur det fungerade på fallföretaget gällande långsiktig planering och arbetssätt. I stora drag framfördes liknande tankar och åsikter, men då de ställda frågorna var öppet ställda så framkom även olika nyanser och delar från de olika respon- denterna. Analysen av resultatet visade att tydligare ramverk, implementering av arbetssätt och ledning var viktiga för att kunna planera långsiktigt och han- tera beroenden. Slutsatsen som drogs var att implementera skalningsmetoden SAFe men också använda sig av koordineringsmetoder. En viktig aspekt att inte förglömma är även förändringsarbetet vid införandet eller förändring av något. För vidare forskning skulle studien kunna göras på fler företag och även en stu- die på implementeringen av den agila skalningsmetoden SAFe skulle kunna gö- ras för att se om det skulle ge en positiv effekt för företaget.

Software companies often choose to develop in C++ because of the high performance that the language offers. Facilitated by static compilation and powerful optimization options, runtime performance is paid for with compilation time. Although the trade-off is inevitable to some extent, building very large C++ programs from scratch can take up to several hours if extra care is not taken during development. This thesis analyzes compilation times for C++ programs and shows how they can be reduced with the help of design patterns, implementation hiding, and framework related fixes. The results presented prove that compilation times can be decreased significantly with no drawbacks to the maintainability of a program. An in-depth analysis of compilation times and dependencies has been conducted for two large software modules from a representative company. Both modules take over an hour of CPU time each to compile. The time consumption for different compiler activities, such as parsing, preprocessing, and runtime optimization tasks have been measured for the modules. The compilation times for unit tests and mocks which use the GoogleTest framework have been analyzed. A simple method that may reduce compilation times by up to 50% for programs that use GoogleTest is presented. A dependency metric has been created, based on the number of include statements found recursively throughout a program. The dependency metric was found to be connected to compilation time for the two analyzed modules. Other factors that can influence compilation times are also shown, such as runtime optimization options, and the use of templates. Experiments which show how a typical usage of templates can drastically increase compilation times are presented. In addition, a solution which allows templates to be used while avoiding code bloat across translation units is reviewed. The solution effectively rivals non-template code in terms of compilation time. The Pointer to Implementation (PImpl) and Dependency Injection design patterns have been used to refactor a small program. Both design patterns performed well, reducing the total compilation time and total compiler memory usage by 70%. A program that detects dependency cycles has been created, but no cycles were found in any of two modules from the representative company.

Product development is more complex than ever. Industries all over the world face intensified competition, forcing firms to improve their innovation performance. This involves integrating software development to a greater extent. As an effort to cope with such progression, agile project management methodologies have been adopted. These include methodologies that are tailored to fit large organisations, made to enhance communication and speed up decision-making. Moreover, such methodologies allocate time for joint planning sessions (such as Program Increment Planning) to foster coordination between teams. The need for extensive coordinating capabilities increases with firm size and product complexity, meaning that large, multinational manufacturers with integrated software- and hardware development face the greatest challenges. With difficult coordination challenges comes a demand for prominent organisational coordination capabilities. This includes capabilities to identify dependencies between agile teams in time, to avoid delays, budget overruns, and quality issues. Hence, firms must adopt sufficient project management procedures, as well as shape organisational artefacts, processes, and culture to maximise their organisational coordination capabilities. In this project, these artefacts, processes, and the organisational culture were defined as factors. Furthermore, the project aimed at (1) – identifying factors that positively contribute to organisations’ capabilities to find inter-team dependencies, and (2) – investigating how to favour those identified factors. The research was conducted at Volvo Car Corporation, a Swedish car manufacturer that undergoes a transition towards being a large-scale agile organisation. Theories concerning coordination, communication, and knowledge management were jointly deployed to construct a state-of-the-art theoretical framework. Thereafter, the conceptual model was the guiding lens for collecting and analysing empirical evidence. Consequently, this project was able to assess 26 factors for identifying inter-team dependencies. Furthermore, several of these factors are proven to be interconnected as they fuel each other and exist in symbiosis. Thus, this project advocates that large-scale agile organisations must understand these factors and their connection to each other — that is when incorporating coordination mechanisms to better identify inter-team dependencies.