In the past few years several major reports highlighted the gap between our knowledge of effective treatments and services currently being received by consumers. These reports agree that we know much about interventions that are effective but make little use of them to help achieve important behavioral health outcomes for children families and adults nationally. This theme is repeated in reports by the Surgeon General (United States Department of Health and Human Services 1999; 2001) the National Institute of Mental Health [NIMH] National Advisory Mental Health Council Workgroup on Child and Adolescent Mental Health Intervention Development and Deployment (2001) Bernfeld Farrington & Leschied (2001) Institute of Medicine (2001) and the Presidents New Freedom Commission on Mental Health (2003). The authors call for applied research to better understand service delivery processes and contextual factors to improve the efficiency and effectiveness of program implementation at local state and national levels. Our understanding of how to develop and evaluate evidence-based intervention programs has been furthered by on-going efforts to research and refine programs and practices to define "evidence bases" and to designate and catalogue "evidence-based programs or practices". However the factors involved in successful implementation of these programs are not as well understood. Current views of implementation are based on the scholarly foundations prepared by Pressman & Wildavskys (1973) study of policy implementation Havelock & Havelocks (1973) classic curriculum for training change agents and Rogers (1983; 1995) series of analyses of factors influencing decisions to choose a given innovation. These foundations were tested and further informed by the experience base generated by pioneering attempts to implement Fairweather Lodges and National Follow-Through education models among others. Petersilia (1990) concluded that "The ideas embodied in innovative social programs are not self-executing." Instead what is needed is an "implementation perspective on innovation--an approach that views postadoption events as crucial and focuses on the actions of those who convert it into practice as the key to success or failure". (excerpt)

Implementation research: a synthesis of the literature.

Background: Systematic literature studies have become common in software engineering, and hence it is important to understand how to conduct them efficiently and reliably.Objective: This paper presents guidelines for conducting literature reviews using a snowballing approach, and they are illustrated and evaluated by replicating a published systematic literature review.Method: The guidelines are based on the experience from conducting several systematic literature reviews and experimenting with different approaches.Results: The guidelines for using snowballing as a way to search for relevant literature was successfully applied to a systematic literature review.Conclusions: It is concluded that using snowballing, as a first search strategy, may very well be a good alternative to the use of database searches.

/pdf/guidelines-for-snowballing-in-systematic-literature-studies-106rgo5oni.pdf

Guidelines for snowballing in systematic literature studies and a replication in software engineering

Thank you for reading experimental and quasi experimental designs for research. Maybe you have knowledge that, people have search numerous times for their favorite readings like this experimental and quasi experimental designs for research, but end up in malicious downloads. Rather than reading a good book with a cup of tea in the afternoon, instead they cope with some infectious virus inside their laptop.

Experimental And Quasi Experimental Designs For Research

Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a cookbook when evaluating new methods or techniques before implementing them in their organization.

Experimentation in Software Engineering

Lessons from applying the systematic literature review process within the software engineering domain

Context: In a previous study, we reported on a systematic literature review (SLR), based on a manual search of 13 journals and conferences undertaken in the period 1st January 2004 to 30th June 2007. Objective: The aim of this on-going research is to provide an annotated catalogue of SLRs available to software engineering researchers and practitioners. This study updates our previous study using a broad automated search. Method: We performed a broad automated search to find SLRs published in the time period 1st January 2004 to 30th June 2008. We contrast the number, quality and source of these SLRs with SLRs found in the original study. Results: Our broad search found an additional 35 SLRs corresponding to 33 unique studies. Of these papers, 17 appeared relevant to the undergraduate educational curriculum and 12 appeared of possible interest to practitioners. The number of SLRs being published is increasing. The quality of papers in conferences and workshops has improved as more researchers use SLR guidelines. Conclusion: SLRs appear to have gone past the stage of being used solely by innovators but cannot yet be considered a main stream software engineering research methodology. They are addressing a wide range of topics but still have limitations, such as often failing to assess primary study quality.

https://romisatriawahono.net/wp-content/uploads/2013/01/Kitchenham-Systematic-literature-reviews-in-software-engineering-%E2%80%93-A-tertiary-study-2012.pdf

Systematic literature reviews in software engineering - A tertiary study

Experiences using systematic review guidelines

/pdf/a-maturity-model-for-the-implementation-of-software-process-3qltd8ucye.pdf

Mahmood Niazi

Papers

Systematic literature reviews in software engineering - A tertiary study

Experiences using systematic review guidelines

A Maturity Model for the Implementation of Software Process Improvement

An exploratory study of why organizations do not adopt CMMI

A maturity model for the implementation of software process improvement: an empirical study