Research emphasises that effective and efficient end-user training is a vital component of the successful utilization of computer technology and that individual differences (e.g., learning styles, cognitive reasoning schemata) may effect the outcomes of end-user training. This study investigates the relationships between end users' Motivational Intent to use computer technology and individual differences. End users' Motivational Intent to use computer technology is significantly different for between-subjects grouped according to their level of anxiety (i.e., positive, neutral, negative). The empirical results indicate that end users' scholastic ability is an important predictor of the incremental change over time to end users' Motivational Intent to use computer technology. End users' learning styles impact the incremental change over time to end users' Motivational Intent to use computer technology. The results suggest that the tailoring of end-user training methods, techniques and materials to accomodate individual differences may be beneficial and worthwhile. / x, 99 leaves : ill. ; 28 cm.

Thesis (D. Min.)--Southwestern Baptist Theological Seminary, 1987. / Bibliography: leaves 305-310.

Thesis (Ed. D.)--University of Alabama, 1991. / eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 111-117).

Thesis (Ed. D.)--University of Alabama, 1991. / Includes bibliographical references (leaves 111-117).

Master-Arbeit Univ. St. Gallen, 2008.

Thesis (Ph. D.)--Oregon State University, 2007. / Printout. Includes bibliographical references (leaves 192-202). Also available on the World Wide Web.

Software-defined Networking (SDN) enables flexible network management, but as networks evolve to a large number of end-points with diverse network policies, higher speed, and higher utilization, abstraction of networks by SDN makes monitoring and debugging network problems increasingly harder and challenging. While some problems impact packet processing in the data plane (e.g., congestion), some cause policy deployment failures (e.g., hardware bugs); both create inconsistency between operator intent and actual network behavior. Existing debugging tools are not sufficient to accurately detect, localize, and understand the root cause of problems observed in a large-scale networks; either they lack in-network resources (compute, memory, or/and network bandwidth) or take long time for debugging network problems. This thesis presents three debugging tools: PathDump, SwitchPointer, and Scout, and a technique for tracing packet trajectories called CherryPick. We call for a different approach to network monitoring and debugging: in contrast to implementing debugging functionality entirely in-network, we should carefully partition the debugging tasks between end-hosts and network elements. Towards this direction, we present CherryPick, PathDump, and SwitchPointer. The core of CherryPick is to cherry-pick the links that are key to representing an end-to-end path of a packet, and to embed picked linkIDs into its header on its way to destination. PathDump is an end-host based network debugger based on tracing packet trajectories, and exploits resources at the end-hosts to implement various monitoring and debugging functionalities. PathDump currently runs over a real network comprising only of commodity hardware, and yet, can support surprisingly a large class of network debugging problems with minimal in-network functionality. The key contributions of SwitchPointer is to efficiently provide network visibility to end-host based network debuggers like PathDump by using switch memory as a "directory service" - each switch, rather than storing telemetry data necessary for debugging functionalities, stores pointers to end hosts where relevant telemetry data is stored. The key design choice of thinking about memory as a directory service allows to solve performance problems that were hard or infeasible with existing designs. Finally, we present and solve a network policy fault localization problem that arises in operating policy management frameworks for a production network. We develop Scout, a fully-automated system that localizes faults in a large scale policy deployment and further pin-points the physical-level failures which are most likely cause for observed faults.

No description available.

Many organizations such as the Institute of Medicine, the World Health Organization and the National Consensus Project for Quality Palliative Care have identified the need for equitable access to palliative and end-of-life care (Ferrell, Coyle, & Paice, 2015). However, in many rural areas of the world, including rural Wyoming, patients at end-of-life are cared for in acute care settings where nurses have not received specialized training and education on evidence based end-of-life care. The aim for this DNP project was to assess rural registered nurses' perceptions of competencies important in end-of-life nursing practice (Coyne & White, 2011). A 32-item survey developed by White and Coyne (2011) was adapted for use in a rural critical access hospital to determine content priorities and educational needs of generalist nurses in a rural setting, regarding providing palliative and end-of-life care. A purposive sample of 16 nurses in a rural critical access hospital in Wheatland, WY, who care for patients at end-of-life, completed the survey. Only one-third of the nurses surveyed reported receiving any type of end-of-life care education in the prior two years. Similar to findings from the study completed in 2011 in an urban area, symptom management, talking to patients and families about death and dying, and pain control were the highest ranking core competencies. Nurses who did report receiving education in end-of-life care still felt inadequately prepared to talk to patients and families about dying, and this needs assessment identified that educational gaps are evident regarding provision of end-of-life nursing care in rural settings. The information gleaned from this survey will be used to design an educational program to disseminate evidence based practice guidelines regarding providing quality end-of-life care using ELNEC (End-of-Life Nursing Education Consortium) modules based on the findings of the needs assessment survey

ITC/USA 2011 Conference Proceedings / The Forty-Seventh Annual International Telemetering Conference and Technical Exhibition / October 24-27, 2011 / Bally's Las Vegas, Las Vegas, Nevada / Today's telemetry systems need to be highly configurable and easily extensible to support a constantly growing number of data acquisition/transmitting components from different manufacturers. One way to achieve this goal is through a standardized descriptive language that can define the system structure as well as end-node devices. The integrated Network Enhanced Telemetry (iNET) program has explored such a possibility by creating a series of standards to define how devices are configured and interoperate with each other. As one of the standards created by the iNET program, the Metadata Description Language (MDL) specifies a common interchange language that defines and configures a Telemetry Network System (TmNS). MDL Instance Documents are used to exchange test requirements, data formats and configuration information among the devices within a TmNS system. MDL, together with other standards created in the iNET program, serve as a foundation for assembling a modern telemetry system. This paper starts with an overview of the MDL-based system description architecture. A typical configuration workflow of an MDL-based system is then described. iNET functionality implementations for new and legacy devices are used as examples to illustrate the power of MDL-based design, as well as the challenges and issues associated with the implementation of the MDL standard. We explain and evaluate the design decisions for a new product, the L-3 NetDAS Recorder, as the case study. We also discuss how a legacy Data Acquisition Unit (DAU) acting as an LTC Data Source Unit can be updated to support MDL based iNET functionality. Our practice shows that more efficient data acquisition systems can be designed and implemented using the metadata definition language as a core tool for equipment and system description. We conclude the paper with design tradeoffs and discussions.