170,025 research outputs found
Hersent M., Zaidman C. — Genre, travail et migrations en Europe
Condon Stéphanie, Simon Patrick. Hersent M., Zaidman C. — Genre, travail et migrations en Europe. In: Population, 59ᵉ année, n°3-4, 2004. pp. 631-632
J. C. Bermejo Barrera, F. J. González García, S. Reboreda Morillo. Los orígenes de la mitología griega,
Bruit-Zaidman Louise. J. C. Bermejo Barrera, F. J. González García, S. Reboreda Morillo. Los orígenes de la mitología griega,. In: Revue de l'histoire des religions, tome 215, n°4, 1998. pp. 511-514
Fougeyrollas-Schwebel D.,Planté C, Riot-Sarcey M., Zaidman C. — Le genre comme catégorie d'analyse. Sociologie, histoire, littérature
Condon Stéphanie, Andro Armelle, Bozon Michel, Brown Elizabeth, Debauche Alice, Ferrand Michèle, Jaspard Maryse, Kateb Kamel, Locoh Thérèse, Moguerou Laure, Pourette Dolorès. Fougeyrollas-Schwebel D.,Planté C, Riot-Sarcey M., Zaidman C. — Le genre comme catégorie d'analyse. Sociologie, histoire, littérature. In: Population, 59ᵉ année, n°1, 2004. pp. 161-163
Fougeyrollas-Schwebel D.,Planté C, Riot-Sarcey M., Zaidman C. — Sciences et genre : l'activité scientifique des femmes. États-Unis, Grande-Bretagne, France
Ferrand Michèle, Andro Armelle, Bozon Michel, Brown Elizabeth, Condon Stéphanie, Debauche Alice, Jaspard Maryse, Kateb Kamel, Locoh Thérèse, Moguerou Laure, Pourette Dolorès. Fougeyrollas-Schwebel D.,Planté C, Riot-Sarcey M., Zaidman C. — Sciences et genre : l'activité scientifique des femmes. États-Unis, Grande-Bretagne, France. In: Population, 59ᵉ année, n°1, 2004. pp. 164-167
How Developers Engage with Static Analysis Tools in Different Contexts
Automatic static analysis tools (ASATs) are instruments that support code quality assessment by automatically detecting defects and design issues. Despite their popularity, they are characterized by (i) a high false positive rate and (ii) the low comprehensibility of the generated warnings. However, no prior studies have investigated the usage of ASATs in different development contexts (e.g., code reviews, regular development), nor how open source projects integrate ASATs into their workflows. These perspectives are paramount to improve the prioritization of the identified warnings. To shed light on the actual ASATs usage practices, in this paper we first survey 56 developers (66% from industry and 34% from open source projects) and interview 11 industrial experts leveraging ASATs in their workflow with the aim of understanding how they use ASATs in different contexts. Furthermore, to investigate how ASATs are being used in the workflows of open source projects, we manually inspect the contribution guidelines of 176 open-source systems and extract the ASATs’ configuration and build files from their corresponding GitHub repositories. Our study highlights that (i) 71% of developers do pay attention to different warning categories depending on the development context; (ii) 63% of our respondents rely on specific factors (e.g., team policies and composition) when prioritizing warnings to fix during their programming; and (iii) 66% of the projects define how to use specific ASATs, but only 37% enforce their usage for new contributions. The perceived relevance of ASATs varies between different projects and domains, which is a sign that ASATs use is still not a common practice. In conclusion, this study confirms previous findings on the unwillingness of developers to configure ASATs and it emphasizes the necessity to improve existing strategies for the selection and prioritization of ASATs warnings that are shown to developers
Glados, a secure access control system
We have created a Secure Access Control System, named Glados. The goal of this system is to limit the access to a building, and separate 'zones' in that building, to authorized persons only. Our primary concerns were security and maintainability. Special care has been taken in identifying possible attack vectors and defending against those. This includes using high-end authentication chips, encryption of communication and centralizing sensitive data. Maintainability was achieved through test-driven development and a modular design.Software EngineeringElectrical Engineering, Mathematics and Computer Scienc
Going Beyond Counting First Authors in Author Co-citation Analysis
The present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
SATT: Tailoring code metric thresholds for different software architectures
Code metric analysis is a well-known approach for assessing the quality of a software system. However, current tools and techniques do not take the system architecture (e.g., MVC, Android) into account. This means that all classes are assessed similarly, regardless of their specific responsibilities. In this paper, we propose SATT (Software Architecture Tailored Thresholds), an approach that detects whether an architectural role is considerably different from others in the system in terms of code metrics, and provides a specific threshold for that role. We evaluated our approach on 2 different architectures (MVC and Android) in more than 400 projects. We also interviewed 6 experts in order to explain why some architectural roles are different from others. Our results shows that SATT can overcome issues that traditional approaches have, especially when some architectural role presents very different metric values than others.Maurício Aniche, Christoph Treude, Andy Zaidman, Arie van Deursen, Marco Aurélio Geros
Automated Fault Localization for Service-Oriented Software Systems
In this thesis, we have focused on applying Spectrum-based Fault Localization (SFL) to diagnose Service-Oriented Systems at runtime. We reused a framework-based online monitoring technique to obtain the service transaction information. We devised a three-phased oracle and combined this with monitoring to detect system failures at runtime. Both monitor and oracle generate component involve- ment and pass/fail information required by SFL. We conducted an experiment with a case system to validate the performance of SFL in diagnosing service-oriented systems. The results show that SFL is able to identify faulty service operations in 73% of the cases correctly. With the preliminary attempt of applying SFL to service-oriented systems, we discovered that the monitoring topology can influence the accuracy of diagnosis for service-oriented systems. Therefore, we applied Genetics Algorithms (GA) to find the optimal monitoring topologies for SFL diagnosis. With the assistance of GA techniques, we have identified the following characteristics of optimal monitoring topologies: \u95 invoking components in isolation \u95 more monitoring points, including the monitoring of inactivity \u95 including the monitoring of the system context \u95 including tracing information Through a careful investigation of the failed diagnoses from the initial step of applying SFL to service-oriented systems, we found that the main reasons for failed diagnoses can be attributed to (1) tight interactions between services and (2) fault intermittency of services. In order to improve the diagnosis, we have proposed two possible solutions to deal with tight interaction. One solution is to increase the monitoring granularity by adding monitors at the code block level in the service implementation. The other solution is to include the monitoring of invocation links between services into the SFL diagnosis. The former solution is able to achieve 100% correct diagnoses, however, it requires the ownership of services to place monitors inside the services. The latter solution can be done with a more realistic set-up and it can also significantly improve the diagnoses. We have also assessed the runtime overhead caused by the diagnosis for service-oriented system. Since the diagnosis engine in our approach is detached from the service-oriented system, the overhead of diagnosis imposed on the running service-oriented system is from monitoring. We measured the monitoring overhead at different levels of granularity, and found out that the monitoring at the service communication level consumes high overhead, whereas the monitoring at the service implementation level is much lower, but highly depends on the number of monitors deployed.Software TechnologyElectrical Engineering, Mathematics and Computer Scienc
- …
