101 |
Effects of Static Stretching on Foot Velocity During the Instep Soccer KickWorkman, Craig D. 01 May 2010 (has links)
The purpose of this study was to assess the acute effects of static stretching on foot velocity at impact with a soccer ball. Eighteen Division I female soccer athletes underwent two test conditions separated by 48 hr. Each condition was randomly assigned and began by placing four retro-reflective markers on bony landmarks of the ankle (total of eight markers, four on each ankle). One condition was the no-stretch condition, in which each participant performed a self-paced jog for 5 min as a warm-up, and then sat quietly for 6 min before performing three maximal instep kicks into a net. The second condition was the stretch condition, which was identical to the no-stretch condition, except the participants performed a series of six randomly ordered stretches instead of sitting quietly for 6 min. Three-dimensional motion analysis was used to quantify the resultant velocity of the head of the 5th metatarsal immediately prior to foot impact with a soccer ball. The results of a dependent t test indicated that there was no significant difference between the no-stretch (18.34 ± 1.29 m/s) and stretch conditions (17.96 ± 1.55 m/s; p = .102, d = .3) Based on these findings, acute stretching performed one time for 30 s before maximal instep soccer kicking has no effect on the resultant foot velocity of Division 1A university female soccer players. Pre-event stretching performed in a like manner may best be prescribed at the discretion of the athlete.
|
102 |
Precise, General, and Efficient Data-flow Analysis for Security Vetting of Android AppsWei, Fengguo 18 June 2018 (has links)
This dissertation presents a new approach to static analysis for security vetting of Android apps, and a general framework called Argus-SAF. Argus-SAF determines points-to information for all objects in an Android app component in a flow and context-sensitive (user-configurable) way and performs data-flow and data dependence analysis for the component. Argus-SAF also tracks inter-component communication activities. It can stitch the component-level information into the app- level information to perform intra-app or inter-app analysis. Moreover, Argus-SAF is NDK/JNI- aware and can efficiently track precise data-flow across language boundary. This dissertation shows that, (a) the aforementioned type of comprehensive app analysis is utterly feasible in terms of computing resources with modern hardware, (b) one can easily leverage the results from this general analysis to build various types of specialized security analyses – in many cases the amount of additional coding needed is around 100 lines of code, and (c) the result of those specialized analyses leveraging Argus-SAF is at least on par and often exceeds prior works designed for the specific problems, which this dissertation demonstrate by comparing Argus-SAF’s results with those of prior works whenever the tool can be obtained. Since Argus-SAF’s analysis directly handles intercomponent and inter-language control and data flows, it can be used to address security problems that result from interactions among multiple components from either the same or different apps and among java code and native code. Argus-SAF’s analysis is sound in that it can assure the absence of the specified security problems in an app with well-specified and reasonable assumptions on Android runtime system and its library.
|
103 |
To inform and engage: museum websites and dynamic delivery of informationZeljkovic, Nada January 2002 (has links)
The World Wide Web has emerged as a powerful communications medium. With the development of new technologies, organizational websites are getting bigger and more complex, using design elements such as sound and motion to engage users' attention. This project will look at how users respond to the ways designers and developers present information on the web in a dynamic form which incorporates sound and motion. The research will focus on evaluating the communicative effectiveness of websites (particularly websites with different degrees of dynamic content in them), and will see if certain ways of presenting dynamic content are more effective than others. The method used will consist of observing users while they try to accomplish specific tasks on selected websites, through interviews, questionnaires and through verbal protocol ('think aloud') analysis. Effectiveness will be measured by such things as how long it takes them to complete each task, how successful they were in finding the necessary information, and the ease of use. Other factors which provide possible explanations for differences in effectiveness will also be measured; these will be drawn from two theoretical bases: communication theory (Fiske, 1982) and social psychology (Ajzen, 1991; Klobas & Morrison, 1999). The outcome of the research will be identification of problem areas associated with the effectiveness of information delivery by dynamic sites. Guidelines for communication designers, information architects and developers of websites, as they evaluate the success of dynamic sites, will be an appendix to the research.
|
104 |
ANALYSE STATIQUE DE LOGICIELS MULTITÂCHES PAR INTERPRÉTATION ABSTRAITEFerrara, Pietro 22 September 2009 (has links) (PDF)
Le but de cette thèse est de présenter une analyse statique générique pour des programmes multitâche écrits en Java.<br />Les programmes multitâche exécutent plusieurs tâches en parallèle. Ces tâches communiquent implicitement par le biais de la mémoire partagée et elles se synchonisent sur des moniteurs (les primitives wait-notify, etc..). Il y a quelques années, les architectures avec double processeurs ont commencé à être disponibles sur le marché à petit prix. Aujourd'hui, presque tous les ordinateurs ont au moins deux noyaux, la tendance actuelle du marché étant de mettre de plus en plus de processeurs par puce. Cette révolution amène également de nouveaux défis en matière de programmation, car elle demande aux développeurs d'implanter des programmes multitâche. Le multitâche est supporté en natif par la plupart des langages de programmation courants, comme Java et C#.<br />Le but de l'analyse statique est de calculer des informations sur le comportement d'un programme, de manière conservative et automatique. Une application de l'analyse statique est le développement d'outils qui aident au débogage des programmes. Plusieurs méthodes d'analyse statique ont été proposées. Nous suivrons le cadre de l'interprétation abstraite, une théorie mathématique permettant de définir des approximations correctes de sémantiques de programmes. Cette méthode a déjà été utilisée pour un large spectre de langages de programmation.<br />L'idée fondamentale des analyseurs statiques génériques est de développer un outils qui puissent être interfacé avec différents domaines numériques et différentes propriétés. Pendant ces dernières années, beaucoup de travaux se sont attaqués à cet enjeu, et ils ont été appliqué avec succès pour déboguer des logiciels industriels. La force de ces analyseurs réside dans le fait qu'une grande partie de l'analyse peut être réutilisée pour vérifier plusieurs propriétés. L'utilisation de différents domaines numériques permet le développement d'analyses plus rapides mais moins précises, ou plus lentes mais plus précises.<br /><br />Dans cette thèse, nous présentons la conception d'un analyseur générique pour des programmes multitâche. Avant tout, nous définissons le modèle mémoire, appelé happens-before memory model. Puis, nous approximons ce modéle mémoire en une semantique calculable. Les modéles mémoire définissent les comportements autorisés pendant l'exé-cution d'un programme multitâche. Commençant par la définition (informelle) de ce modèle mémoire particulier, nous définissons une sémantique qui construit toutes les exécutions finies selon ce modèle mémoire. Une exécution d'un programme multitâche est décrite par une function qui associe les tâches à des séquences (ou traces) d'états. Nous montrons comment concevoir une sémantique abstraite calculable, et nous montrons formellement la correction des résultat de cette analyse.<br />Ensuite, nous définissons et approximons une nouvelle propriété qui porte sur les comportements non-déterministes causés par le multitâche, c'est à dire aux entrelacements arbitraires pendant l'exécution de differentes instructions de lecture. Avant tout, le non déterminisme d'un programme multitâche se définit par une différence entre plusieurs exécutions. Si deux exécutions engendrent des comportements différents dus au valeurs qui sont lues ou écrites en mémoire partagée, alors le programme est non déterministe. Nous approximons cette propriété en deux étapes: dans un premier temps, nous regroupons, pour chaque tâche, la valeur (abstraite) qui peut être écrite dans la mémoire partagée à un point de programme donné. Dans un deuxième temps, nous résumons toutes les valeurs pouvant être écrites en parallèle, tout en nous rapellant l'ensemble des tâches qui pourraient les avoir écrites. à un premier niveau d'approximation, nous introduisons un nouveau concept de déterminisme faible. Nous proposons par ailleurs d'autres manière affaiblir la propriété de déterminisme, par exemple par projection des traces et des états, puis nous définissons une hierarchie globale de ces affaiblissements. Nous étudions aussi comment la présence de conflit sur les accès des données peut affecter le déterminisme du programme.<br />Nous appliquons ce cadre de travail théorique à Java. En particulier, nous définissons une sémantique du language objet de Java, selon sa spécification. Ensuite, nous approximons cette sémantique afin de garder uniquement l'information qui est nécessaire pour l'analyse des programmes multitâche. Le cœur de cette abstraction est une analyse d'alias qui approxime les références afin d'identifier les tâches, de vérifier les accès en mémoire partagée, et de détecter quand deux tâches ont un moniteur commun afin d'en déduire quelles parties du code ne peuvent pas être éxécutées en parallèle.<br />L'analyseur générique qui est décrit ci-dessus a été entierement implanté, dans un outils appelé Checkmate. Checkmate est ainsi le premier analyseur générique pour des programmes multitâche écrits en Java. Des résultats expérimentaux sont donnés et analysés en détails. En particulier, nous étudions la précision de l'analyse lorsqu'elle est appliquée à des schémas courants de la programmation concurrente, ainsi qu'à d'autres exemples. Nous observons également les performances de l'analyse lorsqu'elle est appliquée à une application incrémentale, ainsi qu'à des exemples de références bien connus.<br />Une autre contribution de cette thèse est l'extension d'un analyseur générique existant qui s'appelle Clousot et qui permet de vérifier le non débordement des mémoires tampons. Il s'avère que cette analyse passe à l'échelle des programmes industriels et qu'elle est précise. En résumé, nous présentons une application d'un analyseur statique générique industriel existant pour détecter et prouver une propriété présentant un intérêt pratique, ce qui montre la puissance de cette approche dans le développement d'outils qui soient utiles pour les développeurs.
|
105 |
Tools for static code analysis: A surveyHellström, Patrik January 2009 (has links)
<p>This thesis has investigated what different tools for static code analysis, with anemphasis on security, there exist and which of these that possibly could be used in a project at Ericsson AB in Linköping in which a HIGA (Home IMS Gateway) is constructed. The HIGA is a residential gateway that opens up for the possibility to extend an operator’s Internet Multimedia Subsystem (IMS) all the way to the user’s home and thereby let the end user connect his/her non compliant IMS devices, such as a media server, to an IMS network.</p><p>Static analysis is the process of examining the source code of a program and in that way test a program for various weaknesses without having to actually execute it (compared to dynamic analysis such as testing).</p><p>As a complement to the regular testing, that today is being performed in the HIGA project, four different static analysis tools were evaluated to find out which one was best suited for use in the HIGA project. Two of them were open source tools and two were commercial.</p><p>All of the tools were evaluated in five different areas: documentation, installation & integration procedure, usability, performance and types of bugs found. Furthermore all of the tools were later on used to perform testing of two modules of the HIGA.</p><p>The evaluation showed many differences between the tools in all areas and not surprisingly the two open source tools turned out to be far less mature than the commercial ones. The tools that were best suited for use in the HIGA project were Fortify SCA and Flawfinder.</p><p>As far as the evaluation of the HIGA code is concerned some different bugs which could have jeopardized security and availability of the services provided by it were found.</p>
|
106 |
Code profiling as a design tool for application specific instruction setsSkoglund, Björn January 2007 (has links)
<p>As the embedded devices has become more and more generalized and as their product cycles keeps shrinking the field has opened up for the Application Specific Instruction set Processor. A mix between the classic generalized microcontroller and the specialized ASIC the ASIP keeps a set of general processing instructions for executing embedded software but combines that with a set of heavily specialized instructions for speeding up the data intense application core algorithms. One important aspect of the ASIP design flow</p><p>research is cutting design time and cost. One way of that is automation of the instruction set design. In order to do so a process is needed where the algorithm to be ASIPed is analyzed and critical operations are found and exposed so that they can be implemented in special hardware. This process is called profiling. This thesis describes an implementation of a fine grained source code profiler for use in an ASIP design flow. The profiler software is based on a static-dynamic workflow where data is assembled from both static</p><p>analysis and dynamic execution of the program and then analyzed together in an specially made analysis software.</p>
|
107 |
Analysis of An Uncertain Volatility Model in the framework of static hedging for different scenariosSdobnova, Alena, Blaszkiewicz, Jakub January 2008 (has links)
<p>In Black-Scholes model, the parameters -a volatility and an interest rate were assumed as constants. In this thesis we concentrate on behaviour of the volatility as</p><p>a function and we find more realistic models for the volatility, which elimate a risk</p><p>connected with behaviour of the volatility of an underlying asset. That is</p><p>the reason why we will study the Uncertain Volatility Model. In Chapter</p><p>1 we will make some theoretical introduction to the Uncertain Volatility Model</p><p>introduced by Avellaneda, Levy and Paras and study how it behaves in the different scenarios. In</p><p>Chapter 2 we choose one of the scenarios. We also introduce the BSB equation</p><p>and try to make some modification to narrow the uncertainty bands using</p><p>the idea of a static hedging. In Chapter 3 we try to construct the proper</p><p>portfolio for the static hedging and compare the theoretical results with the real</p><p>market data from the Stockholm Stock Exchange.</p>
|
108 |
Code Profiling : Static Code AnalysisBorchert, Thomas January 2008 (has links)
<p>Capturing the quality of software and detecting sections for further scrutiny within are of high interest for industry as well as for education. Project managers request quality reports in order to evaluate the current status and to initiate appropriate improvement actions and teachers feel the need of detecting students which need extra attention and help in certain programming aspects. By means of software measurement software characteristics can be quantified and the produced measures analyzed to gain an understanding about the underlying software quality.</p><p>In this study, the technique of code profiling (being the activity of creating a summary of distinctive characteristics of software code) was inspected, formulized and conducted by means of a sample group of 19 industry and 37 student programs. When software projects are analyzed by means of software measurements, a considerable amount of data is produced. The task is to organize the data and draw meaningful information from the measures produced, quickly and without high expenses.</p><p>The results of this study indicated that code profiling can be a useful technique for quick program comparisons and continuous quality observations with several application scenarios in both industry and education.</p>
|
109 |
Quasi-static and fatigue behaviour of composite bolted jointsStarikov, Roman January 2001 (has links)
No description available.
|
110 |
Analysis of An Uncertain Volatility Model in the framework of static hedging for different scenariosSdobnova, Alena, Blaszkiewicz, Jakub January 2008 (has links)
In Black-Scholes model, the parameters -a volatility and an interest rate were assumed as constants. In this thesis we concentrate on behaviour of the volatility as a function and we find more realistic models for the volatility, which elimate a risk connected with behaviour of the volatility of an underlying asset. That is the reason why we will study the Uncertain Volatility Model. In Chapter 1 we will make some theoretical introduction to the Uncertain Volatility Model introduced by Avellaneda, Levy and Paras and study how it behaves in the different scenarios. In Chapter 2 we choose one of the scenarios. We also introduce the BSB equation and try to make some modification to narrow the uncertainty bands using the idea of a static hedging. In Chapter 3 we try to construct the proper portfolio for the static hedging and compare the theoretical results with the real market data from the Stockholm Stock Exchange.
|
Page generated in 0.0553 seconds