Abstract The objective of this research is to develop a greater understanding of the career development of software developers in different generations. This research applies qualitative method by using intensive interviews to form the propositions and put forward the proposals. There are two groups, the first group is referred to the software developers over 40 years of age (includes 40) and the second group is referred to the ones between 30 and 40 years old. The study concluded six propositions. First, the reasons why software developers want to work in Software Industry. Second, the time when they start to study the professional skills in information technology. Third, the timing for software developers is working in Software Industry. The forth, what is really reason they change their careers from Research and Development to management. Fifth, they are many different ideas when they choice to organizations scale. Six, the domination of the career development is very different. The detail results listed below as¡G 1.The reasons between two groups entering in Software Industry are similar, but there are difference between the graduate courses and non-undergraduate courses. 2.The timing both for undergraduate courses and non-undergraduate courses in two group starts to study the professional skills in information technology is similar but the location is slightly different. 3.The timing of entering in Software Industry between two groups is dissimilar. 4.The reasons for software developers that changed their careers from software research and development to management between groups one and groups are slide swift. 5.The choices of the organizations scale between groups one and groups two are various. 6.The domination of the career development between groups one and groups two are different.

Det har sedan 2019 varit lagkrav att offentliga webbplatser i Sverige skall uppfylla viss nivå av digital tillgänglighet. När den här studien publiceras ska ytterligare EU-direktiv bli nationell lag, vilket kommer att innebära att även privata aktörer berörs av motsvarande krav, däribland banktjänster och e-handeln. Detta kommer att innebära ökade krav som leverantörer och deras utvecklare behöver kunna möta.  Målen med studien är att skapa en medvetenhet om digital tillgänglighet och tydliggöra, utifrån utvecklarens perspektiv, hur man arbetar för att uppnå denna grad av tillgänglighet och vad som behövs för att mer effektivt tillämpa digital tillgänglighet.  För att åstadkomma detta har en kvalitativ intervjustudie genomförts. Totalt åtta intervjuer har genomförts, som sedan har transkriberats och tematiserats i resultatavsnittet. En induktiv tematisk analys är genomförd utifrån forskningsfrågorna. Den jämför tidigare resultat mot utfall från undersökningen och visar tydligt på likheter men även skillnader och nya upptäckter. Av undersökningen framgår att utvecklare har tillgång till utvärderingsverktyg och riktlinjer som ger ett gott stöd i arbetet, men att ansvaret ofta ligger på enskilda utvecklare snarare än på verksamheten som helhet. Detta är en av de största utmaningarna, tillsammans med att det fortfarande utvecklas otillgängligt parallellt och att tidspress gör att tillgänglighet kan prioriteras ned. Respondenterna är dock överens om att det inte tar längre tid att utveckla tillgängligt än otillgängligt, förutsatt att det tas i beaktande från början. Framgångsfaktorer i arbetet är att sälja in tillgänglighet till kunden, att arbeta strukturerat med kunskapsdelning och att dokumentera lösningar för att spara tid. Utöver detta framgår att tillgänglighetsfrågan skulle vinna på att ägarskapet lyfts till en högre beslutsnivå och kompetensen breddas i leverantörens organisation, samt att utvecklare får tillgång till specialistkompetens och användartester som stöd i arbetet. En grundkunskap om tillgänglighet skulle kunna inkluderas i webbutvecklingsutbildningar i större utsträckning, och en utökning av lagkraven skulle kunna skapa ytterligare incitament hos kunden. / Since 2019, all public websites in Sweden are legally bound to meet a certain degree of digital accessibility. An additional EU directive is being transposed into national law at the time of publication of this thesis, which will impose corresponding requirements on part of the private sector, such as banking services and e-commerce. This will likely cause increased demand which suppliers of web development and, in turn, their developers must be able to meet.  The aims of this study are to create an increased awareness of digital accessibility as well as to clarify, from the developer’s perspective, how this degree of accessibility is achieved and what could make application of digital accessibility more efficient.  In order to achieve this, eight qualitative interviews were conducted, transcribed and thematized in the results section. An inductive thematic analysis has been carried out related to the research questions. It compares the results of previous studies with the outcomes from this study, and shows clear similarities but also differences and new discoveries.  The study shows that developers have access to evaluation tools and guidelines that provide good support in their work, but that the responsibility often lies with individual developers rather than with the business as a whole. This is one of the main challenges, together with the fact that inaccessible development is still being carried out in parallel, and that time pressure leads to deprioritization of accessibility. However, the respondents agree that it does not take any more time to develop accessible rather than inaccessible websites, provided that this is taken into account from the outset. Success factors for digital accessibility are to sell the idea to the customer, to work in a structured way with knowledge sharing and to document solutions in order to save time. In addition to this, it appears that the implementation of accessibility would benefit from the ownership being raised to a higher decision level and the competence being broadened in the supplier's organization, and that developers gain access to specialist competence and user tests to support their work. A basic knowledge of accessibility could be included in web development training to a greater extent, and an extension of the legal requirements could also create additional incentives for the customer.

Um die dezentrale Kommunikation zwischen Beratern und Softwareentwicklern zu verbessern, entschied sich die Saxonia Systems AG zum Test des Microblogging-Dienstes Yammer. Nach nur vier Wochen waren bereits 89 Anwender im System aktiv, die 1.391 Postings verfasst hatten. Die Evaluation durch eine Online-Nutzerbefragung zeigte die prinzipielle Tauglichkeit und Akzeptanz, aber auch die derzeitigen Grenzen von Microblogging auf.

Made available in DSpace on 2014-12-17T15:48:07Z (GMT). No. of bitstreams: 1 DanielAC_DISSERT.pdf: 1379221 bytes, checksum: 4e8ab78d03e452eecd9c3eaa6906e4ee (MD5) Previous issue date: 2013-02-01 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / Software Repository Mining (MSR) is a research area that analyses software repositories in order to derive relevant information for the research and practice of software engineering. The main goal of repository mining is to extract static information from repositories (e.g. code repository or change requisition system) into valuable information providing a way to support the decision making of software projects. On the other hand, another research area called Process Mining (PM) aims to find the characteristics of the underlying process of business organizations, supporting the process improvement and documentation. Recent works have been doing several analyses through MSR and PM techniques: (i) to investigate the evolution of software projects; (ii) to understand the real underlying process of a project; and (iii) create defect prediction models. However, few research works have been focusing on analyzing the contributions of software developers by means of MSR and PM techniques. In this context, this dissertation proposes the development of two empirical studies of assessment of the contribution of software developers to an open-source and a commercial project using those techniques. The contributions of developers are assessed through three different perspectives: (i) buggy commits; (ii) the size of commits; and (iii) the most important bugs. For the opensource project 12.827 commits and 8.410 bugs have been analyzed while 4.663 commits and 1.898 bugs have been analyzed for the commercial project. Our results indicate that, for the open source project, the developers classified as core developers have contributed with more buggy commits (although they have contributed with the majority of commits), more code to the project (commit size) and more important bugs solved while the results could not indicate differences with statistical significance between developer groups for the commercial project / Minera??o de Reposit?rios de Software (MSR) ? uma ?rea que procura analisar reposit?rios de software em busca de informa??es relevantes para a pesquisa e para a pr?tica na engenharia de software. As minera??es buscam transformar informa??es est?ticas de reposit?rios de software (sistemas de ger?ncia de configura??o e mudan?as) em informa??es relevantes que auxiliam a tomada de decis?o dentro do contexto de projetos de software. Por outro lado, a ?rea de Minera??o de Processos (MP) busca descobrir caracter?sticas dos processos que s?o utilizados em organiza??es para auxiliar na melhoria e documenta??o destes processos. Trabalhos recentes t?m buscado utilizar as t?cnicas de MSR e de MP para realizar diversas an?lises na ?rea de Engenharia de Software, tais como: (i) estudar a evolu??o dos projetos de software (ii) entender o processo de software real utilizado em um determinado projeto; e (iii) criar modelos de predi??es de defeitos. Contudo, poucos destes trabalhos buscam utilizar as t?cnicas de MP e MSR com o objetivo de analisar a contribui??o de desenvolvedores na implementa??o de sistemas de software. Esta disserta??o de mestrado prop?e a condu??o de estudos experimentais que buscam avaliar a contribui??o de desenvolvedores de software para projetos, atrav?s da utiliza??o das t?cnicas de MSR e MP. A contribui??o dos desenvolvedores ? avaliada sob tr?s diferentes perspectivas: (i) commits defeituosos; (ii) tamanho dos commits; e (iii) resolu??o de bugs priorit?rios. Dois projetos de software (um open-source e outro privado) foram analisados sob estas tr?s perspectivas. Para o projeto open-souce, 12.827 commits e 8.410 bugs foram avaliados, enquanto que para o projeto privado, 4.663 commits e 1.898 bugs foram avaliados. Os resultados obtidos indicam que para o projeto open-source os desenvolvedores classificados como desenvolvedores core, s?o os que mais produzem commits defeituosos (embora tamb?m sejam os que mais produzem commits), s?o os que contribuem com commits de maior tamanho de c?digo e tamb?m contribuem com mais bugs priorit?rios solucionados. J? para o projeto privado, os resultados n?o indicaram uma diferen?a estatisticamente significativa entre os grupos de desenvolvedores

Um die dezentrale Kommunikation zwischen Beratern und Softwareentwicklern zu verbessern, entschied sich die Saxonia Systems AG zum Test des Microblogging-Dienstes Yammer. Nach nur vier Wochen waren bereits 89 Anwender im System aktiv, die 1.391 Postings verfasst hatten. Die Evaluation durch eine Online-Nutzerbefragung zeigte die prinzipielle Tauglichkeit und Akzeptanz, aber auch die derzeitigen Grenzen von Microblogging auf.

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)