Endre søk
Begrens søket
1234 151 - 171 of 171
RefereraExporteraLink til resultatlisten
Permanent link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Treff pr side
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sortering
  • Standard (Relevans)
  • Forfatter A-Ø
  • Forfatter Ø-A
  • Tittel A-Ø
  • Tittel Ø-A
  • Type publikasjon A-Ø
  • Type publikasjon Ø-A
  • Eldste først
  • Nyeste først
  • Skapad (Eldste først)
  • Skapad (Nyeste først)
  • Senast uppdaterad (Eldste først)
  • Senast uppdaterad (Nyeste først)
  • Disputationsdatum (tidligste først)
  • Disputationsdatum (siste først)
  • Standard (Relevans)
  • Forfatter A-Ø
  • Forfatter Ø-A
  • Tittel A-Ø
  • Tittel Ø-A
  • Type publikasjon A-Ø
  • Type publikasjon Ø-A
  • Eldste først
  • Nyeste først
  • Skapad (Eldste først)
  • Skapad (Nyeste først)
  • Senast uppdaterad (Eldste først)
  • Senast uppdaterad (Nyeste først)
  • Disputationsdatum (tidligste først)
  • Disputationsdatum (siste først)
Merk
Maxantalet träffar du kan exportera från sökgränssnittet är 250. Vid större uttag använd dig av utsökningar.
  • 151. Wohlin, Claes
    et al.
    Petersson, Håkan
    Höst, Martin
    Runeson, Per
    Defect content estimation for two reviewers2001Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Estimation of the defect content is important to enable quality control throughout the software development process. Capture-recapture methods and curve fitting methods have been suggested as tools to estimate the defect content after a review. The methods are highly reliant on the quality of the data. If the number of reviewers is fairly small, it becomes difficult or even impossible to get reliable estimates. This paper presents a comprehensive study of estimates based on two reviewers, using real data from reviews. Three experience-based defect content estimation methods are evaluated vs. methods that use data only from the current review. Some models are possible to distinguish from each other in terms of statistical significance. In order to gain an even better understanding, the best models are compared subjectively. It is concluded that the experience-based methods provide some good opportunities to estimate the defect content after a review.

  • 152.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Prikladniki, Rafael
    Systematic literature reviews in software engineering2013Inngår i: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 55, nr 6, s. 919-920Artikkel i tidsskrift (Annet vitenskapelig)
  • 153.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Runeson, Per
    Da Mota Silveira Neto, Paulo Anselmo
    Engström, Emelie
    Do Carmo Machado, Ivan
    De Almeida, Eduardo Santana
    On the reliability of mapping studies in software engineering2013Inngår i: Journal of Systems and Software, ISSN 0164-1212 , Vol. 86, nr 10, s. 2594-2610Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Systematic literature reviews and systematic mapping studies are becoming increasingly common in software engineering, and hence it becomes even more important to better understand the reliability of such studies. Objective: This paper presents a study of two systematic mapping studies to evaluate the reliability of mapping studies and point out some challenges related to this type of study in software engineering. Method: The research is based on an in-depth case study of two published mapping studies on software product line testing. Results: We found that despite the fact that the two studies are addressing the same topic, there are quite a number of differences when it comes to papers included and in terms of classification of the papers included in the two mapping studies. Conclusions: From this we conclude that although mapping studies are important, their reliability cannot simply be taken for granted. Based on the findings we also provide four conjectures that further research has to address to make secondary studies (systematic mapping studies and systematic literature reviews) even more valuable to both researchers and practitioners.

  • 154.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Runeson, Per
    Lund University.
    Höst, Martin
    Lund University.
    Ohlsson, Magnus C.
    Regnell, Björn
    Lund University.
    Wesslén, Anders
    Experimentation in Software Engineering2015Bok (Annet vitenskapelig)
  • 155.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Runeson, Per
    Höst, Martin
    Ohlsson, Magnus C.
    Regnell, Björn
    Wesslén, Anders
    Experimentation in Software Engineering2012Bok (Annet vitenskapelig)
    Abstract [en]

    Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors’ book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a “cookbook” when evaluating new methods or techniques before implementing them in their organization.

  • 156.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Wnuk, Krzysztof
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Šmite, Darja
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Franke, Ulrik
    Badampudi, Deepika
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Cicchetti, Antonio
    Supporting strategic decision-making for selection of software assets2016Inngår i: Lecture Notes in Business Information Processing / [ed] Lamprecht A.-L.,Maglyas A., Springer, 2016, Vol. 240, s. 1-15Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Companies developing software are constantly striving to gain or keep their competitive advantage on the market. To do so, they should balance what to develop themselves and what to get from elsewhere, which may be software components or software services. These strategic decisions need to be aligned with business objectives and the capabilities and constraints of possible options. These sourcing options include: in-house, COTS, open source and outsourcing. The objective of this paper is to present an approach to support decision-makers in selecting appropriate types of origins in a specific case that maximizes the benefits of the selected business strategy. The approach consists of three descriptive models, as well as a decision process and a knowledge repository. The three models are a decision model that comprises three cornerstones (stakeholders, origins and criteria) and is based on a taxonomy for formulating decision models in this context, and two supporting models (property models and context models). © Springer International Publishing Switzerland 2016.

  • 157.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Šmite, Darja
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Classifications of Software Transfers2012Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Many companies have development sites around the globe. This inevitably means that development work may be transferred between the sites. This paper defines a classification of software transfer types; it divides transfers into three main types: full, partial and gradual transfers to describe the context of a transfer. The differences between transfer types, and hence the need for a classification, are illustrated with staffing curves for two different transfer types. The staffing curves are obtained through a combination of interviews with both high-level management and a group of experts, and an industrial case study. From the empirical work, it is concluded that the distribution of personnel differs for different types of transfer, which means that it is crucial to be clear about different classes of software transfers. If not, it is easy to underestimate the effort needed to transfer software work as well as additional costs related to the transfer as such.

    Fulltekst (pdf)
    fulltext
  • 158.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Šmite, Darja
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Moe, Nilsbrede
    A general theory of software engineering: Balancing human, social and organizational capitals2015Inngår i: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 109, s. 229-242Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    There exists no generally accepted theory in software engineering, and at the same time a scientific discipline needs theories. Some laws, hypotheses and conjectures exist, but yet no generally accepted theory. Several researchers and initiatives emphasize the need for theory in the discipline. The objective of this paper is to formulate a theory of software engineering. The theory is generated from empirical observations of industry practice, including several case studies and many years of experience in working closely between academia and industry. The theory captures the balancing of three different intellectual capitals: human, social and organizational capitals, respectively. The theory is formulated using a method for building theories in software engineering. It results in a theory where the relationships between the three different intellectual capitals are explored and explained. The theory is illustrated based on an industrial case study, where it is shown how decisions made in industry practice are explainable with the formulated theory, and the consequences of the decisions are made explicit. Based on the positive results, it is concluded that the theory may have a good explanatory power, although more evaluations are needed. ©2015TheAuthors.PublishedbyElsevierInc.ThisisanopenaccessarticleundertheCCBY-NC-NDlicense.

  • 159. Xie, M
    et al.
    Hong, G Y
    Wohlin, Claes
    Modeling and Analysis of Software System Reliability.2003Inngår i: Case Studies on Reliability and Maintenance / [ed] Blischke, W; Murphy, P, Germany: Wiley VHC Verlag , 2003Kapittel i bok, del av antologi (Annet vitenskapelig)
  • 160.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Calefato, Fabio
    Wohlin, Claes
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Cost Savings in Global Software Engineering Where's the Evidence?2015Inngår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 32, nr 4, s. 26-32Artikkel i tidsskrift (Annet vitenskapelig)
  • 161.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Moe, Nills Brede
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Šablis, Aivars
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Wohlin, Claes
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software teams and their knowledge networks in large-scale software development2017Inngår i: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 86, nr JUN, s. 71-86Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Context: Large software development projects involve multiple interconnected teams, often spread around the world, developing complex products for a growing number of customers and users. Succeeding with large-scale software development requires access to an enormous amount of knowledge and skills. Since neither individuals nor teams can possibly possess all the needed expertise, the resource availability in a team's knowledge network, also known as social capital, and effective knowledge coordination become paramount. Objective: In this paper, we explore the role of social capital in terms of knowledge networks and networking behavior in large-scale software development projects. Method: We conducted a multi-case study in two organizations, Ericsson and ABB, with software development teams as embedded units of analysis. We organized focus groups with ten software teams and surveyed 61 members from these teams to characterize and visualize the teams' knowledge networks. To complement the team perspective, we conducted individual interviews with representatives of supporting and coordination roles. Based on survey data, data obtained from focus groups, and individual interviews, we compared the different network characteristics and mechanisms that support knowledge networks. We used social network analysis to construct the team networks, thematic coding to identify network characteristics and context factors, and tabular summaries to identify the trends. Results: Our findings indicate that social capital and networking are essential for both novice and mature teams when solving complex, unfamiliar, or interdependent tasks. Network size and networking behavior depend on company experience, employee turnover, team culture, need for networking, and organizational support. A number of mechanisms can support the development of knowledge networks and social capital, for example, introduction of formal technical experts, facilitation of communities of practice and adequate communication infrastructure. Conclusions: Our study emphasizes the importance of social capital and knowledge networks. Therefore, we suggest that, along with investments into training programs, software companies should also cultivate a networking culture to strengthen their social capital, a known driver of better performance.

  • 162. Šmite, Darja
    et al.
    Wohlin, Claes
    A Whisper of Evidence in Global Software Engineering2011Inngår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 28, nr 4, s. 15-18Artikkel i tidsskrift (Annet (populærvitenskap, debatt, mm))
    Fulltekst (pdf)
    fulltext
  • 163.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Wohlin, Claes
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Lessons learned from transferring software products to India2012Inngår i: Journal of Software Maintenance and Evolution: Research and Practice, ISSN 1532-060X, E-ISSN 1532-0618, Vol. 24, nr 6Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Globalization has influenced the way software is developed today, and many software organizations have started to actively utilize resources from around the world. However, these endeavors are recognized as very challenging, and they have attracted a lot of attention in software research in the past decade. Unlike many other research initiatives, which explore the complexities of distributed software development activities, the focus of this paper is on software transfers. Software transfers refer to activities that are moved from one location to another. The authors draw attention to the lessons learned from an empirical investigation of two transfer projects conducted at Ericsson. Both transfers were performed between a site in Sweden and a site in India. The observations outline a set of generic practices that have been found useful for transferring software development within a company. It also highlights a number of challenges to be addressed and a set of corresponding recommendations. Finally, the paper emphasizes the need to identify software products that are suitable for transfers and the need to monitor the long-term effects of transfer.

    Fulltekst (pdf)
    fulltext
  • 164. Šmite, Darja
    et al.
    Wohlin, Claes
    Risk Identification in Software Product Transfers2011Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Software companies today often face the necessity to decide where to develop their products. Inability to employ people or continue ongoing development with the same capacity in a given site of a company often leads to relocation of software work from one site to another. Software product transfers, however, are associated with numerous challenges that require investments, and may also have a secondary harder to capture effect on development productivity, quality and scope. In this paper, we share the results from previous empirical studies of software product transfers and offer a checklist for risk identification. The checklist shall be useful for software companies that consider, plan or execute software transfers. Although many risk factors included in the checklist may seem obvious, our empirical observations indicate that prior to obtaining the necessary experience these factors have been initially overlooked. Thus we believe that the checklist will be especially useful for managers with no or little experiences in relocating software work between the two sites of the same company.

    Fulltekst (pdf)
    fulltext
  • 165. Šmite, Darja
    et al.
    Wohlin, Claes
    Software Product Transfers: Lessons Learned from a Case Study2010Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Although global software work nowadays is not a phenomenon, research and practice is still addressing the complexities associated with the new forms of work enabled through globalization. ‘Go global’ strategies usually prescribe two alternative approaches: distribution of software development activities across several locations, or re-location of work to another site. This research paper focuses on the latter approach that is called software product transfers and discusses findings from an empirical case study conducted in Ericsson. The observations indicate that transferring software work from one site to another site of the same company is a challenging endeavor. Furthermore, practices used in co-located projects do not necessarily lead to a desired outcome. The paper provides an overview of the challenges and highlights practical advice for handling software product transfers.

    Fulltekst (pdf)
    fulltext
  • 166. Šmite, Darja
    et al.
    Wohlin, Claes
    Strategies Facilitating Software Product Transfers2011Inngår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 8, nr 5, s. 60-66Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Globalization of software work has become common in today's market. As part of cost-reduction strategies, many product-focused software companies started shipping their product development to insourcing and outsourcing offshore locations. Unfortunately, moving software products from one site to another isn't always a good business strategy for either the organization or the product. In this article, the authors discuss findings from studying software insourcing transfers at Ericsson, a large software product development company headquartered in Sweden. Their findings suggest that certain product, personnel, and process characteristics can facilitate the execution of an offshore insourcing transfer. On the basis of research conducted together with the company, they share a list of critical factors alleviating transfer difficulties and seven strategies facilitating transition of software work across sites.

    Fulltekst (pdf)
    fulltext
  • 167. Šmite, Darja
    et al.
    Wohlin, Claes
    Aurum, Aybuke
    Jabangwe, Ronald
    Numminen, Emil
    Towards an Understanding of Sourcing Decisions2011Konferansepaper (Fagfellevurdert)
  • 168.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Wohlin, Claes
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Aurum, Aybüke
    Jabangwe, Ronald
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Numminen, Emil
    Blekinge Tekniska Högskola, Sektionen för management.
    Offshore Insourcing in Software Development: Structuring the Decision-Making Process2013Inngår i: Journal of Systems and Software, ISSN 0164-1212, Vol. 86, nr 4, s. 1054-1067Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    A variety of new forms of business are enabled through globalization and practiced by software organizations today. While companies go global to reduce their development costs, access a larger pool of resources and explore new markets, it is often assumed that the level of delivered services shall remain the same after implementing the sourcing decisions. In contrast, critical studies identified that global software development is associated with unique challenges, and a lot of global projects fail to mitigate the implications of a particular global setting. In this paper we explore offshore insourcing decisions on the basis of empirical research literature and an empirical field study conducted at Ericsson. By analyzing decisions in two different cases we found that each offshore insourcing decision consisted of deciding what, where, when, how and why to insource. Related empirical research and field observations suggest that not all combinations are successful and alignment between different decision points has thus a prominent role. To address these concerns we built an empirically-based insourcing decision structure, which outlines a logical path through the decision options and helps selecting an offshore insourcing strategy that targets creation of the necessary alignment. The key element of the proposed approach is a structured and well-defined decision-making process, which is intended to support managers in their decision-making. The usefulness of the proposed approach is evaluated in an additional empirical case of a new offshore insourcing decision.

    Fulltekst (pdf)
    fulltext
  • 169. Šmite, Darja
    et al.
    Wohlin, Claes
    Feldt, Robert
    Gorschek, Tony
    Reporting Empirical Research in Global Software Engineering: A Classification Scheme2008Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Increased popularity of global software engineering (GSE) has resulted in quite a number of research and industrial studies. As the area matures, an increased focus on empirically supported results leads to a greater potential impact on future research and industrial practice. However, since GSE scenarios are diverse, what works in one context might not directly apply in another. Thus it is necessary to understand, how GSE-related empirical findings should be reported to be useful for practitioners and researchers. Furthermore, it‘s important to summarize progress and get the big picture of published research to identify gaps and commonalities. In this paper we analyze differentiating factors of GSE scenarios and offer a classification scheme for describing the context of a GSE study. In addition, we report initial results of a systematic review on GSE-related empirical literature using papers from ICGSE 2006 and 2007, at the same time illustrating and evaluating the proposed scheme.

  • 170.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Wohlin, Claes
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Galviņa, Zane
    Prikladnicki, Rafael
    An empirically based terminology and taxonomy for global software engineering2014Inngår i: Empirical Software Engineering, ISSN 1382-3256, Vol. 191, nr 1, s. 105-153Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Many organizations nowadays strive for utilization of benefits offered by global software engineering (GSE) and sourcing strategies are thus discussed more often. Since there are so many variations of the attributes associated with global software projects a large amount of new terms has been introduced. The diversity in sourcing jargon however has caused difficulties in determining which term to use in which situation, and thus causing further obstacles to searching and finding relevant research during e.g. systematic literature reviews. The inability of judging the applicability of the research in an industrial context is another important implication on the transferability of research into practice. Thus the need for accurate terminology and definitions for different global sourcing situations emerges as a way for the community to build upon each other's work and hence making progress more quickly. In this paper we first investigate the state of the use of the GSE jargon concluding that terminology is very diverse (many synonyms used to describe the same phenomena), often confusing (same terms used to describe different phenomena) and occasionally ambiguous (few terms used to describe several phenomena). In order to address the identified problems, we conducted a Delphi-inspired study with ten well-established researchers in GSE and developed an empirically based glossary for the key concepts in global software engineering. We then propose a taxonomy for GSE by categorizing the selected terms based on generalization-specialization relationships and illustrate how the taxonomy can be used to categorize and map existing knowledge. The contribution targets future researchers, who will publish or synthesize further empirical work and practitioners, who are interested in published empirical cases. Therefore this work is expected to make a contribution to the future development of research in the GSE field, and alleviate understandability and transferability of existing and future knowledge into practice.

  • 171. Šmite, Darja
    et al.
    Wohlin, Claes
    Gorschek, Tony
    Feldt, Robert
    Empirical evidence in global software engineering: a systematic review2010Inngår i: Empirical Software Engineering, ISSN 1382-3256, Vol. 15, nr 1, s. 91-118Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Recognized as one of the trends of the 21st century, globalization of the world economies brought significant changes to nearly all industries, and in particular it includes software development. Many companies started global software engineering (GSE) to benefit from cheaper, faster and better development of software systems, products and services. However, empirical studies indicate that achieving these benefits is not an easy task. Here, we report our findings from investigating empirical evidence in GSE-related research literature. By conducting a systematic review we observe that the GSE field is still immature. The amount of empirical studies is relatively small. The majority of the studies represent problem-oriented reports focusing on different aspects of GSE management rather than in-depth analysis of solutions for example in terms of useful practices or techniques. Companies are still driven by cost reduction strategies, and at the same time, the most frequently discussed recommendations indicate a necessity of investments in travelling and socialization. Thus, at the same time as development goes global there is an ambition to minimize geographical, temporal and cultural separation. These are normally integral parts of cross-border collaboration. In summary, the systematic review results in several descriptive classifications of the papers on empirical studies in GSE and also reports on some best practices identified from literature.

1234 151 - 171 of 171
RefereraExporteraLink til resultatlisten
Permanent link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf