12 resultados para Pedagogical documentation
em University of Queensland eSpace - Australia
Resumo:
Current debates about educational theory are concerned with the relationship between knowledge and power and thereby issues such as who possesses a truth and how have they arrived at it, what questions are important to ask, and how should they best be answered. As such, these debates revolve around questions of preferred, appropriate, and useful theoretical perspectives. This paper overviews the key theoretical perspectives that are currently used in physical education pedagogy research and considers how these inform the questions we ask and shapes the conduct of research. It also addresses what is contested with respect to these perspectives. The paper concludes with some cautions about allegiances to and use of theories in line with concerns for the applicability of educational research to pressing social issues.
Resumo:
Physical education, now often explicitly identified with health in contemporary school curricula, continues to be implicated in the (re)production of the 'cult of the body'. We argue that HPE is a form of health promotion that attempts to 'make' healthy citizens of young people in the context of the 'risk society'. In our view there is still work to be done in understanding how and why physical education (as HPE) continues to be implicated in the reproduction of values associated with the cult of body. We are keen to understand why HPE continues to be ineffective in helping young people gain some measure of analytic and embodied 'distance' from the problematic aspects of the cult of the body. This paper offers an analysis of this enduring issue by using some contemporary analytic discourses including 'governmentality', 'risk society' and the 'new public health'.
Resumo:
The rise of component-based software development has created an urgent need for effective application program interface (API) documentation. Experience has shown that it is hard to create precise and readable documentation. Prose documentation can provide a good overview but lacks precision. Formal methods offer precision but the resulting documentation is expensive to develop. Worse, few developers have the skill or inclination to read formal documentation. We present a pragmatic solution to the problem of API documentation. We augment the prose documentation with executable test cases, including expected outputs, and use the prose plus the test cases as the documentation. With appropriate tool support, the test cases are easy to develop and read. Such test cases constitute a completely formal, albeit partial, specification of input/output behavior. Equally important, consistency between code and documentation is demonstrated by running the test cases. This approach provides an attractive bridge between formal and informal documentation. We also present a tool that supports compact and readable test cases; and generation of test drivers and documentation, and illustrate the approach with detailed case studies. (C) 2002 Elsevier Science Inc. All rights reserved.