An Evaluation of Software Release-Consistent Protocols

This paper presents an evaluation of three software implementations of release consistency. Release consistent protocols allow data communication to be aggregated, and multiple writers to simultaneously modify a single page. We evaluated an eager invalidate protocol that enforces consistency when synchronization variables are released, a lazy invalidate protocol that enforces consistency when synchronization variables are acquired, and a lazy hybrid protocol that selectively uses update to reduce access misses. Our evaluation is based on implementations running on DECstation-5000/240s connected by an ATM LAN, and an execution driven simulator that allows us to vary network parameters. Our results show that the lazy protocols consistently outperform the eager protocol for all but one application, and that the lazy hybrid performs the best overall. However, the relative performance of the implementations is highly dependent on the relative speeds of the network, processor, and communication software. Lower bandwidths and high per byte software communication costs favor the lazy invalidate protocol, while high bandwidths and low per byte costs favor the hybrid. Performance of the eager protocol approaches that of the lazy protocols only when communication becomes essentially free

A website supporting sensitive religious and cultural advance care planning (ACPTalk): Formative and summative evaluation

Background: Advance care planning (ACP) promotes conversations about future health care needs, enacted if a person is incapable of making decisions at end-of-life that may be communicated through written documentation such as advance care directives. To meet the needs of multicultural and multifaith populations in Australia, an advance care planning website, ACPTalk, was funded to support health professionals in conducting conversations within diverse religious and cultural populations. ACPTalk aimed to provide religion-specific advance care planning content and complement existing resources. Objective: The purpose of this paper was to utilize the context, input, process, and product (CIPP) framework to conduct a formative and summative evaluation of ACPTalk. Methods: The CIPP framework was used, which revolves around 4 aspects of evaluation: context, input, process, and product. Context: health professionals’ solutions for the website were determined through thematic analysis of exploratory key stakeholder interviews. Included religions were determined through an environmental scan, Australian population statistics, and documentary analysis of project steering committee meeting minutes. Input: Project implementation and challenges were examined through documentary analysis of project protocols and meeting minutes. Process: To ensure religion-specific content was accurate and appropriate, a website prototype was built with content review and functionality testing by representatives from religious and cultural organizations and other interested health care organizations who completed a Web-based survey. Product: Website analytics were used to report utilization, and stakeholder perceptions were captured through interviews and a website survey. Results: Context: A total of 16 key stakeholder health professional (7 general practitioners, 2 primary health nurses, and 7 palliative care nurses) interviews were analyzed. Website solutions included religious and cultural information, communication ideas, legal information, downloadable content, and Web-based accessibility. Christian and non-Christian faiths were to be included in the religion-specific content. Input: Difficulties gaining consensus on religion-specific content were overcome by further state and national religious organizations providing feedback. Process: A total of 37 content reviewers included representatives of religious and cultural organizations (n=29), health care (n=5), and community organizations (n=3). The majority strongly agree or agree that the content used appropriate language and tone (92%, 34/37), would support health professionals (89%, 33/37), and was accurate (83%, 24/29). Product: Resource usage within the first 9 months was 12,957 page views in 4260 sessions; majority were (83.45%, 3555/4260) from Australia. A total of 107 Australian-based users completed the website survey; most felt information was accurate (77.6%, 83/107), easy to understand (82.2%, 88/107), useful (86.0%, 92/107), and appropriate (86.0%, 92/107). A total of 20 nurses (general practice n=10, palliative care n=8, and both disciplines n=2) participated in stakeholder interviews. Qualitative findings indicated overall positivity in relation to accessibility, functionality, usefulness, design, and increased knowledge of advance care planning. Recommended improvements included shortened content, a comparable website for patients and families, and multilingual translations. Conclusions: The CIPP framework was effectively applied to evaluate the development and end product of an advance care planning website. Although overall findings were positive, further advance care planning website development should consider the recommendations derived from this study