Search

A aceitabilidade das aplicações Web por seus usuários depende diretamente da usabilidade da aplicação, que pode ser melhorada através da realização de inspeções. Este artigo relata um estudo de caso de inspeção de usabilidade utilizando uma técnica chamada WDP. O objetivo é analisar a eficiência e a adequação da técnica ao ambiente industrial através do Modelo de Aceitação de Tecnologia (TAM), de forma a incentivar a sua adoção em outras empresas de desenvolvimento de software.

Ubiquitous computing brings a set of characteristics that are not commonly found in conventional software projects. One of the consequences is an increase in the software development complexity. Additionally, traditional software engineering techniques are not usually adequate to support the development of this system category as they do not cover specific characteristics of this domain. Therefore, this work presents UbiCheck - an approach to support requirements definition in the ubicomp domain, including the results of an initial observational study that indicated such approach can be feasible.

This chapter presents the WDP (Web Design Perspectives-based Usability Evaluation), an inspection technique specifically designed to assess the usability of Web applications. This technique combines Web design perspectives and the heuristic evaluation method proposed by Nielsen (1994b). In addition to describing the components of the WDP technique this chapter also illustrates its use in practice by means of an industrial case study where the technique is applied to inspect a real Web application. In this case study, developers and requirement assessment staff applied the WDP technique to evaluate the usability of modules developed from scratch for a Web application. The results of this case study indicate the feasibility of performing usability inspections with the participation of a software project’s stakeholders, even when stakeholders are not usability experts.

Defect causal analysis (DCA) provides a means for product-focused software process improvement. A DCA approach, called DPPI (Defect Prevention-based Process Improvement), was assembled based on DCA guidance obtained from systematic reviews and on feedback gathered from experts in the field. According to the systematic reviews, and to our knowledge, DPPI represents the only approach that integrates cause-effect learning mechanisms (by using Bayesian networks) into DCA meetings. In this paper we extend the knowledge regarding the feasibility of using DPPI by the software industry, by describing the experience of applying it end-to-end to a real Web-based software project and providing additional industrial usage considerations. Building and using Bayesian networks in the context of DCA showed promising preliminary results and revealed interesting possibilities.

Model-Based Testing (MBT) represents a feasible and interesting testing strategy where test cases are generated from formal models describing the software behavior/structure. The MBT field is continuously evolving, as it could be observed in the increasing number of MBT techniques published at the technical literature. However, there is still a gap between researches regarding MBT and its application in the software industry, mainly occasioned by the lack of information regarding the concepts, available techniques, and challenges in using this testing strategy in real software projects. This chapter presents information intended to support researchers and practitioners reducing this gap, consequently contributing to the transfer of this technology from the academia to the industry. It includes information regarding the concepts of MBT, characterization of 219 MBT available techniques, approaches supporting the selection of MBT techniques for software projects, risk factors that may influence the use of these techniques in the industry together with some mechanisms to mitigate their impact, and future perspectives regarding the MBT field.

The selection of software technologies represents a risk factor to a software project. Therefore, using tailored software technologies to support this task can contribute to reduce the risk of inadequate choices made by software engineers. This paper presents the results of an experimental study conducted to evaluate if three dependent variables (selection time, % of correct choices, and used information) can be significantly affected by two different approaches to support the selection of Model-Based Testing techniques. This study consists of an external replication of an experiment conducted to evaluate two approaches for the selection of testing techniques. Therefore, we present the adaptations performed in the planning and design of the experiment and the challenges observed in conducting a study replication. The results indicated that the time spent to select MBT techniques and the percentage of right selections can be affected by the approach used to select MBT techniques for different software project categories.

The technical literature regarding Model-based Testing (MBT) has several techniques with different characteristics and goals available to be applied in software projects. Besides the lack of information regarding these techniques, they could be applied together in a software project aiming at improving the testing coverage. However, this decision needs to be carefully analyzed to avoid loss of resources in a software project. Based on this scenario, this paper proposes an approach with the purpose of supporting the unique or combined selection of MBT techniques for a given software project considering two aspects: the adequacy level between MBT techniques and the software project characteristics and impact of more than one MBT technique in some testing process variables. At the end, preliminary results of an experimental evaluation are presented.

Experimentation in software engineering represents a means to understand the impact of adopting software technologies. In this paper we describe an on-going experimentation work aiming at to address a real industry need in Brazil: the understanding of how performance variables (such as cost, productivity, and quality) are affected by the adoption of a nationwide software development reference model. The main strategy consists in integrating the application of carefully planned surveys into the model implementation and assessment procedures. Besides the expected performance results, we hope it can be useful to reinforce to the Brazilian software industry the importance of experimentation to support software technologies evaluation.

Defect causal analysis (DCA) is a means of product focused software process improvement. A systematic literature review to identify the DCA state of the art has been undertaken. The systematic review gathered unbiased knowledge and evidence and identified opportunities for further investigation. Moreover, some guidance on how to efficiently implement DCA in software organizations could be elaborated. This paper describes the initial concept of the DBPI (Defect Based Process Improvement) approach. It represents a DCA based approach for process improvement, designed considering the results of the systematic review and the obtained guidance. Its main contributions are tailoring support for DCA based process improvement and addressing an identified opportunity for further investigation by integrating organizational learning mechanisms regarding cause-effect relations into the conduct of DCA.

Given the growth in the number and size of Web Applications worldwide, Web quality assurance, and more specifically Web usability have become key success factors. We have developed a usability inspection technique (WDP - Web Design Perspectives-Based Usability Evaluation) specific for Web applications' usability evaluation. The results of two previous experimental studies indicate the feasibility of the WDP technique showing it to be more effective than and as efficient as Nielsen's Heuristics Evaluation. This work describes a recent step of our research, where we examined how inspectors apply the WDP technique. In order to achieve our goal, we executed an observational study, results of which lead us to two different versions of the WDP technique.

Defect causal analysis has shown itself to be a cheap and high return means of product-focused software process improvement. However, despite its advantages and wide industry adoption little academic research is being done in this area. Thus, professionals face several questions when implementing it in software organizations. Aiming to provide unbiased and evidence-based answers to those questions, a systematic review has been conducted. Based on the results of the systematic review, better guidance for implementing defect causal analysis efficiently in software organizations can be elaborated.

A aceitabilidade das aplicações Web por seus usuários depende diretamente da usabilidade da aplicação, que pode ser melhorada através da realização de inspeções. Neste artigo relatamos um caso prático de inspeção de usabilidade, no qual desenvolvedores e avaliadores de requisitos utilizaram uma técnica de inspeção para a avaliação de módulos recém-desenvolvidos. Os resultados desta experiência indicam a viabilidade de se realizarem inspeções de usabilidade com os próprios stakeholders de um projeto de software, mesmo que estes não sejam especialistas em usabilidade.

Dependency cycles among components (classes) represent a practical challenge when identifying the class integration order in object-oriented software testing. Classical approaches, such as “top-down” or “bottom-up” integration (or their combination) become less useful due to their acyclic characteristics. Some OO integration testing strategies explore the principle of breaking these dependency cycles, but broken dependencies imply that the target class will have to be stubbed when integrating and testing the source class, which increases the testing effort. This paper describes an integration testing strategy that guides software engineers to identify the class integration order with the minimum number of implemented stubs. This strategy can be directly applied to high level OO design (UML class) diagrams allowing the reduction of extra construction efforts related to additional classes needed in other strategies. The results from experimental studies have indicated its feasibility and effectiveness. The use of such integration testing strategy can be supported by a case tool, also described in this paper.

Software technologies, such as model-based testing approaches, have specific characteristics and limitations that can affect their use in software projects. To make available knowledge regarding such technologies is important to support the decision regarding their use in software projects. In particular, a choice of model-based testing approach can influence testing success or failure. Therefore, this paper aims at describing knowledge acquired from a systematic review regarding model-based testing approaches and proposing an infrastructure towards supporting their selection for software projects.

Experimental replications are very important to the advancement of empirical software engineering. Replications are one of the key mechanisms to confirm previous experimental findings. They are also used to transfer experimental knowledge, to train people, and to expand a base of experimental evidence. Unfortunately, experimental replications are difficult endeavors. It is not easy to transfer experimental know-how and experimental findings. Based on our experience, this paper discusses this problem and proposes a Framework for Improving the Replication of Experiments (FIRE). The FIRE addresses knowledge sharing issues both at the intra-group (internal replications) and inter-group (external replications) levels. It encourages coordination of replications in order to facilitate knowledge transfer for lower cost, higher quality replications and more generalizable results.

The development of ubiquitous software project demands the use of specific software technologies to deal with the inherent complexity of this type of project. Despite the advances in the software engineering field, the building of ubiquitous software still represents a grand challenge. For instance, secondary and primary studies indicated the existence of 13 ubiquity characteristics that can influence ubiquitous software projects. Therefore, in this paper we describe these ubiquity characteristics organized into a body of knowledge regarding ubiquitous computing and used to characterize ubiquitous software projects. Besides, an ongoing research concerned with supporting ubiquity requirements definition and verification (checklist based inspection) activities is also introduced.

Model-based testing (MBT) approaches help automatically generate test cases using models extracted from software artifacts, and hold the promise to greatly affect how we build software. A review of the literature shows that certain specialized domains are applying MBT, but it does not yet seem to be a mainstream approach. The authors therefore conducted a systematic review of the literature to investigate how much evidence is available on MBT's costs and benefits, especially regarding how these techniques compare to other common testing approaches. They use these results to derive suggestions regarding what types of studies might further increase the deployment of these techniques.

This paper describes a systematic review performed on model-based testing (MBT) approaches. A selection criterion was used to narrow the initially identified four hundred and six papers to focus on seventy-eight papers. Detailed analysis of these papers shows where MBT approaches have been applied, the characteristics, and the limitations. The comparison criteria includes representation models, support tools, test coverage criteria, the level of automation, intermediate models, and the complexity. This paper defines and explains the review methodology and presents some results.

Given the growth in the number and size of Web Applications worldwide, Web quality assurance, and more specifically Web usability have become key success factors. Therefore, this work proposes a usability evaluation technique based on the combination of Web design perspectives adapted from existing literature, and heuristics. This new technique is assessed using a controlled experiment aimed at measuring the efficiency and effectiveness of our technique, in comparison to Nielsen's heuristic evaluation. Results indicated that our technique was significantly more effective than and as efficient as Nielsen's heuristic evaluation.

In this paper, we report the experiences of a working group who met, as part of the 2006 Dagstuhl Seminar on Empirical Software Engineering, to discuss the teaching of empirical methods to undergraduate students. The nature of the discussion meant that the group also indirectly considered teaching empirical methods to postgraduate students, mainly as a contrast to understand what is appropriate to teach at undergraduate and postgraduate level. The paper first provides a summary of the respective experiences of the participants in the working group. This summary is then used to informally assess the progress that has been made since the previous Dagstuhl Seminar, held in 1992. The paper then reviews some issues that arise when teaching methods to undergraduate students. Finally, some recommendations for the future development of courses are provided.

For a long time scientists have been committed to describe and organize information acquired by observations from the field. To improve the comprehension and testability of the observed information, Bacon’s works proposed to organize the way that the experiences should be structured and somehow formalized, starting with the experimental method idea. From that point in time, the ideas regarding experimentation have been explored and evolved into different scientific areas, including physics, agriculture, medicine, engineering and social sciences among others. It has not been different in Software Engineering. By applying the scientific method to organize their experimental studies, software engineers have intensively worked to understand the application and evolution of software processes and technologies. Acquiring knowledge through different categories of experimental studies has supported researchers and practitioners to build a Software Engineering body of knowledge. Families of studies start to be planed and shared among the research community, composing a common research agenda to enlarge such body of knowledge. Based on this, evidence based software engineering is becoming a reality. Nowadays, besides the experimental studies, the experimentation approach represents an important tool to allow the transfer of software technology to the industry and to improve software processes.

Inspeção de software é uma técnica eficiente para reduzir o trabalho e melhorar a qualidade de artefatos de software. Entretanto, na indústria a aplicação de inspeções muitas vezes se dá de forma pouco sistemática e seu verdadeiro potencial é raramente atingido. Neste artigo relatamos a experiência da institucionalização do processo de inspeção de software para a realização de inspeções de requisitos em um projeto real que segue um ciclo de vida incremental. Entre os resultados obtidos destacamos a identificação de oportunidades de melhoria no processo de software, a partir da análise dos resultados das inspeções em incrementos anteriores.

Este artigo apresenta um arcabouço para a realização de projetos- piloto de forma sistemática, planejada e controlada para que os efeitos das mudanças dos processos de software possam ser observados e mensurados antes de sua institucionalização.

Software testing can be applied during the software development with the purpose of improving the final product quality. However, there is a gap between the state of the art and the state of the practice regarding software testing area. There are just a few evidences concerned with effectiveness of software testing practices suggested by the technical literature in the industry. Based on this context, this paper shows the characterization of the software testing actual state for a specific software development scenario, where it has been evaluated what practices are being applied by these organizations. The results have shown the lack, limitation, and interest of these organizations in the applying of testing for their software projects. Resumo. As atividades de teste estao sempre presentes no desenvolvimento de um software com o objetivo de contribuir para a qualidade do produto final. No entanto, percebe-se a existencia de uma grande diferenca entre o estado da arte e o estado da pratica de teste de software. Existem poucas evidencias relatadas da efetividade das praticas de teste de software sugeridas pela literatura tecnica na industria. Baseado neste contexto, este artigo apresenta a caracterizacao do estado atual das praticas de teste em um cenario de desenvolvimento de software especifico, onde foram avaliadas quais praticas de teste estao sendo adotadas pelas organizacoes. Os resultados indicam carencia, limitacao e o interesse dessas organizacoes em aplicar praticas de teste de software em seus projetos. 1. Introducao

This paper presents a new reading technique called OO-PBR. OO- PBR has been defined in order to allow identifying critical defects in software requirements written in natural language. OO-PBR supports requirements review by exploring object oriented modeling. The steps for defining OO-PBR, its assumptions and experimental results are discussed along the paper. Resumo. Este artigo apresenta uma nova tecnica de leitura, denominada OO- PBR. OO-PBR tem como principal objetivo a deteccao de defeitos criticos em documentos de requisitos de software descritos em linguagem natural. OO- PBR apoia a revisao dos requisitos ao explorar a construcao de modelo de projeto orientado a objetos. As etapas para a definicao de OO-PBR sao discutidas, destacando-se as premissas e os resultados experimentais obtidos. 1. Introducao O documento de requisitos desempenha um papel fundamental no desenvolvimento de software. Ao descrever as caracteristicas e funcionalidades que o sistema deve possuir, o documento de requisitos representa o interesse de diferentes stakeholders, incluindo usuarios, clientes, engenheiros de software, gerentes, entre outros (Sommerville, 2004). Tais stakeholders podem possuir diferentes pontos de vista a respeito das funcionalidades e das restricoes envolvidas no sistema a ser desenvolvido. Dessa forma, e fundamental que o documento de requisitos passe constantemente por um processo de atualizacao e de revisao. Diante desse contexto, uma importante questao identificada e

OBJECTIVE - The objective of this paper is to determine under what circumstances individual organisations would be able to rely on cross-company based estimation models. METHOD - We performed a systematic review of studies that compared predictions from crosscompany models with predictions from within-company models based on analysis of project data. RESULTS - Ten papers compared cross-company and within-company estimation models, however, only seven of the papers presented independent results. Of those seven, three found that crosscompany models were as good as within-company models, four found cross-company models were significantly worse than within-company models. Experimental procedures used by the studies differed making it impossible to undertake formal meta-analysis of the results. The main trend distinguishing study results was that studies with small single company data sets (i.e.

Software organizations have to adapt efficiently to cope with clients needs changes and new and evolving technologies in order to guarantee business success. Moreover, organizations must continuously enhance their capability to develop software in order to increase products and processes quality. These characteristics constitute dynamic environments that require specific competences from software engineers such as knowledge related to software technologies, ability to adapt software processes concerning project characteristics, and experience on product and process quality management. This paper presents enterprise-oriented software development environments that support software engineers to execute software processes more effectively and to produce products with better quality. A main feature of these environments is the support offered to organizational knowledge management. Thus the paper also presents the main characteristics of the knowledge management infrastructure integrated to those environments. The practical experience using the environments has shown several benefits, such as an increase of product and process quality, and the preservation of organizational knowledge related to software processes and the development of software products.

Software Engineering is a wide area of knowledge and various other types of knowledge are required during the software development and maintenance. This paper describes a survey carried out to characterize the importance given by software developers to varying types of knowledge mentioned in the technical literature on Software Engineering. The survey results have been used to guide the elaboration and incorporation of content and tools to the TABA workstation, which allows one to configure and instantiate software development environments for different companies. This paper also addresses the use of the TABA workstation to support software processes deployment in small and medium size Brazilian companies. The goal is to increase the capability of software organizations by the adequate use of Software Engineering techniques in their development and maintenance processes.

Este artigo define Ambientes de Desenvolvimento de Software Orientados a Organização (ADSOrg) como sendo ambientes de desenvolvimento de software que apóiam a gerência do conhecimento relevante para os processos de desenvolvimento e manutenção de software da organização. Além disso, propõe um modelo que especifica os componentes necessários para que tais ambientes contemplem os seus requisitos. Uma estratégia para a construção de ADSOrg a partir de um meta-ambiente também foi definida, implementada e utilizada. Este artigo ainda apresenta um resumo dos resultados de uma pesquisa de campo realizada com a finalidade de orientar os futuros esforços de incorporação de conteúdo e desenvolvimento de ferramentas para ADSOrg.

Uma questão crucial quando aplicando teste de integração em software orientado a objetos é decidir a ordem de integração das classes. As classes precisam ser integradas uma de cada vez ou, em alguns casos, em pequenos clusters [7] já que a abordagem de integração big-bang se demonstra inadequada nesta situação. Conceitos como encapsulamento, herança e polimorfismo adicionam complexidade aos testes, fazendo com que critérios precisem ser estabelecidos para, eventualmente, quebrar a dependência existente entre as classes sem aumentar a complexidade (esforço) do teste. Este trabalho apresenta um conjunto de heurísticas aplicadas aos diagramas de classes UML que permitem estabelecer uma ordem de prioridade para o teste de integração das classes que compõem o software, utilizando o número de stubs necessários para o teste como medida do esforço requerido. Quando comparada às abordagens existentes, estas heurísticas se aplicam em nível mais alto de abstração (projeto), facilitando sua utilização e permitindo antecipar a tomada de decisão no planejamento do teste de integração. Um estudo de caso demonstra sua aplicação e realiza uma comparação dos resultados com estudos realizados encontrados na literatura.

O objetivo de inspeções de software é melhorar a qualidade de artefatos de software através de sua análise, detectando e removendo defeitos antes que o artefato seja passado para a próxima fase do processo de desenvolvimento de software. Muito conhecimento tem sido produzido na área de inspeções de software e se mostrado adequado através de estudos experimentais. Entretanto, pouco apoio computacional capturando este conhecimento está disponível. Este artigo apresenta uma infra-estrutura computacional para apoio ao processo de inspeção de software utilizando como conjunto básico de requisitos o conhecimento adquirido através de estudos experimentais relacionados à inspeção de software.

Entregar um produto com qualidade, dentro do prazo e custos esperados é hoje um grande desafio para as organizações. Fatores como esses impulsionam o interesse, por parte das organizações, pela estimativa e controle do tempo e custos dos projetos de software. Nas últimas décadas, muitas pesquisas têm sido realizadas no sentido de desenvolver modelos para estimar prazos e custos que resultem em estimativas o mais próximo possível dos valores reais dos projetos. A utilização dos conceitos e práticas de gerência do conhecimento tem se mostrado eficiente no apoio ao planejamento de tempo e custos de projetos. Este artigo apresenta o trabalho desenvolvido em uma tese de mestrado que propõe uma abordagem para o planejamento de tempo e custos de projetos de software, baseada nas normas NBR ISO 10006, ISO/IEC DTR 16326, no guia PMBOK (Project Management Body of Knowledge), nos princípios da gerência do conhecimento e nos modelos paramétricos COCOMO II e Análise de Pontos de Função. A ferramenta CustPlan, desenvolvida para apoiar a abordagem descrita, também é apresentada.

Ambientes de Desenvolvimento de Software têm evoluído ao longo do tempo para fornecer apoio mais amplo e efetivo aos desenvolvedores de software. Neste contexto, surgiram os Ambientes de Desenvolvimento de Software Centrados em Processo e os Ambientes de Desenvolvimento de Software Orientados a Organização. Este artigo apresenta a abordagem adotada pela Estação TABA, um meta-ambiente de desenvolvimento de software, para a definição de processos de software para organizações e projetos específicos dentro do contexto dos Ambientes de Desenvolvimento de Software Orientados a Organização. Esta abordagem está baseada na definição de processos em três níveis: processos padrão, especializado e instanciado.

The implementation of knowledge management mechanisms to convert individual knowledge into organizational knowledge is important to guarantee business success in the global and dynamic economy. Besides that, there is a trend in the software industry to create a consistent body of software process knowledge across different organizations through the conversion of organizational knowledge into multi- organizational knowledge. Since software organizations do not execute software processes in the same way, the creation of such body of knowledge is a difficult task. This work presents a knowledge acquisition approach aimed to acquire organization members’ knowledge and store it in a software process community of practice repository accessible through a Web-based system. The application and evaluation of knowledge captured in the context of a specific organization, and reuse of such knowledge in different contexts provides the means for converting organizational knowledge into multi-organizational knowledge.

Software Development Environments have evolved to support software developers activities, and to support organizations to achieve goals such as productivity enhancement, quality improvement, cost reducing, and decrease of time-to-market solutions. In this context, have appeared the Process-centered Software Development Environments and, more recently, the Enterprise-Oriented SoftwareDevelopment Environments. This paper presents the main approaches adopted on the Taba Workstation, a software development meta-environment, to support knowledge management in the context of Enterprise-Oriented Software Development Environments: an ontology-based infrastructure, a knowledge acquisition tool, and a community of practice system.

Entregar um produto com qualidade, dentro do prazo e custos esperados é hoje um grande desafio para as organizações. Fatores como esses impulsionam o interesse, por parte das organizações, pela estimativa e controle do tempo e custos dos projetos de software. Nas últimas décadas, muitas pesquisas têm sido realizadas no sentido de desenvolver modelos para estimar prazos e custos que resultem em estimativas o mais próximo possível dos valores reais dos projetos. A utilização dos conceitos e práticas de gerência do conhecimento tem se mostrado eficiente no apoio ao planejamento de tempo e custos de projetos. Este artigo apresenta uma abordagem para o planejamento de tempo e custos de projetos de software, baseada nas normas NBR ISO 10006, ISO/IEC DTR 16326, no guia PMBOK (Project Management Body of Knowledge), nos princípios da gerência do conhecimento e nos modelos paramétricos COCOMO II e Análise de Pontos de Função. A ferramenta CustPlan desenvolvida para apoiar a abordagem descrita também é apresentada.

O planejamento de riscos é uma das atividades iniciais de um projeto de software e requer uma visão global da organização, sendo fortemente centrado na experiência e conhecimento adquiridos em projetos anteriores. Quanto maior a experiência do gerente de projeto, melhor ele será capaz de identificar riscos, estimar sua probabilidade de ocorrência e impacto e definir os planos de mitigação e contingência. Porém, o conhecimento de riscos de um gerente de projeto não pode permanecer no nível de indivíduo. Para que a organização evolua aprendendo com seus próprios erros e acertos, é necessário que o conhecimento seja gerenciado de forma a tornar possível sua captura, recuperação e futura utilização. Este artigo apresenta uma abordagem para o planejamento de riscos em projetos de software baseada na reutilização do conhecimento organizacional de riscos. São apresentados um processo de gerência de riscos centrado na captura e utilização do conhecimento organizacional de riscos e uma ferramenta de apoio à abordagem proposta. Os resultados de um estudo experimental das relações entre fatos e riscos de projetos de software são apresentados, enfatizando-se sua utilização no contexto da abordagem descrita.

As empresas vêm demonstrando ao longo dos últimos anos um grande interesse no desenvolvimento OO. Nesse sentido, muitas delas já adotaram o RUP como base para seu processo de desenvolvimento. Por ser um framework para processo, diversas variáveis podem afetar sua adaptação, execução e gerência para um projeto. Ter conhecimento sobre essas variáveis e os impactos causados por elas no projeto é fundamental para melhoria contínua do processo. Através da definição de uma estratégia para adquirir conhecimentos, tais como pontos fortes e fracos aprendidos ao longo do projeto, pretende-se atacar com mais objetividade os processos mais deficientes (pontos fracos) e incentivar que os pontos fortes continuem sendo aplicados em projetos futuros. Um estudo de caso aplicando a estratégia de aquisição de conhecimento em um projeto que utiliza um processo baseado no RUP é apresentado. Além disso, uma estratégia para disseminação de conhecimento é descrita. Essa estratégia está fundamentada na construção de planos de ação elaborados com base nas necessidades da equipe.

Recently the awareness of the importance of replicating studies has been growing in the empirical software engineering community. The results of any one study cannot simply be extrapolated to all environments because there are many uncontrollable sources of variation between different environments. In our work, we have reasoned that the availability of laboratory packages for experiments can encourage better replications and complementary studies. However, even with effectively specified laboratory packages, transfer of experimental know-how can still be difficult. A cooperation between Brazilian and American researchers addressing effective running of replications was formed in 1999. One of the specific issues being addressed is the problem of transferring tacit knowledge. We discuss what we learned about the tacit knowledge transfer problem and the evolution of laboratory packages in the description of a replication performed in Brazil using a PBR (Perspective Based Reading) laboratory package; also how further issues are addressed.

This paper describes an object-oriented (O.O.) software engineering training experience, within a collaboration project between academia and industry. This experience involves the academia-industry exchange both for training and technology transfer. The project and team characteristics are described as well as the performed work and obtained results.

The paper addresses an approach to behavior testing in object oriented systems. This approach is used in the MEMPHIS project (C.M.I. Werner et al., 1997) and emphasis on state based testing. The key elements are the generation of testing sequences based on the state transition diagram to test the system objects and the creation of testing scenarios, which allow the verification of object integration.

Considering the systematization of software reuse, it is important to have automated support, such as that provided by software development environments (SDEs). However, in order to have a reuse-based SDE (RBSDE), an adequate software development process, methods and tools that consider software reuse activities must have been previously defined. We describe in this paper the Memphis environment, a RBSDE under development at the Computer Science Department of COPPE/UFRJ (the Computer Science Department of the Federal University of Rio de Jnneiro) that explores object-oriented (OO) technology in order to achieve its objectives. It supports the activities involved in software management, construction, quality assurance and reuse by providing an integrated set of tools and a reuseable component repository.

Em busca da melhoria da qualidade de seus produtos e do aumento da produtividade de suas equipes, organizações têm prestado mais atenção em seus processos de software. Este esforço tem envolvido a definição de um processo para a organização e o estabelecimento de metas de melhoria, levando em consideração boas práticas de engenharia de software. No entanto, nossa experiência em definir processos de software para várias organizações tem mostrado que o conhecimento sobre o domínio e a cultura organizacional são aspectos importantes para a melhoria dos processos de software. Desta forma, descrevemos como nossa abordagem para a definição de processos de software e para suporte automatizado ao desenvolvimento de software evoluiu para tratar estes aspectos. O resultado foi o surgimento de duas novas famílias de ambientes de desenvolvimento de software: Ambientes de Desenvolvimento de Software Orientados a Domínio (ADSOD) e Ambientes de Desenvolvimento de Software Orientados a Organização (ADSOrg). Este artigo apresenta, ainda, um resumo das lições que temos aprendido na definição e melhoria de processos de software.

O gerenciamento de projetos é uma atividade fortemente baseada em conhecimento. Os gerentes utilizam suas habilidades e sua experiência para tomar decisões durante a execução de um processo de desenvolvimento de software. Geralmente, os gerentes experientes obtém mais sucesso que os gerentes novatos em termos de atingir metas de cronograma, custos e funcionalidade. Estes melhores resultados são atingidos devido à experiência acumulada ao longo de situações ocorridas em projetos no passado e no conhecimento derivado destas experiências. Nesta tese, abordamos a criação e reutilização de conhecimento relacionado com o gerenciamento de projetos de software. Apresentamos uma representação para este tipo de conhecimento, os modelos de cenários, que permitem que um gerente verifique o impacto de teorias, ações e estratégias gerenciais que podem ser aplicadas ou impostas sobre um projeto de software. Apresentamos os resultados de estudos experimentais para análise da viabilidade das técnicas propostas e uma aplicação da abordagem proposta em um processo de gerenciamento de riscos.

Observa-se que a atividade de inspeção e as técnicas de leitura associadas são, em geral, discutidas sem considerar explicitamente um processo subjacente de desenvolvimento de software. Em particular, quando se considera a abordagem OO (Orientada a Objetos), as técnicas são, em geral, associadas às notações definidas pela UML (Unified Modeling Language). O fato da UML não estar vinculada a um processo de desenvolvimento dificulta a definição e implantação de atividades de garantia de qualidade de software, em especial, atividades de VV&T (Validação, Verificação e Teste). A falta de um processo permite uma livre escolha do conjunto de diagramas selecionados para o desenvolvimento de uma aplicação, além do que a forma de utilização dos mesmos e a interpretação dos conceitos da própria UML podem variar dentro de um mesmo ambiente de desenvolvimento. Ressalta-se ainda que a atividade de inspeção é essencial para que um determinado processo atinja o nível 3 do CMM (Capability Maturity Model). As técnicas de leitura OORTs (Object Oriented Reading Techniques) foram definidas para um subconjunto da notação UML, considerando um processo de software genérico e simplificado e se aplicam essencialmente na fase de projeto. Neste artigo define-se um conjunto de técnicas de leitura para apoiar atividades de inspeção em um processo de desenvolvimento de software OO baseado na notação UML, denominado ProDeS/UML, que inclui atividades de teste ao longo de suas fases desenvolvimento. Esse conjunto de técnicas de leitura denomina-se OORTs/ProDeS e consiste da integração das técnicas OORTs e da definição de novas técnicas de leitura no contexto do processo ProDeS/UML.

This text describes a simple and effective object oriented software design process template having UML as the modeling language and extensively using inspections to support the construction and maintenance of software products. This software design process uses a sequential organization, based on the waterfall approach, for two reasons: to simplify the explanation of design activities in the context of this text and to make available a standard process that can be continuously improved by developers. The component phases of this design process are described in a way that gives developers the freedom to reorganize the overall process based on their own needs and environment. In addition, a survey is provided of specific literature regarding important aspects of UML and the object oriented paradigm.