The current study examined the impact of expert witness orientation (researcher or clinical practitioner) and type of testimony (testimony for the prosecution, for the defense, for both prosecution and defense, and no testimony) on mock jurors‟ decisions in a sexual abuse trial. Participants read a summary of a sexual abuse criminal trial based on recovered memory; the summary included expert witness testimony (varied across participants based on the conditions described above). Participants then completed a juror decision making task. Results showed that expert witness testimony provided by a researcher did not impact mock jurors‟ guilt ratings any differently than the expert witness testimony provided by a clinical practitioner. However, type of testimony had a significant effect on jurors‟ guilt ratings. The prosecution witness expert testimony influenced mock jurors‟ decision in favor of the prosecution and testimony by a defense expert influenced the jurors‟ decisions in favor of the defense.

In this paper we evaluate how software testing is affected by the usage of a mock-object, a dummy implementation of a real object, in place of having data in a cloud that is accessed through an API. We define the problems for testing that having data in the cloud brings, which of these problems a mock-object can remedy and what problems there are with testing using the mock-object. We also evaluate if testing using the mock-object can find the same faults as testing against the cloud and if the same code can be covered by the tests. This is done at Blekinge Institute of Technology(BTH) by creating an integration system for the company Cybercom Sweden and Karlskrona Municipality. This integration system is made in C# and works by syncing schedules from Novaschem to a cloud service, Google Calendar. With this paper we show that a mock-object in place of a cloud is very useful for testing when it comes to clean-up, triggering certain states and to avoid query limitations. / I detta arbete utvärderar vi hur programvarutestning påverkas av användandet av ett mock-objekt, en dummy-implementation av ett riktigt objekt, istället för att ha data i ett moln som man kommer åt via ett API. Vi definierar de problem som uppkommer av att ha data i molnet, vilka problem som kan avhjälpas av mock-objektet och vilka problem mock-objektet medför. Vi utvärderar även om testning med ett mock-objekt kan finna samma fel som testning mot molnet och om samma kod kan täckas av testerna. Detta görs på Blekinge Tekniska Högskola(BTH) genom att skapa ett integrationssystem för företaget Cybercom Sweden och Karlskrona Kommun. Integrationssystemet görs i C# och fungerar som så att det synkar scheman från Novaschem till en molntjänst, Google Calendar. Med detta arbete visar vi att ett mock-objekt istället för molnet är väldigt användbart när det kommer till städning efter tester, att utlösa vissa tillstånd och för att undvika begränsningar.

In object oriented programming (OOP) class objects are individual units of code that encapsulate the desired functionality of each object. AOP is an attempt to handle the cross-cutting concerns that represent functionality needed by a class, but is not specific to that class. The cross-cutting functionality is implemented in AOP by using a class-like structure, the aspect. Aspects do not have their own context and as such are dependent upon other objects for their context. By not having their own context it is difficult to test the functionality of aspects. This study investigated the effectiveness of using class interfaces and mock objects to unit test aspects. This was accomplished by having the mock object inherit from the same interface as the base code, so that the mock object could be swapped in for the aspect.

Congenital heart valve disease is one of the most common abnormalities in children, with common valve defects being aortic stenosis, mitral stenosis, and valvular regurgitation. Although adult sized mechanical heart valve (MHV) replacements are widely studied and utilized, there are currently no FDA approved prosthetic heart valves available for the pediatric population. This is due to a variety of reasons such as a limited patient pool for clinical trials, limited valve sizes, and complex health histories in children. Much like adult sized mechanical heart valves, potential complications with pediatric heart valve replacements include thrombosis, blood damage due to high shear stresses, and cavitation. Due to pediatric sized MHVs being much smaller in size than adult MHVs, different fluid dynamic conditions and associated complications are expected. In order to accelerate the approval of pediatric sized heart valves for clinical use, it is important to first characterize and assess the fluid dynamics across pediatric sized heart valves. By understanding the hemodynamic performance of the valve, connections can be made concerning potential valve complications such as thrombosis and cavitation. The overall objective of this study is to better characterize and assess the flow field characteristics of a pediatric sized mechanical heart valve using flow visualization techniques in a mock circulatory loop. The mechanical heart valve chosen for this research was a size 17 mm Bjork-Shiley tilting disc valve, as this is a common size valve used for younger patients with smaller cardiovascular anatomy. The mock circulatory loop used in this research was designed to provide realistic pediatric physiological flow conditions, consisting of a Harvard Apparatus Pulsatile blood pump, venous reservoir, and a heart valve testing chamber. In order to expose the valve to realistic pediatric flow conditions, six unique pump operating conditions were tested that involved pre-determined heart rate and stroke volume combinations. In addition, a modified aortic root model was used to hold the mechanical heart valve in place within the loop and to provide more realistic aortic root geometry. This heart valve chamber was made from a transparent acrylic material, allowing for fluid flow visualization. A traditional Particle Image Velocimetry (PIV) experimental set up was used in order to illuminate the particles seeded within the fluid path, and thus allowing for the capture of sequential images using a high speed camera. The data collected throughout this study consisted of flow rate measurements using an ultrasonic flow meter, and the sequential PIV images obtained from the camera in order to analyze general flow characteristics across the pediatric valve. Such information regarding the flow profile across the valve allowed for conclusions to be made regarding the valve performance, such as average flow velocities and regions of regurgitant flow. By gaining a better understanding of the fluid dynamic profile across a pediatric sized heart valve, this may aid in the eventual approval of pediatric sized mechanical heart valves for future clinical use.

Neste trabalho, com base em representações por matrizes de duas linhas para alguns tipos de partição (algumas já conhecidas e outras novas), identificamos propriedades sugeridas por classificá-las de acordo com a soma dos elementos de sua segunda linha. Esta soma sempre fornece alguma propriedade da partição relacionada. Se considerarmos versões sem sinal de algumas funções Mock Theta, seu termo geral pode ser interpretado como função geradora para algum tipo de partição com restrições. Para retornar aos coeficientes originais, é possível definir um peso para cada matriz e depois somá-las para contá-los. Uma representação análoga para essas partições nos permite observar propriedades sobre elas, novamente por meio de uma classificação referente à soma dos seu elementos da segunda linha. Esta seriação é feita por meio de tabelas criadas pelo software matemático Maple, as quais nos sugerem padrões e identidades relacionadas com outros tipos de partições conhecidas e, muitas vezes, encontrando uma fórmula fechada para contá-las. Tendo as conjecturas obtidas, elas são provadas por meio de bijeções entre conjuntos ou por contagem. / In this work, based on representations by matrices of two lines for some kind of partition (some already known and other new ones), we identify properties suggested by classifying them according to the sum of its second line. This sum always provides some properties of the related partition. If we consider unsigned versions of some Mock Theta Functions, its general term can be interpreted as generating function for some kind of partition with restrictions. To come back to the original coefficients, you can set a weight for each array and so add them to evaluate the coefficients. An analogous representation for partitions allows us to observe properties, again by classificating them according to the sum of its elements on the second row. This classification is made by means of tables created by mathematical software Maple, which suggest patterns, identities related to other known types of partitions and often, finding a closed formula to count them. Having established conjectured identities, all are proved by bijections between sets or counting methods.

In this study, 24 adults without any psychological or neurological disorders participated either in 10 neurofeedback training sessions to increase the amplitude of a frequency band between 12 and 15 Hz (sensorimotor rhythm - SMR) or in ten mock neurofeedback sessions. Pre and post training measures of memory and executive functions were completed, along with quantitative electroencephalography (QEEG) measurements in order to detect changes after the training course. Furthermore, measures of SMR amplitude were taken within and across sessions to determine whether self-regulation of SMR had been achieved. The data analysis performed shows no significant differences in cognitive performance between the group who underwent neurofeedback training and the group who underwent mock neurofeedback training. The groups did not show electrophysiological changes after the training. Additionally, no significant changes in SMR amplitude or percent time above threshold across or within the 10 sessions were found in the experimental group. Moreover, the data showed a tendency, which indicates that the higher the baseline amplitude and absolute power of SMR the less time was spent above threshold during the training and the less increase in SMR amplitude between baseline and training periods. The findings obtained indicate that neurofeedback training did not affect memory, executive functions or the QEEG. The absence of significant changes in SMR amplitude across sessions might reflect failure in learning the neurofeedback task and may account for the lack of cognitive improvement and QEEG changes. The fact that the ability to self-regulate SMR might be dependent on baseline amplitude has important implications in setting thresholds. Setting thresholds according to baseline levels might increase the difficulty in maintaining SMR above threshold when the baseline is higher. Future research should also address whether baseline amplitude has a predictive value in determining successful self-regulation of brain activity.

The American Heart Association's Get With the Guidelines (GWTG) has established measures for how quickly a resuscitation team is to respond in a cardiac arrest with performance of cardiopulmonary resuscitation (CPR) and defibrillation. Two of the core measures for GWTG require initiation of CPR within 1 minute of cardiac arrest and defibrillation within 2 minutes in at least 85% of cases. The problem of interest in this Doctor of Nursing Practice (DNP) project was that the facility had not been able to reach 85% on these 2 measures. The purpose of this project was to achieve nursing response times for CPR and defibrillation to meet the core measures. Using the logic model, the project leader implemented mock code training over an 8-week period on the medical-surgical units. The study design for this project was a nonexperimental, retrospective chart review. Compliance data were obtained from the American Heart Association's GWTG database for the facility before and after implementation of mock code training. The results included a review of 10 cardiac arrest cases that occurred after implementation of training. There was 100% compliance with initiation of first compression within 1 minute of cardiac arrest. However, of 2 cases that required defibrillation, only 1 received the shock within 2 minutes. Quantitative descriptive analysis used percentages and a runs chart to compare response times prior to training with response times after training. The chart showed improvement in the area of first compression in meeting the goal of 85% compliance. As a result, the facility will continue to implement mock code training on a routine basis in its effort to improve patient outcomes, including survival and quality of life.

This study aims to examine the relation between mock-documentary and factual discourse of documentary. By factual discourse it is meant to documentary&rsquo / s claim of representing reality. Within this respect, documentary has its own particular codes and conventions to construct its factual discourse. Mock-documentary, simulates these codes and conventions to create a fictional world. In this study, mock-documentary and its relationship with the most popular modes of documentary is examined. Within this study the earliest examples of mock-documentary and recent examples of the form are compared, and it is stated that with the recent examples of the form the critical approach of mock-documentary has been reduced.

No description available.

Software testing has been integrated within software development life cycle due to its importance in assuring software quality, software safety, and customers' satisfaction. However, problems in software testing are prominent among software developers as system grows in size and complexity. Dependency injection becomes an appealing solution for developers with its practicality to improve software design, improve testability, and enable mock testing technique. The study aims to discover the extent to which the dependency injection facilitates software design and software testing. In addition, the effect of mock practice on testing is also assessed. Metrics for investigation are defined and measured on various aspects of two systems. The two systems are selected and developed based on the same user requirements, development technologies, and methodologies. By comparing the two systems against the investigated metrics, we aim to reveal whether the dependency injection improve the code design. Then four test suites from both systems are evaluated in relation to testability. The results demonstrate that the dependency injection does not seem to improve the code design if comparing on the selected metrics. Even though it does not score better, its effect is evident in other software aspects. The testability of the two systems is similar and suffers from the same problem. Meanwhile, mock helps assist software testing and improve testability. The effect of mock technique can be witnessed, especially when it is applied with other test techniques. Explanations and discussions on these findings are addressed in the paper.