No description available.

No description available.

No description available.

Syftet med denna empiriska studie var att granska hur sjuksköterskan dokumente-rar smärta på en postoperativ avdelning och hur åtgärder i samband med smärt-lindring följs upp. Studien genomfördes på Universitetssjukhuset i Malmö genom granskning av journaler för 14 patienter som givit sitt samtycke att delta i studien. Analysen resulterade i tre kategorier: god/tillfredsställande, delvis tillfredsställan-de och bristfällig/obefintlig dokumentation. Resultatet av studien visade brister gällande dokumentation av smärta. Avsaknad av användning av visuell analog skala, smärtans karaktär och uppföljning av smärtlindring kunde noteras i ett fler-tal journaler. Bristerna var särskilt uttalade i fråga om dokumentation av uppföljning. Vidare forskning på området är angelägen för att kunna ta itu med problemet och i framtiden bör sjuksköterskan få fördjupa sina kunskaper i utbildningen eller på sin arbetsplats. / The aim of this empirical study was to examine how nurses document pain in a postoperative unit and the follow up of the alleviation of pain. The study was car-ried out in Malmö University Hospital, Sweden, through examining journals from 14 patients whom agreed to participate. The analyse identified three categories: good/satisfying, partly satisfying and deficient/non-existing documentation. Fur-thermore the study showed qualitative shortages concerning documentation of pain e.g. Lack of using a pain scale, pain character and follow up of alleviation of pain could be seen in many journals. Further research in this area is needed to be able to handle the problem and in service training as well as increased focus on the documentation problems in basic nurse training is recommended.

No description available.

No description available.

The estimation of standard errors is essential to statistical inference. Statistical variability is inherent within data, but is usually of secondary interest; still, some options exist to deal with this variability. One approach is to carefully model the covariance structure. Another approach is robust estimation. In this approach, the covariance structure is estimated from the data. White (1980) introduced a biased, but consistent, robust estimator. Long et al. (2000) added an adjustment factor to White's estimator to remove the bias of the original estimator. Through the use of simulations, this project compares restricted maximum likelihood (REML) with four robust estimation techniques: the Standard Robust Estimator (White 1980), the Long estimator (Long 2000), the Long estimator with a quantile adjustment (Kauermann 2001), and the empirical option of the MIXED procedure in SAS. The results of the simulation show small sample and asymptotic properties of the five estimators. The REML procedure is modelled under the true covariance structure, and is the most consistent of the five estimators. The REML procedure shows a slight small-sample bias as the number of repeated measures increases. The REML procedure may not be the best estimator in a situation in which the covariance structure is in question. The Standard Robust Estimator is consistent, but it has an extreme downward bias for small sample sizes. The Standard Robust Estimator changes little when complexity is added to the covariance structure. The Long estimator is unstable estimator. As complexity is introduced into the covariance structure, the coverage probability with the Long estimator increases. The Long estimator with the quantile adjustment works as designed by mimicking the Long estimator at an inflated quantile level. The empirical option of the MIXED procedure in SAS works well for homogeneous covariance structures. The empirical option of the MIXED procedure in SAS reduces the downward bias of the Standard Robust Estimator when the covariance structure is homogeneous.

Current design theory sets out many rules and guidelines for designers, but good design is still difficult to replicate. Often the design principles found in the manuals are misapplied, resulting in designs that (1) do not fulfill their purpose and (2) disrupt the clarity of information. This thesis will review and provide experimental data supporting a model of visual form/visual purpose connections based on the semiotic of C.S. Peirce. This model was first used by Amare and Manning (2005, 2006, 2007, 2008, 2009) to evaluate and explain both effective and ineffective visual information design. This thesis will extend their approach, reporting on the results of four experiments to test the aesthetic appeal and information retention from various visual designs. The four experiments presented in this thesis show that viewer's ability to recall information does not coincide with designs that they find the most visually stimulating or visually pleasing. High indicative contrasts allow for higher retention rate, but those contrasts do not necessarily conform to viewer's aesthetic preferences. Low indicative contrast options have a lower retention rate, but are preferred aesthetically by viewers. Peircean analysis accounts for this disconnect between usability and preference and can help designers find the balance that is needed between these competing purposes in visual information design.

Empirical research is inexact and error-prone leading researchers to agree that replication of experiments is a necessary step to validating empirical results. Unfortunately, replicating experiments requires substantial investments in manpower and time. These resource requirements can be reduced by incorporating component reuse when building tools for empirical experimentation. Bokeo is an initiative within the Sequoia Lab of the BYU Computer Science Department to develop a platform to assist in the empirical study of software engineering. The i3Persistence Framework is a component of Bokeo which enables researchers to easily build and rapidly deploy tools for empirical experiments by providing an easy-to-use database management service. We introduce the i3Persistence Framework of Bokeo to assist in the development of software to replicate experiments and conduct studies on data from open-source repositories.

Utilizing immutability is considered to have many desired benefits when it comes to software development and reasoning about programs. It is also one of the core principles of functional programming, and many programming languages have support for specifying immutability. Developers can by specifying immutability write code that, for example, prevent program state from being unintentionally mutated. The Scala programming language is a functional and object-oriented language where developers can specify immutability with reassignable and non-reassignable variables. The type system in Scala has no built-in support for developers to express the fact that a type is immutable, immutability is instead by convention and considered best practice. However, knowledge about the immutability usage and how prevalent it is in real-world Scala code are until this point non-existent.            This project presents an immutability analysis and evaluation of six small-to-large open source projects written in Scala providing empirical data on immutability usage. The analysis investigates the immutability property of templates, where a template refers to one of Scala's different class types, on three distinct properties: shallow, conditionally deep and deep immutability, where deep is the strongest immutability property. The analysis works as a plug-in for the Scala compiler that statically analyzes the source code of projects. We report immutability statistics for each evaluated project, including three widely used projects, Scala's standard library, Akka's actor framework and ScalaTest. Explanations to why stronger immutability properties do not hold are also provided. The analysis show that the majority of templates for each project satisfied an immutability property and were not classified as mutable. Because each analyzed project had templates that were assumed to be mutable, as they were unreachable by our analysis, there could potentially be more templates that satisfy an immutability property. Inheritance is shown to be an important factor when it comes to a template's immutability and mutability was found to be lower for the template types case class and singleton object. This can be seen as intended by the designers of Scala, indicating that these type of class abstractions help programmers utilize immutability. Our results show that immutability is frequently used in Scala and the high degree of immutability usage could be due to the functional nature of the language. / Att använda immuterbar (oföränderlig) data anses ha många önskvärda fördelar när det kommer till utveckling av program och att kunna resonera om dess funktionalitet. Immuterbar data är också en viktig princip inom funktionell programmering och många språk har idag stöd för att ange immuterbarhet. Utvecklare kan i kod ange ifall data ska vara immuterbar för att till exempel förhindra ett programtillstånd från att oavsiktligt förändras. Programmeringsspråket Scala är ett funktionellt och objektorienterat språk där utvecklare kan ange immuterbarhet med två typer av variabler, en som är tilldelningsbar och en som är icke-tilldelningsbar. Typsystemet i Scala har inget inbyggt stöd för utvecklare att uttrycka det faktum att en typ är immuterbar, att använda immuterbarhet är i stället konvention och anses vara den bästa metoden. Men uppgifter om hur immuterbarhet egentligen används i riktiga Scala projekt har fram tills nu inte varit tillgängligt. Detta projekt presenterar en immuterbarhetsanalys och en utvärdering av sex små till stora projekt med öppen källkod skrivna i programmeringsspråket Scala. Analysen undersöker immuterbarhetsegenskaper hos Scalas olika typer av klasser med avseende på tre olika egenskaper: ytlig, villkorligt djup och djup immuterbar, där djup är den starkaste immuterbarhetsegenskapen. Analysen fungerar som ett tillägg för Scalas kompilator och utfärdar en statisk analys av källkoden för ett projekt. Statistik om immuterbarhet för varje projekt redovisas och utvärderas, bland annat tre välkända och populära kodbaser, Scalas standard bibliotek, Akka’s actor ramverk och ScalaTest. Förklaringar till varför klasser inte uppfyller en immuterbarhetsegenskap visas också. Analysen visar att majoriteten av alla klasser i projekten har en immuterbarhetsegenskap och var inte klassificerade som muterbara. Eftersom varje projekt hade klasser som antogs vara muterbara för att dessa inte var nåbara för våran analys så kan det potentiellt finnas fler klasser som har en immuterbarhetsegenskap. Vad en klass ärver visar sig vara en viktig faktor när det kommer till vilken typ av immuterbarhetsegenskap den har. Muterbarhet visade sig vara lägre för klasser som är av typen case class and singleton object vilket kan anses vara avsett av Scalas skapare, då dessa klass abstraktioner hjälper programmerare att använda immuterbarhet. Resultaten visar att immuterbarhet används flitigt i Scala och den höga användningsgraden kan vara på grund av att det är ett funktionellt språk.