• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 3
  • 2
  • 2
  • 1
  • 1
  • 1
  • Tagged with
  • 11
  • 11
  • 6
  • 4
  • 4
  • 4
  • 3
  • 3
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

Uppföljningsparametrar vid förbättringsprojekt : En fallstudie inom Laboratoriemedici

Norlund, Lena January 2013 (has links)
Enligt Socialstyrelsens föreskrifter om ledningssystem för kvalitet och patientsäkerhet i hälso- och sjukvården, SOSFS 2005:12, krävs det av vårdgivaren att denne arbetar efter mål. Att formulera mål inom hälso- och sjukvården kräver eftertanke. Målen måste vara mätbara och inkludera flera olika delar av verksamheten. Varje förbättringsprojekt är unikt och bör relateras till de resurser som avsatts. Ett stort problem vid kontinuerlig uppföljning är att välja ut parametrar som ger tillräcklig information och är lätta att skapa. Här krävs mer utvecklade datasystem och även integrering mellan befintliga datasystem  I uppsatsen diskuteras med vilka parametrar man kan utvärdera ett förbättringsprojekt inom laboratoriemedicin. Det finns för närvarande inte några standardiserade kvalitetsparametrar inom klinisk kemi. De parametrar som i denna undersökning visade sig vara mest lämpliga att använda kontinuerligt i det korta perspektivet var svarstider, personalresurser och reagenskostnader. I det längre perspektivet kan ovanstående data kombineras till indikatorer som visar kostnad per analyspoäng och analyspoäng per årsarbetare. De indikatorer som kan få användning först när datasystem utvecklas är data från avvikelsesystem och analyskommentarer som visar t.ex. att svar inte har kunnat lämnas ut. / According to the National Board of Health and Welfare, SOSFS 2005:12, it is required that the caregiver adheres to his work through following stated objectives. Formulating goals in health care requires careful consideration. Goals must be measurable and include many different aspects of the project. Each improvement project is unique and should be directly related to the resources allocated to the project. A major problem for continuous monitoring is to select parameters that provide sufficient information and are easy to produce. This requires more advanced computer systems and integration with existing computer systems. The paper discusses the parameters an improvement project in laboratory medicine can evaluate its results after. There are currently no standardized quality parameters in clinical chemistry. The parameters used in this study that proved to be the most suitable to be used continuously in the short term was the response times, staffing and reagent costs. In the long term, the above data are combined with indicators that show cost per analysis score and analysis points per full-time employees. The indicator that may be used when the computer system is developed is deviation systems and analytical comments that show for example that a response has not been disclosed.
2

Process Evaluation & Improvement

Alsallout, Abdelrahman, Kallungal Khalid, Khaja January 2022 (has links)
This thesis was conducted to analyze and investigate improvement methods for the testing process of steam sterilizers at Getinge AB.Getinge is a leading MedTech multinational company based in Sweden. Steam sterilizer is one of their prominent products. A series of testing must be done before handing over the product to the customer, which mainly requires water and steam as consumable resources. The intention of this project is to find improvement methods or optimization techniques for the testing process and reduce the consumption of resources which would significantly impact the production lead time and cost. Upon the careful examination of the testing process it has been noticed that a significant amount of pure water with heat content has been wasted during the testing process, which could be recirculated/ reused, and the heat could be regenerated for useful purposes. The proposed optimization suggestions through this project are a thermally stratified tank which could handle cold and hot water as the testing process needs the supply of both. Majority of the faults during testing are identified in software implementation and a few in mechanical. A dummy testing is recommended to identify the faults in the implementation of the software without the need of consumable resources. A few methods to tackle mechanical faults are discussed further in this report. When implementing these optimization suggestions, it would drastically improve the testing process by reducing the consumption of resources like water, steam, natural gas, time, and labor.
3

Avaliação de abordagens de gestão do conhecimento aplicadas a um processo de teste de software enxuto

Silva, Ana Eliza Pedroso da 16 June 2015 (has links)
Submitted by Luciana Sebin (lusebin@ufscar.br) on 2016-10-10T18:55:46Z No. of bitstreams: 1 DissAEPS.pdf: 9093309 bytes, checksum: 1d310c56dd7bbae26966b175642a9775 (MD5) / Approved for entry into archive by Marina Freitas (marinapf@ufscar.br) on 2016-10-13T20:33:03Z (GMT) No. of bitstreams: 1 DissAEPS.pdf: 9093309 bytes, checksum: 1d310c56dd7bbae26966b175642a9775 (MD5) / Approved for entry into archive by Marina Freitas (marinapf@ufscar.br) on 2016-10-13T20:33:13Z (GMT) No. of bitstreams: 1 DissAEPS.pdf: 9093309 bytes, checksum: 1d310c56dd7bbae26966b175642a9775 (MD5) / Made available in DSpace on 2016-10-13T20:33:23Z (GMT). No. of bitstreams: 1 DissAEPS.pdf: 9093309 bytes, checksum: 1d310c56dd7bbae26966b175642a9775 (MD5) Previous issue date: 2015-06-16 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES) / Context: A well-defined testing process is necessary to ensure that the required activities are conducted effectively, supported by maturity models such as TMMi. Even so, for this activities results have real impact on the quality and reliability of the produced artefacts, is fundamental manage the knowledge belonging to the involved individuals. In this context, Knowledge Management (KM) is essential to help software testing professionals acquire and disseminate individual and group expertise. However, existing KM approaches for software testing are still incipient and are driven by different key concepts, such as feedback, lessons learned and knowledge documents. Objective: This work investigates the applicability degree of KM approaches in a streamlined software testing process, from the point of view of professionals with experience in leadership and testing team management in Brazilian companies. Method: A literature search allowed us to identify three KM frameworks for software testing processes. Based on them, we devised their underlying KM processes, upon which we performed two evaluations by means of a critical, in-depth analysis and a survey. An additional investigation explored the combination of the three KM key concepts in a single KM approach for software testing. All evaluations relied on the opinion of experienced software testing professionals. Results: Our results indicate the most applicable KM process, among to the three addressed in our study, to support testing teams in their activities. Such process relies on the concept of feedback provided throughout the software testing lifecycle. Conclusion: Different key concepts applied in KM process leads to diverging opinions regarding their applicability, in the particular scenario of software testing. Combining such concepts into a single KM process may not yield a better solution, possibly due to the augmented complexity and required effort to manage knowledge within testing teams. / Contexto: Para que a atividade de teste seja conduzida de maneira eficaz, deve-se possuir processos bem definidos e apoiados por modelos de maturidade como, por exemplo, o TMMi. Entretanto, para que os resultados obtidos tenham real impacto na qualidade e confiabilidade dos artefatos produzidos, ´e fundamental que exista a administração do conhecimento pertencente aos indivíduos envolvidos. Neste contexto, a Gestão do Conhecimento ´e essencial para ajudar os profissionais de teste de software a adquirirem e compartilharem o conhecimento individual e de grupo. Contudo, ressalta-se que as abordagens de Gestão do Conhecimento para teste de software ainda são incipientes e movidas por diferentes conceitos-chave, tais como feedback, lições aprendidas e documentos de conhecimento. Objetivo: O objetivo deste trabalho é investigar o grau de aplicabilidade de abordagens de Gestão do Conhecimento aplicadas em um processo de teste de software enxuto, segundo o ponto de vista de profissionais com experiência em liderança e gestão de equipes de teste em empresas brasileiras. Metodologia: Por meio de uma pesquisa da literatura, foram identificados três frameworks de Gestão do Conhecimento aplicados em teste de software, e a partir destes foram elaborados três processos de Gestão do Conhecimento. Estes processos de Gestão do Conhecimento foram avaliados por dois métodos, uma Análise Crítica aprofundada e um Survey, tendo como referencial um processo de teste enxuto. Uma avaliação adicional analisou a viabilidade da combinação dos conceitos-chave dos três processos elaborados em um único processo de Gestão do Conhecimento. Todas as avaliações empreendidas contaram com a participação de profissionais com experiência em liderança e gestão de equipes de teste. Resultados: As avaliações realizadas indicam o processo de Gestão do Conhecimento mais aplicável, dentre os três investigados neste trabalho, para apoiar as atividades de uma equipe de teste. Tal processo ´e fundamentado na utilização de feedback ao longo de todo o ciclo de teste de software. Conclusão: A junção de diferentes conceitos-chave aplicados em um processo de Gestão do Conhecimento leva a opiniões divergentes, particularmente em um cenário de teste de software. Combinar estes conceitos em um único processo pode não produzir uma solução melhorada, possivelmente devido à maior complexidade e esforço necessários para gerenciar o conhecimento dentro das equipes de teste.
4

FreeTest 2.0: uma evolução do método FreeTest para a melhoria no processo de teste de software em micro e pequenas empresas

Louzada, Jailton Alkimin 11 August 2017 (has links)
Submitted by Franciele Moreira (francielemoreyra@gmail.com) on 2017-09-11T13:42:06Z No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) / Approved for entry into archive by Luciana Ferreira (lucgeral@gmail.com) on 2017-09-15T15:43:54Z (GMT) No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) / Made available in DSpace on 2017-09-15T15:43:54Z (GMT). No. of bitstreams: 2 Dissertação - Jailton Alkimin Louzada - 2017.pdf: 5226619 bytes, checksum: bb291ad68acd8cf80fcb2c6c2392c596 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) Previous issue date: 2017-08-11 / The Information Technology (I.T) market is growing. In the age of information, world economies have been investing more and more in the services market. Within this competitive scenario, software testing is an important component for raising the quality of software developed in Brazil and in the global competitiveness cenario. However, Small and medium-sized enterprises (SMEs) have limited resources for investments in software testing maturity processes, tools and models in their business. Faced with this, this work has as main proposal to produce an apparatus to improve the process of software testing for SMEs. Objective: As the main objectives, this study proposed a more update version of the FreeTest 1.0 process, as well as practical instructions on how to implement the activities suggested in the process, all this formatted in a new process and a wizard respectively. Methodology: In order to fulfill the objectives of this work, the FreeTest 2.0 process was created as an improvement of the FreeTest Method process, focused mainly on Agile techniques, DevOps and aligned with the SMEs ecosystem. And the FreeTest Wizard, which consists of a deployment guide that supports the implementation of the process in a didactic, dynamic and flexible way. Another contribution of this work was the creation of support tools to disseminate this knowledge and content management, in this case the creation of a web platform, distributed free of charge and in the format "as a Service". Finally, the results and conclusions can be seen in the final chapter of this work. / O mercado de Tecnologia da Informação (T.I.) é crescente. Na era da informação, as economias mundiais investem cada vez mais no mercado de Serviços. Dentro deste cenário competitivo, o teste de software é um importante componente para elevação da qualidade do software desenvolvido no Brasil e sua competitividade mundial. Contudo, as Micro e Pequenas Empresas (MPEs) possuem recursos limitados para investimentos em processos, ferramentas e modelos de maturidade de teste de software em seus negócios. Diante disto, este trabalho tem como proposta principal produzir um aparato para melhoria do processo de teste de software para MPEs. Objetivo: Como objetivos principais, este estudo propôs uma versão mais atualizada do processo FreeTest 1.0, bem como instruções práticas de como implantar as atividades sugeridas no processo, tudo isso formatado em um novo processo e um guia de implantação, respectivamente. Metodologia: Com o propósito de cumprir os objetivos almejados neste trabalho foram criados: 1) o processo FreeTest 2.0 como uma melhoria do processo do FreeTest 1.0, focado principalmente em técnicas Ágeis, DevOps e alinhado ao ecossistema das MPEs; e 2) o FreeTest Wizard, que consiste em um guia de implantação que apoia a implantação do processo de forma didática, dinâmica e flexível. Outra contribuição deste trabalho foi a criação de ferramentas de apoio para disseminação deste conhecimento e gestão dos conteúdos, neste caso, a criação de uma plataforma web distribuída de forma gratuita e no formato "as a Service". Por fim, os resultados e conclusões serão vistos no capítulo final deste trabalho.
5

Teste funcional sistemático estendido: uma contribuição na aplicação de critérios de teste caixa-preta / Systematic Functional Test Extended: A Contribution to the Application of Criteria Black Box Testing

Vidal, Adriana Rocha 19 April 2011 (has links)
Submitted by Cássia Santos (cassia.bcufg@gmail.com) on 2014-08-06T11:56:33Z No. of bitstreams: 2 license_rdf: 23148 bytes, checksum: 9da0b6dfac957114c6a7714714b86306 (MD5) Teste_funcional_sistematico_estendido_uma_contribuicao_na_aplicacao_de_criterios_de_teste_caixa_preta.pdf: 6570768 bytes, checksum: 986a111f01281c84429d66513d0a3a54 (MD5) / Made available in DSpace on 2014-08-06T11:56:33Z (GMT). No. of bitstreams: 2 license_rdf: 23148 bytes, checksum: 9da0b6dfac957114c6a7714714b86306 (MD5) Teste_funcional_sistematico_estendido_uma_contribuicao_na_aplicacao_de_criterios_de_teste_caixa_preta.pdf: 6570768 bytes, checksum: 986a111f01281c84429d66513d0a3a54 (MD5) Previous issue date: 2011-04-19 / Building software involves a process composed of activities and methods. Even following these activities and using the proposed methods the resultant product may have some deviation with respect to its functional and nonfunctional requirements, not corresponding to the expected features. To minimize such problems, the test activity aims to ensure both the construction of the correct product and its correct construction. Since testing is considered a costly activity, research are conducted aiming at to make it feasible. This work ts in this context, in order improve the selection of test cases, thus increasing the quality of software products and the performance of testing guideline. It is interesting to note that, testing guideline is a fundamental artifact of the testing process and consists of test cases that, by de nition, execute a particular functionality of the program or check the suitability of the product over its speci ed requirements. Since the quality of the selected test cases have a great impact on the quality of the nal product, this work introduces the Extended Systematic Functional Test (ESFT) as a way to systematize the development and selection of test cases based on functional testing. A web system and a testing guideline used in certi cation were assessed using the ESFT in order to demonstrate the applicability and possible contributions of its use in terms of defect detection. The results are promising since the systematization, increases the number of selected test data, improves the detection of defects, and allow to justify why a particular test data is selected based on functional criteria. / A construção de um software envolve um processo composto de atividades e métodos. Mesmo seguindo tais atividades e utilizando os métodos propostos, um produto infiel aos requisitos funcionais e não funcionais pode ser gerado, não correspondendo as funcionalidades esperadas. Para amenizar tais problemas, a atividade de teste visa a assegurar tanto a construção do produto correto quanto a sua correta construção. Por ser uma atividade considerada onerosa, pesquisas para reduzir os custos da aplicação dos testes são realizadas. Este trabalho se enquadra nesse contexto, objetivando melhorar a seleção de casos de testes, aumentando assim, a qualidade de produtos de software e o desempenho de roteiros de teste. E interessante ressaltar que, roteiro de teste e um artefato fundamental do processo de testes e e constituído por casos de testes que, por definição, executam uma funcionalidade particular do programa ou verificam a adequação do produto em relação aos requisitos especificados. Uma vez que a qualidade dos casos de testes selecionados impacta fortemente na qualidade do produto final, este trabalho apresenta o Teste Funcional Sistemático Estendido(TFSE) como forma de sistematizar a elaboração e seleção de casos de testes, adotando critérios da técnica de teste funcional para essa finalidade. Um sistema web e um roteiro de teste utilizado em certificações foram avaliados utilizando o TFSE visando a demonstrar a aplicabilidade do mesmo e as possíveis contribuições de sua utilização em termos de detecção de defeitos. Os resultados obtidos são promissores uma vez que a sistematização, aumenta o numero de dados de teste selecionados, melhora a capacidade de detecção dos defeitos, e permitir justificar o por quê da seleção de determinado dado de teste com base em critérios funcionais.
6

Computer-aided applications in process plant safety

An, Hong January 2010 (has links)
Process plants that produce chemical products through pre-designed processes are fundamental in the Chemical Engineering industry. The safety of hazardous processing plants is of paramount importance as an accident could cause major damage to property and/or injury to people. HAZID is a computer system that helps designers and operators of process plants to identify potential design and operation problems given a process plant design. However, there are issues that need to be addressed before such a system will be accepted for common use. This research project considers how to improve the usability and acceptability of such a system by developing tools to test the developed models in order for the users to gain confidence in HAZID s output as HAZID is a model based system with a library of equipment models. The research also investigates the development of computer-aided safety applications and how they can be integrated together to extend HAZID to support different kinds of safety-related reasoning tasks. Three computer-aided tools and one reasoning system have been developed from this project. The first is called Model Test Bed, which is to test the correctness of models that have been built. The second is called Safe Isolation Tool, which is to define isolation boundary and identify potential hazards for isolation work. The third is an Instrument Checker, which lists all the instruments and their connections with process items in a process plant for the engineers to consider whether the instrument and its loop provide safeguards to the equipment during the hazard identification procedure. The fourth is a cause-effect analysis system that can automatically generate cause-effect tables for the control engineers to consider the safety design of the control of a plant as the table shows process events and corresponding process responses designed by the control engineer. The thesis provides a full description of the above four tools and how they are integrated into the HAZID system to perform control safety analysis and hazard identification in process plants.
7

Qualité de la conception de tests logiciels : plate-forme de conception et processus de test / Quality of the design of test cases for automotive software : design platform and testing process

Awedikian, Roy 06 February 2009 (has links)
L’électronique dans les voitures devient de plus en plus complexe et représente plus de 30% du coût global d’une voiture. Par exemple, dans une BMW série 5 modèle 2008, on peut trouver jusqu’à 80 calculateurs électroniques communiquant ensemble et représentant aux alentours de 10 millions de lignes de code logiciel. Face à cette montée en complexité, les constructeurs et équipementiers électroniques de l’automobile s’intéressent de plus en plus à des méthodes efficaces de développement, vérification et validation de modules électroniques. Plus précisément, ils focalisent leurs efforts sur la partie logicielle de ces modules puisqu’elle est à l’origine de plus de 80% des problèmes détectés sur ces produits. Dans ce contexte, nous avons mené un travail de recherche dont l’objectif est de proposer une approche globale d’amélioration de la qualité des logiciels embarqués dans les véhicules. Notre recherche part d’un audit des processus et outils actuellement utilisés dans l’industrie électronique automobile. Cet audit a permis d’identifier des leviers potentiels d’amélioration de la qualité logicielle. En se basant sur les résultats de l’audit et en tenant compte de la littérature dans le domaine de la qualité logicielle, nous avons proposé une approche globale de conception de cas de test pour les produits logiciels. En effet, nous avons développé une plateforme de génération automatique de tests pour un produit logiciel. Cette plateforme consiste à modéliser les spécifications du produit logiciel pour le simuler lors de tests, à se focaliser sur les tests critiques (ayant une forte probabilité de détecter des défauts) et à piloter la génération automatique des tests par des critères de qualité ; telles que la couverture du code et de la spécification mais aussi le coût des tests. La génération de tests critiques est rendue possible par la définition de profils d’utilisation réelle par produit logiciel, ainsi que par la réutilisation des défauts et des tests capitalisés sur des anciens projets. En plus des aspects algorithmiques du test logiciel, notre approche prend en compte des aspects organisationnels tels que la gestion des connaissances et des compétences et la gestion de projet logiciel. Notre approche a été mise en œuvre sur deux cas d’étude réels d’un équipementier électronique automobile, disposant de données de tests historiques. Les résultats de nos expérimentations révèlent des gains de qualité significatifs : plus de défauts sont trouvés plus tôt et en moins de temps. / Nowadays, car electronics become more and more complex and represents more than 30% of the total cost of a car. For instance, in a 2008 BMW 5 series model, one can find up to 80 electronic modules communicating together and representing 10 million lines of software code. Facing this growing complexity, carmakers and automotive electronic suppliers are looking for efficient methods to develop, verify and validate electronic modules. In fact, they focus on the software part of these modules since it accounts for more than 80% of the total number of problems detected on these modules. In this context, we achieved our research project with the aim of proposing a global approach able to improve the quality of automotive embedded software. We started with an audit of the software practices currently used in automotive industry and we pinpointed potential levers to improve the global software quality. Based on the results of the audit and the literature review related to software quality, we developed a global approach to improve the design of test cases for software products. In fact, we developed a test generation platform to automatically generate test cases for a software product. It is mainly based on modeling the software functional requirements in order to be simulated when testing the software, focusing on critical tests to be done (because of their higher probability to detect a bug) and monitoring the automatic generation of tests by quality indicators such as the structural and functional coverage but also the tests cost. The generation of critical tests is based on the definition of real use profiles by software product and on the reuse of bugs and test cases capitalized on previous projects. Besides the computational aspects of software testing, our approach takes into account organizational matters such as knowledge management, competency management and project management. Our approach have been implemented in a computer platform and experimented on two typical case studies of an automotive electronic supplier, with historical test data. The results of our experiments reveal significant improvement in software quality: more bugs are detected earlier and in less time.
8

Mapa de apoio à gestão de dívida técnica no processo de teste de software

SOUSA, Cleydiane Lima de 19 February 2016 (has links)
Submitted by Natalia de Souza Gonçalves (natalia.goncalves@ufpe.br) on 2016-09-28T12:23:59Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertacao_Cleydiane_FINAL_Imprimir.pdf: 3971527 bytes, checksum: f06a014d16a761f030bbfccee75d176f (MD5) / Made available in DSpace on 2016-09-28T12:23:59Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertacao_Cleydiane_FINAL_Imprimir.pdf: 3971527 bytes, checksum: f06a014d16a761f030bbfccee75d176f (MD5) Previous issue date: 2016-02-19 / Dívida Técnica (DT) está relacionada a tarefas que devem ser executadas e são acumuladas ao longo de um projeto para serem realizadas posteriormente. A falta de planejamento de tempo e recursos em um projeto, dentre outros problemas, propiciam seu surgimento. DTs não solucionadas tendem a criar dependências e aumentar o grau de complexidade para correção, resultando em maior esforço, custo e retrabalho em um projeto. A sua identificação e gerenciamento ao longo de um projeto é essencial para minimizar seu impacto e consequências negativas. Estudos apontam teste de software como uma das principais áreas impactadas por DTs em projetos de software. Nesta dissertação foram mapeadas, a partir da literatura técnica, 22 possíveis DTs relacionadas ao processo de teste de software, assim como suas causas e indicadores. Elas foram avaliadas por meio de um survey com profissionais da área de teste de software. Como resultados do survey, são apresentados os níveis de concordância obtidos para cada DT, suas causas e indicadores sugeridos. Após essa validação da concordância quanto às DTs, foi identificada a necessidade de vincular soluções às causas de cada DT, para isto foi realizada uma nova revisão de literatura. A partir dos dados das DTs, com suas causas, indicadores e, agora, soluções, foi elaborado um mapa, com objetivo de apoiar profissionais da área de teste de software na gestão de DTs que podem ocorrer no decorrer da execução do processo de teste de software. Após a elaboração do mapa de gestão de dívida técnica, o mesmo foi avaliado a partir de um questionário (baseado na técnica de revisão em pares), por profissionais experientes em teste de software (líderes e consultores). Como resultado desta avaliação, são apresentadas as opiniões e considerações destes profissionais sobre a versão inicial do mapa elaborado. Por fim, é apresentado o resultado final do mapa, com as devidas alterações baseadas nas respostas obtidas no questionário de avaliação do mapa. / Technical Debit (TD) is related to the tasks which have to be executed but are accumulated during the development of a project to be implemented later. The lack of time and resource planning on a project, among other problems, facilitate its emergence. Unsolved TDs tend to create dependencies and increase the degree of complexity for corrections, resulting in bigger efforts, costs and rework on a project. Identifying and managing those issues are essential to minimize the impacts and negative consequences. Studies point out software testing as one of the most affected areas by TDs on a software project. At this dissertation, 22 (twenty-two) possible TDs related to testing software process were mapped from the technical lecture, along with its causes and indicators. They were evaluated through surveys with testing software experts. As result of the survey, it is presented the levels of accordance for each TD, also the suggested causes and indicators. After the accordance validation of the TDs, it was identified a demand to bind solutions to the causes of every TD, for this a new study was made. From the data of the TDs, along with its causes, indicators and solutions, a map was produced in order to support testing software professionals managing TDs that may appear during the testing software process execution. After producing the technical debit management map, the same was submitted for an evaluation, using a questionnaire (based on peer review technique), to testing software experts (leaders and consultants). As result of these evaluations, it is presented the opinions and remarks of those professionals about the final version of the produced map. Finally, it is presented the final result of the map, with the modifications based on the answers obtained through the map evaluation questionnaire.
9

Testing process improvement a implementace vylepšení / Testing process improvement and implementation of improvements

Chaloupecký, Martin January 2013 (has links)
This thesis deals with the testing process improvement and the implementation of specific improvement. Its objective is to describe the methodology TPI NEXT, define possible approaches to synchronization tools HP Quality Center and JIRA and implementation of the application for synchronization defects from HP Quality Center to JIRA. The first part of the thesis defines the basic terminology of testing and testing principles. Second part contains description of the methodology TPI NEXT, focusing on its key areas. The next part of the thesis describes synchronization of HP Quality Center and JIRA in the context of testing process improvement. The main part of the thesis focuses on approaches to synchronization tools HP Quality Center and JIRA and specific implementation of synchronization bridge. This bridge allows unilateral synchronization of defects from HP Quality Center to JIRA and is written in Java.
10

Sjednocení procesu testování v bankovní instituci / Unification of the testing process in banking company

Cestr, Jan January 2015 (has links)
In the present, there are several programmes used for testing in this company. This may lead to a certain mutual inconsistency of the data within the system, as well as to the decrease of orientation and efficiency among the employees, that are in charge of the quality of the developed applications. There is approximately 200 employees in the IT department who focus on the development of the software. The biggest percentage has, though, the position of the tester. The aim of this thesis is to analyse the situation and the testing process in the selected bank company. Simultaneously, we would like to reach certain possibilities to unify the process of testing.

Page generated in 0.482 seconds