The Experts below are selected from a list of 76209 Experts worldwide ranked by ideXlab platform
Scott Proescholdbell - One of the best experts on this subject based on the ideXlab platform.
-
informing best practice with community practice the community change chronicle method for Program Documentation and evaluation
Health Promotion Practice, 2009Co-Authors: Sheryl A Scott, Scott ProescholdbellAbstract:Health promotion professionals are increasingly encouraged to implement evidence-based Programs in health departments, communities, and schools. Yet translating evidence-based research into practice is challenging, especially for complex initiatives that emphasize environmental strategies to create community change. The purpose of this article is to provide health promotion practitioners with a method to evaluate the community change process and document successful applications of environmental strategies. The community change chronicle method uses a five-step process: first, develop a logic model; second, select outcomes of interest; third, review Programmatic data for these outcomes; fourth, collect and analyze relevant materials; and, fifth, disseminate stories. From 2001 to 2003, the authors validated the use of a youth empowerment model and developed eight community change chronicles that documented the creation of tobaccofree schools policies (n = 2), voluntary policies to reduce secondhand smoke in youth hangouts (n = 3), and policy and Program changes in diverse communities (n = 3).
Sheryl A Scott - One of the best experts on this subject based on the ideXlab platform.
-
informing best practice with community practice the community change chronicle method for Program Documentation and evaluation
Health Promotion Practice, 2009Co-Authors: Sheryl A Scott, Scott ProescholdbellAbstract:Health promotion professionals are increasingly encouraged to implement evidence-based Programs in health departments, communities, and schools. Yet translating evidence-based research into practice is challenging, especially for complex initiatives that emphasize environmental strategies to create community change. The purpose of this article is to provide health promotion practitioners with a method to evaluate the community change process and document successful applications of environmental strategies. The community change chronicle method uses a five-step process: first, develop a logic model; second, select outcomes of interest; third, review Programmatic data for these outcomes; fourth, collect and analyze relevant materials; and, fifth, disseminate stories. From 2001 to 2003, the authors validated the use of a youth empowerment model and developed eight community change chronicles that documented the creation of tobaccofree schools policies (n = 2), voluntary policies to reduce secondhand smoke in youth hangouts (n = 3), and policy and Program changes in diverse communities (n = 3).
David Lorge Parnas - One of the best experts on this subject based on the ideXlab platform.
-
using test oracles generated from Program Documentation
IEEE Transactions on Software Engineering, 1998Co-Authors: Dennis Peters, David Lorge ParnasAbstract:The paper illustrates how software can be described precisely using LD-relations, how these descriptions can be presented in a readable manner using tabular notations, and one way such descriptions can be used to test Programs. The authors describe an algorithm that can be used to generate a test oracle from Program Documentation, and present the results of using a tool based on it to help test part of a commercial network management application. The results demonstrate that these methods can be effective at detecting errors and greatly increase the speed and accuracy of test evaluation when compared with manual evaluation. Such oracles can be used for unit testing, in situ testing, constructing self-checking software, and ensuring consistency between code and Documentation.
-
generating a test oracle from Program Documentation work in progress
International Symposium on Software Testing and Analysis, 1994Co-Authors: Dennis Peters, David Lorge ParnasAbstract:A fundamental assumption of software testing is that there is some mechanism, an oracle, that will determine whether or not the results of a test execution are correct. In practice this is often done by comparing the output, either automatically or manually, to some pre-calculated, presumably correct, output [17]. However, if the Program is formally documented it is possible to use the specification to determine the success or failure of a test execution, as in [1], for example. This paper discusses ongoing work to produce a tool that will generate a test oracle from formal Program Documentation.In [9], [10] and [11] Parnas et al. advocate the use of a relational model for documenting the intended behaviour of Programs. In this method, tabular expressions are used to improve readability so that formal Documentation can replace conventional Documentation. Relations are described by giving their characteristic predicate in terms of the values of concrete Program variables. This Documentation method has the advantage that the characteristic predicate can be used as the test oracle -- it simply must be evaluated for each test execution (input & output) to assign pass or fail. In contrast to [1], this paper discusses the testing of individual Programs, not objects as used in [1]. Consequently, the method works with Program Documentation, written in terms of the concrete variables, and no representation function need be supplied. Documentation in this form, and the corresponding oracle, are illustrated by an example.Finally, some of the implications of generating test oracles from relational specifications are discussed.
Dennis Peters - One of the best experts on this subject based on the ideXlab platform.
-
using test oracles generated from Program Documentation
IEEE Transactions on Software Engineering, 1998Co-Authors: Dennis Peters, David Lorge ParnasAbstract:The paper illustrates how software can be described precisely using LD-relations, how these descriptions can be presented in a readable manner using tabular notations, and one way such descriptions can be used to test Programs. The authors describe an algorithm that can be used to generate a test oracle from Program Documentation, and present the results of using a tool based on it to help test part of a commercial network management application. The results demonstrate that these methods can be effective at detecting errors and greatly increase the speed and accuracy of test evaluation when compared with manual evaluation. Such oracles can be used for unit testing, in situ testing, constructing self-checking software, and ensuring consistency between code and Documentation.
-
generating a test oracle from Program Documentation work in progress
International Symposium on Software Testing and Analysis, 1994Co-Authors: Dennis Peters, David Lorge ParnasAbstract:A fundamental assumption of software testing is that there is some mechanism, an oracle, that will determine whether or not the results of a test execution are correct. In practice this is often done by comparing the output, either automatically or manually, to some pre-calculated, presumably correct, output [17]. However, if the Program is formally documented it is possible to use the specification to determine the success or failure of a test execution, as in [1], for example. This paper discusses ongoing work to produce a tool that will generate a test oracle from formal Program Documentation.In [9], [10] and [11] Parnas et al. advocate the use of a relational model for documenting the intended behaviour of Programs. In this method, tabular expressions are used to improve readability so that formal Documentation can replace conventional Documentation. Relations are described by giving their characteristic predicate in terms of the values of concrete Program variables. This Documentation method has the advantage that the characteristic predicate can be used as the test oracle -- it simply must be evaluated for each test execution (input & output) to assign pass or fail. In contrast to [1], this paper discusses the testing of individual Programs, not objects as used in [1]. Consequently, the method works with Program Documentation, written in terms of the concrete variables, and no representation function need be supplied. Documentation in this form, and the corresponding oracle, are illustrated by an example.Finally, some of the implications of generating test oracles from relational specifications are discussed.
Theo Dhondt - One of the best experts on this subject based on the ideXlab platform.
-
an approach to high level behavioral Program Documentation allowing lightweight verification
International Conference on Program Comprehension, 2006Co-Authors: C De Roover, I Michiels, K Gybels, Theo DhondtAbstract:Typically, multiple developers are involved in the various stages of the software development and maintenance process. To ensure an optimal transfer of knowledge between these different peers, a reliable human-readable model of the dynamics of a software artefact is needed. Once these models become machine-verifiable, they can be used throughout an applications lifetime to check whether the documented behavioral properties continue to hold as the application evolves. Unfortunately, most existing modeling media are inadequate to express human-readable behavioral models which are at the same time machine-verifiable. We therefore propose a declarative platform wherein behavioral Program models can be expressed in terms of userdefined high-level concepts and be automatically verified against an applications actual behavior. We demonstrate our approach by using it to both document and verify an interpreter for a garbage-collected Programming language.