In this chapter, we report the analysis and results for each activity based on the empirical data.
Explicate problem
The activity phase is about investigating and analyzing the practical problem and formulating the problem of significance, not only for local practice but also for general interest. The problem in this study was obvious concerning previous evaluations in higher education concerning scientific approaches in writing a thesis and conducting a review of scientific literature. We have more students today than before, but varying experiences of academic studies. To meet this diversity of students, different forms of knowledge representation are needed. If the teaching is based primarily on textbooks that include mostly written text and teachers’ lectures, it will disadvantage many students whose learning strategies are not primarily visual or auditory (Boström & Löfquist, 2012).
Complementary learning tools for books are thus needed. The problem is both democratic and pedagogical. The empirical data we used in this activity was the literature review (Boström & Sjöström, 2021), but we also used one exploratory workshop and focus group discussions. In this stage, we discussed in detail which pedagogical knowledge (PK) and content knowledge (CK) would be included in the learning tool and how the technological knowledge (TK) would support the content. This activity resulted in an overview of a tentative prototype of the research process.
The decisive step in this activity was the exploratory workshop. The researchers stayed as objective as possible to capture and describe the problem and arrive at the best possible overview. Diagnostic assessment of the problem was addressed in workshops and focus groups.
Define requirements
Requirements should describe the expected performance and limitations set on the solution or the external constraints on the solution “outline” as a creative process. The problem is transformed into demands of the artefact. Defined requirements in this activity phase include functionality, structure, and environmental aspects. In this stage detailed discussions were mainly about the technological knowledge (TC) in combination with (TPC). The empirical data used in this activity was first input from the references group and the adjustments to the prototype. Then a second exploratory workshop was conducted, followed by focus group discussions with the research team. These discussions focused mostly on the core based on the TPACK model. The ability of different technical solutions to fulfil the requirements was discussed in order to assure a successful outcome. At the end of this activity, we reached a consensus on the artefact’s structure and content. In this step, diagnostic assessment was also addressed in focus groups. Figure 3 is an illustration of the results of the requirements. The hierarchical learning structure in several layers, which imply a successive refinement of learning, is illustrated.
More precisely, our intention concerning basic learning, was to get the structure of the whole research process to be synchronized and logical and get the illustrations to be as clear as possible. In this step, it was discussed how the illustrations would depict CK as well as possible. Furthermore, we had a requirement that pop-ups should be displayed with an overview description of the content. Finally, we had a requirement that students’ learning should be deepened through theoretical descriptions of the process, combined with interactive personal questioning. These requirements were constantly discussed and re-evaluated with the web –programmer. At this stage, the core of the TPACK-model was incorporated.
Design & Development
In this activity, the artefact that addresses the problem was created. For this learning tool (the artefact), we used a programmer and an illustrator to meet the defined requirements in the creation of the artefact. In this situation, the discussions were mostly about the combination of technical and pedagogical issues (TPK). The programmer proceeded from a visual description of the whole artefact and the researchers’ explanations and then implemented the technical requirements. The illustrator was commissioned to create a complete picture of the process and a pictogram for the important steps in the process. Together with the research team, the execution was discussed several times.
In interviews with these key staff members, the following strategies emerged. The illustrator emphasised that her starting point for the pictograms was that they would reinforce the text that was communicated. The text and pictogram should communicate the same content in the best possible way. The pictograms would also support and strengthen students’ retention. The illustrator made proposals for each pictogram based on what she believed they communicated and signalled. The pictograms were discussed with the research group, and some adjustments were made. The illustrator also designed the overall picture of the learning tool. The first consideration was that the page would be aesthetically pleasing, and that colours and shapes would complement each other but in some cases be distinctive. For example, the illustrator used squares for factors that came from outside the research process, for example the pictogram such as from society, and ovals represent aspects that eventually affected the process.
The programmer emphasised that a complex image formed the basis of the website. The MethodViz software is full-stack application created using an object-oriented PHP architecture. It employs a virtual Windows-server with an Apache webserver and a MySQL database-server. Libraries used include a Bootstrap (CSS library), jQueary for certain JavaScript functionality, and TinyMSC to make neat interaction boxes in the subviews.
The graphic layout had to be iterative, and the progression should be visible. An important problem for him to solve was making the graphic image interactive but also scalable. He solved that problem by building a coordinate system in which the whole image was split into smaller pieces and each smaller image was entered into the coordinate system. The working process was based on conversations with the research team and the illustrator. The conversations shared a common thread in which everyone focused the overall project and then broke everything down into smaller parts regarding content, functionality, and priority. A strength of the work was that we had a clear goal, a clear sketch, and well-formulated goals, which specifically facilitated the programmer´s work. Areas for improvement were more of a technical nature, namely, to create interfaces for editing website content and delimitation of what should be included in the responsive website. The first version of the website focused on layout and lightweight functionality for desktops but also included basic layout for mobile tools. Collaboration with the illustrator was also an important part of the creation process. For example, it was important to understand that different computers have different resolutions, which will display images differently. Changes can also occur in texts when they are translated to different languages. The key to a successful collaboration is to work together to find the best possible solution and be open to feedback.
Text information entered by the user is stored in a database, in which each user has an item for each textbox in the tool. The text is kept between user access sessions and can also be downloaded into a word document for further processing. The database for MethodViz was designed to keep information about its users and their respective interaction inputs. First there is a table defining the users, which stores a unique user ID, e-mail address, password, first and last name, timestamp for creation, and whether the user is admin or not. For the rest, the database follows the hierarchical structure such that each module (e.g. Current knowledge, Problem area, etc.) has its own table. Modules requiring several interaction inputs have a table for each individual input. The tables have a unique ID, user input text, a timestamp for creation and last update, and a project ID. The latter links to an individual project belonging to a user and is defined by a separate table that contains project ID, user ID, project name, and timestamp for creation and last update. The project table enables a user to use MethodViz for several different research projects.
In this step, a combination of formative, diagnostic and summative assessments were carried out. The purpose of the formative assessments was to create improvements in the artefact’s development and design. We used interviews, discussions and simple surveys.
Demonstrate
The fourth activity in the DSR design is to demonstrate the artefact in real-life settings. It is also called “proof-of-concept” because the artefact’s feasibility will be proved. In this activity, the reference group, students, teachers, and researchers, tested and gave feedback regarding the learning tool, using formative assessments. In this step, all aspects were thoroughly examined by the TPACK model. Several adjustments and improvements were made based on the feedback. For example, a marking was needed to indicate where they would start in the research process. No major changes were made to the original artefact except that the research process became an oval instead of a circle because further steps of the research process were added.
As images are directly processed by our long-term memory, we have introduced two kinds of visualizations in the learning tool. Firstly, we have described the interrelations between the steps of the research process with a relational graph. These interrelations can be seen as a linear process with several feedback loops. Our choice was, however, a circular format in order to emphasise the cycle of research being an accumulation of new knowledge to existing knowledge, which then is the basis for future research. The many possible feedback loops within the research process were omitted because the visual impression with be unnecessary complex and not supporting an easy access and learning of the process’ main parts. In the present version, feedbacks were left to be described in texts and to be emphasised by a teacher. Secondly, we have introduced pictograms to each step of the research process. The pictograms have been designed to give a straightforward association with the process step, and been placed both in the relational graph of the research process, as well as on the sub-pages describing each step in detail. The aim was to create a direct link with the students’ long-term memory and so facilitate the learning.
In this activity, approximately 200 students and 20 teachers and researches were involved. We needed such a large number of testers because the testing was combined with the evaluation step to assess the artefact’s usability with respect to learning research methods. The testing was firstly introduced by demonstrating the functionality of the learning tool. Then the test persons were given access to the tool to use it as desired, only using instructions in form of a short overview as part of the learning tool. The assessment for the Demonstrate step consisted of a number of open questions for suggested improvements. The results led to new requirements, such as including the oval format as the process was adapted with further steps.
Evaluate
The last activity was to evaluate the artefact and determine whether it fulfilled the requirements and could solve the practical problem. The project leader carried out a first evaluation checking the functionality with respect to the requirements. Test persons followed the procedure presented in Sect. 5.4. Approximately 200 undergraduate students, 10 PhD students and 10 teachers evaluated the learning tool via either a web survey or discussions. The web survey considered all aspects based on the TPACK model. We used summative tests to assess the learning tool’s final functionality and usability with respect to learning research methods via web surveys. This learning resource has in its various prototypes been evaluated above all with quantitative data but also descriptive statistics. Through conversations, interviews and web surveys, students, experts and teachers continuously have given us feedback on the learning resource. The qualitative data has been analyzed with thematic content analysis. Thus, we have been able to take part in their personal perceptions of the learning tool. The quantitative data has given us indications of whether the various parts of the learning tool have worked at group level for the students. For example, they estimated how they understood the texts or tasks in the form of five-point Lickert scale and open comments. We have seen how different parts of the tool have functioned.
An overwhelming majority believed that this learning tool was long overdue and much needed in academic studies. The overall conclusion in our summary of the evaluations was that the artefact would contribute to a different way of understanding the research process.
In summary
As the researchers who developed this learning tool, we can first and foremost state that this research process has taken time. In a process that combines creative thinking and the scientific method, it is important to keep the structure of the work together and to document all activities thoroughly. The DSR model in Fig. 2 is a fundamental formalisation of the design and development process. It gives the process structure and elucidates the relationship between an appropriate research strategy and its outcomes. Figure 4 shows the main page of the learning tool. The design process and the identified hierarchical structure (see Fig. 4) led to a relational graph of the research process with representative illustrations, where refined knowledge is gained through (1) pop-up windows containing familiarizing descriptions of the step and (2) a profound description in a sub-page. We have chosen the general picture more circular (oval) and not rectilinear because we see the research process as holistic. Then we have chosen a shorter summary of each aspect, which the students get if they hover over words. Then we have each aspect summarized on about one page (left). That text is more formal. On the right side is an exercise assignment that is written more personally to the student.
Students start at the box philosophy of science where there is a short text about its contents followed by some questions to answer. The students save their answers in a database. And then they continue to the next yellow box, scientific literature to get an insight into the specific content. To each step there is also a pictogram illustrating the core of the content. The students continue through the oval and at some stages they might go back and complement their notes, for example the boxes ethics or society. At the end they will have the most important aspects of their chosen content to be able to write the thesis in a logical way.
The sub-page contains a theoretical description of the research step on the left and questions for interaction and relation to the student’s own research on the right (Fig. 5).
Methodological considerations
All research designs have their strengths and weaknesses. Our research strategy in this study has been a kind of action research. Our intention was to produce an artefact (learning tool) that addresses a practical problem in a real-word setting. We, the research team, including the illustrator and the programmers, all participated in the changes. The key activities can be described as cyclical processes. They major concerns in this strategy are weak generalizability and lack of impartiality (Johannessen & Pajons, 2014). The scientific paradigm is often a pragmatic worldview, which naturally leads to weak generalizability. To maintain the scientific approach, we included a reference group with researchers from various disciplines with expertise in various scientific traditions. With these experts’ help, we were able to manage the risk of impartiality. We are also well aware that the results cannot be generalised but that they can inspire other researchers with similar problems.