2 resultados para Rubrica Android

em Universidade Federal de Uberlândia


Relevância:

10.00% 10.00%

Publicador:

Resumo:

This research aims to analyze the meaning making by Elementary Education students from public schools of Uberlândia (Minas Gerais, Brazil) about the social and environmental problems of their surroundings as of audiovisual reading and expression skills. The theoretical framework is based on constructivism, through the study of contributions about: cognitive development; meaningful learning; cognitive processes and types of knowledge; principles of learning with technology; educommunication focused on critical media literacy; and critical environmental education. The study object is a video production workshop organized in nine meetings, from September to November 2015, attended by 15 students. The following data collection instruments were used: the materials produced by the participants, specifically guided critical media literacy, agenda, script and final video; researcher observations from his role as a mediator; and focal interviews. The analysis was divided into two axes: procedural knowledge – technical skills of critical media literacy and production; and conceptual and metacognitive knowledge – representation of social and environmental problems and metacognitive skills of critical media literacy. Data were coded in the form of a skill evaluation rubric and also in the form of graphs. Thus, despite the time constraints, it is inferred that the workshop helped students to deepen their understanding about the discussed content, which is reinforced by observing in the graphs how the constant progressive differentiation of more inclusive concepts occurred along the meetings. It is further considered that the workshop contributed to the students reflect on their way of learning through critical use of techniques of media literacy and production, which can be seen from the satisfactory learners performance in most elements evaluated by the rubrics, as well as from the success in identifying interlocutors, values and actions in the read and built texts, something revealed by the graphs.

Relevância:

10.00% 10.00%

Publicador:

Resumo:

One of the most common forms of reuse is through API usage. However, one of the main challenges to effective usage is an accessible and easy to understand documentation. Several papers have proposed alternatives to make more understandable API documentation, or even more detailed. However, these studies have not taken into account the complexity of understanding of the examples to make these documentations adaptable to different levels of experience of developers. In this work we developed and evaluated four different methodologies to generate tutorials for APIs from the contents of Stack Overflow and organizing them according to the complexity of understanding. The methodologies were evaluated through tutorials generated for the Swing API. A survey was conducted to evaluate eight different features of the generated tutorials. The overall outcome of the tutorials was positive on several characteristics, showing the feasibility of the use of tutorials generated automatically. In addition, the use of criteria for presentation of tutorial elements in order of complexity, the separation of the tutorial in basic and advanced parts, the nature of tutorial to the selected posts and existence of didactic source had significantly different results regarding a chosen generation methodology. A second study compared the official documentation of the Android API and tutorial generated by the best methodology of the previous study. A controlled experiment was conducted with students who had a first contact with the Android development. In the experiment these students developed two tasks, one using the official documentation of Android and using the generated tutorial. The results of this experiment showed that in most cases, the students had the best performance in tasks when they used the tutorial proposed in this work. The main reasons for the poor performance of students in tasks using the official API documentation were due to lack of usage examples, as well as its difficult use.