Software Inspection is an effective and efficient method aiming at discovering faults within software artifacts early in the development lifecycle. The success of software inspections is highly dependent on reading techniques that guide the reviewer through the individual inspection. In other words, reading techniques help the reviewer during the inspection process. In this thesis a quite new reading technique, namely usage-based reading, is further evaluated. A reviewer who applies usage-based reading is guided by a set of prioritized use-cases. Hereby the use-cases are ranked according to their importance from the point of view of the user. Thus, the reviewers inspection effort is focused on the parts of the document that concern the most important functionality from the user’s perspective. The particular goal of this study is to figure out whether time-budgets assigned to each use-cases lead to improvements in inspection performance expressed in terms of efficiency, effectiveness and fault content. This concept is called time-controlled reading. The time-budget determines that a particular use-case must not be inspected longer than a certain number of minutes. Initially the assumption was made that time-budgets lead to performance improvements because the reading process can be better planned in forehand, that means most time is spent on the most important use-cases and all use-cases are utilized within the given inspection time. However, the result of this study contradicts that assumption. I found that both techniques are equally efficient and effective and that they find the same fault content. The reason for this is that the techniques are still quite similar and that the timebudgets assigned to the use-cases did not allow the subjects to thoroughly investigate the use-cases because they struggled with the unknown application domain. This is at least the case for lower ranked use-cases with smaller time-frames. As a consequence of this, one can claim that the results might have pointed in favor for time-controlled reading when people familiar with the application domain would have done the same experiment. / kai-petersen@gmx.de

Submitted by PPG Ci?ncia da Computa??o (ppgcc@pucrs.br) on 2018-05-08T18:28:23Z No. of bitstreams: 1 GABRIEL_PIMENTEL_AFFONSO_DE_OLIVEIRA_DIS.pdf: 1728021 bytes, checksum: ccf1b372e65c1d0cf709157eeb0723ca (MD5) / Approved for entry into archive by Caroline Xavier (caroline.xavier@pucrs.br) on 2018-05-15T18:27:29Z (GMT) No. of bitstreams: 1 GABRIEL_PIMENTEL_AFFONSO_DE_OLIVEIRA_DIS.pdf: 1728021 bytes, checksum: ccf1b372e65c1d0cf709157eeb0723ca (MD5) / Made available in DSpace on 2018-05-15T18:37:12Z (GMT). No. of bitstreams: 1 GABRIEL_PIMENTEL_AFFONSO_DE_OLIVEIRA_DIS.pdf: 1728021 bytes, checksum: ccf1b372e65c1d0cf709157eeb0723ca (MD5) Previous issue date: 2018-03-14 / Tradicionalmente, a engenharia de requisitos se baseia na execu??o sequencial de atividades. Por outro lado, a engenharia de requisitos em metodologias ?geis ? informal. Projetos ?geis s?o bem sucedidos ?sem requisitos? gra?as ao fato de que casos de teste s?o comumentemente vistos como requisitos e de que requisitos s?o detalhados como casos de teste que servem tambem para validar e aceitar cada funcionalidade. Um dos formato destes testes de aceita??o s?o cen?rios criados a partir da t?cnica de desenvolvimento orientado a comportamento (do ingl?s, behavior-driven development, BDD). Estes cen?rios ajudam a evitar problemas de comunica??o entre especialistas de dom?nio e programadores, j? que estes cen?rios s?o escritos numa linguagem comum a esses dois grupos, permitindo um caminho menos amb?guo dos requisitos de neg?cio para a especifica??o do comportamento do um software. Entretanto, aqueles que formalizam cen?rios BDD n?o possuem um conjunto padr?o de regras para se familiarizarem com o conceito de um ?bom? cen?rio, o que pode permitir que cen?rios BDD sofram de problemas conhecidos pela engenharia de requisitos, tais como requisitos incompletos, mal especificados ou inconsistentes. Portanto, para preencher essa lacuna, nessa pesquisa foram coletados dados de entrevistas semi-estruturadas com praticantes de BDD para propormos uma lista de verifica??o baseada em quest?es com 12 perguntas associadas a 8 atributos de qualidade. Esse instrumento deve prover aos praticantes de BDD orienta??es padronizadas para o refinamento de seus cen?rios. / Traditional requirements engineering approaches are based on a sequential execution of activities. In the other hand, requirements engineering in agile development is informal. Agile projects succeed ?without requirements? due to the fact that test cases are commonly viewed as requirements and detailed requirements are documented as test cases that also validate and accept each feature. One format of those acceptance test cases is Behavior-Driven Development scenarios. Those scenarios help to avoid communication problems between the domain experts and programmers on the team, as they are defined using a common language that allows for an easy, less ambiguous path from end-user business requirements to the specification of how the software should behave. However, those who formalize BDD scenarios do not have a standard set of rules to educate themselves on what a ?good? BDD scenario is, which can allow BDD scenarios to suffer from other known problems in requirement engineering such as incomplete, underspecified and inconsistent requirements. Therefore, to fill that gap, this research gathered data from semi-structures interviews performed with BDD practitioners to propose a question-based checklist based on 8 newly defined quality attributes. This question-based checklist provides practitioners with an standard guideline for BDD scenarios? refinement

This diploma thesis investigates the question of the development of reading skills and their relationship with the self-concept of an individual. The teoretical part describes a development of reading literacy from the view of language, because a development of reading closely depends on a language, in which an individual learns to read. Also, it describes a development of reading literacy from the view of variables, which can be found inside of an individual and his environment. Next, we focus on the development of self-concept and self-evaluation, and we describes the specifics of self- evaluation of reading at the end. In the empirical part, we analyse data that were obtained from an Research project of the GAČR, which was carried out in 2013-2015 by members of the working group at the Department of psychology and other specialist from the Department of primary pedagogy and Czech language on College of Education at Charles University in Prague. We analysed of a reading self-evaluation questionnaire of pupils in 3rd and 4th grade of primary school and we compare their scores in the questionnaire with their achievement in a couple of grammar tests which measure two basic components of reading - understanding and decoding. At the end we show examples of case studies of pupil with high and low...

Made available in DSpace on 2016-06-02T19:04:00Z (GMT). No. of bitstreams: 1 6812.pdf: 4823701 bytes, checksum: d6b0f954a2db7f87a5e2bcda3295cb11 (MD5) Previous issue date: 2014-05-30 / Context: Usually, developers of Embedded Systems (ESs) start the development from models next to the code generation phase, for example, SysML diagrams and Simulink models. Despite the whole use of these models by the ES community, there is a lack of Verification and Validation activities (V&V). The certification standards operate, mainly, on code level. Aim:to define a family of reading techniques Reading Techniques for SysML and Simulink (RTSS) that supports the inspection of these diagrams and models, aiming to improve the process and product quality through defects identification, as soon as artifacts are elaborated. Method: the reading techniques were defined based on a systematic process and they support pairs of artifacts. They take some international certification standards into account, as well as elements from the structure of SysML and Simulink languages. Besides, aiming to suggest the use of these techniques inside a development process, the SYSMOD process was took as reference, since it adopts SysML diagrams and Simulink models along its phases. For evaluating the RTSS techniques two controlled experiments and three case studies were conducted as the techniques were elaborated. Results: the results showed that it is feasible to use the techniques and that they are able to detect defects on the pair of artifacts for the ones they were designed. In addition, it was observed that defects that were not identified and corrected inside the phase they were generated, were propagated to the subsequent phases. Conclusion: Based on these results, we can conclude that the RTSS techniques are able to detect defects as the artifacts are elaborated, avoiding their propagation to further phases. This fact can improve both the process and the product besides minimize the rework and the cost of correcting defects in further phases. Finally, we observed that the techniques can be applied even the SYSMOD process is not being used. In this case, it is enough that the pair of artifacts dialed by each technique is available. / Contexto:Em geral, os desenvolvedores de Sistemas Embarcados (SEs) iniciam tais sistemas a partir da elaboração dos diagramas mais próximos da fase de geração de código, como por exemplo, alguns diagramas SysML e o modelo Simulink. Apesar do amplo uso de tais diagramas pela comunidade de SEs, observa-se uma carência por atividades de Verificação e Validação (V&V). As normas de certificação existentes atuam, principalmente, no nível de código. Objetivo:definir uma família de técnicas de leitura Reading Techniques for SysML and Simulink (RTSS) que dê suporte à atividade de inspeção desses tipos dos diagramas, com o intuito de melhorar a qualidade do processo e do produto gerado, identificando defeitos tão logo os artefatos sejam construídos. Metodologia: as técnicas de leitura foram definidas por meio de um processo sistemático e dão suporte à inspeção de pares deartefatos. Elas levam em consideração algumas normas internacionais de certificação de SEs, além de elementos pertinentes às estruturas das linguagens SysML e Simulink. Além disso, para propiciar o uso das técnicas ao longo de um processo de desenvolvimento, utilizou-se como referência o processo SYSMOD, que adota diagramas SysML e modelos Simulink ao longo de suas fases. Para avaliar as técnicas RTSS foram conduzidos dois experimentos controlados e três exemplos de aplicação,à medida que as técnicas foram elaboradas.Resultados: os resultados mostraram que as técnicas são viáveis de serem utilizadas e que elas são capazes de identificar defeitos nos pares de artefatos para os quais elas foram projetadas. Além disso, constatou-se que defeitos que não foram identificados e corrigidos em uma determinada fase do desenvolvimento, foram propagados para fases subsequentes. Conclusão: Com base nesses resultados, pode-se concluir que as técnicas RTSS são capazes de detectar defeitos à medida que os artefatos são construídos, evitando que eles sejam propagados para fases futuras. Isso pode melhorar a qualidade do processo e do produto e pode também minimizar o retrabalho e o custo de se corrigir um defeito em fases adiantadas. Adicionalmente, as técnicas podem ser aplicadas mesmo que o processo SYSMOD não seja adotado, bastando que se tenha disponível o par de artefatos que é tratado em cada uma das técnicas.

Made available in DSpace on 2015-04-11T14:02:47Z (GMT). No. of bitstreams: 1 natasha.pdf: 409600 bytes, checksum: c6c9263e7940b7fa446c53d362613827 (MD5) Previous issue date: 2013-02-20 / FAPEAM - Fundação de Amparo à Pesquisa do Estado do Amazonas / This thesis presents a systematic mapping about techniques for models inspection to ensure the usability and the categorization and analysis these techniques. Moreover, this thesis presents a set of reading techniques specific for usability inspection in design models of software development, MIT (Model Inspection Technique for Usability Evaluation). These techniques have a set of check items that guide the inspector during the usability evaluation. Their purpose is be easily adoptable by software development industry, besides the possibility of be used independently or combined, i.e., their use might vary according with the procedure of development adopted. As the MITs had its construction and evaluation supported by experimentation, this thesis also discusses about the study on academy, as well as evolution of the techniques / Esta dissertação apresenta o mapeamento sistemático realizado sobre Técnicas de Inspeção de Modelos que garantam a Usabilidade e a categorização e análise destas técnicas. Além disso, esta dissertação apresenta um conjunto de técnicas de leitura específicas para inspeção de usabilidade em modelos de projeto de desenvolvimento de software, a MIT (Model Inspection Technique for Usability Evaluation). Estas técnicas possuem um conjunto de itens de verificação que guiam o inspetor durante a avaliação de usabilidade. O seu propósito é que seja facilmente adotável pela indústria de desenvolvimento de software, além da possibilidade de serem usadas de forma independente ou combinada, ou seja, seu uso poderá variar de acordo com o processo de desenvolvimento adotado. Como as MITs tiveram sua construção e avaliação apoiada por experimentação, esta dissertação também aborda sobre o estudo de viabilidade realizado, além da evolução das técnicas.