925 resultados para Impact analysis
Resumo:
This study examined in municipalities of Northeast of Brazil with more than one hundred thousand people who incorporation of Oral Health Teams (OHT) into the Family Health Strategy (FHE) the possible impact on oral health indicators. Sought to answer whether implementation OHT brought the best indicators of health problems and coverage, compared to areas without coverage by the FHE through a community trial in parallel, quasi-randomized. In each of the municipalities surveyed were 20 census tracts, 10 were located in areas covered by oral health teams in the ESF and 10 industries in areas not covered. The final sample consisted of 59.221 individuals. We compared oral health indicators related to health problems, access to services and coverage of oral health actions. The analysis strategy was based on the calculation of prevalence ratios and confidence intervals, adjusted for confounding factors through Poisson regression with robust variance. It also has measured the association between an indicator of social inequality for comparison between areas. The best results are associated with indicators of access and coverage of oral health actions at the expense of the indicators of health problems, suggesting a possible maintenance of a traditional model of practice yet. The results also suggest a possible effect of a specific policy in the area of primary care on inequality in access. From the discussions presented throughout this work, we can see that the impact analysis of public policy, obtained by comparing areas with and without the intervention, not only captures the effect on the target population, but other dimensions of organization service and therefore should be understood as one of the analytical possibilities related to the management
Resumo:
Software Product Line (SPL) consists of a software development paradigm, whose main focus is to identify features common and variability among applications in a specific domain. An LPS is designed to attend all products requirements from its product family. These requirements and LPS may have changes over time due to several factors, such as evolution of product requirements, evolution of the market, evolution of SLP process, evolution of the technologies used to develop the products. To handle these changes, LPS should be modified and evolve in order to not become obsolete, and adapt itself to new requirements. The Changes Impact Analysis is an activity that understand and identify what consequences these changes are cause on LPS. Impact Analysis on LPS may be supported by traceability relationships, which identify relationships between artefacts created during all phases of software development. Despite the solutions of change impact analysis based on traceability for software, there is a lack of solutions for assessing the change impact analysis based on traceability for LPS, since existing solutions do not include estimates specific to the artefacts of LPS. Thus, this paper proposes a process of change impact analysis and an tool for assessing the change impact through traceability of artefacts in LPS. For this purpose, we specified a process of change impact analysis that considers artifacts produced during the development of LPS. We have also implemented a tool which allows estimating and identifying artefacts and products of LPS affected from changes in other products, changes in class, changes in features, changes between releases of LPS and artefacts related to changes in core assets and variability. Finally, the results were evaluated through metrics
Resumo:
Mainstream programming languages provide built-in exception handling mechanisms to support robust and maintainable implementation of exception handling in software systems. Most of these modern languages, such as C#, Ruby, Python and many others, are often claimed to have more appropriated exception handling mechanisms. They reduce programming constraints on exception handling to favor agile changes in the source code. These languages provide what we call maintenance-driven exception handling mechanisms. It is expected that the adoption of these mechanisms improve software maintainability without hindering software robustness. However, there is still little empirical knowledge about the impact that adopting these mechanisms have on software robustness. This work addresses this gap by conducting an empirical study aimed at understanding the relationship between changes in C# programs and their robustness. In particular, we evaluated how changes in the normal and exceptional code were related to exception handling faults. We applied a change impact analysis and a control flow analysis in 100 versions of 16 C# programs. The results showed that: (i) most of the problems hindering software robustness in those programs are caused by changes in the normal code, (ii) many potential faults were introduced even when improving exception handling in C# code, and (iii) faults are often facilitated by the maintenance-driven flexibility of the exception handling mechanism. Moreover, we present a series of change scenarios that decrease the program robustness
Resumo:
Includes bibliography
Resumo:
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Resumo:
Pós-graduação em Geologia Regional - IGCE
Resumo:
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Resumo:
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Resumo:
Pós-graduação em Agronomia (Energia na Agricultura) - FCA
Resumo:
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Resumo:
Pós-graduação em Agronomia - FEIS
Resumo:
Pós-graduação em Engenharia Civil - FEIS
Resumo:
Pós-graduação em Engenharia Civil - FEIS