![]() ![]() ATLAS.ti supports describable and functional links between codes and/or data segments. Particular to ATLAS.ti and capturing the essential aims in the origins of the program is the explicit representation of relationships between concepts. Projects, documents, codes, memos, and groups of these entities are ingredients of virtually any kind of qualitative data analysis software. The idea is that such a de-linearisation fosters a deeper understanding of the researched phenomena, supporting the building up of a ‘context of discovery’. Working with ATLAS.ti is characterised by oscillating between the data level of segmenting, coding and memoing and the conceptual level of linking and building theories. The quotation architecture and integrality of the networking functionality in making connections, expressing ideas and moving on to more abstract analyses are at the heart of the design and workflow. ![]() Inspired by Anselm Strauss’s work and the field of hermeneutic text interpretation, the aim was to support the data-level work inherent to qualitative data analysis. It is now developed and supported by Scientific Software Development GmbH. We present the summaries in alphabetical order.ĪTLAS.ti 1 was developed from the late 1980s in the Psychology Department at the Technical University of Berlin, led by Heiner Legewie, Erhardt Conrad, Thomas Muhr and a team of computer scientists and linguists. ![]() In any case, there is relatively scant reference in this chapter to the fundamental tools for qualitative data analysis that they all provide: coding, organising and searching data ( Chapter 2). Some concentrate on distinctive tools and the ‘personality’ of the software. Some tell the story behind the software because an appreciation of the underlying developmental philosophy is important in understanding the tools. The variety in histories, rationale and functionality means the summaries concentrate on different aspects. You should therefore consult the software websites for additional and up-to-date information. However, software develops quickly and neither this chapter nor the book as a whole describes all the functions available. Information contained here was correct at the time of writing (autumn 2013). We wanted to avoid this chapter becoming a ‘sales pitch’, so we have edited developers’ summaries and added our own contributions. They therefore reflect the philosophy behind each package and also developers’ own views of what is exceptional about their products. Most of these summaries have been developed in conjunction with the software developers themselves. This chapter summarises the CAQDAS packages featured in this book and for which there are step-by-step materials on the companion website ( ). Reading this book is like having Ann and Christina at your shoulder as you analyse your data!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |